On Mon, 16 Dec 2024, James K. Lowden wrote: > On Mon, 16 Dec 2024 23:48:52 +0000 (UTC) > Joseph Myers <josmy...@redhat.com> wrote: > > > However, if introducing a Bison dependency, it needs to be documented > > (being specific about version requirements) in install.texi. > > Under "Tools/packages necessary for building GCC", in Prequisites, > yes?
Yes (with an appropriate note that it's only needed for COBOL). At some point it would be desirable to test the workflow that applies with release tarballs (configure --enable-generated-files-in-srcdir and build; then take the resulting source directory that includes the Bison-generated files and make sure you can build from it on a system that doesn't have Bison installed). But the other issues identified in the discussions so far are probably higher priority, to get it building (and testing with an included testsuite) reliably from git (with Bison etc. installed) across a range of the most common configurations (build / host / target) that people use for building and testing GCC (which includes having working multilib support for the target libraries). > In gcc/cobol/parse,y, we have, > > %require "3.5.1" // 3.8.2 also works, but not 3.8.0 > > David Malcolm reports success with 3.5. Should I change the above on > the strength of his experience, or is a more methodical approach > indicated? I'd advise testing to see what the minimum that actually works is (probably the version where some Bison feature you rely on was introduced). -- Joseph S. Myers josmy...@redhat.com
