Created attachment 903337 [details] emerge --info dev-lang/python This seems to be an old bug with dev-build/autoconf-archive, at least, according to this bug report on the python github: https://github.com/python/cpython/issues/89640 The symptom is that the emerge fails, and the build log ends with: checking whether float word ordering is bigendian... unknown configure: error: Unknown float word ordering. You need to manually preset ax_cv_c_float_words_bigendian=no (or yes) according to your system. Changing from clang to gcc made no difference.
Created attachment 903338 [details] dev-lang/python-3.12.6 build.log
Probably should say I have dev-build/autoconf-archive-2023.02.20 and dev-build/autoconf-2.71-r7.
Just noticed that autoconf is slotted: the other slot is dev-build/autoconf-2.13-r8, if that is relevant.
Created attachment 903339 [details] config.log zipped
Perhaps try adding? https://github.com/autoconf-archive/autoconf-archive/pull/279/commits/23be7ccd7f306fbc73b3f33e2f5ead716d120eef
(In reply to Joakim Tjernlund from comment #5) > Perhaps try adding? > https://github.com/autoconf-archive/autoconf-archive/pull/279/commits/ > 23be7ccd7f306fbc73b3f33e2f5ead716d120eef I've been away, so I've only just had time to try this. That patch seems to be for something other than Python 3.12, as the target file is m4/ax_c_float_words_bigendian.m4, and there's no such file in dev-lang/python-3.12.6_p4. The patch will apply to "aclocal.m4", and as the patch is pretty specific, I guess that's the intended target. To be clear, I could see the ebuild output: Applying user patches from /etc/portage/patches ... * Applying 0014-ax_c_float_words_bigendian.patch ... [ ok ] * User patches applied. HOWEVER, it had no effect on the success of the ebuild. It still results in exactly the same failure and build.log as before. I tried it with both gcc-lto and clang-lto. Both fail. I took the hint from the patch and tried without lto. It compiles happily straight clang. I expect it does with gcc without lto, but didn't try that.
