From owner-freebsd-current@FreeBSD.ORG Mon Mar 7 20:59:57 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 9F9301065673; Mon, 7 Mar 2011 20:59:57 +0000 (UTC) Date: Mon, 7 Mar 2011 20:59:57 +0000 From: Alexander Best To: George Liaskos Message-ID: <20110307205957.GA47557@freebsd.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: freebsd-current@freebsd.org Subject: Re: r219385 build error. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Mar 2011 20:59:57 -0000 On Mon Mar 7 11, George Liaskos wrote: > Hi, > > The following error occurs when i try to build r219385. > > cc -O2 -pipe -march=core2 -DHAVE_CONFIG_H > -I/usr/src/kerberos5/tools/make-roken/../../include -std=gnu99 -c > make-roken.c > make-roken.c:1: error: bad value (core2) for -march= switch > make-roken.c:1: error: bad value (core2) for -mtune= switch > /usr/src/kerberos5/tools/make-print-version/../../../crypto/heimdal/lib/vers/make-print-version.c:1: > error: bad value (core2) for -march= switch > /usr/src/kerberos5/tools/make-print-version/../../../crypto/heimdal/lib/vers/make-print-version.c:1: > error: bad value (core2) for -mtune= switch > *** Error code 1 > 1 error > *** Error code 2 > *** Error code 1 > 1 error > *** Error code 2 > 2 errors > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > > Sure enough i have CPUTYPE?=core2 in make.conf which it doesn' t > expand to nocona after the latest patches. that's because the latest gcc commits have support for core2 and thus it no longer is being expanded to nocona. please note that having core2 in make.conf has always been *wrong*. hence the need to reset it to nocona. the best way to fix this would be to set CPUYTYPE?=native. if you want core2 support now's the chance to actually get it. just update world and you can use CPUTYPE?=core2 and this time it *really* is supported. ;) cheers. alex > > Regards -- a13x