Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!uunet!gatech!purdue!mentor.cc.purdue.edu!rahnds From: rahnds@mentor.cc.purdue.edu (Dale Rahn) Newsgroups: comp.unix.bsd Subject: Re: [386BSD] cc1 fatal error & more! Message-ID: <BuEAx4.JIq@mentor.cc.purdue.edu> Date: 11 Sep 92 03:55:51 GMT References: <0efk57e00WB60gg0pN@andrew.cmu.edu> <6703@vtserf.cc.vt.edu> <1992Sep11.012623.14965@fcom.cc.utah.edu> Organization: Purdue University Lines: 43 In article <1992Sep11.012623.14965@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes: >In article <6703@vtserf.cc.vt.edu> linkt@GroupW.cns.vt.edu (Tim Link) writes: >>In article <0efk57e00WB60gg0pN@andrew.cmu.edu> tj2n+@andrew.cmu.edu (Tao Jiang) writes: >>> >>>Hi, I tried to compile a program and got the cc1 fata error like: >>>cc -I.. -I../.. -O -c fogdeck.c >>>cc: Program cc1 got fatal signal 6. >>>*** Error code 1 >>> > > Make has a terrific leak. I compiled up a different version (sorry, >proprietary). You may want to try gnumake. > >I used to get around the problem by doing: > > make -n > foo > vi foo > sh foo I have been having this problem getting MetaFont to compile. While using Terry's solution I found that the program would not compile using the command line from the shell but did compile when i left off the -O option, it compiled correctly gcc -g -O -I.. -c mf1.c gcc: Program cc1 got fatal signal 6. *** Error code 1 but gcc -g -I.. -c mf1.c returns with no errors and creates mf1.o which will compile and link with no errors. is it possible that the -O option of gcc uses too much memory (i have 8M real, 16M swap but have X386 running) or could there be a problem with gcc. The problem was fixed with a patch to the code which reduced various arrays in the program. but this was not useful to me (it did not allow all of the characters for some fonts. Dale Rahn rahnds@mentor.cc.purdue.edu