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.60) (envelope-from ) id 1GLYiO-0006fP-Ig for garchives@archives.gentoo.org; Fri, 08 Sep 2006 05:15:45 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k885E95u002532; Fri, 8 Sep 2006 05:14:09 GMT Received: from jfindlay.us ([67.137.24.115]) by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k8857Tv8011375 for ; Fri, 8 Sep 2006 05:07:29 GMT Received: by jfindlay.us (Postfix, from userid 500) id 2CE6E7005F; Thu, 7 Sep 2006 23:07:24 -0600 (MDT) Date: Thu, 7 Sep 2006 23:07:24 -0600 From: Justin Findlay To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Problem with Emerge Message-ID: <20060908050724.GF6976@archimedes> Mail-Followup-To: gentoo-user@lists.gentoo.org References: <692017ac0609072011h39b594d7h933916a5e814a6a5@mail.gmail.com> 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=us-ascii Content-Disposition: inline In-Reply-To: <692017ac0609072011h39b594d7h933916a5e814a6a5@mail.gmail.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Archives-Salt: 36f99c80-6390-49e0-9d1c-eb855bf3de4e X-Archives-Hash: 4b89361f77f557d53727f44b3455f42b On AD 2006 September 07 Thursday 11:11:46 PM -0400, Bill Six wrote: >Hi, > >3 days ago I just switched back to Gentoo after not using it for >about 6 months. > >However, I've been having issues emerging packages. Frequently, >the build will crap out and I'll get something like the >following. Any idea why this happens? If you're getting the compiler segmentation fault on many packages at random times you probably have bad hardware. The causes I've seen for this are bad or intermittently bad ram/other hardware, or hardware failure over a certain temperature. The first can be easily diagnosed with memtest86+ as once the probe hits bad sectors you'll know about it. The second is much more difficult to track down but not impossible. If your compiler is segfaulting once the CPU hits a certain temperature, then you can verify this is going on by emerging a package and watching the temperature and observe at which temperature the compiler segfaults. Older Athlons run pretty hot. If this is your case you may want to buy the expensive silver heat sink compound. As for OS problems I don't know what to say except that this may be a sign not to run -mm or better patch sets and expect things to be stable. (: At least all the critical ebuilds should filter out insanity CFLAGS. Justin -- You have 1 Moderator Point! Use it or lose it! -- gentoo-user@gentoo.org mailing list