[Top][All Lists]

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

Re: About config.status

From: Xue Fuqiao
Subject: Re: About config.status
Date: Tue, 19 Nov 2013 06:19:06 +0800

On Mon, Nov 18, 2013 at 10:59 PM, Eric Blake <address@hidden> wrote:
>> In (info "(autoconf) Output"):
>>   Every Autoconf script, e.g., '', should finish by calling
>>   'AC_OUTPUT'.
>> [...]
>>  -- Macro: AC_OUTPUT
>>      Generate 'config.status' and launch it.  Call this macro once, at
>>      the end of ''.
>> It seems that `config.status' is generated by autoconf (from
>>, 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.
> + autoconf => configure
> configure => config.status
> Or, in longhand, using autoconf on 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 or to hack on Autoconf.

I see.  Thanks for your help.


reply via email to

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