This is the mail archive of the
automake@gnu.org
mailing list for the automake project.
Re: invoking config.status
- From: Raja R Harinath <harinath at cs dot umn dot edu>
- To: Harlan Stenn <Harlan dot Stenn at pfcs dot com>
- Cc: automake at gnu dot org
- Date: Fri, 23 Aug 2002 22:45:10 -0500
- Subject: Re: invoking config.status
- References: <6312.1030148283@dog.pfcs.com>
Hi,
Harlan Stenn <Harlan.Stenn@pfcs.com> writes:
> Under 1.5, it would appear that:
>
> CONFIG_FILES=Makefile config.status
>
> differs from:
>
> config.status Makefile
Well, this is a 'autoconf 2.5x' feature.
> in 2 ways:
>
> - "config.status Makefile" will look up the input templates and follow them,
> producing the Makefile as specified from AC_CONFIG_FILES(...) .
This is right.
> - "CONFIG_FILES=Makefile config.status" will produce Makefile using the
> implicit template Makefile:Makefile.in, and then run the default-1
> script (ie, "do the dependency thing").
The first part of this may be a bug in (older?) versions of 'autoconf'.
[snip]
> As for the "run the dependency stuff" piece, is it a bug or a feature that
> it's run in one case and not in the other? I'm not sure if the behavior has
> changed in 1.6.3 or not - I'll probably dig there this weekend.
I guess it's a feature in 'autoconf'. This is handled, somewhat
hackily, in v1.6: look for $(am__depfiles_maybe). It is waiting for
a better way to express hooks on CONFIG_FILES in 'autoconf'.
- Hari
--
Raja R Harinath ------------------------------ harinath@cs.umn.edu