On 03/28/2018 01:32 AM, Peter Humphrey wrote: > On Tuesday, 27 March 2018 16:25:10 BST the...@sys-concept.com wrote: >> SOLVED! >> The gcc-6.4.0-r1 compiled with >> MAKEOPTS="-j1" >> >> What is strange is that this is the second low profile system that >> gcc-6.4.0-r1 failed to compile large package. My other boxed was 4-core >> and 4GB of RAM and I had to switch to MAKEOPTS="-j1" >> >> The above system is: Intel(R) Atom(TM) CPU 330 @ 1.60GHz with 2GB of RAM >> and "gcc-4.9.4" compiled "gcc-6.4.0-r1" with MAKEOPTS="-j5" OK >> but when I switched/upgrade profile to "gcc-6.4.0-r1" it filed to >> compile gcc-6.4.0 with MAKEOPTS="-j5" >> I had lower MAKEOPTS to -j1 >> >> So it seems to me the gcc-6.4.0-r1 much more resource hungry or there is >> a bug in it. > > I have a similar system, but Atom N270. I wouldn't want to compile much on > it, > and certainly not GCC. I NFS-export its $PORTDIR to this much more powerful > box, do the emerging here and then just install packages on the Atom. Still > not exactly fast, but incomparably better.
I should have done it as well, it is a bit too late I have only 45-packages left to compile out of 710. Is it better use NFS or distcc? Do you have a good link how to do it with: "NFS-export $PORTDIR" -- Thelma
