Date: Tue, 28 Aug 2007 10:34:09 -0400 From: "Maxim Khitrov" <mkhitrov@gmail.com> To: "Scot Hetzel" <swhetzel@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: Setting CPUTYPE=native, fails to set MACHINE_CPU correctly. Message-ID: <26ddd1750708280734p432d887ex3bf7ed7892e78a3f@mail.gmail.com> In-Reply-To: <790a9fff0708272354q31afca4fx1e787f9592a6a4e0@mail.gmail.com> References: <790a9fff0708272354q31afca4fx1e787f9592a6a4e0@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/28/07, Scot Hetzel <swhetzel@gmail.com> wrote: > Gcc 4.2 has a new cpu_type (native) for x86 and amd64 systems. This > cpu_type is to allow gcc to automatically detect the processor type > that gcc is running on. > > The problem is that setting CPUTYPE?=native in either src.conf or > make.conf will cause MACHINE_CPU to be set to the wrong value for the > native cpu. There is actually another problem with using CPUTYPE=native, as I found out yesterday. Certain ports may fail to build with it. For example, I was trying to build openoffice.org-2 and it was failing at gcc-ooo with the message "cannot compute suffix of object files." Since it was using the older compiler version, -march=native caused it to fail. There should probably be an additional note somewhere telling people to be careful with this setting. - Max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?26ddd1750708280734p432d887ex3bf7ed7892e78a3f>