Specifying Names for Hosts and Targets
Your CD or media is labeled to indicate the host (and target, if applicable) for which the binaries in GNUPro Toolkit are configured. The specifications used for hosts and targets in the configure script are based on a three-part naming scheme, though the scheme is slightly different between hosts and targets.
The
full naming scheme for hosts in the following pattern encodes three pieces
of information.
architecture-vendor-operating
system
For example, the full name
for a Sun SPARCstation running SunOS 4.1.4 is:
sparc-sun-sunos4.1.
Warning:
configure
can represent a very large number of combinations of architecture, vendor,
and operating system. There is by no means support for all possible combinations!
The following combinations refer to hosts supported by Cygnus Solutions. The OS versions shown are the versions under which this release was built. If you have any questions regarding compatibility, please feel free to contact Cygnus Solutions. (For a matrix which shows all supported host/target combinations, see Native Configurations Supported, Embedded Configurations Supported and Specific Processor Support by Family in Release Notes for GNUPro Toolkit.)
Canonical name | Platform |
alpha-dec-osf3.2C | DEC Alpha Digital UNIX v3.2C |
alpha-dec-osf4.0 | DEC Alpha Digital UNIX v4.0 |
hppa1.1-hp-hpux9 | HP 9000/700, HP-UX A.9.0.5 |
hppa1.1-hp-hpux10 | HP 9000/700, HP-UX B.10.01 |
hppa1.1-hp-hpux10.20 | HP 9000/700, HP-UX B.10.20 |
i386-univel-sysv4.2 | Unixware 2.1.1 |
mips-sgi-irix5 | SGI Irix 5.3 |
mips-sgi-irix6 | SGI Irix 6.2 |
powerpc-ibm-aix4.1 | IBM PowerPC, AIX 4.1.4 |
powerpc-ibm-aix3.2.5 | IBM PowerPC, AIX 3.2.5 |
powerpc-ibm-aix4.1 | IBM PowerPC, AIX 4.1.3 |
sparc-sun-solaris2 | SPARCstation, Solaris 2.4 |
sparc-sun-solaris2.5 | SPARCstation, Solaris 2.5 |
sparc-sun-sunos4.1 | SPARCstation, SunOS 4.1.4 |
If you have a cross-development tape, the label also indicates the target for that configuration. The pattern for target names uses the following form.
Architecture [- Vendor] - Object format
Target names differ slightly from host names in that the last variable indicates the object format rather than the operating system, and the second variable is often left out (this practice is becoming obsolete; in the future, all configuration names will be made up of three parts).
In cross-development configurations, each tool in the GNUPro Toolkit package is installed with the configured name of the target as a prefix. For example, if the C compiler is configured to generate COFF format code for the Motorola 680x0 family, the compiler is installed as ‘m68k-coff-gcc’.
Warning:
configure
can generate a very large number of target name combinations of architecture,
vendor, and object format. There is by no means support for all possible
combinations!
The following lists some of the more common targets supported by Cygnus Solutions. (Not all targets are supported on every host!) The list is not exhaustive; see see Native Configurations Supported, Embedded Configurations Supported and Specific Processor Support by Family in Release Notes for GNUPro Toolkit for an up-to-date matrix with current host/target combinations supported by Cygnus Solutions. Also, see GNUPro Tools for Embedded Systems.
See also config.guess for discussion of a shell script that attempts to deduce the host from which you install.
|
|||||||
|
|||||
|
|||||||||
|
|||||
|
|||||||
|
|
config.guess is a shell script which attempts to deduce the host type from which it is called, using system commands like uname if they are available. config.guess is remarkably adept at deciphering the proper configuration for your host; if you are building a tree to run on the same host on which you’re building it, we recommend not specifying the host name.
config.guess is called by configure; you need never run it by hand, unless you’re curious about the output.