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 1SNQaH-0002Tv-FH for garchives@archives.gentoo.org; Thu, 26 Apr 2012 15:26:17 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 93D3AE0802; Thu, 26 Apr 2012 15:25:57 +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 006C7E07BA for ; Thu, 26 Apr 2012 15:24:42 +0000 (UTC) Received: by bkcjk13 with SMTP id jk13so790456bkc.40 for ; Thu, 26 Apr 2012 08:24:42 -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; bh=yekvoqWWj99sYC5Fm930Mq9lvMXV+Xw/U2pfUrBxPXM=; b=WKal+DHXbHpkni/CcD+8C8DW1Mom9jcrMIP+5LYHlLQseZlmhO8uUVQFTZ/meTvUtm +t5lMty4RRoU8CnGPyYTd3n+NP6XriZ8bRDsxcjf4TlxpNmovnMYSAnoUFv7YHf06FFt CAM4j2RV1v/iSrL7Uaq6QM1slmu6vkFxcebMPAR0oGDhYkNJ6VEdpAflLsPfegLk8akK gHcYowkNdPD0fYRMk8FfHBsZ/KZCQcc/Y8unEZS5OI7lIqm3FY5bcJmlN+C+OaFPLsrk ocLCaLiCpPqsf1rqKlQ9GvslwrdSEq38gWLdd+xnoHUJ/UnGiMgfaKydQ1Gp9NntezT7 C4RA== 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.152.137 with SMTP id g9mr1036982bkw.95.1335453882076; Thu, 26 Apr 2012 08:24:42 -0700 (PDT) Received: by 10.204.153.213 with HTTP; Thu, 26 Apr 2012 08:24:42 -0700 (PDT) In-Reply-To: References: Date: Thu, 26 Apr 2012 11:24:42 -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 X-Archives-Salt: 6c2d0b32-2b1a-4eb7-9823-e556840054f7 X-Archives-Hash: dd3895c9dcc6bfbb49dc43b8a2a4bf92 On Thu, Apr 26, 2012 at 11:01 AM, 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