Summary: | sys-devel/gcc-11.3.0 compile fails during prefix bootstrap | ||
---|---|---|---|
Product: | Gentoo/Alt | Reporter: | APN-Pucky <alexander> |
Component: | Prefix Support | Assignee: | Gentoo Prefix <prefix> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=901317 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log
gcc-build-logs stage3.log |
Description
APN-Pucky
2022-09-19 01:04:01 UTC
Created attachment 812602 [details]
build.log
Created attachment 812605 [details]
gcc-build-logs
Retried it and same result. A similar problem was reported on #gentoo-prefix on an old CentOS machine. I am adding warnings/errors only printed to std::out: * Messages for package sys-devel/gcc-11.3.0: * Disabling bootstrapping. ONLY recommended for development. * This is NOT a safe configuration for endusers! * This compiler may not be safe or reliable for production use! * ERROR: sys-devel/gcc-11.3.0::gentoo failed (compile phase): * emake failed * Created attachment 813787 [details]
stage3.log
g++ -isystem /local0/a_neuw01/gentoo/usr/include -B/local0/a_neuw01/gentoo/usr/lib64 -L/local0/a_neuw01/gentoo/usr/lib64 -Wl,--dynamic-linker=/local0/a_neuw01/gentoo/lib64/ld-linux-x86-64.so.2 -pipe -pipe -O2 -fno-exceptions -fno-rtti -include config.h -I/local0/a_neuw01/gentoo/var/tmp/portage/sys-devel/gcc-11.3.0/work/gcc-11.3.0/libcody \ -MMD -MP -MF buffer.d -c -o buffer.o /local0/a_neuw01/gentoo/var/tmp/portage/sys-devel/gcc-11.3.0/work/gcc-11.3.0/libcody/buffer.cc In file included from /local0/a_neuw01/gentoo/tmp/usr/lib/gcc/x86_64-pc-linux-gnu/11.3.0/include/g++-v11/cstdlib:75, from /local0/a_neuw01/gentoo/tmp/usr/lib/gcc/x86_64-pc-linux-gnu/11.3.0/include/g++-v11/ext/string_conversions.h:41, from /local0/a_neuw01/gentoo/tmp/usr/lib/gcc/x86_64-pc-linux-gnu/11.3.0/include/g++-v11/bits/basic_string.h:6608, from /local0/a_neuw01/gentoo/tmp/usr/lib/gcc/x86_64-pc-linux-gnu/11.3.0/include/g++-v11/string:55, from /local0/a_neuw01/gentoo/var/tmp/portage/sys-devel/gcc-11.3.0/work/gcc-11.3.0/libcody/cody.hh:25, from /local0/a_neuw01/gentoo/var/tmp/portage/sys-devel/gcc-11.3.0/work/gcc-11.3.0/libcody/internal.hh:5, from /local0/a_neuw01/gentoo/var/tmp/portage/sys-devel/gcc-11.3.0/work/gcc-11.3.0/libcody/buffer.cc:6: /usr/include/stdlib.h:56:1: error: '__BEGIN_NAMESPACE_STD' does not name a type 56 | __BEGIN_NAMESPACE_STD | ^~~~~~~~~~~~~~~~~~~~~ /usr/include/stdlib.h:62:5: error: 'div_t' does not name a type 62 | } div_t; | ^~~~~ /usr/include/stdlib.h:73:1: error: '__END_NAMESPACE_STD' does not name a type 73 | __END_NAMESPACE_STD | ^~~~~~~~~~~~~~~~~~~ /usr/include/stdlib.h:82:5: error: 'lldiv_t' does not name a type; did you mean 'ldiv_t'? 82 | } lldiv_t; | ^~~~~~~ | ldiv_t /usr/include/stdlib.h:84:1: error: ' The error seems to be the same as here: https://www.mail-archive.com/gcc-bugs@gcc.gnu.org/msg566121.html It seems like Debian GLIBC 2.24-11+deb9u4 (and similar in centos7) is too old for GCC-11, since it works on a recent Gentoo machine. Is there a way to first compile an older GCC to upgrade GLIBC then, maybe? Or should the system compiler first create a recent glibc then GCC(s) instead of the other way round (more bootstrapping?)? *** This bug has been marked as a duplicate of bug 902123 *** |