[SCM] GNU Autoconf source repository branch, master, updated. v2.63-291-gefb3e8a

[Eric Blake]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU Autoconf source repository".

http://git.sv.gnu.org/gitweb/?p=autoconf.git;a=commitdiff;h=efb3e8a738994924dfed0e1d73c91e0678622b3b

The branch, master has been updated
       via  efb3e8a738994924dfed0e1d73c91e0678622b3b (commit)
       via  e5f657f31e671e95c4989a2840d5053ed1f3cda6 (commit)
       via  996eb0c086f82492d7623d5105abdd450812e460 (commit)
       via  26a4c7275d690900c7c4b4ab9017e6fcce00f372 (commit)
      from  239b0528b2dde294542b2a12b1d4811107cc8a30 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit efb3e8a738994924dfed0e1d73c91e0678622b3b
Author: Eric Blake <address@hidden>
Date:   Tue Mar 17 07:39:40 2009 -0600

    Use test consistently in examples.
    
    * doc/autoconf.texi (Subdirectories, Caching Results)
    (Common Shell Constructs, Prerequisite Macros, Coding Style)
    (Changed Results, Particular Programs, Defining Symbols):
    Protect against arbitrary user strings.
    (Multiple Cases): Mention why $fstype does not need protection.
    Reported by Reuben Thomas.
    
    Signed-off-by: Eric Blake <address@hidden>

commit e5f657f31e671e95c4989a2840d5053ed1f3cda6
Author: Eric Blake <address@hidden>
Date:   Tue Mar 17 06:38:07 2009 -0600

    Improve confusing section names.
    
    * doc/autoconf.texi (Specifying Names): Rename node...
    (Specifying Target Triplets): ...to this.
    (Generic Programs): Adjust references.
    * doc/install.texi (System Type): Touch up formatting.
    * THANKS: Update.
    Reported by Tim Freeman, in http://bugs.debian.org/312873.
    
    Signed-off-by: Eric Blake <address@hidden>

commit 996eb0c086f82492d7623d5105abdd450812e460
Author: Eric Blake <address@hidden>
Date:   Tue Mar 17 06:09:22 2009 -0600

    Remove historical inaccuracy.
    
    * doc/autoconf.texi (Portable Shell): Don't perpetuate myth about
    Reported by Reuben Thomas.
    
    Signed-off-by: Eric Blake <address@hidden>

commit 26a4c7275d690900c7c4b4ab9017e6fcce00f372
Author: Eric Blake <address@hidden>
Date:   Tue Mar 17 06:05:11 2009 -0600

    Recommend AS_HELP_STRING more prominently.
    
    * doc/autoconf.texi (External Software): Reduce mention of
    hand-written help strings.
    Reported by Reuben Thomas.
    
    Signed-off-by: Eric Blake <address@hidden>

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog         |   28 +++++++++++++++++++++
 THANKS            |    1 +
 doc/autoconf.texi |   71 ++++++++++++++++++++++++++---------------------------
 doc/install.texi  |    5 ++-
 4 files changed, 67 insertions(+), 38 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 78ac194..05e3a4d 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,31 @@
+2009-03-17  Eric Blake  <address@hidden>
+
+       Use test consistently in examples.
+       * doc/autoconf.texi (Subdirectories, Caching Results)
+       (Common Shell Constructs, Prerequisite Macros, Coding Style)
+       (Changed Results, Particular Programs, Defining Symbols):
+       Protect against arbitrary user strings.
+       (Multiple Cases): Mention why $fstype does not need protection.
+       Reported by Reuben Thomas.
+
+       Improve confusing section names.
+       * doc/autoconf.texi (Specifying Names): Rename node...
+       (Specifying Target Triplets): ...to this.
+       (Generic Programs): Adjust references.
+       * doc/install.texi (System Type): Touch up formatting.
+       * THANKS: Update.
+       Reported by Tim Freeman, in http://bugs.debian.org/312873.
+
+       Remove historical inaccuracy.
+       * doc/autoconf.texi (Portable Shell): Don't perpetuate myth about
+       #!/bin/sh needing a space.
+       Reported by Reuben Thomas.
+
+       Recommend AS_HELP_STRING more prominently.
+       * doc/autoconf.texi (External Software): Reduce mention of
+       hand-written help strings.
+       Reported by Reuben Thomas.
+
 2009-03-16  Eric Blake  <address@hidden>
 
        Fix 'make pdf'.
diff --git a/THANKS b/THANKS
index 5cb10cb..c3e19a2 100644
--- a/THANKS
+++ b/THANKS
@@ -342,6 +342,7 @@ Ted Bullock                 address@hidden
 Theodore Ts'o               address@hidden
 Thien-Thi Nguyen            address@hidden
 Thomas Winder               address@hidden
+Tim Freeman                 address@hidden
 Tim Mooney                  address@hidden
 Tim Rice                    address@hidden
 Tim Van Holder              address@hidden
diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index 6109bb2..a0a19b8 100644
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -537,7 +537,7 @@ Portable C and C++ Programming
 
 Manual Configuration
 
-* Specifying Names::            Specifying the system type
+* Specifying Target Triplets::  Specifying target triplets
 * Canonicalizing::              Getting the canonical system type
 * Using System Type::           What to do with the system type
 
@@ -3510,7 +3510,7 @@ Make @code{AC_OUTPUT} run @command{configure} in each 
subdirectory
 be a literal, i.e., please do not use:
 
 @example
-if test "$package_foo_enabled" = yes; then
+if test "x$package_foo_enabled" = xyes; then
   $my_subdirs="$my_subdirs foo"
 fi
 AC_CONFIG_SUBDIRS([$my_subdirs])
@@ -3522,7 +3522,7 @@ displaying the options of the package @code{foo}.  
Instead, you should
 write:
 
 @example
-if test "$package_foo_enabled" = yes; then
+if test "x$package_foo_enabled" = xyes; then
   AC_CONFIG_SUBDIRS([foo])
 fi
 @end example
@@ -3930,7 +3930,7 @@ is suggested that you use this Autoconf snippet:
 
 @example
 AC_PROG_LEX
-if test "$LEX" != flex; then
+if test "x$LEX" != xflex; then
   LEX="$SHELL $missing_dir/missing flex"
   AC_SUBST([LEX_OUTPUT_ROOT], [lex.yy])
   AC_SUBST([LEXLIB], [''])
@@ -4058,7 +4058,7 @@ with a prefix of the target type as determined by
 If the tool cannot be found with a prefix, and if the build and target
 types are equal, then it is also searched for without a prefix.
 
-As noted in @ref{Specifying Names, , Specifying the system type}, the
+As noted in @ref{Specifying Target Triplets}, the
 target is rarely specified, because most of the time it is the same
 as the host: it is the type of system for which any compiler tool in
 the package produces code.  What this macro looks for is,
@@ -4084,8 +4084,7 @@ sets @code{RANLIB} to @file{i386-gnu-ranlib} if that 
program exists in
 
 When cross-compiling, this macro will issue a warning if no program
 prefixed with the host type could be found.
-For more information, see @ref{Specifying Names, , Specifying the
-system type}.
+For more information, see @ref{Specifying Target Triplets}.
 @end defmac
 
 @defmac AC_CHECK_TARGET_TOOLS (@var{variable}, @var{progs-to-check-for}, @
@@ -4118,8 +4117,7 @@ is not changed.  Calls @code{AC_SUBST} for @var{variable}.
 
 When cross-compiling, this macro will issue a warning if no program
 prefixed with the host type could be found.
-For more information, see @ref{Specifying Names, , Specifying the
-system type}.
+For more information, see @ref{Specifying Target Triplets}.
 @end defmac
 
 @anchor{AC_PATH_PROG}
@@ -4197,8 +4195,7 @@ name of the program if it is found.
 
 When cross-compiling, this macro will issue a warning if no program
 prefixed with the host type could be found.
-For more information, see @ref{Specifying Names, , Specifying the
-system type}.
+For more information, see @ref{Specifying Target Triplets}.
 @end defmac
 
 
@@ -8609,7 +8606,9 @@ easy to simulate by using a shell variable to keep track 
of whether a
 way to perform the operation has been found yet.
 
 Here is an example that uses the shell variable @code{fstype} to keep
-track of whether the remaining cases need to be checked.
+track of whether the remaining cases need to be checked.  Note that
+since the value of @code{fstype} is under our control, we don't have to
+use the longer @samp{test "x$fstype" = xno}.
 
 @example
 @group
@@ -8677,7 +8676,7 @@ appropriate cache variable, as in this example:
 @example
 AC_CHECK_FUNC([vprintf], [AC_DEFINE([HAVE_VPRINTF], [1],
                           [Define if vprintf exists.])])
-if test "$ac_cv_func_vprintf" != yes; then
+if test "x$ac_cv_func_vprintf" != xyes; then
   AC_CHECK_FUNC([_doprnt], [AC_DEFINE([HAVE_DOPRNT], [1],
                             [Define if _doprnt exists.])])
 fi
@@ -9019,7 +9018,7 @@ AC_DEFUN([AC_SHELL_TRUE],
 [AC_CACHE_CHECK([whether true(1) works], [my_cv_shell_true_works],
                 [my_cv_shell_true_works=no
                  (true) 2>/dev/null && my_cv_shell_true_works=yes
-                 if test "$my_cv_shell_true_works" = yes; then
+                 if test "x$my_cv_shell_true_works" = xyes; then
                    AC_DEFINE([TRUE_WORKS], [1],
                              [Define if `true(1)' works properly.])
                  fi])
@@ -9038,7 +9037,7 @@ AC_DEFUN([AC_SHELL_TRUE],
 [AC_CACHE_CHECK([whether true(1) works], [my_cv_shell_true_works],
                 [my_cv_shell_true_works=no
                  (true) 2>/dev/null && my_cv_shell_true_works=yes])
- if test "$my_cv_shell_true_works" = yes; then
+ if test "x$my_cv_shell_true_works" = xyes; then
    AC_DEFINE([TRUE_WORKS], [1],
              [Define if `true(1)' works properly.])
  fi
@@ -12411,8 +12410,8 @@ simplifications if either @var{run-if-true1} or 
@var{run-if-false}
 is empty.  For example,
 
 @example
-AS_IF([test "$foo" = yes], [HANDLE_FOO([yes])],
-      [test "$foo" != no], [HANDLE_FOO([maybe])],
+AS_IF([test "x$foo" = xyes], [HANDLE_FOO([yes])],
+      [test "x$foo" != xno], [HANDLE_FOO([maybe])],
       [echo foo not specified])
 @end example
 
@@ -12465,7 +12464,7 @@ Transform @var{expression} into a valid shell variable 
name.  For example:
 # This outputs "Have it!".
 header="sys/some file.h"
 AS_TR_SH([HAVE_$header])=yes
-if test "$HAVE_sys_some_file_h" = yes; then echo "Have it!"; fi
+if test "x$HAVE_sys_some_file_h" = xyes; then echo "Have it!"; fi
 @end example
 @end defmac
 
@@ -13145,7 +13144,7 @@ AC_DEFUN([TRAVOLTA],
 [test "$body_temperature_in_celsius" -gt "38" &&
   dance_floor=occupied])
 AC_DEFUN([NEWTON_JOHN],
-[test "$hair_style" = "curly" &&
+[test "x$hair_style" = xcurly &&
   dance_floor=occupied])
 @end group
 
@@ -13164,7 +13163,7 @@ with this @file{configure.ac}
 @example
 AC_INIT([Dance Manager], [1.0], [bug-dance@@example.org])
 RESERVE_DANCE_FLOOR
-if test "$dance_floor" = occupied; then
+if test "x$dance_floor" = xoccupied; then
   AC_MSG_ERROR([cannot pick up here, let's move])
 fi
 @end example
@@ -13177,7 +13176,7 @@ other times than Saturday night since it expands into:
 @group
 test "$body_temperature_in_Celsius" -gt "38" &&
   dance_floor=occupied
-test "$hair_style" = "curly" &&
+test "x$hair_style" = xcurly &&
   dance_floor=occupied
 fi
 if date | grep '^Sat.*pm' >/dev/null 2>&1; then
@@ -13609,7 +13608,7 @@ AC_DEFUN(_AC_EMXOS2,
 [AC_CACHE_CHECK(for EMX OS/2 environment, ac_cv_emxos2,
 [AC_COMPILE_IFELSE([AC_LANG_PROGRAM(, return __EMX__;)],
 ac_cv_emxos2=yes, ac_cv_emxos2=no)])
-test "$ac_cv_emxos2" = yes && EMXOS2=yes])
+test "x$ac_cv_emxos2" = xyes && EMXOS2=yes])
 @end example
 
 @noindent
@@ -13624,7 +13623,7 @@ m4_define([_AC_EMXOS2],
 [AC_COMPILE_IFELSE([AC_LANG_PROGRAM([], [return __EMX__;])],
                    [ac_cv_emxos2=yes],
                    [ac_cv_emxos2=no])])
-test "$ac_cv_emxos2" = yes && EMXOS2=yes[]dnl
+test "x$ac_cv_emxos2" = xyes && EMXOS2=yes[]dnl
 ])# _AC_EMXOS2
 @end example
 
@@ -13691,8 +13690,6 @@ Builtins, , Limitations of Shell Builtins}.
 Some ancient systems have quite
 small limits on the length of the @samp{#!} line; for instance, 32
 bytes (not including the newline) on SunOS 4.
-A few ancient address@hidden based systems (such as Dynix circa 1984)
-required a single space between the @samp{#!} and the @samp{/}.
 However, these ancient systems are no longer of practical concern.
 
 The set of external programs you should run in a @command{configure} script
@@ -18974,18 +18971,22 @@ looking for libraries that are unique to particular 
systems.  However,
 Autoconf provides a uniform method for handling unguessable features.
 
 @menu
-* Specifying Names::            Specifying the system type
+* Specifying Target Triplets::  Specifying target triplets
 * Canonicalizing::              Getting the canonical system type
 * Using System Type::           What to do with the system type
 @end menu
 
address@hidden Specifying Names
address@hidden Specifying the System Type
address@hidden Specifying Target Triplets
address@hidden Specifying target triplets
 @cindex System type
address@hidden Target triplet
address@hidden This node used to be named Specifying Names.  The @anchor allows 
old
address@hidden links to still work.
address@hidden Names}
 
 Autoconf-generated
 @command{configure} scripts can make decisions based on a canonical name
-for the system type, which has the form:
+for the system type, or @dfn{target triplet}, which has the form:
 @address@hidden@address@hidden, where @var{os} can be
 @address@hidden or @address@hidden@var{system}}
 
@@ -18995,7 +18996,8 @@ system it's running on.  To do so it runs a script 
called
 command or symbols predefined by the C preprocessor.
 
 Alternately, the user can specify the system type with command line
-arguments to @command{configure}.  Doing so is necessary when
+arguments to @command{configure} (@pxref{System Type}.  Doing so is
+necessary when
 cross-compiling.  In the most complex case of cross-compiling, three
 system types are involved.  The options to specify them are:
 
@@ -19328,11 +19330,8 @@ looks like this:
 @noindent
 @var{help-string} may be more than one line long, if more detail is
 needed.  Just make sure the columns line up in @samp{configure
---help}.  Avoid tabs in the help string.  You'll need to enclose the
-help string in @samp{[} and @samp{]} in order to produce the leading
-blanks.
-
-You should format your @var{help-string} with the macro
+--help}.  Avoid tabs in the help string.  The easiest way to provide the
+proper leading whitespace is to format your @var{help-string} with the macro
 @code{AS_HELP_STRING} (@pxref{Pretty Help Strings}).
 
 The following example shows how to use the @code{AC_ARG_WITH} macro in
@@ -21450,7 +21449,7 @@ Here is a way to write it for version 2:
 
 @example
 AC_CHECK_FUNCS([syslog])
-if test $ac_cv_func_syslog = no; then
+if test "x$ac_cv_func_syslog" = xno; then
   # syslog is not in the default libraries.  See if it's in some other.
   for lib in bsd socket inet; do
     AC_CHECK_LIB([$lib], [syslog], [AC_DEFINE([HAVE_SYSLOG])
diff --git a/doc/install.texi b/doc/install.texi
index d498639..a51882c 100644
--- a/doc/install.texi
+++ b/doc/install.texi
@@ -7,7 +7,7 @@
 @unnumbered Installation Instructions
 
 Copyright @copyright{} 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004,
-2005, 2006, 2007, 2008 Free Software Foundation, Inc.
+2005, 2006, 2007, 2008, 2009 Free Software Foundation, Inc.
 
 This file is free documentation; the Free Software Foundation gives
 unlimited permission to copy, distribute and modify it.
@@ -242,7 +242,8 @@ which has the form:
 where @var{system} can have one of these forms:
 
 @example
address@hidden @address@hidden
address@hidden
address@hidden@var{os}
 @end example
 
 See the file @file{config.sub} for the possible values of each field.


hooks/post-receive
--
GNU Autoconf source repository