[Gerald Combs <gerald@xxxxxxxx>]

On Tue, 15 Aug 2000, Guy Harris wrote:

> On Tue, Aug 15, 2000 at 11:48:52AM -0400, Wendy A. Verschoor wrote:
> > Trying to compile ethereal 0.8.10 on a Red Hat Linux machine, uname -a
> > says: 
> 
> 	...
> 
> > gcc -DHAVE_CONFIG_H -I. -I. -I.     -Wall -g -O2 -I/usr/lib/glib/include
> > -c libpcap.c
> > gcc: Internal compiler error: program cc1 got fatal signal 11
> 
> 	...
> 
> > how can i fix this?
> 
> By telling Red Hat support that there's a GCC bug that causes it to get
> a SIGSEGV ("signal 11") when it compiles the "libpcap.c" file from
> Ethereal 0.8.10, and asking them if there's a fix to GCC that makes it
> not get a SIGSEGV.

This might be due to the way Linux interacts with the particular hardware
it's running on.  In the past, various people have run into signal 11
errors when compiling large packages (such as the kernel or libc).  There
is a FAQ on the subject at http://www.bitwizard.nl/sig11/ .  Wendy, what
happens when you type 'make' again after the error appears?  Does it
proceed any further, or does it still die on libpcap.c?