This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
gcc 4.4 and alternative so name
- From: ghibo at mandriva dot com
- To: libstdc++ at gcc dot gnu dot org
- Date: Sat, 23 May 2009 11:34:25 +0200 (CEST)
- Subject: gcc 4.4 and alternative so name
Hi. I'm trying to build a package for gcc 4.4, as "alternative" compiler
to the system-wide one. While for the gcc frontend this lead to have
command named like gcc<versioning> (e.g. gcc4.4, g++4.4, and so on) and
it's pretty easy to achieve, the libstdc++ built has soname
libstdc++.so.6.0.11 with a soft link to libstdc++.so.6. Unfortunately the
major version "6" is also the same as of the system wide one (which is
libstdc++.so.6.0.10, but might be older) and thus both libraries can't
coexists in the same path (e.g. /usr/lib or /usr/lib64). So I was
wondering if there is some configure option (or some small patch) to have
the libstdc++ built under another soname, which might be
libstdc++-6.0.11.so.0 or libstdc++-gcc44.so.6.0.11, etc.), so that any
program built with g++4.4 will be automatically linked to that library
instead of the system-wide one and existing programs won't have changed
the dynamic library they are linked to.
Thanks in advance
Regards.
Giuseppe GhibÃ