Date: Tue, 09 Oct 2012 11:47:09 +0200 From: Dimitry Andric <dim@FreeBSD.org> To: d@delphij.net Cc: Xin Li <delphij@delphij.net>, peter@freebsd.org, freebsd-arch@FreeBSD.org Subject: Re: Building environment using system headers instead of the in-tree headers Message-ID: <5073F29D.6060505@FreeBSD.org> In-Reply-To: <50736C5A.1000604@delphij.net> References: <50736C5A.1000604@delphij.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2012-10-09 02:14, Xin Li wrote:
> Josh Paetzel recently discovered an interesting build issue with the
> current FreeBSD 'buildworld', where 'make buildworld' over a FreeBSD
> 9.0 tree on a FreeBSD 9.1 system will fail.
>
> As it turns out, this was caused by addition of xlocale functionality
> on FreeBSD 9.1, which uses macros and expects some new functions found
> in more recent FreeBSD releases. On the other hand, we do not pass
> e.g. -I${.CURDIR}/../../include so the header is preferred than system
> header.
During which stage does this fail? In the '4.2 building libraries' one?
> So an obvious way to get around this would be to add that to CFLAGS.
> It looks like that in r81600 Peter have "sneak in" such change in libc
> because the FILE structure was changed and we have to use that to get
> the code compile.
It shouldn't be needed, if the cross-tools stage completed successfully.
The toolchain built there will *only* look in the /usr/obj directory for
its headers.
Of course, if you are manually running make in lib/libc, then all bets
are off. :) I think there is always a way to shoot yourself in the
foot then.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5073F29D.6060505>