From owner-freebsd-current  Fri Jan 14  6: 9:21 2000
Delivered-To: freebsd-current@freebsd.org
Received: from void.dynip.com (hobax1-247.dialup.optusnet.com.au [198.142.190.247])
	by hub.freebsd.org (Postfix) with ESMTP id B043E14CE3
	for <freebsd-current@FreeBSD.ORG>; Fri, 14 Jan 2000 06:09:06 -0800 (PST)
	(envelope-from death@southcom.com.au)
Received: from windows (windows.void.net [192.168.1.2])
	by void.dynip.com (Postfix) with ESMTP
	id 4D1F755BA; Sat, 15 Jan 2000 01:08:52 +1100 (EST)
Message-Id: <4.2.2.20000115010409.01b82260@mail.southcom.com.au>
X-Sender: death@mail.southcom.com.au
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Sat, 15 Jan 2000 01:08:50 +1100
To: Lamont Lucas <lamont@cluepon.com>
From: james <death@southcom.com.au>
Subject: Re: Problems attempting to upgrade from 3.4-stable to -current
Cc: freebsd-current@FreeBSD.ORG
In-Reply-To: <Pine.BSF.4.10.10001132321480.317-100000@clavin.cluepon.com
 >
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 23:38 13/1/2000 -0800, Lamont Lucas wrote:

>Hi, I've been trying unsuccessfully for two days to upgrade to -current on
>one of my machines at home, and was hoping there might be some suggestions
>from the group I could try.
>
>This is the consistant error off of today's -current tree:
>
>cc -O -pipe -elf -Wall -fkeep-inline-functions
>-I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/csu/i386-elf/crt1.c -o
>crt1.o
>cc: Internal compiler error: program cc1 got fatal signal 12
>*** Error code 1

<snip>

>Any suggestions or work arounds?

Hi,

I had this same problem - although the signal 12 was coming during 
installworld when it was installing 'test' or something. My solution was to 
just download a snapshot of current, and use the 'upgrade' option on the 
install disks. Worked fine. I read on this list about the same time that 
there should be no problems at all upgrading from 3.4-STABLE to 4.0-CURRENT 
by make world'ing, and that signal 12 really does always mean a hardware 
failure - but this is garbage.

Cheers





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