Re: Xcode 2.3 won't compile simple PCH file anymore
Re: Xcode 2.3 won't compile simple PCH file anymore
- Subject: Re: Xcode 2.3 won't compile simple PCH file anymore
- From: Eric Albert <email@hidden>
- Date: Mon, 3 Jul 2006 23:50:44 -0700
On Jul 3, 2006, at 6:56 PM, Mark Munz wrote:
I just upgraded to Xcode 2.3 and it appears to be unable to compile my
existing project.
It appears to be choking on the PCH file, which is just:
#ifdef __OBJC__
#import <Cocoa/Cocoa.h>
#endif
Here is the error:
In file included from /usr/include/sys/acl.h:26,
from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/
CoreServices.framework/Frameworks/CarbonCore.framework/Headers/
Files.h:61,
from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/
CoreServices.framework/Frameworks/CarbonCore.framework/Headers/
Components.h:32,
from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/
CoreServices.framework/Frameworks/CarbonCore.framework/Headers/
CarbonCore.h:81,
from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/
CoreServices.framework/Headers/CoreServices.h:21,
from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/
ApplicationServices.framework/Headers/ApplicationServices.h:20,
from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/
Foundation.framework/Headers/NSAppleEventDescriptor.h:8,
from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/
Foundation.framework/Headers/Foundation.h:104,
from
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/
Cocoa.framework/Headers/Cocoa.h:12,
from /Users/[...]/projectfile_Prefix.pch:6:
/usr/include/sys/kauth.h:233: error: parse error before "xsecurity"
Can anyone give me a clue as to what might be happening here? This
error doesn't really give me any clues as to what the problem could be
(esp. considering the project compiled fine under 2.2.1).
It looks like you're getting headers from /usr/include included,
rather than /Developer/SDKs/MacOSX10.4u.sdk/usr/include. If you
could post the detailed build line (not the the full log, but just
the compiler invocation which failed) it should be fairly easy to
track this down, but a couple possibilities are that you're
specifying /Developer/SDKs/... as a header path rather than setting
your SDK, or that you're explicitly specifying /usr/include as a
header path.
-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