[lkml]   [2001]   [Apr]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: gcc oopses with 2.4.3
On Fri, 6 Apr 2001, Norbert Preining wrote:

> On Fre, 06 Apr 2001, Chris Mason wrote:
> > sigbus from gcc usually points to the ram, have you run a tester?
> But sig 4 is sigill (whatever this may be) and 1ig11 sigsegv, so
> no sigbus!?
> BTW: The last lines of a kernel compile:
> gcc -D__KERNEL__ -I/usr/src/linux-2.4.3-ac3/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o tcp_output.o tcp_output.c
> gcc: Internal compiler error: program cc1 got fatal signal 11
> make[3]: *** [tcp_output.o] Error 1
> make[3]: Leaving directory `/usr/src/linux-2.4.3-ac3/net/ipv4'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory `/usr/src/linux-2.4.3-ac3/net/ipv4'
> make[1]: *** [_subdir_ipv4] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.4.3-ac3/net'
> make: *** [_dir_net] Error 2
> Best wishes
> Norbert

SIGSEGV, still looks like a bad RAM simptom. Think linked-list, bad

Dick Johnson

Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).

"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:24    [W:0.058 / U:3.984 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site