On 28/05/2017 23:31, Salz, Rich via openssl-users wrote:
The openssl program will use the wrong libssl.so and libcrypto.so.
Yes, got it.
But that's small potatoes compared to everyone else finding the wrong shared library, and just saying "use rpath" doesn't help all those others.
Change the /usr/lib/libssl.so symlink to point to libssl.so.1.1,
not libssl.so.1.0 while compiling with OpenSSL 1.1.x headers.
Ditto for libcrypto.so.
Alternatively, place such symlinks in the lib directory that is
next to the include directory with OpenSSL 1.1.x headers.
This should cause the resulting programs to refer to the right
so-name (libssl.so.1.1 etc.) and thus either load the right
library generation (1.1.x) or report that it isn't installed on
the local library path (typically, /lib/, /usr/lib/ and
/usr/local/lib/ in some system dependent order).
After all, this is the whole point of the versioned .so file names.
Enjoy
Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S. https://www.wisemo.com
Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
