On Thu, Feb 23, 2012 at 11:36 AM, Michael Mol <mike...@gmail.com> wrote: > On Thu, Feb 23, 2012 at 2:28 PM, Mark Knecht <markkne...@gmail.com> wrote: >> On Thu, Feb 23, 2012 at 11:17 AM, Grant <emailgr...@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
