System: Vagrant 2.3.4 generic_centos7 UNSTABLE prefix Linux centos7.localdomain 3.10.0-1160.88.1.el7.x86_64 #1 SMP Tue Mar 7 15:41:52 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Steps to reproduce the bug: Run the bootstrap-prefix.sh in mode UNSTABLE (default STABLE) Error message: Hmmmm, I was already afraid of this to happen. Running /home/vagrant/gentoo-prefix/bin/bash ./bootstrap-prefix.sh "/home/vagrant/gentoo-prefix" stage3 somewhere failed :( Details might be found in the build log: /home/vagrant/gentoo-prefix/var/tmp/portage/sys-devel/gcc-13.1.0-r1/temp/build.log I have no clue, really. Please find friendly folks in #gentoo-prefix on irc.gentoo.org, gentoo-alt@lists.gentoo.org mailing list, or file a bug at bugs.gentoo.org under Gentoo/Alt, Prefix Support. This is most inconvenient, and it crushed my ego. Sorry, I give up. Should you want to give it a try, there is /home/vagrant/gentoo-prefix/stage3.log Extra info: https://github.com/APN-Pucky/gentoo-prefix-tester/actions/runs/4858205137
Created attachment 861037 [details] build_UNSTABLE_generic_centos7_20230502062136.log.xz
Linux ubuntu 5.19.0-1012-generic #13~22.04.1-Ubuntu SMP Thu Jan 12 15:34:31 UTC 2023 riscv64 riscv64 riscv64 GNU/Linux
Created attachment 861661 [details] full_STABLE_Linux_ubuntu_5.19.0-1012-generic__13~22.04.1-Ubuntu_SMP_Thu_Jan_12_15_34_31_UTC_2023_riscv64_riscv64_riscv64_GNU_Linux_20230513144951.log.xz
Created attachment 861662 [details] build_STABLE_Linux_ubuntu_5.19.0-1012-generic__13~22.04.1-Ubuntu_SMP_Thu_Jan_12_15_34_31_UTC_2023_riscv64_riscv64_riscv64_GNU_Linux_20230513144951.log.xz
riscv report here is stage2, whereas centos was stage3. In file included from /home/ubuntu/gentoo-prefix-tester/gentoo-prefix/tmp/var/tmp/portage/sys-devel/gcc-13.1.0-r1/work/gcc-13.1.0/libgcc/../gcc/tsystem.h:87, from /home/ubuntu/gentoo-prefix-tester/gentoo-prefix/tmp/var/tmp/portage/sys-devel/gcc-13.1.0-r1/work/gcc-13.1.0/libgcc/libgcc2.c:27: /usr/include/stdio.h:27:10: fatal error: bits/libc-header-start.h: No such file or directory 27 | #include <bits/libc-header-start.h> | compilation terminated. make[2]: *** [Makefile:501: _ashrdi3.o] Error 1 make[2]: Leaving directory '/home/ubuntu/gentoo-prefix-tester/gentoo-prefix/tmp/var/tmp/portage/sys-devel/gcc-13.1.0-r1/work/build/riscv64-pc-linux-gnu/libgcc'
System: Vagrant 2.2.19 perk_debian-11-genericcloud-arm64 STABLE prefix Steps to reproduce the bug: Run the bootstrap-prefix.sh in mode STABLE (default STABLE) Error message: Hmmmm, I was already afraid of this to happen. Running /home/vagrant/gentoo-prefix/bin/bash ./bootstrap-prefix.sh "/home/vagrant/gentoo-prefix" stage3 somewhere failed :( Details might be found in the build log: /home/vagrant/gentoo-prefix/var/tmp/portage/sys-devel/gcc-13.1.0-r1/temp/build.log I have no clue, really. Please find friendly folks in #gentoo-prefix on irc.gentoo.org, gentoo-alt@lists.gentoo.org mailing list, or file a bug at bugs.gentoo.org under Gentoo/Alt, Prefix Support. This is most inconvenient, and it crushed my ego. Sorry, I give up. Should you want to give it a try, there is /home/vagrant/gentoo-prefix/stage3.log Extra info: LOCALRUN
Created attachment 861924 [details] build_STABLE_perk_debian-11-genericcloud-arm64_20230514144439.log.xz
Full log was too big: https://gist.githubusercontent.com/APN-Pucky/b4d9fc48d5e1f6c3f20dc88013dbc9aa/raw/e9aa5dde6902968406cf328f8913d59d7d5807f0/full_STABLE_perk_debian-11-genericcloud-arm64_20230514144439.log {standard input}: Assembler messages: {standard input}:1466154: Warning: end of file not at end of a line; newline inserted xg++: fatal error: Killed signal terminated program cc1plus I presume that is another OOM of qemu.
(In reply to APN-Pucky from comment #8) > Full log was too big: > https://gist.githubusercontent.com/APN-Pucky/ > b4d9fc48d5e1f6c3f20dc88013dbc9aa/raw/ > e9aa5dde6902968406cf328f8913d59d7d5807f0/full_STABLE_perk_debian-11- > genericcloud-arm64_20230514144439.log > > {standard input}: Assembler messages: > {standard input}:1466154: Warning: end of file not at end of a line; newline > inserted > xg++: fatal error: Killed signal terminated program cc1plus > > I presume that is another OOM of qemu. We can't do much then. Use GCC 13 (which will be stabled soon). :(
