Date: Sun, 25 Mar 2001 20:29:23 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: Hans-Bernhard Broeker Message-Id: <7263-Sun25Mar2001202922+0200-eliz@is.elta.co.il> X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.6 CC: djgpp AT delorie DOT com In-reply-to: <99l5d3$fjr$1@nets3.rz.RWTH-Aachen.DE> (message from Hans-Bernhard Broeker on 25 Mar 2001 16:12:19 GMT) Subject: Re: help - collect2.exe not linking element from a library References: <3ABA3BD8 DOT 9ECC1B29 AT nowhere DOT com> <9003-Fri23Mar2001130041+0200-eliz AT is DOT elta DOT co DOT il> <99l5d3$fjr$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > From: Hans-Bernhard Broeker > Newsgroups: comp.os.msdos.djgpp > Date: 25 Mar 2001 16:12:19 GMT > > Eli Zaretskii wrote: > [...] > > You forgot that ld.exe is a one-pass linker: it only scans the > > libraries once, in the order you specify them in the link command > > line. > > Hmmm... but isn't this true only for those libraries you specify with > -l arguments? Libs given by actual filename (like the OP's > c:/.../libmwin.a) are treated like .o files, and those are not subject > to one-pass-only treatment, AFAIK. Are you saying that if I use libc.a instead of -lc, the linker pulls the _entire_ library into the executable? That would be the only way it could work around its one-pass nature. I doubt that the linker does that, though.