This is the mail archive of the
mailing list for the binutils project.
Re: mipsel-linux and --export-dynamic
- From: Thomas Lopatic <thomas at lopatic dot de>
- To: Ian Lance Taylor <ian at wasabisystems dot com>
- Cc: Thomas Lopatic <thomas at lopatic dot de>, binutils at sources dot redhat dot com
- Date: Thu, 04 Nov 2004 17:00:53 +0100
- Subject: Re: mipsel-linux and --export-dynamic
- References: <418A17A6.firstname.lastname@example.org> <email@example.com>
Thanks a lot for shedding some light on this!
I was just a bit confused because the native Linux linker on my system
by default only puts the unresolved (imported) symbols, e.g. _printf,
into the dynamic symbol table. I expected the MIPS cross-linker to
behave in the same way. So, I thought that this was - quite obviously
:-) - a quirk.
I cannot verify this right now, but it may very well be the case that
not all symbols got exported. I just noticed that a lot of the
externally visible symbols were in the dynamic symbol table. And I
concluded that the linker was behaving as if "--export-dynamic" had been
specified. (I used "ld" directly, not via the GCC driver.)
I've had a look at the documentation for version scripts and for the
visibility attribute and for me version scripts will be the way to go in
Quite impressive what you can do with "ld".