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 eric.araujo, jlindenbaum, ned.deily, ronaldoussoren, santoso.wijaya, tarek
Date 2011-03-22.14:03:04
SpamBayes Score 8.881784e-13
Marked as misclassified No
Message-id <1300802588.48.0.808052869426.issue11623@psf.upfronthosting.co.za>
In-reply-to
Content
I haven't put much thought in a solution yet, but at this point I'd go for three changes:

1) Give a clear warning when python was configured for i386/ppc 
   and Xcode4 is installed (instead of giving a vague compiler crash 
   due to crapping out on ppc code)

2) Add an option that forces distutils to compile for i386 only

   This should not be the default because that would result in broken
   packages for users that want to redistribute binaries to ppc 
   machines.

3) The i386/ppc build should use the system headers instead of the
   10.4u SDK (change in configure.in), with a fallback to the 10.4u
   SDK when building extensions on a 10.4 machine (because the 
   "-isysroot /" cannot build universal binaries on all such machines)

BTW. distutils does not have code to work around OSX issues, it has code
to make use of OSX specific compilation features (such as having universal binaries and SDKs). ;-) ;-)
History
Date User Action Args
2011-03-22 14:03:08ronaldoussorensetrecipients: + ronaldoussoren, tarek, ned.deily, eric.araujo, santoso.wijaya, jlindenbaum
2011-03-22 14:03:08ronaldoussorensetmessageid: <1300802588.48.0.808052869426.issue11623@psf.upfronthosting.co.za>
2011-03-22 14:03:05ronaldoussorenlinkissue11623 messages
2011-03-22 14:03:04ronaldoussorencreate