Re: [Flightgear-devel] Internal compiler error

2002-10-03 Thread Clarence Bakirtzidis
: Wednesday, October 02, 2002 11:57 PM Subject: RE: [Flightgear-devel] Internal compiler error Sig 11 errors during large compiles are often symptomatic of RAM problems (http://www.bitwizard.nl/sig11/). I don't know whether this applies to Cygwin as well as Linux, but it might. I doubt

Re: [Flightgear-devel] Internal compiler error

2002-10-03 Thread Julian Foad
Andy Ross wrote: http://www.memtest86.com/ I haven't noticed random crashes or corruption in the two years I've been running my current PC, but I decided to try this anyway. Most of the tests showed no problems, but the block move tests found thousands of errors, mostly in a particular

[Flightgear-devel] Internal compiler error

2002-10-02 Thread Clarence Bakirtzidis
Hi all... I hope this is not a repetitive question (I tried looking through some of the archives and found a similar question, but the answer didn't help me). When I try compiling either plib, simgear, metakit, or flightgear I keep getting "Internal compiler error" at seemingly random

RE: [Flightgear-devel] Internal compiler error

2002-10-02 Thread Richard Bytheway
of it. As an aside, you may want to switch to plib 1.6.0, simgear 0.2.0 and FlightGear 0.8.0/0.9.0 when you get things working. Richard -Original Message- From: Clarence Bakirtzidis [mailto:[EMAIL PROTECTED]] Sent: 02 October 2002 2:41 pm To: flightgear-devel Subject: [Flightgear-devel] Internal

Re: [Flightgear-devel] Internal compiler error

2002-10-02 Thread Curtis L. Olson
In the past I've seen these sorts of errors and behavior caused by both memory problems and CPU overheating. I would be surprised if it wasn't some sort of hardware problem. Curt. Clarence Bakirtzidis writes: Hi all... I hope this is not a repetitive question (I tried looking through some

Re: [Flightgear-devel] Internal compiler error

2002-10-02 Thread Andy Ross
Richard Bytheway wrote:a As mentioned in the Sig11 FAQ (link above), ensure that all the hardware in the PC is the correct spec, and that nothing is overclocked. Try underclocking as a possible workaround. If your RAM is on more than one stick, try removing different parts of it. Oddly, that