Re: Failure to boostrap bison from git repository

[Joel E. Denny]

On Mon, 30 May 2011, Stefano Lattarini wrote:

> > By the way, I'm using 2.68.  If you decide to build a stable autoconf, 
> > 2.68 might be best to try so we can rule out that difference.
> >
> Done, trying both GNU m4 1.4.14 and 1.4.16.  There is still exactly the
> same error:
> 
>   configure.ac:110: error: possibly undefined macro: AC_PROG_GNU_M4
>         If this token and others are legitimate, please use m4_pattern_allow.
>         See the Autoconf documentation.

> $ /opt/extra/autoconf-2.68/bin/autom4te --version
> autom4te (GNU Autoconf) 2.68

> $ `echo 'm4_divert(0)__program__' | /opt/extra/autoconf-2.68/bin/autom4te 
> --language=m4sugar` --version
> stdin:1: warning: prefer named diversions
> m4 (GNU M4) 1.4.14

You also tried the case where autoconf 2.68's autom4te reports m4 1.4.16, 
right?  That's the combination I'm using.

In any case, within your bison checkout, verify the output of this 
command:

  % head -1 m4/m4.m4
  # m4.m4 serial 12

That's where AC_PROG_GNU_M4 is defined.

> > Oops, that was automake not autoconf, but the advice is probably still 
> > worthwhile.

> but this issue shouldn't be relevant in my situation I think

By "the advice", I meant my advice of not using development versions of 
such tools when building bison.  Sorry for the confusion.