• 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: Build mysteriously excludes G3s [Solved, but not understood]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Build mysteriously excludes G3s [Solved, but not understood]


  • Subject: Re: Build mysteriously excludes G3s [Solved, but not understood]
  • From: Greg Guerin <email@hidden>
  • Date: Fri, 19 Mar 2010 19:09:41 -0700

James Bucanek wrote:

To date, no one I've discussed this with has any clear idea why this happens.


http://developer.apple.com/mac/library/DOCUMENTATION/Darwin/Reference/ ManPages/man1/gcc.1.html

- - - -
The subtype of the file created (like ppc7400 or ppc970 or i686) is determined by the flags that specify the ISA that GCC is targetting, like -mcpu or -march. The -force_cpusubtype_ALL option can be used to override this.


The Darwin tools vary in their behavior when presented with an ISA mismatch. The assembler, as, will only permit instructions to be used that are valid for the subtype of the file it is generating, so you cannot put 64-bit instructions in an ppc750 object file. The linker for shared libraries, /usr/bin/libtool, will fail and print an error if asked to create a shared library with a less restrictive subtype than its input files (for instance, trying to put a ppc970 object file in a ppc7400 library). The linker for executables, ld, will quietly give the executable the most restrictive subtype of any of its input files.
- - - -


  -- GG

_______________________________________________
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: Build mysteriously excludes G3s [Solved, but not understood]
      • From: James Bucanek <email@hidden>
  • Prev by Date: Re: Build mysteriously excludes G3s [Solved, but not understood]
  • Next by Date: Re: Build mysteriously excludes G3s [Solved, but not understood]
  • Previous by thread: Re: Build mysteriously excludes G3s [Solved, but not understood]
  • Next by thread: Re: Build mysteriously excludes G3s [Solved, but not understood]
  • Index(es):
    • Date
    • Thread