bug-gnu-utils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: make dist problem w/ autoconf 2.13


From: Dominik Vogt
Subject: Re: make dist problem w/ autoconf 2.13
Date: Sat, 15 Sep 2001 11:57:46 +0200

I'm sorry, I made a mistake in my bug report:

On Sat, Sep 15, 2001 at 11:33:15AM +0200, Dominik Vogt wrote:
> Using autoconf 2.13 and automake 1.4 there seems to be a problem
> with autoreconf vs. autoconf if the config.h.in file is not
> present (e.g. after fetching a fresh source tree from cvs or if it
> was explicitly removed):
> 
>   $ rm config.h.in
>   $ automake --add-missing
>   $ autoreconf
> 
> Both, automake and autoreconf complain about the missing
> config.h.in.  This is not a problem because autoreconf generates
> the file.  But then, in the resulting Makefile.in, config.h.in is
> not listed in the DIST_COMMON variable:
> 
>   DIST_COMMON =  README ./stamp-h.in AUTHORS COPYING ChangeLog INSTALL \
>   Makefile.am Makefile.in NEWS acconfig.h acinclude.m4 aclocal.m4 \
>   config.guess config.sub configure configure.in install-sh missing \
>   mkinstalldirs
> 
> The, if I run
> 
>   $ make dist
> 
> or
> 
>   $ make distcheck
> 
> the config.h.in file is not included in the tarball, so
> 'make distcheck' fails and 'make dist' produces a broken tarball.

Although this still holds true, it also happens if I use autoconf
instead of autoreconf.

> This does not happen if I use 'autoconf' instead of 'autoreconf':
> 
>   $ rm config.h.in
>   $ automake --add-missing
>   $ autoreconf
> 
> Resulting in 
> 
>   DIST_COMMON =  README ./stamp-h.in AUTHORS COPYING ChangeLog INSTALL \
>   Makefile.am Makefile.in NEWS acconfig.h acinclude.m4 aclocal.m4 \
>   config.guess config.h.in config.sub configure configure.in install-sh \
>                ^^^^^^^^^^^
>   missing mkinstalldirs
> 
> Once the config.h.in file has been generated once, everything
> works fine.

This is wrong.  The only way I could find to force that
config.h.in is included in DIST_COMMON is to run automake and
autoconf/autoreconf again:

  $ rm config.h.in
  $ automake --add-missing
  $ autoreconf
  $ automake
  $ autoreconf

Sorry for the confusion.

Bye

Dominik ^_^  ^_^

 --
Dominik Vogt, address@hidden
Reply-To: address@hidden



reply via email to

[Prev in Thread] Current Thread [Next in Thread]