Summary: | emerge --update system compile error | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Angela Kahealani <angela> |
Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | VERIFIED DUPLICATE | ||
Severity: | blocker | CC: | patrick |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | http://dev/null | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
as many error messages as didn't scroll offscreen
emerge --info compile errors: emerge --update world emerge --info |
Description
Angela Kahealani
2005-09-06 02:23:10 UTC
Sorry, without more info we can't help you much. Closing as NEEDINFO, reopen once you can give us more info. Created attachment 67721 [details]
as many error messages as didn't scroll offscreen
gpm would paste into vi, so now have some error messages to reveal problem
That looks like a hardware problem ... gcc segfaults usually happen when the hardware is faulty (cpu overheating, bad memory) or with insane CFLAGS. Please try again to emerge glibc, if the same error happens I'll try to diagnose it, if the error doesn't happen please check your hardware first. Created attachment 67724 [details]
emerge --info
The status of the system during which compile error occurred
Created attachment 67726 [details]
compile errors: emerge --update world
Created attachment 67727 [details]
emerge --info
I'm almost sure that the errors happen because of bad hardware. There's not much we can do about it, closing bug. have now supplied all available error messages from gpm screen capture for both emerge --update system and for emerge --update world, and have also provided emerge --info for both... unless there is some other log file to attach to the bug report, I don't know what else to do... the system is only minimally usable in present state Please, read comment #8 and the other bug. We cannot solve hardware problems. *** This bug has been marked as a duplicate of 20600 *** If it's a hardware bug, it is most likely associated with the fact that the root filesystem resides on a RAID0 (striped) array of Seagate SATA drives which have driver issues in history being run from the SiI3112(a?) controller chip on the Asus A7N8X-E mobo, which although fixed in Fedora Core may not have been handled in Gentoo? SiI3112 works in software RAID-5 over LMV2 for me on two machines, no problems at all. We can't fix your faulty motherboard anyway. CLOSING. *** This bug has been marked as a duplicate of 20600 *** Really CLOSED. |