First, a small addition to the openssl.patch for "test": http://www.algonet.se/~afb/openpkg/openssl-addition.diff (originally did the same thing for "apps" for the bootstrap)
However, the *reason* for the workaround is the fact that since OpenPKG does not provide a shared OpenSSL library, Darwin ld(1) will try to use the /usr/lib variant instead... So this will affect everything else using OpenSSL as well. This is noted in OpenSSL's "PROBLEMS" file, by the way. (file at http://cvs.openssl.org/rlog?f=openssl/PROBLEMS) There are a few workarounds to this little OS quirk: 1) change each and every (!) Makefile using OpenSSL, from "-lssl" to "/openpkg/lib/libssl.a" instead... 2) build shared libraries for OpenPKG's OpenSSL too. (this will make ld pick them up from /openpkg/lib) 3) move the system libraries aside, while building... (/usr/lib/libssl.dylib and /usr/lib/libcrypto.dylib, note that only the non-versioned developer symlinks are affected - not the versioned runtime libraries) I did approach 1) for OpenSSL and approach 3) for Apache, and then "the pitch" succeeded* in running apache+lynx. :-) --anders *) when using the Apple compiler /usr/bin/cc, that is... I faked the binutils/gcc packages to fill dependencies. ______________________________________________________________________ OpenPKG http://openpkg.org Developer Communication List openpkg-dev@openpkg.org
