From scot at thinkunix.net  Sun Nov 28 15:45:42 2004
From: scot at thinkunix.net (Scot Jenkins)
Date: Mon Jan 17 14:29:09 2005
Subject: [TCLUG-DEVEL] Shared library version question
Message-ID: <20041128154542.A32470@thinkunix.net>

I have a RedHat system I'm upgrading from openssl 0.9.6 to 0.9.7.  I
built new openssl rpms but when I try to upgrade it appears some binaries 
have been built specifically against the older version of openssl:

# rpm -Uvh --test openssl-0.9.7e-1.i386.rpm openssl-devel-0.9.7e-1.i386.rpm
error: failed dependencies:
        libcrypto.so.0.9.6 is needed by wget-1.8.2-1
        libcrypto.so.0.9.6 is needed by cadaver-0.20.5-1
        libcrypto.so.0.9.6 is needed by postgresql-7.3.2-1
        libssl.so.0.9.6 is needed by wget-1.8.2-1
        libssl.so.0.9.6 is needed by cadaver-0.20.5-1
        libssl.so.0.9.6 is needed by postgresql-7.3.2-1

Note that these binaries are using shared libraries, they just are
pointing at a specific version:

$ ldd /usr/bin/wget
        libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x40009000)
        libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x40038000)

cadaver and postgres binaries show similar results.

Here's how the libraries and symlinks look under /usr/lib:

$ cd /usr/lib; ls -l libcrypto* libssl*
-rw-r--r--    1 root     root      1798322 Oct 28 17:46 libcrypto.a
lrwxrwxrwx    1 root     root           14 Oct 28 22:19 libcrypto.so ->
libcrypto.so.0*
lrwxrwxrwx    1 root     root           18 Oct 28 12:55 libcrypto.so.0
-> libcrypto.so.0.9.6*
-rwxr-xr-x    1 root     root      1157923 Oct 28 17:46 libcrypto.so.0.9.6*
-rw-r--r--    1 root     root       275996 Oct 28 17:46 libssl.a
lrwxrwxrwx    1 root     root           11 Oct 28 22:19 libssl.so ->
libssl.so.0*
lrwxrwxrwx    1 root     root           15 Oct 28 12:55 libssl.so.0 ->
libssl.so.0.9.6*
-rwxr-xr-x    1 root     root       214722 Oct 28 17:46 libssl.so.0.9.6*

I know I can just install the new version of openssl then rebuild the
other (now broken) software against the new libraries.  My question is, 
how can I force things to build against the symlinks "libssl.so" and 
"libcrypto.so" so that the next time I upgrade openssl, I don't have 
to rebuild a bunch of software?
-- 
scot

_______________________________________________
tclug-devel mailing list
tclug-devel@mn-linux.org
https://mailman.real-time.com/mailman/listinfo/tclug-devel