too long lines were shrinked: x86_64-pc-linux-gnu-gcc -E -MMD -MP -MT multiboot.o -MF ./multiboot.d -c -o - /var/tmp/portage/app-emulation/qemu-6.1.0-r2/work/qemu-6.1.0/pc-bios/optionrom/multiboot.S | x86_64-pc-linux-gnu-as -32 -o multiboot.o x86_64-pc-linux-gnu-gcc -E -MMD -MP -MT linuxboot.o -MF ./linuxboot.d -c -o - /var/tmp/portage/app-emulation/qemu-6.1.0-r2/work/qemu-6.1.0/pc-bios/optionrom/linuxboot.S | x86_64-pc-linux-gnu-as -32 -o linuxboot.o x86_64-pc-linux-gnu-gcc -MMD -MP -MT linuxboot_dma.o -MF ./linuxboot_dma.d -O2 -g -march=i486 -Wall -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -Wold-style-declaration -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qua x86_64-pc-linux-gnu-gcc -E -MMD -MP -MT kvmvapic.o -MF ./kvmvapic.d -c -o - /var/tmp/portage/app-emulation/qemu-6.1.0-r2/work/qemu-6.1.0/pc-bios/optionrom/kvmvapic.S | x86_64-pc-linux-gnu-as -32 -o kvmvapic.o cc1: error: ‘-fcf-protection’ is not compatible with this target make[1]: *** [Makefile:53: linuxboot_dma.o] Error 1 make[1]: Leaving directory '/var/tmp/portage/app-emulation/qemu-6.1.0-r2/work/qemu-6.1.0/softmmu-build/pc-bios/optionrom' make: *** [Makefile:191: pc-bios/optionrom/all] Error 2 make: *** Waiting for unfinished jobs.... ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_systemd-j4-20211208-000031 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-11.2.1 * Python 3.9.9 php cli: HEAD of ::gentoo commit 671771614f120699b3e41ae8af862df2d4c02b53 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Wed Dec 8 01:34:55 2021 +0000 2021-12-08 01:34:54 UTC emerge -qpvO app-emulation/qemu [ebuild N ] app-emulation/qemu-6.1.0-r2 USE="aio bzip2 caps curl doc fdt filecaps jpeg nls oss pin-upstream-blobs png seccomp slirp snappy udev vhost-net vnc xattr zstd -accessibility -alsa -bpf -capstone -debug -fuse -glusterfs -gnutls -gtk -infiniband -io-uring -iscsi -jack -jemalloc -lzo -multipath -ncurses -nfs -numa -opengl -plugins -pulseaudio -python -rbd -sasl -sdl -sdl-image (-selinux) -smartcard -spice -ssh -static -static-user -systemtap -test -usb -usbredir -vde -vhost-user-fs -virgl -virtfs -vte -xen -xfs" PYTHON_TARGETS="python3_9 -python3_8 -python3_10" QEMU_SOFTMMU_TARGETS="i386 x86_64 -aarch64 -alpha -arm -avr -cris -hppa -m68k -microblaze -microblazeel -mips -mips64 -mips64el -mipsel -nios2 -or1k -ppc -ppc64 -riscv32 -riscv64 -rx -s390x -sh4 -sh4eb -sparc -sparc64 -tricore -xtensa -xtensaeb" QEMU_USER_TARGETS="i386 x86_64 -aarch64 -aarch64_be -alpha -arm -armeb -cris -hexagon -hppa -m68k -microblaze -microblazeel -mips -mips64 -mips64el -mipsel -mipsn32 -mipsn32el -nios2 -or1k -ppc -ppc64 -ppc64abi32 -ppc64le -riscv32 -riscv64 -s390x -sh4 -sh4eb -sparc -sparc32plus -sparc64 -xtensa -xtensaeb"
Created attachment 757685 [details] emerge-info.txt
Created attachment 757686 [details] app-emulation:qemu-6.1.0-r2:20211208-020013.log.bz2
Created attachment 757687 [details] emerge-history.txt
Created attachment 757688 [details] environment
Created attachment 757689 [details] etc.portage.tar.bz2
Hit this too, but asked toralf to rebuild GCC first to see if it helps.
(In reply to Sam James from comment #6) > Hit this too, but asked toralf to rebuild GCC first to see if it helps. needs more work, on it
Created attachment 757729 [details] emerge--info_gcc emerge --info gcc
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/gcc-patches.git/commit/?id=34cc4c2a7c835b5787ab1cd5d22ed72e3be2132b commit 34cc4c2a7c835b5787ab1cd5d22ed72e3be2132b Author: Sam James <sam@gentoo.org> AuthorDate: 2021-12-09 02:40:05 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-12-18 22:00:28 +0000 11.3.0: update CET patch to disable on 32-bit / missing CMOV, deux Bug: https://bugs.gentoo.org/828546 Bug: https://bugs.gentoo.org/828549 Bug: https://bugs.gentoo.org/828081 Bug: https://bugs.gentoo.org/827880 Bug: https://bugs.gentoo.org/827905 Bug: https://bugs.gentoo.org/777117 Signed-off-by: Sam James <sam@gentoo.org> 11.3.0/gentoo/26_all_enable-cet.patch | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=58c2f6c4fb228ddc7b17698673fbf80400a452e9 commit 58c2f6c4fb228ddc7b17698673fbf80400a452e9 Author: Sam James <sam@gentoo.org> AuthorDate: 2021-12-18 22:01:34 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-12-18 22:03:06 +0000 sys-devel/gcc: switch patchset version for 11.2.1_p20211127 for CET fixes If hitting related issues before this, please try emerge -v1 sys-devel/gcc. Doesn't seem to have affected many people at all (just tinderbox?) so not worth a revbump (at this point, anyway). Also includes fix for i486 CET (unrelated). Closes: https://bugs.gentoo.org/828546 Closes: https://bugs.gentoo.org/828549 Closes: https://bugs.gentoo.org/828081 Closes: https://bugs.gentoo.org/827880 Closes: https://bugs.gentoo.org/827905 Closes: https://bugs.gentoo.org/777117 Signed-off-by: Sam James <sam@gentoo.org> sys-devel/gcc/Manifest | 2 +- sys-devel/gcc/gcc-11.2.1_p20211127.ebuild | 3 +-- 2 files changed, 2 insertions(+), 3 deletions(-)
@jaak, can you re-emerge gcc with emerge -1 sys-devel/gcc and let me know if it's OK now (after emerge --syncing)? may need to wait a bit first
(In reply to Sam James from comment #11) > @jaak, can you re-emerge gcc with emerge -1 sys-devel/gcc and let me know if > it's OK now (after emerge --syncing)? may need to wait a bit first I wish I could, but fetching https://dev.gentoo.org/~sam/distfiles/sys-devel/gcc/gcc-11.3.0-patches-2.tar.bz2 gives me: !!! Fetched file: gcc-11.3.0-patches-2.tar.bz2 VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 14029 !!! Expected: 15346
The fetch error has disappeared and I can confirm this issue is now fixed. Thank you! :)
(In reply to Jaak Ristioja from comment #13) > The fetch error has disappeared and I can confirm this issue is now fixed. > Thank you! :) Fantastic! Thank you for testing!
