On Sun, Jan 27, 2002 at 09:16:37AM +0100, Richard Levitte - VMS Whacker wrote:
> cjs> -L/usr/local/src/openssl-0.9.6c \
> cjs> +cpd /usr/local/src/openssl-0.9.6c:/usr/local/ssl/lib \
> cjs>
> cjs> ......
> cjs>
> cjs> then...
> cjs> hp[src/openssl-0.9.6c]$ make <-- Successful build
> cjs> hp[src/openssl-0.9.6c]$ make test <--- All tests work fine
> cjs> hp[src/openssl-0.9.6c]# make install
>
> In that test above, if the test programs and the openssl application
> were linked against the shared library (something that's implemented
> in the current development of 0.9.7), exactly which shared libraries
> are they going to use, the ones on the current build library or
> previously installed ones? And in the latter case, what happens if
> this is the first time OpenSSL is built on the system, i.e. there are
> no OpenSSL libraries in the installationn directory?
We are in a conflict here:
* HP-UX records the absolute path to shared libraries when linking.
The usual technique is to re-link during make install. Unfortunately
this is not designed into OpenSSL's "make install" routines (yet?).
Every other technique is error prone. If we use the +cdp technique,
we probably cannot succeed in "make test", as the libraries are not
yet installed at their final destination. If we don't use it, the
"openssl" command line tool won't work as it would try to pick the
shared libraries from the source path.
(Even worse: if there are older libraries already installed, we must
make sure that these are not picked up during build stage and mess
up everything.)
The most simple solution would be to build with a static openssl
command line tool (see also next point).
* The build process for the shared libraries is not that much of a problem.
There is no need to build libssl.sl against libcrypto.sl, one can
simply leave it out. Applications link against -lssl -lcrypto anyway.
If you have a look into the 0.9.7 version of the build procedure, you
will note that I made the appropriate change long time ago.
Simply build the shared libs independent of each other and put them
into their target destination upon install, that's it.
The only problem: in between the procedure was changed to build the
"openssl" command line tool against the shared libraries, so probably
0.9.7 is currently broken as well.
Solution: build "openssl" against static libs _or_ we have to modify the
"install" procedure such that "openssl" is relinked upon installation.
Best regards,
Lutz
PS. I don't know whether I will have the time to look into it before
Wednesday.
--
Lutz Jaenicke [EMAIL PROTECTED]
http://www.aet.TU-Cottbus.DE/personen/jaenicke/
BTU Cottbus, Allgemeine Elektrotechnik
Universitaetsplatz 3-4, D-03044 Cottbus
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
