On Tue, Feb 20, 2018 at 10:28:47AM -0800, Khem Raj wrote: > On Tue, Feb 20, 2018 at 8:17 AM, Denys Dmytriyenko <de...@denix.org> wrote: > > On Tue, Feb 20, 2018 at 04:08:06PM +0000, Khem Raj wrote: > >> On Tue, Feb 20, 2018 at 7:41 AM Martin Jansa <martin.ja...@gmail.com> > >> wrote: > >> > >> > I'm OK with adding bison-native for all versions. > >> > >> As long we know that there are no side effects of this dep in kernel builds > > > > You do realize that when you build with oe-core toolchain, every package > > gets > > bison-native dependency automatically? Regardless whether it was requested > > or > > not. If there were side effects, we would have seen it long time ago... > > Yes I see it seems to be pulled in by toolchain regardless, so for this > patch we might just be adding to determinism. but I think it raises question > on why toolchain is adding this everywhere, I think we should remove it > from toolchain default deps. It will make metadata more consistent > across internal/external toolchains
There were several similar patches I submitted last month for different components to add flex-native and/or bison-native. Most of them got accepted and we had a follow up discussion with Richard in gcc thread: http://lists.openembedded.org/pipermail/openembedded-core/2018-January/146295.html He also submitted this patch to prevent indirect flex/bison-native dependencies, but I don't believe it got merged yet: http://lists.openembedded.org/pipermail/openembedded-core/2018-January/146324.html Richard, do you have any comments? -- Denys -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core