Richard Levitte - VMS Whacker <[EMAIL PROTECTED]> in epsilon.openssl.dev:
> Could someone explain to me what's really the deal with the --prefix
> and --openssldir options to Configure? As it currently is, the whole
> thing is a heap of inconsistency. Depending on what is actually
> given, the final result may be one of the following:
>
> openssldir == prefix
> openssldir == prefix + "/ssl"
>
> This translates into the OPENSSLDIR and INSTALLTOP macros i Makefile.ssl,
> and gives clearly different installations because some of the
> installation actions use OPENSSLDIR while others use INSTALLTOP.
>
> So please tell me if there was some kind of thought behind this or if
> this needs some hacking. As it is right now, it's terribly confusing.
> It looks like what you should use to get the kind of installation
> that's usually mentioned is --openssldir. That makes prefix and
> openssldir equal.
This inconsistency exists for historical reasons (as usual).
The SSLeay installation directory layout is similar to what you now
get when using --openssldir=/usr/local/ssl. If someone wants
binaries, libraries, and header files to be installed to 'standard'
locations (such as /usr/local/bin, /usr/local/lib, and
/usr/local/include, respectively), they probably don't want the
SSLeay/OpenSSL specific stuff to reside directly under /usr/local;
this is why --prefix=/whatever sets openssldir to /whatever/ssl.
If we are going to change this, then we should always use
openssldir = prefix + "/ssl" (or prefix + "/openssldir")
because the openssldir = prefix variant doesn't make sense
if the directory is not exclusive to OpenSSL.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
