On Sun, 6 Jan 2002, Pier Fumagalli wrote:
> My hint - or solution :( is to remove the /usr/lib/libcrypto.* and
> /usr/lib/libssl.* _BEFORE_ compiling OpenSSL....
Removing libssl.* and libcrypt.* is a BAD idea - you'll break some
important stuff that's linked against them. E.g. Mail's Message
framework:
localhost> ldd /System/Library/Frameworks/Message.framework/Message
/System/Library/Frameworks/Message.framework/Message:
...
/usr/lib/libcrypto.0.9.dylib (compatibility version 0.9.0, current version
0.9.6)
...
Just rm the symlinks libssl.dylib and libcrypo.dylib, leaving the real
libs (libX.0.9.dylib):
/usr/lib/libcrypto.dylib -> libcrypto.0.9.dylib
/usr/lib/libssl.dylib -> libssl.0.9.dylib
>
> The patch by itself (attached) fixes just the "config" script and some
> definitions around the source files (not much)... The only thing I'm
> concerned about is about the gmtime/gmtime_r differences... AFAICS there's
> no gmtime_r under OS/X, so when compiling with threading support, I had to
> rely on gmtime... And I don't know if that screws the whole thing up.
I've applied the patches on 0.9.6. I'm in the process of building - I'll
let you know how it comes out. In any case, these patches should be
modified and applied to 0.9.7.
>
> BTW, is there interest in a "Cocoa-Framework" style of build in the main
> development tree? It's a pretty cool feature of OS/X for dynamic libraries,
> with support for versioning and stuff... I'm working on it right now...
IMO, sometimes a lib is just a lib. openssl is a lib on all
(other) platforms, I don't think marginalizing X would be a good thing.
BUT - if you wanted to make a complete Cocoa cover for it, then that would
probably be an interesting framework.
- sq
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
