Paul Eggert <egg...@cs.ucla.edu> writes:
> 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.
Agreed, it is difficult to tell the issue without a step-by-step
process. From the errors that I do see, it seems like files were copied
from modern Gnulib without running ./bootstrap to regenerate gnulib.mk.
FWIW, I ran the following on my GNU/Linux machine in my Bison clone:
$ git submodule update --init && ./bootstrap
$./configure && make && make dist
Then scp'd the tarball to my Windows VM. From there Bison built
perfectly fine in Cygwin there.
> 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.
Yep, that is a better idea. But our CI tests on Cygwin and passes, so it
is unlikely there is a Gnulib bug.
Collin
