From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: help - collect2.exe not linking element from a library
Date: 25 Mar 2001 16:12:19 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 14
Message-ID: <99l5d3$fjr$1@nets3.rz.RWTH-Aachen.DE>
References: <3ABA3BD8 DOT 9ECC1B29 AT nowhere DOT com> <9003-Fri23Mar2001130041+0200-eliz AT is DOT elta DOT co DOT il>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 985536739 15995 137.226.32.75 (25 Mar 2001 16:12:19 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 25 Mar 2001 16:12:19 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> 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.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.