Date: Thu, 20 Mar 2014 11:30:08 -0600 From: Warner Losh <imp@bsdimp.com> To: David Chisnall <theraven@FreeBSD.org> Cc: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, John-Mark Gurney <jmg@funkthat.com>, freebsd-current@freebsd.org, Lev Serebryakov <lev@freebsd.org> Subject: Re: Building with external toolchain was broken 6 months ago with r255187 Message-ID: <D40B5E6C-C176-420A-9620-4D8388D8E9D7@gmail.com> In-Reply-To: <491ECF6C-D868-4971-903E-5F380AB7E05B@FreeBSD.org> References: <323697891.20140319013757@serebryakov.spb.ru> <20140318220140.GA32089@funkthat.com> <7423EF12-9DD4-4C03-9FF6-7BAAB75820F6@lists.zabbadoz.net> <201403201008.48610.jhb@freebsd.org> <491ECF6C-D868-4971-903E-5F380AB7E05B@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 20, 2014, at 8:25 AM, David Chisnall <theraven@FreeBSD.org> = wrote: > On 20 Mar 2014, at 14:08, John Baldwin <jhb@freebsd.org> wrote: >=20 >> No, the compiler should provide a working "wmmintrin.h" header in one = of >> its built-in paths if it supports the AES instructions. This is akin = to >> saying that code that uses "stdio.h" should use -I/usr/src/include. >=20 > It does, however our build system then explicitly says to the compiler = 'don't use your built-it paths because they may contain declarations = that contradict the FreeBSD ones' by means of the sysroot argument. = When not using an external toolchain, we put the compiler's internal = headers inside the sysroot. Sounds like we=92re building the sysroot wrong then. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D40B5E6C-C176-420A-9620-4D8388D8E9D7>