too long lines were shrinked: true "AR_FLAGS=rc" "CC_FOR_BUILD=x86_64-pc-linux-gnu-gcc" "CC_FOR_TARGET=/var/tmp/portage/sys-devel/gcc-13.1.1_p20230527/work/build/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-13.1.1_p20230527/work/build/./gcc/" "CFLAGS=-g -pipe -march=native -fno-diagnostics-color -O2 -m32" "CXXFLAGS=-g -pipe -mar make "DESTDIR=" "RPATH_ENVVAR=LD_LIBRARY_PATH" "TARGET_SUBDIR=x86_64-pc-linux-gnu" "bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/13" "datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/13" "exec_prefix=/usr" "includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/13/include" "datarootdir=/usr/share" "docdir=/usr/share make[3]: Entering directory '/var/tmp/portage/sys-devel/gcc-13.1.1_p20230527/work/build' rm -f stage_current make[3]: Leaving directory '/var/tmp/portage/sys-devel/gcc-13.1.1_p20230527/work/build' Comparing stages 2 and 3 Bootstrap comparison failure! x86_64-pc-linux-gnu/32/libstdc++-v3/libsupc++/eh_globals.o differs x86_64-pc-linux-gnu/32/libstdc++-v3/src/.libs/compatibility-thread-c++0x.o differs ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 23.0_desktop_systemd-20230624-014416 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-12 * clang/llvm (if any): Python 3.11.3 php cli (if any): HEAD of ::gentoo commit b346c2de29d59c9494261d6ce77ad66af2129bf6 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Sat Jun 24 01:31:58 2023 +0000 2023-06-24 01:31:57 UTC emerge -qpvO sys-devel/gcc [ebuild NS ] sys-devel/gcc-13.1.1_p20230527 [12.2.1_p20230428-r1] USE="(cxx) (default-stack-clash-protection*) (default-znow*) fortran jit* (multilib) nptl (pie) sanitize ssp zstd* -ada (-cet) (-custom-cflags) -d -debug -doc (-fixed-point) -go -graphite -hardened (-ieee-long-double) (-libssp) -lto -modula2% -nls* -objc -objc++ -objc-gc -openmp* (-pch) -pgo -systemtap -test (-valgrind) -vanilla -vtv"
Created attachment 864512 [details] emerge-info.txt
Created attachment 864513 [details] emerge-history.txt
Created attachment 864514 [details] environment
Created attachment 864515 [details] etc.portage.tar.xz
Created attachment 864516 [details] gcc-build-logs.tar.xz
Created attachment 864517 [details] logs.tar.xz
Created attachment 864518 [details] sys-devel:gcc-13.1.1_p20230527:20230624-015706.log.xz
Created attachment 864519 [details] temp.tar.xz
x86_64-pc-linux-gnu/32/libstdc++-v3/libsupc++/eh_globals.o differs x86_64-pc-linux-gnu/32/libstdc++-v3/src/.libs/compatibility-thread-c++0x.o differs x86_64-pc-linux-gnu/32/libstdc++-v3/src/c++11/mutex.o differs toralf, if you check the build dir, you should have two copies of each of those - could you upload a tarball (or two tarballs, whatever) with a folder for the stage2 copies, and another folder for the stage3 copies?
(In reply to Sam James from comment #9) > toralf, if you check the build dir, you should have two copies of each of > those - could you upload a tarball (or two tarballs, whatever) with a folder > for the stage2 copies, and another folder for the stage3 copies? Unfortunately the build dir is a tmpfs - and a reproduce attempt was unsuccessful. I enhanced the tinderbox logic to keep the portage tmp dir if the first gcc upgrade fails.
http://tinderbox.zwiebeltoralf.de:31560/23.0_systemd-20230822-012504/var/tmp/tb/issues/20230827-022859-sys-devel_gcc-13.2.1_p20230826/ and then files : tinderbox@mr-fox ~ $ ls -lh /home/tinderbox/img/23.0_systemd-20230822-012504/var/tmp/tb/issues/20230827-022859-sys-devel_gcc-13.2.1_p20230826/files/ total 975M -rw-r--r-- 1 root root 55K Aug 27 02:28 emerge-history.txt.xz -rw-r--r-- 1 root root 129K Aug 27 02:29 environment -rw-r--r-- 1 root root 35K Aug 27 02:40 etc.portage.tar.xz -rw-r--r-- 1 root root 282K Aug 27 02:29 gcc-build-logs.tar.xz -rw-r--r-- 1 root root 125K Aug 27 02:29 logs.tar.xz -rw-r--r-- 1 root root 178K Aug 27 02:28 sys-devel:gcc-13.2.1_p20230826:20230826-235747.log.xz -rw-r--r-- 1 root root 209K Aug 27 02:29 temp.tar.xz -rw-r--r-- 1 root root 973M Aug 27 02:40 var-tmp-portage.tar.xz -rw-r--r-- 1 root root 1.2M Aug 27 02:29 var-tmp-portage.txt.xz
Created attachment 894438 [details] Build log
Comment on attachment 894438 [details] Build log Argh, attached to wrong bug report (although probable dup report). Sry.
(In reply to Toralf Förster from comment #11) > http://tinderbox.zwiebeltoralf.de:31560/23.0_systemd-20230822-012504/var/tmp/ > tb/issues/20230827-022859-sys-devel_gcc-13.2.1_p20230826/ and then files : > I missed this but it's long-gone.
