Re: bison: new module

2020-05-03 Thread Bruno Haible
Hi Akim, > > After you pushed it, I'll test it from within GNU gettext. > > Pushed. I tested it, and it failed to set VARIABLE to ':' if an old bison version is in $PATH. This patch fixes it. 2020-05-03 Bruno Haible bison: Fix today's commit. * m4/bison.m4

Re: bison: new module

2020-05-03 Thread Akim Demaille
> Le 3 mai 2020 à 12:02, Bruno Haible a écrit : > >> How about this? > > Looks good. > > After you pushed it, I'll test it from within GNU gettext. Pushed.

Re: bison: new module

2020-05-03 Thread Bruno Haible
> How about this? Looks good. After you pushed it, I'll test it from within GNU gettext. Bruno

Re: bison: new module

2020-05-03 Thread Akim Demaille
Hi Bruno, > Le 3 mai 2020 à 11:35, Bruno Haible a écrit : > > Hi Akim, > >> I didn't see the need for a temporary directory. > > I didn't talk about a temporary directory, only about a temporary file. Doh... Sorry. > The patch looks nearly good. > >> +if _AC_DO_VAR([$1 conftest.y -o

Re: bison: new module

2020-05-03 Thread Bruno Haible
Hi Akim, > I didn't see the need for a temporary directory. I didn't talk about a temporary directory, only about a temporary file. The patch looks nearly good. > +if _AC_DO_VAR([$1 conftest.y -o conftest.c]); then I would try to avoid the use of undocumented Autoconf internals. Is that

Re: bison: new module

2020-05-03 Thread Akim Demaille
Hi Bruno, > Le 2 mai 2020 à 19:50, Akim Demaille a écrit : > >> At configure time, both solutions are nearly on par: the time to >> create a temporary file is negligible. And both will fail the same >> way for a 'bison' program that references missing shared libraries. >> >> Patch welcome! >

Re: bison: new module

2020-05-02 Thread Akim Demaille
Hi Bruno, > Le 2 mai 2020 à 10:45, Bruno Haible a écrit : > > Hi Akim, > >> I was suggesting that the macro _itself_ could just >> run bison on a file with the %require. > > This sounds better than the existing code that runs '--version'. > > What about users who have non-released versions

Re: bison: new module

2020-05-02 Thread Bruno Haible
Hi Akim, > I was suggesting that the macro _itself_ could just > run bison on a file with the %require. This sounds better than the existing code that runs '--version'. What about users who have non-released versions installed? I think the %require solution will be on par with the --version

Re: bison: new module

2020-05-01 Thread Akim Demaille
Hi Bruno, > Le 1 mai 2020 à 20:10, Bruno Haible a écrit : > > Hi Akim, > >> I would personally just run bison on a file with %require "VERSION". >> It was introduced in 2.2 (2006-05-19), which, I think, is old enough. >> If you agree with that approach, I can provide a patch. > > Alas, this

Re: bison: new module

2020-05-01 Thread Bruno Haible
Hi Akim, > I would personally just run bison on a file with %require "VERSION". > It was introduced in 2.2 (2006-05-19), which, I think, is old enough. > If you agree with that approach, I can provide a patch. Alas, this is not what we want. [1] says "If the requirement is not met, bison exits

Re: bison: new module

2020-05-01 Thread Akim Demaille
Hi Bruno, > Le 1 mai 2020 à 18:21, Bruno Haible a écrit : > > The 'parse-datetime' module has a reasonable configure check for Bison, > specifying the minimum version of Bison that is required for the particular > .y file. > > This patch moves the support to a module 'bison', that can be used

bison: new module

2020-05-01 Thread Bruno Haible
e time to do this now; volunteers welcome! 2020-05-01 Bruno Haible bison: New module. * m4/bison.m4 (gl_PROG_BISON): New macro, extracted from m4/parse-datetime.m4. * m4/parse-datetime.m4 (gl_PARSE_DATETIME): Invoke gl_PROG_BISON. * modules/bison: Ne