-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 (cross-posting to opensuse-packaging as the topic is on purpose) Robert Schiele wrote: ...
So building yourself is the way to go if you don't want to fix the code. Alternatively unpacking a binary package from an older release should do as well.
Apart from that, I'd be willing to provide gcc3 packages for SUSE Linux
in my repository (for C and C++) but... what would be the best place for
it, how to best handle those compat library packages (i.e. where to put
them to avoid conflicts) ?
Does anyone have some hints ?
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
On Fri, Mar 10, 2006 at 11:17:53AM +0100, Pascal Bleser wrote:
Apart from that, I'd be willing to provide gcc3 packages for SUSE Linux in my repository (for C and C++) but... what would be the best place for it, how to best handle those compat library packages (i.e. where to put them to avoid conflicts) ?
Does anyone have some hints ?
Any special directory will do. /opt/gcc33 (or whatever version you want to provide) would be appropriate. Robert -- Robert Schiele Tel.: +49-621-181-2214 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de "Quidquid latine dictum sit, altum sonatur."
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Robert Schiele wrote:
On Fri, Mar 10, 2006 at 11:17:53AM +0100, Pascal Bleser wrote:
Apart from that, I'd be willing to provide gcc3 packages for SUSE Linux in my repository (for C and C++) but... what would be the best place for it, how to best handle those compat library packages (i.e. where to put them to avoid conflicts) ?
Does anyone have some hints ?
Any special directory will do. /opt/gcc33 (or whatever version you want to provide) would be appropriate.
Yes, sure ;)
I meant to for the compat runtime libraries.
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
On Fri, Mar 10, 2006 at 11:36:38AM +0100, Pascal Bleser wrote:
I meant to for the compat runtime libraries.
No nead to package them again. They are already in compat-libstdc++. Robert -- Robert Schiele Tel.: +49-621-181-2214 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de "Quidquid latine dictum sit, altum sonatur."
Am Friday 10 March 2006 11:36 schrieb Pascal Bleser:
Robert Schiele wrote:
On Fri, Mar 10, 2006 at 11:17:53AM +0100, Pascal Bleser wrote:
Apart from that, I'd be willing to provide gcc3 packages for SUSE Linux in my repository (for C and C++) but... what would be the best place for it, how to best handle those compat library packages (i.e. where to put them to avoid conflicts) ?
Does anyone have some hints ?
Any special directory will do. /opt/gcc33 (or whatever version you want to provide) would be appropriate.
Yes, sure ;) I meant to for the compat runtime libraries.
the should be under the same prefix IMHO. The should not be in some standard lib path to avoid clashes with existing gcc4 build libs. This means also that apps using these libs need either to use rpath linker option or the LD_LIBRARY_PATH enviroment variable in some start script. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Adrian Schröter wrote:
Am Friday 10 March 2006 11:36 schrieb Pascal Bleser:
Robert Schiele wrote:
On Fri, Mar 10, 2006 at 11:17:53AM +0100, Pascal Bleser wrote:
Apart from that, I'd be willing to provide gcc3 packages for SUSE Linux in my repository (for C and C++) but... what would be the best place for it, how to best handle those compat library packages (i.e. where to put them to avoid conflicts) ?
Does anyone have some hints ? Any special directory will do. /opt/gcc33 (or whatever version you want to provide) would be appropriate. Yes, sure ;) I meant to for the compat runtime libraries.
the should be under the same prefix IMHO. The should not be in some standard lib path to avoid clashes with existing gcc4 build libs. This means also that apps using these libs need either to use rpath linker option or the LD_LIBRARY_PATH enviroment variable in some start script.
Yes, that would obviously be the most straightforward option.
I'll nevertheless have a look at the gcc-old and compat-libstdc++ packages.
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
On Fri, Mar 10, 2006 at 03:33:05PM +0100, Adrian Schroeter wrote:
the should be under the same prefix IMHO. The should not be in some standard lib path to avoid clashes with existing gcc4 build libs. This means also that
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. Robert -- Robert Schiele Tel.: +49-621-181-2214 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de "Quidquid latine dictum sit, altum sonatur."
Am Friday 10 March 2006 19:41 schrieb Robert Schiele:
On Fri, Mar 10, 2006 at 03:33:05PM +0100, Adrian Schroeter wrote:
the should be under the same prefix IMHO. The should not be in some standard lib path to avoid clashes with existing gcc4 build libs. This means also that
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 Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de
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? Robert -- Robert Schiele Tel.: +49-621-181-2214 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de "Quidquid latine dictum sit, altum sonatur."
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
On Mon, Mar 13, 2006 at 11:26:38AM +0100, Adrian Schroeter wrote:
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
Ah, ok. Then we were really talking about different things here. Robert -- Robert Schiele Tel.: +49-621-181-2214 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de "Quidquid latine dictum sit, altum sonatur."
participants (3)
-
Adrian Schröter -
Pascal Bleser -
Robert Schiele