Pre-Merge-Checks for gcc 6.4.0 seem to check for 4GB, but my compiler aborted while I gave it 4GB. df -h proves that more than 4GB seem to be used: ``` $ df -h /tmp/portage/ Filesystem Size Used Avail Use% Mounted on none 5.0G 4.3G 753M 86% /tmp/portage ``` Can you please increase the required GBs (to 5?) in the pre-merge checks? Many thanks.
just recently, gcc also failed to emerge properly, and I fixed it by increasing the space available for emerging packages. I didn't make notes of the available space previously available, that caused the emerge to fail. However, just now: ``` >>> Completed installing gcc-6.4.0 into /scratch/var/tmp/portage/sys-devel/gcc-6.4.0/image/ * Final size of build directory: 2473964 KiB ( 2.3 GiB) * Final size of installed tree: 366420 KiB (357.8 MiB) ``` The required space may also depend on the USE flags enabled. Here are mine: # equery -q u gcc -cilk +cxx -debug -doc +fortran -go -graphite -mpx +nls +nptl -objc -objc++ - bjc-gc +openmp +pch -pgo -pie -regression-test +sanitize +ssp -vanilla +vtv I don't know how/where gcc does its pre-merge requirement checks. I notice that gcc.ebuild does not include CHECKREQS_DISK_BUILD (see: http://linux.overshoot.tv/wiki/portage_keywords_used_ebuilds )
*** This bug has been marked as a duplicate of bug 526986 ***
