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
170 You must have GNU make installed to build GCC.
178 Necessary to build GCC. If you do not have it installed in your
186 Necessary to build GCC. It can be downloaded from
200 Necessary to build GCC with the Graphite loop optimizations. It
207 Necessary to build GCC with the Graphite loop optimizations. It
217 Necessary to build libgcj, the GCJ runtime.
269 Necessary to build GCC during development because the generated
281 Necessary to build GCC documentation during development because the
323 If you wish to build the `gjdoc' binary in libjava, you will need
360 If you also intend to build binutils (either to upgrade an existing
364 of the binutils you intend to build alongside the compiler (`bfd',
385 use OBJDIR to refer to the toplevel build/object directory.
389 its `gcc' subdirectory, otherwise the build will fail.
393 pathnames. Using these can lead to various sorts of build problems.
396 configuration and build phases.
400 tree. This is how we generally build GCC; building where SRCDIR ==
432 include a build number or build date. This version string will be
669 Build shared versions of libraries, if shared libraries are
674 If a list of packages is given as an argument, build shared
682 Use `--disable-shared' to build only static libraries. Note that
695 `--with-build-time-tools=PATHNAME'.
779 default is to build a predefined set of them.
965 The build rules that regenerate the GCC master message catalog
973 For a native build, the default configuration is to perform a
979 In special cases, you may want to perform a 3-stage build even if
990 generated files are placed in your build directory, which allows
1035 C front end. When this option is used, one can then build the
1044 compatibility with previous Ada build procedures, when it was
1061 Some GCC targets, e.g. powerpc64-linux, build bi-arch compilers.
1146 To build the stage1 compiler with different checking options use
1180 doing a canadian cross build. The `--disable-nls' option disables
1185 build procedure to prefer its copy of GNU `gettext'.
1189 inferior `catgets' interface, the GCC build procedure normally
1191 library. The `--with-catgets' option causes the build procedure
1200 configure GCC for a system (build, host, or target) which has been
1248 build GCC, you can explicitly specify the directory where they are
1266 libraries installed in a standard location and you want to build
1314 `--with-build-sysroot'
1315 `--with-build-sysroot=DIR'
1320 `--with-build-sysroot' when you are configuring with `--prefix'
1324 This option affects the system root for the compiler used to build
1325 target libraries (which runs on the build system); it does not
1326 affect the compiler which is used to build GCC itself.
1347 so GCC can build the exception handling for libgcc.
1361 `--with-build-time-tools=DIR'
1370 different path, and build a toolchain that expects to find the
1381 The following option applies to the build of the Java front end.
1387 just happens not to build on your particular machine. In general,
1402 By default the `libjava' build will not attempt to compile the
1406 use by the build. You must use this option if you intend to
1420 files. If this option is given, the `libjava' build will create
1425 topmost source tree at configure time, then the `libgcj' build
1469 Build most of libgcj with `-freduced-reflection'. This reduces
1489 build time, but is more resource-intensive. If this option is
1577 Specifies the AWT peer library or libraries to build alongside
1584 Build the cairo Graphics2D implementation on GTK.
1611 Now that GCC is configured, you are ready to build the compiler and
1628 If you encounter seemingly strange errors when trying to build the
1633 If you build GCC on a BSD system using a directory stored in an old
1645 files and you do not need Flex installed to build them. There is still
1646 one Flex-based lexical analyzer (part of the build machinery, not of
1647 GCC itself) that is used even if you only build the C front end.
1657 For a native build, the default configuration is to perform a 3-stage
1658 bootstrap of the compiler when `make' is invoked. This will build the
1666 * Build tools necessary to build the compiler.
1676 * Build runtime libraries using the stage3 compiler from the
1689 bootstrap and in the final installation as well, you can build the
1716 built. This will of course only build those runtime libraries, for
1730 are building on: for example, you could build a
1736 the build. It can be set to a whitespace-separated list of names. For
1761 To build a cross compiler, we first recommend building and
1763 to build the cross compiler. The installed native compiler needs to be
1768 desired, the installed native compiler used to build the cross compiler
1776 * Build host tools necessary to build the compiler.
1778 * Build target tools for use by the compiler such as binutils (bfd,
1783 * Build the compiler (single stage only).
1785 * Build runtime libraries using the compiler from the previous step.
1812 The easiest way to provide these files is to build the Binutils
1814 that you use for configuring GCC, then build and install them. They
1830 GNU Make 3.79 and above, which is necessary to build GCC, support
1841 In order to build GNAT, the Ada compiler, you need a working GNAT
1846 In order to build a cross compiler, it is suggested to install the
1847 new compiler as native first, and then use it to build the cross
1852 installed, the build will fail unless `--enable-languages' is used to
1857 runtime libraries. You can check that your build environment is clean
1870 When `make profiledbootstrap' is run, it will first build a `stage1'
1871 compiler. This compiler is used to build a `stageprofile' compiler
1878 The compiler used to build `stage1' needs to support a 64-bit integral
1892 archived results are linked from the build status lists at
1894 a successful build runs the testsuites and submits the results. This
2018 `TARGET/libjava/testsuite' directory in the build tree.
2066 have on your results or your build environment. Please do not edit the
2121 quickly review the build status page for your release, available from
2140 * If the build was for GNU/Linux, also include:
2157 build status list will include a link to the archived copy of your
2435 `--target=crx-elf' is also used to build the `newlib' C library for CRX.
2437 It is also possible to build libstdc++-v3 for the CRX architecture.
2458 on FreeBSD/alpha, using binutils 2.14 or later is required to build
2534 difficult if not impossible to build many C++ applications.
2552 namespace is required for an entire build. This problem can be avoided
2585 and don't build.
2588 binaries for HP-UX. Precompiled binaries must be obtained to build the
2596 It is possible to build GCC 3.3 starting with the bundled HP
2598 used to build later versions. The fastjar program contains ISO C code
2605 distribution can be built. The second approach is to build GCC first
2606 using the HP tools, then build binutils, then rebuild GCC. There have
2624 in `CC' to correctly select the target for the build. It is also
2630 table of cpp needs to be increased for a successful build with the HP
2640 build. This has been reported to sometimes occur in unified builds of
2740 is required to build GCC. For GCC 3.3 and later, this is the default.
2759 and then proceed as described in the build instructions, where we
2771 build, the native AIX compiler *must* be invoked as `cc' (not `xlc').
2897 `m68k-*-rtems', `m68k-*-uclinux' and `m68k-*-linux' build libraries
2998 before starting the build.
3044 If you build GCC on a system that doesn't have the N64 libraries
3057 `libgcj' is known not to build despite this, running into an internal
3064 build GCC for such targets you need to configure with
3084 tools, meaning that you will not be able to build GCC from source. Tool
3184 The build process works more smoothly with the legacy Sun tools so,
3186 `/usr/bin' before `/usr/xpg4/bin' for the duration of the build.
3252 `--disable-multilib', since we will not be able to build the 64-bit
3285 must be specified as the `build' parameter on the configure line. This
3290 % ./configure --build=sparc-sun-solaris2.7 --prefix=xxx
3354 library, the canonical target triplet must be specified as the `build'
3357 % ./configure --build=sparc64-sun-solaris2.7 --prefix=xxx
3400 file to add the module to your kernel build. (Future versions of
3504 GCC will build under Cygwin without modification; it does not build
3522 GCC will build with and support only MinGW runtime 3.12 and later.
3601 system tools, install the required tools in the build directory
3608 2. Specify the host, build and target machine configurations. You do
3611 The "build" machine is the system which you are using, the "host"
3613 (normally the build machine), and the "target" machine is the
3619 machine you are on and use that as the build, host and target
3624 In those cases, specify the build machine's "configuration name"
