changes, what else?

[deliverable/binutils-gdb.git] / configure.texi

diff --git a/configure.texi b/configure.texi
index 4da610046adeae3411850dc36f0d3e0ca63bace1..b9170a3a41a3a5d1a33562d6063ba8309c11859c 100644 (file)
--- a/configure.texi
+++ b/configure.texi
@@ -244,6 +244,30 @@ This option sets the @code{configure} variable @code{prefix}.  Generated
 Makefiles will have their @code{prefix} variables set to this value.
 (See @ref{Install Details}.)
 
+@item -program_prefix=@var{string}
+Configure the source to install certain programs using @var{string} as a
+prefix.  This applies to programs which might be used for cross-compilation,
+such as the compiler and the binutils, and also to programs which have the same
+name as a common Unix program, such as make.
+
+This option sets the @code{configure} variable @code{program_prefix}.
+Generated Makefiles will have their @code{program_prefix} variables set to this
+value.  (See @ref{Install Details}.)
+
+@item -program_suffix=@var{string}
+Configure the source to install certain programs using @var{string} as a
+suffix.  This applies to programs which might be used for cross-compilation.
+
+@item -program_transform_name=@var{sed-pattern}
+Configure the source to install certain programs using the names that result
+from passing the usual name through @code{sed} invoked with @var{sed-pattern}.
+This option may be given multiple times; each @var{sed-pattern} will be applied
+in turn.  This applies to programs which might be used for cross-compilation.
+
+This option sets the @code{configure} variable @code{program_transform_name}.
+Generated Makefiles will have their @code{program_transform_name} variables set
+to this value.  (See @ref{Install Details}.)
+
 @item -recurring
 @c Wouldn't it make more sense to call this "-quiet"? (FIXME).
 This option is used internally by @code{configure} when recurring on
@@ -1013,12 +1037,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}
@@ -1044,12 +1075,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}