from /var/tmp/portage/sci-libs/xkaapi-3.0.3/work/xkaapi-3.0.3/api/kaapixx/ka_error.cpp:48: /var/tmp/portage/sci-libs/xkaapi-3.0.3/work/xkaapi-3.0.3/api/kaapixx/kaapi++.h: In static member function ‘static const kaapi_format_t* ka::WrapperFormat<T>::get_c_format()’: /var/tmp/portage/sci-libs/xkaapi-3.0.3/work/xkaapi-3.0.3/api/kaapixx/kaapi++.h:279:27: internal compiler error: Segmentation fault return format.Format::get_c_format(); ^~~~~~~~~~~~ Please submit a full bug report, ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-systemd_libressl_20171120-180901 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.2.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python3.6 (fallback) [3] python2.7 (fallback) Available Ruby profiles: [1] ruby22 (with Rubygems) * emerge -qpv sci-libs/xkaapi [ebuild N ] sci-libs/xkaapi-3.0.3 USE="cxx fortran openmp -static-libs"
Created attachment 506364 [details] emerge-info.txt
Created attachment 506366 [details] emerge-history.txt
Created attachment 506368 [details] environment
Created attachment 506370 [details] etc.portage.tbz2
Created attachment 506372 [details] logs.tbz2
Created attachment 506374 [details] sci-libs:xkaapi-3.0.3:20171124-113145.log
Created attachment 506376 [details] temp.tbz2
ICE sounds like compiler problem. However, since this is old version of GCC I don't think there's a point in reassigning it now. Let's see if it happens with newer versions.
