Date: Mon, 22 Mar 2010 21:57:58 -0500 From: Scot Hetzel <swhetzel@gmail.com> To: jhell <jhell@dataix.net> Cc: Alexander Best <alexbestms@wwu.de>, freebsd-current@freebsd.org, Garrett Cooper <yanefbsd@gmail.com> Subject: Re: build failures after stdlib update Message-ID: <790a9fff1003221957x6e2b001i3102302618d24051@mail.gmail.com> In-Reply-To: <alpine.BSF.2.00.1003212021250.16103@qvfongpu.qngnvk.ybpny> References: <permail-20100321110009f0889e84000039fe-a_best01@message-id.uni-muenster.de> <alpine.BSF.2.00.1003212021250.16103@qvfongpu.qngnvk.ybpny>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Mar 21, 2010 at 7:29 PM, jhell <jhell@dataix.net> wrote: > Native is equal to CPUTYPE not being defined right ? > Built into GCC is the ability to auto-detect the CPUTYPE when -mtune=native, if you run this command GCC will tell ouput your processor type: gcc -v -x c -E -mtune=native /dev/null -o /dev/null 2>&1 | grep mtune | sed -e 's/.*mtune=//' > So if the above is true why would you set CPUTYPE to native in the first > place ? when you can just leave it unset and its equal to native. > Native allows one to build the sources to the current build machines cputype. There is one bug when setting the CPUTYPE to native, the FreeBSD build system fails to correctly set the MACHINE_CPU to the correct value. I had discovered this problem back in May 2007: http://www.freebsd.org/cgi/query-pr.cgi?pr=112997 Just apply the last patch to share/mk/bsd.cpu.mk and that will fix the problem. Scot
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?790a9fff1003221957x6e2b001i3102302618d24051>