These instructions, from the CHANGES file:
==========
*) Add appropriate support for separate platform-dependent build
directories. The recommended way to make a platform-dependent
build directory is the following (tested on Linux), maybe with
some local tweaks:
# Place yourself outside of the OpenSSL source tree. In
# this example, the environment variable OPENSSL_SOURCE
# is assumed to contain the absolute OpenSSL source directory.
mkdir -p objtree/"`uname -s`-`uname -r`-`uname -m`"
cd objtree/"`uname -s`-`uname -r`-`uname -m`"
(cd $OPENSSL_SOURCE; find . -type f -o -type l) | while read F; do
mkdir -p `dirname $F`
ln -s $OPENSSL_SOURCE/$F $F
done
To be absolutely sure not to disturb the source tree, a "make clean"
is a good thing. If it isn't successfull, don't worry about it,
it probably means the source directory is very clean.
[Richard Levitte]
==========
don't work very well -- in particular, files in $OPENSSL_SOURCE which are
relative links already will end up as absolute links into $OPENSSL_SOURCE,
which breaks those which incorporate results of the Configure step,
such as "include/openssl/opensslconf.h" which should be a link to
"../../crypto/opensslconf.h".
This can lead to some distressing behavior, such as the library being compiled
with RC4_INT being an int, while clients compiled after openssl has been
installed believe it is an unsigned char.
Nick Briggs
Palo Alto Research Center
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
