Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 25 Nov 2000 12:41:40 -0800 (PST)
From:      Tom <tom@uniserve.com>
To:        "David A. Bader" <dbader@eece.unm.edu>
Cc:        dickey@herndon4.his.com, freebsd-stable@freebsd.org
Subject:   Re: http://x68.deja.com/=dnc/[ST_rn=ps,ST_m=ps]/getdoc.xp?AN=697444318&CO
Message-ID:  <Pine.BSF.4.05.10011251238430.24476-100000@shell.uniserve.ca>
In-Reply-To: <200011251946.MAA14282@eece.unm.edu>

next in thread | previous in thread | raw e-mail | index | archive | help

On Sat, 25 Nov 2000, David A. Bader wrote:

> Here is the compile line. Are the "-I" include directories okay?
> 
> cc -fpic -DPIC -O -pipe -I. -I/usr/src/lib/libncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/ncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/include -Wall -DFREEBSD_NATIVE -DNDEBUG -DHAVE_CONFIG_H -DTERMIOS -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/alloc_entry.c -o alloc_entry.So
> cc: Internal compiler error: program cc1 got fatal signal 11
> *** Error code 1

  The compiler crashed.  If there was a problem with the include
directories, you'd expect the compiler to output an error about that and
stop.

  However, if gcc stops with a signal 11 (segment fault), either the
compiler is buggy or damaged, the OS is buggy or damaged, or the hardware
is buggy or damaged.

Tom



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.10011251238430.24476-100000>