@adriansev @agoose77 Circling back to this very late, I think I have the start of an idea of the problem: The RPATH (CentOS) or RUNPATH (Debian) needs to be different if the installation is an egg or a wheel for things to work. This is because the RPATH/RUNPATH needs to take us from the library .so to the dependency library .sos.

Wheel

If you have a wheel then from your site-packages you'll have a nice layout something like

[root@e2b96418e2e5 site-packages]# tree -L 1 | grep -i "xrootd"
|-- XRootD
|-- pyxrootd
`-- xrootd-5.4.2-py3.6.egg-info
[root@e2b96418e2e5 site-packages]# tree -L 1 pyxrootd/
pyxrootd/
|-- __init__.py
|-- __pycache__
|-- client.cpython-36m-x86_64-linux-gnu.so
|-- include
|-- lib64
`-- share

4 directories, 2 files

and the important thing is that the client .so has a RPATH/RUNPATH that points to $ORIGIN/lib64 ($ORIGIN/lib on Debian)

[root@e2b96418e2e5 site-packages]# cd pyxrootd/
[root@e2b96418e2e5 pyxrootd]# objdump -x client.cpython-36m-x86_64-linux-gnu.so | grep PATH
  RPATH                $ORIGIN/lib64      
[root@e2b96418e2e5 pyxrootd]# ls -l lib64/libXrdCl.so.3
lrwxrwxrwx 1 root root 17 Apr  5 23:09 lib64/libXrdCl.so.3 -> libXrdCl.so.3.0.0
[root@e2b96418e2e5 site-packages]# cd 
[root@e2b96418e2e5 ~]# python3 -c 'from XRootD import client; print(client.FileSystem("root://someserver:1094"))'
<XRootD.client.filesystem.FileSystem object at 0x7fd541df7f98>

egg

However, if you have an egg, then the layout changes and from your site-packages you'll have something like

(venv) root@34321f613143:/code/venv/lib/python3.9/site-packages# tree -L 1 | grep -i "xrootd"
|-- pyxrootd
`-- xrootd-2022.415-py3.9-linux-x86_64.egg
(venv) root@34321f613143:/code/venv/lib/python3.9/site-packages# tree -L 2 xrootd-2022.415-py3.9-linux-x86_64.egg/
xrootd-2022.415-py3.9-linux-x86_64.egg/
|-- EGG-INFO
|   |-- PKG-INFO
|   |-- SOURCES.txt
|   |-- dependency_links.txt
|   |-- native_libs.txt
|   |-- not-zip-safe
|   `-- top_level.txt
|-- XRootD
|   |-- __init__.py
|   |-- __pycache__
|   `-- client
`-- pyxrootd
    |-- __init__.py
    |-- __pycache__
    |-- client.cpython-39-x86_64-linux-gnu.so
    `-- client.py

6 directories, 10 files

and now the client .so has a RPATH/RUNPATH that points to $ORIGIN/../../pyxrootd/lib64 ($ORIGIN/../../pyxrootd/lib on Debian)

(venv) root@34321f613143:/code/venv/lib/python3.9/site-packages# cd xrootd-2022.415-py3.9-linux-x86_64.egg/pyxrootd/
(venv) root@34321f613143:/code/venv/lib/python3.9/site-packages/xrootd-2022.415-py3.9-linux-x86_64.egg/pyxrootd# objdump -x client.cpython-39-x86_64-linux-gnu.so | grep PATH
  RUNPATH              $ORIGIN/../../pyxrootd/lib
(venv) root@34321f613143:/code/venv/lib/python3.9/site-packages/xrootd-2022.415-py3.9-linux-x86_64.egg/pyxrootd# ls -l ../../pyxrootd/lib/libXrdCl.so.3
lrwxrwxrwx 1 root root 17 Apr 15 06:44 ../../pyxrootd/lib/libXrdCl.so.3 -> libXrdCl.so.3.0.0
(venv) root@34321f613143:/code/venv/lib/python3.9/site-packages/xrootd-2022.415-py3.9-linux-x86_64.egg/pyxrootd# cd
(venv) root@34321f613143:~# python3 -c 'from XRootD import client; print(client.FileSystem("root://someserver:1094"))'
<XRootD.client.filesystem.FileSystem object at 0x7f5105ee12b0>

This works without any LD_LIBRARY_PATH manipulation as RPATH/RUNPATH are actually being set correctly!

Next question towards solution

needs to be more robust and be able to determine what the layout will be and set the XRDCL_RPATH accordingly if PYPI_BUILD:

Question after all of this is fixed

Summary

I don't have a working fix yet, but I think this is actually understandable now. 👍

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.