1 This is doc/gccinstall.info, produced by makeinfo version 4.12 from
2 /space/rguenther/gcc-4.7.3/gcc-4.7.3/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 whether to enable or disable multiarch support. The
822 default is to check for glibc start files in a multiarch location,
823 and enable it if the files are found. The auto detection is
824 enabled for native builds, and for cross builds configured with
825 `--with-sysroot', and without `--with-native-system-header-dir'.
826 More documentation about multiarch can be found at
827 `http://wiki.debian.org/Multiarch'.
830 Specify that multiple target libraries to support different target
831 variants, calling conventions, etc. should not be built. The
832 default is to build a predefined set of them.
834 Some targets provide finer-grained control over which multilibs
835 are built (e.g., `--disable-softfloat'):
837 fpu, 26bit, underscore, interwork, biendian, nofmult.
840 softfloat, m68881, m68000, m68020.
843 single-float, biendian, softfloat.
845 `powerpc*-*-*, rs6000*-*-*'
846 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos,
850 `--with-multilib-list=LIST'
851 `--without-multilib-list'
852 Specify what multilibs to build. Currently only implemented for
853 sh*-*-* and x86-64-*-linux*.
856 LIST is a comma separated list of CPU names. These must be
857 of the form `sh*' or `m*' (in which case they match the
858 compiler option for that processor). The list should not
859 contain any endian options - these are handled by
862 If LIST is empty, then there will be no multilibs for extra
863 processors. The multilib for the secondary endian remains
866 As a special case, if an entry in the list starts with a `!'
867 (exclamation point), then it is added to the list of excluded
868 multilibs. Entries of this sort should be compatible with
869 `MULTILIB_EXCLUDES' (once the leading `!' has been stripped).
871 If `--with-multilib-list' is not given, then a default set of
872 multilibs is selected based on the value of `--target'. This
873 is usually the complete set of libraries, but some targets
874 imply a more specialized subset.
876 Example 1: to configure a compiler for SH4A only, but
877 supporting both endians, with little endian being the default:
878 --with-cpu=sh4a --with-endian=little,big --with-multilib-list=
880 Example 2: to configure a compiler for both SH4A and
881 SH4AL-DSP, but with only little endian SH4AL:
882 --with-cpu=sh4a --with-endian=little,big \
883 --with-multilib-list=sh4al,!mb/m4al
886 LIST is a comma separated list of `m32', `m64' and `mx32' to
887 enable 32-bit, 64-bit and x32 run-time libraries,
888 respectively. If LIST is empty, then there will be no
889 multilibs and only the default run-time library will be
892 If `--with-multilib-list' is not given, then only 32-bit and
893 64-bit run-time libraries will be enabled.
895 `--with-endian=ENDIANS'
896 Specify what endians to use. Currently only implemented for
899 ENDIANS may be one of the following:
901 Use big endian exclusively.
904 Use little endian exclusively.
907 Use big endian by default. Provide a multilib for little
911 Use little endian by default. Provide a multilib for big
915 Specify that the target supports threads. This affects the
916 Objective-C compiler and runtime library, and exception handling
917 for other languages like C++ and Java. On some systems, this is
920 In general, the best (and, in many cases, the only known) threading
921 model available will be configured for use. Beware that on some
922 systems, GCC has not been taught what threading models are
923 generally available for the system. In this case,
924 `--enable-threads' is an alias for `--enable-threads=single'.
927 Specify that threading support should be disabled for the system.
928 This is an alias for `--enable-threads=single'.
930 `--enable-threads=LIB'
931 Specify that LIB is the thread support library. This affects the
932 Objective-C compiler and runtime library, and exception handling
933 for other languages like C++ and Java. The possibilities for LIB
943 LynxOS thread support.
946 MIPS SDE thread support.
949 This is an alias for `single'.
952 Generic POSIX/Unix98 thread support.
955 RTEMS thread support.
958 Disable thread support, should work for all platforms.
964 VxWorks thread support.
967 Microsoft Win32 API thread support.
970 Specify that the target supports TLS (Thread Local Storage).
971 Usually configure can correctly determine if TLS is supported. In
972 cases where it guesses incorrectly, TLS can be explicitly enabled
973 or disabled with `--enable-tls' or `--disable-tls'. This can
974 happen if the assembler supports TLS but the C library does not,
975 or if the assumptions made by the configure test are incorrect.
978 Specify that the target does not support TLS. This is an alias
979 for `--enable-tls=no'.
984 Specify which cpu variant the compiler should generate code for by
985 default. CPU will be used as the default value of the `-mcpu='
986 switch. This option is only supported on some targets, including
987 ARM, i386, M68k, PowerPC, and SPARC. The `--with-cpu-32' and
988 `--with-cpu-64' options specify separate default CPUs for 32-bit
989 and 64-bit modes; these options are only supported for i386,
992 `--with-schedule=CPU'
1002 These configure options provide default values for the
1003 `-mschedule=', `-march=', `-mtune=', `-mabi=', and `-mfpu='
1004 options and for `-mhard-float' or `-msoft-float'. As with
1005 `--with-cpu', which switches will be accepted and acceptable values
1006 of the arguments depend on the target.
1009 Specify if the compiler should default to `-marm' or `-mthumb'.
1010 This option is only supported on ARM targets.
1012 `--with-stack-offset=NUM'
1013 This option sets the default for the -mstack-offset=NUM option,
1014 and will thus generally also control the setting of this option for
1015 libraries. This option is only supported on Epiphany targets.
1018 This options sets `-mfpmath=sse' by default and specifies the
1019 default ISA for floating-point arithmetics. You can select either
1020 `sse' which enables `-msse2' or `avx' which enables `-mavx' by
1021 default. This option is only supported on i386 and x86-64 targets.
1023 `--with-divide=TYPE'
1024 Specify how the compiler should generate code for checking for
1025 division by zero. This option is only supported on the MIPS
1026 target. The possibilities for TYPE are:
1028 Division by zero checks use conditional traps (this is the
1029 default on systems that support conditional traps).
1032 Division by zero checks use the break instruction.
1035 On MIPS targets, make `-mllsc' the default when no `-mno-llsc'
1036 option is passed. This is the default for Linux-based targets, as
1037 the kernel will emulate them if the ISA does not provide them.
1040 On MIPS targets, make `-mno-llsc' the default when no `-mllsc'
1044 On MIPS targets, make `-msynci' the default when no `-mno-synci'
1048 On MIPS targets, make `-mno-synci' the default when no `-msynci'
1049 option is passed. This is the default.
1052 On MIPS targets, make use of copy relocations and PLTs. These
1053 features are extensions to the traditional SVR4-based MIPS ABIs
1054 and require support from GNU binutils and the runtime C library.
1056 `--enable-__cxa_atexit'
1057 Define if you want to use __cxa_atexit, rather than atexit, to
1058 register C++ destructors for local statics and global objects.
1059 This is essential for fully standards-compliant handling of
1060 destructors, but requires __cxa_atexit in libc. This option is
1061 currently only available on systems with GNU libc. When enabled,
1062 this will cause `-fuse-cxa-atexit' to be passed by default.
1064 `--enable-gnu-indirect-function'
1065 Define if you want to enable the `ifunc' attribute. This option is
1066 currently only available on systems with GNU libc on certain
1069 `--enable-target-optspace'
1070 Specify that target libraries should be optimized for code space
1071 instead of code speed. This is the default for the m32r platform.
1073 `--with-cpp-install-dir=DIRNAME'
1074 Specify that the user visible `cpp' program should be installed in
1075 `PREFIX/DIRNAME/cpp', in addition to BINDIR.
1078 Enable COMDAT group support. This is primarily used to override
1079 the automatically detected value.
1081 `--enable-initfini-array'
1082 Force the use of sections `.init_array' and `.fini_array' (instead
1083 of `.init' and `.fini') for constructors and destructors. Option
1084 `--disable-initfini-array' has the opposite effect. If neither
1085 option is specified, the configure script will try to guess
1086 whether the `.init_array' and `.fini_array' sections are supported
1087 and, if they are, use them.
1089 `--enable-build-with-cxx'
1090 Build GCC using a C++ compiler rather than a C compiler. This is
1091 an experimental option which may become the default in a later
1094 `--enable-build-poststage1-with-cxx'
1095 When bootstrapping, build stages 2 and 3 of GCC using a C++
1096 compiler rather than a C compiler. Stage 1 is still built with a
1097 C compiler. This is enabled by default and may be disabled using
1098 `--disable-build-poststage1-with-cxx'.
1100 `--enable-maintainer-mode'
1101 The build rules that regenerate the Autoconf and Automake output
1102 files as well as the GCC master message catalog `gcc.pot' are
1103 normally disabled. This is because it can only be rebuilt if the
1104 complete source tree is present. If you have changed the sources
1105 and want to rebuild the catalog, configuring with
1106 `--enable-maintainer-mode' will enable this. Note that you need a
1107 recent version of the `gettext' tools to do so.
1109 `--disable-bootstrap'
1110 For a native build, the default configuration is to perform a
1111 3-stage bootstrap of the compiler when `make' is invoked, testing
1112 that GCC can compile itself correctly. If you want to disable
1113 this process, you can configure with `--disable-bootstrap'.
1115 `--enable-bootstrap'
1116 In special cases, you may want to perform a 3-stage build even if
1117 the target and host triplets are different. This is possible when
1118 the host can run code compiled for the target (e.g. host is
1119 i686-linux, target is i486-linux). Starting from GCC 4.2, to do
1120 this you have to configure explicitly with `--enable-bootstrap'.
1122 `--enable-generated-files-in-srcdir'
1123 Neither the .c and .h files that are generated from Bison and flex
1124 nor the info manuals and man pages that are built from the .texi
1125 files are present in the SVN development tree. When building GCC
1126 from that development tree, or from one of our snapshots, those
1127 generated files are placed in your build directory, which allows
1128 for the source to be in a readonly directory.
1130 If you configure with `--enable-generated-files-in-srcdir' then
1131 those generated files will go into the source directory. This is
1132 mainly intended for generating release or prerelease tarballs of
1133 the GCC sources, since it is not a requirement that the users of
1134 source releases to have flex, Bison, or makeinfo.
1136 `--enable-version-specific-runtime-libs'
1137 Specify that runtime libraries should be installed in the compiler
1138 specific subdirectory (`LIBDIR/gcc') rather than the usual places.
1139 In addition, `libstdc++''s include files will be installed into
1140 `LIBDIR' unless you overruled it by using
1141 `--with-gxx-include-dir=DIRNAME'. Using this option is
1142 particularly useful if you intend to use several versions of GCC in
1143 parallel. This is currently supported by `libgfortran',
1144 `libjava', `libmudflap', `libstdc++', and `libobjc'.
1146 `--enable-languages=LANG1,LANG2,...'
1147 Specify that only a particular subset of compilers and their
1148 runtime libraries should be built. For a list of valid values for
1149 LANGN you can issue the following command in the `gcc' directory
1150 of your GCC source tree:
1151 grep language= */config-lang.in
1152 Currently, you can use any of the following: `all', `ada', `c',
1153 `c++', `fortran', `go', `java', `objc', `obj-c++'. Building the
1154 Ada compiler has special requirements, see below. If you do not
1155 pass this flag, or specify the option `all', then all default
1156 languages available in the `gcc' sub-tree will be configured.
1157 Ada, Go and Objective-C++ are not default languages; the rest are.
1159 `--enable-stage1-languages=LANG1,LANG2,...'
1160 Specify that a particular subset of compilers and their runtime
1161 libraries should be built with the system C compiler during stage
1162 1 of the bootstrap process, rather than only in later stages with
1163 the bootstrapped C compiler. The list of valid values is the same
1164 as for `--enable-languages', and the option `all' will select all
1165 of the languages enabled by `--enable-languages'. This option is
1166 primarily useful for GCC development; for instance, when a
1167 development version of the compiler cannot bootstrap due to
1168 compiler bugs, or when one is debugging front ends other than the
1169 C front end. When this option is used, one can then build the
1170 target libraries for the specified languages with the stage-1
1171 compiler by using `make stage1-bubble all-target', or run the
1172 testsuite on the stage-1 compiler for the specified languages
1173 using `make stage1-start check-gcc'.
1176 Specify that the run-time libraries and tools used by GNAT should
1177 not be built. This can be useful for debugging, or for
1178 compatibility with previous Ada build procedures, when it was
1179 required to explicitly do a `make -C gcc gnatlib_and_tools'.
1182 Specify that the run-time libraries for stack smashing protection
1183 should not be built.
1185 `--disable-libquadmath'
1186 Specify that the GCC quad-precision math library should not be
1187 built. On some systems, the library is required to be linkable
1188 when building the Fortran front end, unless
1189 `--disable-libquadmath-support' is used.
1191 `--disable-libquadmath-support'
1192 Specify that the Fortran front end and `libgfortran' do not add
1193 support for `libquadmath' on systems supporting it.
1196 Specify that the run-time libraries used by GOMP should not be
1200 Specify that the compiler should use DWARF 2 debugging information
1203 `--enable-targets=all'
1204 `--enable-targets=TARGET_LIST'
1205 Some GCC targets, e.g. powerpc64-linux, build bi-arch compilers.
1206 These are compilers that are able to generate either 64-bit or
1207 32-bit code. Typically, the corresponding 32-bit target, e.g.
1208 powerpc-linux for powerpc64-linux, only generates 32-bit code.
1209 This option enables the 32-bit target to be a bi-arch compiler,
1210 which is useful when you want a bi-arch compiler that defaults to
1211 32-bit, and you are building a bi-arch or multi-arch binutils in a
1212 combined tree. On mips-linux, this will build a tri-arch compiler
1213 (ABI o32/n32/64), defaulted to o32. Currently, this option only
1214 affects sparc-linux, powerpc-linux, x86-linux, mips-linux and
1217 `--enable-secureplt'
1218 This option enables `-msecure-plt' by default for powerpc-linux.
1219 *Note RS/6000 and PowerPC Options: (gcc)RS/6000 and PowerPC
1223 This option enables `-mcld' by default for 32-bit x86 targets.
1224 *Note i386 and x86-64 Options: (gcc)i386 and x86-64 Options,
1226 `--enable-win32-registry'
1227 `--enable-win32-registry=KEY'
1228 `--disable-win32-registry'
1229 The `--enable-win32-registry' option enables Microsoft
1230 Windows-hosted GCC to look up installations paths in the registry
1231 using the following key:
1233 `HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\KEY'
1235 KEY defaults to GCC version number, and can be overridden by the
1236 `--enable-win32-registry=KEY' option. Vendors and distributors
1237 who use custom installers are encouraged to provide a different
1238 key, perhaps one comprised of vendor name and GCC version number,
1239 to avoid conflict with existing installations. This feature is
1240 enabled by default, and can be disabled by
1241 `--disable-win32-registry' option. This option has no effect on
1245 Specify that the machine does not have a floating point unit. This
1246 option only applies to `m68k-sun-sunosN'. On any other system,
1247 `--nfp' has no effect.
1251 `--enable-werror=yes'
1252 `--enable-werror=no'
1253 When you specify this option, it controls whether certain files in
1254 the compiler are built with `-Werror' in bootstrap stage2 and
1255 later. If you don't specify it, `-Werror' is turned on for the
1256 main development trunk. However it defaults to off for release
1257 branches and final releases. The specific files which get
1258 `-Werror' are controlled by the Makefiles.
1261 `--enable-checking=LIST'
1262 When you specify this option, the compiler is built to perform
1263 internal consistency checks of the requested complexity. This
1264 does not change the generated code, but adds error checking within
1265 the compiler. This will slow down the compiler and may only work
1266 properly if you are building the compiler with GCC. This is `yes'
1267 by default when building from SVN or snapshots, but `release' for
1268 releases. The default for building the stage1 compiler is `yes'.
1269 More control over the checks may be had by specifying LIST. The
1270 categories of checks available are `yes' (most common checks
1271 `assert,misc,tree,gc,rtlflag,runtime'), `no' (no checks at all),
1272 `all' (all but `valgrind'), `release' (cheapest checks
1273 `assert,runtime') or `none' (same as `no'). Individual checks can
1274 be enabled with these flags `assert', `df', `fold', `gc', `gcac'
1275 `misc', `rtl', `rtlflag', `runtime', `tree', and `valgrind'.
1277 The `valgrind' check requires the external `valgrind' simulator,
1278 available from `http://valgrind.org/'. The `df', `rtl', `gcac'
1279 and `valgrind' checks are very expensive. To disable all
1280 checking, `--disable-checking' or `--enable-checking=none' must be
1281 explicitly requested. Disabling assertions will make the compiler
1282 and runtime slightly faster but increase the risk of undetected
1283 internal errors causing wrong code to be generated.
1285 `--disable-stage1-checking'
1286 `--enable-stage1-checking'
1287 `--enable-stage1-checking=LIST'
1288 If no `--enable-checking' option is specified the stage1 compiler
1289 will be built with `yes' checking enabled, otherwise the stage1
1290 checking flags are the same as specified by `--enable-checking'.
1291 To build the stage1 compiler with different checking options use
1292 `--enable-stage1-checking'. The list of checking options is the
1293 same as for `--enable-checking'. If your system is too slow or
1294 too small to bootstrap a released compiler with checking for
1295 stage1 enabled, you can use `--disable-stage1-checking' to disable
1296 checking for the stage1 compiler.
1299 `--enable-coverage=LEVEL'
1300 With this option, the compiler is built to collect self coverage
1301 information, every time it is run. This is for internal
1302 development purposes, and only works when the compiler is being
1303 built with gcc. The LEVEL argument controls whether the compiler
1304 is built optimized or not, values are `opt' and `noopt'. For
1305 coverage analysis you want to disable optimization, for
1306 performance analysis you want to enable optimization. When
1307 coverage is enabled, the default level is without optimization.
1309 `--enable-gather-detailed-mem-stats'
1310 When this option is specified more detailed information on memory
1311 allocation is gathered. This information is printed when using
1316 With this option you can specify the garbage collector
1317 implementation used during the compilation process. CHOICE can be
1318 one of `page' and `zone', where `page' is the default.
1322 The `--enable-nls' option enables Native Language Support (NLS),
1323 which lets GCC output diagnostics in languages other than American
1324 English. Native Language Support is enabled by default if not
1325 doing a canadian cross build. The `--disable-nls' option disables
1328 `--with-included-gettext'
1329 If NLS is enabled, the `--with-included-gettext' option causes the
1330 build procedure to prefer its copy of GNU `gettext'.
1333 If NLS is enabled, and if the host lacks `gettext' but has the
1334 inferior `catgets' interface, the GCC build procedure normally
1335 ignores `catgets' and instead uses GCC's copy of the GNU `gettext'
1336 library. The `--with-catgets' option causes the build procedure
1337 to use the host's `catgets' in this situation.
1339 `--with-libiconv-prefix=DIR'
1340 Search for libiconv header files in `DIR/include' and libiconv
1341 library files in `DIR/lib'.
1344 Enable configuration for an obsoleted system. If you attempt to
1345 configure GCC for a system (build, host, or target) which has been
1346 obsoleted, and you do not specify this flag, configure will halt
1347 with an error message.
1349 All support for systems which have been obsoleted in one release
1350 of GCC is removed entirely in the next major release, unless
1351 someone steps forward to maintain the port.
1353 `--enable-decimal-float'
1354 `--enable-decimal-float=yes'
1355 `--enable-decimal-float=no'
1356 `--enable-decimal-float=bid'
1357 `--enable-decimal-float=dpd'
1358 `--disable-decimal-float'
1359 Enable (or disable) support for the C decimal floating point
1360 extension that is in the IEEE 754-2008 standard. This is enabled
1361 by default only on PowerPC, i386, and x86_64 GNU/Linux systems.
1362 Other systems may also support it, but require the user to
1363 specifically enable it. You can optionally control which decimal
1364 floating point format is used (either `bid' or `dpd'). The `bid'
1365 (binary integer decimal) format is default on i386 and x86_64
1366 systems, and the `dpd' (densely packed decimal) format is default
1369 `--enable-fixed-point'
1370 `--disable-fixed-point'
1371 Enable (or disable) support for C fixed-point arithmetic. This
1372 option is enabled by default for some targets (such as MIPS) which
1373 have hardware-support for fixed-point operations. On other
1374 targets, you may enable this option manually.
1376 `--with-long-double-128'
1377 Specify if `long double' type should be 128-bit by default on
1378 selected GNU/Linux architectures. If using
1379 `--without-long-double-128', `long double' will be by default
1380 64-bit, the same as `double' type. When neither of these
1381 configure options are used, the default will be 128-bit `long
1382 double' when built against GNU C Library 2.4 and later, 64-bit
1383 `long double' otherwise.
1385 `--with-gmp=PATHNAME'
1386 `--with-gmp-include=PATHNAME'
1387 `--with-gmp-lib=PATHNAME'
1388 `--with-mpfr=PATHNAME'
1389 `--with-mpfr-include=PATHNAME'
1390 `--with-mpfr-lib=PATHNAME'
1391 `--with-mpc=PATHNAME'
1392 `--with-mpc-include=PATHNAME'
1393 `--with-mpc-lib=PATHNAME'
1394 If you want to build GCC but do not have the GMP library, the MPFR
1395 library and/or the MPC library installed in a standard location and
1396 do not have their sources present in the GCC source tree then you
1397 can explicitly specify the directory where they are installed
1398 (`--with-gmp=GMPINSTALLDIR', `--with-mpfr=MPFRINSTALLDIR',
1399 `--with-mpc=MPCINSTALLDIR'). The `--with-gmp=GMPINSTALLDIR'
1400 option is shorthand for `--with-gmp-lib=GMPINSTALLDIR/lib' and
1401 `--with-gmp-include=GMPINSTALLDIR/include'. Likewise the
1402 `--with-mpfr=MPFRINSTALLDIR' option is shorthand for
1403 `--with-mpfr-lib=MPFRINSTALLDIR/lib' and
1404 `--with-mpfr-include=MPFRINSTALLDIR/include', also the
1405 `--with-mpc=MPCINSTALLDIR' option is shorthand for
1406 `--with-mpc-lib=MPCINSTALLDIR/lib' and
1407 `--with-mpc-include=MPCINSTALLDIR/include'. If these shorthand
1408 assumptions are not correct, you can use the explicit include and
1409 lib options directly. You might also need to ensure the shared
1410 libraries can be found by the dynamic linker when building and
1411 using GCC, for example by setting the runtime shared library path
1412 variable (`LD_LIBRARY_PATH' on GNU/Linux and Solaris systems).
1414 These flags are applicable to the host platform only. When
1415 building a cross compiler, they will not be used to configure
1418 `--with-ppl=PATHNAME'
1419 `--with-ppl-include=PATHNAME'
1420 `--with-ppl-lib=PATHNAME'
1421 `--with-cloog=PATHNAME'
1422 `--with-cloog-include=PATHNAME'
1423 `--with-cloog-lib=PATHNAME'
1424 If you do not have PPL (the Parma Polyhedra Library) and the CLooG
1425 libraries installed in a standard location and you want to build
1426 GCC, you can explicitly specify the directory where they are
1427 installed (`--with-ppl=PPLINSTALLDIR',
1428 `--with-cloog=CLOOGINSTALLDIR'). The `--with-ppl=PPLINSTALLDIR'
1429 option is shorthand for `--with-ppl-lib=PPLINSTALLDIR/lib' and
1430 `--with-ppl-include=PPLINSTALLDIR/include'. Likewise the
1431 `--with-cloog=CLOOGINSTALLDIR' option is shorthand for
1432 `--with-cloog-lib=CLOOGINSTALLDIR/lib' and
1433 `--with-cloog-include=CLOOGINSTALLDIR/include'. If these
1434 shorthand assumptions are not correct, you can use the explicit
1435 include and lib options directly.
1437 These flags are applicable to the host platform only. When
1438 building a cross compiler, they will not be used to configure
1441 `--with-host-libstdcxx=LINKER-ARGS'
1442 If you are linking with a static copy of PPL, you can use this
1443 option to specify how the linker should find the standard C++
1444 library used internally by PPL. Typical values of LINKER-ARGS
1445 might be `-lstdc++' or `-Wl,-Bstatic,-lstdc++,-Bdynamic -lm'. If
1446 you are linking with a shared copy of PPL, you probably do not
1447 need this option; shared library dependencies will cause the
1448 linker to search for the standard C++ library automatically.
1450 `--with-stage1-ldflags=FLAGS'
1451 This option may be used to set linker flags to be used when linking
1452 stage 1 of GCC. These are also used when linking GCC if
1453 configured with `--disable-bootstrap'. By default no special
1456 `--with-stage1-libs=LIBS'
1457 This option may be used to set libraries to be used when linking
1458 stage 1 of GCC. These are also used when linking GCC if
1459 configured with `--disable-bootstrap'. The default is the
1460 argument to `--with-host-libstdcxx', if specified.
1462 `--with-boot-ldflags=FLAGS'
1463 This option may be used to set linker flags to be used when linking
1464 stage 2 and later when bootstrapping GCC. If neither
1465 -with-boot-libs nor -with-host-libstdcxx is set to a value, then
1466 the default is `-static-libstdc++ -static-libgcc'.
1468 `--with-boot-libs=LIBS'
1469 This option may be used to set libraries to be used when linking
1470 stage 2 and later when bootstrapping GCC. The default is the
1471 argument to `--with-host-libstdcxx', if specified.
1473 `--with-debug-prefix-map=MAP'
1474 Convert source directory names using `-fdebug-prefix-map' when
1475 building runtime libraries. `MAP' is a space-separated list of
1476 maps of the form `OLD=NEW'.
1478 `--enable-linker-build-id'
1479 Tells GCC to pass `--build-id' option to the linker for all final
1480 links (links performed without the `-r' or `--relocatable'
1481 option), if the linker supports it. If you specify
1482 `--enable-linker-build-id', but your linker does not support
1483 `--build-id' option, a warning is issued and the
1484 `--enable-linker-build-id' option is ignored. The default is off.
1486 `--with-linker-hash-style=CHOICE'
1487 Tells GCC to pass `--hash-style=CHOICE' option to the linker for
1488 all final links. CHOICE can be one of `sysv', `gnu', and `both'
1489 where `sysv' is the default.
1491 `--enable-gnu-unique-object'
1492 `--disable-gnu-unique-object'
1493 Tells GCC to use the gnu_unique_object relocation for C++ template
1494 static data members and inline function local statics. Enabled by
1495 default for a native toolchain with an assembler that accepts it
1496 and GLIBC 2.11 or above, otherwise disabled.
1500 Enable support for link-time optimization (LTO). This is enabled
1501 by default, and may be disabled using `--disable-lto'.
1503 `--with-plugin-ld=PATHNAME'
1504 Enable an alternate linker to be used at link-time optimization
1505 (LTO) link time when `-fuse-linker-plugin' is enabled. This
1506 linker should have plugin support such as gold starting with
1507 version 2.20 or GNU ld starting with version 2.21. See
1508 `-fuse-linker-plugin' for details.
1510 Cross-Compiler-Specific Options
1511 -------------------------------
1513 The following options only apply to building cross compilers.
1516 `--with-sysroot=DIR'
1517 Tells GCC to consider DIR as the root of a tree that contains (a
1518 subset of) the root filesystem of the target operating system.
1519 Target system headers, libraries and run-time object files will be
1520 searched for in there. More specifically, this acts as if
1521 `--sysroot=DIR' was added to the default options of the built
1522 compiler. The specified directory is not copied into the install
1523 tree, unlike the options `--with-headers' and `--with-libs' that
1524 this option obsoletes. The default value, in case
1525 `--with-sysroot' is not given an argument, is
1526 `${gcc_tooldir}/sys-root'. If the specified directory is a
1527 subdirectory of `${exec_prefix}', then it will be found relative to
1528 the GCC binaries if the installation tree is moved.
1530 This option affects the system root for the compiler used to build
1531 target libraries (which runs on the build system) and the compiler
1532 newly installed with `make install'; it does not affect the
1533 compiler which is used to build GCC itself.
1535 If you specify the `--with-native-system-header-dir=DIRNAME'
1536 option then the compiler will search that directory within DIRNAME
1537 for native system headers rather than the default `/usr/include'.
1539 `--with-build-sysroot'
1540 `--with-build-sysroot=DIR'
1541 Tells GCC to consider DIR as the system root (see
1542 `--with-sysroot') while building target libraries, instead of the
1543 directory specified with `--with-sysroot'. This option is only
1544 useful when you are already using `--with-sysroot'. You can use
1545 `--with-build-sysroot' when you are configuring with `--prefix'
1546 set to a directory that is different from the one in which you are
1547 installing GCC and your target libraries.
1549 This option affects the system root for the compiler used to build
1550 target libraries (which runs on the build system); it does not
1551 affect the compiler which is used to build GCC itself.
1553 If you specify the `--with-native-system-header-dir=DIRNAME'
1554 option then the compiler will search that directory within DIRNAME
1555 for native system headers rather than the default `/usr/include'.
1558 `--with-headers=DIR'
1559 Deprecated in favor of `--with-sysroot'. Specifies that target
1560 headers are available when building a cross compiler. The DIR
1561 argument specifies a directory which has the target include files.
1562 These include files will be copied into the `gcc' install
1563 directory. _This option with the DIR argument is required_ when
1564 building a cross compiler, if `PREFIX/TARGET/sys-include' doesn't
1565 pre-exist. If `PREFIX/TARGET/sys-include' does pre-exist, the DIR
1566 argument may be omitted. `fixincludes' will be run on these files
1567 to make them compatible with GCC.
1570 Tells GCC not use any target headers from a libc when building a
1571 cross compiler. When crossing to GNU/Linux, you need the headers
1572 so GCC can build the exception handling for libgcc.
1575 `--with-libs="DIR1 DIR2 ... DIRN"'
1576 Deprecated in favor of `--with-sysroot'. Specifies a list of
1577 directories which contain the target runtime libraries. These
1578 libraries will be copied into the `gcc' install directory. If the
1579 directory list is omitted, this option has no effect.
1582 Specifies that `newlib' is being used as the target C library.
1583 This causes `__eprintf' to be omitted from `libgcc.a' on the
1584 assumption that it will be provided by `newlib'.
1587 Specifies that `AVR-Libc' is being used as the target C library.
1588 This causes float support functions like `__addsf3' to be omitted
1589 from `libgcc.a' on the assumption that it will be provided by
1590 `libm.a'. For more technical details, cf. PR54461. This option
1591 is only supported for the AVR target. It is not supported for
1592 RTEMS configurations, which currently use newlib. The option is
1593 supported since version 4.7.2 and is the default in 4.8.0 and
1596 `--with-build-time-tools=DIR'
1597 Specifies where to find the set of target tools (assembler,
1598 linker, etc.) that will be used while building GCC itself. This
1599 option can be useful if the directory layouts are different
1600 between the system you are building GCC on, and the system where
1603 For example, on an `ia64-hp-hpux' system, you may have the GNU
1604 assembler and linker in `/usr/bin', and the native tools in a
1605 different path, and build a toolchain that expects to find the
1606 native tools in `/usr/bin'.
1608 When you use this option, you should ensure that DIR includes
1609 `ar', `as', `ld', `nm', `ranlib' and `strip' if necessary, and
1610 possibly `objdump'. Otherwise, GCC may use an inconsistent set of
1613 Java-Specific Options
1614 ---------------------
1616 The following option applies to the build of the Java front end.
1619 Specify that the run-time libraries used by GCJ should not be
1620 built. This is useful in case you intend to use GCJ with some
1621 other run-time, or you're going to install it separately, or it
1622 just happens not to build on your particular machine. In general,
1623 if the Java front end is enabled, the GCJ libraries will be
1624 enabled too, unless they're known to not work on the target
1625 platform. If GCJ is enabled but `libgcj' isn't built, you may
1626 need to port it; in this case, before modifying the top-level
1627 `configure.in' so that `libgcj' is enabled by default on this
1628 platform, you may use `--enable-libgcj' to override the default.
1631 The following options apply to building `libgcj'.
1636 `--enable-java-maintainer-mode'
1637 By default the `libjava' build will not attempt to compile the
1638 `.java' source files to `.class'. Instead, it will use the
1639 `.class' files from the source tree. If you use this option you
1640 must have executables named `ecj1' and `gjavah' in your path for
1641 use by the build. You must use this option if you intend to
1642 modify any `.java' files in `libjava'.
1644 `--with-java-home=DIRNAME'
1645 This `libjava' option overrides the default value of the
1646 `java.home' system property. It is also used to set
1647 `sun.boot.class.path' to `DIRNAME/lib/rt.jar'. By default
1648 `java.home' is set to `PREFIX' and `sun.boot.class.path' to
1649 `DATADIR/java/libgcj-VERSION.jar'.
1651 `--with-ecj-jar=FILENAME'
1652 This option can be used to specify the location of an external jar
1653 file containing the Eclipse Java compiler. A specially modified
1654 version of this compiler is used by `gcj' to parse `.java' source
1655 files. If this option is given, the `libjava' build will create
1656 and install an `ecj1' executable which uses this jar file at
1659 If this option is not given, but an `ecj.jar' file is found in the
1660 topmost source tree at configure time, then the `libgcj' build
1661 will create and install `ecj1', and will also install the
1662 discovered `ecj.jar' into a suitable place in the install tree.
1664 If `ecj1' is not installed, then the user will have to supply one
1665 on his path in order for `gcj' to properly parse `.java' source
1666 files. A suitable jar is available from
1667 `ftp://sourceware.org/pub/java/'.
1669 `--disable-getenv-properties'
1670 Don't set system properties from `GCJ_PROPERTIES'.
1672 `--enable-hash-synchronization'
1673 Use a global hash table for monitor locks. Ordinarily, `libgcj''s
1674 `configure' script automatically makes the correct choice for this
1675 option for your platform. Only use this if you know you need the
1676 library to be configured differently.
1678 `--enable-interpreter'
1679 Enable the Java interpreter. The interpreter is automatically
1680 enabled by default on all platforms that support it. This option
1681 is really only useful if you want to disable the interpreter
1682 (using `--disable-interpreter').
1684 `--disable-java-net'
1685 Disable java.net. This disables the native part of java.net only,
1686 using non-functional stubs for native method implementations.
1689 Disable JVMPI support.
1691 `--disable-libgcj-bc'
1692 Disable BC ABI compilation of certain parts of libgcj. By default,
1693 some portions of libgcj are compiled with `-findirect-dispatch'
1694 and `-fno-indirect-classes', allowing them to be overridden at
1697 If `--disable-libgcj-bc' is specified, libgcj is built without
1698 these options. This allows the compile-time linker to resolve
1699 dependencies when statically linking to libgcj. However it makes
1700 it impossible to override the affected portions of libgcj at
1703 `--enable-reduced-reflection'
1704 Build most of libgcj with `-freduced-reflection'. This reduces
1705 the size of libgcj at the expense of not being able to do accurate
1706 reflection on the classes it contains. This option is safe if you
1707 know that code using libgcj will never use reflection on the
1708 standard runtime classes in libgcj (including using serialization,
1712 Enable runtime eCos target support.
1715 Don't use `libffi'. This will disable the interpreter and JNI
1716 support as well, as these require `libffi' to work.
1718 `--enable-libgcj-debug'
1719 Enable runtime debugging code.
1721 `--enable-libgcj-multifile'
1722 If specified, causes all `.java' source files to be compiled into
1723 `.class' files in one invocation of `gcj'. This can speed up
1724 build time, but is more resource-intensive. If this option is
1725 unspecified or disabled, `gcj' is invoked once for each `.java'
1726 file to compile into a `.class' file.
1728 `--with-libiconv-prefix=DIR'
1729 Search for libiconv in `DIR/include' and `DIR/lib'.
1731 `--enable-sjlj-exceptions'
1732 Force use of the `setjmp'/`longjmp'-based scheme for exceptions.
1733 `configure' ordinarily picks the correct value based on the
1734 platform. Only use this option if you are sure you need a
1737 `--with-system-zlib'
1738 Use installed `zlib' rather than that included with GCC.
1740 `--with-win32-nlsapi=ansi, unicows or unicode'
1741 Indicates how MinGW `libgcj' translates between UNICODE characters
1744 `--enable-java-home'
1745 If enabled, this creates a JPackage compatible SDK environment
1746 during install. Note that if -enable-java-home is used,
1747 -with-arch-directory=ARCH must also be specified.
1749 `--with-arch-directory=ARCH'
1750 Specifies the name to use for the `jre/lib/ARCH' directory in the
1751 SDK environment created when -enable-java-home is passed. Typical
1752 names for this directory include i386, amd64, ia64, etc.
1754 `--with-os-directory=DIR'
1755 Specifies the OS directory for the SDK include directory. This is
1756 set to auto detect, and is typically 'linux'.
1758 `--with-origin-name=NAME'
1759 Specifies the JPackage origin name. This defaults to the 'gcj' in
1762 `--with-arch-suffix=SUFFIX'
1763 Specifies the suffix for the sdk directory. Defaults to the empty
1764 string. Examples include '.x86_64' in
1765 'java-1.5.0-gcj-1.5.0.0.x86_64'.
1767 `--with-jvm-root-dir=DIR'
1768 Specifies where to install the SDK. Default is $(prefix)/lib/jvm.
1770 `--with-jvm-jar-dir=DIR'
1771 Specifies where to install jars. Default is
1772 $(prefix)/lib/jvm-exports.
1774 `--with-python-dir=DIR'
1775 Specifies where to install the Python modules used for
1776 aot-compile. DIR should not include the prefix used in
1777 installation. For example, if the Python modules are to be
1778 installed in /usr/lib/python2.5/site-packages, then
1779 -with-python-dir=/lib/python2.5/site-packages should be passed. If
1780 this is not specified, then the Python modules are installed in
1781 $(prefix)/share/python.
1783 `--enable-aot-compile-rpm'
1784 Adds aot-compile-rpm to the list of installed scripts.
1786 `--enable-browser-plugin'
1787 Build the gcjwebplugin web browser plugin.
1789 `--enable-static-libjava'
1790 Build static libraries in libjava. The default is to only build
1794 Use the single-byte `char' and the Win32 A functions natively,
1795 translating to and from UNICODE when using these functions.
1796 If unspecified, this is the default.
1799 Use the `WCHAR' and Win32 W functions natively. Adds
1800 `-lunicows' to `libgcj.spec' to link with `libunicows'.
1801 `unicows.dll' needs to be deployed on Microsoft Windows 9X
1802 machines running built executables. `libunicows.a', an
1803 open-source import library around Microsoft's `unicows.dll',
1804 is obtained from `http://libunicows.sourceforge.net/', which
1805 also gives details on getting `unicows.dll' from Microsoft.
1808 Use the `WCHAR' and Win32 W functions natively. Does _not_
1809 add `-lunicows' to `libgcj.spec'. The built executables will
1810 only run on Microsoft Windows NT and above.
1812 AWT-Specific Options
1813 ....................
1816 Use the X Window System.
1818 `--enable-java-awt=PEER(S)'
1819 Specifies the AWT peer library or libraries to build alongside
1820 `libgcj'. If this option is unspecified or disabled, AWT will be
1821 non-functional. Current valid values are `gtk' and `xlib'.
1822 Multiple libraries should be separated by a comma (i.e.
1823 `--enable-java-awt=gtk,xlib').
1825 `--enable-gtk-cairo'
1826 Build the cairo Graphics2D implementation on GTK.
1828 `--enable-java-gc=TYPE'
1829 Choose garbage collector. Defaults to `boehm' if unspecified.
1832 Do not try to compile and run a test GTK+ program.
1834 `--disable-glibtest'
1835 Do not try to compile and run a test GLIB program.
1837 `--with-libart-prefix=PFX'
1838 Prefix where libart is installed (optional).
1840 `--with-libart-exec-prefix=PFX'
1841 Exec prefix where libart is installed (optional).
1843 `--disable-libarttest'
1844 Do not try to compile and run a test libart program.
1847 Overriding `configure' test results
1848 ...................................
1850 Sometimes, it might be necessary to override the result of some
1851 `configure' test, for example in order to ease porting to a new system
1852 or work around a bug in a test. The toplevel `configure' script
1853 provides three variables for this:
1856 The contents of this variable is passed to all build `configure'
1860 The contents of this variable is passed to all host `configure'
1864 The contents of this variable is passed to all target `configure'
1868 In order to avoid shell and `make' quoting issues for complex
1869 overrides, you can pass a setting for `CONFIG_SITE' and set variables
1873 File: gccinstall.info, Node: Building, Next: Testing, Prev: Configuration, Up: Installing GCC
1878 Now that GCC is configured, you are ready to build the compiler and
1881 Some commands executed when making the compiler may fail (return a
1882 nonzero status) and be ignored by `make'. These failures, which are
1883 often due to files that were not found, are expected, and can safely be
1886 It is normal to have compiler warnings when compiling certain files.
1887 Unless you are a GCC developer, you can generally ignore these warnings
1888 unless they cause compilation to fail. Developers should attempt to fix
1889 any warnings encountered, however they can temporarily continue past
1890 warnings-as-errors by specifying the configure flag `--disable-werror'.
1892 On certain old systems, defining certain environment variables such
1893 as `CC' can interfere with the functioning of `make'.
1895 If you encounter seemingly strange errors when trying to build the
1896 compiler in a directory other than the source directory, it could be
1897 because you have previously configured the compiler in the source
1898 directory. Make sure you have done all the necessary preparations.
1900 If you build GCC on a BSD system using a directory stored in an old
1901 System V file system, problems may occur in running `fixincludes' if the
1902 System V file system doesn't support symbolic links. These problems
1903 result in a failure to fix the declaration of `size_t' in
1904 `sys/types.h'. If you find that `size_t' is a signed type and that
1905 type mismatches occur, this could be the cause.
1907 The solution is not to use such a directory for building GCC.
1909 Similarly, when building from SVN or snapshots, or if you modify
1910 `*.l' files, you need the Flex lexical analyzer generator installed.
1911 If you do not modify `*.l' files, releases contain the Flex-generated
1912 files and you do not need Flex installed to build them. There is still
1913 one Flex-based lexical analyzer (part of the build machinery, not of
1914 GCC itself) that is used even if you only build the C front end.
1916 When building from SVN or snapshots, or if you modify Texinfo
1917 documentation, you need version 4.7 or later of Texinfo installed if you
1918 want Info documentation to be regenerated. Releases contain Info
1919 documentation pre-built for the unmodified documentation in the release.
1921 5.1 Building a native compiler
1922 ==============================
1924 For a native build, the default configuration is to perform a 3-stage
1925 bootstrap of the compiler when `make' is invoked. This will build the
1926 entire GCC system and ensure that it compiles itself correctly. It can
1927 be disabled with the `--disable-bootstrap' parameter to `configure',
1928 but bootstrapping is suggested because the compiler will be tested more
1929 completely and could also have better performance.
1931 The bootstrapping process will complete the following steps:
1933 * Build tools necessary to build the compiler.
1935 * Perform a 3-stage bootstrap of the compiler. This includes
1936 building three times the target tools for use by the compiler such
1937 as binutils (bfd, binutils, gas, gprof, ld, and opcodes) if they
1938 have been individually linked or moved into the top level GCC
1939 source tree before configuring.
1941 * Perform a comparison test of the stage2 and stage3 compilers.
1943 * Build runtime libraries using the stage3 compiler from the
1947 If you are short on disk space you might consider `make
1948 bootstrap-lean' instead. The sequence of compilation is the same
1949 described above, but object files from the stage1 and stage2 of the
1950 3-stage bootstrap of the compiler are deleted as soon as they are no
1953 If you wish to use non-default GCC flags when compiling the stage2
1954 and stage3 compilers, set `BOOT_CFLAGS' on the command line when doing
1955 `make'. For example, if you want to save additional space during the
1956 bootstrap and in the final installation as well, you can build the
1957 compiler binaries without debugging information as in the following
1958 example. This will save roughly 40% of disk space both for the
1959 bootstrap and the final installation. (Libraries will still contain
1960 debugging information.)
1962 make BOOT_CFLAGS='-O' bootstrap
1964 You can place non-default optimization flags into `BOOT_CFLAGS'; they
1965 are less well tested here than the default of `-g -O2', but should
1966 still work. In a few cases, you may find that you need to specify
1967 special flags such as `-msoft-float' here to complete the bootstrap; or,
1968 if the native compiler miscompiles the stage1 compiler, you may need to
1969 work around this, by choosing `BOOT_CFLAGS' to avoid the parts of the
1970 stage1 compiler that were miscompiled, or by using `make bootstrap4' to
1971 increase the number of stages of bootstrap.
1973 `BOOT_CFLAGS' does not apply to bootstrapped target libraries.
1974 Since these are always compiled with the compiler currently being
1975 bootstrapped, you can use `CFLAGS_FOR_TARGET' to modify their
1976 compilation flags, as for non-bootstrapped target libraries. Again, if
1977 the native compiler miscompiles the stage1 compiler, you may need to
1978 work around this by avoiding non-working parts of the stage1 compiler.
1979 Use `STAGE1_TFLAGS' to this end.
1981 If you used the flag `--enable-languages=...' to restrict the
1982 compilers to be built, only those you've actually enabled will be
1983 built. This will of course only build those runtime libraries, for
1984 which the particular compiler has been built. Please note, that
1985 re-defining `LANGUAGES' when calling `make' *does not* work anymore!
1987 If the comparison of stage2 and stage3 fails, this normally indicates
1988 that the stage2 compiler has compiled GCC incorrectly, and is therefore
1989 a potentially serious bug which you should investigate and report. (On
1990 a few systems, meaningful comparison of object files is impossible; they
1991 always appear "different". If you encounter this problem, you will
1992 need to disable comparison in the `Makefile'.)
1994 If you do not want to bootstrap your compiler, you can configure with
1995 `--disable-bootstrap'. In particular cases, you may want to bootstrap
1996 your compiler even if the target system is not the same as the one you
1997 are building on: for example, you could build a
1998 `powerpc-unknown-linux-gnu' toolchain on a
1999 `powerpc64-unknown-linux-gnu' host. In this case, pass
2000 `--enable-bootstrap' to the configure script.
2002 `BUILD_CONFIG' can be used to bring in additional customization to
2003 the build. It can be set to a whitespace-separated list of names. For
2004 each such `NAME', top-level `config/`NAME'.mk' will be included by the
2005 top-level `Makefile', bringing in any settings it contains. The
2006 default `BUILD_CONFIG' can be set using the configure option
2007 `--with-build-config=`NAME'...'. Some examples of supported build
2011 Removes any `-O'-started option from `BOOT_CFLAGS', and adds `-O1'
2012 to it. `BUILD_CONFIG=bootstrap-O1' is equivalent to
2013 `BOOT_CFLAGS='-g -O1''.
2016 Analogous to `bootstrap-O1'.
2019 Enables Link-Time Optimization for host tools during bootstrapping.
2020 `BUILD_CONFIG=bootstrap-lto' is equivalent to adding `-flto' to
2024 Verifies that the compiler generates the same executable code,
2025 whether or not it is asked to emit debug information. To this
2026 end, this option builds stage2 host programs without debug
2027 information, and uses `contrib/compare-debug' to compare them with
2028 the stripped stage3 object files. If `BOOT_CFLAGS' is overridden
2029 so as to not enable debug information, stage2 will have it, and
2030 stage3 won't. This option is enabled by default when GCC
2031 bootstrapping is enabled, if `strip' can turn object files
2032 compiled with and without debug info into identical object files.
2033 In addition to better test coverage, this option makes default
2034 bootstraps faster and leaner.
2036 `bootstrap-debug-big'
2037 Rather than comparing stripped object files, as in
2038 `bootstrap-debug', this option saves internal compiler dumps
2039 during stage2 and stage3 and compares them as well, which helps
2040 catch additional potential problems, but at a great cost in terms
2041 of disk space. It can be specified in addition to
2044 `bootstrap-debug-lean'
2045 This option saves disk space compared with `bootstrap-debug-big',
2046 but at the expense of some recompilation. Instead of saving the
2047 dumps of stage2 and stage3 until the final compare, it uses
2048 `-fcompare-debug' to generate, compare and remove the dumps during
2049 stage3, repeating the compilation that already took place in
2050 stage2, whose dumps were not saved.
2052 `bootstrap-debug-lib'
2053 This option tests executable code invariance over debug information
2054 generation on target libraries, just like `bootstrap-debug-lean'
2055 tests it on host programs. It builds stage3 libraries with
2056 `-fcompare-debug', and it can be used along with any of the
2057 `bootstrap-debug' options above.
2059 There aren't `-lean' or `-big' counterparts to this option because
2060 most libraries are only build in stage3, so bootstrap compares
2061 would not get significant coverage. Moreover, the few libraries
2062 built in stage2 are used in stage3 host programs, so we wouldn't
2063 want to compile stage2 libraries with different options for
2064 comparison purposes.
2066 `bootstrap-debug-ckovw'
2067 Arranges for error messages to be issued if the compiler built on
2068 any stage is run without the option `-fcompare-debug'. This is
2069 useful to verify the full `-fcompare-debug' testing coverage. It
2070 must be used along with `bootstrap-debug-lean' and
2071 `bootstrap-debug-lib'.
2074 Arranges for the run time of each program started by the GCC
2075 driver, built in any stage, to be logged to `time.log', in the top
2076 level of the build tree.
2079 5.2 Building a cross compiler
2080 =============================
2082 When building a cross compiler, it is not generally possible to do a
2083 3-stage bootstrap of the compiler. This makes for an interesting
2084 problem as parts of GCC can only be built with GCC.
2086 To build a cross compiler, we recommend first building and
2087 installing a native compiler. You can then use the native GCC compiler
2088 to build the cross compiler. The installed native compiler needs to be
2089 GCC version 2.95 or later.
2091 If the cross compiler is to be built with support for the Java
2092 programming language and the ability to compile .java source files is
2093 desired, the installed native compiler used to build the cross compiler
2094 needs to be the same GCC version as the cross compiler. In addition
2095 the cross compiler needs to be configured with `--with-ecj-jar=...'.
2097 Assuming you have already installed a native copy of GCC and
2098 configured your cross compiler, issue the command `make', which
2099 performs the following steps:
2101 * Build host tools necessary to build the compiler.
2103 * Build target tools for use by the compiler such as binutils (bfd,
2104 binutils, gas, gprof, ld, and opcodes) if they have been
2105 individually linked or moved into the top level GCC source tree
2108 * Build the compiler (single stage only).
2110 * Build runtime libraries using the compiler from the previous step.
2112 Note that if an error occurs in any step the make process will exit.
2114 If you are not building GNU binutils in the same source tree as GCC,
2115 you will need a cross-assembler and cross-linker installed before
2116 configuring GCC. Put them in the directory `PREFIX/TARGET/bin'. Here
2117 is a table of the tools you should put in this directory:
2120 This should be the cross-assembler.
2123 This should be the cross-linker.
2126 This should be the cross-archiver: a program which can manipulate
2127 archive files (linker libraries) in the target machine's format.
2130 This should be a program to construct a symbol table in an archive
2133 The installation of GCC will find these programs in that directory,
2134 and copy or link them to the proper place to for the cross-compiler to
2135 find them when run later.
2137 The easiest way to provide these files is to build the Binutils
2138 package. Configure it with the same `--host' and `--target' options
2139 that you use for configuring GCC, then build and install them. They
2140 install their executables automatically into the proper directory.
2141 Alas, they do not support all the targets that GCC supports.
2143 If you are not building a C library in the same source tree as GCC,
2144 you should also provide the target libraries and headers before
2145 configuring GCC, specifying the directories with `--with-sysroot' or
2146 `--with-headers' and `--with-libs'. Many targets also require "start
2147 files" such as `crt0.o' and `crtn.o' which are linked into each
2148 executable. There may be several alternatives for `crt0.o', for use
2149 with profiling or other compilation options. Check your target's
2150 definition of `STARTFILE_SPEC' to find out what start files it uses.
2152 5.3 Building in parallel
2153 ========================
2155 GNU Make 3.80 and above, which is necessary to build GCC, support
2156 building in parallel. To activate this, you can use `make -j 2'
2157 instead of `make'. You can also specify a bigger number, and in most
2158 cases using a value greater than the number of processors in your
2159 machine will result in fewer and shorter I/O latency hits, thus
2160 improving overall throughput; this is especially true for slow drives
2161 and network filesystems.
2163 5.4 Building the Ada compiler
2164 =============================
2166 In order to build GNAT, the Ada compiler, you need a working GNAT
2167 compiler (GCC version 4.0 or later). This includes GNAT tools such as
2168 `gnatmake' and `gnatlink', since the Ada front end is written in Ada and
2169 uses some GNAT-specific extensions.
2171 In order to build a cross compiler, it is suggested to install the
2172 new compiler as native first, and then use it to build the cross
2175 `configure' does not test whether the GNAT installation works and
2176 has a sufficiently recent version; if too old a GNAT version is
2177 installed, the build will fail unless `--enable-languages' is used to
2178 disable building the Ada front end.
2180 `ADA_INCLUDE_PATH' and `ADA_OBJECT_PATH' environment variables must
2181 not be set when building the Ada compiler, the Ada tools, or the Ada
2182 runtime libraries. You can check that your build environment is clean
2183 by verifying that `gnatls -v' lists only one explicit path in each
2186 5.5 Building with profile feedback
2187 ==================================
2189 It is possible to use profile feedback to optimize the compiler itself.
2190 This should result in a faster compiler binary. Experiments done on
2191 x86 using gcc 3.3 showed approximately 7 percent speedup on compiling C
2192 programs. To bootstrap the compiler with profile feedback, use `make
2195 When `make profiledbootstrap' is run, it will first build a `stage1'
2196 compiler. This compiler is used to build a `stageprofile' compiler
2197 instrumented to collect execution counts of instruction and branch
2198 probabilities. Then runtime libraries are compiled with profile
2199 collected. Finally a `stagefeedback' compiler is built using the
2200 information collected.
2202 Unlike standard bootstrap, several additional restrictions apply.
2203 The compiler used to build `stage1' needs to support a 64-bit integral
2204 type. It is recommended to only use GCC for this. Also parallel make
2205 is currently not supported since collisions in profile collecting may
2209 File: gccinstall.info, Node: Testing, Next: Final install, Prev: Building, Up: Installing GCC
2211 6 Installing GCC: Testing
2212 *************************
2214 Before you install GCC, we encourage you to run the testsuites and to
2215 compare your results with results from a similar configuration that have
2216 been submitted to the gcc-testresults mailing list. Some of these
2217 archived results are linked from the build status lists at
2218 `http://gcc.gnu.org/buildstat.html', although not everyone who reports
2219 a successful build runs the testsuites and submits the results. This
2220 step is optional and may require you to download additional software,
2221 but it can give you confidence in your new GCC installation or point out
2222 problems before you install and start using your new GCC.
2224 First, you must have downloaded the testsuites. These are part of
2225 the full distribution, but if you downloaded the "core" compiler plus
2226 any front ends, you must download the testsuites separately.
2228 Second, you must have the testing tools installed. This includes
2229 DejaGnu, Tcl, and Expect; the DejaGnu site has links to these.
2231 If the directories where `runtest' and `expect' were installed are
2232 not in the `PATH', you may need to set the following environment
2233 variables appropriately, as in the following example (which assumes
2234 that DejaGnu has been installed under `/usr/local'):
2236 TCL_LIBRARY = /usr/local/share/tcl8.0
2237 DEJAGNULIBS = /usr/local/share/dejagnu
2239 (On systems such as Cygwin, these paths are required to be actual
2240 paths, not mounts or links; presumably this is due to some lack of
2241 portability in the DejaGnu code.)
2243 Finally, you can run the testsuite (which may take a long time):
2244 cd OBJDIR; make -k check
2246 This will test various components of GCC, such as compiler front
2247 ends and runtime libraries. While running the testsuite, DejaGnu might
2248 emit some harmless messages resembling `WARNING: Couldn't find the
2249 global config file.' or `WARNING: Couldn't find tool init file' that
2252 If you are testing a cross-compiler, you may want to run the
2253 testsuite on a simulator as described at
2254 `http://gcc.gnu.org/simtest-howto.html'.
2256 6.1 How can you run the testsuite on selected tests?
2257 ====================================================
2259 In order to run sets of tests selectively, there are targets `make
2260 check-gcc' and language specific `make check-c', `make check-c++',
2261 `make check-fortran', `make check-java', `make check-ada', `make
2262 check-objc', `make check-obj-c++', `make check-lto' in the `gcc'
2263 subdirectory of the object directory. You can also just run `make
2264 check' in a subdirectory of the object directory.
2266 A more selective way to just run all `gcc' execute tests in the
2269 make check-gcc RUNTESTFLAGS="execute.exp OTHER-OPTIONS"
2271 Likewise, in order to run only the `g++' "old-deja" tests in the
2272 testsuite with filenames matching `9805*', you would use
2274 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* OTHER-OPTIONS"
2276 The `*.exp' files are located in the testsuite directories of the GCC
2277 source, the most important ones being `compile.exp', `execute.exp',
2278 `dg.exp' and `old-deja.exp'. To get a list of the possible `*.exp'
2279 files, pipe the output of `make check' into a file and look at the
2280 `Running ... .exp' lines.
2282 6.2 Passing options and running multiple testsuites
2283 ===================================================
2285 You can pass multiple options to the testsuite using the
2286 `--target_board' option of DejaGNU, either passed as part of
2287 `RUNTESTFLAGS', or directly to `runtest' if you prefer to work outside
2288 the makefiles. For example,
2290 make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants"
2292 will run the standard `g++' testsuites ("unix" is the target name
2293 for a standard native testsuite situation), passing `-O3
2294 -fmerge-constants' to the compiler on every test, i.e., slashes
2297 You can run the testsuites multiple times using combinations of
2298 options with a syntax similar to the brace expansion of popular shells:
2300 ..."--target_board=arm-sim\{-mhard-float,-msoft-float\}\{-O1,-O2,-O3,\}"
2302 (Note the empty option caused by the trailing comma in the final
2303 group.) The following will run each testsuite eight times using the
2304 `arm-sim' target, as if you had specified all possible combinations
2307 --target_board=arm-sim/-mhard-float/-O1
2308 --target_board=arm-sim/-mhard-float/-O2
2309 --target_board=arm-sim/-mhard-float/-O3
2310 --target_board=arm-sim/-mhard-float
2311 --target_board=arm-sim/-msoft-float/-O1
2312 --target_board=arm-sim/-msoft-float/-O2
2313 --target_board=arm-sim/-msoft-float/-O3
2314 --target_board=arm-sim/-msoft-float
2316 They can be combined as many times as you wish, in arbitrary ways.
2319 ..."--target_board=unix/-Wextra\{-O3,-fno-strength\}\{-fomit-frame,\}"
2321 will generate four combinations, all involving `-Wextra'.
2323 The disadvantage to this method is that the testsuites are run in
2324 serial, which is a waste on multiprocessor systems. For users with GNU
2325 Make and a shell which performs brace expansion, you can run the
2326 testsuites in parallel by having the shell perform the combinations and
2327 `make' do the parallel runs. Instead of using `--target_board', use a
2328 special makefile target:
2330 make -jN check-TESTSUITE//TEST-TARGET/OPTION1/OPTION2/...
2334 make -j3 check-gcc//sh-hms-sim/{-m1,-m2,-m3,-m3e,-m4}/{,-nofpu}
2336 will run three concurrent "make-gcc" testsuites, eventually testing
2337 all ten combinations as described above. Note that this is currently
2338 only supported in the `gcc' subdirectory. (To see how this works, try
2339 typing `echo' before the example given here.)
2341 6.3 Additional testing for Java Class Libraries
2342 ===============================================
2344 The Java runtime tests can be executed via `make check' in the
2345 `TARGET/libjava/testsuite' directory in the build tree.
2347 The Mauve Project provides a suite of tests for the Java Class
2348 Libraries. This suite can be run as part of libgcj testing by placing
2349 the Mauve tree within the libjava testsuite at
2350 `libjava/testsuite/libjava.mauve/mauve', or by specifying the location
2351 of that tree when invoking `make', as in `make MAUVEDIR=~/mauve check'.
2353 6.4 How to interpret test results
2354 =================================
2356 The result of running the testsuite are various `*.sum' and `*.log'
2357 files in the testsuite subdirectories. The `*.log' files contain a
2358 detailed log of the compiler invocations and the corresponding results,
2359 the `*.sum' files summarize the results. These summaries contain
2360 status codes for all tests:
2362 * PASS: the test passed as expected
2364 * XPASS: the test unexpectedly passed
2366 * FAIL: the test unexpectedly failed
2368 * XFAIL: the test failed as expected
2370 * UNSUPPORTED: the test is not supported on this platform
2372 * ERROR: the testsuite detected an error
2374 * WARNING: the testsuite detected a possible problem
2376 It is normal for some tests to report unexpected failures. At the
2377 current time the testing harness does not allow fine grained control
2378 over whether or not a test is expected to fail. This problem should be
2379 fixed in future releases.
2381 6.5 Submitting test results
2382 ===========================
2384 If you want to report the results to the GCC project, use the
2385 `contrib/test_summary' shell script. Start it in the OBJDIR with
2387 SRCDIR/contrib/test_summary -p your_commentary.txt \
2388 -m gcc-testresults@gcc.gnu.org |sh
2390 This script uses the `Mail' program to send the results, so make
2391 sure it is in your `PATH'. The file `your_commentary.txt' is prepended
2392 to the testsuite summary and should contain any special remarks you
2393 have on your results or your build environment. Please do not edit the
2394 testsuite result block or the subject line, as these messages may be
2395 automatically processed.
2398 File: gccinstall.info, Node: Final install, Prev: Testing, Up: Installing GCC
2400 7 Installing GCC: Final installation
2401 ************************************
2403 Now that GCC has been built (and optionally tested), you can install
2405 cd OBJDIR && make install
2407 We strongly recommend to install into a target directory where there
2408 is no previous version of GCC present. Also, the GNAT runtime should
2409 not be stripped, as this would break certain features of the debugger
2410 that depend on this debugging information (catching Ada exceptions for
2413 That step completes the installation of GCC; user level binaries can
2414 be found in `PREFIX/bin' where PREFIX is the value you specified with
2415 the `--prefix' to configure (or `/usr/local' by default). (If you
2416 specified `--bindir', that directory will be used instead; otherwise,
2417 if you specified `--exec-prefix', `EXEC-PREFIX/bin' will be used.)
2418 Headers for the C++ and Java libraries are installed in
2419 `PREFIX/include'; libraries in `LIBDIR' (normally `PREFIX/lib');
2420 internal parts of the compiler in `LIBDIR/gcc' and `LIBEXECDIR/gcc';
2421 documentation in info format in `INFODIR' (normally `PREFIX/info').
2423 When installing cross-compilers, GCC's executables are not only
2424 installed into `BINDIR', that is, `EXEC-PREFIX/bin', but additionally
2425 into `EXEC-PREFIX/TARGET-ALIAS/bin', if that directory exists.
2426 Typically, such "tooldirs" hold target-specific binutils, including
2427 assembler and linker.
2429 Installation into a temporary staging area or into a `chroot' jail
2430 can be achieved with the command
2432 make DESTDIR=PATH-TO-ROOTDIR install
2434 where PATH-TO-ROOTDIR is the absolute path of a directory relative to
2435 which all installation paths will be interpreted. Note that the
2436 directory specified by `DESTDIR' need not exist yet; it will be created
2439 There is a subtle point with tooldirs and `DESTDIR': If you relocate
2440 a cross-compiler installation with e.g. `DESTDIR=ROOTDIR', then the
2441 directory `ROOTDIR/EXEC-PREFIX/TARGET-ALIAS/bin' will be filled with
2442 duplicated GCC executables only if it already exists, it will not be
2443 created otherwise. This is regarded as a feature, not as a bug,
2444 because it gives slightly more control to the packagers using the
2447 You can install stripped programs and libraries with
2451 If you are bootstrapping a released version of GCC then please
2452 quickly review the build status page for your release, available from
2453 `http://gcc.gnu.org/buildstat.html'. If your system is not listed for
2454 the version of GCC that you built, send a note to <gcc@gcc.gnu.org>
2455 indicating that you successfully built and installed GCC. Include the
2456 following information:
2458 * Output from running `SRCDIR/config.guess'. Do not send that file
2459 itself, just the one-line output from running it.
2461 * The output of `gcc -v' for your newly installed `gcc'. This tells
2462 us which version of GCC you built and the options you passed to
2465 * Whether you enabled all languages or a subset of them. If you
2466 used a full distribution then this information is part of the
2467 configure options in the output of `gcc -v', but if you downloaded
2468 the "core" compiler plus additional front ends then it isn't
2469 apparent which ones you built unless you tell us about it.
2471 * If the build was for GNU/Linux, also include:
2472 * The distribution name and version (e.g., Red Hat 7.1 or
2473 Debian 2.2.3); this information should be available from
2476 * The version of the Linux kernel, available from `uname
2477 --version' or `uname -a'.
2479 * The version of glibc you used; for RPM-based systems like Red
2480 Hat, Mandrake, and SuSE type `rpm -q glibc' to get the glibc
2481 version, and on systems like Debian and Progeny use `dpkg -l
2483 For other systems, you can include similar information if you
2484 think it is relevant.
2486 * Any other information that you think would be useful to people
2487 building GCC on the same configuration. The new entry in the
2488 build status list will include a link to the archived copy of your
2491 We'd also like to know if the *note host/target specific
2492 installation notes: Specific. didn't include your host/target
2493 information or if that information is incomplete or out of date. Send
2494 a note to <gcc@gcc.gnu.org> detailing how the information should be
2497 If you find a bug, please report it following the bug reporting
2500 If you want to print the GCC manuals, do `cd OBJDIR; make dvi'. You
2501 will need to have `texi2dvi' (version at least 4.7) and TeX installed.
2502 This creates a number of `.dvi' files in subdirectories of `OBJDIR';
2503 these may be converted for printing with programs such as `dvips'.
2504 Alternately, by using `make pdf' in place of `make dvi', you can create
2505 documentation in the form of `.pdf' files; this requires `texi2pdf',
2506 which is included with Texinfo version 4.8 and later. You can also buy
2507 printed manuals from the Free Software Foundation, though such manuals
2508 may not be for the most recent version of GCC.
2510 If you would like to generate online HTML documentation, do `cd
2511 OBJDIR; make html' and HTML will be generated for the gcc manuals in
2515 File: gccinstall.info, Node: Binaries, Next: Specific, Prev: Installing GCC, Up: Top
2517 8 Installing GCC: Binaries
2518 **************************
2520 We are often asked about pre-compiled versions of GCC. While we
2521 cannot provide these for all platforms, below you'll find links to
2522 binaries for various platforms where creating them by yourself is not
2523 easy due to various reasons.
2525 Please note that we did not create these binaries, nor do we support
2526 them. If you have any problems installing them, please contact their
2530 * Bull's Freeware and Shareware Archive for AIX;
2532 * Hudson Valley Community College Open Source Software for IBM
2535 * AIX 5L and 6 Open Source Packages.
2539 * Renesas H8/300[HS]--GNU Development Tools for the Renesas
2543 * HP-UX Porting Center;
2545 * Binaries for HP-UX 11.00 at Aachen University of Technology.
2547 * SCO OpenServer/Unixware.
2549 * Solaris 2 (SPARC, Intel):
2563 * Microsoft Windows:
2564 * The Cygwin project;
2566 * The MinGW project.
2568 * The Written Word offers binaries for AIX 4.3.3, 5.1 and 5.2, IRIX
2569 6.5, Tru64 UNIX 4.0D and 5.1, GNU/Linux (i386), HP-UX 10.20,
2570 11.00, and 11.11, and Solaris/SPARC 2.5.1, 2.6, 7, 8, 9 and 10.
2572 * OpenPKG offers binaries for quite a number of platforms.
2574 * The GFortran Wiki has links to GNU Fortran binaries for several
2578 File: gccinstall.info, Node: Specific, Next: Old, Prev: Binaries, Up: Top
2580 9 Host/target specific installation notes for GCC
2581 *************************************************
2583 Please read this document carefully _before_ installing the GNU
2584 Compiler Collection on your machine.
2586 Note that this list of install notes is _not_ a list of supported
2587 hosts or targets. Not all supported hosts and targets are listed here,
2588 only the ones that require host-specific or target-specific information
2594 This section contains general configuration information for all
2595 alpha-based platforms using ELF (in particular, ignore this section for
2596 DEC OSF/1, Digital UNIX and Tru64 UNIX). In addition to reading this
2597 section, please read all other sections that match your target.
2599 We require binutils 2.11.2 or newer. Previous binutils releases had
2600 a number of problems with DWARF 2 debugging information, not the least
2601 of which is incorrect linking of shared libraries.
2606 Systems using processors that implement the DEC Alpha architecture and
2607 are running the DEC/Compaq/HP Unix (DEC OSF/1, Digital UNIX, or
2608 Compaq/HP Tru64 UNIX) operating system, for example the DEC Alpha AXP
2611 Support for Tru64 UNIX V5.1 has been obsoleted in GCC 4.7, but can
2612 still be enabled by configuring with `--enable-obsolete'. Support will
2613 be removed in GCC 4.8. As of GCC 4.6, support for Tru64 UNIX V4.0 and
2614 V5.0 has been removed. As of GCC 3.2, versions before
2615 `alpha*-dec-osf4' are no longer supported. (These are the versions
2616 which identify themselves as DEC OSF/1.)
2618 On Tru64 UNIX, virtual memory exhausted bootstrap failures may be
2619 fixed by reconfiguring Kernel Virtual Memory and Swap parameters per
2620 the `/usr/sbin/sys_check' Tuning Suggestions, or applying the patch in
2621 `http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html'. Depending on the OS
2622 version used, you need a data segment size between 512 MB and 1 GB, so
2623 simply use `ulimit -Sd unlimited'.
2625 As of GNU binutils 2.22, neither GNU `as' nor GNU `ld' are supported
2626 on Tru64 UNIX, so you must not configure GCC with `--with-gnu-as' or
2629 Cross-compilers for the Tru64 UNIX target currently do not work
2630 because the auxiliary programs `mips-tdump' and `mips-tfile' can't be
2631 compiled on anything but Tru64 UNIX.
2633 GCC writes a `.verstamp' directive to the assembler output file
2634 unless it is built as a cross-compiler. It gets the version to use from
2635 the system header file `/usr/include/stamp.h'. If you install a new
2636 version of Tru64 UNIX, you should rebuild GCC to pick up the new version
2639 GCC now supports both the native (ECOFF) debugging format used by DBX
2640 and GDB and an encapsulated STABS format for use only with GDB. See the
2641 discussion of the `--with-stabs' option of `configure' above for more
2642 information on these formats and how to select them.
2644 There is a bug in DEC's assembler that produces incorrect line
2645 numbers for ECOFF format when the `.align' directive is used. To work
2646 around this problem, GCC will not emit such alignment directives while
2647 writing ECOFF format debugging information even if optimization is
2648 being performed. Unfortunately, this has the very undesirable
2649 side-effect that code addresses when `-O' is specified are different
2650 depending on whether or not `-g' is also specified.
2652 To avoid this behavior, specify `-gstabs+' and use GDB instead of
2653 DBX. DEC is now aware of this problem with the assembler and hopes to
2654 provide a fix shortly.
2656 amd64-*-solaris2.1[0-9]*
2657 ========================
2659 This is a synonym for `x86_64-*-solaris2.1[0-9]*'.
2664 ARM-family processors. Subtargets that use the ELF object format
2665 require GNU binutils 2.13 or newer. Such subtargets include:
2666 `arm-*-netbsdelf', `arm-*-*linux-gnueabi*' and `arm-*-rtemseabi'.
2671 ATMEL AVR-family micro controllers. These are used in embedded
2672 applications. There are no standard Unix configurations. *Note AVR
2673 Options: (gcc)AVR Options, for the list of supported MCU types.
2675 Use `configure --target=avr --enable-languages="c"' to configure GCC.
2677 Further installation notes and other useful information about AVR
2678 tools can also be obtained from:
2680 * http://www.nongnu.org/avr/
2682 * http://www.amelek.gda.pl/avr/
2684 We _strongly_ recommend using binutils 2.13 or newer.
2686 The following error:
2687 Error: register required
2689 indicates that you should upgrade to a newer version of the binutils.
2694 The Blackfin processor, an Analog Devices DSP. *Note Blackfin Options:
2695 (gcc)Blackfin Options,
2697 More information, and a version of binutils with support for this
2698 processor, is available at `http://blackfin.uclinux.org'
2703 The CR16 CompactRISC architecture is a 16-bit architecture. This
2704 architecture is used in embedded applications.
2706 *Note CR16 Options: (gcc)CR16 Options,
2708 Use `configure --target=cr16-elf --enable-languages=c,c++' to
2709 configure GCC for building a CR16 elf cross-compiler.
2711 Use `configure --target=cr16-uclinux --enable-languages=c,c++' to
2712 configure GCC for building a CR16 uclinux cross-compiler.
2717 CRIS is the CPU architecture in Axis Communications ETRAX
2718 system-on-a-chip series. These are used in embedded applications.
2720 *Note CRIS Options: (gcc)CRIS Options, for a list of CRIS-specific
2723 There are a few different CRIS targets:
2725 Mainly for monolithic embedded systems. Includes a multilib for
2726 the `v10' core used in `ETRAX 100 LX'.
2728 `cris-axis-linux-gnu'
2729 A GNU/Linux port for the CRIS architecture, currently targeting
2730 `ETRAX 100 LX' by default.
2732 For `cris-axis-elf' you need binutils 2.11 or newer. For
2733 `cris-axis-linux-gnu' you need binutils 2.12 or newer.
2735 Pre-packaged tools can be obtained from
2736 `ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/'. More
2737 information about this platform is available at
2738 `http://developer.axis.com/'.
2743 Please have a look at the binaries page.
2745 You cannot install GCC by itself on MSDOS; it will not compile under
2746 any MSDOS compiler except itself. You need to get the complete
2747 compilation package DJGPP, which includes binaries as well as sources,
2748 and includes all the necessary compilation tools and libraries.
2753 Adapteva Epiphany. This configuration is intended for embedded systems.
2758 Support for FreeBSD 1 was discontinued in GCC 3.2. Support for FreeBSD
2759 2 (and any mutant a.out variants of FreeBSD 3) was discontinued in GCC
2762 In order to better utilize FreeBSD base system functionality and
2763 match the configuration of the system compiler, GCC 4.5 and above as
2764 well as GCC 4.4 past 2010-06-20 leverage SSP support in libc (which is
2765 present on FreeBSD 7 or later) and the use of `__cxa_atexit' by default
2766 (on FreeBSD 6 or later). The use of `dl_iterate_phdr' inside
2767 `libgcc_s.so.1' and boehm-gc (on FreeBSD 7 or later) is enabled by GCC
2770 We support FreeBSD using the ELF file format with DWARF 2 debugging
2771 for all CPU architectures. You may use `-gstabs' instead of `-g', if
2772 you really want the old debugging format. There are no known issues
2773 with mixing object files and libraries with different debugging
2774 formats. Otherwise, this release of GCC should now match more of the
2775 configuration used in the stock FreeBSD configuration of GCC. In
2776 particular, `--enable-threads' is now configured by default. However,
2777 as a general user, do not attempt to replace the system compiler with
2778 this release. Known to bootstrap and check with good results on
2779 FreeBSD 7.2-STABLE. In the past, known to bootstrap and check with
2780 good results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4, 4.5, 4.8, 4.9 and
2783 The version of binutils installed in `/usr/bin' probably works with
2784 this release of GCC. Bootstrapping against the latest GNU binutils
2785 and/or the version found in `/usr/ports/devel/binutils' has been known
2786 to enable additional features and improve overall testsuite results.
2787 However, it is currently known that boehm-gc (which itself is required
2788 for java) may not configure properly on FreeBSD prior to the FreeBSD
2789 7.0 release with GNU binutils after 2.16.1.
2794 Renesas H8/300 series of processors.
2796 Please have a look at the binaries page.
2798 The calling convention and structure layout has changed in release
2799 2.6. All code must be recompiled. The calling convention now passes
2800 the first three arguments in function calls in registers. Structures
2801 are no longer a multiple of 2 bytes.
2806 Support for HP-UX version 9 and older was discontinued in GCC 3.4.
2808 We require using gas/binutils on all hppa platforms. Version 2.19 or
2809 later is recommended.
2811 It may be helpful to configure GCC with the `--with-gnu-as' and
2812 `--with-as=...' options to ensure that GCC can find GAS.
2814 The HP assembler should not be used with GCC. It is rarely tested
2815 and may not work. It shouldn't be used with any languages other than C
2816 due to its many limitations.
2818 Specifically, `-g' does not work (HP-UX uses a peculiar debugging
2819 format which GCC does not know about). It also inserts timestamps into
2820 each object file it creates, causing the 3-stage comparison test to
2821 fail during a bootstrap. You should be able to continue by saying
2822 `make all-host all-target' after getting the failure from `make'.
2824 Various GCC features are not supported. For example, it does not
2825 support weak symbols or alias definitions. As a result, explicit
2826 template instantiations are required when using C++. This makes it
2827 difficult if not impossible to build many C++ applications.
2829 There are two default scheduling models for instructions. These are
2830 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
2831 architecture specified for the target machine when configuring.
2832 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when the
2833 target is a `hppa1*' machine.
2835 The PROCESSOR_8000 model is not well suited to older processors.
2836 Thus, it is important to completely specify the machine architecture
2837 when configuring if you want a model other than PROCESSOR_8000. The
2838 macro TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
2839 default scheduling model is desired.
2841 As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
2842 through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
2843 This namespace change might cause problems when bootstrapping with an
2844 earlier version of GCC or the HP compiler as essentially the same
2845 namespace is required for an entire build. This problem can be avoided
2846 in a number of ways. With HP cc, `UNIX_STD' can be set to `95' or
2847 `98'. Another way is to add an appropriate set of predefines to `CC'.
2848 The description for the `munix=' option contains a list of the
2849 predefines used with each standard.
2851 More specific information to `hppa*-hp-hpux*' targets follows.
2856 For hpux10.20, we _highly_ recommend you pick up the latest sed patch
2857 `PHCO_19798' from HP.
2859 The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces
2860 are used for one-only code and data. This resolves many of the previous
2861 problems in using C++ on this target. However, the ABI is not
2862 compatible with the one implemented under HP-UX 11 using secondary
2868 GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
2869 be used to compile GCC 3.0 and up.
2871 The libffi and libjava libraries haven't been ported to 64-bit HP-UX
2874 Refer to binaries for information about obtaining precompiled GCC
2875 binaries for HP-UX. Precompiled binaries must be obtained to build the
2876 Ada language as it can't be bootstrapped using C. Ada is only
2877 available for the 32-bit PA-RISC runtime.
2879 Starting with GCC 3.4 an ISO C compiler is required to bootstrap.
2880 The bundled compiler supports only traditional C; you will need either
2881 HP's unbundled compiler, or a binary distribution of GCC.
2883 It is possible to build GCC 3.3 starting with the bundled HP
2884 compiler, but the process requires several steps. GCC 3.3 can then be
2885 used to build later versions. The fastjar program contains ISO C code
2886 and can't be built with the HP bundled compiler. This problem can be
2887 avoided by not building the Java language. For example, use the
2888 `--enable-languages="c,c++,f77,objc"' option in your configure command.
2890 There are several possible approaches to building the distribution.
2891 Binutils can be built first using the HP tools. Then, the GCC
2892 distribution can be built. The second approach is to build GCC first
2893 using the HP tools, then build binutils, then rebuild GCC. There have
2894 been problems with various binary distributions, so it is best not to
2895 start from a binary distribution.
2897 On 64-bit capable systems, there are two distinct targets. Different
2898 installation prefixes must be used if both are to be installed on the
2899 same system. The `hppa[1-2]*-hp-hpux11*' target generates code for the
2900 32-bit PA-RISC runtime architecture and uses the HP linker. The
2901 `hppa64-hp-hpux11*' target generates 64-bit code for the PA-RISC 2.0
2904 The script config.guess now selects the target type based on the
2905 compiler detected during configuration. You must define `PATH' or `CC'
2906 so that configure finds an appropriate compiler for the initial
2907 bootstrap. When `CC' is used, the definition should contain the
2908 options that are needed whenever `CC' is used.
2910 Specifically, options that determine the runtime architecture must be
2911 in `CC' to correctly select the target for the build. It is also
2912 convenient to place many other compiler options in `CC'. For example,
2913 `CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"' can
2914 be used to bootstrap the GCC 3.3 branch with the HP compiler in 64-bit
2915 K&R/bundled mode. The `+DA2.0W' option will result in the automatic
2916 selection of the `hppa64-hp-hpux11*' target. The macro definition
2917 table of cpp needs to be increased for a successful build with the HP
2918 compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to be defined when
2919 building with the bundled compiler, or when using the `-Ac' option.
2920 These defines aren't necessary with `-Ae'.
2922 It is best to explicitly configure the `hppa64-hp-hpux11*' target
2923 with the `--with-ld=...' option. This overrides the standard search
2924 for ld. The two linkers supported on this target require different
2925 commands. The default linker is determined during configuration. As a
2926 result, it's not possible to switch linkers in the middle of a GCC
2927 build. This has been reported to sometimes occur in unified builds of
2930 A recent linker patch must be installed for the correct operation of
2931 GCC 3.3 and later. `PHSS_26559' and `PHSS_24304' are the oldest linker
2932 patches that are known to work. They are for HP-UX 11.00 and 11.11,
2933 respectively. `PHSS_24303', the companion to `PHSS_24304', might be
2934 usable but it hasn't been tested. These patches have been superseded.
2935 Consult the HP patch database to obtain the currently recommended
2936 linker patch for your system.
2938 The patches are necessary for the support of weak symbols on the
2939 32-bit port, and for the running of initializers and finalizers. Weak
2940 symbols are implemented using SOM secondary definition symbols. Prior
2941 to HP-UX 11, there are bugs in the linker support for secondary symbols.
2942 The patches correct a problem of linker core dumps creating shared
2943 libraries containing secondary symbols, as well as various other
2944 linking issues involving secondary symbols.
2946 GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
2947 run initializers and finalizers on the 64-bit port. The 32-bit port
2948 uses the linker `+init' and `+fini' options for the same purpose. The
2949 patches correct various problems with the +init/+fini options,
2950 including program core dumps. Binutils 2.14 corrects a problem on the
2951 64-bit port resulting from HP's non-standard use of the .init and .fini
2952 sections for array initializers and finalizers.
2954 Although the HP and GNU linkers are both supported for the
2955 `hppa64-hp-hpux11*' target, it is strongly recommended that the HP
2956 linker be used for link editing on this target.
2958 At this time, the GNU linker does not support the creation of long
2959 branch stubs. As a result, it can't successfully link binaries
2960 containing branch offsets larger than 8 megabytes. In addition, there
2961 are problems linking shared libraries, linking executables with
2962 `-static', and with dwarf2 unwind and exception support. It also
2963 doesn't provide stubs for internal calls to global functions in shared
2964 libraries, so these calls can't be overloaded.
2966 The HP dynamic loader does not support GNU symbol versioning, so
2967 symbol versioning is not supported. It may be necessary to disable
2968 symbol versioning with `--disable-symvers' when using GNU ld.
2970 POSIX threads are the default. The optional DCE thread library is
2971 not supported, so `--enable-threads=dce' does not work.
2976 Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present
2977 in glibc 2.2.5 and later. More information is available in the
2978 libstdc++-v3 documentation.
2983 As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
2984 See bug 10877 for more information.
2986 If you receive Signal 11 errors when building on GNU/Linux, then it
2987 is possible you have a hardware problem. Further information on this
2988 can be found on www.bitwizard.nl.
2990 i?86-*-solaris2.[89]
2991 ====================
2993 The Sun assembler in Solaris 8 and 9 has several bugs and limitations.
2994 While GCC works around them, several features are missing, so it is
2995 recommended to use the GNU assembler instead. There is no bundled
2996 version, but the current version, from GNU binutils 2.22, is known to
2999 Solaris 2/x86 doesn't support the execution of SSE/SSE2 instructions
3000 before Solaris 9 4/04, even if the CPU supports them. Programs will
3001 receive `SIGILL' if they try. The fix is available both in Solaris 9
3002 Update 6 and kernel patch 112234-12 or newer. There is no
3003 corresponding patch for Solaris 8. To avoid this problem, `-march'
3004 defaults to `pentiumpro' on Solaris 8 and 9. If you have the patch
3005 installed, you can configure GCC with an appropriate `--with-arch'
3006 option, but need GNU `as' for SSE2 support.
3011 Use this for Solaris 10 or later on x86 and x86-64 systems. Starting
3012 with GCC 4.7, there is also a 64-bit `amd64-*-solaris2.1[0-9]*' or
3013 `x86_64-*-solaris2.1[0-9]*' configuration that corresponds to
3014 `sparcv9-sun-solaris2*'.
3016 It is recommended that you configure GCC to use the GNU assembler, in
3017 `/usr/sfw/bin/gas'. The versions included in Solaris 10, from GNU
3018 binutils 2.15, and Solaris 11, from GNU binutils 2.19, work fine,
3019 although the current version, from GNU binutils 2.22, is known to work,
3020 too. Recent versions of the Sun assembler in `/usr/ccs/bin/as' work
3021 almost as well, though.
3023 For linking, the Sun linker, is preferred. If you want to use the
3024 GNU linker instead, which is available in `/usr/sfw/bin/gld', note that
3025 due to a packaging bug the version in Solaris 10, from GNU binutils
3026 2.15, cannot be used, while the version in Solaris 11, from GNU binutils
3027 2.19, works, as does the latest version, from GNU binutils 2.22.
3029 To use GNU `as', configure with the options `--with-gnu-as
3030 --with-as=/usr/sfw/bin/gas'. It may be necessary to configure with
3031 `--without-gnu-ld --with-ld=/usr/ccs/bin/ld' to guarantee use of Sun
3037 IA-64 processor (also known as IPF, or Itanium Processor Family)
3040 If you are using the installed system libunwind library with
3041 `--with-system-libunwind', then you must use libunwind 0.98 or later.
3043 None of the following versions of GCC has an ABI that is compatible
3044 with any of the other versions in this list, with the exception that
3045 Red Hat 2.96 and Trillian 000171 are compatible with each other: 3.1,
3046 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717. This primarily
3047 affects C++ programs and programs that create shared libraries. GCC
3048 3.1 or later is recommended for compiling linux, the kernel. As of
3049 version 3.1 GCC is believed to be fully ABI compliant, and hence no
3050 more major ABI changes are expected.
3055 Building GCC on this target requires the GNU Assembler. The bundled HP
3056 assembler will not work. To prevent GCC from using the wrong assembler,
3057 the option `--with-gnu-as' may be necessary.
3059 The GCC libunwind library has not been ported to HPUX. This means
3060 that for GCC versions 3.2.3 and earlier, `--enable-libunwind-exceptions'
3061 is required to build GCC. For GCC 3.3 and later, this is the default.
3062 For gcc 3.4.3 and later, `--enable-libunwind-exceptions' is removed and
3063 the system libunwind library will always be used.
3068 Support for AIX version 3 and older was discontinued in GCC 3.4.
3069 Support for AIX version 4.2 and older was discontinued in GCC 4.5.
3071 "out of memory" bootstrap failures may indicate a problem with
3072 process resource limits (ulimit). Hard limits are configured in the
3073 `/etc/security/limits' system configuration file.
3075 GCC can bootstrap with recent versions of IBM XLC, but bootstrapping
3076 with an earlier release of GCC is recommended. Bootstrapping with XLC
3077 requires a larger data segment, which can be enabled through the
3078 LDR_CNTRL environment variable, e.g.,
3080 % LDR_CNTRL=MAXDATA=0x50000000
3083 One can start with a pre-compiled version of GCC to build from
3084 sources. One may delete GCC's "fixed" header files when starting with
3085 a version of GCC built for an earlier release of AIX.
3087 To speed up the configuration phases of bootstrapping and installing
3088 GCC, one may use GNU Bash instead of AIX `/bin/sh', e.g.,
3090 % CONFIG_SHELL=/opt/freeware/bin/bash
3091 % export CONFIG_SHELL
3093 and then proceed as described in the build instructions, where we
3094 strongly recommend specifying an absolute path to invoke
3097 Because GCC on AIX is built as a 32-bit executable by default,
3098 (although it can generate 64-bit programs) the GMP and MPFR libraries
3099 required by gfortran must be 32-bit libraries. Building GMP and MPFR
3100 as static archive libraries works better than shared libraries.
3102 Errors involving `alloca' when building GCC generally are due to an
3103 incorrect definition of `CC' in the Makefile or mixing files compiled
3104 with the native C compiler and GCC. During the stage1 phase of the
3105 build, the native AIX compiler *must* be invoked as `cc' (not `xlc').
3106 Once `configure' has been informed of `xlc', one needs to use `make
3107 distclean' to remove the configure cache files and ensure that `CC'
3108 environment variable does not provide a definition that will confuse
3109 `configure'. If this error occurs during stage2 or later, then the
3110 problem most likely is the version of Make (see above).
3112 The native `as' and `ld' are recommended for bootstrapping on AIX.
3113 The GNU Assembler, GNU Linker, and GNU Binutils version 2.20 is
3114 required to bootstrap on AIX 5. The native AIX tools do interoperate
3117 AIX 5.3 TL10, AIX 6.1 TL05 and AIX 7.1 TL00 introduced an AIX
3118 assembler change that sometimes produces corrupt assembly files causing
3119 AIX linker errors. The bug breaks GCC bootstrap on AIX and can cause
3120 compilation failures with existing GCC installations. An AIX iFix for
3121 AIX 5.3 is available (APAR IZ98385 for AIX 5.3 TL10, APAR IZ98477 for
3122 AIX 5.3 TL11 and IZ98134 for AIX 5.3 TL12). Fixes for AIX 6.1 (APAR
3123 IZ98732 for AIX 6.1 TL05 and APAR IZ98861 for AIX 6.1 TL06) and AIX 7.1
3124 are in verification and packaging phases.
3126 Building `libstdc++.a' requires a fix for an AIX Assembler bug APAR
3127 IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a fix
3128 for another AIX Assembler bug and a co-dependent AIX Archiver fix
3129 referenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1)
3131 `libstdc++' in GCC 3.4 increments the major version number of the
3132 shared object and GCC installation places the `libstdc++.a' shared
3133 library in a common location which will overwrite the and GCC 3.3
3134 version of the shared library. Applications either need to be
3135 re-linked against the new shared library or the GCC 3.1 and GCC 3.3
3136 versions of the `libstdc++' shared object needs to be available to the
3137 AIX runtime loader. The GCC 3.1 `libstdc++.so.4', if present, and GCC
3138 3.3 `libstdc++.so.5' shared objects can be installed for runtime
3139 dynamic loading using the following steps to set the `F_LOADONLY' flag
3140 in the shared object for _each_ multilib `libstdc++.a' installed:
3142 Extract the shared objects from the currently installed
3143 `libstdc++.a' archive:
3144 % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
3146 Enable the `F_LOADONLY' flag so that the shared object will be
3147 available for runtime dynamic loading, but not linking:
3148 % strip -e libstdc++.so.4 libstdc++.so.5
3150 Archive the runtime-only shared object in the GCC 3.4 `libstdc++.a'
3152 % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
3154 Linking executables and shared libraries may produce warnings of
3155 duplicate symbols. The assembly files generated by GCC for AIX always
3156 have included multiple symbol definitions for certain global variable
3157 and function declarations in the original program. The warnings should
3158 not prevent the linker from producing a correct library or runnable
3161 AIX 4.3 utilizes a "large format" archive to support both 32-bit and
3162 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
3163 to parse archive libraries did not handle the new format correctly.
3164 These routines are used by GCC and result in error messages during
3165 linking such as "not a COFF file". The version of the routines shipped
3166 with AIX 4.3.1 should work for a 32-bit environment. The `-g' option
3167 of the archive command may be used to create archives of 32-bit objects
3168 using the original "small format". A correct version of the routines
3169 is shipped with AIX 4.3.2 and above.
3171 Some versions of the AIX binder (linker) can fail with a relocation
3172 overflow severe error when the `-bbigtoc' option is used to link
3173 GCC-produced object files into an executable that overflows the TOC. A
3174 fix for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC)
3175 is available from IBM Customer Support and from its
3176 techsupport.services.ibm.com website as PTF U455193.
3178 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump
3179 core with a segmentation fault when invoked by any version of GCC. A
3180 fix for APAR IX87327 is available from IBM Customer Support and from its
3181 techsupport.services.ibm.com website as PTF U461879. This fix is
3182 incorporated in AIX 4.3.3 and above.
3184 The initial assembler shipped with AIX 4.3.0 generates incorrect
3185 object files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM
3186 COMPILER FAILS TO ASSEMBLE/BIND) is available from IBM Customer Support
3187 and from its techsupport.services.ibm.com website as PTF U453956. This
3188 fix is incorporated in AIX 4.3.1 and above.
3190 AIX provides National Language Support (NLS). Compilers and
3191 assemblers use NLS to support locale-specific representations of
3192 various data formats including floating-point numbers (e.g., `.' vs
3193 `,' for separating decimal fractions). There have been problems
3194 reported where GCC does not produce the same floating-point formats
3195 that the assembler expects. If one encounters this problem, set the
3196 `LANG' environment variable to `C' or `En_US'.
3198 A default can be specified with the `-mcpu=CPU_TYPE' switch and
3199 using the configure option `--with-cpu-CPU_TYPE'.
3204 Vitesse IQ2000 processors. These are used in embedded applications.
3205 There are no standard Unix configurations.
3210 Lattice Mico32 processor. This configuration is intended for embedded
3216 Lattice Mico32 processor. This configuration is intended for embedded
3217 systems running uClinux.
3222 Renesas M32C processor. This configuration is intended for embedded
3228 Renesas M32R processor. This configuration is intended for embedded
3234 By default, `m68k-*-elf*', `m68k-*-rtems', `m68k-*-uclinux' and
3235 `m68k-*-linux' build libraries for both M680x0 and ColdFire processors.
3236 If you only need the M680x0 libraries, you can omit the ColdFire ones
3237 by passing `--with-arch=m68k' to `configure'. Alternatively, you can
3238 omit the M680x0 libraries by passing `--with-arch=cf' to `configure'.
3239 These targets default to 5206 or 5475 code as appropriate for the
3240 target system when configured with `--with-arch=cf' and 68020 code
3243 The `m68k-*-netbsd' and `m68k-*-openbsd' targets also support the
3244 `--with-arch' option. They will generate ColdFire CFV4e code when
3245 configured with `--with-arch=cf' and 68020 code otherwise.
3247 You can override the default processors listed above by configuring
3248 with `--with-cpu=TARGET'. This TARGET can either be a `-mcpu' argument
3249 or one of the following values: `m68000', `m68010', `m68020', `m68030',
3250 `m68040', `m68060', `m68020-40' and `m68020-60'.
3252 GCC requires at least binutils version 2.17 on these targets.
3257 GCC 4.3 changed the uClinux configuration so that it uses the
3258 `m68k-linux-gnu' ABI rather than the `m68k-elf' ABI. It also added
3259 improved support for C++ and flat shared libraries, both of which were
3265 Toshiba Media embedded Processor. This configuration is intended for
3271 Xilinx MicroBlaze processor. This configuration is intended for
3277 If on a MIPS system you get an error message saying "does not have gp
3278 sections for all it's [sic] sectons [sic]", don't worry about it. This
3279 happens whenever you use GAS with the MIPS linker, but there is not
3280 really anything wrong, and it is okay to use the output file. You can
3281 stop such warnings by installing the GNU linker.
3283 It would be nice to extend GAS to produce the gp tables, but they are
3284 optional, and there should not be a warning about their absence.
3286 The libstdc++ atomic locking routines for MIPS targets requires MIPS
3287 II and later. A patch went in just after the GCC 3.3 release to make
3288 `mips*-*-*' use the generic implementation instead. You can also
3289 configure for `mipsel-elf' as a workaround. The `mips*-*-linux*'
3290 target continues to use the MIPS II routines. More work on this is
3291 expected in future releases.
3293 The built-in `__sync_*' functions are available on MIPS II and later
3294 systems and others that support the `ll', `sc' and `sync' instructions.
3295 This can be overridden by passing `--with-llsc' or `--without-llsc'
3296 when configuring GCC. Since the Linux kernel emulates these
3297 instructions if they are missing, the default for `mips*-*-linux*'
3298 targets is `--with-llsc'. The `--with-llsc' and `--without-llsc'
3299 configure options may be overridden at compile time by passing the
3300 `-mllsc' or `-mno-llsc' options to the compiler.
3302 MIPS systems check for division by zero (unless
3303 `-mno-check-zero-division' is passed to the compiler) by generating
3304 either a conditional trap or a break instruction. Using trap results
3305 in smaller code, but is only supported on MIPS II and later. Also,
3306 some versions of the Linux kernel have a bug that prevents trap from
3307 generating the proper signal (`SIGFPE'). To enable the use of break,
3308 use the `--with-divide=breaks' `configure' option when configuring GCC.
3309 The default is to use traps on systems that support them.
3311 The assembler from GNU binutils 2.17 and earlier has a bug in the way
3312 it sorts relocations for REL targets (o32, o64, EABI). This can cause
3313 bad code to be generated for simple C++ programs. Also the linker from
3314 GNU binutils versions prior to 2.17 has a bug which causes the runtime
3315 linker stubs in very large programs, like `libgcj.so', to be
3316 incorrectly generated. GNU Binutils 2.18 and later (and snapshots made
3317 after Nov. 9, 2006) should be free from both of these problems.
3322 Support for IRIX 5 has been removed in GCC 4.6.
3327 Support for IRIX 6.5 has been obsoleted in GCC 4.7, but can still be
3328 enabled by configuring with `--enable-obsolete'. Support will be
3329 removed in GCC 4.8. Support for IRIX 6 releases before 6.5 has been
3330 removed in GCC 4.6, as well as support for the O32 ABI. It is
3331 _strongly_ recommended to upgrade to at least IRIX 6.5.18. This
3332 release introduced full ISO C99 support, though for the N32 and N64 ABIs
3335 To build and use GCC on IRIX 6.5, you need the IRIX Development
3336 Foundation (IDF) and IRIX Development Libraries (IDL). They are
3337 included with the IRIX 6.5 media.
3339 If you are using SGI's MIPSpro `cc' as your bootstrap compiler, you
3340 must ensure that the N32 ABI is in use. To test this, compile a simple
3341 C file with `cc' and then run `file' on the resulting object file. The
3342 output should look like:
3344 test.o: ELF N32 MSB ...
3348 test.o: ELF 32-bit MSB ...
3352 test.o: ELF 64-bit MSB ...
3354 then your version of `cc' uses the O32 or N64 ABI by default. You
3355 should set the environment variable `CC' to `cc -n32' before
3358 If you want the resulting `gcc' to run on old 32-bit systems with
3359 the MIPS R4400 CPU, you need to ensure that only code for the `mips3'
3360 instruction set architecture (ISA) is generated. While GCC 3.x does
3361 this correctly, both GCC 2.95 and SGI's MIPSpro `cc' may change the ISA
3362 depending on the machine where GCC is built. Using one of them as the
3363 bootstrap compiler may result in `mips4' code, which won't run at all
3364 on `mips3'-only systems. For the test program above, you should see:
3366 test.o: ELF N32 MSB mips-3 ...
3370 test.o: ELF N32 MSB mips-4 ...
3372 instead, you should set the environment variable `CC' to `cc -n32
3373 -mips3' or `gcc -mips3' respectively before configuring GCC.
3375 MIPSpro C 7.4 may cause bootstrap failures, due to a bug when
3376 inlining `memcmp'. Either add `-U__INLINE_INTRINSICS' to the `CC'
3377 environment variable as a workaround or upgrade to MIPSpro C 7.4.1m.
3379 GCC on IRIX 6.5 is usually built to support the N32 and N64 ABIs. If
3380 you build GCC on a system that doesn't have the N64 libraries installed
3381 or cannot run 64-bit binaries, you need to configure with
3382 `--disable-multilib' so GCC doesn't try to use them. Look for
3383 `/usr/lib64/libc.so.1' to see if you have the 64-bit libraries
3386 GCC must be configured with GNU `as'. The latest version, from GNU
3387 binutils 2.22, is known to work. On the other hand, bootstrap fails
3388 with GNU `ld' at least since GNU binutils 2.17.
3390 The `--enable-libgcj' option is disabled by default: IRIX 6 uses a
3391 very low default limit (20480) for the command line length. Although
3392 `libtool' contains a workaround for this problem, at least the N64
3393 `libgcj' is known not to build despite this, running into an internal
3394 error of the native `ld'. A sure fix is to increase this limit
3395 (`ncargs') to its maximum of 262144 bytes. If you have root access,
3396 you can use the `systune' command to do this.
3398 `wchar_t' support in `libstdc++' is not available for old IRIX 6.5.x
3399 releases, x < 19. The problem cannot be autodetected and in order to
3400 build GCC for such targets you need to configure with
3401 `--disable-wchar_t'.
3406 The moxie processor. See `http://moxielogic.org/' for more information
3407 about this processor.
3412 You can specify a default version for the `-mcpu=CPU_TYPE' switch by
3413 using the configure option `--with-cpu-CPU_TYPE'.
3415 You will need binutils 2.15 or newer for a working GCC.
3420 PowerPC running Darwin (Mac OS X kernel).
3422 Pre-installed versions of Mac OS X may not include any developer
3423 tools, meaning that you will not be able to build GCC from source. Tool
3424 binaries are available at `http://opensource.apple.com/'.
3426 This version of GCC requires at least cctools-590.36. The
3427 cctools-590.36 package referenced from
3428 `http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html' will not work on
3429 systems older than 10.3.9 (aka darwin7.9.0).
3434 PowerPC system in big endian mode, running System V.4.
3436 powerpc*-*-linux-gnu*
3437 =====================
3439 PowerPC system in big endian mode running Linux.
3444 PowerPC system in big endian mode running NetBSD.
3449 Embedded PowerPC system in big endian mode for use in running under the
3455 Embedded PowerPC system in big endian mode.
3460 PowerPC system in little endian mode, running System V.4.
3465 Embedded PowerPC system in little endian mode for use in running under
3471 Embedded PowerPC system in little endian mode.
3476 The Renesas RL78 processor. This configuration is intended for
3482 The Renesas RX processor. See
3483 `http://eu.renesas.com/fmwk.jsp?cnt=rx600_series_landing.jsp&fp=/products/mpumcu/rx_family/rx600_series'
3484 for more information about this processor.
3489 S/390 system running GNU/Linux for S/390.
3494 zSeries system (64-bit) running GNU/Linux for zSeries.
3499 zSeries system (64-bit) running TPF. This platform is supported as
3500 cross-compilation target only.
3505 Support for Solaris 8 has been obsoleted in GCC 4.7, but can still be
3506 enabled by configuring with `--enable-obsolete'. Support will be
3507 removed in GCC 4.8. Support for Solaris 7 has been removed in GCC 4.6.
3509 Sun does not ship a C compiler with Solaris 2 before Solaris 10,
3510 though you can download the Sun Studio compilers for free. In Solaris
3511 10 and 11, GCC 3.4.3 is available as `/usr/sfw/bin/gcc'. Solaris 11
3512 also provides GCC 4.5.2 as `/usr/gcc/4.5/bin/gcc'. Alternatively, you
3513 can install a pre-built GCC to bootstrap and install GCC. See the
3514 binaries page for details.
3516 The Solaris 2 `/bin/sh' will often fail to configure `libstdc++-v3',
3517 `boehm-gc' or `libjava'. We therefore recommend using the following
3518 initial sequence of commands
3520 % CONFIG_SHELL=/bin/ksh
3521 % export CONFIG_SHELL
3523 and proceed as described in the configure instructions. In addition we
3524 strongly recommend specifying an absolute path to invoke
3527 Solaris 2 comes with a number of optional OS packages. Some of these
3528 are needed to use GCC fully, namely `SUNWarc', `SUNWbtool', `SUNWesu',
3529 `SUNWhea', `SUNWlibm', `SUNWsprot', and `SUNWtoo'. If you did not
3530 install all optional packages when installing Solaris 2, you will need
3531 to verify that the packages that GCC needs are installed.
3533 To check whether an optional package is installed, use the `pkginfo'
3534 command. To add an optional package, use the `pkgadd' command. For
3535 further details, see the Solaris 2 documentation.
3537 Trying to use the linker and other tools in `/usr/ucb' to install
3538 GCC has been observed to cause trouble. For example, the linker may
3539 hang indefinitely. The fix is to remove `/usr/ucb' from your `PATH'.
3541 The build process works more smoothly with the legacy Sun tools so,
3542 if you have `/usr/xpg4/bin' in your `PATH', we recommend that you place
3543 `/usr/bin' before `/usr/xpg4/bin' for the duration of the build.
3545 We recommend the use of the Sun assembler or the GNU assembler, in
3546 conjunction with the Sun linker. The GNU `as' versions included in
3547 Solaris 10, from GNU binutils 2.15, and Solaris 11, from GNU binutils
3548 2.19, are known to work. They can be found in `/usr/sfw/bin/gas'.
3549 Current versions of GNU binutils (2.22) are known to work as well.
3550 Note that your mileage may vary if you use a combination of the GNU
3551 tools and the Sun tools: while the combination GNU `as' + Sun `ld'
3552 should reasonably work, the reverse combination Sun `as' + GNU `ld' may
3553 fail to build or cause memory corruption at runtime in some cases for
3554 C++ programs. GNU `ld' usually works as well, although the version
3555 included in Solaris 10 cannot be used due to several bugs. Again, the
3556 current version (2.22) is known to work, but generally lacks platform
3557 specific features, so better stay with Sun `ld'. To use the LTO linker
3558 plugin (`-fuse-linker-plugin') with GNU `ld', GNU binutils _must_ be
3559 configured with `--enable-largefile'.
3561 To enable symbol versioning in `libstdc++' with Sun `ld', you need
3562 to have any version of GNU `c++filt', which is part of GNU binutils.
3563 `libstdc++' symbol versioning will be disabled if no appropriate
3564 version is found. Sun `c++filt' from the Sun Studio compilers does
3567 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3568 newer: `g++' will complain that types are missing. These headers
3569 assume that omitting the type means `int'; this assumption worked for
3570 C90 but is wrong for C++, and is now wrong for C99 also.
3572 `g++' accepts such (invalid) constructs with the option
3573 `-fpermissive'; it will assume that any missing type is `int' (as
3576 There are patches for Solaris 8 (108652-24 or newer for SPARC,
3577 108653-22 for Intel) that fix this bug.
3579 Sun bug 4927647 sometimes causes random spurious testsuite failures
3580 related to missing diagnostic output. This bug doesn't affect GCC
3581 itself, rather it is a kernel bug triggered by the `expect' program
3582 which is used only by the GCC testsuite driver. When the bug causes
3583 the `expect' program to miss anticipated output, extra testsuite
3586 There are patches for Solaris 8 (117350-12 or newer for SPARC,
3587 117351-12 or newer for Intel) and Solaris 9 (117171-11 or newer for
3588 SPARC, 117172-11 or newer for Intel) that address this problem.
3590 Solaris 8 provides an alternate implementation of the thread library
3591 `libthread'. It is required for TLS support and has been made the
3592 default in Solaris 9, so it is always used on Solaris 8.
3594 Thread-local storage (TLS) is supported in Solaris 8 and 9, but
3595 requires some patches. The `libthread' patches provide the
3596 `__tls_get_addr' (SPARC, 64-bit x86) resp. `___tls_get_addr' (32-bit
3597 x86) functions. On Solaris 8, you need 108993-26 or newer on SPARC,
3598 108994-26 or newer on Intel. On Solaris 9, the necessary support on
3599 SPARC is present since FCS, while 114432-05 or newer is required on
3600 Intel. Additionally, on Solaris 8, patch 109147-14 or newer on SPARC or
3601 109148-22 or newer on Intel are required for the Sun `ld' and runtime
3602 linker (`ld.so.1') support. Again, Solaris 9/SPARC works since FCS,
3603 while 113986-02 is required on Intel. The linker patches must be
3604 installed even if GNU `ld' is used. Sun `as' in Solaris 8 and 9 doesn't
3605 support the necessary relocations, so GNU `as' must be used. The
3606 `configure' script checks for those prerequisites and automatically
3607 enables TLS support if they are met. Although those minimal patch
3608 versions should work, it is recommended to use the latest patch
3609 versions which include additional bug fixes.
3614 This section contains general configuration information for all
3615 SPARC-based platforms. In addition to reading this section, please
3616 read all other sections that match your target.
3618 Newer versions of the GNU Multiple Precision Library (GMP), the MPFR
3619 library and the MPC library are known to be miscompiled by earlier
3620 versions of GCC on these platforms. We therefore recommend the use of
3621 the exact versions of these libraries listed as minimal versions in the
3627 When GCC is configured to use GNU binutils 2.14 or later, the binaries
3628 produced are smaller than the ones produced using Sun's native tools;
3629 this difference is quite significant for binaries containing debugging
3632 Starting with Solaris 7, the operating system is capable of executing
3633 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports this;
3634 the `-m64' option enables 64-bit code generation. However, if all you
3635 want is code tuned for the UltraSPARC CPU, you should try the
3636 `-mtune=ultrasparc' option instead, which produces code that, unlike
3637 full 64-bit code, can still run on non-UltraSPARC machines.
3639 When configuring on a Solaris 7 or later system that is running a
3640 kernel that supports only 32-bit binaries, one must configure with
3641 `--disable-multilib', since we will not be able to build the 64-bit
3644 GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions
3645 of the GNU compiler (especially GCC 3.0.x versions), which lead to the
3646 miscompilation of the stage1 compiler and the subsequent failure of the
3647 bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary
3648 stage, i.e. to bootstrap that compiler with the base compiler and then
3649 use it to bootstrap the final compiler.
3651 GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE
3652 Studio 7) and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes
3653 a bootstrap failure in form of a miscompilation of the stage1 compiler
3654 by the Sun compiler. This is Sun bug 4974440. This is fixed with
3657 GCC 3.4 changed the default debugging format from Stabs to DWARF-2
3658 for 32-bit code on Solaris 7 and later. If you use the Sun assembler,
3659 this change apparently runs afoul of Sun bug 4910101 (which is
3660 referenced as an x86-only problem by Sun, probably because they do not
3661 use DWARF-2). A symptom of the problem is that you cannot compile C++
3662 programs like `groff' 1.19.1 without getting messages similar to the
3665 ld: warning: relocation error: R_SPARC_UA32: ...
3666 external symbolic relocation against non-allocatable section
3667 .debug_info cannot be processed at runtime: relocation ignored.
3669 To work around this problem, compile with `-gstabs+' instead of plain
3672 When configuring the GNU Multiple Precision Library (GMP), the MPFR
3673 library or the MPC library on a Solaris 7 or later system, the canonical
3674 target triplet must be specified as the `build' parameter on the
3675 configure line. This target triplet can be obtained by invoking
3676 `./config.guess' in the toplevel source directory of GCC (and not that
3677 of GMP or MPFR or MPC). For example on a Solaris 9 system:
3679 % ./configure --build=sparc-sun-solaris2.9 --prefix=xxx
3681 sparc-sun-solaris2.10
3682 =====================
3684 There is a bug in older versions of the Sun assembler which breaks
3685 thread-local storage (TLS). A typical error message is
3687 ld: fatal: relocation error: R_SPARC_TLS_LE_HIX22: file /var/tmp//ccamPA1v.o:
3688 symbol <unknown>: bad symbol type SECT: symbol type must be TLS
3690 This bug is fixed in Sun patch 118683-03 or later.
3695 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4 or
3696 newer on this platform. All earlier binutils and glibc releases
3697 mishandled unaligned relocations on `sparc-*-*' targets.
3702 When configuring the GNU Multiple Precision Library (GMP), the MPFR
3703 library or the MPC library, the canonical target triplet must be
3704 specified as the `build' parameter on the configure line. For example
3705 on a Solaris 9 system:
3707 % ./configure --build=sparc64-sun-solaris2.9 --prefix=xxx
3709 The following compiler flags must be specified in the configure step
3710 in order to bootstrap this target with the Sun compiler:
3712 % CC="cc -xarch=v9 -xildoff" SRCDIR/configure [OPTIONS] [TARGET]
3714 `-xarch=v9' specifies the SPARC-V9 architecture to the Sun toolchain
3715 and `-xildoff' turns off the incremental linker.
3720 This is a synonym for `sparc64-*-solaris2*'.
3725 The C6X family of processors. This port requires binutils-2.22 or newer.
3730 The TILE-Gx processor running GNU/Linux. This port requires
3731 binutils-2.22 or newer.
3736 The TILEPro processor running GNU/Linux. This port requires
3737 binutils-2.22 or newer.
3742 Support for VxWorks is in flux. At present GCC supports _only_ the
3743 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC.
3744 We welcome patches for other architectures supported by VxWorks 5.5.
3745 Support for VxWorks AE would also be welcome; we believe this is merely
3746 a matter of writing an appropriate "configlette" (see below). We are
3747 not interested in supporting older, a.out or COFF-based, versions of
3750 VxWorks comes with an older version of GCC installed in
3751 `$WIND_BASE/host'; we recommend you do not overwrite it. Choose an
3752 installation PREFIX entirely outside $WIND_BASE. Before running
3753 `configure', create the directories `PREFIX' and `PREFIX/bin'. Link or
3754 copy the appropriate assembler, linker, etc. into `PREFIX/bin', and set
3755 your PATH to include that directory while running both `configure' and
3758 You must give `configure' the `--with-headers=$WIND_BASE/target/h'
3759 switch so that it can find the VxWorks system headers. Since VxWorks
3760 is a cross compilation target only, you must also specify
3761 `--target=TARGET'. `configure' will attempt to create the directory
3762 `PREFIX/TARGET/sys-include' and copy files into it; make sure the user
3763 running `configure' has sufficient privilege to do so.
3765 GCC's exception handling runtime requires a special "configlette"
3766 module, `contrib/gthr_supp_vxw_5x.c'. Follow the instructions in that
3767 file to add the module to your kernel build. (Future versions of
3768 VxWorks will incorporate this module.)
3770 x86_64-*-*, amd64-*-*
3771 =====================
3773 GCC supports the x86-64 architecture implemented by the AMD64 processor
3774 (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD.
3775 On GNU/Linux the default is a bi-arch compiler which is able to generate
3776 both 64-bit x86-64 and 32-bit x86 code (via the `-m32' switch).
3778 x86_64-*-solaris2.1[0-9]*
3779 =========================
3781 GCC also supports the x86-64 architecture implemented by the AMD64
3782 processor (`amd64-*-*' is an alias for `x86_64-*-*') on Solaris 10 or
3783 later. Unlike other systems, without special options a bi-arch
3784 compiler is built which generates 32-bit code by default, but can
3785 generate 64-bit x86-64 code with the `-m64' switch. Since GCC 4.7,
3786 there is also configuration that defaults to 64-bit code, but can
3787 generate 32-bit code with `-m32'. To configure and build this way, you
3788 have to provide all support libraries like `libgmp' as 64-bit code,
3789 configure with `--target=x86_64-pc-solaris2.1x' and `CC=gcc -m64'.
3794 This target is intended for embedded Xtensa systems using the `newlib'
3795 C library. It uses ELF but does not support shared objects.
3796 Designed-defined instructions specified via the Tensilica Instruction
3797 Extension (TIE) language are only supported through inline assembly.
3799 The Xtensa configuration information must be specified prior to
3800 building GCC. The `include/xtensa-config.h' header file contains the
3801 configuration information. If you created your own Xtensa
3802 configuration with the Xtensa Processor Generator, the downloaded files
3803 include a customized copy of this header file, which you can use to
3804 replace the default header file.
3809 This target is for Xtensa systems running GNU/Linux. It supports ELF
3810 shared objects and the GNU C library (glibc). It also generates
3811 position-independent code (PIC) regardless of whether the `-fpic' or
3812 `-fPIC' options are used. In other respects, this target is the same
3813 as the `xtensa*-*-elf' target.
3818 Intel 16-bit versions
3819 ---------------------
3821 The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not
3824 However, the 32-bit port has limited support for Microsoft Windows
3825 3.11 in the Win32s environment, as a target only. See below.
3827 Intel 32-bit versions
3828 ---------------------
3830 The 32-bit versions of Windows, including Windows 95, Windows NT,
3831 Windows XP, and Windows Vista, are supported by several different target
3832 platforms. These targets differ in which Windows subsystem they target
3833 and which C libraries are used.
3835 * Cygwin *-*-cygwin: Cygwin provides a user-space Linux API
3836 emulation layer in the Win32 subsystem.
3838 * Interix *-*-interix: The Interix subsystem provides native support
3841 * MinGW *-*-mingw32: MinGW is a native GCC port for the Win32
3842 subsystem that provides a subset of POSIX.
3844 * MKS i386-pc-mks: NuTCracker from MKS. See
3845 `http://www.mkssoftware.com/' for more information.
3847 Intel 64-bit versions
3848 ---------------------
3850 GCC contains support for x86-64 using the mingw-w64 runtime library,
3851 available from `http://mingw-w64.sourceforge.net/'. This library
3852 should be used with the target triple x86_64-pc-mingw32.
3854 Presently Windows for Itanium is not supported.
3859 Windows CE is supported as a target only on Hitachi SuperH
3860 (sh-wince-pe), and MIPS (mips-wince-pe).
3862 Other Windows Platforms
3863 -----------------------
3865 GCC no longer supports Windows NT on the Alpha or PowerPC.
3867 GCC no longer supports the Windows POSIX subsystem. However, it does
3868 support the Interix subsystem. See above.
3870 Old target names including *-*-winnt and *-*-windowsnt are no longer
3873 PW32 (i386-pc-pw32) support was never completed, and the project
3874 seems to be inactive. See `http://pw32.sourceforge.net/' for more
3877 UWIN support has been removed due to a lack of maintenance.
3882 Ports of GCC are included with the Cygwin environment.
3884 GCC will build under Cygwin without modification; it does not build
3885 with Microsoft's C++ compiler and there are no plans to make it do so.
3887 The Cygwin native compiler can be configured to target any 32-bit x86
3888 cpu architecture desired; the default is i686-pc-cygwin. It should be
3889 used with as up-to-date a version of binutils as possible; use either
3890 the latest official GNU binutils release in the Cygwin distribution, or
3891 version 2.20 or above if building your own.
3896 The Interix target is used by OpenNT, Interix, Services For UNIX (SFU),
3897 and Subsystem for UNIX-based Applications (SUA). Applications compiled
3898 with this target run in the Interix subsystem, which is separate from
3899 the Win32 subsystem. This target was last known to work in GCC 3.3.
3904 GCC will build with and support only MinGW runtime 3.12 and later.
3905 Earlier versions of headers are incompatible with the new default
3906 semantics of `extern inline' in `-std=c99' and `-std=gnu99' modes.
3911 GCC contains support files for many older (1980s and early 1990s) Unix
3912 variants. For the most part, support for these systems has not been
3913 deliberately removed, but it has not been maintained for several years
3914 and may suffer from bitrot.
3916 Starting with GCC 3.1, each release has a list of "obsoleted"
3917 systems. Support for these systems is still present in that release,
3918 but `configure' will fail unless the `--enable-obsolete' option is
3919 given. Unless a maintainer steps forward, support for these systems
3920 will be removed from the next release of GCC.
3922 Support for old systems as hosts for GCC can cause problems if the
3923 workarounds for compiler, library and operating system bugs affect the
3924 cleanliness or maintainability of the rest of GCC. In some cases, to
3925 bring GCC up on such a system, if still possible with current GCC, may
3926 require first installing an old version of GCC which did work on that
3927 system, and using it to compile a more recent GCC, to avoid bugs in the
3928 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
3929 `old-releases' directory on the GCC mirror sites. Header bugs may
3930 generally be avoided using `fixincludes', but bugs or deficiencies in
3931 libraries and the operating system may still cause problems.
3933 Support for older systems as targets for cross-compilation is less
3934 problematic than support for them as hosts for GCC; if an enthusiast
3935 wishes to make such a target work again (including resurrecting any of
3936 the targets that never worked with GCC 2, starting from the last
3937 version before they were removed), patches following the usual
3938 requirements would be likely to be accepted, since they should not
3939 affect the support for more modern targets.
3941 For some systems, old versions of GNU binutils may also be useful,
3942 and are available from `pub/binutils/old-releases' on sourceware.org
3945 Some of the information on specific systems above relates to such
3946 older systems, but much of the information about GCC on such systems
3947 (which may no longer be applicable to current GCC) is to be found in
3948 the GCC texinfo manual.
3950 all ELF targets (SVR4, Solaris 2, etc.)
3951 =======================================
3953 C++ support is significantly better on ELF targets if you use the GNU
3954 linker; duplicate copies of inlines, vtables and template
3955 instantiations will be discarded automatically.
3958 File: gccinstall.info, Node: Old, Next: GNU Free Documentation License, Prev: Specific, Up: Top
3960 10 Old installation documentation
3961 *********************************
3963 Note most of this information is out of date and superseded by the
3964 previous chapters of this manual. It is provided for historical
3965 reference only, because of a lack of volunteers to merge it into the
3970 * Configurations:: Configurations Supported by GCC.
3972 Here is the procedure for installing GCC on a GNU or Unix system.
3974 1. If you have chosen a configuration for GCC which requires other GNU
3975 tools (such as GAS or the GNU linker) instead of the standard
3976 system tools, install the required tools in the build directory
3977 under the names `as', `ld' or whatever is appropriate.
3979 Alternatively, you can do subsequent compilation using a value of
3980 the `PATH' environment variable such that the necessary GNU tools
3981 come before the standard system tools.
3983 2. Specify the host, build and target machine configurations. You do
3984 this when you run the `configure' script.
3986 The "build" machine is the system which you are using, the "host"
3987 machine is the system where you want to run the resulting compiler
3988 (normally the build machine), and the "target" machine is the
3989 system for which you want the compiler to generate code.
3991 If you are building a compiler to produce code for the machine it
3992 runs on (a native compiler), you normally do not need to specify
3993 any operands to `configure'; it will try to guess the type of
3994 machine you are on and use that as the build, host and target
3995 machines. So you don't need to specify a configuration when
3996 building a native compiler unless `configure' cannot figure out
3997 what your configuration is or guesses wrong.
3999 In those cases, specify the build machine's "configuration name"
4000 with the `--host' option; the host and target will default to be
4001 the same as the host machine.
4005 ./configure --host=sparc-sun-sunos4.1
4007 A configuration name may be canonical or it may be more or less
4010 A canonical configuration name has three parts, separated by
4011 dashes. It looks like this: `CPU-COMPANY-SYSTEM'. (The three
4012 parts may themselves contain dashes; `configure' can figure out
4013 which dashes serve which purpose.) For example,
4014 `m68k-sun-sunos4.1' specifies a Sun 3.
4016 You can also replace parts of the configuration by nicknames or
4017 aliases. For example, `sun3' stands for `m68k-sun', so
4018 `sun3-sunos4.1' is another way to specify a Sun 3.
4020 You can specify a version number after any of the system types,
4021 and some of the CPU types. In most cases, the version is
4022 irrelevant, and will be ignored. So you might as well specify the
4023 version if you know it.
4025 See *note Configurations::, for a list of supported configuration
4026 names and notes on many of the configurations. You should check
4027 the notes in that section before proceeding any further with the
4028 installation of GCC.
4032 File: gccinstall.info, Node: Configurations, Up: Old
4034 10.1 Configurations Supported by GCC
4035 ====================================
4037 Here are the possible CPU types:
4039 1750a, a29k, alpha, arm, avr, cN, clipper, dsp16xx, elxsi, fr30,
4040 h8300, hppa1.0, hppa1.1, i370, i386, i486, i586, i686, i786, i860,
4041 i960, ip2k, m32r, m68000, m68k, m88k, mcore, mips, mipsel, mips64,
4042 mips64el, mn10200, mn10300, ns32k, pdp11, powerpc, powerpcle,
4043 romp, rs6000, sh, sparc, sparclite, sparc64, v850, vax, we32k.
4045 Here are the recognized company names. As you can see, customary
4046 abbreviations are used rather than the longer official names.
4048 acorn, alliant, altos, apollo, apple, att, bull, cbm, convergent,
4049 convex, crds, dec, dg, dolphin, elxsi, encore, harris, hitachi,
4050 hp, ibm, intergraph, isi, mips, motorola, ncr, next, ns, omron,
4051 plexus, sequent, sgi, sony, sun, tti, unicom, wrs.
4053 The company name is meaningful only to disambiguate when the rest of
4054 the information supplied is insufficient. You can omit it, writing
4055 just `CPU-SYSTEM', if it is not needed. For example, `vax-ultrix4.2'
4056 is equivalent to `vax-dec-ultrix4.2'.
4058 Here is a list of system types:
4060 386bsd, aix, acis, amigaos, aos, aout, aux, bosx, bsd, clix, coff,
4061 ctix, cxux, dgux, dynix, ebmon, ecoff, elf, esix, freebsd, hms,
4062 genix, gnu, linux, linux-gnu, hiux, hpux, iris, irix, isc, luna,
4063 lynxos, mach, minix, msdos, mvs, netbsd, newsos, nindy, ns, osf,
4064 osfrose, ptx, riscix, riscos, rtu, sco, sim, solaris, sunos, sym,
4065 sysv, udi, ultrix, unicos, uniplus, unos, vms, vsta, vxworks,
4068 You can omit the system type; then `configure' guesses the operating
4069 system from the CPU and company.
4071 You can add a version number to the system type; this may or may not
4072 make a difference. For example, you can write `bsd4.3' or `bsd4.4' to
4073 distinguish versions of BSD. In practice, the version number is most
4074 needed for `sysv3' and `sysv4', which are often treated differently.
4076 `linux-gnu' is the canonical name for the GNU/Linux target; however
4077 GCC will also accept `linux'. The version of the kernel in use is not
4078 relevant on these systems. A suffix such as `libc1' or `aout'
4079 distinguishes major versions of the C library; all of the suffixed
4080 versions are obsolete.
4082 If you specify an impossible combination such as `i860-dg-vms', then
4083 you may get an error message from `configure', or it may ignore part of
4084 the information and do the best it can with the rest. `configure'
4085 always prints the canonical name for the alternative that it used. GCC
4086 does not support all possible alternatives.
4088 Often a particular model of machine has a name. Many machine names
4089 are recognized as aliases for CPU/company combinations. Thus, the
4090 machine name `sun3', mentioned above, is an alias for `m68k-sun'.
4091 Sometimes we accept a company name as a machine name, when the name is
4092 popularly used for a particular machine. Here is a table of the known
4095 3300, 3b1, 3bN, 7300, altos3068, altos, apollo68, att-7300,
4096 balance, convex-cN, crds, decstation-3100, decstation, delta,
4097 encore, fx2800, gmicro, hp7NN, hp8NN, hp9k2NN, hp9k3NN, hp9k7NN,
4098 hp9k8NN, iris4d, iris, isi68, m3230, magnum, merlin, miniframe,
4099 mmax, news-3600, news800, news, next, pbd, pc532, pmax, powerpc,
4100 powerpcle, ps2, risc-news, rtpc, sun2, sun386i, sun386, sun3,
4101 sun4, symmetry, tower-32, tower.
4103 Remember that a machine name specifies both the cpu type and the company
4107 File: gccinstall.info, Node: GNU Free Documentation License, Next: Concept Index, Prev: Old, Up: Top
4109 GNU Free Documentation License
4110 ******************************
4112 Version 1.3, 3 November 2008
4114 Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
4117 Everyone is permitted to copy and distribute verbatim copies
4118 of this license document, but changing it is not allowed.
4122 The purpose of this License is to make a manual, textbook, or other
4123 functional and useful document "free" in the sense of freedom: to
4124 assure everyone the effective freedom to copy and redistribute it,
4125 with or without modifying it, either commercially or
4126 noncommercially. Secondarily, this License preserves for the
4127 author and publisher a way to get credit for their work, while not
4128 being considered responsible for modifications made by others.
4130 This License is a kind of "copyleft", which means that derivative
4131 works of the document must themselves be free in the same sense.
4132 It complements the GNU General Public License, which is a copyleft
4133 license designed for free software.
4135 We have designed this License in order to use it for manuals for
4136 free software, because free software needs free documentation: a
4137 free program should come with manuals providing the same freedoms
4138 that the software does. But this License is not limited to
4139 software manuals; it can be used for any textual work, regardless
4140 of subject matter or whether it is published as a printed book.
4141 We recommend this License principally for works whose purpose is
4142 instruction or reference.
4144 1. APPLICABILITY AND DEFINITIONS
4146 This License applies to any manual or other work, in any medium,
4147 that contains a notice placed by the copyright holder saying it
4148 can be distributed under the terms of this License. Such a notice
4149 grants a world-wide, royalty-free license, unlimited in duration,
4150 to use that work under the conditions stated herein. The
4151 "Document", below, refers to any such manual or work. Any member
4152 of the public is a licensee, and is addressed as "you". You
4153 accept the license if you copy, modify or distribute the work in a
4154 way requiring permission under copyright law.
4156 A "Modified Version" of the Document means any work containing the
4157 Document or a portion of it, either copied verbatim, or with
4158 modifications and/or translated into another language.
4160 A "Secondary Section" is a named appendix or a front-matter section
4161 of the Document that deals exclusively with the relationship of the
4162 publishers or authors of the Document to the Document's overall
4163 subject (or to related matters) and contains nothing that could
4164 fall directly within that overall subject. (Thus, if the Document
4165 is in part a textbook of mathematics, a Secondary Section may not
4166 explain any mathematics.) The relationship could be a matter of
4167 historical connection with the subject or with related matters, or
4168 of legal, commercial, philosophical, ethical or political position
4171 The "Invariant Sections" are certain Secondary Sections whose
4172 titles are designated, as being those of Invariant Sections, in
4173 the notice that says that the Document is released under this
4174 License. If a section does not fit the above definition of
4175 Secondary then it is not allowed to be designated as Invariant.
4176 The Document may contain zero Invariant Sections. If the Document
4177 does not identify any Invariant Sections then there are none.
4179 The "Cover Texts" are certain short passages of text that are
4180 listed, as Front-Cover Texts or Back-Cover Texts, in the notice
4181 that says that the Document is released under this License. A
4182 Front-Cover Text may be at most 5 words, and a Back-Cover Text may
4183 be at most 25 words.
4185 A "Transparent" copy of the Document means a machine-readable copy,
4186 represented in a format whose specification is available to the
4187 general public, that is suitable for revising the document
4188 straightforwardly with generic text editors or (for images
4189 composed of pixels) generic paint programs or (for drawings) some
4190 widely available drawing editor, and that is suitable for input to
4191 text formatters or for automatic translation to a variety of
4192 formats suitable for input to text formatters. A copy made in an
4193 otherwise Transparent file format whose markup, or absence of
4194 markup, has been arranged to thwart or discourage subsequent
4195 modification by readers is not Transparent. An image format is
4196 not Transparent if used for any substantial amount of text. A
4197 copy that is not "Transparent" is called "Opaque".
4199 Examples of suitable formats for Transparent copies include plain
4200 ASCII without markup, Texinfo input format, LaTeX input format,
4201 SGML or XML using a publicly available DTD, and
4202 standard-conforming simple HTML, PostScript or PDF designed for
4203 human modification. Examples of transparent image formats include
4204 PNG, XCF and JPG. Opaque formats include proprietary formats that
4205 can be read and edited only by proprietary word processors, SGML or
4206 XML for which the DTD and/or processing tools are not generally
4207 available, and the machine-generated HTML, PostScript or PDF
4208 produced by some word processors for output purposes only.
4210 The "Title Page" means, for a printed book, the title page itself,
4211 plus such following pages as are needed to hold, legibly, the
4212 material this License requires to appear in the title page. For
4213 works in formats which do not have any title page as such, "Title
4214 Page" means the text near the most prominent appearance of the
4215 work's title, preceding the beginning of the body of the text.
4217 The "publisher" means any person or entity that distributes copies
4218 of the Document to the public.
4220 A section "Entitled XYZ" means a named subunit of the Document
4221 whose title either is precisely XYZ or contains XYZ in parentheses
4222 following text that translates XYZ in another language. (Here XYZ
4223 stands for a specific section name mentioned below, such as
4224 "Acknowledgements", "Dedications", "Endorsements", or "History".)
4225 To "Preserve the Title" of such a section when you modify the
4226 Document means that it remains a section "Entitled XYZ" according
4229 The Document may include Warranty Disclaimers next to the notice
4230 which states that this License applies to the Document. These
4231 Warranty Disclaimers are considered to be included by reference in
4232 this License, but only as regards disclaiming warranties: any other
4233 implication that these Warranty Disclaimers may have is void and
4234 has no effect on the meaning of this License.
4238 You may copy and distribute the Document in any medium, either
4239 commercially or noncommercially, provided that this License, the
4240 copyright notices, and the license notice saying this License
4241 applies to the Document are reproduced in all copies, and that you
4242 add no other conditions whatsoever to those of this License. You
4243 may not use technical measures to obstruct or control the reading
4244 or further copying of the copies you make or distribute. However,
4245 you may accept compensation in exchange for copies. If you
4246 distribute a large enough number of copies you must also follow
4247 the conditions in section 3.
4249 You may also lend copies, under the same conditions stated above,
4250 and you may publicly display copies.
4252 3. COPYING IN QUANTITY
4254 If you publish printed copies (or copies in media that commonly
4255 have printed covers) of the Document, numbering more than 100, and
4256 the Document's license notice requires Cover Texts, you must
4257 enclose the copies in covers that carry, clearly and legibly, all
4258 these Cover Texts: Front-Cover Texts on the front cover, and
4259 Back-Cover Texts on the back cover. Both covers must also clearly
4260 and legibly identify you as the publisher of these copies. The
4261 front cover must present the full title with all words of the
4262 title equally prominent and visible. You may add other material
4263 on the covers in addition. Copying with changes limited to the
4264 covers, as long as they preserve the title of the Document and
4265 satisfy these conditions, can be treated as verbatim copying in
4268 If the required texts for either cover are too voluminous to fit
4269 legibly, you should put the first ones listed (as many as fit
4270 reasonably) on the actual cover, and continue the rest onto
4273 If you publish or distribute Opaque copies of the Document
4274 numbering more than 100, you must either include a
4275 machine-readable Transparent copy along with each Opaque copy, or
4276 state in or with each Opaque copy a computer-network location from
4277 which the general network-using public has access to download
4278 using public-standard network protocols a complete Transparent
4279 copy of the Document, free of added material. If you use the
4280 latter option, you must take reasonably prudent steps, when you
4281 begin distribution of Opaque copies in quantity, to ensure that
4282 this Transparent copy will remain thus accessible at the stated
4283 location until at least one year after the last time you
4284 distribute an Opaque copy (directly or through your agents or
4285 retailers) of that edition to the public.
4287 It is requested, but not required, that you contact the authors of
4288 the Document well before redistributing any large number of
4289 copies, to give them a chance to provide you with an updated
4290 version of the Document.
4294 You may copy and distribute a Modified Version of the Document
4295 under the conditions of sections 2 and 3 above, provided that you
4296 release the Modified Version under precisely this License, with
4297 the Modified Version filling the role of the Document, thus
4298 licensing distribution and modification of the Modified Version to
4299 whoever possesses a copy of it. In addition, you must do these
4300 things in the Modified Version:
4302 A. Use in the Title Page (and on the covers, if any) a title
4303 distinct from that of the Document, and from those of
4304 previous versions (which should, if there were any, be listed
4305 in the History section of the Document). You may use the
4306 same title as a previous version if the original publisher of
4307 that version gives permission.
4309 B. List on the Title Page, as authors, one or more persons or
4310 entities responsible for authorship of the modifications in
4311 the Modified Version, together with at least five of the
4312 principal authors of the Document (all of its principal
4313 authors, if it has fewer than five), unless they release you
4314 from this requirement.
4316 C. State on the Title page the name of the publisher of the
4317 Modified Version, as the publisher.
4319 D. Preserve all the copyright notices of the Document.
4321 E. Add an appropriate copyright notice for your modifications
4322 adjacent to the other copyright notices.
4324 F. Include, immediately after the copyright notices, a license
4325 notice giving the public permission to use the Modified
4326 Version under the terms of this License, in the form shown in
4329 G. Preserve in that license notice the full lists of Invariant
4330 Sections and required Cover Texts given in the Document's
4333 H. Include an unaltered copy of this License.
4335 I. Preserve the section Entitled "History", Preserve its Title,
4336 and add to it an item stating at least the title, year, new
4337 authors, and publisher of the Modified Version as given on
4338 the Title Page. If there is no section Entitled "History" in
4339 the Document, create one stating the title, year, authors,
4340 and publisher of the Document as given on its Title Page,
4341 then add an item describing the Modified Version as stated in
4342 the previous sentence.
4344 J. Preserve the network location, if any, given in the Document
4345 for public access to a Transparent copy of the Document, and
4346 likewise the network locations given in the Document for
4347 previous versions it was based on. These may be placed in
4348 the "History" section. You may omit a network location for a
4349 work that was published at least four years before the
4350 Document itself, or if the original publisher of the version
4351 it refers to gives permission.
4353 K. For any section Entitled "Acknowledgements" or "Dedications",
4354 Preserve the Title of the section, and preserve in the
4355 section all the substance and tone of each of the contributor
4356 acknowledgements and/or dedications given therein.
4358 L. Preserve all the Invariant Sections of the Document,
4359 unaltered in their text and in their titles. Section numbers
4360 or the equivalent are not considered part of the section
4363 M. Delete any section Entitled "Endorsements". Such a section
4364 may not be included in the Modified Version.
4366 N. Do not retitle any existing section to be Entitled
4367 "Endorsements" or to conflict in title with any Invariant
4370 O. Preserve any Warranty Disclaimers.
4372 If the Modified Version includes new front-matter sections or
4373 appendices that qualify as Secondary Sections and contain no
4374 material copied from the Document, you may at your option
4375 designate some or all of these sections as invariant. To do this,
4376 add their titles to the list of Invariant Sections in the Modified
4377 Version's license notice. These titles must be distinct from any
4378 other section titles.
4380 You may add a section Entitled "Endorsements", provided it contains
4381 nothing but endorsements of your Modified Version by various
4382 parties--for example, statements of peer review or that the text
4383 has been approved by an organization as the authoritative
4384 definition of a standard.
4386 You may add a passage of up to five words as a Front-Cover Text,
4387 and a passage of up to 25 words as a Back-Cover Text, to the end
4388 of the list of Cover Texts in the Modified Version. Only one
4389 passage of Front-Cover Text and one of Back-Cover Text may be
4390 added by (or through arrangements made by) any one entity. If the
4391 Document already includes a cover text for the same cover,
4392 previously added by you or by arrangement made by the same entity
4393 you are acting on behalf of, you may not add another; but you may
4394 replace the old one, on explicit permission from the previous
4395 publisher that added the old one.
4397 The author(s) and publisher(s) of the Document do not by this
4398 License give permission to use their names for publicity for or to
4399 assert or imply endorsement of any Modified Version.
4401 5. COMBINING DOCUMENTS
4403 You may combine the Document with other documents released under
4404 this License, under the terms defined in section 4 above for
4405 modified versions, provided that you include in the combination
4406 all of the Invariant Sections of all of the original documents,
4407 unmodified, and list them all as Invariant Sections of your
4408 combined work in its license notice, and that you preserve all
4409 their Warranty Disclaimers.
4411 The combined work need only contain one copy of this License, and
4412 multiple identical Invariant Sections may be replaced with a single
4413 copy. If there are multiple Invariant Sections with the same name
4414 but different contents, make the title of each such section unique
4415 by adding at the end of it, in parentheses, the name of the
4416 original author or publisher of that section if known, or else a
4417 unique number. Make the same adjustment to the section titles in
4418 the list of Invariant Sections in the license notice of the
4421 In the combination, you must combine any sections Entitled
4422 "History" in the various original documents, forming one section
4423 Entitled "History"; likewise combine any sections Entitled
4424 "Acknowledgements", and any sections Entitled "Dedications". You
4425 must delete all sections Entitled "Endorsements."
4427 6. COLLECTIONS OF DOCUMENTS
4429 You may make a collection consisting of the Document and other
4430 documents released under this License, and replace the individual
4431 copies of this License in the various documents with a single copy
4432 that is included in the collection, provided that you follow the
4433 rules of this License for verbatim copying of each of the
4434 documents in all other respects.
4436 You may extract a single document from such a collection, and
4437 distribute it individually under this License, provided you insert
4438 a copy of this License into the extracted document, and follow
4439 this License in all other respects regarding verbatim copying of
4442 7. AGGREGATION WITH INDEPENDENT WORKS
4444 A compilation of the Document or its derivatives with other
4445 separate and independent documents or works, in or on a volume of
4446 a storage or distribution medium, is called an "aggregate" if the
4447 copyright resulting from the compilation is not used to limit the
4448 legal rights of the compilation's users beyond what the individual
4449 works permit. When the Document is included in an aggregate, this
4450 License does not apply to the other works in the aggregate which
4451 are not themselves derivative works of the Document.
4453 If the Cover Text requirement of section 3 is applicable to these
4454 copies of the Document, then if the Document is less than one half
4455 of the entire aggregate, the Document's Cover Texts may be placed
4456 on covers that bracket the Document within the aggregate, or the
4457 electronic equivalent of covers if the Document is in electronic
4458 form. Otherwise they must appear on printed covers that bracket
4459 the whole aggregate.
4463 Translation is considered a kind of modification, so you may
4464 distribute translations of the Document under the terms of section
4465 4. Replacing Invariant Sections with translations requires special
4466 permission from their copyright holders, but you may include
4467 translations of some or all Invariant Sections in addition to the
4468 original versions of these Invariant Sections. You may include a
4469 translation of this License, and all the license notices in the
4470 Document, and any Warranty Disclaimers, provided that you also
4471 include the original English version of this License and the
4472 original versions of those notices and disclaimers. In case of a
4473 disagreement between the translation and the original version of
4474 this License or a notice or disclaimer, the original version will
4477 If a section in the Document is Entitled "Acknowledgements",
4478 "Dedications", or "History", the requirement (section 4) to
4479 Preserve its Title (section 1) will typically require changing the
4484 You may not copy, modify, sublicense, or distribute the Document
4485 except as expressly provided under this License. Any attempt
4486 otherwise to copy, modify, sublicense, or distribute it is void,
4487 and will automatically terminate your rights under this License.
4489 However, if you cease all violation of this License, then your
4490 license from a particular copyright holder is reinstated (a)
4491 provisionally, unless and until the copyright holder explicitly
4492 and finally terminates your license, and (b) permanently, if the
4493 copyright holder fails to notify you of the violation by some
4494 reasonable means prior to 60 days after the cessation.
4496 Moreover, your license from a particular copyright holder is
4497 reinstated permanently if the copyright holder notifies you of the
4498 violation by some reasonable means, this is the first time you have
4499 received notice of violation of this License (for any work) from
4500 that copyright holder, and you cure the violation prior to 30 days
4501 after your receipt of the notice.
4503 Termination of your rights under this section does not terminate
4504 the licenses of parties who have received copies or rights from
4505 you under this License. If your rights have been terminated and
4506 not permanently reinstated, receipt of a copy of some or all of
4507 the same material does not give you any rights to use it.
4509 10. FUTURE REVISIONS OF THIS LICENSE
4511 The Free Software Foundation may publish new, revised versions of
4512 the GNU Free Documentation License from time to time. Such new
4513 versions will be similar in spirit to the present version, but may
4514 differ in detail to address new problems or concerns. See
4515 `http://www.gnu.org/copyleft/'.
4517 Each version of the License is given a distinguishing version
4518 number. If the Document specifies that a particular numbered
4519 version of this License "or any later version" applies to it, you
4520 have the option of following the terms and conditions either of
4521 that specified version or of any later version that has been
4522 published (not as a draft) by the Free Software Foundation. If
4523 the Document does not specify a version number of this License,
4524 you may choose any version ever published (not as a draft) by the
4525 Free Software Foundation. If the Document specifies that a proxy
4526 can decide which future versions of this License can be used, that
4527 proxy's public statement of acceptance of a version permanently
4528 authorizes you to choose that version for the Document.
4532 "Massive Multiauthor Collaboration Site" (or "MMC Site") means any
4533 World Wide Web server that publishes copyrightable works and also
4534 provides prominent facilities for anybody to edit those works. A
4535 public wiki that anybody can edit is an example of such a server.
4536 A "Massive Multiauthor Collaboration" (or "MMC") contained in the
4537 site means any set of copyrightable works thus published on the MMC
4540 "CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0
4541 license published by Creative Commons Corporation, a not-for-profit
4542 corporation with a principal place of business in San Francisco,
4543 California, as well as future copyleft versions of that license
4544 published by that same organization.
4546 "Incorporate" means to publish or republish a Document, in whole or
4547 in part, as part of another Document.
4549 An MMC is "eligible for relicensing" if it is licensed under this
4550 License, and if all works that were first published under this
4551 License somewhere other than this MMC, and subsequently
4552 incorporated in whole or in part into the MMC, (1) had no cover
4553 texts or invariant sections, and (2) were thus incorporated prior
4554 to November 1, 2008.
4556 The operator of an MMC Site may republish an MMC contained in the
4557 site under CC-BY-SA on the same site at any time before August 1,
4558 2009, provided the MMC is eligible for relicensing.
4561 ADDENDUM: How to use this License for your documents
4562 ====================================================
4564 To use this License in a document you have written, include a copy of
4565 the License in the document and put the following copyright and license
4566 notices just after the title page:
4568 Copyright (C) YEAR YOUR NAME.
4569 Permission is granted to copy, distribute and/or modify this document
4570 under the terms of the GNU Free Documentation License, Version 1.3
4571 or any later version published by the Free Software Foundation;
4572 with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
4573 Texts. A copy of the license is included in the section entitled ``GNU
4574 Free Documentation License''.
4576 If you have Invariant Sections, Front-Cover Texts and Back-Cover
4577 Texts, replace the "with...Texts." line with this:
4579 with the Invariant Sections being LIST THEIR TITLES, with
4580 the Front-Cover Texts being LIST, and with the Back-Cover Texts
4583 If you have Invariant Sections without Cover Texts, or some other
4584 combination of the three, merge those two alternatives to suit the
4587 If your document contains nontrivial examples of program code, we
4588 recommend releasing these examples in parallel under your choice of
4589 free software license, such as the GNU General Public License, to
4590 permit their use in free software.
4593 File: gccinstall.info, Node: Concept Index, Prev: GNU Free Documentation License, Up: Top
4601 * Binaries: Binaries. (line 6)
4602 * build_configargs: Configuration. (line 1458)
4603 * Configuration: Configuration. (line 6)
4604 * configurations supported by GCC: Configurations. (line 6)
4605 * Downloading GCC: Downloading the source.
4607 * Downloading the Source: Downloading the source.
4609 * FDL, GNU Free Documentation License: GNU Free Documentation License.
4611 * Host specific installation: Specific. (line 6)
4612 * host_configargs: Configuration. (line 1462)
4613 * Installing GCC: Binaries: Binaries. (line 6)
4614 * Installing GCC: Building: Building. (line 6)
4615 * Installing GCC: Configuration: Configuration. (line 6)
4616 * Installing GCC: Testing: Testing. (line 6)
4617 * Prerequisites: Prerequisites. (line 6)
4618 * Specific: Specific. (line 6)
4619 * Specific installation notes: Specific. (line 6)
4620 * Target specific installation: Specific. (line 6)
4621 * Target specific installation notes: Specific. (line 6)
4622 * target_configargs: Configuration. (line 1466)
4623 * Testing: Testing. (line 6)
4624 * Testsuite: Testing. (line 6)
4630 Node: Installing GCC
\7f2535
4631 Node: Prerequisites
\7f4050
4632 Node: Downloading the source
\7f14274
4633 Node: Configuration
\7f16211
4634 Ref: with-gnu-as
\7f31217
4635 Ref: with-as
\7f32115
4636 Ref: with-gnu-ld
\7f33528
4637 Node: Building
\7f80760
4638 Node: Testing
\7f96245
4639 Node: Final install
\7f104094
4640 Node: Binaries
\7f109408
4641 Node: Specific
\7f111009
4642 Ref: alpha-x-x
\7f111515
4643 Ref: alpha-dec-osf51
\7f112004
4644 Ref: amd64-x-solaris210
\7f114540
4645 Ref: arm-x-eabi
\7f114643
4651 Ref: epiphany-x-elf
\7f117297
4652 Ref: x-x-freebsd
\7f117402
4653 Ref: h8300-hms
\7f119239
4654 Ref: hppa-hp-hpux
\7f119591
4655 Ref: hppa-hp-hpux10
\7f121962
4656 Ref: hppa-hp-hpux11
\7f122375
4657 Ref: x-x-linux-gnu
\7f128034
4658 Ref: ix86-x-linux
\7f128227
4659 Ref: ix86-x-solaris289
\7f128540
4660 Ref: ix86-x-solaris210
\7f129384
4661 Ref: ia64-x-linux
\7f130575
4662 Ref: ia64-x-hpux
\7f131345
4663 Ref: x-ibm-aix
\7f131900
4664 Ref: iq2000-x-elf
\7f138670
4665 Ref: lm32-x-elf
\7f138810
4666 Ref: lm32-x-uclinux
\7f138914
4667 Ref: m32c-x-elf
\7f139042
4668 Ref: m32r-x-elf
\7f139144
4669 Ref: m68k-x-x
\7f139246
4670 Ref: m68k-x-uclinux
\7f140284
4671 Ref: mep-x-elf
\7f140530
4672 Ref: microblaze-x-elf
\7f140640
4673 Ref: mips-x-x
\7f140759
4674 Ref: mips-sgi-irix5
\7f143155
4675 Ref: mips-sgi-irix6
\7f143235
4676 Ref: moxie-x-elf
\7f146459
4677 Ref: powerpc-x-x
\7f146579
4678 Ref: powerpc-x-darwin
\7f146784
4679 Ref: powerpc-x-elf
\7f147278
4680 Ref: powerpc-x-linux-gnu
\7f147363
4681 Ref: powerpc-x-netbsd
\7f147458
4682 Ref: powerpc-x-eabisim
\7f147546
4683 Ref: powerpc-x-eabi
\7f147672
4684 Ref: powerpcle-x-elf
\7f147748
4685 Ref: powerpcle-x-eabisim
\7f147840
4686 Ref: powerpcle-x-eabi
\7f147973
4687 Ref: rl78-x-elf
\7f148056
4688 Ref: rx-x-elf
\7f148162
4689 Ref: s390-x-linux
\7f148361
4690 Ref: s390x-x-linux
\7f148433
4691 Ref: s390x-ibm-tpf
\7f148520
4692 Ref: x-x-solaris2
\7f148651
4693 Ref: sparc-x-x
\7f154218
4694 Ref: sparc-sun-solaris2
\7f154720
4695 Ref: sparc-sun-solaris210
\7f157474
4696 Ref: sparc-x-linux
\7f157850
4697 Ref: sparc64-x-solaris2
\7f158075
4698 Ref: sparcv9-x-solaris2
\7f158728
4699 Ref: c6x-x-x
\7f158815
4700 Ref: tilegx-*-linux
\7f158906
4701 Ref: tilepro-*-linux
\7f159025
4702 Ref: x-x-vxworks
\7f159146
4703 Ref: x86-64-x-x
\7f160668
4704 Ref: x86-64-x-solaris210
\7f160996
4705 Ref: xtensa-x-elf
\7f161658
4706 Ref: xtensa-x-linux
\7f162329
4707 Ref: windows
\7f162670
4708 Ref: x-x-cygwin
\7f164607
4709 Ref: x-x-interix
\7f165160
4710 Ref: x-x-mingw32
\7f165469
4714 Node: Configurations
\7f171207
4715 Node: GNU Free Documentation License
\7f174748
4716 Node: Concept Index
\7f199895
projects / platform / upstream / gcc48.git / blob