mirror/autoconf
2
0
Fork 0
mirror of git://git.sv.gnu.org/autoconf synced 2024-11-21 01:01:48 +08:00
Code Issues Packages Projects Releases Wiki Activity

* doc/autoconf.texi (Setting Output Variables): Clarify what

Browse Source 
precious variables are.
Suggested by Pontus Skoeld.
This commit is contained in:
Akim Demaille 2002-09-06 11:10:37 +00:00
parent f0d92912ac
commit 899f0c52eb
3 changed files with 19 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
ChangeLog
View File

@ -1,3 +1,9 @@
2002-09-06 Akim Demaille <akim@epita.fr>
* doc/autoconf.texi (Setting Output Variables): Clarify what
precious variables are.
Suggested by Pontus Skoeld.
2002-09-05 Akim Demaille <akim@epita.fr>
* bin/Makefile.am (autoconf, autoheader, autoreconf, autoupdate)

1
THANKS
View File

@ -144,6 +144,7 @@ Peter Eisentraut peter_e@gmx.net
Peter Simons simons@research.cys.de
Peter Stephenson pws@csr.com
Philipp Thomas kthomas@gwdg.de
Pontus Skoeld pont@soua.net
Rainer Orth ro@TechFak.Uni-Bielefeld.DE
Raja R Harinath harinath@cs.umn.edu
Ralf Corsepius corsepiu@faw.uni-ulm.de

17
doc/autoconf.texi
View File

@ -6219,11 +6219,18 @@ Being precious means that
@var{variable} is @code{AC_SUBST}'d.
@item
@var{variable} is kept in the cache including if it was not specified on
the @samp{./configure} command line. Indeed, while @command{configure}
can notice the definition of @code{CC} in @samp{./configure
CC=bizarre-cc}, it is impossible to notice it in @samp{CC=bizarre-cc
./configure}, which, unfortunately, is what most users do.
The value of @var{variable} when @command{configure} was launched is
saved in the cache, including if it was not specified on the command
line but via the environment. Indeed, while @command{configure} can
notice the definition of @code{CC} in @samp{./configure CC=bizarre-cc},
it is impossible to notice it in @samp{CC=bizarre-cc ./configure},
which, unfortunately, is what most users do.
We emphasize that it is the @emph{initial} value of @var{variable} which
is saved, not that found during the execution of @command{configure}.
Indeed, specifying @samp{./configure FOO=foo} and letting
@samp{./configure} guess that @code{FOO} is @code{foo} can be two very
different runs.
@item
@var{variable} is checked for consistency between two