-
-
Notifications
You must be signed in to change notification settings - Fork 485
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot force rpath #94
Comments
I just ran into the same issue. The behavior of
But instead, I get this:
The outcome is only predictable after Output generated with this script:
|
This was referenced Oct 20, 2017
sergiusens
added a commit
to sergiusens/snapcraft
that referenced
this issue
Apr 18, 2018
Given NixOS/patchelf#94 we may find ourselves in a situation where given an elf file with an existing RUNPATH, a proper RPATH may not be set. Signed-off-by: Sergio Schvezov <sergio.schvezov@canonical.com>
sergiusens
added a commit
to sergiusens/snapcraft
that referenced
this issue
Apr 18, 2018
Given NixOS/patchelf#94 we may find ourselves in a situation where given an elf file with an existing RUNPATH, a proper RPATH may not be set. Resolve canonical#2071 Signed-off-by: Sergio Schvezov <sergio.schvezov@canonical.com>
6 tasks
sergiusens
added a commit
to canonical/snapcraft
that referenced
this issue
Apr 18, 2018
Given NixOS/patchelf#94 we may find ourselves in a situation where given an elf file with an existing RUNPATH, a proper RPATH may not be set. Resolve #2071 Signed-off-by: Sergio Schvezov <sergio.schvezov@canonical.com>
This was referenced Dec 12, 2018
This was referenced Jun 27, 2019
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm having trouble setting the
RPATH
on a binary when it already has aRUNPATH
, even when the--force-rpath
option is employed. Test case:Displays nothing, as ls by default appears to have no rpath or runpath.
Now it displays
0x000000000000001d (RUNPATH) Library runpath: [/home/mpn/libs]
. OK, fine!Next do:
Expected result: It will display an RPATH for the binary
Actual result: It still displays only a RUNPATH for the binary
My current workaround has been to delete the existing RUNPATH using
chrpath -d
(using --set-rpath "" with patchelf doesn't appear to do it, as that looks rather to set RUNPATH to an empty string instead), and then to use--force-rpath
with patchelf. Force-rpath does appear to work when there is no RUNPATH present.The text was updated successfully, but these errors were encountered: