Sig11s are usually indicative of hardware faults (usually memory)
There is a Sig11 FAQ somewhere, but unfortunately I don't have the URL to
hand.
Hope this helps!
Barry Zubel
Technical Manager
City Mutual Ltd
-----Original Message-----
From: RHS Linux User <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Tuesday, January 26, 1999 8:51 AM
Subject: Re: Compilation error
:
:It may not apply in your case, but I once had a rash of SIGNAL 11 errors
:compiling 2.0.27 on a cyrix processor with config flag set to a i486.
:Reseting the flag back to a i386 eliminated the errors.
:
:Just a thought,
:Gerald Bryant
:
:
: On Thu, 14 Jan 1999, Clifford Wesley Fulford wrote:
:
:> Trying to compile ftape-4.02 with gcc 2.7 ( i386-redhat-linux-gcc)
:> Cyrix 686.
:> uname -a
:> 2.0.32 #1 Wed Nov 19 00:46:45 EST 1997 i486 unknown
:>
:> I get the following error
:> gcc: Internal compiler error: program cc1 got fatal signal 11
:> make[2]: *** [ftape-bsm.o] Error 1
:> make[1]: *** [modules] Error 2
:> make: *** [all] Error 2
:>
:> Can anyone advise?
:>
:> Clifford
:>
:> --
:> ========================================================================
:> Clifford W Fulford | CBF International | [EMAIL PROTECTED]
:>
:> ========================================================================
:>
:>
:
:
