Re: Detecting (g)m4

2009-08-20 Thread Joel E. Denny
Hi Eric. On Thu, 20 Aug 2009, Eric Blake wrote: [wow, I've been delayed on clearing out my queue of bison work] No problem. You're not alone. :) Better yet, here's my patch that takes advantage of the new checks in serial 8 for 'm4 -g':

Re: Detecting (g)m4

2009-07-21 Thread Joel E. Denny
Hi Eric. On Fri, 17 Jul 2009, Akim Demaille wrote: Le 16 juil. 09 à 19:27, Eric Blake a écrit : Meanwhile, the latest git version uses serial 5 of autoconf's m4/m4.m4, which does a MUCH better job at picking m4 1.4.5 or newer, regardless of spelling. Autoconf itself has moved on to

Re: Detecting (g)m4

2009-07-21 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Joel E. Denny on 7/21/2009 12:40 PM: I currently see serial 8 in autoconf's master branch. Should that be ok for us? I just noticed that branch-2.5 doesn't use the m4/m4.m4 from the autoconf submodule, so I pushed the following

Re: Detecting (g)m4

2009-07-21 Thread Joel E. Denny
On Tue, 21 Jul 2009, Eric Blake wrote: According to Joel E. Denny on 7/21/2009 12:40 PM: I currently see serial 8 in autoconf's master branch. Should that be ok for us? I just noticed that branch-2.5 doesn't use the m4/m4.m4 from the autoconf submodule, so I pushed the following as

Re: Detecting (g)m4

2009-07-18 Thread Eric Blake
[I don't know how to make nabble cc the OP, and I didn't get the original message to do a reply-all from my inbox] I made sure my autoconf was up-to-date and did an autoreconf -f. Still isn't right. Correct. The bug is not what version of autoconf you are using, but what version of

Re: Detecting (g)m4

2009-07-17 Thread Akim Demaille
Le 16 juil. 09 à 19:27, Eric Blake a écrit : Hi Eric! Akim Demaille akim at lrde.epita.fr writes: Maybe not quite a bug, and maybe not your fault, but configure apparently picks the first program called gm4 in my path, not the first appropriate m4 or gm4. You are right, of course. But

Re: Detecting (g)m4

2009-07-17 Thread Hans Aberg
[Please keep the cc to the list so that others know and can help.] M4 and some other components were enhanced in the face of bugs and problems in the context of Bison, but Bison will still work without them, it seems. Hans On 16 Jul 2009, at 20:12, A Braunsdorf wrote: In message

Re: Detecting (g)m4

2009-07-16 Thread Akim Demaille
Le 15 juil. 09 à 23:36, A Braunsdorf a écrit : Maybe not quite a bug, and maybe not your fault, but configure apparently picks the first program called gm4 in my path, not the first appropriate m4 or gm4. My problem is that Sun provides a gm4 that is old and makes nearly all the bison tests

Re: Detecting (g)m4

2009-07-16 Thread Hans Aberg
On 16 Jul 2009, at 09:20, Akim Demaille wrote: Maybe not quite a bug, and maybe not your fault, but configure apparently picks the first program called gm4 in my path, not the first appropriate m4 or gm4. You are right, of course. But it's more efforts to look for the best m4 around, so

Detecting (g)m4

2009-07-15 Thread A Braunsdorf
Maybe not quite a bug, and maybe not your fault, but configure apparently picks the first program called gm4 in my path, not the first appropriate m4 or gm4. My problem is that Sun provides a gm4 that is old and makes nearly all the bison tests fail. I have installed a much newer one as m4