Thanks. I was going to recreate the list locally.
I have a read-only path to the source and was going to run through a
Configure/build test to make sure that nothing is broken.
I'll make sure that any relative links (the include files and a few
others) stay relative in the build area, and anything else that is
modified by Configure/build is also local to the build area.
Prior to this i've just built in the source, installed (into a packaging
directory), cleaned, made again for the sparcv9 version, installed (into
a different packaging directory) and then made a combined package that
understands at (package installation time) whether it should include
sparcv9 specific versions on the target host.
I thought i'd keep things a little cleaner by building outside the
source this time round, but it's been more hassle than I expected. I
am surprised that no one else has griped that it doesn't work as least
as well as many other packages that build for multiple architectures.
\nick
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
