Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 7 Mar 2011 23:19:40 +0200
From:      George Liaskos <geo.liaskos@gmail.com>
To:        Alexander Best <arundel@freebsd.org>
Cc:        freebsd-current@freebsd.org
Subject:   Re: r219385 build error.
Message-ID:  <AANLkTimJpsr=38UPswCXUmajNixTs1qS-8FxT36xAK4V@mail.gmail.com>
In-Reply-To: <20110307205957.GA47557@freebsd.org>
References:  <AANLkTikc-Z9mjmQ7EWnWdqz297hHQ_Kt2k9z05FaNv-y@mail.gmail.com> <20110307205957.GA47557@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
>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?



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimJpsr=38UPswCXUmajNixTs1qS-8FxT36xAK4V>