> Hmm, this is unfortunate since there is no common way to > specify the header path directly. > > I am not sure how much effort we should invent > to support non-GNU implementation > since we already rely on various GNU tools. > > If we decide to support byacc, > we must carry the restriction > that bans GNU-extension. In fact Linux now can be built without using GNU binutils and using LLVM tools instead. It's just one architecture and a specific config now, but eventually the others will be built too. You can follow the progress here: https://github.com/ClangBuiltLinux/continuous-integration/issues/73 I believe that compatibility with different alternative tools is a good thing as long as it doesn't add unwanted complexity. And as this patch is just changing command-line flags to their portable variants and explicitly adds a couple of definitions that are presumed by GNU bison, I can't see a problem with it. Regards, Dmitry
