Hi,
> >Signal 11 usually either means a compiler bug or bad RAM. Try using
> >the BIOS configuration screen to increase the number of wait states on
> >your RAM, and see if that fixe it.
>
> In my BIOS setup, I have:
> ISA MEMORY WAIT STATE either (NORMAL, 1ns,2ns or 3 ns)
> ISA IO WAIT STATE ei
This is from the linux-admin faq:
Question 2.3 What could make GCC produce the "exiting on signal 11" message?
There is a good resource covering this subject avaliable on the Internet
at http://www.bitwizard.nl/sig11/.
Regards,
Marin
"Knowledge is not a crime. Some of
Ibrahim F Haddad wrote:
> > Signal 11 usually either means a compiler bug or bad RAM. Try using
> > the BIOS configuration screen to increase the number of wait states on
> > your RAM, and see if that fixe it.
>
> In my BIOS setup, I have:
> ISA MEMORY WAIT STATE either (NORMAL, 1ns,2ns or 3 n
Hello All,
>Signal 11 usually either means a compiler bug or bad RAM. Try using
>the BIOS configuration screen to increase the number of wait states on
>your RAM, and see if that fixe it.
In my BIOS setup, I have:
ISA MEMORY WAIT STATE either (NORMAL, 1ns,2ns or 3 ns)
ISA IO WAIT STATE either (
Ibrahim F Haddad wrote:
> "gcc: internal compile error: program cc1 got fatal signal 11"
This is usually caused by bad memory. Check your memory simms.
---
Henrik Nordström
Ibrahim F Haddad wrote:
> While compiling (a project of around 12500 lines) from within Xemacs -->
> Esc-x compile --> make -k
> I get the following error message:
> "gcc: internal compile error: program cc1 got fatal signal 11"
>
> The same error message is produced if i run make from the she
