site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com hi all, i'm building on OSX 10.4.2. i've upgraded OpenSSL from v0.9.7 --> v0.9.8, built into /usr/local. 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) ... QUESTION: why is this occuring? is this a problem? thx for any/all comments! cheers, richard _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... i, alas, seem to be getting no 'traction' on this anywhere else, so i'll try here too ... 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) ... NOTE: the lack of a precedent path (/usr/local/) for the libssl*/libcrypto* link components in the latter case. the folks @ openssl suggest that this is NOT an openssl issue, rather a Mac one ... This email sent to site_archiver@lists.apple.com