Lines Matching full:host
112 features of the host system at build time.
267 to use a `--exec-prefix' option of `/usr/cygnus/RELEASE/H-HOST', where
268 HOST is the configuration name of the host system (*note Configuration
381 This macro looks for the executable suffix used on the host
838 script to discover the configuration features on the host system, rather
1112 characteristics of the host system. This file may also be called
1382 like the following, assuming that `host' is a shell variable holding a
1386 case "${host}" in
1418 * Host and Target:: Host and Target.
1419 * Using the Host Type:: Using the Host Type.
1425 File: configure.info, Node: Cross Compilation Concepts, Next: Host and Target, Up: Cross Compilation Tools
1447 File: configure.info, Node: Host and Target, Next: Using the Host Type, Prev: Cross Compilation Concepts, Up: Cross Compilation Tools
1449 5.2 Host and Target
1456 The system on which the tools will run is called the "host" system.
1463 case the GNU/Linux system is the host, and the MIPS ELF system is the
1476 For a native tool, the target is the same as the host. For example, for
1477 a GNU/Linux native compiler, the host is GNU/Linux, and the target is
1481 File: configure.info, Node: Using the Host Type, Next: Specifying the Target, Prev: Host and Target, Up: Cross Compilation Tools
1483 5.3 Using the Host Type
1486 In almost all cases the host system is the system on which you run the
1491 host system, and the package is not a cross compilation tool and
1496 `host'
1497 The canonical configuration name of the host. This will normally
1500 `--host' option.
1503 In the unusual case that the user used an explicit `--host' option,
1504 this will be the argument to `--host'. In the normal case, this
1505 will be the same as the `host' variable.
1516 File: configure.info, Node: Specifying the Target, Next: Using the Target Type, Prev: Using the Host Type, Up: Cross Compilation Tools
1522 same as the host. This is the more common case; for example, it leads
1546 `AC_CANONICAL_HOST' (*note Using the Host Type::).
1549 Note that the host versions of these variables will also be defined by
1564 Note that if `host' and `target' are the same string, you can assume
1568 It is arguably possible for `host' and `target' to represent the
1576 without specifying a `--host' option, it is assumed that the user wants
1633 * Host and Target Libraries:: Host and Target Libraries.
1639 File: configure.info, Node: Host and Target Libraries, Next: Target Library Configure Scripts, Up: Cross Tools in the Cygnus Tree
1641 5.6.1 Host and Target Libraries
1644 The Cygnus tree distinguishes host libraries from target libraries.
1646 Host libraries are built with the compiler used to build the programs
1647 which run on the host, which is called the host compiler. This includes
1649 host compiler, and are linked into programs like the binutils or gcc
1650 which run on the host.
1654 built using the host compiler. Target libraries are libraries such as
1655 `newlib' and `libstdc++'. These libraries are not linked into the host
1671 not used. Instead, the `--host' option is used with the argument of
1673 option was used for the overall configuration, the `--host' option will
1680 the definition of host, this means that their host system is the same as
1687 reason to assume that the C++ compiler used to build the host tools (if
1693 normally configured and built as siblings of the host tools. In a cross
1699 the host libraries and tools, but does not configure any of the target
1702 * Build the host libraries.
1704 * Build the host programs, including gcc. Note that we call gcc
1705 both a host program (since it runs on the host) and a target
1717 File: configure.info, Node: Target Library Configure Scripts, Next: Make Targets in Cygnus Tree, Prev: Host and Target Libraries, Up: Cross Tools in the Cygnus Tree
1749 built in directories which are siblings to the host tools, and are
1757 configured with the `--with-cross-host' option. The value of this
1758 option will be the host system of the overall build. Recall that the
1759 host system of the library will be the target of the overall build. If
1760 the overall build is a native build, the `--with-cross-host' option
1768 `--with-cross-host' option may be used to distinguish these cases.
1770 This same test of `--with-cross-host' may be used to see whether it
1772 `--with-cross-host' option is not used, then the library is being built
1784 For every subdirectory DIR which holds a host library or program,
1787 There are dependencies among host tools. For example, building gcc
1813 the only directory which is built both using the host compiler and
1817 host tools, and they are also incorporated into the `libstdc++' target
1825 subdirectory, the same objects are normally used as both the host build
1827 only C code, and in a native configuration the results of the host
1835 There are currently no other libraries built for both the host and
1855 * Build Cross Host Tools:: Build Cross Host Tools.
1856 * Build and Host Options:: Build and Host Options.
1889 File: configure.info, Node: Canadian Cross Concepts, Next: Build Cross Host Tools, Prev: Canadian Cross Example, Up: Canadian Cross
1901 The system on which the tools will run is called the host system.
1905 and the host system would be Solaris.
1910 is called the target system. (For a more complete discussion of host
1911 and target systems, *note Host and Target::).
1915 this case the build system would be GNU/Linux, the host system would be
1918 The name Canadian Cross comes from the case when the build, host, and
1923 File: configure.info, Node: Build Cross Host Tools, Next: Build and Host Options, Prev: Canadian Cross Concepts, Up: Canadian Cross
1925 6.3 Build Cross Host Tools
1932 These tools will be build cross host tools. That is, they will run
1933 on the build system, and will produce code that runs on the host system.
1935 It is easy to confuse the meaning of build and host here. Always
1937 host system is where the resulting program will run. Therefore, you
1938 need a build cross host compiler.
1942 so forth, as well as libraries and include files for the host system.
1945 File: configure.info, Node: Build and Host Options, Next: CCross not in Cygnus Tree, Prev: Build Cross Host Tools, Up: Canadian Cross
1947 6.4 Build and Host Options
1950 When you run `configure', you must use both the `--build' and `--host'
1958 The `--host' option is used to specify the configuration name of the
1959 host system.
1962 value for the `--host' option (*note Using the Host Type::). We can
1964 it is run, it really identifies the build system. Since the host
1967 result of `config.guess' as the default for the host system when the
1968 `--host' option is not used.
1970 It might seem that if the `--host' option were used without the
1973 of `config.guess' differed from the `--host' option. However, for
1975 explicit `--host' option, rather than using the default from
1978 Therefore, by convention, if the `--host' option is used, but the
1980 host system.
1983 File: configure.info, Node: CCross not in Cygnus Tree, Next: CCross in Cygnus Tree, Prev: Build and Host Options, Up: Canadian Cross
2027 appropriate environment variables are automatically set to `HOST-TOOL',
2028 where HOST is the value used for the `--host' option, and TOOL is the
2032 Adding a prefix of HOST will give the usual name for the build cross
2033 host tools. To see this, consider that when these cross tools were
2035 code for the host system. That is, they were configured with a
2037 calling the host. Recall that the default name for installed cross
2039 Type::). Since that is the system which we are now calling the host,
2040 HOST is the right prefix to use.
2043 `--host=solaris', then the Cygnus tree will automatically default to
2045 installed this compiler, probably by doing a build with no `--host'
2060 compiler (*note Host and Target Libraries::). However, this will not
2062 built target compiler will be a program which runs on the host system,
2070 For example, it would be possible to build just the host cross target
2071 tools on the build system, to copy the tools to the host system, and to
2072 build the target libraries on the host system. The requirement for
2074 to be able to build both host programs and target libraries in a single
2105 SRCDIR/configure --build=i386-linux-gnu --host=i386-cygwin32 \
2148 which correspond to the similar `target' and `host' variables, except
2152 want to test the host environment, not the build environment.
2155 host environment. That is because the tests will be done by running the
2156 compiler, which is actually a build cross host compiler. If the
2158 in the host environment.
2162 build system, not the host system. If your configure scripts examines
2164 based on those files may or may not be the case on the host system.
2169 will be compiled for the host system, which means that it will not run
2204 build a program for the host system, but the program is being built on
2208 host system. In the Cygnus tree, this make variable `$(CC_FOR_BUILD)'
2213 `config.h' with information for the host system. However, you are
2265 with `# per-host:'. This is the common part.
2268 with `# per-target:'. This is the per host part.
2285 Cygnus configure will next set the `build' and `host' shell
2286 variables, and execute the per host part. This may set the shell
2301 `Makefile' by adding definitions for `make' variables such as `host'
2312 particular host or target. They serve to select particular files to
2316 and normally requires support to be added manually for each new host.
2430 it is run for the target libraries (*note Host and Target Libraries::).
2600 * --build option: Build and Host Options.
2602 * --host option: Build and Host Options.
2607 * AC_CANONICAL_HOST: Using the Host Type. (line 10)
2631 * build option: Build and Host Options.
2639 * canadian cross, configuring: Build and Host Options.
2657 * configure build system: Build and Host Options.
2659 * configure host: Build and Host Options.
2666 * configuring a canadian cross: Build and Host Options.
2677 * host names: Configuration Names. (line 6)
2678 * host option: Build and Host Options.
2680 * host system: Host and Target. (line 6)
2681 * host triplets: Configuration Names. (line 6)
2706 * target system: Host and Target. (line 6)
2743 Node: Host and Target54923
2744 Node: Using the Host Type56424
2748 Node: Host and Target Libraries63050
2755 Node: Build Cross Host Tools76098
2756 Node: Build and Host Options77050
