[Buildroot] [autobuild.buildroot.net] Build results for 2014-05-11

[Thomas Petazzoni <thomas.petazzoni@free-electrons.com>]

Dear Beno?t Th?baudeau,

On Wed, 14 May 2014 23:25:53 +0200, Beno?t Th?baudeau wrote:

> > Right. It just papers over the real problem which is building a target config
> > test using the host toolchain, and then running it. The patch at
> > http://patchwork.ozlabs.org/patch/348765/ is better, I believe.
> 
> The issue in my case was that the native toolchain used for the
> configure test implicitly #included a header file, which triggered a
> conflict of direct inclusion between the native and cross toolchains
> header files. Passing --sysroot forces the native toolchain to only
> use the header files from the cross toolchain, fixing this conflict.
> This directly addresses the issue without any assumption regarding the
> cross libc.

Right, but using target headers with the native toolchain is wrong, and
potentially also very fragile.

> http://patchwork.ozlabs.org/patch/348765/ works too, but it removes a
> configure test and it relies on the "all libc variants we support have
> the netinet/tcp.h header" assumption, which might become wrong in the
> future, which is why I didn't choose this solution.

How likely is that to happen? If it does, we will have very clear
build failures, so we will notice, no?

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com