OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update descriptions for ${host} and ${target} to reflect that they are now 

canonical triples, not the original user entries.
This commit is contained in:
Roland Pesch 1992-08-13 23:31:53 +00:00
parent c8c7e0bf25
commit 3a0055878e
1 changed files with 26 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
configure.texi
View File

@ -1013,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}
@ -1044,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}