• 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: strip error using framework in 10.5 build that was (I think) compiled on 10.6
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: strip error using framework in 10.5 build that was (I think) compiled on 10.6


  • Subject: Re: strip error using framework in 10.5 build that was (I think) compiled on 10.6
  • From: Kevin Brock <email@hidden>
  • Date: Tue, 13 Oct 2009 13:11:53 -0700

Chris Espinosa wrote:

On Oct 13, 2009, at 12:31 PM, Kevin Brock wrote:

I've got a set of projects that builds on both 10.5 & 10.6.  Standard 32/64 universal binary stuff.

I upgraded a 3rd party framework that didn't support 64-bit to a version that did (Growl-WithInstaller.framework v1.2), and now I can build the projects on 10.6 with Xcode 3.2, but on 10.5 with Xcode 3.1.4 I get the error:

strip: for architecture x86_64 object: <path to GWI.framework> malformed object (unknown load command 5)

Anyone have a clue about what this load command is?  I can't find many references to this exact error on the net.  The ones I have found are all people wondering what's going on--haven't seen any of them answered yet.

I *think* the framework was built on 10.6, but I'm not certain.

If you do an otool -l <path to GWI.framework> what is load command 5? If it's LC_DYLD_INFO_ONLY then the framework was not built with a Deployment Target of 10.5 and can't be used on Leopard.


It's LC_UUID.  Now load command *6* is 0x00000022, which shows up as 'unknown' on 10.5 and as LC_DYLD_INFO on 10.6.

The package that's built on 10.6 will install and run on 10.5.  I just can't build the package on 10.5.  It would *appear* that Xcode 3.2. is adding a load command to its frameworks that makes them unusable with 3.1.* projects...

Anyone know of a workaround for this?

I saw a similar problem where Xcode 3.1.2 was adding LC_UUID to certain type of projects, which made the binaries unusable on 10.4 (even though the target OS was 10.4).  Yes, I filed a radar about that one.  Still open.

Kevin

 _______________________________________________
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: strip error using framework in 10.5 build that was (I think) compiled on 10.6
      • From: Brandon Walkin <email@hidden>
References: 
 >strip error using framework in 10.5 build that was (I think) compiled on 10.6 (From: Kevin Brock <email@hidden>)
 >Re: strip error using framework in 10.5 build that was (I think) compiled on 10.6 (From: Chris Espinosa <email@hidden>)

  • Prev by Date: Re: strip error using framework in 10.5 build that was (I think) compiled on 10.6
  • Next by Date: std::__debug problem with linking against template libraries
  • Previous by thread: Re: strip error using framework in 10.5 build that was (I think) compiled on 10.6
  • Next by thread: Re: strip error using framework in 10.5 build that was (I think) compiled on 10.6
  • Index(es):
    • Date
    • Thread