Lines Matching refs:system

4 @settitle The GNU configure and build system
10 * configure: (configure).	The GNU configure and build system
14 This file documents the GNU configure and build system.
41 @title The GNU configure and build system
65 @top GNU configure and build system
67 The GNU configure and build system.
89 also includes a discussion of the older Cygnus configure system.
126 The GNU configure and build system has two main goals.
129 system permits the developer to concentrate on writing the program,
142 The GNU configure and build system is comprised of several different
152 of the host system at build time.
154 a system for describing how to build a program, permitting the developer
177 developers frequently did not have access to every system, and the
209 The X Window system is built using the imake tool, which uses a database
212 installed, violating one of the goals of the GNU system.
305 configuration name of the host system (@pxref{Configuration Names}).
313 To start using the GNU configure and build system with your software
334 conditions that may change from one system to another, such as the
421 configure system.  This of course requires that developers be aware of,
436 This macro looks for the executable suffix used on the host system.  On
487 directs the libc header files to provide the standard GNU system
630 This requirement is really a bug in the system, and the requirement may
710 and use the @samp{utime} system call to set the modification and access
773 On older Unix systems derived from BSD 4.3, the @samp{utime} system call
879 # Uncomment this if utime (FILE, NULL) works on your system.
926 script to discover the configuration features on the host system, rather
1046 As was seen in the previous chapter, the GNU configure and build system
1050 The system is rather flexible, and can be used in many different ways.
1103 is always required when using the GNU configure system.  @xref{Write
1200 host system.  This file may also be called @file{config.h.in}.
1278 This can speed up running @file{configure} scripts on your system.
1293 The GNU configure and build system requires several support files to be
1319 A shell script which determines the configuration name for the system on
1331 the particular system on which it is used.
1365 @cindex canonical system names
1366 @cindex system names
1367 @cindex system types
1369 The GNU configure system names all systems using a @dfn{configuration
1404 system.  This is often simply @samp{unknown}.  Other common strings are
1405 @samp{pc} for an IBM PC compatible system, or the name of a workstation
1408 The name of the operating system which is run on the system.  This will
1411 @samp{aix4.1.4.0} are seen.  For an embedded system, which has no
1412 operating system, this field normally indicates the type of object file
1417 @samp{linux}, is separated from the operating system, @samp{gnulibc1}.
1421 configuration name for the system on which it is run.  It does by
1423 system.
1439 test for a particular system.  This is because as Unix evolves,
1443 defining a macro which describes the particular system you are on.
1445 Testing for a particular system is normally done using a case statement
1461 It is particularly important to use @samp{*} after the operating system
1477 The GNU configure and build system can be used to build @dfn{cross
1479 one system and produces code which runs on another system.
1494 A compiler which produces programs which run on a different system is a
1499 system as the one on which the compiler runs.  When it is necessary to
1506 is used to debug code which runs on another system.  Everything that is
1512 @cindex host system
1513 @cindex target system
1516 involved: the system on which the tools will run, and the system for
1519 The system on which the tools will run is called the @dfn{host} system.
1521 The system for which the tools generate code is called the @dfn{target}
1522 system.
1525 system and generates ELF programs for a MIPS embedded system.  In this
1526 case the GNU/Linux system is the host, and the MIPS ELF system is the
1547 In almost all cases the host system is the system on which you run the
1553 host system, and the package is not a cross compilation tool and
1591 name of the system for which you wish to generate code.
1595 system, you would use @samp{--target mips-elf}.
1630 the same system, but for the strings to not be identical.  For example,
1645 appear in the file system, such as a directory name or part of a tool
1652 system, @samp{target} should be used.  This is because a wide variety of
1680 Cygnus configure system, not autoconf.  The top level @file{Makefile.in}
1736 the definition of host, this means that their host system is the same as
1737 the target system of the overall configuration.
1813 be the host system of the overall build.  Recall that the host system of
1897 It is possible to use the GNU configure and build system to build a
1898 program which will run on a system which is different from the system on
1920 a Solaris system.  You would use a GNU/Linux cross Solaris compiler to
1924 system.  You would have to copy it over to a Solaris system before you
1928 system in the first place.  However, perhaps the Solaris system is not
1931 GNU/Linux system is much faster than your Solaris system.
1934 run on a non-Unix system, such as DOS or Windows.  It may be simpler to
1935 configure and build on a Unix system than to support the configuration
1936 machinery on a non-Unix system.
1942 involved: the system on which the tools are being built, and the system
1945 The system on which the tools are being built is called the @dfn{build}
1946 system.
1948 The system on which the tools will run is called the host system.
1951 system, as in the previous section, the build system would be GNU/Linux,
1952 and the host system would be Solaris.
1956 case, the system for which the resulting cross compiler generates code
1957 is called the target system.  (For a more complete discussion of host
1961 building a Windows cross MIPS ELF compiler on a GNU/Linux system.  In
1962 this case the build system would be GNU/Linux, the host system would be
1963 Windows, and the target system would be MIPS ELF.
1977 the build system, and will produce code that runs on the host system.
1980 remember that the build system is where you are doing the build, and the
1981 host system is where the resulting program will run.  Therefore, you
1986 so forth, as well as libraries and include files for the host system.
1998 @cindex configure build system
2000 the build system.  This can normally be the result of running the
2008 the host system.
2012 can now see that since @file{config.guess} returns the type of system on
2013 which it is run, it really identifies the build system.  Since the host
2014 system is normally the same as the build system (i.e., people do not
2016 result of @file{config.guess} as the default for the host system when
2021 @file{config.guess} to determine the build system, and presume a
2029 then the build system defaults to the host system.
2050 system, and your GNU/Linux cross Solaris compiler were named
2077 were built, they were configured to run on the build system and to
2078 produce code for the host system.  That is, they were configured with a
2079 @samp{--target} option that is the same as the system which we are now
2081 tools uses the target system as a prefix (@pxref{Using the Target
2082 Type}).  Since that is the system which we are now calling the host,
2103 compiler will be a program which runs on the host system, and therefore
2104 will not be able to run on the build system.
2112 on the build system, to copy the tools to the host system, and to build
2113 the target libraries on the host system.  The requirement for build
2118 system, which means that it must use a build cross target toolchain.
2121 on a GNU/Linux system.  You must have previously installed both a
2182 You ordinarily do not need to know the type of the build system in a
2185 used to determine the target system.  This macro will set the variables
2188 @samp{host} variables, except that they describe the build system.
2201 build system, not the host system.  If your configure scripts examines
2202 files, those files will be on the build system.  Whatever you determine
2203 based on those files may or may not be the case on the host system.
2208 will be compiled for the host system, which means that it will not run
2209 on the build system.
2244 build a program for the host system, but the program is being built on
2245 the build system.
2247 You must instead use a compiler for the build system, rather than the
2248 host system.  In the Cygnus tree, this make variable
2249 @samp{$(CC_FOR_BUILD)} will hold a compiler for the build system.
2253 build @file{config.h} with information for the host system.  However,
2254 you are compiling the file using a compiler for the build system (a
2263 programs run on the build system and into the final program.  This
2264 approach may be of interest for advanced build system hackers.  Note
2265 that the build system compiler is rather confusingly called
2393 The C++ library configure system, written by Per Bothner, deserves
2427 Multilibs are not really part of the GNU configure and build system, but
2618 It is the build system which was developed at Cygnus, using the Cygnus