From owner-freebsd-current@FreeBSD.ORG Tue Aug 19 10:33:49 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B6A3416A4BF for ; Tue, 19 Aug 2003 10:33:49 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id E35C843FBD for ; Tue, 19 Aug 2003 10:33:48 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.9/8.12.9) with ESMTP id h7JHXlQX076440; Tue, 19 Aug 2003 10:33:47 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.9/8.12.9/Submit) id h7JHXi0L076439; Tue, 19 Aug 2003 10:33:44 -0700 (PDT) Date: Tue, 19 Aug 2003 10:33:44 -0700 From: "David O'Brien" To: Stefan Bethke Message-ID: <20030819173344.GB76279@dragon.nuxi.com> References: <2147483647.1061141322@[172.22.33.128]> <20030817224741.T320@alpha.siliconlandmark.com> <20030818030054.GA58513@dragon.nuxi.com> <20030818211512.GB47959@garage.freebsd.pl> <844382971.1061287624@[10.0.1.3]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <844382971.1061287624@[10.0.1.3]> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.1-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-current@freebsd.org cc: Andre Guibert de Bruet Subject: Re: CPUTYPE considered harmful? (was: Lot's of SIGILL, SIGSEGV) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2003 17:33:50 -0000 On Tue, Aug 19, 2003 at 10:07:04AM +0200, Stefan Bethke wrote: > >I think he is right, because when upgrading host where was gcc3.2 to > >current -CURRENT (with gcc3.3) 'make world' builds make(1) in first > >place and it is builded by gcc3.2 with CPUTYPE=p4, so it will be broken. > > > >So gcc have to be upgraded in first place (with CPUTYPE=p3). > > Hhm, sounds reasonable. > > However, I had the exact same problem updating from a 5.1-RC to a recent > current on a P III 900, and there, I had CPUTYPE=p3 in make.conf. You must have a early 5.1-RC. Later ones and the release treated CPUTYPE=p4 as an alias for CPUTYPE=p3.