1 This is doc/gccinstall.info, produced by makeinfo version 4.13 from
2 /d/gcc-4.7.2/gcc-4.7.2/gcc/doc/install.texi.
4 Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
5 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010
6 Free Software Foundation, Inc.
8 Permission is granted to copy, distribute and/or modify this document
9 under the terms of the GNU Free Documentation License, Version 1.3 or
10 any later version published by the Free Software Foundation; with no
11 Invariant Sections, the Front-Cover texts being (a) (see below), and
12 with the Back-Cover Texts being (b) (see below). A copy of the license
13 is included in the section entitled "GNU Free Documentation License".
15 (a) The FSF's Front-Cover Text is:
19 (b) The FSF's Back-Cover Text is:
21 You have freedom to copy and modify this GNU Manual, like GNU
22 software. Copies published by the Free Software Foundation raise
23 funds for GNU development.
25 Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
26 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010
27 Free Software Foundation, Inc.
29 Permission is granted to copy, distribute and/or modify this document
30 under the terms of the GNU Free Documentation License, Version 1.3 or
31 any later version published by the Free Software Foundation; with no
32 Invariant Sections, the Front-Cover texts being (a) (see below), and
33 with the Back-Cover Texts being (b) (see below). A copy of the license
34 is included in the section entitled "GNU Free Documentation License".
36 (a) The FSF's Front-Cover Text is:
40 (b) The FSF's Back-Cover Text is:
42 You have freedom to copy and modify this GNU Manual, like GNU
43 software. Copies published by the Free Software Foundation raise
44 funds for GNU development.
46 INFO-DIR-SECTION Software development
48 * gccinstall: (gccinstall). Installing the GNU Compiler Collection.
52 File: gccinstall.info, Node: Top, Up: (dir)
56 * Installing GCC:: This document describes the generic installation
57 procedure for GCC as well as detailing some target
58 specific installation instructions.
60 * Specific:: Host/target specific installation notes for GCC.
61 * Binaries:: Where to get pre-compiled binaries.
63 * Old:: Old installation documentation.
65 * GNU Free Documentation License:: How you can copy and share this manual.
66 * Concept Index:: This index has two entries.
69 File: gccinstall.info, Node: Installing GCC, Next: Binaries, Up: Top
74 The latest version of this document is always available at
75 http://gcc.gnu.org/install/.
77 This document describes the generic installation procedure for GCC
78 as well as detailing some target specific installation instructions.
80 GCC includes several components that previously were separate
81 distributions with their own installation instructions. This document
82 supersedes all package specific installation instructions.
84 _Before_ starting the build/install procedure please check the *note
85 host/target specific installation notes: Specific. We recommend you
86 browse the entire generic installation instructions before you proceed.
88 Lists of successful builds for released versions of GCC are
89 available at `http://gcc.gnu.org/buildstat.html'. These lists are
90 updated as new information becomes available.
92 The installation procedure itself is broken into five steps.
97 * Downloading the source::
100 * Testing:: (optional)
103 Please note that GCC does not support `make uninstall' and probably
104 won't do so in the near future as this would open a can of worms.
105 Instead, we suggest that you install GCC into a directory of its own
106 and simply remove that directory when you do not need that specific
107 version of GCC any longer, and, if shared libraries are installed there
108 as well, no more binaries exist that use them.
111 File: gccinstall.info, Node: Prerequisites, Next: Downloading the source, Up: Installing GCC
116 GCC requires that various tools and packages be available for use in
117 the build procedure. Modifying GCC sources requires additional tools
120 Tools/packages necessary for building GCC
121 =========================================
124 Necessary to bootstrap GCC, although versions of GCC prior to 3.4
125 also allow bootstrapping with a traditional (K&R) C compiler.
127 To build all languages in a cross-compiler or other configuration
128 where 3-stage bootstrap is not performed, you need to start with
129 an existing GCC binary (version 2.95 or later) because source code
130 for language frontends other than C might use GCC extensions.
133 In order to build the Ada compiler (GNAT) you must already have
134 GNAT installed because portions of the Ada frontend are written in
135 Ada (with GNAT extensions.) Refer to the Ada installation
136 instructions for more specific information.
138 A "working" POSIX compatible shell, or GNU bash
139 Necessary when running `configure' because some `/bin/sh' shells
140 have bugs and may crash when configuring the target libraries. In
141 other cases, `/bin/sh' or `ksh' have disastrous corner-case
142 performance problems. This can cause target `configure' runs to
143 literally take days to complete in some cases.
145 So on some platforms `/bin/ksh' is sufficient, on others it isn't.
146 See the host/target specific instructions for your platform, or
147 use `bash' to be sure. Then set `CONFIG_SHELL' in your
148 environment to your "good" shell prior to running
151 `zsh' is not a fully compliant POSIX shell and will not work when
155 Necessary for creating some of the generated source files for GCC.
156 If in doubt, use a recent GNU awk version, as some of the older
157 ones are broken. GNU awk version 3.1.5 is known to work.
160 Necessary in some circumstances, optional in others. See the
161 host/target specific instructions for your platform for the exact
164 gzip version 1.2.4 (or later) or
165 bzip2 version 1.0.2 (or later)
166 Necessary to uncompress GCC `tar' files when source code is
167 obtained via FTP mirror sites.
169 GNU make version 3.80 (or later)
170 You must have GNU make installed to build GCC.
172 GNU tar version 1.14 (or later)
173 Necessary (only on some platforms) to untar the source code. Many
174 systems' `tar' programs will also work, only try GNU `tar' if you
177 Perl version 5.6.1 (or later)
178 Necessary when targetting Darwin, building `libstdc++', and not
179 using `--disable-symvers'. Necessary when targetting Solaris 2
180 with Sun `ld' and not using `--disable-symvers'. The bundled
181 `perl' in Solaris 8 and up works.
183 Necessary when regenerating `Makefile' dependencies in libiberty.
184 Necessary when regenerating `libiberty/functions.texi'. Necessary
185 when generating manpages from Texinfo manuals. Used by various
186 scripts to generate some files included in SVN (mainly
187 Unicode-related and rarely changing) from source tables.
189 `jar', or InfoZIP (`zip' and `unzip')
190 Necessary to build libgcj, the GCJ runtime.
193 Several support libraries are necessary to build GCC, some are
194 required, others optional. While any sufficiently new version of
195 required tools usually work, library requirements are generally
196 stricter. Newer versions may work in some cases, but it's safer to use
197 the exact versions documented. We appreciate bug reports about
198 problems with newer versions, though. If your OS vendor provides
199 packages for the support libraries then using those packages may be the
200 simplest way to install the libraries.
202 GNU Multiple Precision Library (GMP) version 4.3.2 (or later)
203 Necessary to build GCC. If a GMP source distribution is found in a
204 subdirectory of your GCC sources named `gmp', it will be built
205 together with GCC. Alternatively, if GMP is already installed but
206 it is not in your library search path, you will have to configure
207 with the `--with-gmp' configure option. See also `--with-gmp-lib'
208 and `--with-gmp-include'.
210 MPFR Library version 2.4.2 (or later)
211 Necessary to build GCC. It can be downloaded from
212 `http://www.mpfr.org/'. If an MPFR source distribution is found
213 in a subdirectory of your GCC sources named `mpfr', it will be
214 built together with GCC. Alternatively, if MPFR is already
215 installed but it is not in your default library search path, the
216 `--with-mpfr' configure option should be used. See also
217 `--with-mpfr-lib' and `--with-mpfr-include'.
219 MPC Library version 0.8.1 (or later)
220 Necessary to build GCC. It can be downloaded from
221 `http://www.multiprecision.org/'. If an MPC source distribution
222 is found in a subdirectory of your GCC sources named `mpc', it
223 will be built together with GCC. Alternatively, if MPC is already
224 installed but it is not in your default library search path, the
225 `--with-mpc' configure option should be used. See also
226 `--with-mpc-lib' and `--with-mpc-include'.
228 Parma Polyhedra Library (PPL) version 0.11
229 Necessary to build GCC with the Graphite loop optimizations. It
230 can be downloaded from `http://www.cs.unipr.it/ppl/Download/'.
232 The `--with-ppl' configure option should be used if PPL is not
233 installed in your default library search path.
235 CLooG-PPL version 0.15 or CLooG 0.16
236 Necessary to build GCC with the Graphite loop optimizations. There
237 are two versions available. CLooG-PPL 0.15 as well as CLooG 0.16.
238 The former is the default right now. It can be downloaded from
239 `ftp://gcc.gnu.org/pub/gcc/infrastructure/' as
240 `cloog-ppl-0.15.tar.gz'.
242 CLooG 0.16 support is still in testing stage, but will be the
243 default in future GCC releases. It is also available at
244 `ftp://gcc.gnu.org/pub/gcc/infrastructure/' as
245 `cloog-0.16.1.tar.gz'. To use it add the additional configure
246 option `--enable-cloog-backend=isl'. Even if CLooG 0.16 does not
247 use PPL, PPL is still required for Graphite.
249 In both cases `--with-cloog' configure option should be used if
250 CLooG is not installed in your default library search path.
253 Tools/packages necessary for modifying GCC
254 ==========================================
256 autoconf version 2.64
257 GNU m4 version 1.4.6 (or later)
258 Necessary when modifying `configure.ac', `aclocal.m4', etc. to
259 regenerate `configure' and `config.in' files.
261 automake version 1.11.1
262 Necessary when modifying a `Makefile.am' file to regenerate its
263 associated `Makefile.in'.
265 Much of GCC does not use automake, so directly edit the
266 `Makefile.in' file. Specifically this applies to the `gcc',
267 `intl', `libcpp', `libiberty', `libobjc' directories as well as
268 any of their subdirectories.
270 For directories that use automake, GCC requires the latest release
271 in the 1.11 series, which is currently 1.11.1. When regenerating
272 a directory to a newer version, please update all the directories
273 using an older 1.11 to the latest released version.
275 gettext version 0.14.5 (or later)
276 Needed to regenerate `gcc.pot'.
278 gperf version 2.7.2 (or later)
279 Necessary when modifying `gperf' input files, e.g.
280 `gcc/cp/cfns.gperf' to regenerate its associated header file, e.g.
286 Necessary to run the GCC testsuite; see the section on testing for
289 autogen version 5.5.4 (or later) and
290 guile version 1.4.1 (or later)
291 Necessary to regenerate `fixinc/fixincl.x' from
292 `fixinc/inclhack.def' and `fixinc/*.tpl'.
294 Necessary to run `make check' for `fixinc'.
296 Necessary to regenerate the top level `Makefile.in' file from
297 `Makefile.tpl' and `Makefile.def'.
299 Flex version 2.5.4 (or later)
300 Necessary when modifying `*.l' files.
302 Necessary to build GCC during development because the generated
303 output files are not included in the SVN repository. They are
304 included in releases.
306 Texinfo version 4.7 (or later)
307 Necessary for running `makeinfo' when modifying `*.texi' files to
310 Necessary for running `make dvi' or `make pdf' to create printable
311 documentation in DVI or PDF format. Texinfo version 4.8 or later
312 is required for `make pdf'.
314 Necessary to build GCC documentation during development because the
315 generated output files are not included in the SVN repository.
316 They are included in releases.
318 TeX (any working version)
319 Necessary for running `texi2dvi' and `texi2pdf', which are used
320 when running `make dvi' or `make pdf' to create DVI or PDF files,
325 Necessary to access the SVN repository. Public releases and weekly
326 snapshots of the development sources are also available via FTP.
328 GNU diffutils version 2.7 (or later)
329 Useful when submitting patches for the GCC source code.
331 patch version 2.5.4 (or later)
332 Necessary when applying patches, created with `diff', to one's own
337 If you wish to modify `.java' files in libjava, you will need to
338 configure with `--enable-java-maintainer-mode', and you will need
339 to have executables named `ecj1' and `gjavah' in your path. The
340 `ecj1' executable should run the Eclipse Java compiler via the
341 GCC-specific entry point. You can download a suitable jar from
342 `ftp://sourceware.org/pub/java/', or by running the script
343 `contrib/download_ecj'.
345 antlr.jar version 2.7.1 (or later)
347 If you wish to build the `gjdoc' binary in libjava, you will need
348 to have an `antlr.jar' library available. The library is searched
349 for in system locations but can be specified with
350 `--with-antlr-jar=' instead. When configuring with
351 `--enable-java-maintainer-mode', you will need to have one of the
352 executables named `cantlr', `runantlr' or `antlr' in your path.
356 File: gccinstall.info, Node: Downloading the source, Next: Configuration, Prev: Prerequisites, Up: Installing GCC
361 GCC is distributed via SVN and FTP tarballs compressed with `gzip' or
362 `bzip2'. It is possible to download a full distribution or specific
365 Please refer to the releases web page for information on how to
368 The full distribution includes the C, C++, Objective-C, Fortran,
369 Java, and Ada (in the case of GCC 3.1 and later) compilers. The full
370 distribution also includes runtime libraries for C++, Objective-C,
371 Fortran, and Java. In GCC 3.0 and later versions, the GNU compiler
372 testsuites are also included in the full distribution.
374 If you choose to download specific components, you must download the
375 core GCC distribution plus any language specific distributions you wish
376 to use. The core distribution includes the C language front end as
377 well as the shared components. Each language has a tarball which
378 includes the language front end as well as the language runtime (when
381 Unpack the core distribution as well as any language specific
382 distributions in the same directory.
384 If you also intend to build binutils (either to upgrade an existing
385 installation or for use in place of the corresponding tools of your
386 OS), unpack the binutils distribution either in the same directory or a
387 separate one. In the latter case, add symbolic links to any components
388 of the binutils you intend to build alongside the compiler (`bfd',
389 `binutils', `gas', `gprof', `ld', `opcodes', ...) to the directory
390 containing the GCC sources.
392 Likewise the GMP, MPFR and MPC libraries can be automatically built
393 together with GCC. Unpack the GMP, MPFR and/or MPC source
394 distributions in the directory containing the GCC sources and rename
395 their directories to `gmp', `mpfr' and `mpc', respectively (or use
396 symbolic links with the same name).
399 File: gccinstall.info, Node: Configuration, Next: Building, Prev: Downloading the source, Up: Installing GCC
401 4 Installing GCC: Configuration
402 *******************************
404 Like most GNU software, GCC must be configured before it can be
405 built. This document describes the recommended configuration procedure
406 for both native and cross targets.
408 We use SRCDIR to refer to the toplevel source directory for GCC; we
409 use OBJDIR to refer to the toplevel build/object directory.
411 If you obtained the sources via SVN, SRCDIR must refer to the top
412 `gcc' directory, the one where the `MAINTAINERS' file can be found, and
413 not its `gcc' subdirectory, otherwise the build will fail.
415 If either SRCDIR or OBJDIR is located on an automounted NFS file
416 system, the shell's built-in `pwd' command will return temporary
417 pathnames. Using these can lead to various sorts of build problems.
418 To avoid this issue, set the `PWDCMD' environment variable to an
419 automounter-aware `pwd' command, e.g., `pawd' or `amq -w', during the
420 configuration and build phases.
422 First, we *highly* recommend that GCC be built into a separate
423 directory from the sources which does *not* reside within the source
424 tree. This is how we generally build GCC; building where SRCDIR ==
425 OBJDIR should still work, but doesn't get extensive testing; building
426 where OBJDIR is a subdirectory of SRCDIR is unsupported.
428 If you have previously built GCC in the same directory for a
429 different target machine, do `make distclean' to delete all files that
430 might be invalid. One of the files this deletes is `Makefile'; if
431 `make distclean' complains that `Makefile' does not exist or issues a
432 message like "don't know how to make distclean" it probably means that
433 the directory is already suitably clean. However, with the recommended
434 method of building in a separate OBJDIR, you should simply use a
435 different OBJDIR for each target.
437 Second, when configuring a native system, either `cc' or `gcc' must
438 be in your path or you must set `CC' in your environment before running
439 configure. Otherwise the configuration scripts may fail.
445 % SRCDIR/configure [OPTIONS] [TARGET]
450 If you will be distributing binary versions of GCC, with modifications
451 to the source code, you should use the options described in this
452 section to make clear that your version contains modifications.
454 `--with-pkgversion=VERSION'
455 Specify a string that identifies your package. You may wish to
456 include a build number or build date. This version string will be
457 included in the output of `gcc --version'. This suffix does not
458 replace the default version string, only the `GCC' part.
460 The default value is `GCC'.
463 Specify the URL that users should visit if they wish to report a
464 bug. You are of course welcome to forward bugs reported to you to
465 the FSF, if you determine that they are not bugs in your
468 The default value refers to the FSF's GCC bug tracker.
474 * GCC has code to correctly determine the correct value for TARGET
475 for nearly all native systems. Therefore, we highly recommend you
476 do not provide a configure target when configuring a native
479 * TARGET must be specified as `--target=TARGET' when configuring a
480 cross compiler; examples of valid targets would be m68k-elf,
483 * Specifying just TARGET instead of `--target=TARGET' implies that
484 the host defaults to TARGET.
486 Options specification
487 =====================
489 Use OPTIONS to override several configure time options for GCC. A list
490 of supported OPTIONS follows; `configure --help' may list other
491 options, but those not listed below may not work and should not
494 Note that each `--enable' option has a corresponding `--disable'
495 option and that each `--with' option has a corresponding `--without'
499 Specify the toplevel installation directory. This is the
500 recommended way to install the tools into a directory other than
501 the default. The toplevel installation directory defaults to
504 We *highly* recommend against DIRNAME being the same or a
505 subdirectory of OBJDIR or vice versa. If specifying a directory
506 beneath a user's home directory tree, some shells will not expand
507 DIRNAME correctly if it contains the `~' metacharacter; use
510 The following standard `autoconf' options are supported. Normally
511 you should not need to use these options.
512 `--exec-prefix=DIRNAME'
513 Specify the toplevel installation directory for
514 architecture-dependent files. The default is `PREFIX'.
517 Specify the installation directory for the executables called
518 by users (such as `gcc' and `g++'). The default is
522 Specify the installation directory for object code libraries
523 and internal data files of GCC. The default is
526 `--libexecdir=DIRNAME'
527 Specify the installation directory for internal executables
528 of GCC. The default is `EXEC-PREFIX/libexec'.
530 `--with-slibdir=DIRNAME'
531 Specify the installation directory for the shared libgcc
532 library. The default is `LIBDIR'.
534 `--datarootdir=DIRNAME'
535 Specify the root of the directory tree for read-only
536 architecture-independent data files referenced by GCC. The
537 default is `PREFIX/share'.
540 Specify the installation directory for documentation in info
541 format. The default is `DATAROOTDIR/info'.
544 Specify the installation directory for some
545 architecture-independent data files referenced by GCC. The
546 default is `DATAROOTDIR'.
549 Specify the installation directory for documentation files
550 (other than Info) for GCC. The default is `DATAROOTDIR/doc'.
553 Specify the installation directory for HTML documentation
554 files. The default is `DOCDIR'.
557 Specify the installation directory for PDF documentation
558 files. The default is `DOCDIR'.
561 Specify the installation directory for manual pages. The
562 default is `DATAROOTDIR/man'. (Note that the manual pages
563 are only extracts from the full GCC manuals, which are
564 provided in Texinfo format. The manpages are derived by an
565 automatic conversion process from parts of the full manual.)
567 `--with-gxx-include-dir=DIRNAME'
568 Specify the installation directory for G++ header files. The
569 default depends on other configuration options, and differs
570 between cross and native configurations.
573 Specify additional command line driver SPECS. This can be
574 useful if you need to turn on a non-standard feature by
575 default without modifying the compiler's source code, for
577 `--with-specs=%{!fcommon:%{!fno-common:-fno-common}}'. *Note
578 Specifying subprocesses and the switches to pass to them:
582 `--program-prefix=PREFIX'
583 GCC supports some transformations of the names of its programs when
584 installing them. This option prepends PREFIX to the names of
585 programs to install in BINDIR (see above). For example, specifying
586 `--program-prefix=foo-' would result in `gcc' being installed as
587 `/usr/local/bin/foo-gcc'.
589 `--program-suffix=SUFFIX'
590 Appends SUFFIX to the names of programs to install in BINDIR (see
591 above). For example, specifying `--program-suffix=-3.1' would
592 result in `gcc' being installed as `/usr/local/bin/gcc-3.1'.
594 `--program-transform-name=PATTERN'
595 Applies the `sed' script PATTERN to be applied to the names of
596 programs to install in BINDIR (see above). PATTERN has to consist
597 of one or more basic `sed' editing commands, separated by
598 semicolons. For example, if you want the `gcc' program name to be
599 transformed to the installed program `/usr/local/bin/myowngcc' and
600 the `g++' program name to be transformed to
601 `/usr/local/bin/gspecial++' without changing other program names,
602 you could use the pattern
603 `--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/''
604 to achieve this effect.
606 All three options can be combined and used together, resulting in
607 more complex conversion patterns. As a basic rule, PREFIX (and
608 SUFFIX) are prepended (appended) before further transformations
609 can happen with a special transformation script PATTERN.
611 As currently implemented, this option only takes effect for native
612 builds; cross compiler binaries' names are not transformed even
613 when a transformation is explicitly asked for by one of these
616 For native builds, some of the installed programs are also
617 installed with the target alias in front of their name, as in
618 `i686-pc-linux-gnu-gcc'. All of the above transformations happen
619 before the target alias is prepended to the name--so, specifying
620 `--program-prefix=foo-' and `program-suffix=-3.1', the resulting
621 binary would be installed as
622 `/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1'.
624 As a last shortcoming, none of the installed Ada programs are
625 transformed yet, which will be fixed in some time.
627 `--with-local-prefix=DIRNAME'
628 Specify the installation directory for local include files. The
629 default is `/usr/local'. Specify this option if you want the
630 compiler to search directory `DIRNAME/include' for locally
631 installed header files _instead_ of `/usr/local/include'.
633 You should specify `--with-local-prefix' *only* if your site has a
634 different convention (not `/usr/local') for where to put
637 The default value for `--with-local-prefix' is `/usr/local'
638 regardless of the value of `--prefix'. Specifying `--prefix' has
639 no effect on which directory GCC searches for local header files.
640 This may seem counterintuitive, but actually it is logical.
642 The purpose of `--prefix' is to specify where to _install GCC_.
643 The local header files in `/usr/local/include'--if you put any in
644 that directory--are not part of GCC. They are part of other
645 programs--perhaps many others. (GCC installs its own header files
646 in another directory which is based on the `--prefix' value.)
648 Both the local-prefix include directory and the GCC-prefix include
649 directory are part of GCC's "system include" directories.
650 Although these two directories are not fixed, they need to be
651 searched in the proper order for the correct processing of the
652 include_next directive. The local-prefix include directory is
653 searched before the GCC-prefix include directory. Another
654 characteristic of system include directories is that pedantic
655 warnings are turned off for headers in these directories.
657 Some autoconf macros add `-I DIRECTORY' options to the compiler
658 command line, to ensure that directories containing installed
659 packages' headers are searched. When DIRECTORY is one of GCC's
660 system include directories, GCC will ignore the option so that
661 system directories continue to be processed in the correct order.
662 This may result in a search order different from what was
663 specified but the directory will still be searched.
665 GCC automatically searches for ordinary libraries using
666 `GCC_EXEC_PREFIX'. Thus, when the same installation prefix is
667 used for both GCC and packages, GCC will automatically search for
668 both headers and libraries. This provides a configuration that is
669 easy to use. GCC behaves in a manner similar to that when it is
670 installed as a system compiler in `/usr'.
672 Sites that need to install multiple versions of GCC may not want to
673 use the above simple configuration. It is possible to use the
674 `--program-prefix', `--program-suffix' and
675 `--program-transform-name' options to install multiple versions
676 into a single directory, but it may be simpler to use different
677 prefixes and the `--with-local-prefix' option to specify the
678 location of the site-specific files for each version. It will
679 then be necessary for users to specify explicitly the location of
680 local site libraries (e.g., with `LIBRARY_PATH').
682 The same value can be used for both `--with-local-prefix' and
683 `--prefix' provided it is not `/usr'. This can be used to avoid
684 the default search of `/usr/local/include'.
686 *Do not* specify `/usr' as the `--with-local-prefix'! The
687 directory you use for `--with-local-prefix' *must not* contain any
688 of the system's standard header files. If it did contain them,
689 certain programs would be miscompiled (including GNU Emacs, on
690 certain targets), because this would override and nullify the
691 header file corrections made by the `fixincludes' script.
693 Indications are that people who use this option use it based on
694 mistaken ideas of what it is for. People use it as if it
695 specified where to install part of GCC. Perhaps they make this
696 assumption because installing GCC creates the directory.
698 `--with-native-system-header-dir=DIRNAME'
699 Specifies that DIRNAME is the directory that contains native system
700 header files, rather than `/usr/include'. This option is most
701 useful if you are creating a compiler that should be isolated from
702 the system as much as possible. It is most commonly used with the
703 `--with-sysroot' option and will cause GCC to search DIRNAME
704 inside the system root specified by that option.
706 `--enable-shared[=PACKAGE[,...]]'
707 Build shared versions of libraries, if shared libraries are
708 supported on the target platform. Unlike GCC 2.95.x and earlier,
709 shared libraries are enabled by default on all platforms that
710 support shared libraries.
712 If a list of packages is given as an argument, build shared
713 libraries only for the listed packages. For other packages, only
714 static libraries will be built. Package names currently
715 recognized in the GCC tree are `libgcc' (also known as `gcc'),
716 `libstdc++' (not `libstdc++-v3'), `libffi', `zlib', `boehm-gc',
717 `ada', `libada', `libjava', `libgo', and `libobjc'. Note
718 `libiberty' does not support shared libraries at all.
720 Use `--disable-shared' to build only static libraries. Note that
721 `--disable-shared' does not accept a list of package names as
722 argument, only `--enable-shared' does.
725 Specify that the compiler should assume that the assembler it
726 finds is the GNU assembler. However, this does not modify the
727 rules to find an assembler and will result in confusion if the
728 assembler found is not actually the GNU assembler. (Confusion may
729 also result if the compiler finds the GNU assembler but has not
730 been configured with `--with-gnu-as'.) If you have more than one
731 assembler installed on your system, you may want to use this
732 option in connection with `--with-as=PATHNAME' or
733 `--with-build-time-tools=PATHNAME'.
735 The following systems are the only ones where it makes a difference
736 whether you use the GNU assembler. On any other system,
737 `--with-gnu-as' has no effect.
743 * `sparc-sun-solaris2.ANY'
745 * `sparc64-ANY-solaris2.ANY'
748 Specify that the compiler should use the assembler pointed to by
749 PATHNAME, rather than the one found by the standard rules to find
750 an assembler, which are:
751 * Unless GCC is being built with a cross compiler, check the
752 `LIBEXEC/gcc/TARGET/VERSION' directory. LIBEXEC defaults to
753 `EXEC-PREFIX/libexec'; EXEC-PREFIX defaults to PREFIX, which
754 defaults to `/usr/local' unless overridden by the
755 `--prefix=PATHNAME' switch described above. TARGET is the
756 target system triple, such as `sparc-sun-solaris2.7', and
757 VERSION denotes the GCC version, such as 3.0.
759 * If the target system is the same that you are building on,
760 check operating system specific directories (e.g.
761 `/usr/ccs/bin' on Sun Solaris 2).
763 * Check in the `PATH' for a tool whose name is prefixed by the
764 target system triple.
766 * Check in the `PATH' for a tool whose name is not prefixed by
767 the target system triple, if the host and target system
768 triple are the same (in other words, we use a host tool if it
769 can be used for the target as well).
771 You may want to use `--with-as' if no assembler is installed in
772 the directories listed above, or if you have multiple assemblers
773 installed and want to choose one that is not found by the above
777 Same as `--with-gnu-as' but for the linker.
780 Same as `--with-as' but for the linker.
783 Specify that stabs debugging information should be used instead of
784 whatever format the host normally uses. Normally GCC uses the
785 same debug format as the host system.
787 On MIPS based systems and on Alphas, you must specify whether you
788 want GCC to create the normal ECOFF debugging format, or to use
789 BSD-style stabs passed through the ECOFF symbol table. The normal
790 ECOFF debug format cannot fully handle languages other than C.
791 BSD stabs format can handle other languages, but it only works
792 with the GNU debugger GDB.
794 Normally, GCC uses the ECOFF debugging format by default; if you
795 prefer BSD stabs, specify `--with-stabs' when you configure GCC.
797 No matter which default you choose when you configure GCC, the user
798 can use the `-gcoff' and `-gstabs+' options to specify explicitly
799 the debug format for a particular compilation.
801 `--with-stabs' is meaningful on the ISC system on the 386, also, if
802 `--with-gas' is used. It selects use of stabs debugging
803 information embedded in COFF output. This kind of debugging
804 information supports C++ well; ordinary COFF debugging information
807 `--with-stabs' is also meaningful on 386 systems running SVR4. It
808 selects use of stabs debugging information embedded in ELF output.
809 The C++ compiler currently (2.6.0) does not support the DWARF
810 debugging information normally used on 386 SVR4 platforms; stabs
811 provide a workable alternative. This requires gas and gdb, as the
812 normal SVR4 tools can not generate or interpret stabs.
815 Specify the default TLS dialect, for systems were there is a
816 choice. For ARM targets, possible values for DIALECT are `gnu' or
817 `gnu2', which select between the original GNU dialect and the GNU
818 TLS descriptor-based dialect.
821 Specify that multiple target libraries to support different target
822 variants, calling conventions, etc. should not be built. The
823 default is to build a predefined set of them.
825 Some targets provide finer-grained control over which multilibs
826 are built (e.g., `--disable-softfloat'):
828 fpu, 26bit, underscore, interwork, biendian, nofmult.
831 softfloat, m68881, m68000, m68020.
834 single-float, biendian, softfloat.
836 `powerpc*-*-*, rs6000*-*-*'
837 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos,
841 `--with-multilib-list=LIST'
842 `--without-multilib-list'
843 Specify what multilibs to build. Currently only implemented for
844 sh*-*-* and x86-64-*-linux*.
847 LIST is a comma separated list of CPU names. These must be
848 of the form `sh*' or `m*' (in which case they match the
849 compiler option for that processor). The list should not
850 contain any endian options - these are handled by
853 If LIST is empty, then there will be no multilibs for extra
854 processors. The multilib for the secondary endian remains
857 As a special case, if an entry in the list starts with a `!'
858 (exclamation point), then it is added to the list of excluded
859 multilibs. Entries of this sort should be compatible with
860 `MULTILIB_EXCLUDES' (once the leading `!' has been stripped).
862 If `--with-multilib-list' is not given, then a default set of
863 multilibs is selected based on the value of `--target'. This
864 is usually the complete set of libraries, but some targets
865 imply a more specialized subset.
867 Example 1: to configure a compiler for SH4A only, but
868 supporting both endians, with little endian being the default:
869 --with-cpu=sh4a --with-endian=little,big --with-multilib-list=
871 Example 2: to configure a compiler for both SH4A and
872 SH4AL-DSP, but with only little endian SH4AL:
873 --with-cpu=sh4a --with-endian=little,big \
874 --with-multilib-list=sh4al,!mb/m4al
877 LIST is a comma separated list of `m32', `m64' and `mx32' to
878 enable 32-bit, 64-bit and x32 run-time libraries,
879 respectively. If LIST is empty, then there will be no
880 multilibs and only the default run-time library will be
883 If `--with-multilib-list' is not given, then only 32-bit and
884 64-bit run-time libraries will be enabled.
886 `--with-endian=ENDIANS'
887 Specify what endians to use. Currently only implemented for
890 ENDIANS may be one of the following:
892 Use big endian exclusively.
895 Use little endian exclusively.
898 Use big endian by default. Provide a multilib for little
902 Use little endian by default. Provide a multilib for big
906 Specify that the target supports threads. This affects the
907 Objective-C compiler and runtime library, and exception handling
908 for other languages like C++ and Java. On some systems, this is
911 In general, the best (and, in many cases, the only known) threading
912 model available will be configured for use. Beware that on some
913 systems, GCC has not been taught what threading models are
914 generally available for the system. In this case,
915 `--enable-threads' is an alias for `--enable-threads=single'.
918 Specify that threading support should be disabled for the system.
919 This is an alias for `--enable-threads=single'.
921 `--enable-threads=LIB'
922 Specify that LIB is the thread support library. This affects the
923 Objective-C compiler and runtime library, and exception handling
924 for other languages like C++ and Java. The possibilities for LIB
934 LynxOS thread support.
937 MIPS SDE thread support.
940 This is an alias for `single'.
943 Generic POSIX/Unix98 thread support.
946 RTEMS thread support.
949 Disable thread support, should work for all platforms.
955 VxWorks thread support.
958 Microsoft Win32 API thread support.
961 Specify that the target supports TLS (Thread Local Storage).
962 Usually configure can correctly determine if TLS is supported. In
963 cases where it guesses incorrectly, TLS can be explicitly enabled
964 or disabled with `--enable-tls' or `--disable-tls'. This can
965 happen if the assembler supports TLS but the C library does not,
966 or if the assumptions made by the configure test are incorrect.
969 Specify that the target does not support TLS. This is an alias
970 for `--enable-tls=no'.
975 Specify which cpu variant the compiler should generate code for by
976 default. CPU will be used as the default value of the `-mcpu='
977 switch. This option is only supported on some targets, including
978 ARM, i386, M68k, PowerPC, and SPARC. The `--with-cpu-32' and
979 `--with-cpu-64' options specify separate default CPUs for 32-bit
980 and 64-bit modes; these options are only supported for i386,
983 `--with-schedule=CPU'
993 These configure options provide default values for the
994 `-mschedule=', `-march=', `-mtune=', `-mabi=', and `-mfpu='
995 options and for `-mhard-float' or `-msoft-float'. As with
996 `--with-cpu', which switches will be accepted and acceptable values
997 of the arguments depend on the target.
1000 Specify if the compiler should default to `-marm' or `-mthumb'.
1001 This option is only supported on ARM targets.
1003 `--with-stack-offset=NUM'
1004 This option sets the default for the -mstack-offset=NUM option,
1005 and will thus generally also control the setting of this option for
1006 libraries. This option is only supported on Epiphany targets.
1009 This options sets `-mfpmath=sse' by default and specifies the
1010 default ISA for floating-point arithmetics. You can select either
1011 `sse' which enables `-msse2' or `avx' which enables `-mavx' by
1012 default. This option is only supported on i386 and x86-64 targets.
1014 `--with-divide=TYPE'
1015 Specify how the compiler should generate code for checking for
1016 division by zero. This option is only supported on the MIPS
1017 target. The possibilities for TYPE are:
1019 Division by zero checks use conditional traps (this is the
1020 default on systems that support conditional traps).
1023 Division by zero checks use the break instruction.
1026 On MIPS targets, make `-mllsc' the default when no `-mno-llsc'
1027 option is passed. This is the default for Linux-based targets, as
1028 the kernel will emulate them if the ISA does not provide them.
1031 On MIPS targets, make `-mno-llsc' the default when no `-mllsc'
1035 On MIPS targets, make `-msynci' the default when no `-mno-synci'
1039 On MIPS targets, make `-mno-synci' the default when no `-msynci'
1040 option is passed. This is the default.
1043 On MIPS targets, make use of copy relocations and PLTs. These
1044 features are extensions to the traditional SVR4-based MIPS ABIs
1045 and require support from GNU binutils and the runtime C library.
1047 `--enable-__cxa_atexit'
1048 Define if you want to use __cxa_atexit, rather than atexit, to
1049 register C++ destructors for local statics and global objects.
1050 This is essential for fully standards-compliant handling of
1051 destructors, but requires __cxa_atexit in libc. This option is
1052 currently only available on systems with GNU libc. When enabled,
1053 this will cause `-fuse-cxa-atexit' to be passed by default.
1055 `--enable-gnu-indirect-function'
1056 Define if you want to enable the `ifunc' attribute. This option is
1057 currently only available on systems with GNU libc on certain
1060 `--enable-target-optspace'
1061 Specify that target libraries should be optimized for code space
1062 instead of code speed. This is the default for the m32r platform.
1064 `--with-cpp-install-dir=DIRNAME'
1065 Specify that the user visible `cpp' program should be installed in
1066 `PREFIX/DIRNAME/cpp', in addition to BINDIR.
1069 Enable COMDAT group support. This is primarily used to override
1070 the automatically detected value.
1072 `--enable-initfini-array'
1073 Force the use of sections `.init_array' and `.fini_array' (instead
1074 of `.init' and `.fini') for constructors and destructors. Option
1075 `--disable-initfini-array' has the opposite effect. If neither
1076 option is specified, the configure script will try to guess
1077 whether the `.init_array' and `.fini_array' sections are supported
1078 and, if they are, use them.
1080 `--enable-build-with-cxx'
1081 Build GCC using a C++ compiler rather than a C compiler. This is
1082 an experimental option which may become the default in a later
1085 `--enable-build-poststage1-with-cxx'
1086 When bootstrapping, build stages 2 and 3 of GCC using a C++
1087 compiler rather than a C compiler. Stage 1 is still built with a
1088 C compiler. This is enabled by default and may be disabled using
1089 `--disable-build-poststage1-with-cxx'.
1091 `--enable-maintainer-mode'
1092 The build rules that regenerate the Autoconf and Automake output
1093 files as well as the GCC master message catalog `gcc.pot' are
1094 normally disabled. This is because it can only be rebuilt if the
1095 complete source tree is present. If you have changed the sources
1096 and want to rebuild the catalog, configuring with
1097 `--enable-maintainer-mode' will enable this. Note that you need a
1098 recent version of the `gettext' tools to do so.
1100 `--disable-bootstrap'
1101 For a native build, the default configuration is to perform a
1102 3-stage bootstrap of the compiler when `make' is invoked, testing
1103 that GCC can compile itself correctly. If you want to disable
1104 this process, you can configure with `--disable-bootstrap'.
1106 `--enable-bootstrap'
1107 In special cases, you may want to perform a 3-stage build even if
1108 the target and host triplets are different. This is possible when
1109 the host can run code compiled for the target (e.g. host is
1110 i686-linux, target is i486-linux). Starting from GCC 4.2, to do
1111 this you have to configure explicitly with `--enable-bootstrap'.
1113 `--enable-generated-files-in-srcdir'
1114 Neither the .c and .h files that are generated from Bison and flex
1115 nor the info manuals and man pages that are built from the .texi
1116 files are present in the SVN development tree. When building GCC
1117 from that development tree, or from one of our snapshots, those
1118 generated files are placed in your build directory, which allows
1119 for the source to be in a readonly directory.
1121 If you configure with `--enable-generated-files-in-srcdir' then
1122 those generated files will go into the source directory. This is
1123 mainly intended for generating release or prerelease tarballs of
1124 the GCC sources, since it is not a requirement that the users of
1125 source releases to have flex, Bison, or makeinfo.
1127 `--enable-version-specific-runtime-libs'
1128 Specify that runtime libraries should be installed in the compiler
1129 specific subdirectory (`LIBDIR/gcc') rather than the usual places.
1130 In addition, `libstdc++''s include files will be installed into
1131 `LIBDIR' unless you overruled it by using
1132 `--with-gxx-include-dir=DIRNAME'. Using this option is
1133 particularly useful if you intend to use several versions of GCC in
1134 parallel. This is currently supported by `libgfortran',
1135 `libjava', `libmudflap', `libstdc++', and `libobjc'.
1137 `--enable-languages=LANG1,LANG2,...'
1138 Specify that only a particular subset of compilers and their
1139 runtime libraries should be built. For a list of valid values for
1140 LANGN you can issue the following command in the `gcc' directory
1141 of your GCC source tree:
1142 grep language= */config-lang.in
1143 Currently, you can use any of the following: `all', `ada', `c',
1144 `c++', `fortran', `go', `java', `objc', `obj-c++'. Building the
1145 Ada compiler has special requirements, see below. If you do not
1146 pass this flag, or specify the option `all', then all default
1147 languages available in the `gcc' sub-tree will be configured.
1148 Ada, Go and Objective-C++ are not default languages; the rest are.
1150 `--enable-stage1-languages=LANG1,LANG2,...'
1151 Specify that a particular subset of compilers and their runtime
1152 libraries should be built with the system C compiler during stage
1153 1 of the bootstrap process, rather than only in later stages with
1154 the bootstrapped C compiler. The list of valid values is the same
1155 as for `--enable-languages', and the option `all' will select all
1156 of the languages enabled by `--enable-languages'. This option is
1157 primarily useful for GCC development; for instance, when a
1158 development version of the compiler cannot bootstrap due to
1159 compiler bugs, or when one is debugging front ends other than the
1160 C front end. When this option is used, one can then build the
1161 target libraries for the specified languages with the stage-1
1162 compiler by using `make stage1-bubble all-target', or run the
1163 testsuite on the stage-1 compiler for the specified languages
1164 using `make stage1-start check-gcc'.
1167 Specify that the run-time libraries and tools used by GNAT should
1168 not be built. This can be useful for debugging, or for
1169 compatibility with previous Ada build procedures, when it was
1170 required to explicitly do a `make -C gcc gnatlib_and_tools'.
1173 Specify that the run-time libraries for stack smashing protection
1174 should not be built.
1176 `--disable-libquadmath'
1177 Specify that the GCC quad-precision math library should not be
1178 built. On some systems, the library is required to be linkable
1179 when building the Fortran front end, unless
1180 `--disable-libquadmath-support' is used.
1182 `--disable-libquadmath-support'
1183 Specify that the Fortran front end and `libgfortran' do not add
1184 support for `libquadmath' on systems supporting it.
1187 Specify that the run-time libraries used by GOMP should not be
1191 Specify that the compiler should use DWARF 2 debugging information
1194 `--enable-targets=all'
1195 `--enable-targets=TARGET_LIST'
1196 Some GCC targets, e.g. powerpc64-linux, build bi-arch compilers.
1197 These are compilers that are able to generate either 64-bit or
1198 32-bit code. Typically, the corresponding 32-bit target, e.g.
1199 powerpc-linux for powerpc64-linux, only generates 32-bit code.
1200 This option enables the 32-bit target to be a bi-arch compiler,
1201 which is useful when you want a bi-arch compiler that defaults to
1202 32-bit, and you are building a bi-arch or multi-arch binutils in a
1203 combined tree. On mips-linux, this will build a tri-arch compiler
1204 (ABI o32/n32/64), defaulted to o32. Currently, this option only
1205 affects sparc-linux, powerpc-linux, x86-linux, mips-linux and
1208 `--enable-secureplt'
1209 This option enables `-msecure-plt' by default for powerpc-linux.
1210 *Note RS/6000 and PowerPC Options: (gcc)RS/6000 and PowerPC
1214 This option enables `-mcld' by default for 32-bit x86 targets.
1215 *Note i386 and x86-64 Options: (gcc)i386 and x86-64 Options,
1217 `--enable-win32-registry'
1218 `--enable-win32-registry=KEY'
1219 `--disable-win32-registry'
1220 The `--enable-win32-registry' option enables Microsoft
1221 Windows-hosted GCC to look up installations paths in the registry
1222 using the following key:
1224 `HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\KEY'
1226 KEY defaults to GCC version number, and can be overridden by the
1227 `--enable-win32-registry=KEY' option. Vendors and distributors
1228 who use custom installers are encouraged to provide a different
1229 key, perhaps one comprised of vendor name and GCC version number,
1230 to avoid conflict with existing installations. This feature is
1231 enabled by default, and can be disabled by
1232 `--disable-win32-registry' option. This option has no effect on
1236 Specify that the machine does not have a floating point unit. This
1237 option only applies to `m68k-sun-sunosN'. On any other system,
1238 `--nfp' has no effect.
1242 `--enable-werror=yes'
1243 `--enable-werror=no'
1244 When you specify this option, it controls whether certain files in
1245 the compiler are built with `-Werror' in bootstrap stage2 and
1246 later. If you don't specify it, `-Werror' is turned on for the
1247 main development trunk. However it defaults to off for release
1248 branches and final releases. The specific files which get
1249 `-Werror' are controlled by the Makefiles.
1252 `--enable-checking=LIST'
1253 When you specify this option, the compiler is built to perform
1254 internal consistency checks of the requested complexity. This
1255 does not change the generated code, but adds error checking within
1256 the compiler. This will slow down the compiler and may only work
1257 properly if you are building the compiler with GCC. This is `yes'
1258 by default when building from SVN or snapshots, but `release' for
1259 releases. The default for building the stage1 compiler is `yes'.
1260 More control over the checks may be had by specifying LIST. The
1261 categories of checks available are `yes' (most common checks
1262 `assert,misc,tree,gc,rtlflag,runtime'), `no' (no checks at all),
1263 `all' (all but `valgrind'), `release' (cheapest checks
1264 `assert,runtime') or `none' (same as `no'). Individual checks can
1265 be enabled with these flags `assert', `df', `fold', `gc', `gcac'
1266 `misc', `rtl', `rtlflag', `runtime', `tree', and `valgrind'.
1268 The `valgrind' check requires the external `valgrind' simulator,
1269 available from `http://valgrind.org/'. The `df', `rtl', `gcac'
1270 and `valgrind' checks are very expensive. To disable all
1271 checking, `--disable-checking' or `--enable-checking=none' must be
1272 explicitly requested. Disabling assertions will make the compiler
1273 and runtime slightly faster but increase the risk of undetected
1274 internal errors causing wrong code to be generated.
1276 `--disable-stage1-checking'
1277 `--enable-stage1-checking'
1278 `--enable-stage1-checking=LIST'
1279 If no `--enable-checking' option is specified the stage1 compiler
1280 will be built with `yes' checking enabled, otherwise the stage1
1281 checking flags are the same as specified by `--enable-checking'.
1282 To build the stage1 compiler with different checking options use
1283 `--enable-stage1-checking'. The list of checking options is the
1284 same as for `--enable-checking'. If your system is too slow or
1285 too small to bootstrap a released compiler with checking for
1286 stage1 enabled, you can use `--disable-stage1-checking' to disable
1287 checking for the stage1 compiler.
1290 `--enable-coverage=LEVEL'
1291 With this option, the compiler is built to collect self coverage
1292 information, every time it is run. This is for internal
1293 development purposes, and only works when the compiler is being
1294 built with gcc. The LEVEL argument controls whether the compiler
1295 is built optimized or not, values are `opt' and `noopt'. For
1296 coverage analysis you want to disable optimization, for
1297 performance analysis you want to enable optimization. When
1298 coverage is enabled, the default level is without optimization.
1300 `--enable-gather-detailed-mem-stats'
1301 When this option is specified more detailed information on memory
1302 allocation is gathered. This information is printed when using
1307 With this option you can specify the garbage collector
1308 implementation used during the compilation process. CHOICE can be
1309 one of `page' and `zone', where `page' is the default.
1313 The `--enable-nls' option enables Native Language Support (NLS),
1314 which lets GCC output diagnostics in languages other than American
1315 English. Native Language Support is enabled by default if not
1316 doing a canadian cross build. The `--disable-nls' option disables
1319 `--with-included-gettext'
1320 If NLS is enabled, the `--with-included-gettext' option causes the
1321 build procedure to prefer its copy of GNU `gettext'.
1324 If NLS is enabled, and if the host lacks `gettext' but has the
1325 inferior `catgets' interface, the GCC build procedure normally
1326 ignores `catgets' and instead uses GCC's copy of the GNU `gettext'
1327 library. The `--with-catgets' option causes the build procedure
1328 to use the host's `catgets' in this situation.
1330 `--with-libiconv-prefix=DIR'
1331 Search for libiconv header files in `DIR/include' and libiconv
1332 library files in `DIR/lib'.
1335 Enable configuration for an obsoleted system. If you attempt to
1336 configure GCC for a system (build, host, or target) which has been
1337 obsoleted, and you do not specify this flag, configure will halt
1338 with an error message.
1340 All support for systems which have been obsoleted in one release
1341 of GCC is removed entirely in the next major release, unless
1342 someone steps forward to maintain the port.
1344 `--enable-decimal-float'
1345 `--enable-decimal-float=yes'
1346 `--enable-decimal-float=no'
1347 `--enable-decimal-float=bid'
1348 `--enable-decimal-float=dpd'
1349 `--disable-decimal-float'
1350 Enable (or disable) support for the C decimal floating point
1351 extension that is in the IEEE 754-2008 standard. This is enabled
1352 by default only on PowerPC, i386, and x86_64 GNU/Linux systems.
1353 Other systems may also support it, but require the user to
1354 specifically enable it. You can optionally control which decimal
1355 floating point format is used (either `bid' or `dpd'). The `bid'
1356 (binary integer decimal) format is default on i386 and x86_64
1357 systems, and the `dpd' (densely packed decimal) format is default
1360 `--enable-fixed-point'
1361 `--disable-fixed-point'
1362 Enable (or disable) support for C fixed-point arithmetic. This
1363 option is enabled by default for some targets (such as MIPS) which
1364 have hardware-support for fixed-point operations. On other
1365 targets, you may enable this option manually.
1367 `--with-long-double-128'
1368 Specify if `long double' type should be 128-bit by default on
1369 selected GNU/Linux architectures. If using
1370 `--without-long-double-128', `long double' will be by default
1371 64-bit, the same as `double' type. When neither of these
1372 configure options are used, the default will be 128-bit `long
1373 double' when built against GNU C Library 2.4 and later, 64-bit
1374 `long double' otherwise.
1376 `--with-gmp=PATHNAME'
1377 `--with-gmp-include=PATHNAME'
1378 `--with-gmp-lib=PATHNAME'
1379 `--with-mpfr=PATHNAME'
1380 `--with-mpfr-include=PATHNAME'
1381 `--with-mpfr-lib=PATHNAME'
1382 `--with-mpc=PATHNAME'
1383 `--with-mpc-include=PATHNAME'
1384 `--with-mpc-lib=PATHNAME'
1385 If you want to build GCC but do not have the GMP library, the MPFR
1386 library and/or the MPC library installed in a standard location and
1387 do not have their sources present in the GCC source tree then you
1388 can explicitly specify the directory where they are installed
1389 (`--with-gmp=GMPINSTALLDIR', `--with-mpfr=MPFRINSTALLDIR',
1390 `--with-mpc=MPCINSTALLDIR'). The `--with-gmp=GMPINSTALLDIR'
1391 option is shorthand for `--with-gmp-lib=GMPINSTALLDIR/lib' and
1392 `--with-gmp-include=GMPINSTALLDIR/include'. Likewise the
1393 `--with-mpfr=MPFRINSTALLDIR' option is shorthand for
1394 `--with-mpfr-lib=MPFRINSTALLDIR/lib' and
1395 `--with-mpfr-include=MPFRINSTALLDIR/include', also the
1396 `--with-mpc=MPCINSTALLDIR' option is shorthand for
1397 `--with-mpc-lib=MPCINSTALLDIR/lib' and
1398 `--with-mpc-include=MPCINSTALLDIR/include'. If these shorthand
1399 assumptions are not correct, you can use the explicit include and
1400 lib options directly. You might also need to ensure the shared
1401 libraries can be found by the dynamic linker when building and
1402 using GCC, for example by setting the runtime shared library path
1403 variable (`LD_LIBRARY_PATH' on GNU/Linux and Solaris systems).
1405 These flags are applicable to the host platform only. When
1406 building a cross compiler, they will not be used to configure
1409 `--with-ppl=PATHNAME'
1410 `--with-ppl-include=PATHNAME'
1411 `--with-ppl-lib=PATHNAME'
1412 `--with-cloog=PATHNAME'
1413 `--with-cloog-include=PATHNAME'
1414 `--with-cloog-lib=PATHNAME'
1415 If you do not have PPL (the Parma Polyhedra Library) and the CLooG
1416 libraries installed in a standard location and you want to build
1417 GCC, you can explicitly specify the directory where they are
1418 installed (`--with-ppl=PPLINSTALLDIR',
1419 `--with-cloog=CLOOGINSTALLDIR'). The `--with-ppl=PPLINSTALLDIR'
1420 option is shorthand for `--with-ppl-lib=PPLINSTALLDIR/lib' and
1421 `--with-ppl-include=PPLINSTALLDIR/include'. Likewise the
1422 `--with-cloog=CLOOGINSTALLDIR' option is shorthand for
1423 `--with-cloog-lib=CLOOGINSTALLDIR/lib' and
1424 `--with-cloog-include=CLOOGINSTALLDIR/include'. If these
1425 shorthand assumptions are not correct, you can use the explicit
1426 include and lib options directly.
1428 These flags are applicable to the host platform only. When
1429 building a cross compiler, they will not be used to configure
1432 `--with-host-libstdcxx=LINKER-ARGS'
1433 If you are linking with a static copy of PPL, you can use this
1434 option to specify how the linker should find the standard C++
1435 library used internally by PPL. Typical values of LINKER-ARGS
1436 might be `-lstdc++' or `-Wl,-Bstatic,-lstdc++,-Bdynamic -lm'. If
1437 you are linking with a shared copy of PPL, you probably do not
1438 need this option; shared library dependencies will cause the
1439 linker to search for the standard C++ library automatically.
1441 `--with-stage1-ldflags=FLAGS'
1442 This option may be used to set linker flags to be used when linking
1443 stage 1 of GCC. These are also used when linking GCC if
1444 configured with `--disable-bootstrap'. By default no special
1447 `--with-stage1-libs=LIBS'
1448 This option may be used to set libraries to be used when linking
1449 stage 1 of GCC. These are also used when linking GCC if
1450 configured with `--disable-bootstrap'. The default is the
1451 argument to `--with-host-libstdcxx', if specified.
1453 `--with-boot-ldflags=FLAGS'
1454 This option may be used to set linker flags to be used when linking
1455 stage 2 and later when bootstrapping GCC. If neither
1456 -with-boot-libs nor -with-host-libstdcxx is set to a value, then
1457 the default is `-static-libstdc++ -static-libgcc'.
1459 `--with-boot-libs=LIBS'
1460 This option may be used to set libraries to be used when linking
1461 stage 2 and later when bootstrapping GCC. The default is the
1462 argument to `--with-host-libstdcxx', if specified.
1464 `--with-debug-prefix-map=MAP'
1465 Convert source directory names using `-fdebug-prefix-map' when
1466 building runtime libraries. `MAP' is a space-separated list of
1467 maps of the form `OLD=NEW'.
1469 `--enable-linker-build-id'
1470 Tells GCC to pass `--build-id' option to the linker for all final
1471 links (links performed without the `-r' or `--relocatable'
1472 option), if the linker supports it. If you specify
1473 `--enable-linker-build-id', but your linker does not support
1474 `--build-id' option, a warning is issued and the
1475 `--enable-linker-build-id' option is ignored. The default is off.
1477 `--with-linker-hash-style=CHOICE'
1478 Tells GCC to pass `--hash-style=CHOICE' option to the linker for
1479 all final links. CHOICE can be one of `sysv', `gnu', and `both'
1480 where `sysv' is the default.
1482 `--enable-gnu-unique-object'
1483 `--disable-gnu-unique-object'
1484 Tells GCC to use the gnu_unique_object relocation for C++ template
1485 static data members and inline function local statics. Enabled by
1486 default for a native toolchain with an assembler that accepts it
1487 and GLIBC 2.11 or above, otherwise disabled.
1491 Enable support for link-time optimization (LTO). This is enabled
1492 by default, and may be disabled using `--disable-lto'.
1494 `--with-plugin-ld=PATHNAME'
1495 Enable an alternate linker to be used at link-time optimization
1496 (LTO) link time when `-fuse-linker-plugin' is enabled. This
1497 linker should have plugin support such as gold starting with
1498 version 2.20 or GNU ld starting with version 2.21. See
1499 `-fuse-linker-plugin' for details.
1501 Cross-Compiler-Specific Options
1502 -------------------------------
1504 The following options only apply to building cross compilers.
1507 `--with-sysroot=DIR'
1508 Tells GCC to consider DIR as the root of a tree that contains (a
1509 subset of) the root filesystem of the target operating system.
1510 Target system headers, libraries and run-time object files will be
1511 searched for in there. More specifically, this acts as if
1512 `--sysroot=DIR' was added to the default options of the built
1513 compiler. The specified directory is not copied into the install
1514 tree, unlike the options `--with-headers' and `--with-libs' that
1515 this option obsoletes. The default value, in case
1516 `--with-sysroot' is not given an argument, is
1517 `${gcc_tooldir}/sys-root'. If the specified directory is a
1518 subdirectory of `${exec_prefix}', then it will be found relative to
1519 the GCC binaries if the installation tree is moved.
1521 This option affects the system root for the compiler used to build
1522 target libraries (which runs on the build system) and the compiler
1523 newly installed with `make install'; it does not affect the
1524 compiler which is used to build GCC itself.
1526 If you specify the `--with-native-system-header-dir=DIRNAME'
1527 option then the compiler will search that directory within DIRNAME
1528 for native system headers rather than the default `/usr/include'.
1530 `--with-build-sysroot'
1531 `--with-build-sysroot=DIR'
1532 Tells GCC to consider DIR as the system root (see
1533 `--with-sysroot') while building target libraries, instead of the
1534 directory specified with `--with-sysroot'. This option is only
1535 useful when you are already using `--with-sysroot'. You can use
1536 `--with-build-sysroot' when you are configuring with `--prefix'
1537 set to a directory that is different from the one in which you are
1538 installing GCC and your target libraries.
1540 This option affects the system root for the compiler used to build
1541 target libraries (which runs on the build system); it does not
1542 affect the compiler which is used to build GCC itself.
1544 If you specify the `--with-native-system-header-dir=DIRNAME'
1545 option then the compiler will search that directory within DIRNAME
1546 for native system headers rather than the default `/usr/include'.
1549 `--with-headers=DIR'
1550 Deprecated in favor of `--with-sysroot'. Specifies that target
1551 headers are available when building a cross compiler. The DIR
1552 argument specifies a directory which has the target include files.
1553 These include files will be copied into the `gcc' install
1554 directory. _This option with the DIR argument is required_ when
1555 building a cross compiler, if `PREFIX/TARGET/sys-include' doesn't
1556 pre-exist. If `PREFIX/TARGET/sys-include' does pre-exist, the DIR
1557 argument may be omitted. `fixincludes' will be run on these files
1558 to make them compatible with GCC.
1561 Tells GCC not use any target headers from a libc when building a
1562 cross compiler. When crossing to GNU/Linux, you need the headers
1563 so GCC can build the exception handling for libgcc.
1566 `--with-libs="DIR1 DIR2 ... DIRN"'
1567 Deprecated in favor of `--with-sysroot'. Specifies a list of
1568 directories which contain the target runtime libraries. These
1569 libraries will be copied into the `gcc' install directory. If the
1570 directory list is omitted, this option has no effect.
1573 Specifies that `newlib' is being used as the target C library.
1574 This causes `__eprintf' to be omitted from `libgcc.a' on the
1575 assumption that it will be provided by `newlib'.
1577 `--with-build-time-tools=DIR'
1578 Specifies where to find the set of target tools (assembler,
1579 linker, etc.) that will be used while building GCC itself. This
1580 option can be useful if the directory layouts are different
1581 between the system you are building GCC on, and the system where
1584 For example, on an `ia64-hp-hpux' system, you may have the GNU
1585 assembler and linker in `/usr/bin', and the native tools in a
1586 different path, and build a toolchain that expects to find the
1587 native tools in `/usr/bin'.
1589 When you use this option, you should ensure that DIR includes
1590 `ar', `as', `ld', `nm', `ranlib' and `strip' if necessary, and
1591 possibly `objdump'. Otherwise, GCC may use an inconsistent set of
1594 Java-Specific Options
1595 ---------------------
1597 The following option applies to the build of the Java front end.
1600 Specify that the run-time libraries used by GCJ should not be
1601 built. This is useful in case you intend to use GCJ with some
1602 other run-time, or you're going to install it separately, or it
1603 just happens not to build on your particular machine. In general,
1604 if the Java front end is enabled, the GCJ libraries will be
1605 enabled too, unless they're known to not work on the target
1606 platform. If GCJ is enabled but `libgcj' isn't built, you may
1607 need to port it; in this case, before modifying the top-level
1608 `configure.in' so that `libgcj' is enabled by default on this
1609 platform, you may use `--enable-libgcj' to override the default.
1612 The following options apply to building `libgcj'.
1617 `--enable-java-maintainer-mode'
1618 By default the `libjava' build will not attempt to compile the
1619 `.java' source files to `.class'. Instead, it will use the
1620 `.class' files from the source tree. If you use this option you
1621 must have executables named `ecj1' and `gjavah' in your path for
1622 use by the build. You must use this option if you intend to
1623 modify any `.java' files in `libjava'.
1625 `--with-java-home=DIRNAME'
1626 This `libjava' option overrides the default value of the
1627 `java.home' system property. It is also used to set
1628 `sun.boot.class.path' to `DIRNAME/lib/rt.jar'. By default
1629 `java.home' is set to `PREFIX' and `sun.boot.class.path' to
1630 `DATADIR/java/libgcj-VERSION.jar'.
1632 `--with-ecj-jar=FILENAME'
1633 This option can be used to specify the location of an external jar
1634 file containing the Eclipse Java compiler. A specially modified
1635 version of this compiler is used by `gcj' to parse `.java' source
1636 files. If this option is given, the `libjava' build will create
1637 and install an `ecj1' executable which uses this jar file at
1640 If this option is not given, but an `ecj.jar' file is found in the
1641 topmost source tree at configure time, then the `libgcj' build
1642 will create and install `ecj1', and will also install the
1643 discovered `ecj.jar' into a suitable place in the install tree.
1645 If `ecj1' is not installed, then the user will have to supply one
1646 on his path in order for `gcj' to properly parse `.java' source
1647 files. A suitable jar is available from
1648 `ftp://sourceware.org/pub/java/'.
1650 `--disable-getenv-properties'
1651 Don't set system properties from `GCJ_PROPERTIES'.
1653 `--enable-hash-synchronization'
1654 Use a global hash table for monitor locks. Ordinarily, `libgcj''s
1655 `configure' script automatically makes the correct choice for this
1656 option for your platform. Only use this if you know you need the
1657 library to be configured differently.
1659 `--enable-interpreter'
1660 Enable the Java interpreter. The interpreter is automatically
1661 enabled by default on all platforms that support it. This option
1662 is really only useful if you want to disable the interpreter
1663 (using `--disable-interpreter').
1665 `--disable-java-net'
1666 Disable java.net. This disables the native part of java.net only,
1667 using non-functional stubs for native method implementations.
1670 Disable JVMPI support.
1672 `--disable-libgcj-bc'
1673 Disable BC ABI compilation of certain parts of libgcj. By default,
1674 some portions of libgcj are compiled with `-findirect-dispatch'
1675 and `-fno-indirect-classes', allowing them to be overridden at
1678 If `--disable-libgcj-bc' is specified, libgcj is built without
1679 these options. This allows the compile-time linker to resolve
1680 dependencies when statically linking to libgcj. However it makes
1681 it impossible to override the affected portions of libgcj at
1684 `--enable-reduced-reflection'
1685 Build most of libgcj with `-freduced-reflection'. This reduces
1686 the size of libgcj at the expense of not being able to do accurate
1687 reflection on the classes it contains. This option is safe if you
1688 know that code using libgcj will never use reflection on the
1689 standard runtime classes in libgcj (including using serialization,
1693 Enable runtime eCos target support.
1696 Don't use `libffi'. This will disable the interpreter and JNI
1697 support as well, as these require `libffi' to work.
1699 `--enable-libgcj-debug'
1700 Enable runtime debugging code.
1702 `--enable-libgcj-multifile'
1703 If specified, causes all `.java' source files to be compiled into
1704 `.class' files in one invocation of `gcj'. This can speed up
1705 build time, but is more resource-intensive. If this option is
1706 unspecified or disabled, `gcj' is invoked once for each `.java'
1707 file to compile into a `.class' file.
1709 `--with-libiconv-prefix=DIR'
1710 Search for libiconv in `DIR/include' and `DIR/lib'.
1712 `--enable-sjlj-exceptions'
1713 Force use of the `setjmp'/`longjmp'-based scheme for exceptions.
1714 `configure' ordinarily picks the correct value based on the
1715 platform. Only use this option if you are sure you need a
1718 `--with-system-zlib'
1719 Use installed `zlib' rather than that included with GCC.
1721 `--with-win32-nlsapi=ansi, unicows or unicode'
1722 Indicates how MinGW `libgcj' translates between UNICODE characters
1725 `--enable-java-home'
1726 If enabled, this creates a JPackage compatible SDK environment
1727 during install. Note that if -enable-java-home is used,
1728 -with-arch-directory=ARCH must also be specified.
1730 `--with-arch-directory=ARCH'
1731 Specifies the name to use for the `jre/lib/ARCH' directory in the
1732 SDK environment created when -enable-java-home is passed. Typical
1733 names for this directory include i386, amd64, ia64, etc.
1735 `--with-os-directory=DIR'
1736 Specifies the OS directory for the SDK include directory. This is
1737 set to auto detect, and is typically 'linux'.
1739 `--with-origin-name=NAME'
1740 Specifies the JPackage origin name. This defaults to the 'gcj' in
1743 `--with-arch-suffix=SUFFIX'
1744 Specifies the suffix for the sdk directory. Defaults to the empty
1745 string. Examples include '.x86_64' in
1746 'java-1.5.0-gcj-1.5.0.0.x86_64'.
1748 `--with-jvm-root-dir=DIR'
1749 Specifies where to install the SDK. Default is $(prefix)/lib/jvm.
1751 `--with-jvm-jar-dir=DIR'
1752 Specifies where to install jars. Default is
1753 $(prefix)/lib/jvm-exports.
1755 `--with-python-dir=DIR'
1756 Specifies where to install the Python modules used for
1757 aot-compile. DIR should not include the prefix used in
1758 installation. For example, if the Python modules are to be
1759 installed in /usr/lib/python2.5/site-packages, then
1760 -with-python-dir=/lib/python2.5/site-packages should be passed. If
1761 this is not specified, then the Python modules are installed in
1762 $(prefix)/share/python.
1764 `--enable-aot-compile-rpm'
1765 Adds aot-compile-rpm to the list of installed scripts.
1767 `--enable-browser-plugin'
1768 Build the gcjwebplugin web browser plugin.
1770 `--enable-static-libjava'
1771 Build static libraries in libjava. The default is to only build
1775 Use the single-byte `char' and the Win32 A functions natively,
1776 translating to and from UNICODE when using these functions.
1777 If unspecified, this is the default.
1780 Use the `WCHAR' and Win32 W functions natively. Adds
1781 `-lunicows' to `libgcj.spec' to link with `libunicows'.
1782 `unicows.dll' needs to be deployed on Microsoft Windows 9X
1783 machines running built executables. `libunicows.a', an
1784 open-source import library around Microsoft's `unicows.dll',
1785 is obtained from `http://libunicows.sourceforge.net/', which
1786 also gives details on getting `unicows.dll' from Microsoft.
1789 Use the `WCHAR' and Win32 W functions natively. Does _not_
1790 add `-lunicows' to `libgcj.spec'. The built executables will
1791 only run on Microsoft Windows NT and above.
1793 AWT-Specific Options
1794 ....................
1797 Use the X Window System.
1799 `--enable-java-awt=PEER(S)'
1800 Specifies the AWT peer library or libraries to build alongside
1801 `libgcj'. If this option is unspecified or disabled, AWT will be
1802 non-functional. Current valid values are `gtk' and `xlib'.
1803 Multiple libraries should be separated by a comma (i.e.
1804 `--enable-java-awt=gtk,xlib').
1806 `--enable-gtk-cairo'
1807 Build the cairo Graphics2D implementation on GTK.
1809 `--enable-java-gc=TYPE'
1810 Choose garbage collector. Defaults to `boehm' if unspecified.
1813 Do not try to compile and run a test GTK+ program.
1815 `--disable-glibtest'
1816 Do not try to compile and run a test GLIB program.
1818 `--with-libart-prefix=PFX'
1819 Prefix where libart is installed (optional).
1821 `--with-libart-exec-prefix=PFX'
1822 Exec prefix where libart is installed (optional).
1824 `--disable-libarttest'
1825 Do not try to compile and run a test libart program.
1828 Overriding `configure' test results
1829 ...................................
1831 Sometimes, it might be necessary to override the result of some
1832 `configure' test, for example in order to ease porting to a new system
1833 or work around a bug in a test. The toplevel `configure' script
1834 provides three variables for this:
1837 The contents of this variable is passed to all build `configure'
1841 The contents of this variable is passed to all host `configure'
1845 The contents of this variable is passed to all target `configure'
1849 In order to avoid shell and `make' quoting issues for complex
1850 overrides, you can pass a setting for `CONFIG_SITE' and set variables
1854 File: gccinstall.info, Node: Building, Next: Testing, Prev: Configuration, Up: Installing GCC
1859 Now that GCC is configured, you are ready to build the compiler and
1862 Some commands executed when making the compiler may fail (return a
1863 nonzero status) and be ignored by `make'. These failures, which are
1864 often due to files that were not found, are expected, and can safely be
1867 It is normal to have compiler warnings when compiling certain files.
1868 Unless you are a GCC developer, you can generally ignore these warnings
1869 unless they cause compilation to fail. Developers should attempt to fix
1870 any warnings encountered, however they can temporarily continue past
1871 warnings-as-errors by specifying the configure flag `--disable-werror'.
1873 On certain old systems, defining certain environment variables such
1874 as `CC' can interfere with the functioning of `make'.
1876 If you encounter seemingly strange errors when trying to build the
1877 compiler in a directory other than the source directory, it could be
1878 because you have previously configured the compiler in the source
1879 directory. Make sure you have done all the necessary preparations.
1881 If you build GCC on a BSD system using a directory stored in an old
1882 System V file system, problems may occur in running `fixincludes' if the
1883 System V file system doesn't support symbolic links. These problems
1884 result in a failure to fix the declaration of `size_t' in
1885 `sys/types.h'. If you find that `size_t' is a signed type and that
1886 type mismatches occur, this could be the cause.
1888 The solution is not to use such a directory for building GCC.
1890 Similarly, when building from SVN or snapshots, or if you modify
1891 `*.l' files, you need the Flex lexical analyzer generator installed.
1892 If you do not modify `*.l' files, releases contain the Flex-generated
1893 files and you do not need Flex installed to build them. There is still
1894 one Flex-based lexical analyzer (part of the build machinery, not of
1895 GCC itself) that is used even if you only build the C front end.
1897 When building from SVN or snapshots, or if you modify Texinfo
1898 documentation, you need version 4.7 or later of Texinfo installed if you
1899 want Info documentation to be regenerated. Releases contain Info
1900 documentation pre-built for the unmodified documentation in the release.
1902 5.1 Building a native compiler
1903 ==============================
1905 For a native build, the default configuration is to perform a 3-stage
1906 bootstrap of the compiler when `make' is invoked. This will build the
1907 entire GCC system and ensure that it compiles itself correctly. It can
1908 be disabled with the `--disable-bootstrap' parameter to `configure',
1909 but bootstrapping is suggested because the compiler will be tested more
1910 completely and could also have better performance.
1912 The bootstrapping process will complete the following steps:
1914 * Build tools necessary to build the compiler.
1916 * Perform a 3-stage bootstrap of the compiler. This includes
1917 building three times the target tools for use by the compiler such
1918 as binutils (bfd, binutils, gas, gprof, ld, and opcodes) if they
1919 have been individually linked or moved into the top level GCC
1920 source tree before configuring.
1922 * Perform a comparison test of the stage2 and stage3 compilers.
1924 * Build runtime libraries using the stage3 compiler from the
1928 If you are short on disk space you might consider `make
1929 bootstrap-lean' instead. The sequence of compilation is the same
1930 described above, but object files from the stage1 and stage2 of the
1931 3-stage bootstrap of the compiler are deleted as soon as they are no
1934 If you wish to use non-default GCC flags when compiling the stage2
1935 and stage3 compilers, set `BOOT_CFLAGS' on the command line when doing
1936 `make'. For example, if you want to save additional space during the
1937 bootstrap and in the final installation as well, you can build the
1938 compiler binaries without debugging information as in the following
1939 example. This will save roughly 40% of disk space both for the
1940 bootstrap and the final installation. (Libraries will still contain
1941 debugging information.)
1943 make BOOT_CFLAGS='-O' bootstrap
1945 You can place non-default optimization flags into `BOOT_CFLAGS'; they
1946 are less well tested here than the default of `-g -O2', but should
1947 still work. In a few cases, you may find that you need to specify
1948 special flags such as `-msoft-float' here to complete the bootstrap; or,
1949 if the native compiler miscompiles the stage1 compiler, you may need to
1950 work around this, by choosing `BOOT_CFLAGS' to avoid the parts of the
1951 stage1 compiler that were miscompiled, or by using `make bootstrap4' to
1952 increase the number of stages of bootstrap.
1954 `BOOT_CFLAGS' does not apply to bootstrapped target libraries.
1955 Since these are always compiled with the compiler currently being
1956 bootstrapped, you can use `CFLAGS_FOR_TARGET' to modify their
1957 compilation flags, as for non-bootstrapped target libraries. Again, if
1958 the native compiler miscompiles the stage1 compiler, you may need to
1959 work around this by avoiding non-working parts of the stage1 compiler.
1960 Use `STAGE1_TFLAGS' to this end.
1962 If you used the flag `--enable-languages=...' to restrict the
1963 compilers to be built, only those you've actually enabled will be
1964 built. This will of course only build those runtime libraries, for
1965 which the particular compiler has been built. Please note, that
1966 re-defining `LANGUAGES' when calling `make' *does not* work anymore!
1968 If the comparison of stage2 and stage3 fails, this normally indicates
1969 that the stage2 compiler has compiled GCC incorrectly, and is therefore
1970 a potentially serious bug which you should investigate and report. (On
1971 a few systems, meaningful comparison of object files is impossible; they
1972 always appear "different". If you encounter this problem, you will
1973 need to disable comparison in the `Makefile'.)
1975 If you do not want to bootstrap your compiler, you can configure with
1976 `--disable-bootstrap'. In particular cases, you may want to bootstrap
1977 your compiler even if the target system is not the same as the one you
1978 are building on: for example, you could build a
1979 `powerpc-unknown-linux-gnu' toolchain on a
1980 `powerpc64-unknown-linux-gnu' host. In this case, pass
1981 `--enable-bootstrap' to the configure script.
1983 `BUILD_CONFIG' can be used to bring in additional customization to
1984 the build. It can be set to a whitespace-separated list of names. For
1985 each such `NAME', top-level `config/`NAME'.mk' will be included by the
1986 top-level `Makefile', bringing in any settings it contains. The
1987 default `BUILD_CONFIG' can be set using the configure option
1988 `--with-build-config=`NAME'...'. Some examples of supported build
1992 Removes any `-O'-started option from `BOOT_CFLAGS', and adds `-O1'
1993 to it. `BUILD_CONFIG=bootstrap-O1' is equivalent to
1994 `BOOT_CFLAGS='-g -O1''.
1997 Analogous to `bootstrap-O1'.
2000 Enables Link-Time Optimization for host tools during bootstrapping.
2001 `BUILD_CONFIG=bootstrap-lto' is equivalent to adding `-flto' to
2005 Verifies that the compiler generates the same executable code,
2006 whether or not it is asked to emit debug information. To this
2007 end, this option builds stage2 host programs without debug
2008 information, and uses `contrib/compare-debug' to compare them with
2009 the stripped stage3 object files. If `BOOT_CFLAGS' is overridden
2010 so as to not enable debug information, stage2 will have it, and
2011 stage3 won't. This option is enabled by default when GCC
2012 bootstrapping is enabled, if `strip' can turn object files
2013 compiled with and without debug info into identical object files.
2014 In addition to better test coverage, this option makes default
2015 bootstraps faster and leaner.
2017 `bootstrap-debug-big'
2018 Rather than comparing stripped object files, as in
2019 `bootstrap-debug', this option saves internal compiler dumps
2020 during stage2 and stage3 and compares them as well, which helps
2021 catch additional potential problems, but at a great cost in terms
2022 of disk space. It can be specified in addition to
2025 `bootstrap-debug-lean'
2026 This option saves disk space compared with `bootstrap-debug-big',
2027 but at the expense of some recompilation. Instead of saving the
2028 dumps of stage2 and stage3 until the final compare, it uses
2029 `-fcompare-debug' to generate, compare and remove the dumps during
2030 stage3, repeating the compilation that already took place in
2031 stage2, whose dumps were not saved.
2033 `bootstrap-debug-lib'
2034 This option tests executable code invariance over debug information
2035 generation on target libraries, just like `bootstrap-debug-lean'
2036 tests it on host programs. It builds stage3 libraries with
2037 `-fcompare-debug', and it can be used along with any of the
2038 `bootstrap-debug' options above.
2040 There aren't `-lean' or `-big' counterparts to this option because
2041 most libraries are only build in stage3, so bootstrap compares
2042 would not get significant coverage. Moreover, the few libraries
2043 built in stage2 are used in stage3 host programs, so we wouldn't
2044 want to compile stage2 libraries with different options for
2045 comparison purposes.
2047 `bootstrap-debug-ckovw'
2048 Arranges for error messages to be issued if the compiler built on
2049 any stage is run without the option `-fcompare-debug'. This is
2050 useful to verify the full `-fcompare-debug' testing coverage. It
2051 must be used along with `bootstrap-debug-lean' and
2052 `bootstrap-debug-lib'.
2055 Arranges for the run time of each program started by the GCC
2056 driver, built in any stage, to be logged to `time.log', in the top
2057 level of the build tree.
2060 5.2 Building a cross compiler
2061 =============================
2063 When building a cross compiler, it is not generally possible to do a
2064 3-stage bootstrap of the compiler. This makes for an interesting
2065 problem as parts of GCC can only be built with GCC.
2067 To build a cross compiler, we recommend first building and
2068 installing a native compiler. You can then use the native GCC compiler
2069 to build the cross compiler. The installed native compiler needs to be
2070 GCC version 2.95 or later.
2072 If the cross compiler is to be built with support for the Java
2073 programming language and the ability to compile .java source files is
2074 desired, the installed native compiler used to build the cross compiler
2075 needs to be the same GCC version as the cross compiler. In addition
2076 the cross compiler needs to be configured with `--with-ecj-jar=...'.
2078 Assuming you have already installed a native copy of GCC and
2079 configured your cross compiler, issue the command `make', which
2080 performs the following steps:
2082 * Build host tools necessary to build the compiler.
2084 * Build target tools for use by the compiler such as binutils (bfd,
2085 binutils, gas, gprof, ld, and opcodes) if they have been
2086 individually linked or moved into the top level GCC source tree
2089 * Build the compiler (single stage only).
2091 * Build runtime libraries using the compiler from the previous step.
2093 Note that if an error occurs in any step the make process will exit.
2095 If you are not building GNU binutils in the same source tree as GCC,
2096 you will need a cross-assembler and cross-linker installed before
2097 configuring GCC. Put them in the directory `PREFIX/TARGET/bin'. Here
2098 is a table of the tools you should put in this directory:
2101 This should be the cross-assembler.
2104 This should be the cross-linker.
2107 This should be the cross-archiver: a program which can manipulate
2108 archive files (linker libraries) in the target machine's format.
2111 This should be a program to construct a symbol table in an archive
2114 The installation of GCC will find these programs in that directory,
2115 and copy or link them to the proper place to for the cross-compiler to
2116 find them when run later.
2118 The easiest way to provide these files is to build the Binutils
2119 package. Configure it with the same `--host' and `--target' options
2120 that you use for configuring GCC, then build and install them. They
2121 install their executables automatically into the proper directory.
2122 Alas, they do not support all the targets that GCC supports.
2124 If you are not building a C library in the same source tree as GCC,
2125 you should also provide the target libraries and headers before
2126 configuring GCC, specifying the directories with `--with-sysroot' or
2127 `--with-headers' and `--with-libs'. Many targets also require "start
2128 files" such as `crt0.o' and `crtn.o' which are linked into each
2129 executable. There may be several alternatives for `crt0.o', for use
2130 with profiling or other compilation options. Check your target's
2131 definition of `STARTFILE_SPEC' to find out what start files it uses.
2133 5.3 Building in parallel
2134 ========================
2136 GNU Make 3.80 and above, which is necessary to build GCC, support
2137 building in parallel. To activate this, you can use `make -j 2'
2138 instead of `make'. You can also specify a bigger number, and in most
2139 cases using a value greater than the number of processors in your
2140 machine will result in fewer and shorter I/O latency hits, thus
2141 improving overall throughput; this is especially true for slow drives
2142 and network filesystems.
2144 5.4 Building the Ada compiler
2145 =============================
2147 In order to build GNAT, the Ada compiler, you need a working GNAT
2148 compiler (GCC version 4.0 or later). This includes GNAT tools such as
2149 `gnatmake' and `gnatlink', since the Ada front end is written in Ada and
2150 uses some GNAT-specific extensions.
2152 In order to build a cross compiler, it is suggested to install the
2153 new compiler as native first, and then use it to build the cross
2156 `configure' does not test whether the GNAT installation works and
2157 has a sufficiently recent version; if too old a GNAT version is
2158 installed, the build will fail unless `--enable-languages' is used to
2159 disable building the Ada front end.
2161 `ADA_INCLUDE_PATH' and `ADA_OBJECT_PATH' environment variables must
2162 not be set when building the Ada compiler, the Ada tools, or the Ada
2163 runtime libraries. You can check that your build environment is clean
2164 by verifying that `gnatls -v' lists only one explicit path in each
2167 5.5 Building with profile feedback
2168 ==================================
2170 It is possible to use profile feedback to optimize the compiler itself.
2171 This should result in a faster compiler binary. Experiments done on
2172 x86 using gcc 3.3 showed approximately 7 percent speedup on compiling C
2173 programs. To bootstrap the compiler with profile feedback, use `make
2176 When `make profiledbootstrap' is run, it will first build a `stage1'
2177 compiler. This compiler is used to build a `stageprofile' compiler
2178 instrumented to collect execution counts of instruction and branch
2179 probabilities. Then runtime libraries are compiled with profile
2180 collected. Finally a `stagefeedback' compiler is built using the
2181 information collected.
2183 Unlike standard bootstrap, several additional restrictions apply.
2184 The compiler used to build `stage1' needs to support a 64-bit integral
2185 type. It is recommended to only use GCC for this. Also parallel make
2186 is currently not supported since collisions in profile collecting may
2190 File: gccinstall.info, Node: Testing, Next: Final install, Prev: Building, Up: Installing GCC
2192 6 Installing GCC: Testing
2193 *************************
2195 Before you install GCC, we encourage you to run the testsuites and to
2196 compare your results with results from a similar configuration that have
2197 been submitted to the gcc-testresults mailing list. Some of these
2198 archived results are linked from the build status lists at
2199 `http://gcc.gnu.org/buildstat.html', although not everyone who reports
2200 a successful build runs the testsuites and submits the results. This
2201 step is optional and may require you to download additional software,
2202 but it can give you confidence in your new GCC installation or point out
2203 problems before you install and start using your new GCC.
2205 First, you must have downloaded the testsuites. These are part of
2206 the full distribution, but if you downloaded the "core" compiler plus
2207 any front ends, you must download the testsuites separately.
2209 Second, you must have the testing tools installed. This includes
2210 DejaGnu, Tcl, and Expect; the DejaGnu site has links to these.
2212 If the directories where `runtest' and `expect' were installed are
2213 not in the `PATH', you may need to set the following environment
2214 variables appropriately, as in the following example (which assumes
2215 that DejaGnu has been installed under `/usr/local'):
2217 TCL_LIBRARY = /usr/local/share/tcl8.0
2218 DEJAGNULIBS = /usr/local/share/dejagnu
2220 (On systems such as Cygwin, these paths are required to be actual
2221 paths, not mounts or links; presumably this is due to some lack of
2222 portability in the DejaGnu code.)
2224 Finally, you can run the testsuite (which may take a long time):
2225 cd OBJDIR; make -k check
2227 This will test various components of GCC, such as compiler front
2228 ends and runtime libraries. While running the testsuite, DejaGnu might
2229 emit some harmless messages resembling `WARNING: Couldn't find the
2230 global config file.' or `WARNING: Couldn't find tool init file' that
2233 If you are testing a cross-compiler, you may want to run the
2234 testsuite on a simulator as described at
2235 `http://gcc.gnu.org/simtest-howto.html'.
2237 6.1 How can you run the testsuite on selected tests?
2238 ====================================================
2240 In order to run sets of tests selectively, there are targets `make
2241 check-gcc' and language specific `make check-c', `make check-c++',
2242 `make check-fortran', `make check-java', `make check-ada', `make
2243 check-objc', `make check-obj-c++', `make check-lto' in the `gcc'
2244 subdirectory of the object directory. You can also just run `make
2245 check' in a subdirectory of the object directory.
2247 A more selective way to just run all `gcc' execute tests in the
2250 make check-gcc RUNTESTFLAGS="execute.exp OTHER-OPTIONS"
2252 Likewise, in order to run only the `g++' "old-deja" tests in the
2253 testsuite with filenames matching `9805*', you would use
2255 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* OTHER-OPTIONS"
2257 The `*.exp' files are located in the testsuite directories of the GCC
2258 source, the most important ones being `compile.exp', `execute.exp',
2259 `dg.exp' and `old-deja.exp'. To get a list of the possible `*.exp'
2260 files, pipe the output of `make check' into a file and look at the
2261 `Running ... .exp' lines.
2263 6.2 Passing options and running multiple testsuites
2264 ===================================================
2266 You can pass multiple options to the testsuite using the
2267 `--target_board' option of DejaGNU, either passed as part of
2268 `RUNTESTFLAGS', or directly to `runtest' if you prefer to work outside
2269 the makefiles. For example,
2271 make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants"
2273 will run the standard `g++' testsuites ("unix" is the target name
2274 for a standard native testsuite situation), passing `-O3
2275 -fmerge-constants' to the compiler on every test, i.e., slashes
2278 You can run the testsuites multiple times using combinations of
2279 options with a syntax similar to the brace expansion of popular shells:
2281 ..."--target_board=arm-sim\{-mhard-float,-msoft-float\}\{-O1,-O2,-O3,\}"
2283 (Note the empty option caused by the trailing comma in the final
2284 group.) The following will run each testsuite eight times using the
2285 `arm-sim' target, as if you had specified all possible combinations
2288 --target_board=arm-sim/-mhard-float/-O1
2289 --target_board=arm-sim/-mhard-float/-O2
2290 --target_board=arm-sim/-mhard-float/-O3
2291 --target_board=arm-sim/-mhard-float
2292 --target_board=arm-sim/-msoft-float/-O1
2293 --target_board=arm-sim/-msoft-float/-O2
2294 --target_board=arm-sim/-msoft-float/-O3
2295 --target_board=arm-sim/-msoft-float
2297 They can be combined as many times as you wish, in arbitrary ways.
2300 ..."--target_board=unix/-Wextra\{-O3,-fno-strength\}\{-fomit-frame,\}"
2302 will generate four combinations, all involving `-Wextra'.
2304 The disadvantage to this method is that the testsuites are run in
2305 serial, which is a waste on multiprocessor systems. For users with GNU
2306 Make and a shell which performs brace expansion, you can run the
2307 testsuites in parallel by having the shell perform the combinations and
2308 `make' do the parallel runs. Instead of using `--target_board', use a
2309 special makefile target:
2311 make -jN check-TESTSUITE//TEST-TARGET/OPTION1/OPTION2/...
2315 make -j3 check-gcc//sh-hms-sim/{-m1,-m2,-m3,-m3e,-m4}/{,-nofpu}
2317 will run three concurrent "make-gcc" testsuites, eventually testing
2318 all ten combinations as described above. Note that this is currently
2319 only supported in the `gcc' subdirectory. (To see how this works, try
2320 typing `echo' before the example given here.)
2322 6.3 Additional testing for Java Class Libraries
2323 ===============================================
2325 The Java runtime tests can be executed via `make check' in the
2326 `TARGET/libjava/testsuite' directory in the build tree.
2328 The Mauve Project provides a suite of tests for the Java Class
2329 Libraries. This suite can be run as part of libgcj testing by placing
2330 the Mauve tree within the libjava testsuite at
2331 `libjava/testsuite/libjava.mauve/mauve', or by specifying the location
2332 of that tree when invoking `make', as in `make MAUVEDIR=~/mauve check'.
2334 6.4 How to interpret test results
2335 =================================
2337 The result of running the testsuite are various `*.sum' and `*.log'
2338 files in the testsuite subdirectories. The `*.log' files contain a
2339 detailed log of the compiler invocations and the corresponding results,
2340 the `*.sum' files summarize the results. These summaries contain
2341 status codes for all tests:
2343 * PASS: the test passed as expected
2345 * XPASS: the test unexpectedly passed
2347 * FAIL: the test unexpectedly failed
2349 * XFAIL: the test failed as expected
2351 * UNSUPPORTED: the test is not supported on this platform
2353 * ERROR: the testsuite detected an error
2355 * WARNING: the testsuite detected a possible problem
2357 It is normal for some tests to report unexpected failures. At the
2358 current time the testing harness does not allow fine grained control
2359 over whether or not a test is expected to fail. This problem should be
2360 fixed in future releases.
2362 6.5 Submitting test results
2363 ===========================
2365 If you want to report the results to the GCC project, use the
2366 `contrib/test_summary' shell script. Start it in the OBJDIR with
2368 SRCDIR/contrib/test_summary -p your_commentary.txt \
2369 -m gcc-testresults@gcc.gnu.org |sh
2371 This script uses the `Mail' program to send the results, so make
2372 sure it is in your `PATH'. The file `your_commentary.txt' is prepended
2373 to the testsuite summary and should contain any special remarks you
2374 have on your results or your build environment. Please do not edit the
2375 testsuite result block or the subject line, as these messages may be
2376 automatically processed.
2379 File: gccinstall.info, Node: Final install, Prev: Testing, Up: Installing GCC
2381 7 Installing GCC: Final installation
2382 ************************************
2384 Now that GCC has been built (and optionally tested), you can install
2386 cd OBJDIR && make install
2388 We strongly recommend to install into a target directory where there
2389 is no previous version of GCC present. Also, the GNAT runtime should
2390 not be stripped, as this would break certain features of the debugger
2391 that depend on this debugging information (catching Ada exceptions for
2394 That step completes the installation of GCC; user level binaries can
2395 be found in `PREFIX/bin' where PREFIX is the value you specified with
2396 the `--prefix' to configure (or `/usr/local' by default). (If you
2397 specified `--bindir', that directory will be used instead; otherwise,
2398 if you specified `--exec-prefix', `EXEC-PREFIX/bin' will be used.)
2399 Headers for the C++ and Java libraries are installed in
2400 `PREFIX/include'; libraries in `LIBDIR' (normally `PREFIX/lib');
2401 internal parts of the compiler in `LIBDIR/gcc' and `LIBEXECDIR/gcc';
2402 documentation in info format in `INFODIR' (normally `PREFIX/info').
2404 When installing cross-compilers, GCC's executables are not only
2405 installed into `BINDIR', that is, `EXEC-PREFIX/bin', but additionally
2406 into `EXEC-PREFIX/TARGET-ALIAS/bin', if that directory exists.
2407 Typically, such "tooldirs" hold target-specific binutils, including
2408 assembler and linker.
2410 Installation into a temporary staging area or into a `chroot' jail
2411 can be achieved with the command
2413 make DESTDIR=PATH-TO-ROOTDIR install
2415 where PATH-TO-ROOTDIR is the absolute path of a directory relative to
2416 which all installation paths will be interpreted. Note that the
2417 directory specified by `DESTDIR' need not exist yet; it will be created
2420 There is a subtle point with tooldirs and `DESTDIR': If you relocate
2421 a cross-compiler installation with e.g. `DESTDIR=ROOTDIR', then the
2422 directory `ROOTDIR/EXEC-PREFIX/TARGET-ALIAS/bin' will be filled with
2423 duplicated GCC executables only if it already exists, it will not be
2424 created otherwise. This is regarded as a feature, not as a bug,
2425 because it gives slightly more control to the packagers using the
2428 You can install stripped programs and libraries with
2432 If you are bootstrapping a released version of GCC then please
2433 quickly review the build status page for your release, available from
2434 `http://gcc.gnu.org/buildstat.html'. If your system is not listed for
2435 the version of GCC that you built, send a note to <gcc@gcc.gnu.org>
2436 indicating that you successfully built and installed GCC. Include the
2437 following information:
2439 * Output from running `SRCDIR/config.guess'. Do not send that file
2440 itself, just the one-line output from running it.
2442 * The output of `gcc -v' for your newly installed `gcc'. This tells
2443 us which version of GCC you built and the options you passed to
2446 * Whether you enabled all languages or a subset of them. If you
2447 used a full distribution then this information is part of the
2448 configure options in the output of `gcc -v', but if you downloaded
2449 the "core" compiler plus additional front ends then it isn't
2450 apparent which ones you built unless you tell us about it.
2452 * If the build was for GNU/Linux, also include:
2453 * The distribution name and version (e.g., Red Hat 7.1 or
2454 Debian 2.2.3); this information should be available from
2457 * The version of the Linux kernel, available from `uname
2458 --version' or `uname -a'.
2460 * The version of glibc you used; for RPM-based systems like Red
2461 Hat, Mandrake, and SuSE type `rpm -q glibc' to get the glibc
2462 version, and on systems like Debian and Progeny use `dpkg -l
2464 For other systems, you can include similar information if you
2465 think it is relevant.
2467 * Any other information that you think would be useful to people
2468 building GCC on the same configuration. The new entry in the
2469 build status list will include a link to the archived copy of your
2472 We'd also like to know if the *note host/target specific
2473 installation notes: Specific. didn't include your host/target
2474 information or if that information is incomplete or out of date. Send
2475 a note to <gcc@gcc.gnu.org> detailing how the information should be
2478 If you find a bug, please report it following the bug reporting
2481 If you want to print the GCC manuals, do `cd OBJDIR; make dvi'. You
2482 will need to have `texi2dvi' (version at least 4.7) and TeX installed.
2483 This creates a number of `.dvi' files in subdirectories of `OBJDIR';
2484 these may be converted for printing with programs such as `dvips'.
2485 Alternately, by using `make pdf' in place of `make dvi', you can create
2486 documentation in the form of `.pdf' files; this requires `texi2pdf',
2487 which is included with Texinfo version 4.8 and later. You can also buy
2488 printed manuals from the Free Software Foundation, though such manuals
2489 may not be for the most recent version of GCC.
2491 If you would like to generate online HTML documentation, do `cd
2492 OBJDIR; make html' and HTML will be generated for the gcc manuals in
2496 File: gccinstall.info, Node: Binaries, Next: Specific, Prev: Installing GCC, Up: Top
2498 8 Installing GCC: Binaries
2499 **************************
2501 We are often asked about pre-compiled versions of GCC. While we
2502 cannot provide these for all platforms, below you'll find links to
2503 binaries for various platforms where creating them by yourself is not
2504 easy due to various reasons.
2506 Please note that we did not create these binaries, nor do we support
2507 them. If you have any problems installing them, please contact their
2511 * Bull's Freeware and Shareware Archive for AIX;
2513 * Hudson Valley Community College Open Source Software for IBM
2516 * AIX 5L and 6 Open Source Packages.
2520 * Renesas H8/300[HS]--GNU Development Tools for the Renesas
2524 * HP-UX Porting Center;
2526 * Binaries for HP-UX 11.00 at Aachen University of Technology.
2528 * SCO OpenServer/Unixware.
2530 * Solaris 2 (SPARC, Intel):
2544 * Microsoft Windows:
2545 * The Cygwin project;
2547 * The MinGW project.
2549 * The Written Word offers binaries for AIX 4.3.3, 5.1 and 5.2, IRIX
2550 6.5, Tru64 UNIX 4.0D and 5.1, GNU/Linux (i386), HP-UX 10.20,
2551 11.00, and 11.11, and Solaris/SPARC 2.5.1, 2.6, 7, 8, 9 and 10.
2553 * OpenPKG offers binaries for quite a number of platforms.
2555 * The GFortran Wiki has links to GNU Fortran binaries for several
2559 File: gccinstall.info, Node: Specific, Next: Old, Prev: Binaries, Up: Top
2561 9 Host/target specific installation notes for GCC
2562 *************************************************
2564 Please read this document carefully _before_ installing the GNU
2565 Compiler Collection on your machine.
2567 Note that this list of install notes is _not_ a list of supported
2568 hosts or targets. Not all supported hosts and targets are listed here,
2569 only the ones that require host-specific or target-specific information
2575 This section contains general configuration information for all
2576 alpha-based platforms using ELF (in particular, ignore this section for
2577 DEC OSF/1, Digital UNIX and Tru64 UNIX). In addition to reading this
2578 section, please read all other sections that match your target.
2580 We require binutils 2.11.2 or newer. Previous binutils releases had
2581 a number of problems with DWARF 2 debugging information, not the least
2582 of which is incorrect linking of shared libraries.
2587 Systems using processors that implement the DEC Alpha architecture and
2588 are running the DEC/Compaq/HP Unix (DEC OSF/1, Digital UNIX, or
2589 Compaq/HP Tru64 UNIX) operating system, for example the DEC Alpha AXP
2592 Support for Tru64 UNIX V5.1 has been obsoleted in GCC 4.7, but can
2593 still be enabled by configuring with `--enable-obsolete'. Support will
2594 be removed in GCC 4.8. As of GCC 4.6, support for Tru64 UNIX V4.0 and
2595 V5.0 has been removed. As of GCC 3.2, versions before
2596 `alpha*-dec-osf4' are no longer supported. (These are the versions
2597 which identify themselves as DEC OSF/1.)
2599 On Tru64 UNIX, virtual memory exhausted bootstrap failures may be
2600 fixed by reconfiguring Kernel Virtual Memory and Swap parameters per
2601 the `/usr/sbin/sys_check' Tuning Suggestions, or applying the patch in
2602 `http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html'. Depending on the OS
2603 version used, you need a data segment size between 512 MB and 1 GB, so
2604 simply use `ulimit -Sd unlimited'.
2606 As of GNU binutils 2.22, neither GNU `as' nor GNU `ld' are supported
2607 on Tru64 UNIX, so you must not configure GCC with `--with-gnu-as' or
2610 Cross-compilers for the Tru64 UNIX target currently do not work
2611 because the auxiliary programs `mips-tdump' and `mips-tfile' can't be
2612 compiled on anything but Tru64 UNIX.
2614 GCC writes a `.verstamp' directive to the assembler output file
2615 unless it is built as a cross-compiler. It gets the version to use from
2616 the system header file `/usr/include/stamp.h'. If you install a new
2617 version of Tru64 UNIX, you should rebuild GCC to pick up the new version
2620 GCC now supports both the native (ECOFF) debugging format used by DBX
2621 and GDB and an encapsulated STABS format for use only with GDB. See the
2622 discussion of the `--with-stabs' option of `configure' above for more
2623 information on these formats and how to select them.
2625 There is a bug in DEC's assembler that produces incorrect line
2626 numbers for ECOFF format when the `.align' directive is used. To work
2627 around this problem, GCC will not emit such alignment directives while
2628 writing ECOFF format debugging information even if optimization is
2629 being performed. Unfortunately, this has the very undesirable
2630 side-effect that code addresses when `-O' is specified are different
2631 depending on whether or not `-g' is also specified.
2633 To avoid this behavior, specify `-gstabs+' and use GDB instead of
2634 DBX. DEC is now aware of this problem with the assembler and hopes to
2635 provide a fix shortly.
2637 amd64-*-solaris2.1[0-9]*
2638 ========================
2640 This is a synonym for `x86_64-*-solaris2.1[0-9]*'.
2645 ARM-family processors. Subtargets that use the ELF object format
2646 require GNU binutils 2.13 or newer. Such subtargets include:
2647 `arm-*-netbsdelf', `arm-*-*linux-gnueabi' and `arm-*-rtemseabi'.
2652 ATMEL AVR-family micro controllers. These are used in embedded
2653 applications. There are no standard Unix configurations. *Note AVR
2654 Options: (gcc)AVR Options, for the list of supported MCU types.
2656 Use `configure --target=avr --enable-languages="c"' to configure GCC.
2658 Further installation notes and other useful information about AVR
2659 tools can also be obtained from:
2661 * http://www.nongnu.org/avr/
2663 * http://www.amelek.gda.pl/avr/
2665 We _strongly_ recommend using binutils 2.13 or newer.
2667 The following error:
2668 Error: register required
2670 indicates that you should upgrade to a newer version of the binutils.
2675 The Blackfin processor, an Analog Devices DSP. *Note Blackfin Options:
2676 (gcc)Blackfin Options,
2678 More information, and a version of binutils with support for this
2679 processor, is available at `http://blackfin.uclinux.org'
2684 The CR16 CompactRISC architecture is a 16-bit architecture. This
2685 architecture is used in embedded applications.
2687 *Note CR16 Options: (gcc)CR16 Options,
2689 Use `configure --target=cr16-elf --enable-languages=c,c++' to
2690 configure GCC for building a CR16 elf cross-compiler.
2692 Use `configure --target=cr16-uclinux --enable-languages=c,c++' to
2693 configure GCC for building a CR16 uclinux cross-compiler.
2698 CRIS is the CPU architecture in Axis Communications ETRAX
2699 system-on-a-chip series. These are used in embedded applications.
2701 *Note CRIS Options: (gcc)CRIS Options, for a list of CRIS-specific
2704 There are a few different CRIS targets:
2706 Mainly for monolithic embedded systems. Includes a multilib for
2707 the `v10' core used in `ETRAX 100 LX'.
2709 `cris-axis-linux-gnu'
2710 A GNU/Linux port for the CRIS architecture, currently targeting
2711 `ETRAX 100 LX' by default.
2713 For `cris-axis-elf' you need binutils 2.11 or newer. For
2714 `cris-axis-linux-gnu' you need binutils 2.12 or newer.
2716 Pre-packaged tools can be obtained from
2717 `ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/'. More
2718 information about this platform is available at
2719 `http://developer.axis.com/'.
2724 Please have a look at the binaries page.
2726 You cannot install GCC by itself on MSDOS; it will not compile under
2727 any MSDOS compiler except itself. You need to get the complete
2728 compilation package DJGPP, which includes binaries as well as sources,
2729 and includes all the necessary compilation tools and libraries.
2734 Adapteva Epiphany. This configuration is intended for embedded systems.
2739 Support for FreeBSD 1 was discontinued in GCC 3.2. Support for FreeBSD
2740 2 (and any mutant a.out variants of FreeBSD 3) was discontinued in GCC
2743 In order to better utilize FreeBSD base system functionality and
2744 match the configuration of the system compiler, GCC 4.5 and above as
2745 well as GCC 4.4 past 2010-06-20 leverage SSP support in libc (which is
2746 present on FreeBSD 7 or later) and the use of `__cxa_atexit' by default
2747 (on FreeBSD 6 or later). The use of `dl_iterate_phdr' inside
2748 `libgcc_s.so.1' and boehm-gc (on FreeBSD 7 or later) is enabled by GCC
2751 We support FreeBSD using the ELF file format with DWARF 2 debugging
2752 for all CPU architectures. You may use `-gstabs' instead of `-g', if
2753 you really want the old debugging format. There are no known issues
2754 with mixing object files and libraries with different debugging
2755 formats. Otherwise, this release of GCC should now match more of the
2756 configuration used in the stock FreeBSD configuration of GCC. In
2757 particular, `--enable-threads' is now configured by default. However,
2758 as a general user, do not attempt to replace the system compiler with
2759 this release. Known to bootstrap and check with good results on
2760 FreeBSD 7.2-STABLE. In the past, known to bootstrap and check with
2761 good results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4, 4.5, 4.8, 4.9 and
2764 The version of binutils installed in `/usr/bin' probably works with
2765 this release of GCC. Bootstrapping against the latest GNU binutils
2766 and/or the version found in `/usr/ports/devel/binutils' has been known
2767 to enable additional features and improve overall testsuite results.
2768 However, it is currently known that boehm-gc (which itself is required
2769 for java) may not configure properly on FreeBSD prior to the FreeBSD
2770 7.0 release with GNU binutils after 2.16.1.
2775 Renesas H8/300 series of processors.
2777 Please have a look at the binaries page.
2779 The calling convention and structure layout has changed in release
2780 2.6. All code must be recompiled. The calling convention now passes
2781 the first three arguments in function calls in registers. Structures
2782 are no longer a multiple of 2 bytes.
2787 Support for HP-UX version 9 and older was discontinued in GCC 3.4.
2789 We require using gas/binutils on all hppa platforms. Version 2.19 or
2790 later is recommended.
2792 It may be helpful to configure GCC with the `--with-gnu-as' and
2793 `--with-as=...' options to ensure that GCC can find GAS.
2795 The HP assembler should not be used with GCC. It is rarely tested
2796 and may not work. It shouldn't be used with any languages other than C
2797 due to its many limitations.
2799 Specifically, `-g' does not work (HP-UX uses a peculiar debugging
2800 format which GCC does not know about). It also inserts timestamps into
2801 each object file it creates, causing the 3-stage comparison test to
2802 fail during a bootstrap. You should be able to continue by saying
2803 `make all-host all-target' after getting the failure from `make'.
2805 Various GCC features are not supported. For example, it does not
2806 support weak symbols or alias definitions. As a result, explicit
2807 template instantiations are required when using C++. This makes it
2808 difficult if not impossible to build many C++ applications.
2810 There are two default scheduling models for instructions. These are
2811 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
2812 architecture specified for the target machine when configuring.
2813 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when the
2814 target is a `hppa1*' machine.
2816 The PROCESSOR_8000 model is not well suited to older processors.
2817 Thus, it is important to completely specify the machine architecture
2818 when configuring if you want a model other than PROCESSOR_8000. The
2819 macro TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
2820 default scheduling model is desired.
2822 As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
2823 through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
2824 This namespace change might cause problems when bootstrapping with an
2825 earlier version of GCC or the HP compiler as essentially the same
2826 namespace is required for an entire build. This problem can be avoided
2827 in a number of ways. With HP cc, `UNIX_STD' can be set to `95' or
2828 `98'. Another way is to add an appropriate set of predefines to `CC'.
2829 The description for the `munix=' option contains a list of the
2830 predefines used with each standard.
2832 More specific information to `hppa*-hp-hpux*' targets follows.
2837 For hpux10.20, we _highly_ recommend you pick up the latest sed patch
2838 `PHCO_19798' from HP.
2840 The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces
2841 are used for one-only code and data. This resolves many of the previous
2842 problems in using C++ on this target. However, the ABI is not
2843 compatible with the one implemented under HP-UX 11 using secondary
2849 GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
2850 be used to compile GCC 3.0 and up.
2852 The libffi and libjava libraries haven't been ported to 64-bit HP-UX
2855 Refer to binaries for information about obtaining precompiled GCC
2856 binaries for HP-UX. Precompiled binaries must be obtained to build the
2857 Ada language as it can't be bootstrapped using C. Ada is only
2858 available for the 32-bit PA-RISC runtime.
2860 Starting with GCC 3.4 an ISO C compiler is required to bootstrap.
2861 The bundled compiler supports only traditional C; you will need either
2862 HP's unbundled compiler, or a binary distribution of GCC.
2864 It is possible to build GCC 3.3 starting with the bundled HP
2865 compiler, but the process requires several steps. GCC 3.3 can then be
2866 used to build later versions. The fastjar program contains ISO C code
2867 and can't be built with the HP bundled compiler. This problem can be
2868 avoided by not building the Java language. For example, use the
2869 `--enable-languages="c,c++,f77,objc"' option in your configure command.
2871 There are several possible approaches to building the distribution.
2872 Binutils can be built first using the HP tools. Then, the GCC
2873 distribution can be built. The second approach is to build GCC first
2874 using the HP tools, then build binutils, then rebuild GCC. There have
2875 been problems with various binary distributions, so it is best not to
2876 start from a binary distribution.
2878 On 64-bit capable systems, there are two distinct targets. Different
2879 installation prefixes must be used if both are to be installed on the
2880 same system. The `hppa[1-2]*-hp-hpux11*' target generates code for the
2881 32-bit PA-RISC runtime architecture and uses the HP linker. The
2882 `hppa64-hp-hpux11*' target generates 64-bit code for the PA-RISC 2.0
2885 The script config.guess now selects the target type based on the
2886 compiler detected during configuration. You must define `PATH' or `CC'
2887 so that configure finds an appropriate compiler for the initial
2888 bootstrap. When `CC' is used, the definition should contain the
2889 options that are needed whenever `CC' is used.
2891 Specifically, options that determine the runtime architecture must be
2892 in `CC' to correctly select the target for the build. It is also
2893 convenient to place many other compiler options in `CC'. For example,
2894 `CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"' can
2895 be used to bootstrap the GCC 3.3 branch with the HP compiler in 64-bit
2896 K&R/bundled mode. The `+DA2.0W' option will result in the automatic
2897 selection of the `hppa64-hp-hpux11*' target. The macro definition
2898 table of cpp needs to be increased for a successful build with the HP
2899 compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to be defined when
2900 building with the bundled compiler, or when using the `-Ac' option.
2901 These defines aren't necessary with `-Ae'.
2903 It is best to explicitly configure the `hppa64-hp-hpux11*' target
2904 with the `--with-ld=...' option. This overrides the standard search
2905 for ld. The two linkers supported on this target require different
2906 commands. The default linker is determined during configuration. As a
2907 result, it's not possible to switch linkers in the middle of a GCC
2908 build. This has been reported to sometimes occur in unified builds of
2911 A recent linker patch must be installed for the correct operation of
2912 GCC 3.3 and later. `PHSS_26559' and `PHSS_24304' are the oldest linker
2913 patches that are known to work. They are for HP-UX 11.00 and 11.11,
2914 respectively. `PHSS_24303', the companion to `PHSS_24304', might be
2915 usable but it hasn't been tested. These patches have been superseded.
2916 Consult the HP patch database to obtain the currently recommended
2917 linker patch for your system.
2919 The patches are necessary for the support of weak symbols on the
2920 32-bit port, and for the running of initializers and finalizers. Weak
2921 symbols are implemented using SOM secondary definition symbols. Prior
2922 to HP-UX 11, there are bugs in the linker support for secondary symbols.
2923 The patches correct a problem of linker core dumps creating shared
2924 libraries containing secondary symbols, as well as various other
2925 linking issues involving secondary symbols.
2927 GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
2928 run initializers and finalizers on the 64-bit port. The 32-bit port
2929 uses the linker `+init' and `+fini' options for the same purpose. The
2930 patches correct various problems with the +init/+fini options,
2931 including program core dumps. Binutils 2.14 corrects a problem on the
2932 64-bit port resulting from HP's non-standard use of the .init and .fini
2933 sections for array initializers and finalizers.
2935 Although the HP and GNU linkers are both supported for the
2936 `hppa64-hp-hpux11*' target, it is strongly recommended that the HP
2937 linker be used for link editing on this target.
2939 At this time, the GNU linker does not support the creation of long
2940 branch stubs. As a result, it can't successfully link binaries
2941 containing branch offsets larger than 8 megabytes. In addition, there
2942 are problems linking shared libraries, linking executables with
2943 `-static', and with dwarf2 unwind and exception support. It also
2944 doesn't provide stubs for internal calls to global functions in shared
2945 libraries, so these calls can't be overloaded.
2947 The HP dynamic loader does not support GNU symbol versioning, so
2948 symbol versioning is not supported. It may be necessary to disable
2949 symbol versioning with `--disable-symvers' when using GNU ld.
2951 POSIX threads are the default. The optional DCE thread library is
2952 not supported, so `--enable-threads=dce' does not work.
2957 Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present
2958 in glibc 2.2.5 and later. More information is available in the
2959 libstdc++-v3 documentation.
2964 As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
2965 See bug 10877 for more information.
2967 If you receive Signal 11 errors when building on GNU/Linux, then it
2968 is possible you have a hardware problem. Further information on this
2969 can be found on www.bitwizard.nl.
2971 i?86-*-solaris2.[89]
2972 ====================
2974 The Sun assembler in Solaris 8 and 9 has several bugs and limitations.
2975 While GCC works around them, several features are missing, so it is
2976 recommended to use the GNU assembler instead. There is no bundled
2977 version, but the current version, from GNU binutils 2.22, is known to
2980 Solaris 2/x86 doesn't support the execution of SSE/SSE2 instructions
2981 before Solaris 9 4/04, even if the CPU supports them. Programs will
2982 receive `SIGILL' if they try. The fix is available both in Solaris 9
2983 Update 6 and kernel patch 112234-12 or newer. There is no
2984 corresponding patch for Solaris 8. To avoid this problem, `-march'
2985 defaults to `pentiumpro' on Solaris 8 and 9. If you have the patch
2986 installed, you can configure GCC with an appropriate `--with-arch'
2987 option, but need GNU `as' for SSE2 support.
2992 Use this for Solaris 10 or later on x86 and x86-64 systems. Starting
2993 with GCC 4.7, there is also a 64-bit `amd64-*-solaris2.1[0-9]*' or
2994 `x86_64-*-solaris2.1[0-9]*' configuration that corresponds to
2995 `sparcv9-sun-solaris2*'.
2997 It is recommended that you configure GCC to use the GNU assembler, in
2998 `/usr/sfw/bin/gas'. The versions included in Solaris 10, from GNU
2999 binutils 2.15, and Solaris 11, from GNU binutils 2.19, work fine,
3000 although the current version, from GNU binutils 2.22, is known to work,
3001 too. Recent versions of the Sun assembler in `/usr/ccs/bin/as' work
3002 almost as well, though.
3004 For linking, the Sun linker, is preferred. If you want to use the
3005 GNU linker instead, which is available in `/usr/sfw/bin/gld', note that
3006 due to a packaging bug the version in Solaris 10, from GNU binutils
3007 2.15, cannot be used, while the version in Solaris 11, from GNU binutils
3008 2.19, works, as does the latest version, from GNU binutils 2.22.
3010 To use GNU `as', configure with the options `--with-gnu-as
3011 --with-as=/usr/sfw/bin/gas'. It may be necessary to configure with
3012 `--without-gnu-ld --with-ld=/usr/ccs/bin/ld' to guarantee use of Sun
3018 IA-64 processor (also known as IPF, or Itanium Processor Family)
3021 If you are using the installed system libunwind library with
3022 `--with-system-libunwind', then you must use libunwind 0.98 or later.
3024 None of the following versions of GCC has an ABI that is compatible
3025 with any of the other versions in this list, with the exception that
3026 Red Hat 2.96 and Trillian 000171 are compatible with each other: 3.1,
3027 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717. This primarily
3028 affects C++ programs and programs that create shared libraries. GCC
3029 3.1 or later is recommended for compiling linux, the kernel. As of
3030 version 3.1 GCC is believed to be fully ABI compliant, and hence no
3031 more major ABI changes are expected.
3036 Building GCC on this target requires the GNU Assembler. The bundled HP
3037 assembler will not work. To prevent GCC from using the wrong assembler,
3038 the option `--with-gnu-as' may be necessary.
3040 The GCC libunwind library has not been ported to HPUX. This means
3041 that for GCC versions 3.2.3 and earlier, `--enable-libunwind-exceptions'
3042 is required to build GCC. For GCC 3.3 and later, this is the default.
3043 For gcc 3.4.3 and later, `--enable-libunwind-exceptions' is removed and
3044 the system libunwind library will always be used.
3049 Support for AIX version 3 and older was discontinued in GCC 3.4.
3050 Support for AIX version 4.2 and older was discontinued in GCC 4.5.
3052 "out of memory" bootstrap failures may indicate a problem with
3053 process resource limits (ulimit). Hard limits are configured in the
3054 `/etc/security/limits' system configuration file.
3056 GCC can bootstrap with recent versions of IBM XLC, but bootstrapping
3057 with an earlier release of GCC is recommended. Bootstrapping with XLC
3058 requires a larger data segment, which can be enabled through the
3059 LDR_CNTRL environment variable, e.g.,
3061 % LDR_CNTRL=MAXDATA=0x50000000
3064 One can start with a pre-compiled version of GCC to build from
3065 sources. One may delete GCC's "fixed" header files when starting with
3066 a version of GCC built for an earlier release of AIX.
3068 To speed up the configuration phases of bootstrapping and installing
3069 GCC, one may use GNU Bash instead of AIX `/bin/sh', e.g.,
3071 % CONFIG_SHELL=/opt/freeware/bin/bash
3072 % export CONFIG_SHELL
3074 and then proceed as described in the build instructions, where we
3075 strongly recommend specifying an absolute path to invoke
3078 Because GCC on AIX is built as a 32-bit executable by default,
3079 (although it can generate 64-bit programs) the GMP and MPFR libraries
3080 required by gfortran must be 32-bit libraries. Building GMP and MPFR
3081 as static archive libraries works better than shared libraries.
3083 Errors involving `alloca' when building GCC generally are due to an
3084 incorrect definition of `CC' in the Makefile or mixing files compiled
3085 with the native C compiler and GCC. During the stage1 phase of the
3086 build, the native AIX compiler *must* be invoked as `cc' (not `xlc').
3087 Once `configure' has been informed of `xlc', one needs to use `make
3088 distclean' to remove the configure cache files and ensure that `CC'
3089 environment variable does not provide a definition that will confuse
3090 `configure'. If this error occurs during stage2 or later, then the
3091 problem most likely is the version of Make (see above).
3093 The native `as' and `ld' are recommended for bootstrapping on AIX.
3094 The GNU Assembler, GNU Linker, and GNU Binutils version 2.20 is
3095 required to bootstrap on AIX 5. The native AIX tools do interoperate
3098 AIX 5.3 TL10, AIX 6.1 TL05 and AIX 7.1 TL00 introduced an AIX
3099 assembler change that sometimes produces corrupt assembly files causing
3100 AIX linker errors. The bug breaks GCC bootstrap on AIX and can cause
3101 compilation failures with existing GCC installations. An AIX iFix for
3102 AIX 5.3 is available (APAR IZ98385 for AIX 5.3 TL10, APAR IZ98477 for
3103 AIX 5.3 TL11 and IZ98134 for AIX 5.3 TL12). Fixes for AIX 6.1 (APAR
3104 IZ98732 for AIX 6.1 TL05 and APAR IZ98861 for AIX 6.1 TL06) and AIX 7.1
3105 are in verification and packaging phases.
3107 Building `libstdc++.a' requires a fix for an AIX Assembler bug APAR
3108 IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a fix
3109 for another AIX Assembler bug and a co-dependent AIX Archiver fix
3110 referenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1)
3112 `libstdc++' in GCC 3.4 increments the major version number of the
3113 shared object and GCC installation places the `libstdc++.a' shared
3114 library in a common location which will overwrite the and GCC 3.3
3115 version of the shared library. Applications either need to be
3116 re-linked against the new shared library or the GCC 3.1 and GCC 3.3
3117 versions of the `libstdc++' shared object needs to be available to the
3118 AIX runtime loader. The GCC 3.1 `libstdc++.so.4', if present, and GCC
3119 3.3 `libstdc++.so.5' shared objects can be installed for runtime
3120 dynamic loading using the following steps to set the `F_LOADONLY' flag
3121 in the shared object for _each_ multilib `libstdc++.a' installed:
3123 Extract the shared objects from the currently installed
3124 `libstdc++.a' archive:
3125 % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
3127 Enable the `F_LOADONLY' flag so that the shared object will be
3128 available for runtime dynamic loading, but not linking:
3129 % strip -e libstdc++.so.4 libstdc++.so.5
3131 Archive the runtime-only shared object in the GCC 3.4 `libstdc++.a'
3133 % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
3135 Linking executables and shared libraries may produce warnings of
3136 duplicate symbols. The assembly files generated by GCC for AIX always
3137 have included multiple symbol definitions for certain global variable
3138 and function declarations in the original program. The warnings should
3139 not prevent the linker from producing a correct library or runnable
3142 AIX 4.3 utilizes a "large format" archive to support both 32-bit and
3143 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
3144 to parse archive libraries did not handle the new format correctly.
3145 These routines are used by GCC and result in error messages during
3146 linking such as "not a COFF file". The version of the routines shipped
3147 with AIX 4.3.1 should work for a 32-bit environment. The `-g' option
3148 of the archive command may be used to create archives of 32-bit objects
3149 using the original "small format". A correct version of the routines
3150 is shipped with AIX 4.3.2 and above.
3152 Some versions of the AIX binder (linker) can fail with a relocation
3153 overflow severe error when the `-bbigtoc' option is used to link
3154 GCC-produced object files into an executable that overflows the TOC. A
3155 fix for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC)
3156 is available from IBM Customer Support and from its
3157 techsupport.services.ibm.com website as PTF U455193.
3159 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump
3160 core with a segmentation fault when invoked by any version of GCC. A
3161 fix for APAR IX87327 is available from IBM Customer Support and from its
3162 techsupport.services.ibm.com website as PTF U461879. This fix is
3163 incorporated in AIX 4.3.3 and above.
3165 The initial assembler shipped with AIX 4.3.0 generates incorrect
3166 object files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM
3167 COMPILER FAILS TO ASSEMBLE/BIND) is available from IBM Customer Support
3168 and from its techsupport.services.ibm.com website as PTF U453956. This
3169 fix is incorporated in AIX 4.3.1 and above.
3171 AIX provides National Language Support (NLS). Compilers and
3172 assemblers use NLS to support locale-specific representations of
3173 various data formats including floating-point numbers (e.g., `.' vs
3174 `,' for separating decimal fractions). There have been problems
3175 reported where GCC does not produce the same floating-point formats
3176 that the assembler expects. If one encounters this problem, set the
3177 `LANG' environment variable to `C' or `En_US'.
3179 A default can be specified with the `-mcpu=CPU_TYPE' switch and
3180 using the configure option `--with-cpu-CPU_TYPE'.
3185 Vitesse IQ2000 processors. These are used in embedded applications.
3186 There are no standard Unix configurations.
3191 Lattice Mico32 processor. This configuration is intended for embedded
3197 Lattice Mico32 processor. This configuration is intended for embedded
3198 systems running uClinux.
3203 Renesas M32C processor. This configuration is intended for embedded
3209 Renesas M32R processor. This configuration is intended for embedded
3215 By default, `m68k-*-elf*', `m68k-*-rtems', `m68k-*-uclinux' and
3216 `m68k-*-linux' build libraries for both M680x0 and ColdFire processors.
3217 If you only need the M680x0 libraries, you can omit the ColdFire ones
3218 by passing `--with-arch=m68k' to `configure'. Alternatively, you can
3219 omit the M680x0 libraries by passing `--with-arch=cf' to `configure'.
3220 These targets default to 5206 or 5475 code as appropriate for the
3221 target system when configured with `--with-arch=cf' and 68020 code
3224 The `m68k-*-netbsd' and `m68k-*-openbsd' targets also support the
3225 `--with-arch' option. They will generate ColdFire CFV4e code when
3226 configured with `--with-arch=cf' and 68020 code otherwise.
3228 You can override the default processors listed above by configuring
3229 with `--with-cpu=TARGET'. This TARGET can either be a `-mcpu' argument
3230 or one of the following values: `m68000', `m68010', `m68020', `m68030',
3231 `m68040', `m68060', `m68020-40' and `m68020-60'.
3233 GCC requires at least binutils version 2.17 on these targets.
3238 GCC 4.3 changed the uClinux configuration so that it uses the
3239 `m68k-linux-gnu' ABI rather than the `m68k-elf' ABI. It also added
3240 improved support for C++ and flat shared libraries, both of which were
3246 Toshiba Media embedded Processor. This configuration is intended for
3252 Xilinx MicroBlaze processor. This configuration is intended for
3258 If on a MIPS system you get an error message saying "does not have gp
3259 sections for all it's [sic] sectons [sic]", don't worry about it. This
3260 happens whenever you use GAS with the MIPS linker, but there is not
3261 really anything wrong, and it is okay to use the output file. You can
3262 stop such warnings by installing the GNU linker.
3264 It would be nice to extend GAS to produce the gp tables, but they are
3265 optional, and there should not be a warning about their absence.
3267 The libstdc++ atomic locking routines for MIPS targets requires MIPS
3268 II and later. A patch went in just after the GCC 3.3 release to make
3269 `mips*-*-*' use the generic implementation instead. You can also
3270 configure for `mipsel-elf' as a workaround. The `mips*-*-linux*'
3271 target continues to use the MIPS II routines. More work on this is
3272 expected in future releases.
3274 The built-in `__sync_*' functions are available on MIPS II and later
3275 systems and others that support the `ll', `sc' and `sync' instructions.
3276 This can be overridden by passing `--with-llsc' or `--without-llsc'
3277 when configuring GCC. Since the Linux kernel emulates these
3278 instructions if they are missing, the default for `mips*-*-linux*'
3279 targets is `--with-llsc'. The `--with-llsc' and `--without-llsc'
3280 configure options may be overridden at compile time by passing the
3281 `-mllsc' or `-mno-llsc' options to the compiler.
3283 MIPS systems check for division by zero (unless
3284 `-mno-check-zero-division' is passed to the compiler) by generating
3285 either a conditional trap or a break instruction. Using trap results
3286 in smaller code, but is only supported on MIPS II and later. Also,
3287 some versions of the Linux kernel have a bug that prevents trap from
3288 generating the proper signal (`SIGFPE'). To enable the use of break,
3289 use the `--with-divide=breaks' `configure' option when configuring GCC.
3290 The default is to use traps on systems that support them.
3292 The assembler from GNU binutils 2.17 and earlier has a bug in the way
3293 it sorts relocations for REL targets (o32, o64, EABI). This can cause
3294 bad code to be generated for simple C++ programs. Also the linker from
3295 GNU binutils versions prior to 2.17 has a bug which causes the runtime
3296 linker stubs in very large programs, like `libgcj.so', to be
3297 incorrectly generated. GNU Binutils 2.18 and later (and snapshots made
3298 after Nov. 9, 2006) should be free from both of these problems.
3303 Support for IRIX 5 has been removed in GCC 4.6.
3308 Support for IRIX 6.5 has been obsoleted in GCC 4.7, but can still be
3309 enabled by configuring with `--enable-obsolete'. Support will be
3310 removed in GCC 4.8. Support for IRIX 6 releases before 6.5 has been
3311 removed in GCC 4.6, as well as support for the O32 ABI. It is
3312 _strongly_ recommended to upgrade to at least IRIX 6.5.18. This
3313 release introduced full ISO C99 support, though for the N32 and N64 ABIs
3316 To build and use GCC on IRIX 6.5, you need the IRIX Development
3317 Foundation (IDF) and IRIX Development Libraries (IDL). They are
3318 included with the IRIX 6.5 media.
3320 If you are using SGI's MIPSpro `cc' as your bootstrap compiler, you
3321 must ensure that the N32 ABI is in use. To test this, compile a simple
3322 C file with `cc' and then run `file' on the resulting object file. The
3323 output should look like:
3325 test.o: ELF N32 MSB ...
3329 test.o: ELF 32-bit MSB ...
3333 test.o: ELF 64-bit MSB ...
3335 then your version of `cc' uses the O32 or N64 ABI by default. You
3336 should set the environment variable `CC' to `cc -n32' before
3339 If you want the resulting `gcc' to run on old 32-bit systems with
3340 the MIPS R4400 CPU, you need to ensure that only code for the `mips3'
3341 instruction set architecture (ISA) is generated. While GCC 3.x does
3342 this correctly, both GCC 2.95 and SGI's MIPSpro `cc' may change the ISA
3343 depending on the machine where GCC is built. Using one of them as the
3344 bootstrap compiler may result in `mips4' code, which won't run at all
3345 on `mips3'-only systems. For the test program above, you should see:
3347 test.o: ELF N32 MSB mips-3 ...
3351 test.o: ELF N32 MSB mips-4 ...
3353 instead, you should set the environment variable `CC' to `cc -n32
3354 -mips3' or `gcc -mips3' respectively before configuring GCC.
3356 MIPSpro C 7.4 may cause bootstrap failures, due to a bug when
3357 inlining `memcmp'. Either add `-U__INLINE_INTRINSICS' to the `CC'
3358 environment variable as a workaround or upgrade to MIPSpro C 7.4.1m.
3360 GCC on IRIX 6.5 is usually built to support the N32 and N64 ABIs. If
3361 you build GCC on a system that doesn't have the N64 libraries installed
3362 or cannot run 64-bit binaries, you need to configure with
3363 `--disable-multilib' so GCC doesn't try to use them. Look for
3364 `/usr/lib64/libc.so.1' to see if you have the 64-bit libraries
3367 GCC must be configured with GNU `as'. The latest version, from GNU
3368 binutils 2.22, is known to work. On the other hand, bootstrap fails
3369 with GNU `ld' at least since GNU binutils 2.17.
3371 The `--enable-libgcj' option is disabled by default: IRIX 6 uses a
3372 very low default limit (20480) for the command line length. Although
3373 `libtool' contains a workaround for this problem, at least the N64
3374 `libgcj' is known not to build despite this, running into an internal
3375 error of the native `ld'. A sure fix is to increase this limit
3376 (`ncargs') to its maximum of 262144 bytes. If you have root access,
3377 you can use the `systune' command to do this.
3379 `wchar_t' support in `libstdc++' is not available for old IRIX 6.5.x
3380 releases, x < 19. The problem cannot be autodetected and in order to
3381 build GCC for such targets you need to configure with
3382 `--disable-wchar_t'.
3387 The moxie processor. See `http://moxielogic.org/' for more information
3388 about this processor.
3393 You can specify a default version for the `-mcpu=CPU_TYPE' switch by
3394 using the configure option `--with-cpu-CPU_TYPE'.
3396 You will need binutils 2.15 or newer for a working GCC.
3401 PowerPC running Darwin (Mac OS X kernel).
3403 Pre-installed versions of Mac OS X may not include any developer
3404 tools, meaning that you will not be able to build GCC from source. Tool
3405 binaries are available at `http://opensource.apple.com/'.
3407 This version of GCC requires at least cctools-590.36. The
3408 cctools-590.36 package referenced from
3409 `http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html' will not work on
3410 systems older than 10.3.9 (aka darwin7.9.0).
3415 PowerPC system in big endian mode, running System V.4.
3417 powerpc*-*-linux-gnu*
3418 =====================
3420 PowerPC system in big endian mode running Linux.
3425 PowerPC system in big endian mode running NetBSD.
3430 Embedded PowerPC system in big endian mode for use in running under the
3436 Embedded PowerPC system in big endian mode.
3441 PowerPC system in little endian mode, running System V.4.
3446 Embedded PowerPC system in little endian mode for use in running under
3452 Embedded PowerPC system in little endian mode.
3457 The Renesas RL78 processor. This configuration is intended for
3463 The Renesas RX processor. See
3464 `http://eu.renesas.com/fmwk.jsp?cnt=rx600_series_landing.jsp&fp=/products/mpumcu/rx_family/rx600_series'
3465 for more information about this processor.
3470 S/390 system running GNU/Linux for S/390.
3475 zSeries system (64-bit) running GNU/Linux for zSeries.
3480 zSeries system (64-bit) running TPF. This platform is supported as
3481 cross-compilation target only.
3486 Support for Solaris 8 has been obsoleted in GCC 4.7, but can still be
3487 enabled by configuring with `--enable-obsolete'. Support will be
3488 removed in GCC 4.8. Support for Solaris 7 has been removed in GCC 4.6.
3490 Sun does not ship a C compiler with Solaris 2 before Solaris 10,
3491 though you can download the Sun Studio compilers for free. In Solaris
3492 10 and 11, GCC 3.4.3 is available as `/usr/sfw/bin/gcc'. Solaris 11
3493 also provides GCC 4.5.2 as `/usr/gcc/4.5/bin/gcc'. Alternatively, you
3494 can install a pre-built GCC to bootstrap and install GCC. See the
3495 binaries page for details.
3497 The Solaris 2 `/bin/sh' will often fail to configure `libstdc++-v3',
3498 `boehm-gc' or `libjava'. We therefore recommend using the following
3499 initial sequence of commands
3501 % CONFIG_SHELL=/bin/ksh
3502 % export CONFIG_SHELL
3504 and proceed as described in the configure instructions. In addition we
3505 strongly recommend specifying an absolute path to invoke
3508 Solaris 2 comes with a number of optional OS packages. Some of these
3509 are needed to use GCC fully, namely `SUNWarc', `SUNWbtool', `SUNWesu',
3510 `SUNWhea', `SUNWlibm', `SUNWsprot', and `SUNWtoo'. If you did not
3511 install all optional packages when installing Solaris 2, you will need
3512 to verify that the packages that GCC needs are installed.
3514 To check whether an optional package is installed, use the `pkginfo'
3515 command. To add an optional package, use the `pkgadd' command. For
3516 further details, see the Solaris 2 documentation.
3518 Trying to use the linker and other tools in `/usr/ucb' to install
3519 GCC has been observed to cause trouble. For example, the linker may
3520 hang indefinitely. The fix is to remove `/usr/ucb' from your `PATH'.
3522 The build process works more smoothly with the legacy Sun tools so,
3523 if you have `/usr/xpg4/bin' in your `PATH', we recommend that you place
3524 `/usr/bin' before `/usr/xpg4/bin' for the duration of the build.
3526 We recommend the use of the Sun assembler or the GNU assembler, in
3527 conjunction with the Sun linker. The GNU `as' versions included in
3528 Solaris 10, from GNU binutils 2.15, and Solaris 11, from GNU binutils
3529 2.19, are known to work. They can be found in `/usr/sfw/bin/gas'.
3530 Current versions of GNU binutils (2.22) are known to work as well.
3531 Note that your mileage may vary if you use a combination of the GNU
3532 tools and the Sun tools: while the combination GNU `as' + Sun `ld'
3533 should reasonably work, the reverse combination Sun `as' + GNU `ld' may
3534 fail to build or cause memory corruption at runtime in some cases for
3535 C++ programs. GNU `ld' usually works as well, although the version
3536 included in Solaris 10 cannot be used due to several bugs. Again, the
3537 current version (2.22) is known to work, but generally lacks platform
3538 specific features, so better stay with Sun `ld'. To use the LTO linker
3539 plugin (`-fuse-linker-plugin') with GNU `ld', GNU binutils _must_ be
3540 configured with `--enable-largefile'.
3542 To enable symbol versioning in `libstdc++' with Sun `ld', you need
3543 to have any version of GNU `c++filt', which is part of GNU binutils.
3544 `libstdc++' symbol versioning will be disabled if no appropriate
3545 version is found. Sun `c++filt' from the Sun Studio compilers does
3548 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3549 newer: `g++' will complain that types are missing. These headers
3550 assume that omitting the type means `int'; this assumption worked for
3551 C90 but is wrong for C++, and is now wrong for C99 also.
3553 `g++' accepts such (invalid) constructs with the option
3554 `-fpermissive'; it will assume that any missing type is `int' (as
3557 There are patches for Solaris 8 (108652-24 or newer for SPARC,
3558 108653-22 for Intel) that fix this bug.
3560 Sun bug 4927647 sometimes causes random spurious testsuite failures
3561 related to missing diagnostic output. This bug doesn't affect GCC
3562 itself, rather it is a kernel bug triggered by the `expect' program
3563 which is used only by the GCC testsuite driver. When the bug causes
3564 the `expect' program to miss anticipated output, extra testsuite
3567 There are patches for Solaris 8 (117350-12 or newer for SPARC,
3568 117351-12 or newer for Intel) and Solaris 9 (117171-11 or newer for
3569 SPARC, 117172-11 or newer for Intel) that address this problem.
3571 Solaris 8 provides an alternate implementation of the thread library
3572 `libthread'. It is required for TLS support and has been made the
3573 default in Solaris 9, so it is always used on Solaris 8.
3575 Thread-local storage (TLS) is supported in Solaris 8 and 9, but
3576 requires some patches. The `libthread' patches provide the
3577 `__tls_get_addr' (SPARC, 64-bit x86) resp. `___tls_get_addr' (32-bit
3578 x86) functions. On Solaris 8, you need 108993-26 or newer on SPARC,
3579 108994-26 or newer on Intel. On Solaris 9, the necessary support on
3580 SPARC is present since FCS, while 114432-05 or newer is required on
3581 Intel. Additionally, on Solaris 8, patch 109147-14 or newer on SPARC or
3582 109148-22 or newer on Intel are required for the Sun `ld' and runtime
3583 linker (`ld.so.1') support. Again, Solaris 9/SPARC works since FCS,
3584 while 113986-02 is required on Intel. The linker patches must be
3585 installed even if GNU `ld' is used. Sun `as' in Solaris 8 and 9 doesn't
3586 support the necessary relocations, so GNU `as' must be used. The
3587 `configure' script checks for those prerequisites and automatically
3588 enables TLS support if they are met. Although those minimal patch
3589 versions should work, it is recommended to use the latest patch
3590 versions which include additional bug fixes.
3595 This section contains general configuration information for all
3596 SPARC-based platforms. In addition to reading this section, please
3597 read all other sections that match your target.
3599 Newer versions of the GNU Multiple Precision Library (GMP), the MPFR
3600 library and the MPC library are known to be miscompiled by earlier
3601 versions of GCC on these platforms. We therefore recommend the use of
3602 the exact versions of these libraries listed as minimal versions in the
3608 When GCC is configured to use GNU binutils 2.14 or later, the binaries
3609 produced are smaller than the ones produced using Sun's native tools;
3610 this difference is quite significant for binaries containing debugging
3613 Starting with Solaris 7, the operating system is capable of executing
3614 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports this;
3615 the `-m64' option enables 64-bit code generation. However, if all you
3616 want is code tuned for the UltraSPARC CPU, you should try the
3617 `-mtune=ultrasparc' option instead, which produces code that, unlike
3618 full 64-bit code, can still run on non-UltraSPARC machines.
3620 When configuring on a Solaris 7 or later system that is running a
3621 kernel that supports only 32-bit binaries, one must configure with
3622 `--disable-multilib', since we will not be able to build the 64-bit
3625 GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions
3626 of the GNU compiler (especially GCC 3.0.x versions), which lead to the
3627 miscompilation of the stage1 compiler and the subsequent failure of the
3628 bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary
3629 stage, i.e. to bootstrap that compiler with the base compiler and then
3630 use it to bootstrap the final compiler.
3632 GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE
3633 Studio 7) and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes
3634 a bootstrap failure in form of a miscompilation of the stage1 compiler
3635 by the Sun compiler. This is Sun bug 4974440. This is fixed with
3638 GCC 3.4 changed the default debugging format from Stabs to DWARF-2
3639 for 32-bit code on Solaris 7 and later. If you use the Sun assembler,
3640 this change apparently runs afoul of Sun bug 4910101 (which is
3641 referenced as an x86-only problem by Sun, probably because they do not
3642 use DWARF-2). A symptom of the problem is that you cannot compile C++
3643 programs like `groff' 1.19.1 without getting messages similar to the
3646 ld: warning: relocation error: R_SPARC_UA32: ...
3647 external symbolic relocation against non-allocatable section
3648 .debug_info cannot be processed at runtime: relocation ignored.
3650 To work around this problem, compile with `-gstabs+' instead of plain
3653 When configuring the GNU Multiple Precision Library (GMP), the MPFR
3654 library or the MPC library on a Solaris 7 or later system, the canonical
3655 target triplet must be specified as the `build' parameter on the
3656 configure line. This target triplet can be obtained by invoking
3657 `./config.guess' in the toplevel source directory of GCC (and not that
3658 of GMP or MPFR or MPC). For example on a Solaris 9 system:
3660 % ./configure --build=sparc-sun-solaris2.9 --prefix=xxx
3662 sparc-sun-solaris2.10
3663 =====================
3665 There is a bug in older versions of the Sun assembler which breaks
3666 thread-local storage (TLS). A typical error message is
3668 ld: fatal: relocation error: R_SPARC_TLS_LE_HIX22: file /var/tmp//ccamPA1v.o:
3669 symbol <unknown>: bad symbol type SECT: symbol type must be TLS
3671 This bug is fixed in Sun patch 118683-03 or later.
3676 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4 or
3677 newer on this platform. All earlier binutils and glibc releases
3678 mishandled unaligned relocations on `sparc-*-*' targets.
3683 When configuring the GNU Multiple Precision Library (GMP) or the MPFR
3684 library, the canonical target triplet must be specified as the `build'
3685 parameter on the configure line. For example on a Solaris 9 system:
3687 % ./configure --build=sparc64-sun-solaris2.9 --prefix=xxx
3689 The following compiler flags must be specified in the configure step
3690 in order to bootstrap this target with the Sun compiler:
3692 % CC="cc -xarch=v9 -xildoff" SRCDIR/configure [OPTIONS] [TARGET]
3694 `-xarch=v9' specifies the SPARC-V9 architecture to the Sun toolchain
3695 and `-xildoff' turns off the incremental linker.
3700 This is a synonym for `sparc64-*-solaris2*'.
3705 The C6X family of processors. This port requires binutils-2.22 or newer.
3710 The TILE-Gx processor running GNU/Linux. This port requires
3711 binutils-2.22 or newer.
3716 The TILEPro processor running GNU/Linux. This port requires
3717 binutils-2.22 or newer.
3722 Support for VxWorks is in flux. At present GCC supports _only_ the
3723 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC.
3724 We welcome patches for other architectures supported by VxWorks 5.5.
3725 Support for VxWorks AE would also be welcome; we believe this is merely
3726 a matter of writing an appropriate "configlette" (see below). We are
3727 not interested in supporting older, a.out or COFF-based, versions of
3730 VxWorks comes with an older version of GCC installed in
3731 `$WIND_BASE/host'; we recommend you do not overwrite it. Choose an
3732 installation PREFIX entirely outside $WIND_BASE. Before running
3733 `configure', create the directories `PREFIX' and `PREFIX/bin'. Link or
3734 copy the appropriate assembler, linker, etc. into `PREFIX/bin', and set
3735 your PATH to include that directory while running both `configure' and
3738 You must give `configure' the `--with-headers=$WIND_BASE/target/h'
3739 switch so that it can find the VxWorks system headers. Since VxWorks
3740 is a cross compilation target only, you must also specify
3741 `--target=TARGET'. `configure' will attempt to create the directory
3742 `PREFIX/TARGET/sys-include' and copy files into it; make sure the user
3743 running `configure' has sufficient privilege to do so.
3745 GCC's exception handling runtime requires a special "configlette"
3746 module, `contrib/gthr_supp_vxw_5x.c'. Follow the instructions in that
3747 file to add the module to your kernel build. (Future versions of
3748 VxWorks will incorporate this module.)
3750 x86_64-*-*, amd64-*-*
3751 =====================
3753 GCC supports the x86-64 architecture implemented by the AMD64 processor
3754 (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD.
3755 On GNU/Linux the default is a bi-arch compiler which is able to generate
3756 both 64-bit x86-64 and 32-bit x86 code (via the `-m32' switch).
3758 x86_64-*-solaris2.1[0-9]*
3759 =========================
3761 GCC also supports the x86-64 architecture implemented by the AMD64
3762 processor (`amd64-*-*' is an alias for `x86_64-*-*') on Solaris 10 or
3763 later. Unlike other systems, without special options a bi-arch
3764 compiler is built which generates 32-bit code by default, but can
3765 generate 64-bit x86-64 code with the `-m64' switch. Since GCC 4.7,
3766 there is also configuration that defaults to 64-bit code, but can
3767 generate 32-bit code with `-m32'. To configure and build this way, you
3768 have to provide all support libraries like `libgmp' as 64-bit code,
3769 configure with `--target=x86_64-pc-solaris2.1x' and `CC=gcc -m64'.
3774 This target is intended for embedded Xtensa systems using the `newlib'
3775 C library. It uses ELF but does not support shared objects.
3776 Designed-defined instructions specified via the Tensilica Instruction
3777 Extension (TIE) language are only supported through inline assembly.
3779 The Xtensa configuration information must be specified prior to
3780 building GCC. The `include/xtensa-config.h' header file contains the
3781 configuration information. If you created your own Xtensa
3782 configuration with the Xtensa Processor Generator, the downloaded files
3783 include a customized copy of this header file, which you can use to
3784 replace the default header file.
3789 This target is for Xtensa systems running GNU/Linux. It supports ELF
3790 shared objects and the GNU C library (glibc). It also generates
3791 position-independent code (PIC) regardless of whether the `-fpic' or
3792 `-fPIC' options are used. In other respects, this target is the same
3793 as the `xtensa*-*-elf' target.
3798 Intel 16-bit versions
3799 ---------------------
3801 The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not
3804 However, the 32-bit port has limited support for Microsoft Windows
3805 3.11 in the Win32s environment, as a target only. See below.
3807 Intel 32-bit versions
3808 ---------------------
3810 The 32-bit versions of Windows, including Windows 95, Windows NT,
3811 Windows XP, and Windows Vista, are supported by several different target
3812 platforms. These targets differ in which Windows subsystem they target
3813 and which C libraries are used.
3815 * Cygwin *-*-cygwin: Cygwin provides a user-space Linux API
3816 emulation layer in the Win32 subsystem.
3818 * Interix *-*-interix: The Interix subsystem provides native support
3821 * MinGW *-*-mingw32: MinGW is a native GCC port for the Win32
3822 subsystem that provides a subset of POSIX.
3824 * MKS i386-pc-mks: NuTCracker from MKS. See
3825 `http://www.mkssoftware.com/' for more information.
3827 Intel 64-bit versions
3828 ---------------------
3830 GCC contains support for x86-64 using the mingw-w64 runtime library,
3831 available from `http://mingw-w64.sourceforge.net/'. This library
3832 should be used with the target triple x86_64-pc-mingw32.
3834 Presently Windows for Itanium is not supported.
3839 Windows CE is supported as a target only on Hitachi SuperH
3840 (sh-wince-pe), and MIPS (mips-wince-pe).
3842 Other Windows Platforms
3843 -----------------------
3845 GCC no longer supports Windows NT on the Alpha or PowerPC.
3847 GCC no longer supports the Windows POSIX subsystem. However, it does
3848 support the Interix subsystem. See above.
3850 Old target names including *-*-winnt and *-*-windowsnt are no longer
3853 PW32 (i386-pc-pw32) support was never completed, and the project
3854 seems to be inactive. See `http://pw32.sourceforge.net/' for more
3857 UWIN support has been removed due to a lack of maintenance.
3862 Ports of GCC are included with the Cygwin environment.
3864 GCC will build under Cygwin without modification; it does not build
3865 with Microsoft's C++ compiler and there are no plans to make it do so.
3867 The Cygwin native compiler can be configured to target any 32-bit x86
3868 cpu architecture desired; the default is i686-pc-cygwin. It should be
3869 used with as up-to-date a version of binutils as possible; use either
3870 the latest official GNU binutils release in the Cygwin distribution, or
3871 version 2.20 or above if building your own.
3876 The Interix target is used by OpenNT, Interix, Services For UNIX (SFU),
3877 and Subsystem for UNIX-based Applications (SUA). Applications compiled
3878 with this target run in the Interix subsystem, which is separate from
3879 the Win32 subsystem. This target was last known to work in GCC 3.3.
3884 GCC will build with and support only MinGW runtime 3.12 and later.
3885 Earlier versions of headers are incompatible with the new default
3886 semantics of `extern inline' in `-std=c99' and `-std=gnu99' modes.
3891 GCC contains support files for many older (1980s and early 1990s) Unix
3892 variants. For the most part, support for these systems has not been
3893 deliberately removed, but it has not been maintained for several years
3894 and may suffer from bitrot.
3896 Starting with GCC 3.1, each release has a list of "obsoleted"
3897 systems. Support for these systems is still present in that release,
3898 but `configure' will fail unless the `--enable-obsolete' option is
3899 given. Unless a maintainer steps forward, support for these systems
3900 will be removed from the next release of GCC.
3902 Support for old systems as hosts for GCC can cause problems if the
3903 workarounds for compiler, library and operating system bugs affect the
3904 cleanliness or maintainability of the rest of GCC. In some cases, to
3905 bring GCC up on such a system, if still possible with current GCC, may
3906 require first installing an old version of GCC which did work on that
3907 system, and using it to compile a more recent GCC, to avoid bugs in the
3908 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
3909 `old-releases' directory on the GCC mirror sites. Header bugs may
3910 generally be avoided using `fixincludes', but bugs or deficiencies in
3911 libraries and the operating system may still cause problems.
3913 Support for older systems as targets for cross-compilation is less
3914 problematic than support for them as hosts for GCC; if an enthusiast
3915 wishes to make such a target work again (including resurrecting any of
3916 the targets that never worked with GCC 2, starting from the last
3917 version before they were removed), patches following the usual
3918 requirements would be likely to be accepted, since they should not
3919 affect the support for more modern targets.
3921 For some systems, old versions of GNU binutils may also be useful,
3922 and are available from `pub/binutils/old-releases' on sourceware.org
3925 Some of the information on specific systems above relates to such
3926 older systems, but much of the information about GCC on such systems
3927 (which may no longer be applicable to current GCC) is to be found in
3928 the GCC texinfo manual.
3930 all ELF targets (SVR4, Solaris 2, etc.)
3931 =======================================
3933 C++ support is significantly better on ELF targets if you use the GNU
3934 linker; duplicate copies of inlines, vtables and template
3935 instantiations will be discarded automatically.
3938 File: gccinstall.info, Node: Old, Next: GNU Free Documentation License, Prev: Specific, Up: Top
3940 10 Old installation documentation
3941 *********************************
3943 Note most of this information is out of date and superseded by the
3944 previous chapters of this manual. It is provided for historical
3945 reference only, because of a lack of volunteers to merge it into the
3950 * Configurations:: Configurations Supported by GCC.
3952 Here is the procedure for installing GCC on a GNU or Unix system.
3954 1. If you have chosen a configuration for GCC which requires other GNU
3955 tools (such as GAS or the GNU linker) instead of the standard
3956 system tools, install the required tools in the build directory
3957 under the names `as', `ld' or whatever is appropriate.
3959 Alternatively, you can do subsequent compilation using a value of
3960 the `PATH' environment variable such that the necessary GNU tools
3961 come before the standard system tools.
3963 2. Specify the host, build and target machine configurations. You do
3964 this when you run the `configure' script.
3966 The "build" machine is the system which you are using, the "host"
3967 machine is the system where you want to run the resulting compiler
3968 (normally the build machine), and the "target" machine is the
3969 system for which you want the compiler to generate code.
3971 If you are building a compiler to produce code for the machine it
3972 runs on (a native compiler), you normally do not need to specify
3973 any operands to `configure'; it will try to guess the type of
3974 machine you are on and use that as the build, host and target
3975 machines. So you don't need to specify a configuration when
3976 building a native compiler unless `configure' cannot figure out
3977 what your configuration is or guesses wrong.
3979 In those cases, specify the build machine's "configuration name"
3980 with the `--host' option; the host and target will default to be
3981 the same as the host machine.
3985 ./configure --host=sparc-sun-sunos4.1
3987 A configuration name may be canonical or it may be more or less
3990 A canonical configuration name has three parts, separated by
3991 dashes. It looks like this: `CPU-COMPANY-SYSTEM'. (The three
3992 parts may themselves contain dashes; `configure' can figure out
3993 which dashes serve which purpose.) For example,
3994 `m68k-sun-sunos4.1' specifies a Sun 3.
3996 You can also replace parts of the configuration by nicknames or
3997 aliases. For example, `sun3' stands for `m68k-sun', so
3998 `sun3-sunos4.1' is another way to specify a Sun 3.
4000 You can specify a version number after any of the system types,
4001 and some of the CPU types. In most cases, the version is
4002 irrelevant, and will be ignored. So you might as well specify the
4003 version if you know it.
4005 See *note Configurations::, for a list of supported configuration
4006 names and notes on many of the configurations. You should check
4007 the notes in that section before proceeding any further with the
4008 installation of GCC.
4012 File: gccinstall.info, Node: Configurations, Up: Old
4014 10.1 Configurations Supported by GCC
4015 ====================================
4017 Here are the possible CPU types:
4019 1750a, a29k, alpha, arm, avr, cN, clipper, dsp16xx, elxsi, fr30,
4020 h8300, hppa1.0, hppa1.1, i370, i386, i486, i586, i686, i786, i860,
4021 i960, ip2k, m32r, m68000, m68k, m88k, mcore, mips, mipsel, mips64,
4022 mips64el, mn10200, mn10300, ns32k, pdp11, powerpc, powerpcle,
4023 romp, rs6000, sh, sparc, sparclite, sparc64, v850, vax, we32k.
4025 Here are the recognized company names. As you can see, customary
4026 abbreviations are used rather than the longer official names.
4028 acorn, alliant, altos, apollo, apple, att, bull, cbm, convergent,
4029 convex, crds, dec, dg, dolphin, elxsi, encore, harris, hitachi,
4030 hp, ibm, intergraph, isi, mips, motorola, ncr, next, ns, omron,
4031 plexus, sequent, sgi, sony, sun, tti, unicom, wrs.
4033 The company name is meaningful only to disambiguate when the rest of
4034 the information supplied is insufficient. You can omit it, writing
4035 just `CPU-SYSTEM', if it is not needed. For example, `vax-ultrix4.2'
4036 is equivalent to `vax-dec-ultrix4.2'.
4038 Here is a list of system types:
4040 386bsd, aix, acis, amigaos, aos, aout, aux, bosx, bsd, clix, coff,
4041 ctix, cxux, dgux, dynix, ebmon, ecoff, elf, esix, freebsd, hms,
4042 genix, gnu, linux, linux-gnu, hiux, hpux, iris, irix, isc, luna,
4043 lynxos, mach, minix, msdos, mvs, netbsd, newsos, nindy, ns, osf,
4044 osfrose, ptx, riscix, riscos, rtu, sco, sim, solaris, sunos, sym,
4045 sysv, udi, ultrix, unicos, uniplus, unos, vms, vsta, vxworks,
4048 You can omit the system type; then `configure' guesses the operating
4049 system from the CPU and company.
4051 You can add a version number to the system type; this may or may not
4052 make a difference. For example, you can write `bsd4.3' or `bsd4.4' to
4053 distinguish versions of BSD. In practice, the version number is most
4054 needed for `sysv3' and `sysv4', which are often treated differently.
4056 `linux-gnu' is the canonical name for the GNU/Linux target; however
4057 GCC will also accept `linux'. The version of the kernel in use is not
4058 relevant on these systems. A suffix such as `libc1' or `aout'
4059 distinguishes major versions of the C library; all of the suffixed
4060 versions are obsolete.
4062 If you specify an impossible combination such as `i860-dg-vms', then
4063 you may get an error message from `configure', or it may ignore part of
4064 the information and do the best it can with the rest. `configure'
4065 always prints the canonical name for the alternative that it used. GCC
4066 does not support all possible alternatives.
4068 Often a particular model of machine has a name. Many machine names
4069 are recognized as aliases for CPU/company combinations. Thus, the
4070 machine name `sun3', mentioned above, is an alias for `m68k-sun'.
4071 Sometimes we accept a company name as a machine name, when the name is
4072 popularly used for a particular machine. Here is a table of the known
4075 3300, 3b1, 3bN, 7300, altos3068, altos, apollo68, att-7300,
4076 balance, convex-cN, crds, decstation-3100, decstation, delta,
4077 encore, fx2800, gmicro, hp7NN, hp8NN, hp9k2NN, hp9k3NN, hp9k7NN,
4078 hp9k8NN, iris4d, iris, isi68, m3230, magnum, merlin, miniframe,
4079 mmax, news-3600, news800, news, next, pbd, pc532, pmax, powerpc,
4080 powerpcle, ps2, risc-news, rtpc, sun2, sun386i, sun386, sun3,
4081 sun4, symmetry, tower-32, tower.
4083 Remember that a machine name specifies both the cpu type and the company
4087 File: gccinstall.info, Node: GNU Free Documentation License, Next: Concept Index, Prev: Old, Up: Top
4089 GNU Free Documentation License
4090 ******************************
4092 Version 1.3, 3 November 2008
4094 Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
4097 Everyone is permitted to copy and distribute verbatim copies
4098 of this license document, but changing it is not allowed.
4102 The purpose of this License is to make a manual, textbook, or other
4103 functional and useful document "free" in the sense of freedom: to
4104 assure everyone the effective freedom to copy and redistribute it,
4105 with or without modifying it, either commercially or
4106 noncommercially. Secondarily, this License preserves for the
4107 author and publisher a way to get credit for their work, while not
4108 being considered responsible for modifications made by others.
4110 This License is a kind of "copyleft", which means that derivative
4111 works of the document must themselves be free in the same sense.
4112 It complements the GNU General Public License, which is a copyleft
4113 license designed for free software.
4115 We have designed this License in order to use it for manuals for
4116 free software, because free software needs free documentation: a
4117 free program should come with manuals providing the same freedoms
4118 that the software does. But this License is not limited to
4119 software manuals; it can be used for any textual work, regardless
4120 of subject matter or whether it is published as a printed book.
4121 We recommend this License principally for works whose purpose is
4122 instruction or reference.
4124 1. APPLICABILITY AND DEFINITIONS
4126 This License applies to any manual or other work, in any medium,
4127 that contains a notice placed by the copyright holder saying it
4128 can be distributed under the terms of this License. Such a notice
4129 grants a world-wide, royalty-free license, unlimited in duration,
4130 to use that work under the conditions stated herein. The
4131 "Document", below, refers to any such manual or work. Any member
4132 of the public is a licensee, and is addressed as "you". You
4133 accept the license if you copy, modify or distribute the work in a
4134 way requiring permission under copyright law.
4136 A "Modified Version" of the Document means any work containing the
4137 Document or a portion of it, either copied verbatim, or with
4138 modifications and/or translated into another language.
4140 A "Secondary Section" is a named appendix or a front-matter section
4141 of the Document that deals exclusively with the relationship of the
4142 publishers or authors of the Document to the Document's overall
4143 subject (or to related matters) and contains nothing that could
4144 fall directly within that overall subject. (Thus, if the Document
4145 is in part a textbook of mathematics, a Secondary Section may not
4146 explain any mathematics.) The relationship could be a matter of
4147 historical connection with the subject or with related matters, or
4148 of legal, commercial, philosophical, ethical or political position
4151 The "Invariant Sections" are certain Secondary Sections whose
4152 titles are designated, as being those of Invariant Sections, in
4153 the notice that says that the Document is released under this
4154 License. If a section does not fit the above definition of
4155 Secondary then it is not allowed to be designated as Invariant.
4156 The Document may contain zero Invariant Sections. If the Document
4157 does not identify any Invariant Sections then there are none.
4159 The "Cover Texts" are certain short passages of text that are
4160 listed, as Front-Cover Texts or Back-Cover Texts, in the notice
4161 that says that the Document is released under this License. A
4162 Front-Cover Text may be at most 5 words, and a Back-Cover Text may
4163 be at most 25 words.
4165 A "Transparent" copy of the Document means a machine-readable copy,
4166 represented in a format whose specification is available to the
4167 general public, that is suitable for revising the document
4168 straightforwardly with generic text editors or (for images
4169 composed of pixels) generic paint programs or (for drawings) some
4170 widely available drawing editor, and that is suitable for input to
4171 text formatters or for automatic translation to a variety of
4172 formats suitable for input to text formatters. A copy made in an
4173 otherwise Transparent file format whose markup, or absence of
4174 markup, has been arranged to thwart or discourage subsequent
4175 modification by readers is not Transparent. An image format is
4176 not Transparent if used for any substantial amount of text. A
4177 copy that is not "Transparent" is called "Opaque".
4179 Examples of suitable formats for Transparent copies include plain
4180 ASCII without markup, Texinfo input format, LaTeX input format,
4181 SGML or XML using a publicly available DTD, and
4182 standard-conforming simple HTML, PostScript or PDF designed for
4183 human modification. Examples of transparent image formats include
4184 PNG, XCF and JPG. Opaque formats include proprietary formats that
4185 can be read and edited only by proprietary word processors, SGML or
4186 XML for which the DTD and/or processing tools are not generally
4187 available, and the machine-generated HTML, PostScript or PDF
4188 produced by some word processors for output purposes only.
4190 The "Title Page" means, for a printed book, the title page itself,
4191 plus such following pages as are needed to hold, legibly, the
4192 material this License requires to appear in the title page. For
4193 works in formats which do not have any title page as such, "Title
4194 Page" means the text near the most prominent appearance of the
4195 work's title, preceding the beginning of the body of the text.
4197 The "publisher" means any person or entity that distributes copies
4198 of the Document to the public.
4200 A section "Entitled XYZ" means a named subunit of the Document
4201 whose title either is precisely XYZ or contains XYZ in parentheses
4202 following text that translates XYZ in another language. (Here XYZ
4203 stands for a specific section name mentioned below, such as
4204 "Acknowledgements", "Dedications", "Endorsements", or "History".)
4205 To "Preserve the Title" of such a section when you modify the
4206 Document means that it remains a section "Entitled XYZ" according
4209 The Document may include Warranty Disclaimers next to the notice
4210 which states that this License applies to the Document. These
4211 Warranty Disclaimers are considered to be included by reference in
4212 this License, but only as regards disclaiming warranties: any other
4213 implication that these Warranty Disclaimers may have is void and
4214 has no effect on the meaning of this License.
4218 You may copy and distribute the Document in any medium, either
4219 commercially or noncommercially, provided that this License, the
4220 copyright notices, and the license notice saying this License
4221 applies to the Document are reproduced in all copies, and that you
4222 add no other conditions whatsoever to those of this License. You
4223 may not use technical measures to obstruct or control the reading
4224 or further copying of the copies you make or distribute. However,
4225 you may accept compensation in exchange for copies. If you
4226 distribute a large enough number of copies you must also follow
4227 the conditions in section 3.
4229 You may also lend copies, under the same conditions stated above,
4230 and you may publicly display copies.
4232 3. COPYING IN QUANTITY
4234 If you publish printed copies (or copies in media that commonly
4235 have printed covers) of the Document, numbering more than 100, and
4236 the Document's license notice requires Cover Texts, you must
4237 enclose the copies in covers that carry, clearly and legibly, all
4238 these Cover Texts: Front-Cover Texts on the front cover, and
4239 Back-Cover Texts on the back cover. Both covers must also clearly
4240 and legibly identify you as the publisher of these copies. The
4241 front cover must present the full title with all words of the
4242 title equally prominent and visible. You may add other material
4243 on the covers in addition. Copying with changes limited to the
4244 covers, as long as they preserve the title of the Document and
4245 satisfy these conditions, can be treated as verbatim copying in
4248 If the required texts for either cover are too voluminous to fit
4249 legibly, you should put the first ones listed (as many as fit
4250 reasonably) on the actual cover, and continue the rest onto
4253 If you publish or distribute Opaque copies of the Document
4254 numbering more than 100, you must either include a
4255 machine-readable Transparent copy along with each Opaque copy, or
4256 state in or with each Opaque copy a computer-network location from
4257 which the general network-using public has access to download
4258 using public-standard network protocols a complete Transparent
4259 copy of the Document, free of added material. If you use the
4260 latter option, you must take reasonably prudent steps, when you
4261 begin distribution of Opaque copies in quantity, to ensure that
4262 this Transparent copy will remain thus accessible at the stated
4263 location until at least one year after the last time you
4264 distribute an Opaque copy (directly or through your agents or
4265 retailers) of that edition to the public.
4267 It is requested, but not required, that you contact the authors of
4268 the Document well before redistributing any large number of
4269 copies, to give them a chance to provide you with an updated
4270 version of the Document.
4274 You may copy and distribute a Modified Version of the Document
4275 under the conditions of sections 2 and 3 above, provided that you
4276 release the Modified Version under precisely this License, with
4277 the Modified Version filling the role of the Document, thus
4278 licensing distribution and modification of the Modified Version to
4279 whoever possesses a copy of it. In addition, you must do these
4280 things in the Modified Version:
4282 A. Use in the Title Page (and on the covers, if any) a title
4283 distinct from that of the Document, and from those of
4284 previous versions (which should, if there were any, be listed
4285 in the History section of the Document). You may use the
4286 same title as a previous version if the original publisher of
4287 that version gives permission.
4289 B. List on the Title Page, as authors, one or more persons or
4290 entities responsible for authorship of the modifications in
4291 the Modified Version, together with at least five of the
4292 principal authors of the Document (all of its principal
4293 authors, if it has fewer than five), unless they release you
4294 from this requirement.
4296 C. State on the Title page the name of the publisher of the
4297 Modified Version, as the publisher.
4299 D. Preserve all the copyright notices of the Document.
4301 E. Add an appropriate copyright notice for your modifications
4302 adjacent to the other copyright notices.
4304 F. Include, immediately after the copyright notices, a license
4305 notice giving the public permission to use the Modified
4306 Version under the terms of this License, in the form shown in
4309 G. Preserve in that license notice the full lists of Invariant
4310 Sections and required Cover Texts given in the Document's
4313 H. Include an unaltered copy of this License.
4315 I. Preserve the section Entitled "History", Preserve its Title,
4316 and add to it an item stating at least the title, year, new
4317 authors, and publisher of the Modified Version as given on
4318 the Title Page. If there is no section Entitled "History" in
4319 the Document, create one stating the title, year, authors,
4320 and publisher of the Document as given on its Title Page,
4321 then add an item describing the Modified Version as stated in
4322 the previous sentence.
4324 J. Preserve the network location, if any, given in the Document
4325 for public access to a Transparent copy of the Document, and
4326 likewise the network locations given in the Document for
4327 previous versions it was based on. These may be placed in
4328 the "History" section. You may omit a network location for a
4329 work that was published at least four years before the
4330 Document itself, or if the original publisher of the version
4331 it refers to gives permission.
4333 K. For any section Entitled "Acknowledgements" or "Dedications",
4334 Preserve the Title of the section, and preserve in the
4335 section all the substance and tone of each of the contributor
4336 acknowledgements and/or dedications given therein.
4338 L. Preserve all the Invariant Sections of the Document,
4339 unaltered in their text and in their titles. Section numbers
4340 or the equivalent are not considered part of the section
4343 M. Delete any section Entitled "Endorsements". Such a section
4344 may not be included in the Modified Version.
4346 N. Do not retitle any existing section to be Entitled
4347 "Endorsements" or to conflict in title with any Invariant
4350 O. Preserve any Warranty Disclaimers.
4352 If the Modified Version includes new front-matter sections or
4353 appendices that qualify as Secondary Sections and contain no
4354 material copied from the Document, you may at your option
4355 designate some or all of these sections as invariant. To do this,
4356 add their titles to the list of Invariant Sections in the Modified
4357 Version's license notice. These titles must be distinct from any
4358 other section titles.
4360 You may add a section Entitled "Endorsements", provided it contains
4361 nothing but endorsements of your Modified Version by various
4362 parties--for example, statements of peer review or that the text
4363 has been approved by an organization as the authoritative
4364 definition of a standard.
4366 You may add a passage of up to five words as a Front-Cover Text,
4367 and a passage of up to 25 words as a Back-Cover Text, to the end
4368 of the list of Cover Texts in the Modified Version. Only one
4369 passage of Front-Cover Text and one of Back-Cover Text may be
4370 added by (or through arrangements made by) any one entity. If the
4371 Document already includes a cover text for the same cover,
4372 previously added by you or by arrangement made by the same entity
4373 you are acting on behalf of, you may not add another; but you may
4374 replace the old one, on explicit permission from the previous
4375 publisher that added the old one.
4377 The author(s) and publisher(s) of the Document do not by this
4378 License give permission to use their names for publicity for or to
4379 assert or imply endorsement of any Modified Version.
4381 5. COMBINING DOCUMENTS
4383 You may combine the Document with other documents released under
4384 this License, under the terms defined in section 4 above for
4385 modified versions, provided that you include in the combination
4386 all of the Invariant Sections of all of the original documents,
4387 unmodified, and list them all as Invariant Sections of your
4388 combined work in its license notice, and that you preserve all
4389 their Warranty Disclaimers.
4391 The combined work need only contain one copy of this License, and
4392 multiple identical Invariant Sections may be replaced with a single
4393 copy. If there are multiple Invariant Sections with the same name
4394 but different contents, make the title of each such section unique
4395 by adding at the end of it, in parentheses, the name of the
4396 original author or publisher of that section if known, or else a
4397 unique number. Make the same adjustment to the section titles in
4398 the list of Invariant Sections in the license notice of the
4401 In the combination, you must combine any sections Entitled
4402 "History" in the various original documents, forming one section
4403 Entitled "History"; likewise combine any sections Entitled
4404 "Acknowledgements", and any sections Entitled "Dedications". You
4405 must delete all sections Entitled "Endorsements."
4407 6. COLLECTIONS OF DOCUMENTS
4409 You may make a collection consisting of the Document and other
4410 documents released under this License, and replace the individual
4411 copies of this License in the various documents with a single copy
4412 that is included in the collection, provided that you follow the
4413 rules of this License for verbatim copying of each of the
4414 documents in all other respects.
4416 You may extract a single document from such a collection, and
4417 distribute it individually under this License, provided you insert
4418 a copy of this License into the extracted document, and follow
4419 this License in all other respects regarding verbatim copying of
4422 7. AGGREGATION WITH INDEPENDENT WORKS
4424 A compilation of the Document or its derivatives with other
4425 separate and independent documents or works, in or on a volume of
4426 a storage or distribution medium, is called an "aggregate" if the
4427 copyright resulting from the compilation is not used to limit the
4428 legal rights of the compilation's users beyond what the individual
4429 works permit. When the Document is included in an aggregate, this
4430 License does not apply to the other works in the aggregate which
4431 are not themselves derivative works of the Document.
4433 If the Cover Text requirement of section 3 is applicable to these
4434 copies of the Document, then if the Document is less than one half
4435 of the entire aggregate, the Document's Cover Texts may be placed
4436 on covers that bracket the Document within the aggregate, or the
4437 electronic equivalent of covers if the Document is in electronic
4438 form. Otherwise they must appear on printed covers that bracket
4439 the whole aggregate.
4443 Translation is considered a kind of modification, so you may
4444 distribute translations of the Document under the terms of section
4445 4. Replacing Invariant Sections with translations requires special
4446 permission from their copyright holders, but you may include
4447 translations of some or all Invariant Sections in addition to the
4448 original versions of these Invariant Sections. You may include a
4449 translation of this License, and all the license notices in the
4450 Document, and any Warranty Disclaimers, provided that you also
4451 include the original English version of this License and the
4452 original versions of those notices and disclaimers. In case of a
4453 disagreement between the translation and the original version of
4454 this License or a notice or disclaimer, the original version will
4457 If a section in the Document is Entitled "Acknowledgements",
4458 "Dedications", or "History", the requirement (section 4) to
4459 Preserve its Title (section 1) will typically require changing the
4464 You may not copy, modify, sublicense, or distribute the Document
4465 except as expressly provided under this License. Any attempt
4466 otherwise to copy, modify, sublicense, or distribute it is void,
4467 and will automatically terminate your rights under this License.
4469 However, if you cease all violation of this License, then your
4470 license from a particular copyright holder is reinstated (a)
4471 provisionally, unless and until the copyright holder explicitly
4472 and finally terminates your license, and (b) permanently, if the
4473 copyright holder fails to notify you of the violation by some
4474 reasonable means prior to 60 days after the cessation.
4476 Moreover, your license from a particular copyright holder is
4477 reinstated permanently if the copyright holder notifies you of the
4478 violation by some reasonable means, this is the first time you have
4479 received notice of violation of this License (for any work) from
4480 that copyright holder, and you cure the violation prior to 30 days
4481 after your receipt of the notice.
4483 Termination of your rights under this section does not terminate
4484 the licenses of parties who have received copies or rights from
4485 you under this License. If your rights have been terminated and
4486 not permanently reinstated, receipt of a copy of some or all of
4487 the same material does not give you any rights to use it.
4489 10. FUTURE REVISIONS OF THIS LICENSE
4491 The Free Software Foundation may publish new, revised versions of
4492 the GNU Free Documentation License from time to time. Such new
4493 versions will be similar in spirit to the present version, but may
4494 differ in detail to address new problems or concerns. See
4495 `http://www.gnu.org/copyleft/'.
4497 Each version of the License is given a distinguishing version
4498 number. If the Document specifies that a particular numbered
4499 version of this License "or any later version" applies to it, you
4500 have the option of following the terms and conditions either of
4501 that specified version or of any later version that has been
4502 published (not as a draft) by the Free Software Foundation. If
4503 the Document does not specify a version number of this License,
4504 you may choose any version ever published (not as a draft) by the
4505 Free Software Foundation. If the Document specifies that a proxy
4506 can decide which future versions of this License can be used, that
4507 proxy's public statement of acceptance of a version permanently
4508 authorizes you to choose that version for the Document.
4512 "Massive Multiauthor Collaboration Site" (or "MMC Site") means any
4513 World Wide Web server that publishes copyrightable works and also
4514 provides prominent facilities for anybody to edit those works. A
4515 public wiki that anybody can edit is an example of such a server.
4516 A "Massive Multiauthor Collaboration" (or "MMC") contained in the
4517 site means any set of copyrightable works thus published on the MMC
4520 "CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0
4521 license published by Creative Commons Corporation, a not-for-profit
4522 corporation with a principal place of business in San Francisco,
4523 California, as well as future copyleft versions of that license
4524 published by that same organization.
4526 "Incorporate" means to publish or republish a Document, in whole or
4527 in part, as part of another Document.
4529 An MMC is "eligible for relicensing" if it is licensed under this
4530 License, and if all works that were first published under this
4531 License somewhere other than this MMC, and subsequently
4532 incorporated in whole or in part into the MMC, (1) had no cover
4533 texts or invariant sections, and (2) were thus incorporated prior
4534 to November 1, 2008.
4536 The operator of an MMC Site may republish an MMC contained in the
4537 site under CC-BY-SA on the same site at any time before August 1,
4538 2009, provided the MMC is eligible for relicensing.
4541 ADDENDUM: How to use this License for your documents
4542 ====================================================
4544 To use this License in a document you have written, include a copy of
4545 the License in the document and put the following copyright and license
4546 notices just after the title page:
4548 Copyright (C) YEAR YOUR NAME.
4549 Permission is granted to copy, distribute and/or modify this document
4550 under the terms of the GNU Free Documentation License, Version 1.3
4551 or any later version published by the Free Software Foundation;
4552 with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
4553 Texts. A copy of the license is included in the section entitled ``GNU
4554 Free Documentation License''.
4556 If you have Invariant Sections, Front-Cover Texts and Back-Cover
4557 Texts, replace the "with...Texts." line with this:
4559 with the Invariant Sections being LIST THEIR TITLES, with
4560 the Front-Cover Texts being LIST, and with the Back-Cover Texts
4563 If you have Invariant Sections without Cover Texts, or some other
4564 combination of the three, merge those two alternatives to suit the
4567 If your document contains nontrivial examples of program code, we
4568 recommend releasing these examples in parallel under your choice of
4569 free software license, such as the GNU General Public License, to
4570 permit their use in free software.
4573 File: gccinstall.info, Node: Concept Index, Prev: GNU Free Documentation License, Up: Top
4581 * Binaries: Binaries. (line 6)
4582 * build_configargs: Configuration. (line 1439)
4583 * Configuration: Configuration. (line 6)
4584 * configurations supported by GCC: Configurations. (line 6)
4585 * Downloading GCC: Downloading the source.
4587 * Downloading the Source: Downloading the source.
4589 * FDL, GNU Free Documentation License: GNU Free Documentation License.
4591 * Host specific installation: Specific. (line 6)
4592 * host_configargs: Configuration. (line 1443)
4593 * Installing GCC: Binaries: Binaries. (line 6)
4594 * Installing GCC: Building: Building. (line 6)
4595 * Installing GCC: Configuration: Configuration. (line 6)
4596 * Installing GCC: Testing: Testing. (line 6)
4597 * Prerequisites: Prerequisites. (line 6)
4598 * Specific: Specific. (line 6)
4599 * Specific installation notes: Specific. (line 6)
4600 * Target specific installation: Specific. (line 6)
4601 * Target specific installation notes: Specific. (line 6)
4602 * target_configargs: Configuration. (line 1447)
4603 * Testing: Testing. (line 6)
4604 * Testsuite: Testing. (line 6)
4610 Node: Installing GCC
\7f2521
4611 Node: Prerequisites
\7f4036
4612 Node: Downloading the source
\7f14260
4613 Node: Configuration
\7f16197
4614 Ref: with-gnu-as
\7f31203
4615 Ref: with-as
\7f32101
4616 Ref: with-gnu-ld
\7f33514
4617 Node: Building
\7f79771
4618 Node: Testing
\7f95256
4619 Node: Final install
\7f103105
4620 Node: Binaries
\7f108419
4621 Node: Specific
\7f110020
4622 Ref: alpha-x-x
\7f110526
4623 Ref: alpha-dec-osf51
\7f111015
4624 Ref: amd64-x-solaris210
\7f113551
4625 Ref: arm-x-eabi
\7f113654
4631 Ref: epiphany-x-elf
\7f116307
4632 Ref: x-x-freebsd
\7f116412
4633 Ref: h8300-hms
\7f118249
4634 Ref: hppa-hp-hpux
\7f118601
4635 Ref: hppa-hp-hpux10
\7f120972
4636 Ref: hppa-hp-hpux11
\7f121385
4637 Ref: x-x-linux-gnu
\7f127044
4638 Ref: ix86-x-linux
\7f127237
4639 Ref: ix86-x-solaris289
\7f127550
4640 Ref: ix86-x-solaris210
\7f128394
4641 Ref: ia64-x-linux
\7f129585
4642 Ref: ia64-x-hpux
\7f130355
4643 Ref: x-ibm-aix
\7f130910
4644 Ref: iq2000-x-elf
\7f137680
4645 Ref: lm32-x-elf
\7f137820
4646 Ref: lm32-x-uclinux
\7f137924
4647 Ref: m32c-x-elf
\7f138052
4648 Ref: m32r-x-elf
\7f138154
4649 Ref: m68k-x-x
\7f138256
4650 Ref: m68k-x-uclinux
\7f139294
4651 Ref: mep-x-elf
\7f139540
4652 Ref: microblaze-x-elf
\7f139650
4653 Ref: mips-x-x
\7f139769
4654 Ref: mips-sgi-irix5
\7f142165
4655 Ref: mips-sgi-irix6
\7f142245
4656 Ref: moxie-x-elf
\7f145469
4657 Ref: powerpc-x-x
\7f145589
4658 Ref: powerpc-x-darwin
\7f145794
4659 Ref: powerpc-x-elf
\7f146288
4660 Ref: powerpc-x-linux-gnu
\7f146373
4661 Ref: powerpc-x-netbsd
\7f146468
4662 Ref: powerpc-x-eabisim
\7f146556
4663 Ref: powerpc-x-eabi
\7f146682
4664 Ref: powerpcle-x-elf
\7f146758
4665 Ref: powerpcle-x-eabisim
\7f146850
4666 Ref: powerpcle-x-eabi
\7f146983
4667 Ref: rl78-x-elf
\7f147066
4668 Ref: rx-x-elf
\7f147172
4669 Ref: s390-x-linux
\7f147371
4670 Ref: s390x-x-linux
\7f147443
4671 Ref: s390x-ibm-tpf
\7f147530
4672 Ref: x-x-solaris2
\7f147661
4673 Ref: sparc-x-x
\7f153228
4674 Ref: sparc-sun-solaris2
\7f153730
4675 Ref: sparc-sun-solaris210
\7f156484
4676 Ref: sparc-x-linux
\7f156860
4677 Ref: sparc64-x-solaris2
\7f157085
4678 Ref: sparcv9-x-solaris2
\7f157721
4679 Ref: c6x-x-x
\7f157808
4680 Ref: tilegx-*-linux
\7f157899
4681 Ref: tilepro-*-linux
\7f158018
4682 Ref: x-x-vxworks
\7f158139
4683 Ref: x86-64-x-x
\7f159661
4684 Ref: x86-64-x-solaris210
\7f159989
4685 Ref: xtensa-x-elf
\7f160651
4686 Ref: xtensa-x-linux
\7f161322
4687 Ref: windows
\7f161663
4688 Ref: x-x-cygwin
\7f163600
4689 Ref: x-x-interix
\7f164153
4690 Ref: x-x-mingw32
\7f164462
4694 Node: Configurations
\7f170200
4695 Node: GNU Free Documentation License
\7f173741
4696 Node: Concept Index
\7f198888
projects / platform / upstream / gcc48.git / blob