Summary: | starting from a stage3 (rc3) tarball on an LFS system, compiling the gentoo-sources kernel segfaults in "make bzImage" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | david t-g <davidtg-gentoo-bugzilla> |
Component: | [OLD] Core system | Assignee: | x86-kernel (DEPRECATED) <x86-kernel> |
Status: | RESOLVED INVALID | ||
Severity: | critical | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
david t-g
2003-04-11 18:13:31 UTC
this does not seem to be a gentoo-sources issue. looks as if the user has a hardware issue of some sort (probably memory). the sig 11 (seg fault) signifies a program (here gcc) accessed a memory location it was not allocated. we've had real good success with gcc-3.2.1 so, i suspect it is not a design flaw in gcc. also, the compile failed in at least 3 different places and the last was 'as' the gnu assembler, it errored on what gcc passed for it to assemble. if it was the kernel source, we would expect to fail in the same place. but, it compiles different items each time before failing... try running memtest to rule out bad memory. or look @ this article, it may be useful: http://www.bitwizard.nl/sig11/ closing as this cannot be reproduced. please reopen if you have more info. Jay |