Summary: | Weird kills: Internal error: Killed (program cc1) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Auke Booij (tulcod) <auke> |
Component: | [OLD] Core system | Assignee: | AMD64 Project <amd64> |
Status: | RESOLVED INVALID | ||
Severity: | critical | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log |
Description
Auke Booij (tulcod)
2008-04-17 16:13:35 UTC
Created attachment 150075 [details]
build.log
build.log for the emerge of ffmpeg as an example
Do these failures happen in the same exact place every time? yes, seems like so. and like i said, the kernel compiles fine, among some ohter packages, so the problem is unlikely to be caused by hardware. okay, now this is interesting. I took the tarball out of /usr/portage/distfiles/, unpacked it in /tmp and built it. No problems whatsoever. I doubt I ran ./configure exactly the same as portage, but at least this indicates that the problem is not completely my fault :) So I tried again, this time I made sure the output of ./configure matched the version emerge gave me. The complete build succeeded. The problem does not have to do with my hardware or the packages themselves. I don't follow. So now you are able to build the package? It randomly failing and now it working indicates a hardware problem, not a software one. In userspace, without the help of emerge, I can build the package without a single problem. emerge fails building the package with the same ./configure settings. Did you supply the same exact CFLAGS as well, because if you were building it by hand, you probably didn't. With emerge please try it a few times and see if it fails in the same spot each time. Okay, so good news and bad news. The good news is that my setup works now, on the same hardware. The bad news is that I had to reinstall gentoo. Sorry, but I'm kind of in a hurry and can't really take the time to debug all this. The only thing I can say is that my setup started acting weird after only trying to compile gcc 4.3.0. The problem was not caused by hardware. okay, whatever, all this was solved with a bios update :-/ sry guys |