Re: FYI: autoheader -vs- AC_CONFIG_HEADERS (Was: Re: Conditionally compiling Java)

[Raja R Harinath]

Hi,

Alexandre Duret-Lutz <address@hidden> writes:

>>>> "Braden" == Braden McDaniel <address@hidden> writes:
>
> [...]
>
>  Braden> Looks promising; however, when I try to use the CVS
>  Braden> version of automake, I get an error from autoheader:
>
>  Braden> autoheader: error: AC_CONFIG_HEADERS not found in configure.ac
>
>  Braden> I am in fact using the macro AM_CONFIG_HEADER, but changing to
>  Braden> AC_CONFIG_HEADERS has no effect. Yeah, I know: autoheader comes with
>  Braden> autoconf, not automake. So, any idea what might be triggering this?
>
> Thanks.  I'm checking in the following fix.
>
> 2002-06-13  Alexandre Duret-Lutz  <address@hidden>
>
>       * m4/header.m4 (_AM_CONFIG_HEADER_INSINUATE): Use m4_copy instead
>       of m4_rename so that AC_CONFIG_HEADER is never undefined and
>       therefore still traced after the redefinition.
>       * tests/defs (AUTOHEADER): Define.
>       * tests/autoheader.test: New file.
>       * tests/Makefile.am (TESTS): Add autoheader.test.
>       Reported by Braden McDaniel.

But, I don't think this addresses the failure of 'autoheader' when
configure.in use AM_CONFIG_HEADER([foo]).  AM_CONFIG_HEADER needs to
be defined in terms of AC_CONFIG_HEADERS for 'autoheader' to work
with semi-legacy configure.in files.

I would suggest that you replace the current definition of
AM_CONFIG_HEADER with _AM_CONFIG_HEADERS, which is traced, and which
is used in the INSINUATion.  Then, revert AM_CONFIG_HEADER to

  AU_DEFUN([AM_CONFIG_HEADER],[AC_CONFIG_HEADERS([$1])])

(This also solves the singular/plural identity crisis in the current
definition of AM_CONFIG_HEADER.)

- Hari
-- 
Raja R Harinath ------------------------------ address@hidden