compile options: '-Inumpy/core/src/private -Inumpy/core/src -Inumpy/core -Inumpy/core/src/npymath -Inumpy/core/src/multiarray -Inumpy/core/src/umath -Inumpy/core/src/npysort -I/usr/include/python2.7 -c' x86_64-pc-linux-gnu-gcc: _configtest.c _configtest.c:1:10: fatal error: sys/endian.h: No such file or directory #include <sys/endian.h> ^~~~~~~~~~~~~~ compilation terminated. ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-gnome_libressl_20190127-101048 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-8.2.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) emerge -qpvO dev-python/numpy [ebuild N ] dev-python/numpy-1.15.4 USE="-doc -lapack -test" PYTHON_TARGETS="python2_7 python3_6 -python3_4 -python3_5 -python3_7"
Created attachment 563092 [details] emerge-info.txt
Created attachment 563094 [details] dev-python:numpy-1.15.4:20190128-013944.log
Created attachment 563096 [details] emerge-history.txt
Created attachment 563098 [details] environment
Created attachment 563100 [details] etc.portage.tbz2
Created attachment 563102 [details] temp.tbz2
numpy.distutils is known to be a... flaky... build system. They have since moved to meson in order to fix that general flakiness, so build issues related to configtests performed by the old build system can't possibly exist anymore (new issues are always a possibility :D) I figure this bug report is no longer applicable.
