Gentoo Archives: gentoo-user

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

Replies