> Unfortunately, about -R/-rpath, I've avoided it so far for exactly the > reason you mentioned: it doesn't quite support moving libraries to a > dofferent place and still have it work.
And that is what I'm suggesting to adhere to. I.e. to avoid it (and even to remove it from tru64!) and leave this final decision to those who deploy the toolkit. > And also, I have understood > that libssl.so does need a -R/-rpath to be able to find libcrypto.so, > on which it depends. This is not true. The fact that 'ldd libssl.so' says "can't locate libcrypto.so" does *not* mean that libssl.so is bound to fail to link with libcrypto.so. -L and -R options at *application* link time provide for that. -R/-rpath option at libssl.so link time can and should be omitted. -R/-rpath option at *application* link time is the one to be used. A. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
