-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
openssl: libs don't contain an RPATH value #1
Comments
Why should OpenSSL libs have a RPATH value? |
Found some references here : http://en.wikipedia.org/wiki/Rpath An interesting part is |
If you use -z nodeflib, you'll lose libc.so, with is quite useful IMHO. OpenSSL shall have the path to the libraries it uses: If any of its dependency is not satisfied by the executable, it has to load it by itself. In that particular case, it doesn't do any harm at the end, as there is not dependency outside of the standard path. Let's close it. |
Using readelf on the shared library provided by OpenSSL, no RPATH value is shown. This will lead to some wrong dependencies (using libs in /lib and /usr/lib in place of the intended ones).
The text was updated successfully, but these errors were encountered: