Created attachment 521056 [details] emerge --info * Messages for package sys-devel/gcc-6.4.0-r1: * ERROR: sys-devel/gcc-6.4.0-r1::gentoo failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=sys-devel/gcc-6.4.0-r1::gentoo'`, * the complete build log and the output of `emerge -pqv '=sys-devel/gcc-6.4.0-r1::gentoo'`. * The complete build log is located at '/var/tmp/portage/sys-devel/gcc-6.4.0-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-6.4.0-r1/temp/environment'. * Working directory: '/var/tmp/portage/sys-devel/gcc-6.4.0-r1/work/build' * S: '/var/tmp/portage/sys-devel/gcc-6.4.0-r1/work/gcc-6.4.0' * * Please include /var/tmp/portage/sys-devel/gcc-6.4.0-r1/work/gcc-build-logs.tar.bz2 in your bug report. * Here's the emerge "pqv": [ebuild NS ] sys-devel/gcc-6.4.0-r1 [4.9.3] USE="cxx fortran (multilib) nls nptl openmp pch (pie) sanitize ssp vtv (-altivec) (-awt) -cilk -debug -doc (-fixed-point) (-gcj) -go -graphite (-hardened) (-jit) (-libssp) -mpx -objc -objc++ -objc-gc -pgo -regression-test -vanilla" Other items will follow as attachments. Note: the build log is 4MB, so I'll upload the last 100 lines.
Created attachment 521058 [details] Build.log -- last 100 lines original build file is 6MB, so only providing last 100 lines. I do have the full log if you need it, but please suggest where I should make it available.
I tried to emerge gcc-6.4.0 to see if that could successfully build. Early on I got this message: tar: gcc-6.4.0/fixincludes: Cannot mkdir: No space left on device tar: gcc-6.4.0/fixincludes/fixincl.x: Cannot open: No such file or directory df -l shows the root area 100% filled, so I'm guessing lack of space may be the culprit for this bug. Please do not spend any time on this until I update this bug and confirm that space is not an underlying factor.
Please reopen if it happens again. Next time, try compressing the build log, it should help a lot.
I have 20 GB allocated to the environment, when GCC commenced building I was using 77% leaving about 5 GB available. I went through and removed any old tmp files to bring this down to 77%, I do not know what the disk availability was when I first attempted to build GCC. Nonetheless, I monitored the GCC build and found my disk usage rose to 96% during the compile, so that would be about 4 GB+ needed for the compile. This is a DOM0 environment, I'll recommend on whatever wiki page that concerns Xen with Gentoo to allot a disk space greater than 20 GB for DOM0. This is a minimalist build simply to support Xen. I wonder if during the compile and library processing stages a simple script that monitors available percentage of disk space and reports out possible insufficient disk space when a certain threshold is reached should be further implemented. I did receive a warning on my second attempt to build a lesser version of GCC as that was early on in the configuration process. I hope nobody spent time on this before my announcement above that the underlying problem may be due to lack of disk space. If anyone reading this within 30 days of this posting believes it would be helpful for me to upload the entire build.log, then let me know and I'll zip it up and add to this ticket.
