Lines Matching full:build
84 _Before_ starting the build/install procedure please check the *Note
117 the build procedure. Modifying GCC sources requires additional tools
127 To build all languages in a cross-compiler or other configuration
133 In order to build the Ada compiler (GNAT) you must already have
165 You must have GNU make installed to build GCC.
173 Necessary to build GCC. If you do not have it installed in your
179 Necessary to build GCC. It can be downloaded from
191 Necessary to build libgcj, the GCJ runtime.
241 Necessary when modifying `*.y' files. Necessary to build the
251 Necessary to build GCC during development because the generated
263 Necessary to build GCC documentation during development because the
333 If you also intend to build binutils (either to upgrade an existing
337 of the binutils you intend to build alongside the compiler (`bfd',
352 use OBJDIR to refer to the toplevel build/object directory.
356 its `gcc' subdirectory, otherwise the build will fail.
360 pathnames. Using these can lead to various sorts of build problems.
363 configuration and build phases.
367 tree. This is how we generally build GCC; building where SRCDIR ==
399 include a build number or build date. This version string will be
614 Build shared versions of libraries, if shared libraries are
619 If a list of packages is given as an argument, build shared
627 Use `--disable-shared' to build only static libraries. Note that
640 `--with-build-time-tools=PATHNAME'.
738 default is to build a predefined set of them.
910 The build rules that regenerate the GCC master message catalog
918 For a native build, the default configuration is to perform a
924 In special cases, you may want to perform a 3-stage build even if
935 generated files are placed in your build directory, which allows
980 C front end. When this option is used, one can then build the
989 compatibility with previous Ada build procedures, when it was
1006 Some GCC targets, e.g. powerpc64-linux, build bi-arch compilers.
1110 doing a canadian cross build. The `--disable-nls' option disables
1115 build procedure to prefer its copy of GNU `gettext'.
1119 inferior `catgets' interface, the GCC build procedure normally
1121 library. The `--with-catgets' option causes the build procedure
1130 configure GCC for a system (build, host, or target) which has been
1178 build GCC, you can explicitly specify the directory where they are
1212 `--with-build-sysroot'
1213 `--with-build-sysroot=DIR'
1218 `--with-build-sysroot' when you are configuring with `--prefix'
1222 This option affects the system root for the compiler used to build
1223 target libraries (which runs on the build system); it does not
1224 affect the compiler which is used to build GCC itself.
1241 so GCC can build the exception handling for libgcc.
1255 `--with-build-time-tools=DIR'
1264 different path, and build a toolchain that expects to find the
1275 The following option applies to the build of the Java front end.
1281 just happens not to build on your particular machine. In general,
1296 By default the `libjava' build will not attempt to compile the
1300 use by the build. You must use this option if you intend to
1314 files. If this option is given, the `libjava' build will create
1319 topmost source tree at configure time, then the `libgcj' build
1375 build time, but is more resource-intensive. If this option is
1420 Specifies the AWT peer library or libraries to build alongside
1427 Build the cairo Graphics2D implementation on GTK.
1454 Now that GCC is configured, you are ready to build the compiler and
1471 If you encounter seemingly strange errors when trying to build the
1476 If you build GCC on a BSD system using a directory stored in an old
1489 to build them. Note that most front ends now use hand-written parsers,
1494 There is still one Flex-based lexical analyzer (part of the build
1495 machinery, not of GCC itself) that is used even if you only build the C
1506 For a native build, the default configuration is to perform a 3-stage
1507 bootstrap of the compiler when `make' is invoked. This will build the
1515 * Build tools necessary to build the compiler.
1525 * Build runtime libraries using the stage3 compiler from the
1536 final installation as well, you can build the compiler binaries without
1562 built. This will of course only build those runtime libraries, for
1576 are building on: for example, you could build a
1588 To build a cross compiler, we first recommend building and
1590 to build the cross compiler. The installed native compiler needs to be
1595 desired, the installed native compiler used to build the cross compiler
1603 * Build host tools necessary to build the compiler.
1605 * Build target tools for use by the compiler such as binutils (bfd,
1610 * Build the compiler (single stage only).
1612 * Build runtime libraries using the compiler from the previous step.
1639 The easiest way to provide these files is to build the Binutils
1641 that you use for configuring GCC, then build and install them. They
1657 GNU Make 3.79 and above, which is necessary to build GCC, support
1668 In order to build GNAT, the Ada compiler, you need a working GNAT
1673 In order to build a cross compiler, it is suggested to install the
1674 new compiler as native first, and then use it to build the cross
1679 installed, the build will fail unless `--enable-languages' is used to
1684 runtime libraries. You can check that your build environment is clean
1697 When `make profiledbootstrap' is run, it will first build a `stage1'
1698 compiler. This compiler is used to build a `stageprofile' compiler
1705 The compiler used to build `stage1' needs to support a 64-bit integral
1719 archived results are linked from the build status lists at
1721 a successful build runs the testsuites and submits the results. This
1845 `TARGET/libjava/testsuite' directory in the build tree.
1893 have on your results or your build environment. Please do not edit the
1948 quickly review the build status page for your release, available from
1967 * If the build was for GNU/Linux, also include:
1984 build status list will include a link to the archived copy of your
2178 supported, and it is not possible to build parallel applications. Cray
2298 `--target=crx-elf' is also used to build the `newlib' C library for CRX.
2300 It is also possible to build libstdc++-v3 for the CRX architecture.
2321 on FreeBSD/alpha, using binutils 2.14 or later is required to build
2406 namespace is required for an entire build. This problem can be avoided
2459 binaries for HP-UX. Precompiled binaries must be obtained to build the
2462 haven't been ported to HP-UX and don't build.
2468 It is possible to build GCC 3.3 starting with the bundled HP
2470 used to build later versions. The fastjar program contains ISO C code
2477 distribution can be built. The second approach is to build GCC first
2478 using the HP tools, then build binutils, then rebuild GCC. There have
2497 in `CC' to correctly select the target for the build. It is also
2503 table of cpp needs to be increased for a successful build with the HP
2513 build. This has been been reported to sometimes occur in unified
2519 Although the HP assembler can be used for an initial build, it
2524 not impossible to build many C++ applications. You can't generate
2665 This target is a little tricky to build because we have to
2710 is required to build GCC. For GCC 3.3 and later, this is the default.
2729 and then proceed as described in the build instructions, where we
2741 build, the native AIX compiler *must* be invoked as `cc' (not `xlc').
2867 `m68k-*-rtems' and `m68k-*-uclinux' build libraries for both M680x0 and
3012 before starting the build.
3058 If you build GCC on a system that doesn't have the N64 libraries
3071 `libgcj' is known not to build despite this, running into an internal
3078 build GCC for such targets you need to configure with
3096 tools, meaning that you will not be able to build GCC from source. Tool
3119 PowerPC system in big endian mode running NetBSD. To build the
3198 The build process works more smoothly with the legacy Sun tools so,
3200 `/usr/bin' before `/usr/xpg4/bin' for the duration of the build.
3278 `--disable-multilib', since we will not be able to build the 64-bit
3311 must be specified as the `build' parameter on the configure line. This
3316 % ./configure --build=sparc-sun-solaris2.7 --prefix=xxx
3380 library, the canonical target triplet must be specified as the `build'
3383 % ./configure --build=sparc64-sun-solaris2.7 --prefix=xxx
3459 file to add the module to your kernel build. (Future versions of
3499 GCC will build under Cygwin without modification; it does not build
3502 For MinGW, GCC will build with and support only MinGW runtime 3.12
3582 system tools, install the required tools in the build directory
3589 2. Specify the host, build and target machine configurations. You do
3592 The "build" machine is the system which you are using, the "host"
3594 (normally the build machine), and the "target" machine is the
3600 machine you are on and use that as the build, host and target
3605 In those cases, specify the build machine's "configuration name"
