🚀 go-pugleaf

In article <505i9l$620@Nntp1.mcs.net>, Dale Van Beveren wrote:
>hgriggs@mpx.com.au (Henry Griggs) wrote:
>
>>I'm trying to upgrade my compiler from gcc v2.4 to gcc 2.5.8. I've
>>followed the instructions as best I can, and got to the stage where I
>>am building the stage 1 compiler. When it gets to the part where it's
>>doing
>
>>-muldi3
>>-divdi3
>>-moddi3
>>...
>>-udivmoddi4
>
>>it then gives me this error: 
>
>>xgcc: Internal compiler error: program cc1 got fatal signal 11
>>make: *** [libgcc2.a] Error 127
>
>>Can anyone shed any light on the fatal signal 11?

I can't tell you what to do about it -- but there has been some
discussion on this signal 11 lately.  If you have a pentium the
speed may be a problem.  There is a way out of the problem --
you will have to either look at the archives of comp.os.linux.*
or get lucky with an answer from an authoratative source.  Just
a hint for you to follow up on.

Best Regards,
 
Joe Hartmann 
-------------------------------------------------------------
First Student at the:

      Linux Academy in the Sunshine Town of Newport, NH

Happy GPL and all that!
-------------------------------------------------------------

>
>>Henry
>>*****
>>hgriggs@mpx.com.au
>>Sydney, Australia.
>I'm relatively new at linux but, I had the same error upgrading to
>2.0.12 of slackware linux. Solution was to turn off external cache
>when needing to compile the kernel. It works, the kernel, fine with
>cache back on. Quirk with the compiler?
>Dale
>grlic920@mcs.net
>Lockport, IL 
>
>