On Sat, May 20, 2017 at 7:10 AM, Hiran Chaudhuri <hiran.chaudhuri@xxxxxxx> wrote: > Am 19-May-2017 00:36:18 +0200 schrieb openssl-users@xxxxxxxxxxxx: > >> hiran.chaudhuri> Now this is interesting. Yes, openssl can find both the >> libraries >> hiran.chaudhuri> libssl and libcrypto. Would that imply that rpath is only >> a setting >> hiran.chaudhuri> for application (executables) but not for shared >> libraries? >> hiran.chaudhuri> In that case the test I tried would be totally >> meaningless. >> >> Yes, that's correct. > > NO, it is not correct, shared libraries also have rpaths for their > own dependencies. And when building OpenSSL for installation in > non-default locations (not /usr/lib and the like) the libraries > should have an rpath. > > It would sound logical. But how could I then enforce the runpath to be set > in the libraries? https://wiki.openssl.org/index.php/Compilation_and_Installation#Using_RPATHs. I've never understood the use case - build a new/updated openssl, compile time link against the new one, and then runtime link against the old one. Jeff -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
