Date: Sun, 26 Apr 1998 11:54:59 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Nate Eldredge <nate AT cartsys DOT com>
cc: Charles Terry <cterry AT plinet DOT com>, djgpp AT delorie DOT com
Subject: Re: Unresolved externals
In-Reply-To: <19980424035042.AAJ8293@ppp125.cartsys.com>
Message-ID: <Pine.SUN.3.91.980426115435.19566G-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Thu, 23 Apr 1998, Nate Eldredge wrote:

> >Did anybody actually try this?  I think that if the linker reports 
> >unresolved externals, it leaves them zeroed.  So, if the execution 
> >thread never gets there, the program will run just fine (if it does get 
> >there, it will crash).
> 
> I may be confused here. Are we talking about DJGPP's stock `ld'?

Yes, I was talking about stock `ld'.

> For me
> (Binutils 2.7), if the linker reports an unresolved external when creating
> an executable, it halts the linking and does not actually create the
> executable. I browsed the docs and did not see any option to make it a
> warning instead and continue the link.

If the excutable is not created, obviously it cannot be run.  But if
there's a way to force `ld' create it anyway (like `ld' from RSXNT
does), then I think it could be run provided the execution never gets
to the unresolved externals.