On Wednesday, 3 April 2024 19:20:27 BST Paul Sopka wrote: > On 03.04.24 09:40, Michael wrote: > > 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 > > Good evening Michael > > Thank you for your suggestions, I tried them, but unfortunately it > didn't help. > > Also, i found out that removing CPU_FLAGS_X86 made the issue disappear, > but another issue appeared later. I experience a similar hang, at "-- > Looking for a ASM_NASM compiler". > > Further, compiling GCC throws the following warnings: > > * QA Notice: Installing libtool files (.la) without corresponding > static libraries! > * /usr/libexec/gcc/x86_64-pc-linux-gnu/13/liblto_plugin.la > * QA Notice: Found the following implicit function declarations in > configure logs: > * > /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-g > nu/32/libgfortran/config.log:4628 - fpsetmask > * > /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-g > nu/libgfortran/config.log:4536 - fpsetmask > * Check that no features were accidentally disabled. > * See https://wiki.gentoo.org/wiki/Modern_C_porting. > * QA Notice: Package triggers severe warnings which indicate that it > * may exhibit random runtime failures. > * > /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/gcc-13-20240210/gcc/vec > .h:316: warning: ‘free’ called on unallocated object ‘accesses’ > [-Wfree-nonheap-object] > * > /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/gcc-13-20240210/gcc/vec > .h:316:10: warning: ‘free’ called on unallocated object ‘dest_bbs’ > [-Wfree-nonheap-object] > * > /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/gcc-13-20240210/gcc/vec > .h:316: warning: ‘free’ called on unallocated object ‘accesses’ > [-Wfree-nonheap-object] > * > /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/gcc-13-20240210/gcc/vec > .h:316:10: warning: ‘free’ called on unallocated object ‘dest_bbs’ > [-Wfree-nonheap-object] > * > /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/gcc-13-20240210/libsani > tizer/hwasan/hwasan.cpp:539:52: warning: format ‘%zd’ expects a matching > ‘signed size_t’ argument > [-Wformat=] > * Please do not file a Gentoo bug and instead report the above QA > * issues directly to the upstream developers of this software. > * Homepage: https://gcc.gnu.org/ > > Is this normal?
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
signature.asc
Description: This is a digitally signed message part.
