In message <[EMAIL PROTECTED]> on Fri, 10 Jan 2003 15:03:00 +0100, Andy
Polyakov <[EMAIL PROTECTED]> said:
appro> There is another option, "The Right Thing":-)
Of course :-).
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 also, I have understood
that libssl.so does need a -R/-rpath to be able to find libcrypto.so,
on which it depends. And you're quite correct, the openssl
application should be linked with it, which we don't do at all today...
appro> (*) Most OSes support equivalent option. Most notably -rpath (Linux,
appro> Tru64, IRIX). And when it comes to Solaris and Linux there is an easter
appro> egg here. Starting with 2.6 Solaris run-time linker implements support
appro> for $ORIGIN. E.g. if you pass -R \$ORIGIN/../lib to the linker, the
appro> application will be looking for .so objects in ../lib relative to the
appro> application binary. This $ORIGIN thing is very useful. It's so useful,
appro> that it's tempting to wrap openssl binary into a script which would
appro> emulate $ORIGIN on platforms that lack $ORIGIN. Yes, approximately the
appro> way autoconf does in build tree. Should I look into it?
That's a good idea.
--
Richard Levitte \ Spannv�gen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
\ SWEDEN \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
