[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [bison 3.1/test suite] all syncline tests failing Windows (illegal c
RE: [bison 3.1/test suite] all syncline tests failing Windows (illegal characters in test file names)
Tue, 30 Oct 2018 16:20:44 +0100
On Sun, 28 Oct 2018 08:40:50 +0100, Akim Demaille wrote:
> > Was too fast hitting send: I had to adjust the gettext version to 0.19 (from
> 0.18, in configure.ac) to get the ball rolling.
> I’m a bit lost.
> You are not expected to have to change anything, why did you have to do it?
Make complains if the gettext version in configure.ac (0.18) does not match the
system gettext version (which is 0.19 here):
Making all in po
make: Entering directory '../bison-3.2/po'
*** error: gettext infrastructure mismatch: using a Makefile.in.in from
gettextversion 0.18 but the autoconf macros are from gettext version 0.19
Issue remains with bison 3.2 from yesterday. After changing configure.ac make
fires the autoreconf loop again to make sure that every thing is consistent.
> >> Finally it is through. In version 22.214.171.124-7175 one test fails. It
> >> is #1 for which it looks like the expectation is right, but a bit
> >> scrambled (see below). So nothing really bad I think.
> >> ~~~
> >> +++ /c/...../bison/bison-126.96.36.199-7175/bison-188.8.131.52-
> >> 7175/tests/testsuite.dir/at-groups/1/stderr 2018-10-27
> >> +0200
> >> @@ -1,3 +1,3 @@
> >> -bison: option '--skeleton' requires an argument
> >> +bison: option requires an argument — skeleton
> This is unexpected. If you run bison --skeleton, you should get the first
> message, not the second.
Here is what I manually get: the first version. Surprise?
$ bison --skeleton
bison: option requires an argument -- skeleton
Try 'bison --help' for more information.
$ bison --version | head -n 1
bison (GNU Bison) 3.1
... and same result for bison 3.2. Is this connected to any default strings for
gettext? Really just guessing.