At 02:18 AM 5/17/98 -0400, Ray Curtis wrote:
>>>>>> "rs" == Richard Sharpe <[EMAIL PROTECTED]> writes:
>
>rs> Hi,
>rs> I tried compiling the 3.0.32 kernel with the IPChains stuff in it on my
>rs> Cyrix-based machine last night, and I got a rude shock.
>
>rs> The build failed with the following messages:
>
>rs> gcc: Internal compiler error: program cc1 got fatal signal 11
>
>This is usually the result of a hardware problem concerning memory.
>
>Check out:
>
>http://www.bitwizard.nl/sig11/

When I checked out this location, I got an even ruder shock:

>Others have noted the following possibilities: 
>     Red Hat 5.0 crashes for some people while installing. Others are only 
>    running into problems when compiling the kernel. It seems that the gcc
>    that comes with Red Hat 5.0 is odd in the respect that it crashes on 
>    Cyrix processors when compiling the kernel. This is VERY odd. I would
>    think that the only way that this can be the case is whent he
>    Cyrix has a bug that has gone undetected all this time, and reliably 
>    gets triggered when THAT gcc compiles the Linux kernel. Anyway, if 
>    you just want compile a kernel, you should get the 
>    gcc-compiled-for-glibc from sunsite. I don't know of a workaround if
>    your system crashes while installing, except for installing a minimal
>    base and then adding packages using 'glint' or 'rpm'. 

My, my. I certainly have compiled the kernel before under RH4.2, but not
under RH5.0. 

Oh well, its off to Sunsite I go.

>-- 
>Curtis Consulting
>mailto:[EMAIL PROTECTED]
>http://www.clark.net/pub/ray


Regards
-------
Richard Sharpe, [EMAIL PROTECTED], NIC-Handle:RJS96
NS Computer Software and Services P/L, 
Ph: +61-8-8281-0063, FAX: +61-8-8250-2080, 
Samba, Linux, Apache, Digital UNIX, AIX, Netscape, Stronghold, C, ...


-- 
  PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
         To unsubscribe: mail [EMAIL PROTECTED] with 
                       "unsubscribe" as the Subject.

Reply via email to