Mailinglist Archive: opensuse-packaging (60 mails)
| < Previous | Next > |
Re: [opensuse-packaging] Re: [opensuse-factory] Re: gcc 3.x compatibility package
- From: Pascal Bleser <pascal.bleser@xxxxxxxxx>
- Date: Fri, 10 Mar 2006 16:26:21 +0100
- Message-id: <44119A9D.9050702@xxxxxxxxx>
-----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/
/\\ <pascal.bleser@xxxxxxxxx> <guru@xxxxxxxxxxx>
_\_v The more things change, the more they stay insane.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFEEZqdr3NMWliFcXcRAhMCAJ0eEcaE37E1NJ2LFiKrWaYbGVz7TgCgiGe7
3LV/a1k6j4IMzNy8NOoHE0I=
=S4oM
-----END PGP SIGNATURE-----
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/
/\\ <pascal.bleser@xxxxxxxxx> <guru@xxxxxxxxxxx>
_\_v The more things change, the more they stay insane.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFEEZqdr3NMWliFcXcRAhMCAJ0eEcaE37E1NJ2LFiKrWaYbGVz7TgCgiGe7
3LV/a1k6j4IMzNy8NOoHE0I=
=S4oM
-----END PGP SIGNATURE-----
| < Previous | Next > |