> appro> And as for -rpath option. What are the arguments against making it
> appro> default?
>
> Distribution. If someone builds libcrypto.so with -rpath
> /usr/local/lib, it means libcrypto.so has to be installed in
> /usr/local/lib on the target system even if the admin on that one
> would have prefered to have it in /opt/ssl/lib.
What is the ratio between those who distribute and compile themselves
for Tru64? Among those who prefer binary distribution what is the ratio
of those who fetch one and then actually relocate it? Who (majority or
minority) do we care about? Note that the way it looks now the configure
procedure favors those who compile themselves. Indeed, those who
distribute binaries should probably generate blended code and therefore
has basicaly two options: a) compile on some ancient box; b) modify
configure line. How about alpha-cc (with -fast alone) and alpha-cc-dist
(with -fast -arch generic) targets and moving -rpath to $lflags (or add
$shared_lflags) field of only alpha-cc record? Basically we could/should
have something similar for all OSes, i.e. choice between optimized
builds suitable for the compiling host and blended build suitable for
binary distribution.
A.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
