public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gcc fails and then succeeds - definitely a problem?
Date: Thu, 23 Feb 2012 11:46:03 -0800	[thread overview]
Message-ID: <CAK2H+efd9CaCRNFA9c-xN8J8cWpMV1cZVsrDqFSbbSp_A_6YJA@mail.gmail.com> (raw)
In-Reply-To: <CA+czFiDqQmadcJ6rEeHH3tobmev5aqR7D9yqedFT6SQz-D4AgA@mail.gmail.com>

On Thu, Feb 23, 2012 at 11:36 AM, Michael Mol <mikemol@gmail.com> wrote:
> On Thu, Feb 23, 2012 at 2:28 PM, Mark Knecht <markknecht@gmail.com> wrote:
>> On Thu, Feb 23, 2012 at 11:17 AM, Grant <emailgrant@gmail.com> wrote:
>>> The gcc update just failed to compile on one of my systems with a
>>> segfault, but then succeeded after trying again even though I didn't
>>> change anything.  Does that indicate a hardware problem for sure?
>>> Should I run memtester?  Any other tests to run?  Nothing in dmesg.
>>>
>>> - Grant
>>>
>>
>> Might be.....might be nothing. Maybe a stray neutrino hit your
>> processor at just the wrong instant. ;-)
>>
>> More likely i my mind is some little corner condition in the software
>> running on your system. I've had the same thing happen many times
>> actually, and actually a few more times since I started playing with
>> your /etc/make.conf -j/-l values which push the system a little
>> harder.
>
> Whenever I get build failures with the load-adaptive MAKEOPTS and
> EMERGE_DEFAULT_OPTS, I check the build log to see if it's relatively
> obvious that something was depended upon before it was built. If so, I
> file a bug.
>
> Happens every month or so, for me.
>

There are log files? You're telling me I should read them? Gawd,
pretty soon you're gonna try to make a real admin of me instead of
just the oblivious happy home user that I am... ;-)

Good inputs. Thanks!

Cheers,
Mark



  reply	other threads:[~2012-02-23 19:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23 19:17 [gentoo-user] gcc fails and then succeeds - definitely a problem? Grant
2012-02-23 19:23 ` Michael Mol
2012-02-23 19:40   ` Grant
2012-02-23 21:11     ` Grant
2012-02-23 21:18       ` Mark Knecht
2012-02-23 21:27       ` Alex Schuster
2012-02-23 19:25 ` [gentoo-user] " Heorhi Valakhanovich
2012-02-23 19:28 ` [gentoo-user] " Mark Knecht
2012-02-23 19:36   ` Michael Mol
2012-02-23 19:46     ` Mark Knecht [this message]
2012-02-23 21:37       ` Alan McKinnon
2012-02-23 19:39 ` Alan McKinnon
2012-02-23 19:47   ` Grant
2012-02-23 20:38     ` Neil Bothwick
2012-02-23 21:00       ` Grant
2012-02-23 22:05         ` Michael Mol

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=CAK2H+efd9CaCRNFA9c-xN8J8cWpMV1cZVsrDqFSbbSp_A_6YJA@mail.gmail.com \
    --to=markknecht@gmail.com \
    --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