Xref: utzoo comp.unix.questions:15426 comp.bugs.sys5:1068
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!iuvax!cica!gatech!bbn!bbn.com!rsalz
From: rsalz@bbn.com (Rich Salz)
Newsgroups: comp.unix.questions,comp.bugs.sys5
Subject: Re: ranlib
Message-ID: <1922@prune.bbn.com>
Date: 4 Aug 89 14:46:03 GMT
References: <457@mccc.UUCP> <10659@smoke.BRL.MIL> <1920@prune.bbn.com> <10663@smoke.BRL.MIL>
Organization: BBN Systems and Technologies Corporation
Lines: 22

In article <1920@prune.bbn.com> I wrote that the builtin table of contents
(TOC) stuff makes building large libraries take too long.

In <10663@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn) writes:
>Doesn't the "q" option do that?  Seems like it should.

I'm not sure, but it seems that "q" just zaps the module at the end of the
file, but still rebuilds the TOC anyway.  Even if it works/worked right,
however, it still doesn't solve my problem.

I've got a big library (400 files in 20 directories) and I'm going to be
replacing about 20 modules (scattered over, say, 10 directories) in that
library.  About a half-hour of time is WASTED as "ar" creates a TOC 10
times.

It would be much more effective if I could NOT build the TOC until the
end.   I used to agree that having ranlib as a separate command was a real
crock, but then I had to use the SysV-oid version of ar...
	/r$
-- 
Please send comp.sources.unix-related mail to rsalz@uunet.uu.net.
Use a domain-based address or give alternate paths, or you may lose out.