Summary: | Emerge gnome-games-2.12.2 fails | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | matthew.cline |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | VERIFIED NEEDINFO | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | screen log of failed emerge |
Description
matthew.cline
2005-12-12 16:17:15 UTC
There's no error in the output you've posted. After this output, emerge silently dies and returns me to the command prompt. What other info can I provide? Created attachment 74686 [details]
screen log of failed emerge
I don't know if this is helpful, but I've attached a screen log of the failed
emerge.
Thats odd. It seems that your kernel is killing the compiler/process behind it, causing it to just go up and die. Look at dmesg to see if you run into OOM or otherwise. "terminating" isn't a message I recognize, and since portage doesn't start to spew out its "aborted.." backlog, it means that by this time, the emerge process is already dead. I'm afraid I cannot help anything here, since theres nothing in the -build- process that is executed or that fails inherently, but the linking stage of gcc/binutils. I think the "terminating" message is a result of ending the screen session, not related to the build process. In any event, I tried to emerge this package again, and it worked. The only thing I can think of as being different is that tried the emerge via ssh rather than from my full-blown XFCE desktop. This would seem to lend support to the idea that it could have been an OOM issue. However, I had successfully emerged other, much larger packages (such as all of KDE) without these problems. Very weird, but working fine now. Thank you for your help. |