run time, run-time -> runtime

[Paul Eggert]

I noticed that the Autoconf documentation and comments weren't
consistent on "runtime" versus "run-time" versus "run time", so
I standardized on "runtime" as follows:

2006-04-23  Paul Eggert  <address@hidden>

        * doc/autoconf.texi (Runtime): Renamed from "Run Time".  All uses
        of "run time" and "run-time" changed to "runtime", for consistency.
        * lib/autoconf/fortran.m4: Likewise (in comment).
        * lib/autoconf/functions.m4: Likewise.
        * lib/autoconf/general.m4: Likewise.
        * lib/autoconf/headers.m4: Likewise.

Index: doc/autoconf.texi
===================================================================
RCS file: /cvsroot/autoconf/autoconf/doc/autoconf.texi,v
retrieving revision 1.998
diff -p -u -r1.998 autoconf.texi
--- doc/autoconf.texi   24 Apr 2006 05:54:54 -0000      1.998
+++ doc/autoconf.texi   24 Apr 2006 06:42:15 -0000
@@ -395,7 +395,7 @@ Writing Tests
 * Running the Preprocessor::    Detecting preprocessor symbols
 * Running the Compiler::        Detecting language or header features
 * Running the Linker::          Detecting library features
-* Run Time::                    Testing for run-time features
+* Runtime::                     Testing for runtime features
 * Systemology::                 A zoology of operating systems
 * Multiple Cases::              Tests for several possible values
 
@@ -699,7 +699,7 @@ Peter Simons}.
 @cindex GNU build system
 
 Autoconf solves an important problem---reliable discovery of
-system-specific build and run-time information---but this is only one
+system-specific build and runtime information---but this is only one
 piece of the puzzle for the development of portable software.  To this
 end, the @acronym{GNU} project has developed a suite of integrated
 utilities to finish the job Autoconf started: the @acronym{GNU} build
@@ -3753,7 +3753,7 @@ accept program names that are not prefix
 @cindex File, checking
 
 You might also need to check for the existence of files.  Before using
-these macros, ask yourself whether a run-time test might not be a better
+these macros, ask yourself whether a runtime test might not be a better
 solution.  Be aware that, like most Autoconf macros, they test a feature
 of the host machine, and therefore, they die when cross-compiling.
 
@@ -6122,7 +6122,7 @@ warnings, such as deprecation notices.
 The following macros check for C compiler or machine architecture
 features.  To check for characteristics not listed here, use
 @code{AC_COMPILE_IFELSE} (@pxref{Running the Compiler}) or
address@hidden (@pxref{Run Time}).
address@hidden (@pxref{Runtime}).
 
 @defmac AC_PROG_CC_STDC
 @acindex{PROG_CC_STDC}
@@ -6560,7 +6560,7 @@ Test whether the Fortran compiler accept
 The following macros check for Fortran compiler characteristics.
 To check for characteristics not listed here, use
 @code{AC_COMPILE_IFELSE} (@pxref{Running the Compiler}) or
address@hidden (@pxref{Run Time}), making sure to first set the
address@hidden (@pxref{Runtime}), making sure to first set the
 current language to Fortran 77 or Fortran via @code{AC_LANG([Fortran 77])}
 or @code{AC_LANG(Fortran)} (@pxref{Language Choice}).
 
@@ -6572,7 +6572,7 @@ or @code{AC_LANG(Fortran)} (@pxref{Langu
 @acindex{FC_LIBRARY_LDFLAGS}
 @ovindex FCLIBS
 Determine the linker flags (e.g., @option{-L} and @option{-l}) for the
address@hidden intrinsic and run-time libraries} that are required to
address@hidden intrinsic and runtime libraries} that are required to
 successfully link a Fortran program or shared library.  The output
 variable @code{FLIBS} or @code{FCLIBS} is set to these flags (which
 should be included after @code{LIBS} when linking).
@@ -6588,7 +6588,7 @@ linked together, then the C++ compiler/l
 global constructors, instantiating templates, enabling exception
 support, etc.).
 
-However, the Fortran intrinsic and run-time libraries must be linked in
+However, the Fortran intrinsic and runtime libraries must be linked in
 as well, but the C++ compiler/linker doesn't know by default how to add
 these Fortran 77 libraries.  Hence, this macro was created to determine
 these Fortran libraries.
@@ -7110,7 +7110,7 @@ software package, the best thing to do i
 * Running the Preprocessor::    Detecting preprocessor symbols
 * Running the Compiler::        Detecting language or header features
 * Running the Linker::          Detecting library features
-* Run Time::                    Testing for run-time features
+* Runtime::                     Testing for runtime features
 * Systemology::                 A zoology of operating systems
 * Multiple Cases::              Tests for several possible values
 @end menu
@@ -7422,7 +7422,7 @@ In Erlang tests, the created source file
 one @code{start/0} function, which is called to perform the test.  The
 @var{prologue} is optional code that is inserted between the module header and
 the @code{start/0} function definition.  @var{body} is the body of the
address@hidden/0} function without the final period (@pxref{Run Time}, about
address@hidden/0} function without the final period (@pxref{Runtime}, about
 constraints on this function's behaviour).
 
 For instance:
@@ -7603,7 +7603,7 @@ available.  Trying to link with the func
 approach because it avoids dealing with the variations in the options
 and output formats of @code{nm} and @code{ar} and in the location of the
 standard libraries.  It also allows configuring for cross-compilation or
-checking a function's run-time behavior if needed.  On the other hand,
+checking a function's runtime behavior if needed.  On the other hand,
 it can be slower than scanning the libraries once, but accuracy is more
 important than speed.
 
@@ -7627,7 +7627,7 @@ current compilation flags.
 
 It is customary to report unexpected failures with
 @code{AC_MSG_FAILURE}.  This macro does not try to execute the program;
-use @code{AC_RUN_IFELSE} if you need to do that (@pxref{Run Time}).
+use @code{AC_RUN_IFELSE} if you need to do that (@pxref{Runtime}).
 @end defmac
 
 The @code{AC_LINK_IFELSE} macro cannot be used for Erlang tests, since Erlang
@@ -7635,16 +7635,16 @@ programs are interpreted and do not requ
 
 
 
address@hidden Run Time
address@hidden Checking Run Time Behavior
address@hidden Runtime
address@hidden Checking Runtime Behavior
 
-Sometimes you need to find out how a system performs at run time, such
+Sometimes you need to find out how a system performs at runtime, such
 as whether a given function has a certain capability or bug.  If you
 can, make such checks when your program runs instead of when it is
 configured.  You can check for things like the machine's endianness when
 your program initializes itself.
 
-If you really need to test for a run-time behavior while configuring,
+If you really need to test for a runtime behavior while configuring,
 you can write a test program to determine the result, and compile and
 run it using @code{AC_RUN_IFELSE}.  Avoid running test programs if
 possible, because this prevents people from configuring your package for
@@ -7676,7 +7676,7 @@ It is customary to report unexpected fai
 @end defmac
 
 Try to provide a pessimistic default value to use when cross-compiling
-makes run-time tests impossible.  You do this by passing the optional
+makes runtime tests impossible.  You do this by passing the optional
 last argument to @code{AC_RUN_IFELSE}.  @command{autoconf} prints a
 warning message when creating @command{configure} each time it
 encounters a call to @code{AC_RUN_IFELSE} with no
@@ -10738,7 +10738,7 @@ significantly.  Anyway, this kind of con
 typical use of Autoconf.  In fact, it's even not recommended, because M4
 macros can't look into shell conditionals, so we may fail to expand a
 macro when it was expanded before in a conditional path, and the
-condition turned out to be false at run-time, and we end up not
+condition turned out to be false at runtime, and we end up not
 executing the macro at all.
 
 @node File Descriptors
@@ -14290,7 +14290,7 @@ AC_SUBST([CYCLE_OBJ])
 @code{AC_CONFIG_LINKS} (@pxref{Configuration Links}) is another good way
 to select variant source files, for example optimized code for some
 CPUs.  The configured CPU type doesn't always indicate exact CPU types,
-so some run-time capability checks may be necessary too.
+so some runtime capability checks may be necessary too.
 
 @example
 case $host in
@@ -14700,7 +14700,7 @@ edited @emph{only by users}, not by prog
 can either be based on the @code{prefix} variable, or be a standard
 location such as the user's home directory.  It could even be specified
 by an environment variable.  The programs should examine that file at
-run time, rather than at compile time.  Run-time configuration is more
+runtime, rather than at compile time.  Runtime configuration is more
 convenient for users and makes the configuration process simpler than
 getting the information while configuring.  @xref{Directory Variables, ,
 Variables for Installation Directories, standards, @acronym{GNU} Coding
@@ -16072,7 +16072,7 @@ AC_RUN_IFELSE(
 @end example
 
 @noindent
address@hidden Time}.
address@hidden
 @end defmac
 
 @defmac AC_UID_T
Index: lib/autoconf/fortran.m4
===================================================================
RCS file: /cvsroot/autoconf/autoconf/lib/autoconf/fortran.m4,v
retrieving revision 1.205
diff -p -u -r1.205 fortran.m4
--- lib/autoconf/fortran.m4     6 Apr 2006 11:24:00 -0000       1.205
+++ lib/autoconf/fortran.m4     24 Apr 2006 06:42:15 -0000
@@ -607,7 +607,7 @@ fi],
 # ----------------------
 #
 # Determine the linker flags (e.g. "-L" and "-l") for the Fortran
-# intrinsic and run-time libraries that are required to successfully
+# intrinsic and runtime libraries that are required to successfully
 # link a Fortran program or shared library.  The output variable
 # FLIBS/FCLIBS is set to these flags.
 #
@@ -621,7 +621,7 @@ fi],
 # like calling global constructors, instantiating templates, enabling
 # exception support, etc.).
 #
-# However, the Fortran intrinsic and run-time libraries must be
+# However, the Fortran intrinsic and runtime libraries must be
 # linked in as well, but the C++ compiler/linker doesn't know how to
 # add these Fortran libraries.  Hence, the macro
 # "AC_F77_LIBRARY_LDFLAGS" was created to determine these Fortran
Index: lib/autoconf/functions.m4
===================================================================
RCS file: /cvsroot/autoconf/autoconf/lib/autoconf/functions.m4,v
retrieving revision 1.98
diff -p -u -r1.98 functions.m4
--- lib/autoconf/functions.m4   8 Apr 2006 21:46:04 -0000       1.98
+++ lib/autoconf/functions.m4   24 Apr 2006 06:42:15 -0000
@@ -332,7 +332,7 @@ main ()
 AH_VERBATIM([STACK_DIRECTION],
 [/* If using the C implementation of alloca, define if you know the
    direction of stack growth for your system; otherwise it will be
-   automatically deduced at run-time.
+   automatically deduced at runtime.
        STACK_DIRECTION > 0 => grows toward higher addresses
        STACK_DIRECTION < 0 => grows toward lower addresses
        STACK_DIRECTION = 0 => direction of growth unknown */
Index: lib/autoconf/general.m4
===================================================================
RCS file: /cvsroot/autoconf/autoconf/lib/autoconf/general.m4,v
retrieving revision 1.910
diff -p -u -r1.910 general.m4
--- lib/autoconf/general.m4     23 Apr 2006 06:49:53 -0000      1.910
+++ lib/autoconf/general.m4     24 Apr 2006 06:42:15 -0000
@@ -2353,9 +2353,9 @@ AC_LINK_IFELSE([AC_LANG_PROGRAM([[$2]], 
 
 
 
-## -------------------------------- ##
-## Checking for run-time features.  ##
-## -------------------------------- ##
+## ------------------------------- ##
+## Checking for runtime features.  ##
+## ------------------------------- ##
 
 
 # _AC_RUN_IFELSE(PROGRAM, [ACTION-IF-TRUE], [ACTION-IF-FALSE])
Index: lib/autoconf/headers.m4
===================================================================
RCS file: /cvsroot/autoconf/autoconf/lib/autoconf/headers.m4,v
retrieving revision 1.48
diff -p -u -r1.48 headers.m4
--- lib/autoconf/headers.m4     8 Apr 2006 21:46:04 -0000       1.48
+++ lib/autoconf/headers.m4     24 Apr 2006 06:42:15 -0000
@@ -599,7 +599,7 @@ AC_DEFUN([AC_HEADER_STDBOOL],
            This test is not quite right, since xlc is allowed to
            reject this program, as the initializer for xlcbug is
            not one of the forms that C requires support for.
-           However, doing the test right would require a run-time
+           However, doing the test right would require a runtime
            test, and that would make cross-compilation harder.
            Let us hope that IBM fixes the xlc bug, and also adds
            support for this kind of constant expression.  In the