Re: autoconf-2.64 required?

[Benjamin Lindner]

Jaroslav Hajek wrote:
> On Sat, Aug 15, 2009 at 12:02 AM, Michael
> Goffioul<address@hidden> wrote:
> > Hi,
> >
> > it seems that octave now requires autoconf-2.64 and not 2.60 as mentioned
> > in the AC_PREREQ of configure.in. Since change 0ce82753dd72, my
> > autoconf-2.61 is unable to process configure.in and fails with:
> >
> > configure.in:40: error: possibly undefined macro: AC_DEFINE
> >      If this token and others are legitimate, please use m4_pattern_allow.
> >      See the Autoconf documentation.
> > configure.in:63: error: possibly undefined macro: AS_HELP_STRING
> > configure.in:617: error: possibly undefined macro: AC_LANG_PUSH
> > configure.in:665: error: possibly undefined macro: AC_LANG_POP
> > configure:1511: error: possibly undefined macro: m4_ifblank
> > configure:9276: error: possibly undefined macro: m4_ifnblank
> > configure:9479: error: possibly undefined macro: m4_toupper
> >
> > Can anybody confirm this?
> >
> > Michael.
>
> Autoconf 2.64 is really very new; though by the time Octave 3.4 will
> be released, it may already be widespread.
> However, in this case apparently it's just m4_ifblank and m4_ifnblank
> missing, so an easy remedy is to steal them out from autoconf 2.64 and
> define them ourselves if they're not there:
> http://hg.savannah.gnu.org/hgweb/octave/rev/691545147aca
>
> this enables use of autoconf 2.63 for me.
>
> cheers

Great!

With this changeset, autoconf & configure run on msys using autoconf 2.61

thanks
benjamin