* cpu-z8k.c (compatible): made static to reduce name space

[binutils-gdb.git] / configure.texi

diff --git a/configure.texi b/configure.texi
index 89bcef7c13ca1d546f9a56074a1dd3d9ca0e3aa5..3ed1d09f2351950246308effd9ecc3fdfdbcb28f 100644 (file)
--- a/configure.texi
+++ b/configure.texi
@@ -10,6 +10,14 @@
 @end tex
 @setchapternewpage off
 
+@ifinfo
+@format
+START-INFO-DIR-ENTRY
+* configure: (configure).              Cygnus configure.
+END-INFO-DIR-ENTRY
+@end format
+@end ifinfo
+
 @ifinfo
 This document attempts to describe the Cygnus Support version of
 @code{configure}.
@@ -64,11 +72,6 @@ by Cygnus Support.
 @end titlepage
 
 @ifinfo
-@format
-START-INFO-DIR-ENTRY
-* configure: (configure.info). Cygnus configure.
-END-INFO-DIR-ENTRY
-@end format
 
 @node top, What Configure Does, (dir), (dir)
 @top top
@@ -986,7 +989,7 @@ recur.  You must usually set this in the per-invocation section of
 @file{configure.in}.
 If @file{Makefile.in} contains a line starting with @code{SUBDIRS =},
 then it will be replaced with an assignment to @code{SUBDIRS} using
-the value of @code{configdirs} (if #code{subdirs} is empty).  This can
+the value of @code{configdirs} (if @code{subdirs} is empty).  This can
 be used to determine which directories to configure and build depending
 on the host and target configurations.
 @c Most other matching makefile/config vars use the same name.  Why not
@@ -1010,12 +1013,19 @@ same Makefile fragments, and the same @code{configure.in}.
 @end defvar
 
 @defvar{host}
-Contains the name that the user entered for the host.  Since many things
-that the user could enter would map to the same output from
-@code{config.sub}, this variable is innappropriate to use for picking
-available configurations.  For that, use @code{host_cpu},
-@code{host_vendor}, and/or @code{host_os}.  This variable is useful,
-however, for error messages.
+Contains the full configuration name (generated by the script
+@file{config.sub} from the name that the user entered) for the host.
+This is a three-part name of the form 
+
+@example
+@var{cpu}-@var{vendor}-@var{os}
+@end example
+
+@noindent
+There are separate variables @code{host_cpu}, @code{host_vendor}, and
+@code{host_os} that you can use to test each of the three parts; this
+variable is useful, however, for error messages, and for testing
+combinations of the three components.
 @end defvar
 
 @defvar{host_cpu}
@@ -1041,12 +1051,19 @@ host as returned by @file{config.sub}.
 @end defvar
 
 @defvar{target}
-Contains the  name that the user entered for the target.  Since
-many things that the user could enter would map to the same canonical
-triple, this variable is innappropriate to use for picking available
-configurations.  For that, use @code{target_cpu}, @code{target_vendor},
-and/or @code{target_os}.  This variable is useful, however, for error
-messages.
+Contains the full configuration name (generated by the script
+@file{config.sub} from the name that the user entered) for the target.
+This is a three-part name of the form 
+
+@example
+@var{cpu}-@var{vendor}-@var{os}
+@end example
+
+@noindent
+There are separate variables @code{target_cpu}, @code{target_vendor}, and
+@code{target_os} that you can use to test each of the three parts; this
+variable is useful, however, for error messages, and for testing
+combinations of the three components.
 @end defvar
 
 @defvar{target_cpu}
@@ -1077,8 +1094,8 @@ might also be use to decide which libraries to build or what user
 interface the tool should provide.
 @end defvar
 
-@defvar{nfp}
-Is set to @code{true} if the user invoked configure with the @code{-nfp}
+@defvar{floating_point}
+Is set to @code{no} if the user invoked configure with the @code{-nfp}
 command line option, otherwise it is empty.  This is a request to target
 machines with @emph{no floating point} unit, even if the targets
 ordinarily have floating point units available.  This option has no