Re: Comments on new gcc-nocygwin-tools.jam?

From: Raoul Gough (raoulgough_at_[hidden])
Date: 2003-01-22 14:44:00

"Raoul Gough" <raoulgough_at_[hidden]> wrote in message
news:002b01c2c221$1dfe4e70$0100a8c0_at_albert...
[snip]
> I'm a bit concerned about the build problems with the new
gcc-nocygwin
> toolset (the ones that don't arise on your system). I've fixed the
> problems on my system, but I can't understand why it worked for you
> without the fixes. If you can spare a couple of minutes for this, it
> would be good to confirm the following points on your system:
>
> 1. Is the toolset really building cygwin-independant code?
> 2. Is it doing so with the cygwin compiler?

William Kempf sent me some more details from his build, which *is*
working as it should be. After some further investigation on my
system, it turns out that my ld was out of date and using a newer
version fixes the problem. The old version was:

$ ld --version
GNU ld version 2.11.92 20011001

More recent versions have code to filter out the symbols from certain
objects and libraries when doing an export-all-symbols, including
crt2.o and dllcrt2.o, where the multiple definition errors were coming
from (atexit and _onexit). The relevant change was probably this one
(from the ld ChangeLog):

2001-10-11 Danny Smith <danny_r_smith_2001_at_[hidden]>

* pe-dll.c (autofilter_entry_type autofilter_liblist: Add
startup files for mingw32 dlls to list.

So I guess any ld built with sources newer than 2001-10-11 should be
OK, even with the --export-all-symbols flag.

Regards,
Raoul Gough.

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com