Created attachment 887520 [details] build.log I have 2 systems which are running Gentoo llvm/musl profile and both fail to compile GCC with the error found in the attached build.log. net-libs/nodejs seems to have a hard-dependency on GCC, even on the LLVM profiles, which is the reason for installing this, but cannot do so.
Please provide emerge --info.
checking for suffix of object files... configure: error: in `/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-gentoo-linux-musl/libgcc': configure: error: cannot compute suffix of object files: cannot compile See `config.log' for more details Please attach /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-gentoo-linux-musl/libgcc/config.log.
Created attachment 887561 [details] config.log
Created attachment 887563 [details] emerge --info
From config.log: configure:3814: /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/./gcc/ -B/usr/x86_64-gentoo-linux-musl/bin/ -B/usr/x86_64-gentoo-linux-musl/lib/ -isystem /usr/x86_64-gentoo-linux-musl/include -isystem /usr/x86_64-gentoo-linux-musl/sys-include -fno-checking -c -g -ggdb -march=znver3 -mtune=znver3 -pipe -O2 conftest.c >&5 clang: error: unsupported option '--64' clang: error: no input files configure:3818: $? = 2 configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "GNU C Runtime Library" | #define PACKAGE_TARNAME "libgcc" | #define PACKAGE_VERSION "1.0" | #define PACKAGE_STRING "GNU C Runtime Library 1.0" | #define PACKAGE_BUGREPORT "" | #define PACKAGE_URL "http://www.gnu.org/software/libgcc/" | /* end confdefs.h. */ | | int | main () | { | | ; | return 0; | } configure:3832: error: in `/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-gentoo-linux-musl/libgcc': configure:3834: error: cannot compute suffix of object files: cannot compile
It looks like xgcc is calling clang --64? That seems weird.
(In reply to Mike Gilbert from comment #6) > It looks like xgcc is calling clang --64? That seems weird. Is there a way I can prevent this? It's not in my custom flags.