This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
symbol versioning
- From: Phil Edwards <phil at jaj dot com>
- To: libstdc++ at gcc dot gnu dot org
- Date: Fri, 8 Feb 2002 15:55:22 -0500
- Subject: symbol versioning
sleep-deprived blathering alert
I have some initial hacks at symbol versioning. This has been something
I've been thinking about for a long time, and Stan's question yesterday
pushed it to the foreground of my brain. The good news is that getting
the .so to be versioned is easy. Bad news is hunting down all the symbols
we need to export is going to be a pain, unless I'm overlooking something,
which is certainly possible because I'm way too tired to be hacking anything
ELF-related right now...
(How do I tell which symbols in a .so have what version? I'm used to 'nm'
showing symbols with @FOO_X.Y appended, but I'm not seeing that with the
new version strings I've chosen.)
Parts of the testsuite work. Then something will die with 'relocation error:
program.exe: symbol _Z_argleblarglemangle, version FOO_X.Y not defined in
file libstdc++.so.4 with link time reference' which doesn't particularly
mean anything to me since I've not seen that message before. The 'with
link time reference' is a bit disturbing; presumably this is something
more evil than "undefined symbol". So I go back and export more symbols,
and sometimes it helps, sometime it doesn't.
It's definitely an educational break from writing doxygen comments. :-)
Phil