Am Monday 13 March 2006 09:58 schrieb Robert Schiele:
On Mon, Mar 13, 2006 at 09:36:37AM +0100, Adrian Schroeter wrote:
Am Friday 10 March 2006 19:41 schrieb Robert Schiele:
Nah, that is what shared library versioning is for. Putting runtime libraries in an extra directory is only needed if the author of the software did not understand how to do shared library versioning correctly.
so you plan to extend the version by some $gcc3 extension ? But this would break already compiled binaries (esp. binary only apps).
Adrian? What are you talking about?
A gcc-3.3 system has /usr/lib/libstdc++.so.5 and a gcc 4.x system does have /usr/lib/libstdc++.so.6. Where is the conflict? What do you expect to break when you just copy /usr/lib/libstdc++.so.5 to a gcc 4.x system?
We do not speak about the lib from the compiler here, but about independend libs on top of it. You do only get different sonames for libs, if the build system really has code to detect the compiler version, which usually is not the case. So, for instance, a libzypp would keep the same soname, but becomes incompatible due to the two different compilers. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de