On Mon, Mar 25 2013, Michael Hampicke wrote: > Am 25.03.2013 21:57, schrieb [email protected]: >> For a long time I have had in make.conf >> >> EMERGE_DEFAULT_OPTS="--ask --deep --tree --verbose --jobs --load-average=5" >> MAKEOPTS="--jobs --load-average=5" >> >> (for previous processors the 5 was 3). >> >> It seems that this configuration fails for several packages (or tickles >> bugs in their ebuilds/Makefiles). >> >> Lately whenever a build fails I change to >> >> MAKEOPTS="--jobs=1" >> >> and this very often "fixes" the problem. >> >> It is not clear that any time saved by having jobs=5 compensates for >> having to redo builds. So my question is do people >> >> 1. keep jobs=1 in MAKEOPTS >> 2. have jobs=n in MAKEOPTS but degrade on error as I do >> 3. have jobs=n and file bugs when it fails. >> >> thanks, >> allan >> >> PS I do not change EMERGE_DEFAULT_OPTS >> > > This is what I use: > EMERGE_DEFAULT_OPTS="--jobs=2 --load-average=6" > > I havent't had any failed builds that were related to the --jobs option. > The only exception is when rebuilding my kernel modules. I have to build > spl first, then zfs-kmod. But that's because zfs-kmod requires a > complete built spl.
I don't change EMERGE_DEFAULT_OPTS either. What I change is MAKEOPTS. That is, I always permit portage to run two emerges in parallel. I am considering telling make to not run different parts of one emerge in parallel. allan
