This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ronaldoussoren
Recipients loewis, ronaldoussoren
Date 2008-10-08.06:02:12
SpamBayes Score 2.7062463e-11
Marked as misclassified No
Message-id <>
In-reply-to <>
On 7 Oct, 2008, at 22:13, Martin v. Löwis wrote:

> Martin v. Löwis <> added the comment:
>> Somewhere along the way the calculation of the architecture string  
>> got
>> messed up, resulting in the current situation. That is, the current
>> situation is not as designed by the original author of the universal
>> binary support code.
> Ok, what *is* the desired way of naming architectures on that system?
> Is that documented somewhere?

It is not documented anywhere but in the code, but this is the  
intended behaviour:

* A single architecture build (what you would build on any other unix  
   uses the architecture string of the architecture
   it was build for (that is, "i386", "ppc", "x86_64" or "ppc64")

* A 32-bit universal build uses "fat" as the architecture string,  
regardless of the
    architecture of the machine we're running on.
    As an exception: OS X 10.3.9 machines are treated as if we're on a  
    architecture build because the compiler on that platform doesn't  
    building fat binaries.

* A 4-way universal build (that is, including all architectures  
supported by
    OSX) uses "universal" as the architecture string.

We (Bob Ippolitto and I) had some discussion about the architecture  
strings when
we were working on support for universal binaries and rejected my  
initial suggestion
of using "i386,ppc" instead of "fat" because that would be unwieldy.

Date User Action Args
2008-10-08 06:02:15ronaldoussorensetrecipients: + ronaldoussoren, loewis
2008-10-08 06:02:14ronaldoussorenlinkissue4064 messages
2008-10-08 06:02:12ronaldoussorencreate