Jivin Mike Frysinger lays it down ...
> the default elf2flt linker script atm outputs __{C,D}TOR_{LIST,END}__
> unconditionally. this can conflict with the symbols already provided
> by gcc's crt{begin,end} objects. so how best to handle this ? are
> these symbols really needed anymore ? or are they for ports whose gcc
> doesnt provide these symbols but install relies on the C library to do
> the processing or something ?
On the older toolchains it used to get it wrong all the time, so we
would pull the support from the toolchain and do it in the linker
script. The ifo pages for ld actually show hwo to do this, don't know
why they changed their minds ;-)
> should i add another configure option to disable all these things ?
> or just delete them permanently ? or have it handled like SINGLE_LINK
> ?
There has always been a problem with clashes in this space.
The elf2flt.ld script does it correctly for elf2flt purposes.
Erwin (a long time ago) proposed having ld-elf2flt either strip the
appropriate clashing crt*.o files from the link or fail if they exist.
Two choices I guess:
drop support for vintage compilers and remove the CTOR/DTOR support
from the script.
or
detect the clash to have a config option to disable it in some way
that cab be made to work with both.
Thoughts ?
Cheers,
Davidm
--
David McCullough, [EMAIL PROTECTED], Ph:+61 734352815
Secure Computing - SnapGear http://www.uCdot.org http://www.snapgear.com
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
