On Mon, 2017-05-29 at 18:54 +0300, Alexander Kanavin wrote: > I see. You are right here. I admit I don't fully understand if it's > generally okay for -native recipes to look around in (and later use) > host include directories like that, as we're striving towards > reproducible builds, and this behavior is not supportive of them. > Richard, can we have your say please?
Its unavoidable really, we have to have some host system we build on as we need a compiler/headers from it. Even if you build a gcc-native, what would you compile it with? :) If you do want to avoid the risk, you'd choose your own custom base OS (or container) and then always build on that. It would then be both reproducible and deterministic. We don't want to mandate a specific host configuration out the box though. So this patch avoids an issue. We don't tend to run into too many issues like this one thankfully. Cheers, Richard -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
