From:	Rod DOT Bates AT wichita DOT boeing DOT com (Bates, Rod)
Subject:	RE: Undefined link symbols
19 Aug 1998 08:42:39 -0700 :
Message-ID:	<6C7E2A10BB01D111929500400B406DDEE63915.cygnus.gnu-win32@xch-wch-02.ks.boeing.com>
Mime-Version:	1.0
To:	"'gnu-win32 AT cygnus DOT com'" <gnu-win32 AT cygnus DOT com>

Earlier, I wrote: 

> While linking, I get undefined symbols _setjmp, ___infinity,
> ___errno, and sometimes _stderr.   My program is written
> in a mixture of Ada, using the gnat compiler, and Modula-3,
> using the Pm3 compiler.  It compiles, links, and runs fine on
> Linux.  When I go to NT, the link step gives these undefined
> symbols.
> 
> Both these compilers use gcc as the code generator and,
> on NT, cygwin.  Can anybody tell me where these symbols
> should be found, so I can tell my link step where to look?
> 
I have more information.  When I use the gcc that came with
gnat, I get undefined symbols _setjmp, ___errno, and ___infinity,
referenced from within the Modula-3 runtime library.  

When I use the gcc that came with cygwin, I get undefined
symbol _stderr, referenced from within the gnat RTL.  

I have dumped the calls to ld that these two gcc's generate.
They differ in many ways in the -L and -l options supplied
by gcc itself (those supplied explicitly by my build scripts are
the same).  However, If I manually add all the -L and -l 
options to one of the ld commands which were present in
the other, it doesn't help.  

I am now systematically looking for lib*.a files anywhere on
my system and for the missing symbols inside them.  

> Rodney Bates   
> 
> 
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -