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