| PROBLEMS (100936) | PROBLEMS (101613) |
|---|---|
| 1* System libcrypto.dylib and libssl.dylib are used by system ld on MacOS X. 2[NOTE: This is currently undergoing tests, and may be removed soon] 3 4This is really a misfeature in ld, which seems to look for .dylib libraries 5along the whole library path before it bothers looking for .a libraries. This 6means that -L switches won't matter unless OpenSSL is built with shared 7library support. 8 --- 18 unchanged lines hidden (view full) --- 27build, then move libcrypto.0.9.dylib and libssl.0.9.dylib back to their 28original places. Note that the version numbers on those two libraries 29may differ on your machine. 30 31 32As long as Apple doesn't fix the problem with ld, this problem building 33OpenSSL will remain as is. 34 | 1* System libcrypto.dylib and libssl.dylib are used by system ld on MacOS X. 2[NOTE: This is currently undergoing tests, and may be removed soon] 3 4This is really a misfeature in ld, which seems to look for .dylib libraries 5along the whole library path before it bothers looking for .a libraries. This 6means that -L switches won't matter unless OpenSSL is built with shared 7library support. 8 --- 18 unchanged lines hidden (view full) --- 27build, then move libcrypto.0.9.dylib and libssl.0.9.dylib back to their 28original places. Note that the version numbers on those two libraries 29may differ on your machine. 30 31 32As long as Apple doesn't fix the problem with ld, this problem building 33OpenSSL will remain as is. 34 |
| 35 36* Parallell make leads to errors 37 38While running tests, running a parallell make is a bad idea. Many test 39scripts use the same name for output and input files, which means different 40will interfere with each other and lead to test failure. 41 42The solution is simple for now: don't run parallell make when testing. |
|