🚀 go-pugleaf

In article <1992Sep1.151041.15826@micrografx.com> sstaton@micrografx.com (Steven R. Staton) writes:
>When I build an archive (library) using 'ar r <objectfilelist>' and then  
>run ranlib on it, I cannot link the object modules into any code.  ld  
>reports:
>
>/bin/ld: table of contents for archive: /usr/lib/libTest.a is out of date;  
>rerun ranlib(1) (can't load from it)
>
>When I build the f2c package, it does the exact same thing except that I  
>can link the libF77 and libI77 libraries without incident.  The only  
>difference between how f2c makes it's libraries is in the source; ie. no  
>difference in the methodology.
>
>Does anyone know what secret ingredient I am missing?
>-- 
>     Steven R. Staton      |   The two most common things in the
>     Micrografx, Inc.      | Universe are Dark Matter and Stupidity
>  sstaton@micrografx.com   |

It may happen, that you had copied your *.a file from temporary location, after
calling your ranlib. If this is the case, the time change caused by copying
results in the linker problems you quote.

You can use "cp -p ..." to preserve the date/time.

	-Z.