The binary or shared library sets RPATH or RUNPATH. This overrides the normal library search path, possibly interfering with local policy and causing problems for multilib, among other issues.
The only time a binary or shared library in a Debian package should
set RPATH or RUNPATH is if it is linked to private shared libraries
in the same package. In that case, place those private shared
/usr/lib/package. Libraries used by
binaries in other packages should be placed in
/usr/lib as appropriate, with a proper SONAME, in which case
RPATH/RUNPATH is unnecessary.
To fix this problem, look for link lines like:
gcc test.o -o test -Wl,--rpath,/usr/local/lib
gcc test.o -o test -R/usr/local/lib
and remove the
-R argument. You can also
use the chrpath utility to remove the RPATH.
For more information please consult:
The tag is present in Lintian version
That is the most recent version we know about.
We use semantic versions.
The patch number is a commit step indicator relative to the
release tag in our Git
You can find the detection logic for this version at commit ffc17eb. For merge requests, please use the latest version in the Lintian check binaries/rpath.