On 04.04.24 00:44, Michael wrote:
> No, this is not normal.  I wonder if your make.conf settings are correct.
> Start with some safe CFLAGS as suggested here:
>
> https://wiki.gentoo.org/wiki/Safe_CFLAGS
>
> Then use the package 'app-portage/cpuid2cpuflags' to set the correct CPU
> flags:
>
> https://wiki.gentoo.org/wiki/CPU_FLAGS_*
>
> At this point you should be able to use gcc with no further problems.  You can
> try to optimise your settings further by taking a look at suggestions here:
>
> https://wiki.gentoo.org/wiki/GCC_optimization

Thank you for pointing into the right direction.

After changing -march=raptorlake to -march=alderlake on an i5-13600KS 
and running the following three times:

> In case you haven't done it yet, if you rebuild the toolchain things
> should
> hopefully self-correct on your system:
>
> emerge --sync
>
> emerge -1av sys-devel/binutils
>
> emerge -1av --nodeps sys-devel/gcc
>
> Use 'gcc-config -l' to check you are using the correct gcc version.
>
> emerge -1av sys-libs/glibc
>
> emerge -1av dev-build/libtool
>
> env-update && source /etc/profile
I don't get the hang at "-- Detecting C compiler ABI info" anymore. It 
now hangs later on "-- Looking for a ASM_NASM compiler".

My CPU_FLAGS_* are correct, I checked them with 
app-portage/cpuid2cpuflags to make sure they are up to date and they were.

Do you have any idea for this?

Thank you

Nanderty