ssl-3.10.1 (in /usr/erlware) was causing errors on my system because
it can't find the shared libraries libssl and libcrypto, but they were
definitely installed.
It seems that the Erlware version of ssl-3.10.1 was compiled on a
system that linked the priv/bin/ssl_esock binary to libssl.so.4 and
crypto.so.4. My Ubuntu (32 and 64 bit) does not have libssl.so.4 (or
libcrypto.so.4) - it has .so.0.9.8. The ssl_esock binary cannot find
the .so.4 names and causes an error. The missing links can easily be
verified by using ldd:
# ldd /usr/local/erlware/lib/ssl-3.10.1/priv/bin/ssl_esock
... stuff ...
libssl.so.4 => not found
libcrypto.so.4 => not found
In addition, this binary is supposed to be chmod +x, but Erlware's
version is not set executable.
One might think this is an Erlang makefile problem, but when I
compile OTP R13B on my system, ssl_esock is correctly linked to
libssl.so.0.9.8 and libcrypto.so.0.9.8.
A workaround seems to be:
cd /usr/lib
ln -s libcrypto.so.0.9.8 libcrypto.so.4
ln -s libssl.so.0.9.8 libssl.so.4
chmod +x /usr/local/erlware/lib/ssl-3.10.1/priv/bin/ssl_esock
Now ldd shows ssl_esock to be happy.
# ldd /usr/local/erlware/lib/ssl-3.10.1/priv/bin/ssl_esock
... stuff...
libssl.so.4 => /usr/lib/libssl.so.4 (0xb7ef1000)
libcrypto.so.4 => /usr/lib/libcrypto.so.4 (0xb7d9b000)
Perhaps when installing ssl-3.10.1, Erlware could check for the
existence of libssl.so.4 and libcrypto.so.4 and create the softlinks
if required?
Also, sometimes on my system the ssl_esock binary mysteriously and
spontaneously reverts to chmod -x status. I have no explanation for
this.
Hope this helps someone, somewhere.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"erlware-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/erlware-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
