-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Set an RPATH on all libraries requiring fortran in binary-dist #17901
Conversation
cd $private_libdir | ||
for file in openlibm quadmath gfortran openblas arpack lapack openspecfun; do | ||
for dylib in $(ls lib$file*.so* 2>/dev/null); do | ||
patchelf --set-rpath \$ORIGIN $dylib |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we have the PATCHELF
exported in a way that would propagate? someone might have it somewhere else, but I guess that's a second-order concern here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, we build patchelf ourself and call it $(PATCHELF)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That variable is only set in deps/, if you feel like rearranging things and threading it through, be my guest, but this code catches patchelf globally or in usr/tools, so I don't really see the need to do the extra work to make it work with an override PATCHELF
.
This should help, thanks |
Somebody could override it, I suppose, but would such a somebody be making binary-dists, who knows. I don't think I particularly care. |
(cherry picked from commit 8615732)
@tkelman see if this is what you had in mind