Print

Print


> setting `LD_LIBRARY_PATH` is a workaround in my opinion. The shared library (client) has `RPATH` / `RUNPATH` set to find the dependency libraries, but for some reason the install layout isn't correct on Debian / Fedora (at least, not for the matrix that I tried): the `RUNPATH` is being set, but it points to a non-existent directory. Specifically, the `pyxrootd` client lib is installed into the `.egg-info` directory instead of the `pyxrootd` directory in `site-packages`. This looks like a bug rather than a deliberate layout decision, although I'm not familiar with the platform nuances here to know for certain!

Agreed — definitely a "get things working now" approach (though I've become far too used to having to update `LD_LIBRARY_PATH` for working with Debian packages in general, so this is sadly not rare). Once it is understood what it _should_ be and what it is _now_ I would recommend opening up a new Issue that documents all of this clearly and asks an XRootD maintainer to fix it. :+1: 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/xrootd/xrootd/issues/1668#issuecomment-1088955533
You are receiving this because you are subscribed to this thread.

Message ID: <[log in to unmask]>

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1