| 1 |
On Tuesday, 27 March 2018 16:25:10 BST thelma@×××××××××××.com wrote: |
| 2 |
> SOLVED! |
| 3 |
> The gcc-6.4.0-r1 compiled with |
| 4 |
> MAKEOPTS="-j1" |
| 5 |
> |
| 6 |
> What is strange is that this is the second low profile system that |
| 7 |
> gcc-6.4.0-r1 failed to compile large package. My other boxed was 4-core |
| 8 |
> and 4GB of RAM and I had to switch to MAKEOPTS="-j1" |
| 9 |
> |
| 10 |
> The above system is: Intel(R) Atom(TM) CPU 330 @ 1.60GHz with 2GB of RAM |
| 11 |
> and "gcc-4.9.4" compiled "gcc-6.4.0-r1" with MAKEOPTS="-j5" OK |
| 12 |
> but when I switched/upgrade profile to "gcc-6.4.0-r1" it filed to |
| 13 |
> compile gcc-6.4.0 with MAKEOPTS="-j5" |
| 14 |
> I had lower MAKEOPTS to -j1 |
| 15 |
> |
| 16 |
> So it seems to me the gcc-6.4.0-r1 much more resource hungry or there is |
| 17 |
> a bug in it. |
| 18 |
|
| 19 |
I have a similar system, but Atom N270. I wouldn't want to compile much on it, |
| 20 |
and certainly not GCC. I NFS-export its $PORTDIR to this much more powerful |
| 21 |
box, do the emerging here and then just install packages on the Atom. Still |
| 22 |
not exactly fast, but incomparably better. |
| 23 |
|
| 24 |
-- |
| 25 |
Regards |
| 26 |
Peter |
Archives