Fedora RPM package build failing with RPATH of /usr/local/lib64
Summary
Fedora Linux recently introduced RPATH hardening on RPM generation, and it fails when the RPATH is set to a default of /usr/local/lib64
https://fedoraproject.org/wiki/Changes/Broken_RPATH_will_fail_rpmbuild
https://docs.fedoraproject.org/en-US/packaging-guidelines/#_beware_of_rpath
While /usr/local/lib64
is not considered acceptable, either a directory under there, like /usr/local/lib64/wireshark
or a path that includes $ORIGIN
is considered acceptable. So enabling -DENABLE_RPATH_ORIGIN=ON
in the spec file for Fedora is acceptable, as would be moving the libraries to a subdirectory instead. It is also possible to disable the RPATH checks via several mechanisms described in the links
Steps to reproduce
ninja rpm-package
Also look at the recent CI builds
What is the current bug behavior?
Fails complaining of an invalid RPATH
What is the expected correct behavior?
Package should build
Relevant logs and/or screenshots
*******************************************************************************
*
* WARNING: 'check-rpaths' detected a broken RPATH OR RUNPATH and will cause
* 'rpmbuild' to fail. To ignore these errors, you can set the
* '$QA_RPATHS' environment variable which is a bitmask allowing the
* values below. The current value of QA_RPATHS is 0x0000.
*
* 0x0001 ... standard RPATHs (e.g. /usr/lib); such RPATHs are a minor
* issue but are introducing redundant searchpaths without
* providing a benefit. They can also cause errors in multilib
* environments.
* 0x0002 ... invalid RPATHs; these are RPATHs which are neither absolute
* nor relative filenames and can therefore be a SECURITY risk
* 0x0004 ... insecure RPATHs; these are relative RPATHs which are a
* SECURITY risk
* 0x0008 ... the special '$ORIGIN' RPATHs are appearing after other
* RPATHs; this is just a minor issue but usually unwanted
* 0x0010 ... the RPATH is empty; there is no reason for such RPATHs
* and they cause unneeded work while loading libraries
* 0x0020 ... an RPATH references '..' of an absolute path; this will break
* the functionality when the path before '..' is a symlink
*
*
* Examples:
* - to ignore standard and empty RPATHs, execute 'rpmbuild' like
* $ QA_RPATHS=$(( 0x0001|0x0010 )) rpmbuild my-package.src.rpm
* - to check existing files, set $RPM_BUILD_ROOT and execute check-rpaths like
* $ RPM_BUILD_ROOT=<top-dir> /usr/lib/rpm/check-rpaths
*
*******************************************************************************
ERROR 0002: file '/usr/local/lib64/wireshark/extcap/androiddump' contains an invalid '/usr/local/lib64' in [/usr/local/lib64]
ERROR 0002: file '/usr/local/lib64/wireshark/extcap/sdjournal' contains an invalid '/usr/local/lib64' in [/usr/local/lib64]
ERROR 0002: file '/usr/local/lib64/wireshark/extcap/randpktdump' contains an invalid '/usr/local/lib64' in [/usr/local/lib64]
ERROR 0002: file '/usr/local/lib64/wireshark/extcap/udpdump' contains an invalid '/usr/local/lib64' in [/usr/local/lib64]
ERROR 0002: file '/usr/local/lib64/wireshark/extcap/ciscodump' contains an invalid '/usr/local/lib64' in [/usr/local/lib64]
ERROR 0002: file '/usr/local/lib64/wireshark/extcap/dpauxmon' contains an invalid '/usr/local/lib64' in [/usr/local/lib64]
ERROR 0002: file '/usr/local/lib64/wireshark/extcap/sshdump' contains an invalid '/usr/local/lib64' in [/usr/local/lib64]