automake-patches
[Top][All Lists]
Advanced

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

[PATCH 2/3] Replace 'configure' with '@command{configure}' as appropriat


From: William Pursell
Subject: [PATCH 2/3] Replace 'configure' with '@command{configure}' as appropriate.
Date: Mon, 01 Dec 2008 21:06:18 +0000
User-agent: Thunderbird 2.0.0.18 (Macintosh/20081105)


There are several occurences of the phrase 'at configure time'
where it may be appropriate to make this change as well, but
it is not clear to me that doing so is correct and I'm
applying the principal of minimal change.  (aka laziness).
---
 doc/automake.texi |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/automake.texi b/doc/automake.texi
index d93f1e3..91ad424 100644
--- a/doc/automake.texi
+++ b/doc/automake.texi
@@ -2160,7 +2160,7 @@ things so that the build can continue.

 @item mkinstalldirs
 This script used to be a wrapper around @samp{mkdir -p}, which is not
-portable.  Now we prefer to use @samp{install-sh -d} when configure
+portable.  Now we prefer to use @samp{install-sh -d} when @command{configure}
 finds that @samp{mkdir -p} does not work, this makes one less script to
 distribute.

@@ -7447,12 +7447,12 @@ The Python version number, in the form @address@hidden
 @item PYTHON_PREFIX
 The string @address@hidden@}}.  This term may be used in future work
 that needs the contents of Python's @samp{sys.prefix}, but general
-consensus is to always use the value from configure.
+consensus is to always use the value from @command{configure}.

 @item PYTHON_EXEC_PREFIX
 The string @address@hidden@}}.  This term may be used in future work
 that needs the contents of Python's @samp{sys.exec_prefix}, but general
-consensus is to always use the value from configure.
+consensus is to always use the value from @command{configure}.

 @item PYTHON_PLATFORM
 The canonical name used by Python to describe the operating system, as
@@ -8475,7 +8475,7 @@ macros with side effects.
 @code{CONFIG_STATUS_DEPENDENCIES} adds dependencies to the
 @file{config.status} rule, whose effect is to run @file{configure}.
 This variable should therefore carry any non-standard source that may
-be read as a side effect of running configure, like @file{version.sh}
+be read as a side effect of running @command{configure}, like @file{version.sh}
 in the example above.

 Speaking of @file{version.sh} scripts, we recommend against them
--
1.6.0.4.782.geea74.dirty


--
William Pursell




reply via email to

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