[openssl-users] openssl 1.0.2 shared build's linking is not consistent - bin and libs linked to different libcrypto.so's
h15234 at mailas.com
h15234 at mailas.com
Wed Apr 8 02:31:04 UTC 2015
Hi
> > readelf -d `which openssl` | egrep -i "rpath|ssl|crypto"
> > 0x0000000000000001 (NEEDED) Shared library: [libssl.so.1.0.0]
> > 0x0000000000000001 (NEEDED) Shared library: [libcrypto.so.1.0.0]
> > 0x000000000000001d (RUNPATH) Library runpath: [/usr/local/ssl/lib64]
>
> I believe this is different than "/usr/local/sslTEST/bin/openssl" and
> friends. It looks like the one you found in in /usr/local/ssl/bin, and
> not /usr/local/sslTEST/bin.
Yep. But it's correct and relevant. Now.
I've switched to /usr/local/ssl. /usr/local/sslTEST -- which I used in earlier tests -- no longer exists,
> >> "Your executable is probably missing it"
> > ... from where? How/where else to specify?
>
> My bad. I was not aware you were talking about the openssl program
> itself. I thought you were discussing arbitrary executables you were
> building.
Nah. Specifically a problem with just openssl. Everything ELSE I build has no such problems. Set rpath as above, and libs are linked peristently as I intend.
Hanlon
More information about the openssl-users
mailing list