Wrong soname in openssl libraries -> library not found

[schoopy]

Dear all,

Could someone else commit that version beta13 is having problem with ldap.
Cause is libcrypto.so.0.9.7 not found even though the links exists but ldconfig does not take it into account due to bad soname.

check :

ldd /usr/lib/sasl/libotp.so.2

linux-gate.so.1 => (0xb7ee8000)
libcrypto.so.0.9.7 => not found
libresolv.so.2 => /lib/libresolv.so.2 (0xb7ec2000)
libc.so.6 => /lib/libc.so.6 (0xb7d83000)
/lib/ld-linux.so.2 (0xb7ee9000)

My feeling is that openssl is to be recompiled!

Regards

[schoopy]

Sorry I was talking about beta12.
The problem is in the sasl library that have direct dependency to openssl 0.9.7.
Whatever symlink you try to create libcrypto.so.0.9.7 will no appear in the ldconfig, there will only be 0.9.8. Same for libssl.so.0.9.7.
The only possibility is to export LD_LIBRARY_PATH so that symlink get used. This is rather painful especially within script.

Consequently Cyrus-sasl has to be recompiled, I tried and now problem is gone.

Regards,

[Author]

Posts