Michael Matz wrote:
> Yes, this is a problem of libtool on linux, in that on that platform
> -export-symbols is implemented not with a linker script (as on
> e.g. Solaris), but instead with the GNU linkers --retain-symbols-file
> option, which does only limit the normal, but not the dynamic symbols
> (which I would consider a bug in ld).
>
> On KDE we have a similar problem. I guess, you would need libtool option
> to directly pass a option to the linker (it's -Wl,... or -Xlinker
> ... IIRC).
<SNIP>
> You could also implement the current Solaris behaviour on Linux. You would
> have to change the definition of $archive_expsym_cmds in ltcf-cxx.sh (in
> case you use the multi-language branch of libtool).
What is the 'right' way to fix this?
It seems like both ld and libtool need fixing. Libtool should
understand that the current version of GNU ld has this bug (I agree it
is a bug). In addition to fixing libtool to accommodate the current
version of GNU ld should work correctly.
Does anyone know if work has been done on either of these fronts? I
don't want to duplicate anyone else's effort.
I would assume that changing libtool should be a _LOT_ easier. I'm
going to look into that today.
I don't want to have to ship a libtool or ld patch with my project.
What is the release cycle like on libtool and ld? What are the chances
of getting a patch into the next release of either?
-Allen
