Repository navigation
Running Python from the build directory can lead to wrong libpython being loaded #128469
Description
Feature or enhancement
Proposal:
Right now, since we don't set RPATH, when using a shared libpython and running Python from the build directory, the library might resolve to the system, instead of the local one.
If possible, it would be good to set RPATH on the Python binary in the build directory, to force the local libpython library to be loaded. It would also be preferred to use RPATH instead of RUNPATH, as the prior has precedence over LD_LIBRARY_PATH, which users might have set.
Has this already been discussed elsewhere?
No response given
Links to previous discussion of this feature:
No response
Activity
pythonGH-128469: set RPATH on the builddir Python executable
[-]Set `RPATH` on the builddir Python executable[/-][+]Running Python from the build directory can lead to wrong `libpython` being loaded[/+]pythonGH-128469: warn when libpython was loaded from outside the buil…
Merge branch 'main' into pythongh-128469-warning
GH-128469: warn when libpython was loaded from outside the build dire…
encukou commentedon Jan 30, 2025
The new test fails on some buildbots, for example here: https://buildbot.python.org/#/builders/543/builds/7232/steps/7/logs/stdio
Can you fix it today, or should we revert it for now?
FFY00 commentedon Jan 30, 2025
Yes, I will look at it in a bit.
Revert "pythonGH-128469: warn when libpython was loaded from outside …
GH-128469: Revert "warn when libpython was loaded from outside the bu…
pythonGH-128469: warn when libpython was loaded from outside the buil…
pythonGH-128469: Revert "warn when libpython was loaded from outside …