From owner-freebsd-current@FreeBSD.ORG Mon Mar 7 21:19:41 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C100106564A for ; Mon, 7 Mar 2011 21:19:41 +0000 (UTC) (envelope-from geo.liaskos@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 027938FC17 for ; Mon, 7 Mar 2011 21:19:40 +0000 (UTC) Received: by gyh4 with SMTP id 4so2059786gyh.13 for ; Mon, 07 Mar 2011 13:19:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=YolLko/Qq4obdtULW3x6Aj+l49MWXsW3vvtdRSADOAo=; b=S3c7uGHCLpJaD2sBEl5ZHzXROdiuLp3V8p96nAZVT4BgUgZc55HrktrPnygVUSjq4j nyXYdqmiVLN7pnA0UVfl8gtEsBK+vfSRgN1bNk9gHnt3rXFN85NOzyGYD2ewHKvRfeuF YxDsllZIF9UTMW8JNlmcdsWErbdIv9TbL/iT0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=EPw6LuJvitoNGWZbxK9a6L+Nbn9Ik3CJidsl4s3N563iQcAymHeGNJWEvM22/5NaPx N+W5wwrvQB/hPR109HD8FXplXvLmvRbYFZg426PdACe5RHj1evpc438fL9BtCi6PeBHa miG5e0NfS/RHpx2bKMdRtlM/dVw1g8TskrRjw= MIME-Version: 1.0 Received: by 10.100.195.5 with SMTP id s5mr1633793anf.224.1299532780197; Mon, 07 Mar 2011 13:19:40 -0800 (PST) Received: by 10.100.106.15 with HTTP; Mon, 7 Mar 2011 13:19:40 -0800 (PST) In-Reply-To: <20110307205957.GA47557@freebsd.org> References: <20110307205957.GA47557@freebsd.org> Date: Mon, 7 Mar 2011 23:19:40 +0200 Message-ID: From: George Liaskos To: Alexander Best Content-Type: text/plain; charset=UTF-8 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 21:19:41 -0000 >What process did you follow to get here? I did a make toolchain followed by make buildworld. > 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. ;) I saw the relevant commits about core2, this is the reason i decided to do a rebuild. I didn't know that core2 was wrong, it's in the make.conf documentation, "native" it's not and after serious googling i found out that i should actually avoid it. I always believed that core2 was there [make.conf] as a future proof upgrade path for when the base toolchain actually supports core2. So, should i use native cputype?