Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utcs!mnetor!seismo!ut-sally!pyramid!decwrl!sun!guy
From: guy@sun.UUCP
Newsgroups: net.unix-wizards
Subject: Re: ranlib and ``ucb''
Message-ID: <5019@sun.uucp>
Date: Fri, 11-Jul-86 14:19:12 EDT
Article-I.D.: sun.5019
Posted: Fri Jul 11 14:19:12 1986
Date-Received: Sat, 12-Jul-86 06:22:57 EDT
References: <1916@brl-smoke.ARPA> <1278@ncoast.UUCP> <292@foxvax5.UUCP> <2041@brl-smoke.ARPA>
Organization: Sun Microsystems, Inc.
Lines: 18

> This is a real win if you copy library archives around,
> since Berkeley "ld" thinks your new archives are out-of-date
> if you don't run "ranlib" on the newly-created libraries,
> whereas the correct information is embedded in the library
> and follows it around under the System V scheme.

Well, more precisely, the correct information is embedded in the library
and follows it around under both schemes.  However, in the V7 scheme, when
you *modify* the library, you have to regenerate the table of contents,
while in the S5 scheme, the archiver does it for you.  As such, the V7
linker must check to make sure that the modification time of the library
isn't more recent than the modification time of the symbol table;
unfortunately, this breaks things when you copy libraries.  The S5 linker
doesn't need to make this check, and doesn't.
-- 
	Guy Harris
	{ihnp4, decvax, seismo, decwrl, ...}!sun!guy
	guy@sun.com (or guy@sun.arpa)