[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [scl.org] SCL packages and linker paths



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Le 27/07/2015 02:11, Noah Kantrowitz a écrit :
> Hi there. I'm working on some Chef tooling for Python and Ruby to
> allow swapping runtimes in a modular way. The easiest way to do
> this is to pass through different paths to a Python binary. For
> system packages, it uses /usr/bin/python while for SCL it uses
> /opt/rh/<something/root/usr/bin/python. This means not using the
> `scl enable` command though, which presents a problem. Most of the
> environment variables set in the enable files are nice but not
> required, but LD_LIBRARY_PATH presents an issue. Because the SCL
> binaries do not have an RPATH in their header, they simply fail to
> start in most cases, or locate the wrong libraries if there is
> overlap with system packages. Is there a compelling reason to not
> bake this RPATH into the SCL binaries directly? This would make it
> much easier to build tooling that treats the Python and Ruby
> packages as just another way to install things.

This is what the PHP build system doest for years.

Not use in PHP RHSCL because everything is in base system.
But various package in the php5xmore collection rely on this behavior.


Remi.

> --Noah
> 
> 
> 
> _______________________________________________ SCLorg mailing
> list SCLorg redhat com 
> https://www.redhat.com/mailman/listinfo/sclorg
> 


- -- 
rcollet redhat com | Senior Software Engineer / BaseOS / WebStack team
GPG Key: 0x29F16A18
Fingerprint: 5A0E 6F54 D94D 5732 69EE  E3FF 614A 6905 29F1 6A18
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlW3eRkACgkQYUppBSnxahhwkQCeMNxRtzLMQIJq7Sz0PPrx+xzD
YBgAoOYjeBb3l5m1Wea7Acyblb3peObs
=qT1k
-----END PGP SIGNATURE-----


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]