PROBLEMS revision 100936 
1100936Snectar* System libcrypto.dylib and libssl.dylib are used by system ld on MacOS X.
2100936Snectar[NOTE: This is currently undergoing tests, and may be removed soon]
3109998Smarkm
4109998SmarkmThis is really a misfeature in ld, which seems to look for .dylib libraries
5109998Smarkmalong the whole library path before it bothers looking for .a libraries.  This
6109998Smarkmmeans that -L switches won't matter unless OpenSSL is built with shared
7109998Smarkmlibrary support.
8109998Smarkm
9109998SmarkmThe workaround may be to change the following lines in apps/Makefile.ssl and
10100936Snectartest/Makefile.ssl:
11100936Snectar
12100936Snectar  LIBCRYPTO=-L.. -lcrypto
13100936Snectar  LIBSSL=-L.. -lssl
14100936Snectar
15142425Snectarto:
16142425Snectar
17100936Snectar  LIBCRYPTO=../libcrypto.a
18100936Snectar  LIBSSL=../libssl.a
19100936Snectar
20100936SnectarIt's possible that something similar is needed for shared library support
21100936Snectaras well.  That hasn't been well tested yet.
22100936Snectar
23100936Snectar
24100936SnectarAnother solution that many seem to recommend is to move the libraries
25100936Snectar/usr/lib/libcrypto.0.9.dylib, /usr/lib/libssl.0.9.dylib to a different
26100936Snectardirectory, build and install OpenSSL and anything that depends on your
27100936Snectarbuild, then move libcrypto.0.9.dylib and libssl.0.9.dylib back to their
28100936Snectaroriginal places.  Note that the version numbers on those two libraries
29100936Snectarmay differ on your machine.
30100936Snectar
31100936Snectar
32100936SnectarAs long as Apple doesn't fix the problem with ld, this problem building
33100936SnectarOpenSSL will remain as is.
34100936Snectar
35100936Snectar