From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SNTQR-0003YV-IV for garchives@archives.gentoo.org; Thu, 26 Apr 2012 18:28:19 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CA788E0509; Thu, 26 Apr 2012 18:27:45 +0000 (UTC) Received: from mail-bk0-f53.google.com (mail-bk0-f53.google.com [209.85.214.53]) by pigeon.gentoo.org (Postfix) with ESMTP id D90D1E0827 for ; Thu, 26 Apr 2012 18:26:08 +0000 (UTC) Received: by bkcjk13 with SMTP id jk13so968182bkc.40 for ; Thu, 26 Apr 2012 11:26:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=CICG/Rf2TDvpTC7mBIY6RrfZHYmLmjWwRLEh+A3gq00=; b=K9vJ3QkgK6IIEQGnw330lzIywIO7a58q0I0MmffKf8BeHfNhJFVD64e6XYuze+pfD5 WyEh7r3aN+7kXVpbQXt1lS9A5Z+SSJrHnqj5iIPgmunKO2WuwD0qZdx0VN21bha9DwxO 31DAX4PaYgBf2ajL88eWUNQZwTlJyFG9F7oflclUtyhCNeAhpeTwLiF2ChokWy82QCjU CoL+5/GEY0pFhhWaMeE6+2T7XnGZGV2sAICS0yTyspcLhdgAGLvR9YUlnxgG6CdiVwam V+n3bV0eBGqLm/e+DYW9Npc9WLv+z09ojpJ2/dcO3/44GsMYSnzFSszK2zE1Dqk27z4c zsqQ== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.204.155.152 with SMTP id s24mr2753678bkw.91.1335464767891; Thu, 26 Apr 2012 11:26:07 -0700 (PDT) Received: by 10.204.153.213 with HTTP; Thu, 26 Apr 2012 11:26:07 -0700 (PDT) In-Reply-To: References: Date: Thu, 26 Apr 2012 14:26:07 -0400 Message-ID: Subject: Re: [gentoo-user] Just a heads-up, I think =sys-libs/glibc-2.14.1-r3 is a stinker. From: Michael Mol To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 28c06d20-a1d0-47d7-8f64-969bcb2483fb X-Archives-Hash: 853e6685e89d855567aef2df4114b3a4 On Thu, Apr 26, 2012 at 2:20 PM, Canek Pel=C3=A1ez Vald=C3=A9s wrote: > On Thu, Apr 26, 2012 at 11:53 AM, Michael Mol wrote: >> On Thu, Apr 26, 2012 at 11:27 AM, Mark Knecht wro= te: >>> On Thu, Apr 26, 2012 at 7:41 AM, Michael Mol wrote: >>>> On Thu, Apr 26, 2012 at 10:34 AM, Qian Qiao wrot= e: >>>>> On Thu, Apr 26, 2012 at 19:40, Michael Mol wrote: >>>>>> >>>>>> MAKEOPTS=3D"-j1" didn't fix it. Off to find another solution. >>>>>> -- >>>>>> :wq >>>>>> >>>>> >>>>> Does sound like it's just you. I've been running with MAKEOPTS=3D"-j1= 3" >>>>> 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=3D"buildpkg" >>> >>> EMERGE_DEFAULT_OPTS=3D"--with-bdeps=3Dy --jobs=3D5" >>> MAKEOPTS=3D"-j13 -l8" >>> PORTAGE_NICENESS=3D5 >>> PORTAGE_IONICE_COMMAND=3D"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=3Dnative. Nothing special here. Noting this >> here because people keep freaking out when they see it in-line. >> SYS_CFLAGS_MARCH_NATIVE_EXP=3D"-march=3Damdfam10 -mcx16 -msahf -mpopcnt >> --param l1-cache-size=3D64 --param l1-cache-line-size=3D64 --param >> l2-cache-size=3D512 -mtune=3Damdfam10" >> CFLAGS=3D"${SYS_CFLAGS_MARCH_NATIVE_EXP} -O2 -pipe -ggdb3" >> CXXFLAGS=3D"${CFLAGS}" >> FEATURES=3D"splitdebug" >> MAKEOPTS=3D"--jobs --load=3D5" >> EMERGE_DEFAULT_OPTS=3D"--jobs --load-average=3D6 --verbose --tree >> --with-bdeps=3Dy --keep-going" > > 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. Good to know. I'm still trying to figure out why emerging glibc, specifically, breaks/broke two out of three systems for me. --=20 :wq