You need to run "ldd -v" on your executable to check why your binary has
dependency on libptcorsdk.so.2, and then check your linking command if
the dependency could be removed.
A workaround you could give a try is to set LD_PRELOAD to forcibly load
libssl before libptcoresdk if the dependency on libptcorsdk could not be
removed.
Wayming
On 02/10/15 04:55, Viktor Dukhovni wrote:
On Thu, Oct 01, 2015 at 06:43:17PM +0000, Tiantian Liu via RT wrote:
#3 0x004c5e98 in tls1_new (s=0xb4964ec8) at t1_lib.c:154
#4 0x00300376 in SSL_new () from /usr/lib/libptcoresdk.so.2
I found my application called SSL_new from /usr/lib/libptcoresdk.so.2, which is
third party library.
I think it should call the SSL_new from your Openssl library, like
/usr/lib/libssl.so.1.0.0. right?
Yes, this is an instance of "DLL hell". You need to link with the
right libssl. If libptcoresdk conflicts with the OpenSSL API, you
can't use both OpenSSL and that library.
_______________________________________________
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
