Created attachment 901515 [details] build.log On gcc14 or without -fuse-ld=mold build succeeds.
Created attachment 901516 [details] Output of emerge --info dev-build/ninja
Can you run the failing command manually in the build directory under gdb to find where it traps?
Created attachment 901671 [details] gdb coredump
Created attachment 901672 [details] build.log
Created attachment 901768 [details] build.log
Created attachment 901769 [details] gdb coredump
I recompiled it using gcc-14 but it still failed. It never failed before. My gcc-14 and mold are built on gcc-15.
I think you need to figure out which part of your system is miscompiled. I'm using GCC 15 (and mold + lto) on various systems and had no issues. Please also keep in mind that given the flags you mentioned in another bug, it's not always enough to just rebuild _one_ thing with safe flags. It might be that a dependency is contaminated.
It seems that gcc 15 has broken too many things. I don't want to move further because I have reinstalled my system.
I really think it's more about the flags, but it is what it is now.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f6da81d9f85e2223a469e043dc95fd6fc555409f commit f6da81d9f85e2223a469e043dc95fd6fc555409f Author: Sam James <sam@gentoo.org> AuthorDate: 2024-10-28 11:36:23 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-10-28 11:38:18 +0000 sys-devel/mold: workaround linux-6.11 incompatibility Don't write to existing files, instead replace them. This fixes (or works around) an incompatibility with linux-6.11. Bug: https://github.com/rui314/mold/issues/1361 Bug: https://bugs.gentoo.org/938659 Closes: https://bugs.gentoo.org/941070 Thanks-to: Jinghao Jia <jinghao7@illinois.edu> Thanks-to: ernsteiswuerfel <erhard_f@mailbox.org> Signed-off-by: Sam James <sam@gentoo.org> sys-devel/mold/files/mold-2.34.1-linux-6.11.patch | 22 +++++ sys-devel/mold/mold-2.34.1-r1.ebuild | 107 ++++++++++++++++++++++ sys-devel/mold/mold-9999.ebuild | 4 + 3 files changed, 133 insertions(+)
I think your issue was really bug 941070 and it should be fixed/worked around now.