why? upgrade from OpenSSL v0.9.7 --> 0.9.8 chages linking behavior on OSX

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

why? upgrade from OpenSSL v0.9.7 --> 0.9.8 chages linking behavior on OSX

OpenMacNews
hi all,

let's try this again ...

i'm building on OSX 10.4.2.

i've upgraded OpenSSL from v0.9.7 --> v0.9.8, built into /usr/local.

when i build an app against ssl libs, e.g., here: 'lynx' (results are the same
for an/all other apps ...), 'otool -L' on the resultant binary shows:

FOR OPENSSL VERSION v0.9.7
% otool -L lynx
...
  /usr/local/libssl.0.9.7.dylib (compatibility version 0.9.0, current version
0.9.7)
  /usr/local/libcrypto.0.9.7.dylib (compatibility version 0.9.0, current
version 0.9.7)
...

FOR OPENSSL VERSION v0.9.8
% otool -L lynx
...
  libssl.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
  libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
...

NOTE: the lack of a precedent path (/usr/local/) for the libssl*/libcrypto*
link components in the latter case.


QUESTION:

why is this occuring?  is this a problem?


thx for any/all comments!

cheers,

richard

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [hidden email]
Automated List Manager                           [hidden email]