Hi, I tried to switch to new profile 23 (from default/linux/amd64/17.1/no-multilib, I use OpenRC). On step 9 (news https://gitweb.gentoo.org/data/gentoo-news.git/tree/2024-03-22-new-23-profiles/2024-03-22-new-23-profiles.en.txt), sys-devel/binutils compilation is fine. But then gcc fails: make[4]: Entering directory '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/libitm' true DO=install multi-do # make /bin/mkdir -p '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64' /usr/lib/portage/python3.11/ebuild-helpers/xattr/install -c -m 644 libitm.spec '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64' /bin/mkdir -p '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64' /bin/sh ./libtool --mode=install /usr/lib/portage/python3.11/ebuild-helpers/xattr/install -c libitm.la '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64' libtool: install: /usr/lib/portage/python3.11/ebuild-helpers/xattr/install -c .libs/libitm.so.1.0.0 /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64/libitm.so.1.0.0 libtool: install: (cd /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64 && { ln -s -f libitm.so.1.0.0 libitm.so.1 || { rm -f libitm.so.1 && ln -s libitm.so.1.0.0 libitm.so.1; }; }) libtool: install: (cd /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64 && { ln -s -f libitm.so.1.0.0 libitm.so || { rm -f libitm.so && ln -s libitm.so.1.0.0 libitm.so; }; }) libtool: install: /usr/lib/portage/python3.11/ebuild-helpers/xattr/install -c .libs/libitm.lai /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64/libitm.la libtool: install: /usr/lib/portage/python3.11/ebuild-helpers/xattr/install -c .libs/libitm.a /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64/libitm.a libtool: install: chmod 644 /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64/libitm.a libtool: install: /usr/x86_64-pc-linux-gnu/bin/ranlib /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64/libitm.a libtool: install: warning: remember to run `libtool --finish /usr/lib/../lib64' /bin/mkdir -p '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/share/gcc-data/x86_64-pc-linux-gnu/13/info' /usr/lib/portage/python3.11/ebuild-helpers/xattr/install -c -m 644 ./libitm.info '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/share/gcc-data/x86_64-pc-linux-gnu/13/info' install-info --info-dir='/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/share/gcc-data/x86_64-pc-linux-gnu/13/info' '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/share/gcc-data/x86_64-pc-linux-gnu/13/info/libitm.info' make[4]: Leaving directory '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/libitm' make[3]: Leaving directory '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/libitm' make[2]: Leaving directory '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/libitm' make[2]: Entering directory '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/libatomic' Makefile:910: warning: overriding recipe for target 'all-multi' Makefile:901: warning: ignoring old recipe for target 'all-multi' make[2]: Leaving directory '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/libatomic' make[2]: Entering directory '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/libatomic' Making install in testsuite make[3]: Entering directory '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/libatomic/testsuite' make[4]: Entering directory '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/libatomic/testsuite' make[4]: Nothing to be done for 'install-exec-am'. make[4]: Nothing to be done for 'install-data-am'. make[4]: Leaving directory '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/libatomic/testsuite' make[3]: Leaving directory '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/libatomic/testsuite' make[3]: Entering directory '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/libatomic' Makefile:910: warning: overriding recipe for target 'all-multi' Makefile:901: warning: ignoring old recipe for target 'all-multi' make[3]: Leaving directory '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/libatomic' make[3]: Entering directory '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/libatomic' true DO=all multi-do # make make[4]: Entering directory '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/libatomic' Makefile:910: warning: overriding recipe for target 'all-multi' Makefile:901: warning: ignoring old recipe for target 'all-multi' make[4]: Leaving directory '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/libatomic' make[4]: Entering directory '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/libatomic' true DO=install multi-do # make /bin/mkdir -p '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64' /bin/sh ./libtool --mode=install /usr/lib/portage/python3.11/ebuild-helpers/xattr/install -c libatomic.la '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64' libtool: install: /usr/lib/portage/python3.11/ebuild-helpers/xattr/install -c .libs/libatomic.so.1.2.0 /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64/libatomic.so.1.2.0 libtool: install: (cd /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64 && { ln -s -f libatomic.so.1.2.0 libatomic.so.1 || { rm -f libatomic.so.1 && ln -s libatomic.so.1.2.0 libatomic.so.1; }; }) libtool: install: (cd /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64 && { ln -s -f libatomic.so.1.2.0 libatomic.so || { rm -f libatomic.so && ln -s libatomic.so.1.2.0 libatomic.so; }; }) libtool: install: /usr/lib/portage/python3.11/ebuild-helpers/xattr/install -c .libs/libatomic.lai /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64/libatomic.la libtool: install: /usr/lib/portage/python3.11/ebuild-helpers/xattr/install -c .libs/libatomic.a /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64/libatomic.a libtool: install: chmod 644 /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64/libatomic.a libtool: install: /usr/x86_64-pc-linux-gnu/bin/ranlib /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64/libatomic.a libtool: install: warning: remember to run `libtool --finish /usr/lib/../lib64' make[4]: Nothing to be done for 'install-data-am'. make[4]: Leaving directory '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/libatomic' make[3]: Leaving directory '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/libatomic' make[2]: Leaving directory '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/libatomic' make[1]: Leaving directory '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build' [31;01m*[0m ERROR: sys-devel/gcc-13.2.1_p20240210::gentoo failed (install phase): [31;01m*[0m (no error message) [31;01m*[0m [31;01m*[0m Call stack: [31;01m*[0m ebuild.sh, line 136: Called src_install [31;01m*[0m environment, line 3407: Called toolchain_src_install [31;01m*[0m environment, line 4874: Called gcc_movelibs [31;01m*[0m environment, line 1948: Called die [31;01m*[0m The specific snippet of code: [31;01m*[0m find -depth "${ED}" -type d -exec rmdir {} + &> /dev/null || die [31;01m*[0m [31;01m*[0m If you need support, post the output of `emerge --info '=sys-devel/gcc-13.2.1_p20240210::gentoo'`, [31;01m*[0m the complete build log and the output of `emerge -pqv '=sys-devel/gcc-13.2.1_p20240210::gentoo'`. Do not see any error or strange things in logs, excepts: “Nothing to be done for 'install-data-am'.” I disabled ccache, remove changes that I wanted to do in USE at the same time. But it is still fail with the same message. I tried to look at that but did not see similart reports in that context. Any idea? Reproducible: Always Steps to Reproduce: 1. emerge --ask --oneshot --verbose sys-devel/gcc
Created attachment 888727 [details] gcc-build-logs.tar.xz
Hi, this one should be okay now if you emerge --sync.
Created attachment 888728 [details] build.log.xz
(In reply to Sam James from comment #2) > Hi, this one should be okay now if you emerge --sync. Hi Sam, I saw that you make some commits on gcc-*. But on this version, only https://gitweb.gentoo.org/repo/gentoo.git/commit/sys-devel/gcc/gcc-13.2.1_p20240210.ebuild?id=1d93a491096f1cc0234fcf44458bfec142c213bb It did not look revelant for me. But ok, I will try. Thanks for the very very quick anwser.
(In reply to Sébastien P. from comment #4) The fixes are in the eclass (toolchain.eclass) so it should be OK.
After syncing, gcc merge is fine. Thank you @Sam.
