I've gathered some info the last few days and pondered a bit, and
finally came up with a hopefully better system to get shared libraries
(libcrypto.so and libssl.so).  I've done pretty extensive tests on my
laptop (running GNU/Debian unstable), and it seems to work well there.

The issues I've battled with are:

  - installing the shared libraries didn't create softlinks from
    things like libcrypto.so.0 to libcrypto.so.0.9.6, and instead made
    you end up with actual copies of the same library under several
    names.

  - the Makefile was not very comprehensible and did a lot of magic to
    get things right and in the right order.

  - {Net,Open,Free}BSD had no or not very good support.

  - if there's no need for special compiler flags on the platform used
    to create PIC code, no shared library would get created.

Things I have still not dealt with:

  - HP-UX, AIX (I've access to an HP box (HP-UX 11) and an AIX box
    (AIX 4.3), but it still takes some time to get all I need
    together).

  - linking the OpenSSL applications and test programs against the
    shared libraries instead of the static ones.


If I did link against shared libraries, I would rapidly get in
trouble, since I install on /usr/local/ssl, and there are older
OpenSSL libraries (from a Debian package) in /usr/lib...  If anyone
has a good solution for this one, I'm listening.  The stuff I have in
my /usr/lib is this: 

lrwxrwxrwx    1 root     root           18 mar 16  2000 /usr/lib/libcrypto.so.0 -> 
libcrypto.so.0.9.4
-rw-r--r--    1 root     root       685228 mar 11  2000 /usr/lib/libcrypto.so.0.9.4
-rw-r--r--    1 root     root       808952 okt  5 20:50 /usr/lib/libcrypto.so.0.9.5
lrwxrwxrwx    1 root     root           15 mar 16  2000 /usr/lib/libssl.so.0 -> 
libssl.so.0.9.4
-rw-r--r--    1 root     root       177356 mar 11  2000 /usr/lib/libssl.so.0.9.4
-rw-r--r--    1 root     root       183864 okt  5 20:50 /usr/lib/libssl.so.0.9.5


Anyhow, there have been a number of people with opinions about the way
shared libraries were produce with OpenSSL through the configuration
option "shared".  I'd like primarly those people, but also anyone
who'd like to do so, to grab the next snapshot (it'll be produced in
about 2½ hours from the time of writing) and test this, both
build and install.  I recommend installing in a private directory, so
you don't happen to disturb the rest of the system:

  ./config shared --openssldir=$(HOME)/private-root/usr/local/ssl
  make
  make test
  make install


This should work on any system.  However, on systems where Configure
doesn't have support for shared libraries, you simply won't see any,
but the rest (building the static libraries and so on) should work as
before.  If not, I've things to do, I guess :-).

-- 
Richard Levitte   \ Spannvägen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken   \ S-168 35  BROMMA  \ T: +46-8-26 52 47
Redakteur@Stacken   \      SWEDEN       \ or +46-709-50 36 10
Procurator Odiosus Ex Infernis                -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Software Engineer, Celo Communications: http://www.celocom.com/

Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to