Re: internal compiler errors

[whizbang <whizbang nbnet nb ca>]

toneman@phil.uu.nl wrote:

> On Sun, 29 Aug 1999, whizbang wrote:
>
> whizba> my compiler seems to have recently broken. it was working fine until the
> whizba> latest batch of gnome updates, but now whenever i try to to compile a
> whizba> gnome/gtk program i get an error like
> whizba>
> whizba> Project.cc:172: Internal compiler error.
> whizba> Project.cc:172: Please submit a full bug report to
> whizba> `egcs-bugs@egcs.cygnus.com'.
> whizba> Project.cc:172: See <URL:http://egcs.cygnus.com/faq.html#bugreport> for
> whizba> details.make[2]: *** [Project.o] Error 1
> whizba> make[2]: Leaving directory `/tmp/grpmw-0.1/source'
> whizba> make[1]: *** [all-recursive] Error 1
> whizba> make[1]: Leaving directory `/tmp/grpmw-0.1'
> whizba> make: *** [all-recursive-am] Error 2
> whizba>
> whizba> or something similar (depending on the package) the error always includes
> whizba> the phrase "internal compiler error". i am not a programmer, so i don't know
> whizba> if this qualifies for a gnome bug report, but i do know that it is happening
> whizba> on gnome/gtk programs, and that i have not installed anything that would
> whizba> modify my compiler or other libs (including gtk itself) since it broke.
> whizba>
> whizba> my system is redhat 6.0 on a k6-2 400 and i have all the redhat errata
> whizba> updates, and XF86 3.3.4. here are my gnome versions
>
> Any chance you overclocked your system. I overclocked my
> k6-2 just a little, and all of a sudden I was getting the same
> kind of errors :(
>
> I just assumed this was similar to the old gcc Signal 11 error
> (i.e. Your hardware sucks ;-)
>

you win. my hardware suck. i am such an ass :-P
thanks, you've saved my life (what's a linux box without a working cc?)

>
> Greetings,
>
> Michiel

--
Dr. Whiz-Bang
whizbang@nbnet.nb.ca
Don't waste your time here --> http://whizbang.penguinpowered.com