Mail Archives: djgpp/2000/05/31/08:02:27
J.W. Dare <jwdare AT novia DOT net> 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.
- Raw text -