[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue in autoconf with config.status generation
From: |
Ralf Wildenhues |
Subject: |
Re: Issue in autoconf with config.status generation |
Date: |
Thu, 18 Sep 2008 18:25:30 +0200 |
User-agent: |
Mutt/1.5.17+20080114 (2008-01-14) |
Hello Evan,
* Evan Hunter wrote on Thu, Sep 18, 2008 at 05:20:08PM CEST:
>
> As I understand it, the 'config.status --recheck' command is supposed
> re-run the configure script using all the same options as it was
> originally run with.
> The problem I'm finding is that the command-line options are being
> saved in the config.status, but not the environment variables.
No. Exception are the "precious" variables that have been declared as
such with AC_ARG_VAR. It was deemed infeasible to save the state of all
environment variables, for several practical reasons.
That's why, instead of
> CRITICAL_VARIABLE=ok ./configure
you are now encouraged to use
./configure CRITICAL_VARIABLE=ok
for variables you want saved and restored.
Cheers,
Ralf