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 lemburg
Recipients lemburg, loewis, ronaldoussoren, trentm
Date 2008-10-06.22:47:13
SpamBayes Score 7.42716e-05
Marked as misclassified No
Message-id <48EA9570.2010902@egenix.com>
In-reply-to <1223332030.39.0.313145041612.issue4060@psf.upfronthosting.co.za>
Content
BTW: Does this simplified approach really work for Python on Mac OS X:

On 2008-10-07 00:27, Trent Mick wrote:
>>     The block below does compile-time checking for endianness on
> platforms 	 
>>     that use GCC and therefore allows compiling fat binaries on OSX by
> using 	 
>>     '-arch ppc -arch i386' as the compile flags. The phrasing was
> choosen 	 
>>     such that the configure-result is used on systems that don't use
> GCC. 	 

For most other tools that require configure tests regarding endianness
on Mac OS X, the process of building a universal binary goes something
like this:

http://developer.apple.com/opensource/buildingopensourceuniversal.html

ie. you run the whole process twice and then combine the results using
lipo.
History
Date User Action Args
2008-10-06 22:47:14lemburgsetrecipients: + lemburg, loewis, ronaldoussoren, trentm
2008-10-06 22:47:14lemburglinkissue4060 messages
2008-10-06 22:47:13lemburgcreate