| 1 |
On Thu, Apr 26, 2012 at 2:20 PM, Canek Peláez Valdés <caneko@×××××.com> wrote: |
| 2 |
> On Thu, Apr 26, 2012 at 11:53 AM, Michael Mol <mikemol@×××××.com> wrote: |
| 3 |
>> On Thu, Apr 26, 2012 at 11:27 AM, Mark Knecht <markknecht@×××××.com> wrote: |
| 4 |
>>> On Thu, Apr 26, 2012 at 7:41 AM, Michael Mol <mikemol@×××××.com> wrote: |
| 5 |
>>>> On Thu, Apr 26, 2012 at 10:34 AM, Qian Qiao <qian.qiao@×××××.com> wrote: |
| 6 |
>>>>> On Thu, Apr 26, 2012 at 19:40, Michael Mol <mikemol@×××××.com> wrote: |
| 7 |
>>>>>> |
| 8 |
>>>>>> MAKEOPTS="-j1" didn't fix it. Off to find another solution. |
| 9 |
>>>>>> -- |
| 10 |
>>>>>> :wq |
| 11 |
>>>>>> |
| 12 |
>>>>> |
| 13 |
>>>>> Does sound like it's just you. I've been running with MAKEOPTS="-j13" |
| 14 |
>>>>> and everything compiled and ran just fine. |
| 15 |
>>>> |
| 16 |
>>>> Checking to see if it's a distcc problem, now. If it is, it'll only be |
| 17 |
>>>> the third time I've ever had issues from distcc, and the first time a |
| 18 |
>>>> distcc issue resulted in a successful build of a package that broke |
| 19 |
>>>> things. |
| 20 |
>>>> |
| 21 |
>>>> -- |
| 22 |
>>>> :wq |
| 23 |
>>>> |
| 24 |
>>> |
| 25 |
>>> Late to the party as I've been travelling. Running glibc-2.14.1-r3 |
| 26 |
>>> here with no problems. |
| 27 |
>>> |
| 28 |
>>> For the i7 i980x here's my make.conf stuff |
| 29 |
>>> |
| 30 |
>>> FEATURES="buildpkg" |
| 31 |
>>> |
| 32 |
>>> EMERGE_DEFAULT_OPTS="--with-bdeps=y --jobs=5" |
| 33 |
>>> MAKEOPTS="-j13 -l8" |
| 34 |
>>> PORTAGE_NICENESS=5 |
| 35 |
>>> PORTAGE_IONICE_COMMAND="ionice -c 3 -p \${PID}" |
| 36 |
>>> |
| 37 |
>>> This machine is mostly stable. |
| 38 |
>> |
| 39 |
>> For comparison, here's the current setup on my Phenom 9650: |
| 40 |
>> |
| 41 |
>> #expanded form of -march=native. Nothing special here. Noting this |
| 42 |
>> here because people keep freaking out when they see it in-line. |
| 43 |
>> SYS_CFLAGS_MARCH_NATIVE_EXP="-march=amdfam10 -mcx16 -msahf -mpopcnt |
| 44 |
>> --param l1-cache-size=64 --param l1-cache-line-size=64 --param |
| 45 |
>> l2-cache-size=512 -mtune=amdfam10" |
| 46 |
>> CFLAGS="${SYS_CFLAGS_MARCH_NATIVE_EXP} -O2 -pipe -ggdb3" |
| 47 |
>> CXXFLAGS="${CFLAGS}" |
| 48 |
>> FEATURES="splitdebug" |
| 49 |
>> MAKEOPTS="--jobs --load=5" |
| 50 |
>> EMERGE_DEFAULT_OPTS="--jobs --load-average=6 --verbose --tree |
| 51 |
>> --with-bdeps=y --keep-going" |
| 52 |
> |
| 53 |
> OK, I got my atom server (which is amd64) to emerge glibc. The trick |
| 54 |
> was to reboot it; it had several weeks uptime, I suppose something |
| 55 |
> "stale" was in there. I rebooted it, emerged glibc, and everything is |
| 56 |
> fine. |
| 57 |
|
| 58 |
Good to know. I'm still trying to figure out why emerging glibc, |
| 59 |
specifically, breaks/broke two out of three systems for me. |
| 60 |
|
| 61 |
|
| 62 |
-- |
| 63 |
:wq |
Archives