1 |
On Mon, Mar 25 2013, Michael Hampicke wrote: |
2 |
|
3 |
> Am 25.03.2013 21:57, schrieb gottlieb@×××.edu: |
4 |
>> For a long time I have had in make.conf |
5 |
>> |
6 |
>> EMERGE_DEFAULT_OPTS="--ask --deep --tree --verbose --jobs --load-average=5" |
7 |
>> MAKEOPTS="--jobs --load-average=5" |
8 |
>> |
9 |
>> (for previous processors the 5 was 3). |
10 |
>> |
11 |
>> It seems that this configuration fails for several packages (or tickles |
12 |
>> bugs in their ebuilds/Makefiles). |
13 |
>> |
14 |
>> Lately whenever a build fails I change to |
15 |
>> |
16 |
>> MAKEOPTS="--jobs=1" |
17 |
>> |
18 |
>> and this very often "fixes" the problem. |
19 |
>> |
20 |
>> It is not clear that any time saved by having jobs=5 compensates for |
21 |
>> having to redo builds. So my question is do people |
22 |
>> |
23 |
>> 1. keep jobs=1 in MAKEOPTS |
24 |
>> 2. have jobs=n in MAKEOPTS but degrade on error as I do |
25 |
>> 3. have jobs=n and file bugs when it fails. |
26 |
>> |
27 |
>> thanks, |
28 |
>> allan |
29 |
>> |
30 |
>> PS I do not change EMERGE_DEFAULT_OPTS |
31 |
>> |
32 |
> |
33 |
> This is what I use: |
34 |
> EMERGE_DEFAULT_OPTS="--jobs=2 --load-average=6" |
35 |
> |
36 |
> I havent't had any failed builds that were related to the --jobs option. |
37 |
> The only exception is when rebuilding my kernel modules. I have to build |
38 |
> spl first, then zfs-kmod. But that's because zfs-kmod requires a |
39 |
> complete built spl. |
40 |
|
41 |
I don't change EMERGE_DEFAULT_OPTS either. What I change is |
42 |
MAKEOPTS. |
43 |
|
44 |
That is, I always permit portage to run two emerges in parallel. |
45 |
I am considering telling make to not run different parts of one emerge |
46 |
in parallel. |
47 |
|
48 |
allan |