On Sun, May 28, 2017 at 5:25 PM, Salz, Rich <rsalz@xxxxxxxxxx> wrote: >> We still don't know what use case is being represented by omitting the >> RPATH in the OpenSSL build. > > Because only one program, apps/openssl, presumably needs rpath. But that doesn't solve the problem for *external applications* that need to find OpenSSL in a different place, does it? > Without RPATH's (or some other mechanism, like making openssl a script that sets LD_LIBRARY_PATH), libssl.so will use the wrong libcrypto.so. The openssl program will use the wrong libssl.so and libcrypto.so. Jeff -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
