All too familiar I'm afriad.....
Sig 11 is segmentation fault... GCC throws a SIG 11 almost by clockwork if
theres any RAM corruption... this is caused either by bad RAM or bad CPU
timing.....
Basically, I have got this NUMEROUS times with Cyrix CPU's.... Mabe your
CPU fan has stopped!
On Wed, 30 Dec 1998, Lucid Dream wrote:
> I don't suppose this error looks familiar to anyone?
>
> ----------------------------------------------------------------
> gcc -DTHE_FTAPE_MAINTAINER=\"[EMAIL PROTECTED]\"
> -DBROKEN_FLOPPY_DRIVER -DCONFIG_FT_PROC_FS -DCONFIG_FT_STD_FDC_0
> -DCONFIG_FT_INT_0=1 -DCONFIG_FTAPE_MODULE -DCONFIG_FT_INTERNAL_MODULE
> -DCONFIG_FT_TRAKKER_MODULE -DCONFIG_FT_BPCK_MODULE -DCONFIG_ZFTAPE_MODULE
> -DCONFIG_ZFT_COMPRESSOR_MODULE -D__KERNEL__ -I.
> -I../../include -I/usr/src/linux/include -m486 -malign-loops=2
> -malign-jumps=2 -malign-functions=2 -DCPU=586 -E -D__GENKSYMS__
> ftape_syms.c \
> | /sbin/genksyms ../../include/linux/modules 2> /dev/null; \
> fi
> gcc: Internal compiler error: program cpp got fatal signal 11
> make[2]: *** [../../include/linux/modules/ftape_syms.ver] Error 139
> make[2]: Leaving directory `/usr/local/ftape-4.02/ftape/lowlevel'
> make[1]: *** [modules] Error 2
> make[1]: Leaving directory `/usr/local/ftape-4.02/ftape'
> make: *** [all] Error 2
> ---------------------------------------------------------
>
> My apologies if this is a well-known problem and my tired brain has missed
> an obvious answer.
>
> -----------------
> Lucid Dream
> www.unixgeeks.org
>
James ([EMAIL PROTECTED])
Vortex Internet
My Windows unders~1 long filena~1, and yours?
