From 2f13e0916590f8488178999aec4874ed5662a031 Mon Sep 17 00:00:00 2001 From: nectar Date: Tue, 30 Jul 2002 13:38:06 +0000 Subject: Import of OpenSSL 0.9.6e. --- crypto/openssl/PROBLEMS | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 crypto/openssl/PROBLEMS (limited to 'crypto/openssl/PROBLEMS') diff --git a/crypto/openssl/PROBLEMS b/crypto/openssl/PROBLEMS new file mode 100644 index 0000000..f072449 --- /dev/null +++ b/crypto/openssl/PROBLEMS @@ -0,0 +1,34 @@ +* System libcrypto.dylib and libssl.dylib are used by system ld on MacOS X. +[NOTE: This is currently undergoing tests, and may be removed soon] + +This is really a misfeature in ld, which seems to look for .dylib libraries +along the whole library path before it bothers looking for .a libraries. This +means that -L switches won't matter unless OpenSSL is built with shared +library support. + +The workaround may be to change the following lines in apps/Makefile.ssl and +test/Makefile.ssl: + + LIBCRYPTO=-L.. -lcrypto + LIBSSL=-L.. -lssl + +to: + + LIBCRYPTO=../libcrypto.a + LIBSSL=../libssl.a + +It's possible that something similar is needed for shared library support +as well. That hasn't been well tested yet. + + +Another solution that many seem to recommend is to move the libraries +/usr/lib/libcrypto.0.9.dylib, /usr/lib/libssl.0.9.dylib to a different +directory, build and install OpenSSL and anything that depends on your +build, then move libcrypto.0.9.dylib and libssl.0.9.dylib back to their +original places. Note that the version numbers on those two libraries +may differ on your machine. + + +As long as Apple doesn't fix the problem with ld, this problem building +OpenSSL will remain as is. + -- cgit v1.1