Re: Leopard xCode 2.5 Libtool build error
Re: Leopard xCode 2.5 Libtool build error
- Subject: Re: Leopard xCode 2.5 Libtool build error
- From: Chris Espinosa <email@hidden>
- Date: Mon, 3 Dec 2007 16:53:07 -0800
On Dec 3, 2007, at 2:46 PM, David Alter wrote:
Hi All,
I have a project that works fine when building it on Tiger. Opened
it up with xCode 2.5 on Leopard and it does not want to build. I
have not seen errors like this before and I not sure what to look
for. I have this same error regardless if I'm building as Universal
or just i386.
Here is the error
\Libtool /Users/david/Development/Projects/FM-NEXUS/Dev/license/
build/Debug/libfmnexusLicAn.a normal i386
cd /Users/david/Development/Projects/FM-NEXUS/Dev/license
setenv MACOSX_DEPLOYMENT_TARGET 10.4
/Xcode2.5/usr/bin/libtool -static -arch_only i386 -o /Users/david/
Development/Projects/FM-NEXUS/Dev/license/build/Debug/
libfmnexusLicAn.a -L/Users/david/Development/Projects/FM-NEXUS/Dev/
license/build/Debug -L/Users/david/Development/Projects/FM-NEXUS/Dev/
license/libs /usr/lib/libssl.dylib /usr/lib/libcrypto.dylib -
filelist /Users/david/Development/Projects/FM-NEXUS/Dev/license/
build/LicAnallzer.build/Debug/fmnexusLicAn.build/Objects-normal/i386/
fmnexusLicAn.LinkFileList -syslibroot /Xcode2.5/SDKs/MacOSX10.4u.sdk
/Xcode2.5/usr/bin/libtool: for architecture ppc7400 object: /usr/lib/
libssl.dylib malformed object (unknown load command 7)
/Xcode2.5/usr/bin/libtool: for architecture: (null) file: /usr/lib/
libssl.dylib is not an object file (not allowed in a library)
/Xcode2.5/usr/bin/libtool: for architecture ppc64 object: /usr/lib/
libssl.dylib malformed object (unknown load command 7)
/Xcode2.5/usr/bin/libtool: for architecture ppc7400 object: /usr/lib/
libcrypto.dylib malformed object (unknown load command 7)
/Xcode2.5/usr/bin/libtool: for architecture: (null) file: /usr/lib/
libcrypto.dylib is not an object file (not allowed in a library)
/Xcode2.5/usr/bin/libtool: for architecture ppc64 object: /usr/lib/
libcrypto.dylib malformed object (unknown load command 7)
This Tiger project is explicitly linking against Leopard link
libraries (/usr/lib/libcrypto) instead of using an SDK. This isn't
going to work.
You need to find where in your project an explicit path to
libcrypto.dylib is being set and make that relative to the SDK.
Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden