Summary: | gentoo-dev-sources-2.6.10-r4 fails to compile (poweroff.o) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | ta2002 <throw_away_2002> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED INVALID | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
As titled (I hope :) ), my .config file
.config file (in text form) |
Description
ta2002
2005-01-11 08:23:37 UTC
Please attach your .config Created attachment 48225 [details]
As titled (I hope :) ), my .config file
I don't the "proper" way to attach a .config
(never done it before), so I used bzip2 to
compress it.
Please just attach it as text/plain so that it is readable and easy to access. Created attachment 48233 [details]
.config file (in text form)
Done.
Can't reproduce here. EINVAL is quite an important define, sounds like something has gone missing. Could you try: rm -rf /usr/src/linux-2.6.10-gentoo-r4 emerge gentoo-dev-sources And try again.. OK, I did that (an also recompiled the entire system with gcc 3.3.5). Somewhere, the problem disappeared. :) I had (maybe) a similar problem during the recompile. In one of the packages, one of the files just seemed completely out to lunch. The compile crashed, but the problem disappeared when I tried emerge --resume (without changing anything). I wonder if I have some kind of I/O (SATA) problem. Have to actually boot with 2.6.10 (and that might solve it) to test it further. Thanks. I think you might be getting confused with something else. "emerging" a kernel does not compile anything, it just unpacks and moves the source files. Thanks for reporting this issue anyway. > "emerging" a kernel does not compile anything
I understand that. I wonder if just unpacking all
of those files at once (on an SATA drive - and I
have had an issue with my SATA removable drive
since 2.6.7, though none with the fixed drive -
you might see another bug report soon on that if
2.6.10 does not solve the problem) occasionally
spits out a corrupted file.
Nothing worse than flaky (difficult to replicate)
bugs.
|