Summary: | qt-3.3.3 compile fails with G++ internal error | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Simon Matthews <simon+bugzilla> |
Component: | New packages | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED INVALID | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Simon Matthews
2004-09-21 14:51:28 UTC
can't fix g++ compiler errors - local issue. What do you mean by "local issue"? Did this bug get assigned to the wrong person? If so, how do I get it correctly assigned? I mean that when the compiler seg faults it's a problem in the compiler, not in qt. We get these bugs all of the time. It's usually bad hardware - search bugzilla or the forums for "g++: Internal error: Terminated" and you will see... I have the same issue with qt-3.3.3 emerge failing - I can emerge other packages - in fact have emerged the entire system over this weekend without problems. If it is a compiler or hardware issue why am I not seeing it on other packages? Is there any test you can suggest? Because qt is one of the most computationally expensive programs to compile. memtest86 is a good one to start with I never would have believed it but yes it was a hardware problem (bad memory) It seemed strange that it always failed on the qt emerge and on no other emerges. Thanks for the help! I replaced the SIMM and it is busy emerging KDE and has finished emerging qt. great! |