Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
From: Nate Eldredge <nate AT cartsys DOT com>
Subject: Re: Unresolved externals
Cc: Charles Terry <cterry AT plinet DOT com>, djgpp AT delorie DOT com
Date: Thu, 23 Apr 1998 20:51:05 -0700
Message-ID: <19980424035042.AAJ8293@ppp125.cartsys.com>
Precedence: bulk

At 01:44  4/21/1998 +0300, Eli Zaretskii wrote:
>
>On Mon, 20 Apr 1998, Nate Eldredge wrote:
>
>> At 08:21  4/19/1998 -0700, Charles Terry wrote:
>> 
>> >BTW I don't think I could run the program as the linker 
>> >reported the unresolve linkage as an error, not a warning.
>> >Is that right?
>> 
>> Yes, that's right
>
>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'? 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.

Of course, if you link with `-r', it won't even report them, since it's not
a problem.

Nate Eldredge
nate AT cartsys DOT com