[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH 5/5] Use consistent notation for cache variables.
From: |
Ralf Wildenhues |
Subject: |
[PATCH 5/5] Use consistent notation for cache variables. |
Date: |
Sun, 13 Sep 2009 10:36:43 +0200 |
User-agent: |
Mutt/1.5.20 (2009-08-09) |
* doc/autoconf.texi (Generic Programs): Remove `$' before
variable name.
---
doc/autoconf.texi | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index 9206475..379a553 100644
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -4255,13 +4255,13 @@ Generic Programs
@acindex{PATH_PROGS_FEATURE_CHECK}
@caindex address@hidden
This macro was introduced in Autoconf 2.62. If @var{variable} is not
-empty, then set the cache variable @address@hidden to
+empty, then set the cache variable @address@hidden to
its value. Otherwise, check for each program in the blank-separated
list @var{progs-to-check-for} existing in @var{path}. For each program
-found, execute @var{feature-test} with @address@hidden
+found, execute @var{feature-test} with @address@hidden
set to the absolute name of the candidate program. If no invocation of
@var{feature-test} sets the shell variable
address@hidden@var{variable}}, then @var{action-if-not-found} is
address@hidden@var{variable}}, then @var{action-if-not-found} is
executed. @var{feature-test} will be run even when
@address@hidden is set, to provide the ability to
choose a better candidate found later in @var{path}; to accept the
--
1.6.3.2.388.gb7132
- Re: [PATCH 2/5] New FAQ node: Debugging., (continued)
[PATCH 3/5] New cache variable index in the manual., Ralf Wildenhues, 2009/09/13
[PATCH 4/5] Documentation of specific and general cache variables., Ralf Wildenhues, 2009/09/13
[PATCH 5/5] Use consistent notation for cache variables.,
Ralf Wildenhues <=