[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FYI: autoheader -vs- AC_CONFIG_HEADERS (Was: Re: Conditionally compi
|
From: |
Tom Tromey |
|
Subject: |
Re: FYI: autoheader -vs- AC_CONFIG_HEADERS (Was: Re: Conditionally compiling Java) |
|
Date: |
05 Jul 2002 18:09:55 -0600 |
|
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 |
>>>>> "Hari" == Raja R Harinath <address@hidden> writes:
Hari> But, I don't think this addresses the failure of 'autoheader'
Hari> when configure.in use AM_CONFIG_HEADER([foo]). AM_CONFIG_HEADER
Hari> needs to be defined in terms of AC_CONFIG_HEADERS for
Hari> 'autoheader' to work with semi-legacy configure.in files.
Today I tried the latest automake on GNU fileutils 4.1.9.
I get this when I run aclocal; autoconf:
configure.ac:7: error: possibly undefined macro: AM_CONFIG_HEADER
fleche. grep AM_CONFIG configure
AM_CONFIG_HEADER(config.h:config.hin)
In configure.ac I see this:
AM_CONFIG_HEADER(config.h:config.hin)
AC_CANONICAL_HOST
AM_INIT_AUTOMAKE([1.6 gnits dist-bzip2])
If I move AM_INIT_AUTOMAKE first, then things work as expected.
However... I expected `autoconf -Wobsolete' to warn about
AM_CONFIG_HEADER, but it doesn't.
Tom