On Wed, 2013-09-11 at 15:01 +0200, Nicolas Dechesne wrote:
On Wed, Sep 11, 2013 at 2:00 PM, Richard Purdie richard.purdie@linuxfoundation.org wrote:
Not really, its actually intentionally designed like this since its pointless rebuilding gcc-cross multiple time just because we want to use it with a different sysroot. We therefore just pass in the arguments to the compiler to ensure it uses the right one. If you remove them, you hit the problems you describe. We should probably compile in a bogus sysroot so it never works and makes this kind of issue more visible.
hmm. ok. i see. it would certainly help to have a better 'error' message... i suppose that not having a builtin sysroot at all, would be an even bigger problem as it would default to /usr/include...
Right, that would be even worse than a poisoned one...
Cheers,
Richard