From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: Internal compiler error Date: 31 May 2000 11:06:21 GMT Organization: Aachen University of Technology (RWTH) Lines: 29 Message-ID: <8h2rnd$i7n$1@nets3.rz.RWTH-Aachen.DE> References: NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 959771181 18679 137.226.32.75 (31 May 2000 11:06:21 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 31 May 2000 11:06:21 GMT Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com J.W. Dare wrote: > While using djgpp for my first semester C++ programming class > assignments, approximatly half of the time the compiler quits with > error messages similar to the two below. A second attempt will > usually compile the code. As Manni Heumann alrady suggested somewhat subtly in his reply, this type of behaviour more often than not means that your hardware is bad, or at least badly configured. Running 'gcc' is quite a sensitive test for any kind of hardware-induced inconsistency in a PC. That's why experienced PC hardware tuners usually try a Linux kernel compilation with several gcc's running in parallel to test a newly tuned machine. A CPU that has gone beyond it's temperature limits because the fan is dead is the usual reason if this happens with an 'old' machine that has been working reliably, before. If you exchanged any crucial parts of it (RAM, CPU, the Motherboard), or played with the BIOS setup options to speed it up, chances are that those changes are the cause. In a brand-new box, this usually is caused by bad RAM chips. Happens more often than most vendors are willing to admit... Windows 9x often still seems to work, on such a machine with flakey memory. Draw your own conclusion about what that tells about the inner quality of that OS... -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.