I know that LD_LIBRARY_PATH is evil and it\'s a good habit to avoid using it.
I have a program called server.c
on a remote Solaris 9 server that holds two versi
I figured out that I can include the absolute path of the specific library that I want to link to and it worked fine for me:
LD = ${RPATH} -lsocket -lnsl -lpthread ${OPENSSLDIR}/lib/libssl.so.1.0.0 \
${OPENSSLDIR}/lib/libcrypto.so.1.0.0
If you are using g++, Piotr Lesnicki pointed out that -l:libssl.so.1.0.0
also works. See more at the original post.
Do you have any links to the SSL lib? If not, can you create a link to the the desired SSL lib like
ln -s libssl.so.1.0.0 libssl.so
in the ssl directory and try it