|
|
You've got hardware problems.
If you're getting segfaults and re-starting ``make'' lets you continue, you've almost certainly got bad hardware. If gcc is dying with SIG11 errors, you can remove the ``almost.'' In fact, repeatedly compiling known-good code is a classic hardware test.
You've got hardware problems.
I've had seg faults with g77 v. 3.4 that are reproducible, but I haven't got around them by retrying. Sometimes lowering the optimization helps.
You've got hardware problems.
This is exactly what I was about to say... every single time (and I've been doing this a pretty long time) I've seen gcc die on an 11, it's been bad hardware. And not even bad as in "broken" all the time, e.g. I have a couple of Shuttle SK43Gs that die identically during extended compiles, apparently by design. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.32 seconds |
|