Re: libcrypto and libssl arch issue
site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Thanks.....Peter On Nov 16, 2007, at 12:40 PM, Stéphane Sudre wrote: On Nov 16, 2007, at 6:14 PM, Matt Meissner wrote: Hi, On my fresh 10.5.1 system on an Intel iMac: _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... Speaking of OpenSSL, can anyone clue me in as to the reason for still using version 0.9.7 ? I had thought that Leopard would include 0.9.8 and was surprised that it didn't. $ file /usr/lib/libcrypto.* /usr/lib/libcrypto.0.9.7.dylib: Mach-O universal binary with 4 architectures /usr/lib/libcrypto.0.9.7.dylib (for architecture ppc7400): Mach-O dynamically linked shared library ppc /usr/lib/libcrypto.0.9.7.dylib (for architecture ppc64): Mach-O 64- bit dynamically linked shared library ppc64 /usr/lib/libcrypto.0.9.7.dylib (for architecture i386): Mach-O dynamically linked shared library i386 /usr/lib/libcrypto.0.9.7.dylib (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64 /usr/lib/libcrypto.0.9.dylib: Mach-O dynamically linked shared library ppc /usr/lib/libcrypto.dylib: Mach-O universal binary with 4 architectures /usr/lib/libcrypto.dylib (for architecture ppc7400): Mach-O dynamically linked shared library ppc /usr/lib/libcrypto.dylib (for architecture ppc64): Mach-O 64-bit dynamically linked shared library ppc64 /usr/lib/libcrypto.dylib (for architecture i386): Mach-O dynamically linked shared library i386 /usr/lib/libcrypto.dylib (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64 libcrypto.0.9.dylib is PPC only. Same problem with libssl. 0.9.dylib. It causes dlopen() /usr/lib/libcrypto.0.9.dylib to fail on Intel platforms. Before I submit a bug report, just wondering if anyone else can confirm this or if it is an oddity of my install. Yes, this is a known issue, but I'm not sure it's worth filing a bug report: I filed a bug report against this problem when there was still plenty of time to fix it (> 5 months IIRC) and it was not fixed. And since you would have anyway a version of Leopard that does not include this version, the idea is to forget about it and find a solution. In my case, the solution has been to use different settings for the i386 and ppc builds. You would of course need to ship an update of your product. This email sent to site_archiver@lists.apple.com
participants (1)
-
Peter Lovell