[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: About config.status
|
From: |
Eric Blake |
|
Subject: |
Re: About config.status |
|
Date: |
Mon, 18 Nov 2013 07:59:14 -0700 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 |
On 11/18/2013 05:39 AM, Xue Fuqiao wrote:
> Hi list,
>
> In (info "(autoconf) Output"):
>
> Every Autoconf script, e.g., 'configure.ac', should finish by calling
> 'AC_OUTPUT'.
> [...]
> -- Macro: AC_OUTPUT
> Generate 'config.status' and launch it. Call this macro once, at
> the end of 'configure.ac'.
>
> It seems that `config.status' is generated by autoconf (from
> configure.ac), but (info "(autoconf) config.status Invocation")
> indicates that `config.status' is generated by `configure'. I've read
> (info "(autoconf) FAQ"), but it didn't help. Can anyone point me in the
> right direction?
Both statements are true, if you allow for transitivity.
configure.ac + autoconf => configure
configure => config.status
Or, in longhand, using autoconf on configure.ac generates a shell script
(configure) which in turn generates another shell script
(config.status). If you want to change what gets put in config.status,
your options are to alter your configure.ac or to hack on Autoconf.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature