[Buildroot] [RFC] [PATCH v2 2/2] support/kconfig: Bump to kconfig from Linux 4.17-rc2

Thomas Petazzoni thomas.petazzoni at bootlin.com
Sun May 20 14:50:09 UTC 2018


On Sun, 20 May 2018 16:41:41 +0200, Yann E. MORIN wrote:

> I initially did not reply further to this part, becuase I seem to
> remember that there was a change in behavious with certain versions of
> flex/bison, that made the output change drastically, and I was afraid we
> could be bitten by this...
> But in the end, this is not a problem, because we would not care to
> mix-n-match files built with different versions of said tools, as they
> would be those from the distro, always, and never those we ship, since
> we would no longer ship them.
> And eventually, I now remember that the issue was with gperf changing
> its API (a function prototype changed), and that was causing pain. But
> now, kconfig no longer uses gperf to start with, so no incompatibility
> anymore anyway.
> Which would allow us to drop the dependency of linux on host-{flex,bison}
> that we had to add recently.

If we start relying on the system-installed flex and bison, then we
should remove host-flex and host-bison entirely, not only for the linux
package. The question is whether bison and flex both behave in a
reasonably similar way regardless of which version is used.

When I see that even "tar" does not have a sufficiently stable
behavior (which forces us to build host-tar), I'm a bit worried about
more complex tools such as flex and bison.

Best regards,

Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering

More information about the buildroot mailing list