From owner-freebsd-questions  Fri Feb 27 09:47:42 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA26239
          for freebsd-questions-outgoing; Fri, 27 Feb 1998 09:47:42 -0800 (PST)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from top.monad.net (root@top.monad.net [204.97.16.3])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26226
          for <questions@FreeBSD.ORG>; Fri, 27 Feb 1998 09:47:30 -0800 (PST)
          (envelope-from vdk@chaosphere.com)
Received: from logrus.chaosphere.com (logrus.top.monad.net [206.231.108.252])
	by top.monad.net (8.8.8/What) with SMTP id MAA12062
	for <questions@FreeBSD.ORG>; Fri, 27 Feb 1998 12:47:24 -0500 (EST)
Date: Fri, 27 Feb 1998 12:49:08 -0500 (EST)
From: Obi Wan Oblivion <vdk@chaosphere.com>
To: questions@FreeBSD.ORG
Subject: make world still failing on 2.2.5-RELEASE
In-Reply-To: <19980223095328.47451@iii.co.uk>
Message-ID: <Pine.BSF.3.96.980227124148.28018A-100000@logrus.chaosphere.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 23 Feb 1998 nik@iii.co.uk wrote:

> On Fri, Feb 20, 1998 at 12:50:01PM -0500, Obi Wan Oblivion wrote:
> >    cc: Internal compiler error: program cc1 got fatal signal 10
> 
> <snip>
> 
> >    Internal compiler error.
> 
> You have dodgy hardware. It may be a flaky RAM chip, or it might be an
> unnoticed bad spot on your disk that's corrupting swap. Or it might be 
> that your CPU is overheating.

Okay,

I now have 128MB RAM, brand new.  No swap is being used during the build
process now.  I run:

     make buildworld

after CVSupping to stable and the build now dies with:

   cc -O -I/usr/src/usr.bin/make   -I/usr/obj/usr/src/tmp/usr/include -c
   /usr/src/usr.bin/make/for.c
   cc: Internal compiler error: program cc1 got fatal signal 11
   *** Error code 1

   Stop.
   *** Error code 1

Which seems to indicate that something is still wrong.

My question:  Is there something that will let me test my components and
tell me exactly what's going wrong?  I can certainly replace everything in
my system, but I'd rather not have to go through the hassle.

Is there something specific I can look for?  Any help would be
appreciated.

Thanks!

-Jeff

Transformers - They're more than meets the eye!




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