From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1H8yMV-0007yl-NQ for garchives@archives.gentoo.org; Mon, 22 Jan 2007 12:33:24 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.8) with SMTP id l0MCVO3N004790; Mon, 22 Jan 2007 12:31:24 GMT Received: from mxfep03.bredband.com (mxfep03.bredband.com [195.54.107.76]) by robin.gentoo.org (8.13.8/8.13.8) with ESMTP id l0MCPi6E030334 for ; Mon, 22 Jan 2007 12:25:45 GMT Received: from ironport2.bredband.com ([195.54.107.84] [195.54.107.84]) by mxfep03.bredband.com with ESMTP id <20070122122544.UNBZ2708.mxfep03.bredband.com@ironport2.bredband.com> for ; Mon, 22 Jan 2007 13:25:44 +0100 Received: from c-c0f5e055.104-1-64736c15.cust.bredbandsbolaget.se (HELO explosive.homelinux.org) ([85.224.245.192]) by ironport2.bredband.com with ESMTP/TLS/AES256-SHA; 22 Jan 2007 13:25:43 +0100 From: Naga To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] GCC Failing Date: Mon, 22 Jan 2007 13:25:40 +0100 User-Agent: KMail/1.9.5 References: In-Reply-To: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701221325.41785.nagatoro@gmail.com> X-Archives-Salt: e5490146-e8d5-42ef-9c55-faf41e466811 X-Archives-Hash: 08ddc1b7e004bc4aefe8577c6359bf92 On Monday 22 January 2007 12:48, Vlad Dogaru wrote: > Hello, > > what I initially thought was a problem with kdelibs is turning into > something even more strange. Emerge failed for every package I tried > to install with the message: "Internal compiler error: Segmentation > Fault". I have tried re-emerging gcc from two local mirrors, but got a > bunch of hash failures and corrupted archives. I am now trying > distfiles.gentoo.org, but this will take quite long. Any ideas as to > what might have happened? Could this be connected to X running > alarmingly slow? Faulty memory? Got something like this once and then it was a memory module that was broken. Try and check it with memcheck86 (think I got the name right :)) -- Naga -- gentoo-user@gentoo.org mailing list