The Bison bug is described at
https://lists.gnu.org/archive/html/bug-bison/2025-07/msg00003.html
Its fix is at
https://lists.gnu.org/archive/html/bison-patches/2025-07/msg00000.html
I'm hoping anyone here who also maintains Bison will have a chance to
look at the bug and the patch - since bison-patches hasn't gotten much
attention in couple years
On 7/11/2025 12:04 AM, Z. Majeed wrote:
Thanks Paul for the update - that fixed the build - I am building from
git source - for the usual reasons - I found a bug in Bison and wanted
to confirm with latest source from Savannah - also it's nicer for
tracking changes than a tarball
I think the problems I had after tracking the wint_t bug to gnulib
came from messing up submodule updates and bootstrap
I just blew everything away for a clone of latest Bison - and it worked
On Thursday, July 10, 2025 at 08:37:53 PM CDT, Paul Eggert
<egg...@cs.ucla.edu> wrote:
I'm not quite following all those bug reports. When you say "build Bison
from source", do you mean "build from the latest release tarball", or
"build from Git"? I suspect you mean the latter, but if so you'll likely
have more hassle. Why is the latter needed?
As far as building from Git goes, the gist seems to be that there's a
recent Gnulib change that Bison needs. To work around that problem, I
updated Bison to use the current Gnulib on Savannah, so if you're
building from Git you can build from that.
Please try to separate any Gnulib bugs (which you should be able to
reproduce via "./gnulib-tool --test MODULENAME" in Gnulib) from Bison
bugs. That way, Gnulib maintainers won't be bothered by Bison bugs and
vice versa.
