From owner-FreeBSD-users-jp@jp.freebsd.org  Tue Nov 12 23:31:44 1996
Received: by jaz.jp.freebsd.org (8.7.3+2.6Wbeta5/8.7.3) id XAA05386
	Tue, 12 Nov 1996 23:31:44 +0900 (JST)
Received: by jaz.jp.freebsd.org (8.7.3+2.6Wbeta5/8.7.3) with ESMTP id XAA05381
	for <FreeBSD-users-jp@jp.freebsd.org>; Tue, 12 Nov 1996 23:31:43 +0900 (JST)
Received: from ppp.at-m.or.jp (ppp204.at-m.or.jp [202.232.201.204]) by mail.at-m.or.jp (8.7.5/3.4Wbeta5-) with ESMTP id XAA22854; Tue, 12 Nov 1996 23:30:24 +0900 (JST)
Received: from x (localhost [127.0.0.1]) by ppp.at-m.or.jp (8.7.5/3.4Wbeta5-96110600) with ESMTP id XAA00389; Tue, 12 Nov 1996 23:35:15 +0900
Message-Id: <199611121435.XAA00389@ppp.at-m.or.jp>
To: FreeBSD-users-jp@jp.freebsd.org, kane@kane.shimosuwa.nagano.jp
From: murakami@mail.at-m.or.jp
In-Reply-To: Your message of "Tue, 12 Nov 1996 23:07:11 +0900"
References: <199611121407.XAA00493@tatsu.kane.shimosuwa.nagano.jp>
X-Mailer: Mew version 1.06 on Emacs 19.28.1, Mule 2.3
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-2022-jp
Date: Tue, 12 Nov 1996 23:35:14 +0900
Reply-To: FreeBSD-users-jp@jp.freebsd.org
X-Distribute: distribute [version 2.1 (Alpha) patchlevel=19]
X-Sequence: FreeBSD-users-jp 6191
Subject: [FreeBSD-users-jp 6191] Re: cc faild with signal 11
Errors-To: owner-FreeBSD-users-jp@jp.freebsd.org
Sender: owner-FreeBSD-users-jp@jp.freebsd.org

$BB<>e$H$b$&$7$^$9(B

> $B6bH"$H?=$7$^$9!#(B
> 
> FreeBSD 2.1.5R $B$G%+!<%M%k$N:F9=C[$r9T$C$?$H$3$m(B cc (cpp ?) $B$,(B
> signal 11 $B$GMn$A$F$7$^$$$^$7$?!#:F$S(B make $B$9$k$H7QB3$7!"#22s7+$jJV$7$?(B
> $B$H$3$m%+!<%M%k$N(B make $B$O=*N;$7$?$N$G$9$,!"%7%9%F%`$N$I$3$+$,$*$+$7$$$N(B
> $B$G$7$g$&$+!)(B

Linux$BMQ$N(BDocument$B$N0lIt$G$9$,!"0zMQ$7$^$9(B

GCC Signal 11 error
===================

   Many people have been reporting messages like the following,
especially when compiling a new kernel:

   `gcc:  Internal compiler error:  program cc1 got fatal signal 11'.

   This is NOT a kernel bug.  Rather, these messages are generally
caused by hardware problems.  See http://www.bitwizard.nl/sig11/ for
the sig11 FAQ.

