From: Justin Findlay <justin@jfindlay.us>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problem with Emerge
Date: Thu, 7 Sep 2006 23:07:24 -0600 [thread overview]
Message-ID: <20060908050724.GF6976@archimedes> (raw)
In-Reply-To: <692017ac0609072011h39b594d7h933916a5e814a6a5@mail.gmail.com>
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
next prev parent reply other threads:[~2006-09-08 5:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 3:11 [gentoo-user] Problem with Emerge Bill Six
2006-09-08 5:07 ` Justin Findlay [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-08 2:54 Bill Six
2006-09-08 3:12 ` Dale
2006-09-08 3:36 ` Bill Six
2006-09-08 4:03 ` Donnie Berkholz
2006-09-08 5:07 ` Richard Broersma Jr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060908050724.GF6976@archimedes \
--to=justin@jfindlay.us \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox