[issue20342] Endianness not detected correctly due to AC_RUN_IFELSE macros

Gregory P. Smith added the comment: I'll leave it open, nothing about this should be ppc64 vs ppc64el specific. Our cross compilation story has historically been not great. Building for a target of one endianness from a build host of other endianness... sounds like exactly one of many

[issue20342] Endianness not detected correctly due to AC_RUN_IFELSE macros

Yury V. Zaytsev added the comment: Well, the machine that I had the problem on does no longer exist and I'm not sure whether this is a generic POWER issue. The problem was that I had to cross-compile Python on one generation of POWER machines for another POWER chip using its own special

[issue20342] Endianness not detected correctly due to AC_RUN_IFELSE macros

Gregory P. Smith added the comment: any idea if this is still relevant? -- components: +Cross-Build nosy: +Alex.Willmer, gregory.p.smith ___ Python tracker ___

[issue20342] Endianness not detected correctly due to AC_RUN_IFELSE macros

Yury V. Zaytsev added the comment: I've re-named the issue to reflect the problem. One possible solution that I can see is to use AC_C_BIGENDIAN macro, either exclusively, or only when cross-compiling. In the latest autoconf sources, this macro seems to try to detect the endianness from

[issue20342] Endianness not detected correctly due to AC_RUN_IFELSE macros

STINNER Victor added the comment: doko One possible solution that I can see is to use AC_C_BIGENDIAN macro, either exclusively, or only when cross-compiling. This is wrong. The macro is not used to check the endian but to check the IEEE 754 implementation. The check is important to decide if