Unable to emerge gcc I was attempting do a ‘emerge –ask –newuse –update –deep @world’ Each time it would fail at emerging gcc. I then attempted to emerge gcc by itself. The output stayed at ‘emerging gcc’ then spued a large stream lines with looked like compiler output. The final lines are: * Messages for package sys-devel/gcc-11.2.0: * ERROR: sys-devel/gcc-11.2.0::gentoo failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=sys-devel/gcc-11.2.0::gentoo'`, * the complete build log and the output of `emerge -pqv '=sys-devel/gcc-11.2.0::gentoo'`. * The complete build log is located at '/var/tmp/portage/sys-devel/gcc-11.2.0/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-11.2.0/temp/environment'. * Working directory: '/var/tmp/portage/sys-devel/gcc-11.2.0/work/build' * S: '/var/tmp/portage/sys-devel/gcc-11.2.0/work/gcc-11.2.0' * * Please include /var/tmp/portage/sys-devel/gcc-11.2.0/work/gcc-build-logs.tar.bz2 in your bug report. I have attached the outputs and files requested
>I have attached the outputs and files requested They do not seem to be attached.
Check if you have enough disk space and memory. Try reducing MAKEOPTS if you're short on memory too.
Created attachment 745950 [details] gcc-pqv-emerge.log
Created attachment 745953 [details] emerge --info
Created attachment 745956 [details] Enviroment
(In reply to Frank Daniel from comment #4) > Created attachment 745953 [details] > emerge --info Note that MAKEOPTS="-j17" with 16GB RAM is unsafe. At worst, compiler jobs may take up to 2GB of RAM per instance. You therefore should be running with -j8 at most. Can you share the tarball the error asks you to upload?
Created attachment 746067 [details] gcc-build-logs.tar.bz2
I found that the tar ball was smaller than I thought. I have added it to the attachments.
The gentoo installation is by its self on a 200Gb ssd.
Every time I've seen something like this: >/usr/include/gnu/stubs.h:7:11: fatal error: gnu/stubs-32.h: No such file or directory it's ended up being an odd multilib-broken situation. Hm.
Is there anything interesting about your machine? Perhaps only recently migrated from 17.0? Also, I would not have USE=debug in make.conf. It is not for debugging symbols (see https://wiki.gentoo.org/wiki/Debugging for that), but for enabling asserts and other debug codepaths. It is best enabled in package.use for stuff you specifically want it for, if anything.
I am going to backup the install and start anew. If you want me to try anything email me. I can get the backup reinstall in about 10 minutes.
Well I did start over. Actual twice. First time the same thing happened. The sec time the issue came for rust. But there wasn't a tar ball for that. The last time I made some changes in make.conf (which I didn't document and will haunt me later) that worked. I now have an issue with kde/plasma and duplicity of emerged code. But that for a later Bug report if needed. So, this bug can be closed from my end.
