From owner-freebsd-stable  Tue Nov 30 10:55:24 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from misha.cisco.com (misha.cisco.com [171.69.206.50])
	by hub.freebsd.org (Postfix) with ESMTP id 09CF115805
	for <freebsd-stable@FreeBSD.ORG>; Tue, 30 Nov 1999 10:55:03 -0800 (PST)
	(envelope-from mi@misha.cisco.com)
Received: (from mi@localhost)
	by misha.cisco.com (8.9.3/8.9.1) id NAA50402;
	Tue, 30 Nov 1999 13:54:28 -0500 (EST)
	(envelope-from mi)
Message-Id: <199911301854.NAA50402@misha.cisco.com>
Subject: Re: Today's Buildworld Fails
In-Reply-To: <4.2.2.19991130133851.014b3100@216.67.12.69> from Forrest Aldrich
 at "Nov 30, 1999 01:39:33 pm"
To: Forrest Aldrich <forrie@forrie.com>
Date: Tue, 30 Nov 1999 13:54:28 -0500 (EST)
Cc: freebsd-stable@FreeBSD.ORG
Reply-To: mi@aldan.algebra.com
From: Mikhail Teterin <mi@aldan.algebra.com>
X-Mailer: ELM [version 2.4ME+ PL60 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Forrest Aldrich once wrote:

> cc -O -pipe   -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/mtree/compare.c
> cc: Internal compiler error: program cc1 got fatal signal 11
> *** Error code 1
 
> The machine in question has tons of RAM, so that's not the issue.

It probably is  :) This, I believe,  is one of the GNU-C  FAQs. The most
probable cause is the buggy  RAM and/or overclocking. Try restarting the
build. If it goes  on smoothly this time, or fails  in a different spot,
you have the hardware problem.

	-mi


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