]> code.ossystems Code Review - openembedded-core.git/commit
python3: don't use runtime checks to identify float endianism
authorRoss Burton <ross.burton@intel.com>
Wed, 5 Sep 2018 10:48:53 +0000 (11:48 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Fri, 7 Sep 2018 16:48:27 +0000 (17:48 +0100)
commit1781b87ae0765c1867da2fa8c56bf988b4e84405
tree8c63e25a50b5ce93be01f639c91b25171dbcd337
parent561577add4b935d9bfb7b7dd6abdc3e26c1d9143
python3: don't use runtime checks to identify float endianism

Python uses AC_RUN_IFELSE to determine the byte order for floats and doubles,
and falls back onto "I don't know" if it can't run code.  This results in
crippled floating point numbers in Python, and the regression tests fail.

Instead of running code, take a macro from autoconf-archive which compiles C
with a special double in which has an ASCII representation, and then greps the
binary to identify the format.

Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/recipes-devtools/python/python3/float-endian.patch [new file with mode: 0644]
meta/recipes-devtools/python/python3_3.5.5.bb