From owner-freebsd-stable Thu Mar 14 6:42:18 2002 Delivered-To: freebsd-stable@freebsd.org Received: from shikima.mine.nu (pc1-card4-0-cust77.cdf.cable.ntl.com [62.252.49.77]) by hub.freebsd.org (Postfix) with ESMTP id 6CD0C37B405 for ; Thu, 14 Mar 2002 06:42:16 -0800 (PST) Received: from rasputin by shikima.mine.nu with local (Exim 3.35 #1) id 16lWQn-000335-00; Thu, 14 Mar 2002 14:42:13 +0000 Date: Thu, 14 Mar 2002 14:42:13 +0000 From: Rasputin To: "Callum M. Duncan" Cc: stable@freebsd.org Subject: Re: Recent STABLE build killed compiler? Message-ID: <20020314144213.A11686@shikima.mine.nu> Reply-To: Rasputin References: <20020313215116.B7433@bebox.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020313215116.B7433@bebox.net>; from callum@bebox.net on Wed, Mar 13, 2002 at 09:51:16PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Callum M. Duncan [020314 02:51]: > It appears that a recent build of STABLE killed my ability to > compile things. :-( > > Now when I attempt to compile _anything_ I get > > cc: Internal compiler error: program cc1 got fatal signal 11 > everything in ports...) Do you have CPUTYPE set? I got this one when I used CPUTYPE=k6-2 Since then CPUTYPE=k6 has been fine. Backing out a broken world/compiler can be - interesting, but you can normally do it if you know someone who you can scp virgin binaries off (assuming you have a working scp). It should be possible to restore broken binaries from CD too. -- If you can survive death, you can probably survive anything. Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message