This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: what can link.exe do that cygwin32-ld can't ?
- To: Ulrich dot Lauther at mchp dot siemens dot de
- Subject: Re: what can link.exe do that cygwin32-ld can't ?
- From: ian at cygnus dot com
- Date: Fri, 4 Jul 1997 00:34:11 -0400 (EDT)
- CC: gnu-win32 at cygnus dot com
- Newsgroups: cygnus.gnu-win32
- References: <199707031315.PAA22297.cygnus.gnu-win32@fubini.mchp.siemens.de>
In cygnus.gnu-win32 you write:
>In the FAQ, under the heading
>"Can I mix objects compiled with msvc++ and gcc? "
>it is said: "The key seems to be using MS's LINK.EXE
>to do the linking instead of GNU ld."
>Could somebody enlighten me why that is the case? It prevents me from using a cross
>compiler/linker.
It's because the implementation of the PE format in the b18 release is
incorrect. PE appears to be like COFF, but, unfortunately, differs in
a key respect: in PE, symbol values are section relative, whereas in
COFF, symbol values are absolute addresses.
I've corrected this in the development sources; they now generate
correct PE files. Unfortunately, this means that in the next cygwin
release, everybody will have to rebuild their .o and .a files.
Ian
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".