[gentoo-user] Just a heads-up, I think =sys-libs/glibc-2.14.1-r3 is a stinker.

On Thu, Apr 26, 2012 at 22:41, Michael Mol wrote:

On Thu, Apr 26, 2012 at 10:34 AM, Qian Qiao wrote:

On Thu, Apr 26, 2012 at 19:40, Michael Mol wrote:

MAKEOPTS="-j1" didn't fix it. Off to find another solution.
:wq

Does sound like it's just you. I've been running with MAKEOPTS="-j13"
and everything compiled and ran just fine.

Checking to see if it's a distcc problem, now. If it is, it'll only be
the third time I've ever had issues from distcc, and the first time a
distcc issue resulted in a successful build of a package that broke
things.

I thought glibc doesn't use distcc even if you have it enabled.
Correct me if I'm wrong though.

On Thu, Apr 26, 2012 at 11:01 AM, Paul Hartman
<paul.hartman+ wrote:

On Thu, Apr 26, 2012 at 9:41 AM, Michael Mol wrote:

Checking to see if it's a distcc problem, now. If it is, it'll only be
the third time I've ever had issues from distcc, and the first time a
distcc issue resulted in a successful build of a package that broke
things.

Just to cover all possibilities... since everyone else is saying it's
not a problem for them -- have you run a memory test?

Not going to be a memory issue.

1) It killed two different boxes at the same time, and one of those
has 10GB of ECC memory.
2) On the machine I can still get into, It consistently breaks each
time I emerge glibc locally, and it consistently works if I unpack the
tarball I noted from gentooexperimental.org.

:wq

On Thu, Apr 26, 2012 at 7:41 AM, Michael Mol wrote:

On Thu, Apr 26, 2012 at 10:34 AM, Qian Qiao wrote:

On Thu, Apr 26, 2012 at 19:40, Michael Mol wrote:

MAKEOPTS="-j1" didn't fix it. Off to find another solution.
:wq

Does sound like it's just you. I've been running with MAKEOPTS="-j13"
and everything compiled and ran just fine.

Checking to see if it's a distcc problem, now. If it is, it'll only be
the third time I've ever had issues from distcc, and the first time a
distcc issue resulted in a successful build of a package that broke
things.

:wq

Late to the party as I've been travelling. Running glibc-2.14.1-r3
here with no problems.

For the i7 i980x here's my make.conf stuff

FEATURES="buildpkg"

EMERGE_DEFAULT_OPTS="--with-bdeps=y --jobs=5"
MAKEOPTS="-j13 -l8"
PORTAGE_NICENESS=5
PORTAGE_IONICE_COMMAND="ionice -c 3 -p \${PID}"

This machine is mostly stable.

- Mark

On Thu, Apr 26, 2012 at 11:27 AM, Mark Knecht wrote:

On Thu, Apr 26, 2012 at 7:41 AM, Michael Mol wrote:

On Thu, Apr 26, 2012 at 10:34 AM, Qian Qiao wrote:

On Thu, Apr 26, 2012 at 19:40, Michael Mol wrote:

MAKEOPTS="-j1" didn't fix it. Off to find another solution.
:wq

Does sound like it's just you. I've been running with MAKEOPTS="-j13"
and everything compiled and ran just fine.

Checking to see if it's a distcc problem, now. If it is, it'll only be
the third time I've ever had issues from distcc, and the first time a
distcc issue resulted in a successful build of a package that broke
things.

:wq

Late to the party as I've been travelling. Running glibc-2.14.1-r3
here with no problems.

For the i7 i980x here's my make.conf stuff

FEATURES="buildpkg"

EMERGE_DEFAULT_OPTS="--with-bdeps=y --jobs=5"
MAKEOPTS="-j13 -l8"
PORTAGE_NICENESS=5
PORTAGE_IONICE_COMMAND="ionice -c 3 -p \${PID}"

This machine is mostly stable.

For comparison, here's the current setup on my Phenom 9650:

#expanded form of -march=native. Nothing special here. Noting this
here because people keep freaking out when they see it in-line.
SYS_CFLAGS_MARCH_NATIVE_EXP="-march=amdfam10 -mcx16 -msahf -mpopcnt
l2-cache-sizeQ2 -mtune=amdfam10"
CFLAGS="${SYS_CFLAGS_MARCH_NATIVE_EXP} -O2 -pipe -ggdb3"
CXXFLAGS="${CFLAGS}"
FEATURES="splitdebug"
MAKEOPTS="--jobs --load=5"
EMERGE_DEFAULT_OPTS="--jobs --load-average=6 --verbose --tree



:wq

On Thu, Apr 26, 2012 at 11:53 AM, Michael Mol wrote:

On Thu, Apr 26, 2012 at 11:27 AM, Mark Knecht wrote:

On Thu, Apr 26, 2012 at 7:41 AM, Michael Mol wrote:

On Thu, Apr 26, 2012 at 10:34 AM, Qian Qiao wrote:

On Thu, Apr 26, 2012 at 19:40, Michael Mol wrote:

MAKEOPTS="-j1" didn't fix it. Off to find another solution.
:wq

Does sound like it's just you. I've been running with MAKEOPTS="-j13"
and everything compiled and ran just fine.

Checking to see if it's a distcc problem, now. If it is, it'll only be
the third time I've ever had issues from distcc, and the first time a
distcc issue resulted in a successful build of a package that broke
things.

:wq

Late to the party as I've been travelling. Running glibc-2.14.1-r3
here with no problems.

For the i7 i980x here's my make.conf stuff

FEATURES="buildpkg"

EMERGE_DEFAULT_OPTS="--with-bdeps=y --jobs=5"
MAKEOPTS="-j13 -l8"
PORTAGE_NICENESS=5
PORTAGE_IONICE_COMMAND="ionice -c 3 -p \${PID}"

This machine is mostly stable.

For comparison, here's the current setup on my Phenom 9650:

#expanded form of -march=native. Nothing special here. Noting this
here because people keep freaking out when they see it in-line.
SYS_CFLAGS_MARCH_NATIVE_EXP="-march=amdfam10 -mcx16 -msahf -mpopcnt
l2-cache-sizeQ2 -mtune=amdfam10"
CFLAGS="${SYS_CFLAGS_MARCH_NATIVE_EXP} -O2 -pipe -ggdb3"
CXXFLAGS="${CFLAGS}"
FEATURES="splitdebug"
MAKEOPTS="--jobs --load=5"
EMERGE_DEFAULT_OPTS="--jobs --load-average=6 --verbose --tree

OK, I got my atom server (which is amd64) to emerge glibc. The trick
was to reboot it; it had several weeks uptime, I suppose something
"stale" was in there. I rebooted it, emerged glibc, and everything is
fine.

Regards.
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México