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 cdavid
Recipients cdavid
Date 2008-12-23.03:59:54
SpamBayes Score 0.008887308
Marked as misclassified No
Message-id <1230004796.26.0.433339643882.issue4728@psf.upfronthosting.co.za>
In-reply-to
Content
I had some problems with python and universal builds related to the
WORDS_BIGENDIAN macro. Because universal builds are built in one pass
(one configure), the AC_C_ENDIAN cannot be used reliably. Example:

int main()
{
#ifdef WORDS_BIGENDIAN
    printf("Big endian macro defined\n");
#else
    printf("No big endian macro defined\n");
#endif

    return 0;
}

If I build this against python 2.5, it prints no big endian macro (I
have an intel CPU), as expected. But with python 2.6.0 (official binary
from python.org), I get Big endian macro defined.
History
Date User Action Args
2008-12-23 03:59:56cdavidsetrecipients: + cdavid
2008-12-23 03:59:56cdavidsetmessageid: <1230004796.26.0.433339643882.issue4728@psf.upfronthosting.co.za>
2008-12-23 03:59:55cdavidlinkissue4728 messages
2008-12-23 03:59:54cdavidcreate