Currently many packages are building with RPATHing the libraries due to
packages using libtool having an incorrect ld detection (cause proper detection
was broken on other distros). The introduction of LT_SYS_LIBRARY_PATH
overrides the detection to ensure it doesn't add RPATH for /usr/lib64
thinking it won't be found. The norm appears to be searching for directories
in /etc/ld.so.conf which doesn't exist in Solus.
The second tool to combat RPATH issues is adding the runpath optimize key.
--enable-new-dtags changes linking to use DT_RUNPATH instead of DT_RPATH,
the difference being that RUNPATH dirs are searched after the default
library locations. This will alleviate issues where RPATH is difficult to
remove and not break expected library loading order.
Currently many packages are building with RPATHing the libraries due to packages using libtool having an incorrect ld detection (cause proper detection was broken on other distros). The introduction of
LT_SYS_LIBRARY_PATHoverrides the detection to ensure it doesn't add RPATH for/usr/lib64thinking it won't be found. The norm appears to be searching for directories in/etc/ld.so.confwhich doesn't exist in Solus.The second tool to combat RPATH issues is adding the
runpathoptimize key.--enable-new-dtagschanges linking to useDT_RUNPATHinstead ofDT_RPATH, the difference being thatRUNPATHdirs are searched after the default library locations. This will alleviate issues whereRPATHis difficult to remove and not break expected library loading order.Signed-off-by: Peter O'Connor peter@solus-project.com