Created attachment 471224 [details] build.log showing gcc failing on an NFS root filesystem machine with 4GB of system memory Can someone add diskspace and memory space checks before compilation of gcc starts since it appears gcc > 4.9 uses quite a bit more memory/disk space than previous versions and causes problems on lower memory/disk systems (e.g. NFS root filesystem diskless machines)
Created attachment 471234 [details] No -pipe and MAKEOPTS="-j1" still fails with 4GB of space to compile It looks like the minimum requirements for gcc-5.4.0 is quite high. I removed -pipe and ran it with MAKEOPTS="-j1" and it still ran out of space (it had almost the entire 4 GB to work with). This ebuild should definitely fail if there's not enough memory/diskspace to compile similar to libreoffice and firefox. It looks like I have to get more system memory just to compile newer versions of gcc on this machine even though it really doesn't need more memory for every day stuff since it's just a mythfrontend box.
Does newer gcc still fail the same? 4GB sounds like a lot of RAM for a single-threaded compilation.
(In reply to Sergei Trofimovich from comment #2) > Does newer gcc still fail the same? 4GB sounds like a lot of RAM for a > single-threaded compilation. I can't say at this point. I gave up trying to make it work and just bought more RAM (now 8GB) for the machine since RAM is cheap for that machine and the motherboard allowed more RAM.
(In reply to Matthew Schultz from comment #3) > (In reply to Sergei Trofimovich from comment #2) > > Does newer gcc still fail the same? 4GB sounds like a lot of RAM for a > > single-threaded compilation. > > I can't say at this point. I gave up trying to make it work and just bought > more RAM (now 8GB) for the machine since RAM is cheap for that machine and > the motherboard allowed more RAM. Aha, let's close as obsolete then. Thanks for the update!
