I took the plunge and was one of the first people in line yesterday at the Apple Store in Columbia, MD yesterday. I then raced home to find out what Leopard was all about. The first acceptance test was being able to work with my job’s VPN, and problems quickly arose.
Leopard ships with a libcrypto and libssl that only has the ppc architecture:
cmac:lib bryan$ file libcrypto.0.9.dylib libcrypto.0.9.dylib.old: Mach-O dynamically linked shared library ppc
A symptom of this error from the console log could potentially look like:
Dyld Error Message:
Library not loaded: /usr/lib/libssl.0.9.dylib
Referenced from: /Library/Frameworks/net.juniper.DSCoreServices.framework/Versions/5.5.0/net.juniper.DSCoreServices
Reason: no suitable image found. Did find:
/usr/lib/libssl.0.9.dylib: mach-o, but wrong architecture
/usr/lib/libssl.0.9.dylib: mach-o, but wrong architecture
or
Dyld Error Message:
Library not loaded: /usr/lib/libcrypto.0.9.dylib
Referenced from: /Library/Frameworks/net.juniper.DSCoreServices.framework/Versions/5.5.0/net.juniper.DSCoreServices
Reason: no suitable image found. Did find:
/usr/lib/libcrypto.0.9.dylib: mach-o, but wrong architecture
/usr/lib/libcrypto.0.9.dylib: mach-o, but wrong architecture
The easy solution to this is to backup you libcrypto.0.9.dylib, libssl0.9.dylib and copy over the libcrypto.0.9.7.dylib and libcrypto.0.9.7.dylib.
You can use Terminal.app to make these changes. It is in your Applications folder. (Make sure that you are only copying the part after the $)
$ cd /usr/lib $ sudo cp libcrypto.0.9.dylib libcrypto.0.9.dylib.old $ sudo cp libssl.0.9.dylib libssl.0.9.dylib.old $ sudo ln -sf libcrypto.0.9.7.dylib libcrypto.0.9.dylib $ sudo ln -sf libssl.0.9.7.dylib libssl.0.9.dylib
After this, you can close Terminal.
Updated 10/31 – changed directions to use ln instead.
