Hello all,

I've got a relatively minor problem with OpenSSL linking, it may be a flaw in the configure script, or just me not finding the right option.

Here is is: I want to build OpenSSL with an integrated linker runpath, so I don't need LD_LIBRARY_PATH or crle hacks.

Since some OpenSSL binaries depend on the library itself, I built it this way:

./config --prefix=/usr/local/openssl-0.9.7g shared \
  -R/usr/local/openssl-0.9.7g/lib

However, it seems it's not using my -R parameter when linking libssl.so:

$ ldd lib/libssl.so
        libcrypto.so.0.9.7 =>    (file not found)
        libsocket.so.1 =>        /usr/lib/libsocket.so.1

It does work for the openssl binary, though:

$ ldd bin/openssl
libssl.so.0.9.7 => /usr/local/openssl-0.9.7g/lib/libssl.so.0.9.7 libcrypto.so.0.9.7 => /usr/local/openssl-0.9.7g/lib/libcrypto.so.0.9.7

I did a very small hack to my Makefile:

$ diff Makefile.bak Makefile
268c268
<               $(MAKE) SHLIBDIRS=ssl SHLIBDEPS='-lcrypto' build-shared; \
---
> $(MAKE) SHLIBDIRS=ssl SHLIBDEPS='-lcrypto -R/usr/local/openssl-0.9.7g/lib' build-shared; \

And now that works:

$ ldd lib/libssl.so
libcrypto.so.0.9.7 => /usr/local/openssl-0.9.7g/lib/libcrypto.so.0.9.7

Any idea on what would be the Right Way to do it? Is there another parameter I could give to ./config?

This on a Solaris 9 box, using SunCC.

Laurent
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    openssl-users@openssl.org
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to