Re: [Flightgear-devel] Internal compiler error
Thanks for your help guys. It turns out it was a RAM problem afterall. I borrowed some RAM from a friend and tried compiling with it installed in my machine and everything works fine. The suspect RAM I had was a RAmos 512MB PC133 CL3 SDRAM chip. I borrowed two 128MB Hyundai SDRAM chips (one is PC100 and the other PC133). I might try to do a swap with my friend for a while since my RAM only seemed to cause problems compiling but not for other normal applications. Regards, Clarence. - Original Message - From: Richard Bytheway [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: 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 that this is a problem with the source as many people have built all the source you mention without problem, myself included on W2K/Cygwin. 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. 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 ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Internal compiler error
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 bit of the data bus. I was surprised and concerned! This is running at rated speed; I haven't yet tried under-clocking. - Julian ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Internal compiler error
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 points. If I re-run the make, sometimes it successfully compiles the file it failed on and then fails again on a different file. Occassionally it takes up to 10 reties before a file will compile. On one occassion I managed to build everything using this tedious approach but flightgear would not run, it kept generating segmentation faults. When I download the pre-built binaries for flightgear it runs without any problems. The strange thing is I get the "Internal compiler error" when compiling under Windows 2000/Cygwin and under Red Hat Linux 7.3! Does this mean it is a hardware-related problem? I have no problems running any other software. My setup is Pentium III 600EB 512MB PC133 SDRAM 60GB HDD, Leadtek GeForce 2 64MB, SBLive. Here is a sample run in plib which generates the "Internal compiler error" SAMPLE RUN START Administrator@ZELIOS-PENTIUM3 /usr/local/plib-1.4.2$ makeMaking all in srcmake[1]: Entering directory `/usr/local/plib-1.4.2/src'Making all in utilmake[2]: Entering directory `/usr/local/plib-1.4.2/src/util'make[2]: Nothing to be done for `all'.make[2]: Leaving directory `/usr/local/plib-1.4.2/src/util'Making all in jsmake[2]: Entering directory `/usr/local/plib-1.4.2/src/js'make[2]: Nothing to be done for `all'.make[2]: Leaving directory `/usr/local/plib-1.4.2/src/js'Making all in slmake[2]: Entering directory `/usr/local/plib-1.4.2/src/sl'make[2]: Nothing to be done for `all'.make[2]: Leaving directory `/usr/local/plib-1.4.2/src/sl'Making all in puimake[2]: Entering directory `/usr/local/plib-1.4.2/src/pui'make[2]: Nothing to be done for `all'.make[2]: Leaving directory `/usr/local/plib-1.4.2/src/pui'Making all in sgmake[2]: Entering directory `/usr/local/plib-1.4.2/src/sg'make[2]: Nothing to be done for `all'.make[2]: Leaving directory `/usr/local/plib-1.4.2/src/sg'Making all in ssgmake[2]: Entering directory `/usr/local/plib-1.4.2/src/ssg'c++ -DPACKAGE=\"plib\" -DVERSION=\"1.4.2\" -DWIN32=1 -DSTDC_HEADERS=1 -DHAVE_GL_GL_H=1 -DHAVE_GL_GLU_H=1 -DWIN32=1 -DGLUT_IS_PRESENT=1 -I. -I. -I../../src/sg-I../../src/util -I/usr/local/include -g -O2 -O6 -Wall -malign-double -I/usr/local/include -L/usr/local/lib -c ssgSimpleState.cxxssgSimpleState.cxx: In method `void ssgSimpleState::setTexture(char *, int = 1,int = 1, int = 1)':ssgSimpleState.cxx:632: Internal compiler error.ssgSimpleState.cxx:632: Please submit a full bug report.ssgSimpleState.cxx:632: See URL:http://www.gnu.org/software/gcc/bugs.html forinstructions.make[2]: *** [ssgSimpleState.o] Error 1make[2]: Leaving directory `/usr/local/plib-1.4.2/src/ssg'make[1]: *** [all-recursive] Error 1make[1]: Leaving directory `/usr/local/plib-1.4.2/src'make: *** [all-recursive] Error 1 Administrator@ZELIOS-PENTIUM3 /usr/local/plib-1.4.2$ SAMPLE RUN END I have tried several things to get this error to go away, including: * Removing the -O optimisation flags * Removing the -g debug option * Using -O3 -fomit-frame-pointer -DNDEBUG for CXXFLAGS as suggested in an old post Sometimes even ./configure abort and generates "Signal 11". The code versions I am using are: plib-1.4.2 SimGear-0.0.18 FlightGear-0.7.10 Any help would be greatly appreciated as I am trying to make some small modifications to FlightGear for a university project. I have been trying to compile flightgear on and off for a few weeks now. I have managed to get it to compile on Windows 2000/Cygwin on my PC at work without any problems, it's just my home PC which has this problem. Regards, Clarence.
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 that this is a problem with the source as many people have built all the source you mention without problem, myself included on W2K/Cygwin. 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. 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 compiler error 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). snip ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Internal compiler error
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 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 points. If I re-run the make, sometimes it successfully compiles the file it failed on and then fails again on a different file. Occassionally it takes up to 10 reties before a file will compile. On one occassion I managed to build everything using this tedious approach but flightgear would not run, it kept generating segmentation faults. When I download the pre-built binaries for flightgear it runs without any problems. The strange thing is I get the Internal compiler error when compiling under Windows 2000/Cygwin and under Red Hat Linux 7.3! Does this mean it is a hardware-related problem? I have no problems running any other software. My setup is Pentium III 600EB 512MB PC133 SDRAM 60GB HDD, Leadtek GeForce 2 64MB, SBLive. Here is a sample run in plib which generates the Internal compiler error SAMPLE RUN START Administrator@ZELIOS-PENTIUM3 /usr/local/plib-1.4.2 $ make Making all in src make[1]: Entering directory `/usr/local/plib-1.4.2/src' Making all in util make[2]: Entering directory `/usr/local/plib-1.4.2/src/util' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/usr/local/plib-1.4.2/src/util' Making all in js make[2]: Entering directory `/usr/local/plib-1.4.2/src/js' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/usr/local/plib-1.4.2/src/js' Making all in sl make[2]: Entering directory `/usr/local/plib-1.4.2/src/sl' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/usr/local/plib-1.4.2/src/sl' Making all in pui make[2]: Entering directory `/usr/local/plib-1.4.2/src/pui' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/usr/local/plib-1.4.2/src/pui' Making all in sg make[2]: Entering directory `/usr/local/plib-1.4.2/src/sg' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/usr/local/plib-1.4.2/src/sg' Making all in ssg make[2]: Entering directory `/usr/local/plib-1.4.2/src/ssg' c++ -DPACKAGE=\plib\ -DVERSION=\1.4.2\ -DWIN32=1 -DSTDC_HEADERS=1 -DHAVE_GL_ GL_H=1 -DHAVE_GL_GLU_H=1 -DWIN32=1 -DGLUT_IS_PRESENT=1 -I. -I. -I../../src/sg -I../../src/util -I/usr/local/include -g -O2 -O6 -Wall -malign-double -I/usr/ local/include -L/usr/local/lib -c ssgSimpleState.cxx ssgSimpleState.cxx: In method `void ssgSimpleState::setTexture(char *, int = 1, int = 1, int = 1)': ssgSimpleState.cxx:632: Internal compiler error. ssgSimpleState.cxx:632: Please submit a full bug report. ssgSimpleState.cxx:632: See URL:http://www.gnu.org/software/gcc/bugs.html for instructions. make[2]: *** [ssgSimpleState.o] Error 1 make[2]: Leaving directory `/usr/local/plib-1.4.2/src/ssg' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/plib-1.4.2/src' make: *** [all-recursive] Error 1 Administrator@ZELIOS-PENTIUM3 /usr/local/plib-1.4.2 $ SAMPLE RUN END I have tried several things to get this error to go away, including: * Removing the -O optimisation flags * Removing the -g debug option * Using -O3 -fomit-frame-pointer -DNDEBUG for CXXFLAGS as suggested in an old post Sometimes even ./configure abort and generates Signal 11. The code versions I am using are: plib-1.4.2 SimGear-0.0.18 FlightGear-0.7.10 Any help would be greatly appreciated as I am trying to make some small modifications to FlightGear for a university project. I have been trying to compile flightgear on and off for a few weeks now. I have managed to get it to compile on Windows 2000/Cygwin on my PC at work without any problems, it's just my home PC which has this problem. Regards, Clarence. !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0 Transitional//EN HTMLHEAD META content=text/html; charset=iso-8859-1 http-equiv=Content-Type META content=MSHTML 5.00.3315.2870 name=GENERATOR STYLE/STYLE /HEAD BODY bgColor=#ff DIVFONT face=Arial size=2Hi all.../FONT/DIV DIVnbsp;/DIV DIVFONT face=Arial size=2I hope this is not a repetitive question (I tried looking through some/FONT/DIV DIVFONT face=Arial size=2of the archives and found a similar question, but the answer didn't help/FONT/DIV DIVFONT face=Arial size=2me)./FONT/DIV DIVnbsp;/DIV DIVFONT face=Arial size=2When I try compiling either plib, simgear, metakit, or flightgear I/FONT/DIV DIVFONT face=Arial size=2keep getting Internal compiler error at seemingly random points./FONT/DIV DIVFONT face=Arial size=2If I re-run the make, sometimes it successfully
Re: [Flightgear-devel] Internal compiler error
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 FAQ fails to mention the single best tool for detecting these problems: http://www.memtest86.com/ Get this and run it. It's a boot image, so if you don't have a Linux installation (LILO and GRUB can run it just like a kernel) or a floppy, you may have to do some gymnastics. Leave it running overnight and see what you find. You'd be amazed at the number of working machines in the world have slightly bad RAM. One of my boxes, which seems perfectly stable, gets about 1 error every 10 hours. If you see any more than that, consider replacing your memory or motherboard. Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com Men go crazy in conflagrations. They only get better one by one. - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
