Re: [PATCH 00/14] glr2.cc: fix linking conflicts

> On 13 Sep 2021, at 17:37, Tom Shields =
<[email protected]> wrote:
>=20
> I tried building the Ox 1.6 distributed release as follows:
>=20
> ./configure --enable-maintainer-mode BISON=3Dbison-3.8.1.21
>=20
> Note: this uses the Apple Xcode C compiler.
>=20
> I get fails on these Ox test cases: bison-3.x-calc, =
bison-3.x-calc-pure, bison-3.x-calc-push, bison-3.x-calc-pure-treeviz & =
bison-3.x-calc-push-treeviz.
>=20
> A quick check of the test-suite.log file shows that the default =
=E2=80=98yyerror=E2=80=99 and =E2=80=98yylex=E2=80=99 signatures changed =
in the Bison default C skeleton at some point after the release of Ox =
1.6, which was built & tested with Bison 3.3.2.
>=20
> I=E2=80=99m not sure it is worth upgrading Ox 1.6 (and possibly 1.7 & =
1.8), but I=E2=80=99ll see if some judiciously applied =E2=80=98#ifdef's =
can handle the skeleton changes.
>=20
> On the other hand, I don=E2=80=99t get a fail on the oxpt test case.
>=20
> Please send me the config.log and oxpt.log files from your failed test =
of Ox 1.6 when you get a chance.

Since you are actively developing Ox, I deleted 1.6. :-) Though I have a =
backup, but 1.10 using C++ sounds more exciting. But Bison only supports =
the last version, fixes may end up in a new later version. This is =
typical for projects that need to save on manpower.

Otherwise, I just used the Bison 3.8.1 that Akim just released.