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
