Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mcvax!ukc!pc
From: pc@ukc.ac.uk (R.P.A.Collinson)
Newsgroups: comp.sys.atari.st
Subject: Re: A couple of questions
Message-ID: <2229@eagle.ukc.ac.uk>
Date: Fri, 5-Dec-86 20:19:56 EST
Article-I.D.: eagle.2229
Posted: Fri Dec  5 20:19:56 1986
Date-Received: Sun, 7-Dec-86 03:46:26 EST
Reply-To: pc@ukc.ac.uk (R.P.A.Collinson)
Organization: U of Kent at Canterbury, Canterbury, UK
Lines: 18

KJBSF@slacvm.bitnet writes:
>I've been getting some message from Mark Williams C about an 'outdated
>ranlib' whenever I try to use the AES or VDI libraries when compiling
>a program.  What does this mean?  Do I need to send my disks back to MW to
>get something fixed?
>
I got this on libc.a when I copied it from the floppy onto a hard disc.
I did
	<ensure the date is correct>
	ar x libc.a ranlib.sym
	ar r libc.a ranlib.sym
	(I went to do an rm ranlib.sym and discovered hat the file had
	 already gone)
	
and after a lot of disc whirring the problem went away. Basically, I altered
the time on the symbol table file to be after that on the ar file.

Would have been nice to have had a ranlib out of MW C tho...