• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Xcode 2.2 precomp link warning
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode 2.2 precomp link warning


  • Subject: Re: Xcode 2.2 precomp link warning
  • From: Eric Albert <email@hidden>
  • Date: Sun, 13 Nov 2005 10:25:53 -0800

On Nov 13, 2005, at 3:42 AM, Greg Hurrell wrote:

El 12/11/2005, a las 3:54, Ricky Sharp escribió:

I just moved my Cocoa application and IB palette projects from Xcode 2.1 to 2.2. All projects target the 10.4u SDK and are built as universal binaries. I have Mac OS X 10.4.3

My palettes build a-ok. However, in the Development config of the app project, I receive the following link warning:

/usr/bin/ld: warning /Library/Caches/com.apple.Xcode.501/SharedPrecompiledHeaders/ Drills_Prefix-fwqjojpadsxwrxgacyvlyoodmshw/Drills_Prefix.pch.gch.o cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded)

I also have been seeing a lot of similar warning since upgrading to Xcode 2.2. In my case, they appear in only a few of the 20 projects that I have built since upgrading. I have yet to identify what it is that those few projects have in common that makes them produce the warning.


/usr/bin/ld: warning /Library/Caches/com.apple.Xcode.501/SharedPrecompiledHeaders/AppKit- blqywaoivjvvmxbulbeesgzoomdp/AppKit.h.gch.o cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded)

How bad does this warning rank on the badness scale? Is the linked product horribly broken as a result or is this just a minor thing?

In both cases here, the thing that stands out as odd is that the linker is being told to pull in your precompiled header. That doesn't make any sense. If you can figure out why that's happening, I bet you'll be able to track down the real problem. Perhaps the .pch file is in your compile sources build phase or something like that?


-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


  • Follow-Ups:
    • Re: Xcode 2.2 precomp link warning
      • From: Chris Espinosa <email@hidden>
References: 
 >Xcode 2.2 precomp link warning (From: Ricky Sharp <email@hidden>)
 >Re: Xcode 2.2 precomp link warning (From: Greg Hurrell <email@hidden>)

  • Prev by Date: Re: Serious problem with XCode 2.2 treating unsigned long differently ?!
  • Next by Date: Re: Xcode 2.2 precomp link warning
  • Previous by thread: Re: Xcode 2.2 precomp link warning
  • Next by thread: Re: Xcode 2.2 precomp link warning
  • Index(es):
    • Date
    • Thread