Re: Error msg: load command <##> unknown cmd field
Re: Error msg: load command <##> unknown cmd field
- Subject: Re: Error msg: load command <##> unknown cmd field
- From: Eric Albert <email@hidden>
- Date: Wed, 5 Jul 2006 14:05:18 -0700
On Jul 5, 2006, at 10:59 AM, Dan Wood wrote:
We are having some build issues with xcode on some -- not all -- of
our build machines. One intel, another PPC, though other intel and
PPC machines are fine.
I am linking in a custom-built set of webkit frameworks. This has
been working fine until recently, when I updated to a new version
of webkit and updated everything to xcode 2.3.
The problem is in the step where it's linking my framework
(KTComponents) against the other frameworks. Here's a sample of
the transcript.
Interestingly, there are two numbers in the error message, 18 and 21.
ld: /Users/dwood/Subversion/sandvox/trunk/Frameworks/
KTComponents/../../Frameworks/WebKit/JavaScriptCore.framework/
JavaScriptCore load command 18 unknown cmd field
ld: /Users/dwood/Subversion/sandvox/trunk/Frameworks/
KTComponents/../../Frameworks/WebKit/WebCore.framework/WebCore load
command 21 unknown cmd field
ld: /Users/dwood/Subversion/sandvox/trunk/Frameworks/
KTComponents/../../Frameworks/WebKit/WebKit.framework/WebKit load
command 18 unknown cmd field
/usr/bin/libtool: internal link edit command failed
It looks like this is the linker telling you that it doesn't
recognize load commands with values of 18 and 21. You can see load
command constants in /usr/include/mach-o/loader.h. 18 is
LC_SUB_FRAMEWORK and 21 is LC_SUB_LIBRARY. Both of those have been
supported in Mac OS X for a very long time. I can't imagine how you
could end up with a linker which doesn't understand them, but you
might want to reinstall the developer tools.
-Eric
_______________________________________________
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