| 1 |
On Thu, Apr 26, 2012 at 7:41 AM, Michael Mol <mikemol@×××××.com> wrote: |
| 2 |
> On Thu, Apr 26, 2012 at 10:34 AM, Qian Qiao <qian.qiao@×××××.com> wrote: |
| 3 |
>> On Thu, Apr 26, 2012 at 19:40, Michael Mol <mikemol@×××××.com> wrote: |
| 4 |
>>> |
| 5 |
>>> MAKEOPTS="-j1" didn't fix it. Off to find another solution. |
| 6 |
>>> -- |
| 7 |
>>> :wq |
| 8 |
>>> |
| 9 |
>> |
| 10 |
>> Does sound like it's just you. I've been running with MAKEOPTS="-j13" |
| 11 |
>> and everything compiled and ran just fine. |
| 12 |
> |
| 13 |
> Checking to see if it's a distcc problem, now. If it is, it'll only be |
| 14 |
> the third time I've ever had issues from distcc, and the first time a |
| 15 |
> distcc issue resulted in a successful build of a package that broke |
| 16 |
> things. |
| 17 |
> |
| 18 |
> -- |
| 19 |
> :wq |
| 20 |
> |
| 21 |
|
| 22 |
Late to the party as I've been travelling. Running glibc-2.14.1-r3 |
| 23 |
here with no problems. |
| 24 |
|
| 25 |
For the i7 i980x here's my make.conf stuff |
| 26 |
|
| 27 |
FEATURES="buildpkg" |
| 28 |
|
| 29 |
EMERGE_DEFAULT_OPTS="--with-bdeps=y --jobs=5" |
| 30 |
MAKEOPTS="-j13 -l8" |
| 31 |
PORTAGE_NICENESS=5 |
| 32 |
PORTAGE_IONICE_COMMAND="ionice -c 3 -p \${PID}" |
| 33 |
|
| 34 |
This machine is mostly stable. |
| 35 |
|
| 36 |
- Mark |
Archives