Upstream patch [1] fixes the compilation. Strangely this does only occur on my Haswell system, my other two Skylake systems do not show the segfault. [1] https://github.com/python/cpython/commit/0b91f8a668201fc58fa732b8acc496caedfdbae0
confirm it on Haswell system. there is no this bug on AMD Phenom_II and Turion_II
2.7.15 builds fine
Also confirm this bug on Haskell.
Breaks down on Threadripper too.
Segfault in generate-posix-vars also occurs on Kentsfield (Intel Core 2 Quad Q6600) using GCC 8.1.0. I can work around it by setting: CC=x86_64-pc-linux-gnu-gcc-7.3.0 CXX=x86_64-pc-linux-gnu-g++-7.3.0 in /etc/portage/env/dev-lang/python-2.7.14. Yes, I am still using a processor that's more than 11 years old.
Fedora ended up using https://mail.python.org/pipermail/python-dev/2018-January/152011.html I think
(In reply to Pacho Ramos from comment #6) > Fedora ended up using > https://mail.python.org/pipermail/python-dev/2018-January/152011.html I think I'm pretty sure that was what landed in 2.7.15.
(In reply to Matt Whitlock from comment #5) > ... Intel Core 2 ... Still love my rock-solid ThinkPad T60 from 2007 :-) @ Python Gentoo Team: In-between, dev-lang/python-2.7.15:2.7 has been stabilized on all arches. So this bug could be considered as 'RESOLVED FIXED' ?