Re: Proposal to fail builds if RPATH is found in Fedora 35
Kalev Lember wrote:
I don't think there is anything wrong with having rpath to a
private
directory (/usr/lib64/samba) -- that's exactly what rpath is for, so that
the app could find its private libraries that we don't want the whole
world to have access to. What we should avoid is rpath to standard libdir,
which is /usr/lib or /usr/lib64.
+1
And the reason for that is that having RPATH to a standard libdir breaks
overrides through ld.so.conf.d or LD_LIBRARY_PATH. E.g., the -freeworld
library packages in RPM Fusion (e.g., qt5-qtwebengine-freeworld) (which use
ld.so.conf.d) will NOT work with packages that have RPATH set to the
directory containing the Fedora build of the library.
Kevin Kofler