Re: [PATCH] at: explicitly depend on bison-native for deterministic builds

[Denys Dmytriyenko <denis@denix.org>]

On Tue, Jan 09, 2018 at 11:11:56PM +0000, Richard Purdie wrote:
> On Tue, 2018-01-09 at 17:24 -0500, Denys Dmytriyenko wrote:
> > From: Denys Dmytriyenko <denys@ti.com>
> > 
> > Usually bison-native gets into sysroot through indirect dependencies,
> > even with RSS. But when bison-native is not in sysroot, due to
> > different
> > system config,
> 
> Any idea what that "different system config" is?
> 
> I get worried about things like this and would like to understand it a
> little better...

Well, if you check recipe-sysroot-native of any target package, you'll see 
that bison-native gets staged for absolutely all target packages, regardless 
of explicit dependencies listed in the corresponding recipe. So, it must be 
coming indirectly from a toolchain dependency. And binutils-cross appears to 
DEPENDS on bison-native. In my case, I'm using an external toolchain and not 
building binutils-cross, hence not getting its dependencies indirectly.

BTW, to verify this theory, I modified binutils and removed bison-native 
dependency, added bison to HOSTTOOLS and now "at" package doesn't have it in 
recipe-sysroot-native. So, the patch is to make this dependency explicit.

-- 
Denys