any insights? upgrade from OpenSSL v0.9.7 --> 0.9.8 changes linking behavior on OSX
any insights? upgrade from OpenSSL v0.9.7 --> 0.9.8 changes linking behavior on OSX
- Subject: any insights? upgrade from OpenSSL v0.9.7 --> 0.9.8 changes linking behavior on OSX
- From: OpenMacNews <email@hidden>
- Date: Tue, 19 Jul 2005 07:28:01 -0700
hi all,
i, alas, seem to be getting no 'traction' on this anywhere else, so i'll try
here too ...
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?
the folks @ openssl suggest that this is NOT an openssl issue, rather a Mac one
...
thx for any/all comments!
cheers,
richard
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden