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 the Fortran frontend. If you do not have it
179 Necessary to build the Fortran frontend. It can be downloaded from
192 Necessary to build libgcj, the GCJ runtime.
249 Necessary to build GCC during development because the generated
256 Necessary to build GCC during development because the generated
268 Necessary to build GCC documentation during development because the
328 If you also intend to build binutils (either to upgrade an existing
332 of the binutils you intend to build alongside the compiler (`bfd',
347 use OBJDIR to refer to the toplevel build/object directory.
351 its `gcc' subdirectory, otherwise the build will fail.
355 pathnames. Using these can lead to various sorts of build problems.
358 configuration and build phases.
362 tree. This is how we generally build GCC; building where SRCDIR ==
585 Build shared versions of libraries, if shared libraries are
590 If a list of packages is given as an argument, build shared
598 Use `--disable-shared' to build only static libraries. Note that
611 `--with-build-time-tools=PATHNAME'.
709 default is to build a predefined set of them.
872 The build rules that regenerate the GCC master message catalog
880 For a native build, the default configuration is to perform a
886 In special cases, you may want to perform a 3-stage build even if
897 generated files are placed in your build directory, which allows
942 compatibility with previous Ada build procedures, when it was
959 Some GCC targets, e.g. powerpc64-linux, build bi-arch compilers.
1058 doing a canadian cross build. The `--disable-nls' option disables
1063 build procedure to prefer its copy of GNU `gettext'.
1067 inferior `catgets' interface, the GCC build procedure normally
1069 library. The `--with-catgets' option causes the build procedure
1078 configure GCC for a system (build, host, or target) which has been
1120 `--with-build-sysroot'
1121 `--with-build-sysroot=DIR'
1126 `--with-build-sysroot' when you are configuring with `--prefix'
1130 This option affects the system root for the compiler used to build
1131 target libraries (which runs on the build system); it does not
1132 affect the compiler which is used to build GCC itself.
1149 so GCC can build the exception handling for libgcc.
1163 `--with-build-time-tools=DIR'
1172 different path, and build a toolchain that expects to find the
1183 The following options apply to the build of the Fortran front end.
1193 build the Fortran front-end, you can explicitly specify the
1208 The following option applies to the build of the Java front end.
1214 just happens not to build on your particular machine. In general,
1263 build time, but is more resource-intensive. If this option is
1308 Specifies the AWT peer library or libraries to build alongside
1315 Build the cairo Graphics2D implementation on GTK.
1342 Now that GCC is configured, you are ready to build the compiler and
1359 If you encounter seemingly strange errors when trying to build the
1364 If you build GCC on a BSD system using a directory stored in an old
1376 not need Bison installed to build them.
1386 For a native build, the default configuration is to perform a 3-stage
1387 bootstrap of the compiler when `make' is invoked. This will build the
1395 * Build tools necessary to build the compiler.
1405 * Build runtime libraries using the stage3 compiler from the
1416 final installation as well, you can build the compiler binaries without
1442 built. This will of course only build those runtime libraries, for
1456 are building on: for example, you could build a
1468 To build a cross compiler, we first recommend building and
1470 to build the cross compiler. The installed native compiler needs to be
1477 * Build host tools necessary to build the compiler.
1479 * Build target tools for use by the compiler such as binutils (bfd,
1484 * Build the compiler (single stage only).
1486 * Build runtime libraries using the compiler from the previous step.
1513 The easiest way to provide these files is to build the Binutils
1515 that you use for configuring GCC, then build and install them. They
1531 GNU Make 3.79 and above, which is necessary to build GCC, support
1542 In order to build GNAT, the Ada compiler, you need a working GNAT
1547 In order to build a cross compiler, it is suggested to install the
1548 new compiler as native first, and then use it to build the cross
1553 installed, the build will fail unless `--enable-languages' is used to
1565 When `make profiledbootstrap' is run, it will first build a `stage1'
1566 compiler. This compiler is used to build a `stageprofile' compiler
1573 The compiler used to build `stage1' needs to support a 64-bit integral
1587 archived results are linked from the build status lists at
1589 a successful build runs the testsuites and submits the results. This
1709 `TARGET/libjava/testsuite' directory in the build tree.
1761 have on your results or your build environment. Please do not edit the
1813 quickly review the build status page for your release, available from
1832 * If the build was for GNU/Linux, also include:
1849 build status list will include a link to the archived copy of your
2043 supported, and it is not possible to build parallel applications. Cray
2180 `--target=crx-elf' is also used to build the `newlib' C library for CRX.
2182 It is also possible to build libstdc++-v3 for the CRX architecture.
2203 on FreeBSD/alpha, using binutils 2.14 or later is required to build
2288 namespace is required for an entire build. This problem can be avoided
2341 binaries for HP-UX. Precompiled binaries must be obtained to build the
2344 haven't been ported to HP-UX and don't build.
2350 It is possible to build GCC 3.3 starting with the bundled HP
2352 used to build later versions. The fastjar program contains ISO C code
2359 distribution can be built. The second approach is to build GCC first
2360 using the HP tools, then build binutils, then rebuild GCC. There have
2379 in `CC' to correctly select the target for the build. It is also
2385 table of cpp needs to be increased for a successful build with the HP
2395 build. This has been been reported to sometimes occur in unified
2401 Although the HP assembler can be used for an initial build, it
2406 not impossible to build many C++ applications. You can't generate
2547 This target is a little tricky to build because we have to
2592 is required to build GCC. For GCC 3.3 and later, this is the default.
2611 and then proceed as described in the build instructions, where we
2623 build, the native AIX compiler *must* be invoked as `cc' (not `xlc').
2855 before starting the build.
2901 If you build GCC on a system that doesn't have the N64 libraries
2915 this problem, at least the N64 `libgcj' is known not to build despite
2922 build GCC for such targets you need to configure with
2940 tools, meaning that you will not be able to build GCC from source. Tool
2964 PowerPC system in big endian mode running NetBSD. To build the
3043 The build process works more smoothly with the legacy Sun tools so,
3045 `/usr/bin' before `/usr/xpg4/bin' for the duration of the build.
3123 `--disable-multilib', since we will not be able to build the 64-bit
3156 must be specified as the `build' parameter on the configure line. This
3161 % ./configure --build=sparc-sun-solaris2.7 --prefix=xxx
3225 library, the canonical target triplet must be specified as the `build'
3228 % ./configure --build=sparc64-sun-solaris2.7 --prefix=xxx
3304 file to add the module to your kernel build. (Future versions of
3344 GCC will build under Cygwin without modification; it does not build
3422 system tools, install the required tools in the build directory
3429 2. Specify the host, build and target machine configurations. You do
3432 The "build" machine is the system which you are using, the "host"
3434 (normally the build machine), and the "target" machine is the
3440 machine you are on and use that as the build, host and target
3445 In those cases, specify the build machine's "configuration name"
