[scl.org] SCL packages and linker paths

Noah Kantrowitz noah at coderanger.net
Mon Jul 27 00:11:45 UTC 2015


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.

--Noah

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://listman.redhat.com/archives/sclorg/attachments/20150726/8b8a88f2/attachment.sig>


More information about the SCLorg mailing list