On Tue, Apr 7, 2015 at 10:13 PM, <h15...@mailas.com> wrote:
> On Tue, Apr 7, 2015, at 07:06 PM, Jeffrey Walton wrote:
>> > Setting *FLAGS & rpath, although the openssl binary links correctly
>> > against its own {libcrypto,libssl}.so, the libssl.so links against
>> > *system*,
>> > not its own, libcrypto.
>>
>> You can verify the RPATHs are actually present by dumping the
>> DT_RUNPATH section of the ELF executable:
>>
>> readelf -d <file> | grep -i RPATH
>
> Here
>
> 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.
>> "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.
Jeff
_______________________________________________
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
