This happens sometimes when overclocking your processor ... other times .. well
yoiu got me, but if you rerun the compile command again it will pick up where
it left off. I ve had trouble with this myself... if your using bash or tcsh ..
just hit the up arrow and hit enter.
which processor do you have btw ?
On 09-Apr-99 Mike Werner wrote:
> [EMAIL PROTECTED] wrote:
>>
>> Hello,
>> I've been trying to make modules for my kernel 2.2.5 for slackware 3.6. I
>> got the following error message:
>> gcc internal compiler error. Program cc1 got fatal signal 11.
>> Can anyone tell me what this means and how to fix it? If you need
>> system
>> information let me know, but I myself am unsure which information is
>> appropriate for this error.
>> Thanks.
>> Dave,.
>
> This usually signals a hardware problem. For more info take a look at
> http://www.bitwizard.nl/sig11/
> It's explained there better than I could, but basically one of the more
> common causes is dodgy memory. The BIOS "memory test" is pretty much a
> joke - don't rely on it. There're causes other than memory - that URL
> above is quite detailed on what the different causes are and how to
> figure out what the actual problem is.
> --
> Mike Werner KA8YSD | "Where do you want to go today?"
> ICQ# 12934898 | "As far from Redmond as possible!"
> '91 GS500E |
> Morgantown WV | Only dead fish go with the flow.
>
> -----BEGIN GEEK CODE BLOCK-----
> Version: 3.1
> GU d-@ s:+ a- C++>$ UL++ P+ L+++ E W++ N++ !o w--- O- !M V-- PS+ PE+
> Y+ R+ !tv b+++(++++) DI+ D--- G e*>++ h! r++ y++++
> ------END GEEK CODE BLOCK------
----------------------------------
Tony Hernandez ::: Intellon Corporation
MCP A+
Workstation Administrator
----------------------------------
