Re: autoconf bug in current (1-Nov-2004) CVS

[Lars Clausen <lars raeder dk>]

On Mon, 2004-11-01 at 21:06, Steven Lembark wrote:
> Verbose attached
> 
> $ autoconf
> configure.in:5: error: possibly undefined macro: AM_INIT_AUTOMAKE
>       If this token and others are legitimate, please use m4_pattern_allow.
>       See the Autoconf documentation.
> configure.in:11: error: possibly undefined macro: AM_CONFIG_HEADER
> configure.in:19: error: possibly undefined macro: AM_MAINTAINER_MODE
> configure.in:22: error: possibly undefined macro: AC_DISABLE_STATIC
> configure.in:23: error: possibly undefined macro: AC_PROG_LIBTOOL
> configure.in:26: error: possibly undefined macro: AM_SANITY_CHECK
> configure.in:47: error: possibly undefined macro: AC_PROG_INTLTOOL
> configure.in:55: error: possibly undefined macro: AM_PATH_GLIB_2_0
> configure.in:60: error: possibly undefined macro: AM_PATH_GTK_2_0
> configure.in:64: error: possibly undefined macro: AC_MSG_ERROR
> configure.in:121: error: possibly undefined macro: AM_CONDITIONAL
> configure.in:241: error: possibly undefined macro: AM_GLIB_GNU_GETTEXT
> configure.in:410: error: possibly undefined macro: AM_PATH_PYTHON
> configure.in:411: error: possibly undefined macro: AM_CHECK_PYMOD
> configure.in:412: error: possibly undefined macro: AM_CHECK_PYTHON_HEADERS
> configure.in:413: error: possibly undefined macro: AM_CHECK_PYTHON_LIB

What version of automake do you use?  Did the same setup work earlier?

-Lars