I believe a signal 11 may signify a memory problem. Perhaps you need to look at a new chip or two. Tom Veldhouse veldy at veldy.net ----- Original Message ----- From: Dave Sherohman <esper at sherohman.org> To: <tclug-list at mn-linux.org> Sent: Tuesday, July 11, 2000 10:21 AM Subject: Re: [TCLUG:19528] Weird gcc errors > Kevin R. Bullock said: > > Amongst other errors (make exiting loudly, etc.), I get the following > > every time I try to build my kernel, after it compiles a few files: > > > > gcc: Internal compiler error: program cc1 got fatal signal 11 > > cpp: output pipe has been closed > > > > Anyone seen this? What's wrong? > > Not too long ago, I started getting this on a firewallish box building > a 2.2.14 kernel after doing a major kernel reconfig. I suspect that it > may have been related to including a number of the 'IP Advanced Router' > options, but I didn't bother trying to isolate the exact cause. (This same > box had successfully compiled its previous 2.2.14 kernel.) > > Before trying to track down the offending option, I copied over the 2.2.16 > source, and (with the same kernel config) it compiled just fine. > > -- > "Two words: Windows survives." - Craig Mundie, Microsoft senior strategist > "So does syphillis. Good thing we have penicillin." - Matthew Alton > Geek Code 3.1: GCS d- s+: a- C++ UL++$ P+>+++ L+++>++++ E- W--(++) N+ o+ > !K w---$ O M- V? PS+ PE Y+ PGP t 5++ X+ R++ tv b+ DI++++ D G e* h+ r++ y+ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: tclug-list-unsubscribe at mn-linux.org > For additional commands, e-mail: tclug-list-help at mn-linux.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: tclug-list-unsubscribe at mn-linux.org For additional commands, e-mail: tclug-list-help at mn-linux.org