14 Apr
2009
14 Apr
'09
6:30 p.m.
On Tue, Apr 14, 2009 at 5:14 PM, Antoine Pitrou
If this approach is sane, could it be adopted for all other instances of endianness detection in the py3k code base?
I think everything else is fine: float endianness detection (for marshal, pickle, struct) is done at runtime. Integer endianness detection goes via AC_C_BIGENDIAN, which understands universal builds---but only for autoconf >= 2.62.
Has anyone tested a recent py3k using universal builds? Do all tests pass?
Do you know the right way to create a universal build? If so, I'm in a position to test on 32-bit PPC, 32-bit Intel and 64-bit Intel. Mark