In article <1992Aug18.001710.10722@sol.UVic.CA> pmacdona@sanjuan (Peter MacDonald) writes:
quoted text
>In article <l90346INN8sa@ozona.cs.utexas.edu> jefftep@cs.utexas.edu (Jeffrey Grills) writes:
>>In article <1992Aug17.153437.25068@cs.tu-berlin.de> mackpei@cs.tu-berlin.de (Xue-Jun Pei) writes:
>>>I got the following error while trying to recompile 0.96c with GCC
>>>2.2.2:
[deleted]
quoted text
>>>gcc: Internal compiler error: program cc1 got fatal signal 11
>>>make: *** [init/main.o] Error 1
>>>Sorry for it has been mentioned before, I couldn't find it.
>>>Any help would be appreciated!
>Seems I am seeing the same problem, since I have started using
>2.2.2d.
>Peter.

I was having that sort of problem myself, though I think it might have
admitted to being the cpp getting the signal; anyway, something in gcc
gets "fatal signal 11", so I gcc -E'd the file, same thing.
So I looked and discovered that between the MCC 0.96 base distribution
and the then-current MCC gcc disks, I had two different (diff: binariy files
cpp and /lib/cpp differ) copies of cpp, so I moved one to cpp~, symlinked,
and everything worked fine.  I don't know why it started breaking, or what
two cpp's were doing, but that fixed it.  See if that's your problem too.

        Keith
(rohrer@fncrd0.fnal.gov)
-- 
Disclaimer: None of Grinnell College, URA, Fermilab, and any other affiliated
persons or orginizations have licensed my ideas or opinions, and thus are
not entitled to any which may appear above.