Marc-Andre Lemburg <[EMAIL PROTECTED]> added the comment: 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. ---------- title: PyUnicode_DecodeUTF16(..., byteorder=0) gets it wrong on Mac OS X/PowerPC -> PyUnicode_DecodeUTF16(..., byteorder=0) gets it wrong on Mac OS X/PowerPC _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4060> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
