1 \input texinfo.tex @c -*-texinfo-*-
4 @setfilename gccinstall.info
5 @settitle Installing GCC
10 @include gcc-common.texi
12 @c Specify title for specific html page
14 @settitle Installing GCC
17 @settitle Host/Target specific installation notes for GCC
19 @ifset prerequisiteshtml
20 @settitle Prerequisites for GCC
23 @settitle Downloading GCC
26 @settitle Installing GCC: Configuration
29 @settitle Installing GCC: Building
32 @settitle Installing GCC: Testing
34 @ifset finalinstallhtml
35 @settitle Installing GCC: Final installation
38 @settitle Installing GCC: Binaries
41 @settitle Installing GCC: Old documentation
44 @settitle Installing GCC: GNU Free Documentation License
47 @c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
48 @c 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, Inc.
49 @c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com
51 @c IMPORTANT: whenever you modify this file, run `install.texi2html' to
52 @c test the generation of HTML documents for the gcc.gnu.org web pages.
54 @c Do not use @footnote{} in this file as it breaks install.texi2html!
56 @c Include everything if we're not making html
60 @set prerequisiteshtml
71 @c Part 2 Summary Description and Copyright
73 Copyright @copyright{} 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
74 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,
75 2008 Free Software Foundation, Inc.
77 Permission is granted to copy, distribute and/or modify this document
78 under the terms of the GNU Free Documentation License, Version 1.2 or
79 any later version published by the Free Software Foundation; with no
80 Invariant Sections, the Front-Cover texts being (a) (see below), and
81 with the Back-Cover Texts being (b) (see below). A copy of the
82 license is included in the section entitled ``@uref{./gfdl.html,,GNU
83 Free Documentation License}''.
85 (a) The FSF's Front-Cover Text is:
89 (b) The FSF's Back-Cover Text is:
91 You have freedom to copy and modify this GNU Manual, like GNU
92 software. Copies published by the Free Software Foundation raise
93 funds for GNU development.
98 @dircategory Software development
100 * gccinstall: (gccinstall). Installing the GNU Compiler Collection.
103 @c Part 3 Titlepage and Copyright
105 @title Installing GCC
108 @c The following two commands start the copyright page.
110 @vskip 0pt plus 1filll
114 @c Part 4 Top node, Master Menu, and/or Table of Contents
117 @comment node-name, next, Previous, up
120 * Installing GCC:: This document describes the generic installation
121 procedure for GCC as well as detailing some target
122 specific installation instructions.
124 * Specific:: Host/target specific installation notes for GCC.
125 * Binaries:: Where to get pre-compiled binaries.
127 * Old:: Old installation documentation.
129 * GNU Free Documentation License:: How you can copy and share this manual.
130 * Concept Index:: This index has two entries.
138 @c Part 5 The Body of the Document
139 @c ***Installing GCC**********************************************************
141 @comment node-name, next, previous, up
142 @node Installing GCC, Binaries, , Top
146 @chapter Installing GCC
149 The latest version of this document is always available at
150 @uref{http://gcc.gnu.org/install/,,http://gcc.gnu.org/install/}.
152 This document describes the generic installation procedure for GCC as well
153 as detailing some target specific installation instructions.
155 GCC includes several components that previously were separate distributions
156 with their own installation instructions. This document supersedes all
157 package specific installation instructions.
159 @emph{Before} starting the build/install procedure please check the
161 @ref{Specific, host/target specific installation notes}.
164 @uref{specific.html,,host/target specific installation notes}.
166 We recommend you browse the entire generic installation instructions before
169 Lists of successful builds for released versions of GCC are
170 available at @uref{http://gcc.gnu.org/buildstat.html}.
171 These lists are updated as new information becomes available.
173 The installation procedure itself is broken into five steps.
178 * Downloading the source::
181 * Testing:: (optional)
188 @uref{prerequisites.html,,Prerequisites}
190 @uref{download.html,,Downloading the source}
192 @uref{configure.html,,Configuration}
194 @uref{build.html,,Building}
196 @uref{test.html,,Testing} (optional)
198 @uref{finalinstall.html,,Final install}
202 Please note that GCC does not support @samp{make uninstall} and probably
203 won't do so in the near future as this would open a can of worms. Instead,
204 we suggest that you install GCC into a directory of its own and simply
205 remove that directory when you do not need that specific version of GCC
206 any longer, and, if shared libraries are installed there as well, no
207 more binaries exist that use them.
210 There are also some @uref{old.html,,old installation instructions},
211 which are mostly obsolete but still contain some information which has
212 not yet been merged into the main part of this manual.
220 @uref{./index.html,,Return to the GCC Installation page}
226 @c ***Prerequisites**************************************************
228 @comment node-name, next, previous, up
229 @node Prerequisites, Downloading the source, , Installing GCC
231 @ifset prerequisiteshtml
233 @chapter Prerequisites
235 @cindex Prerequisites
237 GCC requires that various tools and packages be available for use in the
238 build procedure. Modifying GCC sources requires additional tools
241 @heading Tools/packages necessary for building GCC
243 @item ISO C90 compiler
244 Necessary to bootstrap GCC, although versions of GCC prior
245 to 3.4 also allow bootstrapping with a traditional (K&R) C compiler.
247 To build all languages in a cross-compiler or other configuration where
248 3-stage bootstrap is not performed, you need to start with an existing
249 GCC binary (version 2.95 or later) because source code for language
250 frontends other than C might use GCC extensions.
254 In order to build the Ada compiler (GNAT) you must already have GNAT
255 installed because portions of the Ada frontend are written in Ada (with
256 GNAT extensions.) Refer to the Ada installation instructions for more
257 specific information.
259 @item A ``working'' POSIX compatible shell, or GNU bash
261 Necessary when running @command{configure} because some
262 @command{/bin/sh} shells have bugs and may crash when configuring the
263 target libraries. In other cases, @command{/bin/sh} or @command{ksh}
264 have disastrous corner-case performance problems. This
265 can cause target @command{configure} runs to literally take days to
266 complete in some cases.
268 So on some platforms @command{/bin/ksh} is sufficient, on others it
269 isn't. See the host/target specific instructions for your platform, or
270 use @command{bash} to be sure. Then set @env{CONFIG_SHELL} in your
271 environment to your ``good'' shell prior to running
272 @command{configure}/@command{make}.
274 @command{zsh} is not a fully compliant POSIX shell and will not
275 work when configuring GCC@.
277 @item A POSIX or SVR4 awk
279 Necessary for creating some of the generated source files for GCC@.
280 If in doubt, use a recent GNU awk version, as some of the older ones
281 are broken. GNU awk version 3.1.5 is known to work.
285 Necessary in some circumstances, optional in others. See the
286 host/target specific instructions for your platform for the exact
289 @item gzip version 1.2.4 (or later) or
290 @itemx bzip2 version 1.0.2 (or later)
292 Necessary to uncompress GCC @command{tar} files when source code is
293 obtained via FTP mirror sites.
295 @item GNU make version 3.80 (or later)
297 You must have GNU make installed to build GCC@.
299 @item GNU tar version 1.14 (or later)
301 Necessary (only on some platforms) to untar the source code. Many
302 systems' @command{tar} programs will also work, only try GNU
303 @command{tar} if you have problems.
305 @item GNU Multiple Precision Library (GMP) version 4.2 (or later)
307 Necessary to build GCC@. If you do not have it installed in your
308 library search path, you will have to configure with the
309 @option{--with-gmp} configure option. See also @option{--with-gmp-lib}
310 and @option{--with-gmp-include}. Alternatively, if a GMP source
311 distribution is found in a subdirectory of your GCC sources named
312 @file{gmp}, it will be built together with GCC@.
314 @item MPFR Library version 2.3.2 (or later)
316 Necessary to build GCC@. It can be downloaded from
317 @uref{http://www.mpfr.org/}. The @option{--with-mpfr} configure
318 option should be used if your MPFR Library is not installed in your
319 default library search path. See also @option{--with-mpfr-lib} and
320 @option{--with-mpfr-include}. Alternatively, if a MPFR source
321 distribution is found in a subdirectory of your GCC sources named
322 @file{mpfr}, it will be built together with GCC@.
324 @item Parma Polyhedra Library (PPL) version 0.10
326 Necessary to build GCC with the Graphite loop optimizations.
327 It can be downloaded from @uref{http://www.cs.unipr.it/ppl/Download/}.
329 The @option{--with-ppl} configure option should be used if PPL is not
330 installed in your default library search path.
332 @item CLooG-PPL version 0.15
334 Necessary to build GCC with the Graphite loop optimizations. It can
335 be downloaded from @uref{ftp://gcc.gnu.org/pub/gcc/infrastructure/}.
336 The code in @file{cloog-ppl-0.15.tar.gz} comes from a branch of CLooG
337 available from @uref{http://repo.or.cz/w/cloog-ppl.git}. CLooG-PPL
338 should be configured with @option{--with-ppl}.
340 The @option{--with-cloog} configure option should be used if CLooG is
341 not installed in your default library search path.
343 @item @command{jar}, or InfoZIP (@command{zip} and @command{unzip})
345 Necessary to build libgcj, the GCJ runtime.
347 @item MPC Library version 0.8.0 (or later)
349 Optional when building GCC@. Having this library will enable
350 additional optimizations on complex numbers. It can be downloaded
351 from @uref{http://www.multiprecision.org/mpc/}. The
352 @option{--with-mpc} configure option should be used if your MPC
353 Library is not installed in your default library search path. See
354 also @option{--with-mpc-lib} and @option{--with-mpc-include}.
355 Alternatively, if an MPC source distribution is found in a
356 subdirectory of your GCC sources named @file{mpc}, it will be built
359 @item libelf version 0.8.12 (or later)
361 Necessary to build link-time optimization (LTO) support. It can be
362 downloaded from @uref{http://www.mr511.de/software/libelf-0.8.12.tar.gz},
363 though it is commonly available in several systems.
365 The @option{--with-libelf} configure option should be used if libelf is
366 not installed in your default library search patch.
370 @heading Tools/packages necessary for modifying GCC
372 @item autoconf version 2.64
373 @itemx GNU m4 version 1.4.6 (or later)
375 Necessary when modifying @file{configure.ac}, @file{aclocal.m4}, etc.@:
376 to regenerate @file{configure} and @file{config.in} files.
378 @item automake version 1.11
380 Necessary when modifying a @file{Makefile.am} file to regenerate its
381 associated @file{Makefile.in}.
383 Much of GCC does not use automake, so directly edit the @file{Makefile.in}
384 file. Specifically this applies to the @file{gcc}, @file{intl},
385 @file{libcpp}, @file{libiberty}, @file{libobjc} directories as well
386 as any of their subdirectories.
388 For directories that use automake, GCC requires the latest release in
389 the 1.11 series, which is currently 1.11. When regenerating a directory
390 to a newer version, please update all the directories using an older 1.11
391 to the latest released version.
393 @item gettext version 0.14.5 (or later)
395 Needed to regenerate @file{gcc.pot}.
397 @item gperf version 2.7.2 (or later)
399 Necessary when modifying @command{gperf} input files, e.g.@:
400 @file{gcc/cp/cfns.gperf} to regenerate its associated header file, e.g.@:
401 @file{gcc/cp/cfns.h}.
407 Necessary to run the GCC testsuite; see the section on testing for details.
409 @item autogen version 5.5.4 (or later) and
410 @itemx guile version 1.4.1 (or later)
412 Necessary to regenerate @file{fixinc/fixincl.x} from
413 @file{fixinc/inclhack.def} and @file{fixinc/*.tpl}.
415 Necessary to run @samp{make check} for @file{fixinc}.
417 Necessary to regenerate the top level @file{Makefile.in} file from
418 @file{Makefile.tpl} and @file{Makefile.def}.
420 @item Flex version 2.5.4 (or later)
422 Necessary when modifying @file{*.l} files.
424 Necessary to build GCC during development because the generated output
425 files are not included in the SVN repository. They are included in
428 @item Texinfo version 4.7 (or later)
430 Necessary for running @command{makeinfo} when modifying @file{*.texi}
431 files to test your changes.
433 Necessary for running @command{make dvi} or @command{make pdf} to
434 create printable documentation in DVI or PDF format. Texinfo version
435 4.8 or later is required for @command{make pdf}.
437 Necessary to build GCC documentation during development because the
438 generated output files are not included in the SVN repository. They are
439 included in releases.
441 @item @TeX{} (any working version)
443 Necessary for running @command{texi2dvi} and @command{texi2pdf}, which
444 are used when running @command{make dvi} or @command{make pdf} to create
445 DVI or PDF files, respectively.
447 @item SVN (any version)
448 @itemx SSH (any version)
450 Necessary to access the SVN repository. Public releases and weekly
451 snapshots of the development sources are also available via FTP@.
453 @item Perl version 5.6.1 (or later)
455 Necessary when regenerating @file{Makefile} dependencies in libiberty.
456 Necessary when regenerating @file{libiberty/functions.texi}.
457 Necessary when generating manpages from Texinfo manuals.
458 Necessary when targetting Darwin, building libstdc++,
459 and not using @option{--disable-symvers}.
460 Used by various scripts to generate some files included in SVN (mainly
461 Unicode-related and rarely changing) from source tables.
463 @item GNU diffutils version 2.7 (or later)
465 Useful when submitting patches for the GCC source code.
467 @item patch version 2.5.4 (or later)
469 Necessary when applying patches, created with @command{diff}, to one's
475 If you wish to modify @file{.java} files in libjava, you will need to
476 configure with @option{--enable-java-maintainer-mode}, and you will need
477 to have executables named @command{ecj1} and @command{gjavah} in your path.
478 The @command{ecj1} executable should run the Eclipse Java compiler via
479 the GCC-specific entry point. You can download a suitable jar from
480 @uref{ftp://sourceware.org/pub/java/}, or by running the script
481 @command{contrib/download_ecj}.
483 @item antlr.jar version 2.7.1 (or later)
486 If you wish to build the @command{gjdoc} binary in libjava, you will
487 need to have an @file{antlr.jar} library available. The library is
488 searched in system locations but can be configured with
489 @option{--with-antlr-jar=} instead. When configuring with
490 @option{--enable-java-maintainer-mode}, you will need to have one of
491 the executables named @command{cantlr}, @command{runantlr} or
492 @command{antlr} in your path.
501 @uref{./index.html,,Return to the GCC Installation page}
505 @c ***Downloading the source**************************************************
507 @comment node-name, next, previous, up
508 @node Downloading the source, Configuration, Prerequisites, Installing GCC
512 @chapter Downloading GCC
514 @cindex Downloading GCC
515 @cindex Downloading the Source
517 GCC is distributed via @uref{http://gcc.gnu.org/svn.html,,SVN} and FTP
518 tarballs compressed with @command{gzip} or
519 @command{bzip2}. It is possible to download a full distribution or specific
522 Please refer to the @uref{http://gcc.gnu.org/releases.html,,releases web page}
523 for information on how to obtain GCC@.
525 The full distribution includes the C, C++, Objective-C, Fortran, Java,
526 and Ada (in the case of GCC 3.1 and later) compilers. The full
527 distribution also includes runtime libraries for C++, Objective-C,
528 Fortran, and Java. In GCC 3.0 and later versions, the GNU compiler
529 testsuites are also included in the full distribution.
531 If you choose to download specific components, you must download the core
532 GCC distribution plus any language specific distributions you wish to
533 use. The core distribution includes the C language front end as well as the
534 shared components. Each language has a tarball which includes the language
535 front end as well as the language runtime (when appropriate).
537 Unpack the core distribution as well as any language specific
538 distributions in the same directory.
540 If you also intend to build binutils (either to upgrade an existing
541 installation or for use in place of the corresponding tools of your
542 OS), unpack the binutils distribution either in the same directory or
543 a separate one. In the latter case, add symbolic links to any
544 components of the binutils you intend to build alongside the compiler
545 (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
546 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
548 Likewise the GMP, MPFR and MPC libraries can be automatically built
549 together with GCC. Unpack the GMP, MPFR and/or MPC source
550 distributions in the directory containing the GCC sources and rename
551 their directories to @file{gmp}, @file{mpfr} and @file{mpc},
552 respectively (or use symbolic links with the same name).
559 @uref{./index.html,,Return to the GCC Installation page}
563 @c ***Configuration***********************************************************
565 @comment node-name, next, previous, up
566 @node Configuration, Building, Downloading the source, Installing GCC
570 @chapter Installing GCC: Configuration
572 @cindex Configuration
573 @cindex Installing GCC: Configuration
575 Like most GNU software, GCC must be configured before it can be built.
576 This document describes the recommended configuration procedure
577 for both native and cross targets.
579 We use @var{srcdir} to refer to the toplevel source directory for
580 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
582 If you obtained the sources via SVN, @var{srcdir} must refer to the top
583 @file{gcc} directory, the one where the @file{MAINTAINERS} file can be
584 found, and not its @file{gcc} subdirectory, otherwise the build will fail.
586 If either @var{srcdir} or @var{objdir} is located on an automounted NFS
587 file system, the shell's built-in @command{pwd} command will return
588 temporary pathnames. Using these can lead to various sorts of build
589 problems. To avoid this issue, set the @env{PWDCMD} environment
590 variable to an automounter-aware @command{pwd} command, e.g.,
591 @command{pawd} or @samp{amq -w}, during the configuration and build
594 First, we @strong{highly} recommend that GCC be built into a
595 separate directory from the sources which does @strong{not} reside
596 within the source tree. This is how we generally build GCC; building
597 where @var{srcdir} == @var{objdir} should still work, but doesn't
598 get extensive testing; building where @var{objdir} is a subdirectory
599 of @var{srcdir} is unsupported.
601 If you have previously built GCC in the same directory for a
602 different target machine, do @samp{make distclean} to delete all files
603 that might be invalid. One of the files this deletes is @file{Makefile};
604 if @samp{make distclean} complains that @file{Makefile} does not exist
605 or issues a message like ``don't know how to make distclean'' it probably
606 means that the directory is already suitably clean. However, with the
607 recommended method of building in a separate @var{objdir}, you should
608 simply use a different @var{objdir} for each target.
610 Second, when configuring a native system, either @command{cc} or
611 @command{gcc} must be in your path or you must set @env{CC} in
612 your environment before running configure. Otherwise the configuration
616 Note that the bootstrap compiler and the resulting GCC must be link
617 compatible, else the bootstrap will fail with linker errors about
618 incompatible object file formats. Several multilibed targets are
619 affected by this requirement, see
621 @ref{Specific, host/target specific installation notes}.
624 @uref{specific.html,,host/target specific installation notes}.
633 % @var{srcdir}/configure [@var{options}] [@var{target}]
636 @heading Distributor options
638 If you will be distributing binary versions of GCC, with modifications
639 to the source code, you should use the options described in this
640 section to make clear that your version contains modifications.
643 @item --with-pkgversion=@var{version}
644 Specify a string that identifies your package. You may wish
645 to include a build number or build date. This version string will be
646 included in the output of @command{gcc --version}. This suffix does
647 not replace the default version string, only the @samp{GCC} part.
649 The default value is @samp{GCC}.
651 @item --with-bugurl=@var{url}
652 Specify the URL that users should visit if they wish to report a bug.
653 You are of course welcome to forward bugs reported to you to the FSF,
654 if you determine that they are not bugs in your modifications.
656 The default value refers to the FSF's GCC bug tracker.
660 @heading Target specification
663 GCC has code to correctly determine the correct value for @var{target}
664 for nearly all native systems. Therefore, we highly recommend you do
665 not provide a configure target when configuring a native compiler.
668 @var{target} must be specified as @option{--target=@var{target}}
669 when configuring a cross compiler; examples of valid targets would be
670 m68k-elf, sh-elf, etc.
673 Specifying just @var{target} instead of @option{--target=@var{target}}
674 implies that the host defaults to @var{target}.
678 @heading Options specification
680 Use @var{options} to override several configure time options for
681 GCC@. A list of supported @var{options} follows; @samp{configure
682 --help} may list other options, but those not listed below may not
683 work and should not normally be used.
685 Note that each @option{--enable} option has a corresponding
686 @option{--disable} option and that each @option{--with} option has a
687 corresponding @option{--without} option.
690 @item --prefix=@var{dirname}
691 Specify the toplevel installation
692 directory. This is the recommended way to install the tools into a directory
693 other than the default. The toplevel installation directory defaults to
696 We @strong{highly} recommend against @var{dirname} being the same or a
697 subdirectory of @var{objdir} or vice versa. If specifying a directory
698 beneath a user's home directory tree, some shells will not expand
699 @var{dirname} correctly if it contains the @samp{~} metacharacter; use
702 The following standard @command{autoconf} options are supported. Normally you
703 should not need to use these options.
705 @item --exec-prefix=@var{dirname}
706 Specify the toplevel installation directory for architecture-dependent
707 files. The default is @file{@var{prefix}}.
709 @item --bindir=@var{dirname}
710 Specify the installation directory for the executables called by users
711 (such as @command{gcc} and @command{g++}). The default is
712 @file{@var{exec-prefix}/bin}.
714 @item --libdir=@var{dirname}
715 Specify the installation directory for object code libraries and
716 internal data files of GCC@. The default is @file{@var{exec-prefix}/lib}.
718 @item --libexecdir=@var{dirname}
719 Specify the installation directory for internal executables of GCC@.
720 The default is @file{@var{exec-prefix}/libexec}.
722 @item --with-slibdir=@var{dirname}
723 Specify the installation directory for the shared libgcc library. The
724 default is @file{@var{libdir}}.
726 @item --datarootdir=@var{dirname}
727 Specify the root of the directory tree for read-only architecture-independent
728 data files referenced by GCC@. The default is @file{@var{prefix}/share}.
730 @item --infodir=@var{dirname}
731 Specify the installation directory for documentation in info format.
732 The default is @file{@var{datarootdir}/info}.
734 @item --datadir=@var{dirname}
735 Specify the installation directory for some architecture-independent
736 data files referenced by GCC@. The default is @file{@var{datarootdir}}.
738 @item --docdir=@var{dirname}
739 Specify the installation directory for documentation files (other
740 than Info) for GCC@. The default is @file{@var{datarootdir}/doc}.
742 @item --htmldir=@var{dirname}
743 Specify the installation directory for HTML documentation files.
744 The default is @file{@var{docdir}}.
746 @item --pdfdir=@var{dirname}
747 Specify the installation directory for PDF documentation files.
748 The default is @file{@var{docdir}}.
750 @item --mandir=@var{dirname}
751 Specify the installation directory for manual pages. The default is
752 @file{@var{datarootdir}/man}. (Note that the manual pages are only extracts
753 from the full GCC manuals, which are provided in Texinfo format. The manpages
754 are derived by an automatic conversion process from parts of the full
757 @item --with-gxx-include-dir=@var{dirname}
759 the installation directory for G++ header files. The default depends
760 on other configuration options, and differs between cross and native
765 @item --program-prefix=@var{prefix}
766 GCC supports some transformations of the names of its programs when
767 installing them. This option prepends @var{prefix} to the names of
768 programs to install in @var{bindir} (see above). For example, specifying
769 @option{--program-prefix=foo-} would result in @samp{gcc}
770 being installed as @file{/usr/local/bin/foo-gcc}.
772 @item --program-suffix=@var{suffix}
773 Appends @var{suffix} to the names of programs to install in @var{bindir}
774 (see above). For example, specifying @option{--program-suffix=-3.1}
775 would result in @samp{gcc} being installed as
776 @file{/usr/local/bin/gcc-3.1}.
778 @item --program-transform-name=@var{pattern}
779 Applies the @samp{sed} script @var{pattern} to be applied to the names
780 of programs to install in @var{bindir} (see above). @var{pattern} has to
781 consist of one or more basic @samp{sed} editing commands, separated by
782 semicolons. For example, if you want the @samp{gcc} program name to be
783 transformed to the installed program @file{/usr/local/bin/myowngcc} and
784 the @samp{g++} program name to be transformed to
785 @file{/usr/local/bin/gspecial++} without changing other program names,
786 you could use the pattern
787 @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}
788 to achieve this effect.
790 All three options can be combined and used together, resulting in more
791 complex conversion patterns. As a basic rule, @var{prefix} (and
792 @var{suffix}) are prepended (appended) before further transformations
793 can happen with a special transformation script @var{pattern}.
795 As currently implemented, this option only takes effect for native
796 builds; cross compiler binaries' names are not transformed even when a
797 transformation is explicitly asked for by one of these options.
799 For native builds, some of the installed programs are also installed
800 with the target alias in front of their name, as in
801 @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
802 before the target alias is prepended to the name---so, specifying
803 @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
804 resulting binary would be installed as
805 @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.
807 As a last shortcoming, none of the installed Ada programs are
808 transformed yet, which will be fixed in some time.
810 @item --with-local-prefix=@var{dirname}
812 installation directory for local include files. The default is
813 @file{/usr/local}. Specify this option if you want the compiler to
814 search directory @file{@var{dirname}/include} for locally installed
815 header files @emph{instead} of @file{/usr/local/include}.
817 You should specify @option{--with-local-prefix} @strong{only} if your
818 site has a different convention (not @file{/usr/local}) for where to put
821 The default value for @option{--with-local-prefix} is @file{/usr/local}
822 regardless of the value of @option{--prefix}. Specifying
823 @option{--prefix} has no effect on which directory GCC searches for
824 local header files. This may seem counterintuitive, but actually it is
827 The purpose of @option{--prefix} is to specify where to @emph{install
828 GCC}. The local header files in @file{/usr/local/include}---if you put
829 any in that directory---are not part of GCC@. They are part of other
830 programs---perhaps many others. (GCC installs its own header files in
831 another directory which is based on the @option{--prefix} value.)
833 Both the local-prefix include directory and the GCC-prefix include
834 directory are part of GCC's ``system include'' directories. Although these
835 two directories are not fixed, they need to be searched in the proper
836 order for the correct processing of the include_next directive. The
837 local-prefix include directory is searched before the GCC-prefix
838 include directory. Another characteristic of system include directories
839 is that pedantic warnings are turned off for headers in these directories.
841 Some autoconf macros add @option{-I @var{directory}} options to the
842 compiler command line, to ensure that directories containing installed
843 packages' headers are searched. When @var{directory} is one of GCC's
844 system include directories, GCC will ignore the option so that system
845 directories continue to be processed in the correct order. This
846 may result in a search order different from what was specified but the
847 directory will still be searched.
849 GCC automatically searches for ordinary libraries using
850 @env{GCC_EXEC_PREFIX}. Thus, when the same installation prefix is
851 used for both GCC and packages, GCC will automatically search for
852 both headers and libraries. This provides a configuration that is
853 easy to use. GCC behaves in a manner similar to that when it is
854 installed as a system compiler in @file{/usr}.
856 Sites that need to install multiple versions of GCC may not want to
857 use the above simple configuration. It is possible to use the
858 @option{--program-prefix}, @option{--program-suffix} and
859 @option{--program-transform-name} options to install multiple versions
860 into a single directory, but it may be simpler to use different prefixes
861 and the @option{--with-local-prefix} option to specify the location of the
862 site-specific files for each version. It will then be necessary for
863 users to specify explicitly the location of local site libraries
864 (e.g., with @env{LIBRARY_PATH}).
866 The same value can be used for both @option{--with-local-prefix} and
867 @option{--prefix} provided it is not @file{/usr}. This can be used
868 to avoid the default search of @file{/usr/local/include}.
870 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
871 The directory you use for @option{--with-local-prefix} @strong{must not}
872 contain any of the system's standard header files. If it did contain
873 them, certain programs would be miscompiled (including GNU Emacs, on
874 certain targets), because this would override and nullify the header
875 file corrections made by the @command{fixincludes} script.
877 Indications are that people who use this option use it based on mistaken
878 ideas of what it is for. People use it as if it specified where to
879 install part of GCC@. Perhaps they make this assumption because
880 installing GCC creates the directory.
882 @item --enable-shared[=@var{package}[,@dots{}]]
883 Build shared versions of libraries, if shared libraries are supported on
884 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
885 are enabled by default on all platforms that support shared libraries.
887 If a list of packages is given as an argument, build shared libraries
888 only for the listed packages. For other packages, only static libraries
889 will be built. Package names currently recognized in the GCC tree are
890 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
891 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc},
892 @samp{ada}, @samp{libada}, @samp{libjava} and @samp{libobjc}.
893 Note @samp{libiberty} does not support shared libraries at all.
895 Use @option{--disable-shared} to build only static libraries. Note that
896 @option{--disable-shared} does not accept a list of package names as
897 argument, only @option{--enable-shared} does.
899 @item @anchor{with-gnu-as}--with-gnu-as
900 Specify that the compiler should assume that the
901 assembler it finds is the GNU assembler. However, this does not modify
902 the rules to find an assembler and will result in confusion if the
903 assembler found is not actually the GNU assembler. (Confusion may also
904 result if the compiler finds the GNU assembler but has not been
905 configured with @option{--with-gnu-as}.) If you have more than one
906 assembler installed on your system, you may want to use this option in
907 connection with @option{--with-as=@var{pathname}} or
908 @option{--with-build-time-tools=@var{pathname}}.
910 The following systems are the only ones where it makes a difference
911 whether you use the GNU assembler. On any other system,
912 @option{--with-gnu-as} has no effect.
915 @item @samp{hppa1.0-@var{any}-@var{any}}
916 @item @samp{hppa1.1-@var{any}-@var{any}}
917 @item @samp{sparc-sun-solaris2.@var{any}}
918 @item @samp{sparc64-@var{any}-solaris2.@var{any}}
921 @item @anchor{with-as}--with-as=@var{pathname}
922 Specify that the compiler should use the assembler pointed to by
923 @var{pathname}, rather than the one found by the standard rules to find
924 an assembler, which are:
927 Unless GCC is being built with a cross compiler, check the
928 @file{@var{libexec}/gcc/@var{target}/@var{version}} directory.
929 @var{libexec} defaults to @file{@var{exec-prefix}/libexec};
930 @var{exec-prefix} defaults to @var{prefix}, which
931 defaults to @file{/usr/local} unless overridden by the
932 @option{--prefix=@var{pathname}} switch described above. @var{target}
933 is the target system triple, such as @samp{sparc-sun-solaris2.7}, and
934 @var{version} denotes the GCC version, such as 3.0.
937 If the target system is the same that you are building on, check
938 operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
942 Check in the @env{PATH} for a tool whose name is prefixed by the
943 target system triple.
946 Check in the @env{PATH} for a tool whose name is not prefixed by the
947 target system triple, if the host and target system triple are
948 the same (in other words, we use a host tool if it can be used for
952 You may want to use @option{--with-as} if no assembler
953 is installed in the directories listed above, or if you have multiple
954 assemblers installed and want to choose one that is not found by the
957 @item @anchor{with-gnu-ld}--with-gnu-ld
958 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
961 @item --with-ld=@var{pathname}
962 Same as @uref{#with-as,,@option{--with-as}}
966 Specify that stabs debugging
967 information should be used instead of whatever format the host normally
968 uses. Normally GCC uses the same debug format as the host system.
970 On MIPS based systems and on Alphas, you must specify whether you want
971 GCC to create the normal ECOFF debugging format, or to use BSD-style
972 stabs passed through the ECOFF symbol table. The normal ECOFF debug
973 format cannot fully handle languages other than C@. BSD stabs format can
974 handle other languages, but it only works with the GNU debugger GDB@.
976 Normally, GCC uses the ECOFF debugging format by default; if you
977 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
979 No matter which default you choose when you configure GCC, the user
980 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
981 the debug format for a particular compilation.
983 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
984 @option{--with-gas} is used. It selects use of stabs debugging
985 information embedded in COFF output. This kind of debugging information
986 supports C++ well; ordinary COFF debugging information does not.
988 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
989 selects use of stabs debugging information embedded in ELF output. The
990 C++ compiler currently (2.6.0) does not support the DWARF debugging
991 information normally used on 386 SVR4 platforms; stabs provide a
992 workable alternative. This requires gas and gdb, as the normal SVR4
993 tools can not generate or interpret stabs.
995 @item --disable-multilib
996 Specify that multiple target
997 libraries to support different target variants, calling
998 conventions, etc.@: should not be built. The default is to build a
999 predefined set of them.
1001 Some targets provide finer-grained control over which multilibs are built
1002 (e.g., @option{--disable-softfloat}):
1008 fpu, 26bit, underscore, interwork, biendian, nofmult.
1011 softfloat, m68881, m68000, m68020.
1014 single-float, biendian, softfloat.
1016 @item powerpc*-*-*, rs6000*-*-*
1017 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
1022 @item --with-multilib-list=@var{list}
1023 @itemx --without-multilib-list
1024 Specify what multilibs to build.
1025 Currently only implemented for sh*-*-*.
1027 @var{list} is a comma separated list of CPU names. These must be of the
1028 form @code{sh*} or @code{m*} (in which case they match the compiler option
1029 for that processor). The list should not contain any endian options -
1030 these are handled by @option{--with-endian}.
1032 If @var{list} is empty, then there will be no multilibs for extra
1033 processors. The multilib for the secondary endian remains enabled.
1035 As a special case, if an entry in the list starts with a @code{!}
1036 (exclamation point), then it is added to the list of excluded multilibs.
1037 Entries of this sort should be compatible with @samp{MULTILIB_EXCLUDES}
1038 (once the leading @code{!} has been stripped).
1040 If @option{--with-multilib-list} is not given, then a default set of
1041 multilibs is selected based on the value of @option{--target}. This is
1042 usually the complete set of libraries, but some targets imply a more
1045 Example 1: to configure a compiler for SH4A only, but supporting both
1046 endians, with little endian being the default:
1048 --with-cpu=sh4a --with-endian=little,big --with-multilib-list=
1051 Example 2: to configure a compiler for both SH4A and SH4AL-DSP, but with
1052 only little endian SH4AL:
1054 --with-cpu=sh4a --with-endian=little,big --with-multilib-list=sh4al,!mb/m4al
1057 @item --with-endian=@var{endians}
1058 Specify what endians to use.
1059 Currently only implemented for sh*-*-*.
1061 @var{endians} may be one of the following:
1064 Use big endian exclusively.
1066 Use little endian exclusively.
1068 Use big endian by default. Provide a multilib for little endian.
1070 Use little endian by default. Provide a multilib for big endian.
1073 @item --enable-threads
1074 Specify that the target
1075 supports threads. This affects the Objective-C compiler and runtime
1076 library, and exception handling for other languages like C++ and Java.
1077 On some systems, this is the default.
1079 In general, the best (and, in many cases, the only known) threading
1080 model available will be configured for use. Beware that on some
1081 systems, GCC has not been taught what threading models are generally
1082 available for the system. In this case, @option{--enable-threads} is an
1083 alias for @option{--enable-threads=single}.
1085 @item --disable-threads
1086 Specify that threading support should be disabled for the system.
1087 This is an alias for @option{--enable-threads=single}.
1089 @item --enable-threads=@var{lib}
1091 @var{lib} is the thread support library. This affects the Objective-C
1092 compiler and runtime library, and exception handling for other languages
1093 like C++ and Java. The possibilities for @var{lib} are:
1101 Ada tasking support. For non-Ada programs, this setting is equivalent
1102 to @samp{single}. When used in conjunction with the Ada run time, it
1103 causes GCC to use the same thread primitives as Ada uses. This option
1104 is necessary when using both Ada and the back end exception handling,
1105 which is the default for most Ada targets.
1107 Generic MACH thread support, known to work on NeXTSTEP@. (Please note
1108 that the file needed to support this configuration, @file{gthr-mach.h}, is
1109 missing and thus this setting will cause a known bootstrap failure.)
1111 This is an alias for @samp{single}.
1113 Generic POSIX/Unix98 thread support.
1115 Generic POSIX/Unix95 thread support.
1117 RTEMS thread support.
1119 Disable thread support, should work for all platforms.
1121 Sun Solaris 2/Unix International thread support. Only use this if you
1122 really need to use this legacy API instead of the default, @samp{posix}.
1124 VxWorks thread support.
1126 Microsoft Win32 API thread support.
1128 Novell Kernel Services thread support.
1132 Specify that the target supports TLS (Thread Local Storage). Usually
1133 configure can correctly determine if TLS is supported. In cases where
1134 it guesses incorrectly, TLS can be explicitly enabled or disabled with
1135 @option{--enable-tls} or @option{--disable-tls}. This can happen if
1136 the assembler supports TLS but the C library does not, or if the
1137 assumptions made by the configure test are incorrect.
1140 Specify that the target does not support TLS.
1141 This is an alias for @option{--enable-tls=no}.
1143 @item --with-cpu=@var{cpu}
1144 @itemx --with-cpu-32=@var{cpu}
1145 @itemx --with-cpu-64=@var{cpu}
1146 Specify which cpu variant the compiler should generate code for by default.
1147 @var{cpu} will be used as the default value of the @option{-mcpu=} switch.
1148 This option is only supported on some targets, including ARM, i386, M68k,
1149 PowerPC, and SPARC@. The @option{--with-cpu-32} and
1150 @option{--with-cpu-64} options specify separate default CPUs for
1151 32-bit and 64-bit modes; these options are only supported for i386,
1154 @item --with-schedule=@var{cpu}
1155 @itemx --with-arch=@var{cpu}
1156 @itemx --with-arch-32=@var{cpu}
1157 @itemx --with-arch-64=@var{cpu}
1158 @itemx --with-tune=@var{cpu}
1159 @itemx --with-tune-32=@var{cpu}
1160 @itemx --with-tune-64=@var{cpu}
1161 @itemx --with-abi=@var{abi}
1162 @itemx --with-fpu=@var{type}
1163 @itemx --with-float=@var{type}
1164 These configure options provide default values for the @option{-mschedule=},
1165 @option{-march=}, @option{-mtune=}, @option{-mabi=}, and @option{-mfpu=}
1166 options and for @option{-mhard-float} or @option{-msoft-float}. As with
1167 @option{--with-cpu}, which switches will be accepted and acceptable values
1168 of the arguments depend on the target.
1170 @item --with-mode=@var{mode}
1171 Specify if the compiler should default to @option{-marm} or @option{-mthumb}.
1172 This option is only supported on ARM targets.
1174 @item --with-divide=@var{type}
1175 Specify how the compiler should generate code for checking for
1176 division by zero. This option is only supported on the MIPS target.
1177 The possibilities for @var{type} are:
1180 Division by zero checks use conditional traps (this is the default on
1181 systems that support conditional traps).
1183 Division by zero checks use the break instruction.
1186 @c If you make --with-llsc the default for additional targets,
1187 @c update the --with-llsc description in the MIPS section below.
1190 On MIPS targets, make @option{-mllsc} the default when no
1191 @option{-mno-lsc} option is passed. This is the default for
1192 Linux-based targets, as the kernel will emulate them if the ISA does
1195 @item --without-llsc
1196 On MIPS targets, make @option{-mno-llsc} the default when no
1197 @option{-mllsc} option is passed.
1200 On MIPS targets, make @option{-msynci} the default when no
1201 @option{-mno-synci} option is passed.
1203 @item --without-synci
1204 On MIPS targets, make @option{-mno-synci} the default when no
1205 @option{-msynci} option is passed. This is the default.
1207 @item --with-mips-plt
1208 On MIPS targets, make use of copy relocations and PLTs.
1209 These features are extensions to the traditional
1210 SVR4-based MIPS ABIs and require support from GNU binutils
1211 and the runtime C library.
1213 @item --enable-__cxa_atexit
1214 Define if you want to use __cxa_atexit, rather than atexit, to
1215 register C++ destructors for local statics and global objects.
1216 This is essential for fully standards-compliant handling of
1217 destructors, but requires __cxa_atexit in libc. This option is currently
1218 only available on systems with GNU libc. When enabled, this will cause
1219 @option{-fuse-cxa-atexit} to be passed by default.
1221 @item --enable-target-optspace
1223 libraries should be optimized for code space instead of code speed.
1224 This is the default for the m32r platform.
1226 @item --with-cpp-install-dir=@var{dirname}
1227 Specify that the user visible @command{cpp} program should be installed
1228 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
1230 @item --enable-initfini-array
1231 Force the use of sections @code{.init_array} and @code{.fini_array}
1232 (instead of @code{.init} and @code{.fini}) for constructors and
1233 destructors. Option @option{--disable-initfini-array} has the
1234 opposite effect. If neither option is specified, the configure script
1235 will try to guess whether the @code{.init_array} and
1236 @code{.fini_array} sections are supported and, if they are, use them.
1238 @item --enable-build-with-cxx
1239 Build GCC using a C++ compiler rather than a C compiler. This is an
1240 experimental option which may become the default in a later release.
1242 @item --enable-maintainer-mode
1243 The build rules that regenerate the Autoconf and Automake output files as
1244 well as the GCC master message catalog @file{gcc.pot} are normally
1245 disabled. This is because it can only be rebuilt if the complete source
1246 tree is present. If you have changed the sources and want to rebuild the
1247 catalog, configuring with @option{--enable-maintainer-mode} will enable
1248 this. Note that you need a recent version of the @code{gettext} tools
1251 @item --disable-bootstrap
1252 For a native build, the default configuration is to perform
1253 a 3-stage bootstrap of the compiler when @samp{make} is invoked,
1254 testing that GCC can compile itself correctly. If you want to disable
1255 this process, you can configure with @option{--disable-bootstrap}.
1257 @item --enable-bootstrap
1258 In special cases, you may want to perform a 3-stage build
1259 even if the target and host triplets are different.
1260 This is possible when the host can run code compiled for
1261 the target (e.g.@: host is i686-linux, target is i486-linux).
1262 Starting from GCC 4.2, to do this you have to configure explicitly
1263 with @option{--enable-bootstrap}.
1265 @item --enable-generated-files-in-srcdir
1266 Neither the .c and .h files that are generated from Bison and flex nor the
1267 info manuals and man pages that are built from the .texi files are present
1268 in the SVN development tree. When building GCC from that development tree,
1269 or from one of our snapshots, those generated files are placed in your
1270 build directory, which allows for the source to be in a readonly
1273 If you configure with @option{--enable-generated-files-in-srcdir} then those
1274 generated files will go into the source directory. This is mainly intended
1275 for generating release or prerelease tarballs of the GCC sources, since it
1276 is not a requirement that the users of source releases to have flex, Bison,
1279 @item --enable-version-specific-runtime-libs
1281 that runtime libraries should be installed in the compiler specific
1282 subdirectory (@file{@var{libdir}/gcc}) rather than the usual places. In
1283 addition, @samp{libstdc++}'s include files will be installed into
1284 @file{@var{libdir}} unless you overruled it by using
1285 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
1286 particularly useful if you intend to use several versions of GCC in
1287 parallel. This is currently supported by @samp{libgfortran},
1288 @samp{libjava}, @samp{libmudflap}, @samp{libstdc++}, and @samp{libobjc}.
1290 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
1291 Specify that only a particular subset of compilers and
1292 their runtime libraries should be built. For a list of valid values for
1293 @var{langN} you can issue the following command in the
1294 @file{gcc} directory of your GCC source tree:@*
1296 grep language= */config-lang.in
1298 Currently, you can use any of the following:
1299 @code{all}, @code{ada}, @code{c}, @code{c++}, @code{fortran}, @code{java},
1300 @code{objc}, @code{obj-c++}.
1301 Building the Ada compiler has special requirements, see below.
1302 If you do not pass this flag, or specify the option @code{all}, then all
1303 default languages available in the @file{gcc} sub-tree will be configured.
1304 Ada and Objective-C++ are not default languages; the rest are.
1305 Re-defining @code{LANGUAGES} when calling @samp{make} @strong{does not}
1306 work anymore, as those language sub-directories might not have been
1309 @item --enable-stage1-languages=@var{lang1},@var{lang2},@dots{}
1310 Specify that a particular subset of compilers and their runtime
1311 libraries should be built with the system C compiler during stage 1 of
1312 the bootstrap process, rather than only in later stages with the
1313 bootstrapped C compiler. The list of valid values is the same as for
1314 @option{--enable-languages}, and the option @code{all} will select all
1315 of the languages enabled by @option{--enable-languages}. This option is
1316 primarily useful for GCC development; for instance, when a development
1317 version of the compiler cannot bootstrap due to compiler bugs, or when
1318 one is debugging front ends other than the C front end. When this
1319 option is used, one can then build the target libraries for the
1320 specified languages with the stage-1 compiler by using @command{make
1321 stage1-bubble all-target}, or run the testsuite on the stage-1 compiler
1322 for the specified languages using @command{make stage1-start check-gcc}.
1324 @item --disable-libada
1325 Specify that the run-time libraries and tools used by GNAT should not
1326 be built. This can be useful for debugging, or for compatibility with
1327 previous Ada build procedures, when it was required to explicitly
1328 do a @samp{make -C gcc gnatlib_and_tools}.
1330 @item --disable-libssp
1331 Specify that the run-time libraries for stack smashing protection
1332 should not be built.
1334 @item --disable-libgomp
1335 Specify that the run-time libraries used by GOMP should not be built.
1338 Specify that the compiler should
1339 use DWARF 2 debugging information as the default.
1341 @item --enable-targets=all
1342 @itemx --enable-targets=@var{target_list}
1343 Some GCC targets, e.g.@: powerpc64-linux, build bi-arch compilers.
1344 These are compilers that are able to generate either 64-bit or 32-bit
1345 code. Typically, the corresponding 32-bit target, e.g.@:
1346 powerpc-linux for powerpc64-linux, only generates 32-bit code. This
1347 option enables the 32-bit target to be a bi-arch compiler, which is
1348 useful when you want a bi-arch compiler that defaults to 32-bit, and
1349 you are building a bi-arch or multi-arch binutils in a combined tree.
1350 On mips-linux, this will build a tri-arch compiler (ABI o32/n32/64),
1352 Currently, this option only affects sparc-linux, powerpc-linux, x86-linux
1355 @item --enable-secureplt
1356 This option enables @option{-msecure-plt} by default for powerpc-linux.
1358 @xref{RS/6000 and PowerPC Options,, RS/6000 and PowerPC Options, gcc,
1359 Using the GNU Compiler Collection (GCC)},
1362 See ``RS/6000 and PowerPC Options'' in the main manual
1366 This option enables @option{-mcld} by default for 32-bit x86 targets.
1368 @xref{i386 and x86-64 Options,, i386 and x86-64 Options, gcc,
1369 Using the GNU Compiler Collection (GCC)},
1372 See ``i386 and x86-64 Options'' in the main manual
1375 @item --enable-win32-registry
1376 @itemx --enable-win32-registry=@var{key}
1377 @itemx --disable-win32-registry
1378 The @option{--enable-win32-registry} option enables Microsoft Windows-hosted GCC
1379 to look up installations paths in the registry using the following key:
1382 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
1385 @var{key} defaults to GCC version number, and can be overridden by the
1386 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
1387 who use custom installers are encouraged to provide a different key,
1388 perhaps one comprised of vendor name and GCC version number, to
1389 avoid conflict with existing installations. This feature is enabled
1390 by default, and can be disabled by @option{--disable-win32-registry}
1391 option. This option has no effect on the other hosts.
1394 Specify that the machine does not have a floating point unit. This
1395 option only applies to @samp{m68k-sun-sunos@var{n}}. On any other
1396 system, @option{--nfp} has no effect.
1398 @item --enable-werror
1399 @itemx --disable-werror
1400 @itemx --enable-werror=yes
1401 @itemx --enable-werror=no
1402 When you specify this option, it controls whether certain files in the
1403 compiler are built with @option{-Werror} in bootstrap stage2 and later.
1404 If you don't specify it, @option{-Werror} is turned on for the main
1405 development trunk. However it defaults to off for release branches and
1406 final releases. The specific files which get @option{-Werror} are
1407 controlled by the Makefiles.
1409 @item --enable-checking
1410 @itemx --enable-checking=@var{list}
1411 When you specify this option, the compiler is built to perform internal
1412 consistency checks of the requested complexity. This does not change the
1413 generated code, but adds error checking within the compiler. This will
1414 slow down the compiler and may only work properly if you are building
1415 the compiler with GCC@. This is @samp{yes} by default when building
1416 from SVN or snapshots, but @samp{release} for releases. The default
1417 for building the stage1 compiler is @samp{yes}. More control
1418 over the checks may be had by specifying @var{list}. The categories of
1419 checks available are @samp{yes} (most common checks
1420 @samp{assert,misc,tree,gc,rtlflag,runtime}), @samp{no} (no checks at
1421 all), @samp{all} (all but @samp{valgrind}), @samp{release} (cheapest
1422 checks @samp{assert,runtime}) or @samp{none} (same as @samp{no}).
1423 Individual checks can be enabled with these flags @samp{assert},
1424 @samp{df}, @samp{fold}, @samp{gc}, @samp{gcac} @samp{misc}, @samp{rtl},
1425 @samp{rtlflag}, @samp{runtime}, @samp{tree}, and @samp{valgrind}.
1427 The @samp{valgrind} check requires the external @command{valgrind}
1428 simulator, available from @uref{http://valgrind.org/}. The
1429 @samp{df}, @samp{rtl}, @samp{gcac} and @samp{valgrind} checks are very expensive.
1430 To disable all checking, @samp{--disable-checking} or
1431 @samp{--enable-checking=none} must be explicitly requested. Disabling
1432 assertions will make the compiler and runtime slightly faster but
1433 increase the risk of undetected internal errors causing wrong code to be
1436 @item --disable-stage1-checking
1437 @item --enable-stage1-checking
1438 @itemx --enable-stage1-checking=@var{list}
1439 If no @option{--enable-checking} option is specified the stage1
1440 compiler will be built with @samp{yes} checking enabled, otherwise
1441 the stage1 checking flags are the same as specified by
1442 @option{--enable-checking}. To build the stage1 compiler with
1443 different checking options use @option{--enable-stage1-checking}.
1444 The list of checking options is the same as for @option{--enable-checking}.
1445 If your system is too slow or too small to bootstrap a released compiler
1446 with checking for stage1 enabled, you can use @samp{--disable-stage1-checking}
1447 to disable checking for the stage1 compiler.
1449 @item --enable-coverage
1450 @itemx --enable-coverage=@var{level}
1451 With this option, the compiler is built to collect self coverage
1452 information, every time it is run. This is for internal development
1453 purposes, and only works when the compiler is being built with gcc. The
1454 @var{level} argument controls whether the compiler is built optimized or
1455 not, values are @samp{opt} and @samp{noopt}. For coverage analysis you
1456 want to disable optimization, for performance analysis you want to
1457 enable optimization. When coverage is enabled, the default level is
1458 without optimization.
1460 @item --enable-gather-detailed-mem-stats
1461 When this option is specified more detailed information on memory
1462 allocation is gathered. This information is printed when using
1463 @option{-fmem-report}.
1466 @itemx --with-gc=@var{choice}
1467 With this option you can specify the garbage collector implementation
1468 used during the compilation process. @var{choice} can be one of
1469 @samp{page} and @samp{zone}, where @samp{page} is the default.
1472 @itemx --disable-nls
1473 The @option{--enable-nls} option enables Native Language Support (NLS),
1474 which lets GCC output diagnostics in languages other than American
1475 English. Native Language Support is enabled by default if not doing a
1476 canadian cross build. The @option{--disable-nls} option disables NLS@.
1478 @item --with-included-gettext
1479 If NLS is enabled, the @option{--with-included-gettext} option causes the build
1480 procedure to prefer its copy of GNU @command{gettext}.
1482 @item --with-catgets
1483 If NLS is enabled, and if the host lacks @code{gettext} but has the
1484 inferior @code{catgets} interface, the GCC build procedure normally
1485 ignores @code{catgets} and instead uses GCC's copy of the GNU
1486 @code{gettext} library. The @option{--with-catgets} option causes the
1487 build procedure to use the host's @code{catgets} in this situation.
1489 @item --with-libiconv-prefix=@var{dir}
1490 Search for libiconv header files in @file{@var{dir}/include} and
1491 libiconv library files in @file{@var{dir}/lib}.
1493 @item --enable-obsolete
1494 Enable configuration for an obsoleted system. If you attempt to
1495 configure GCC for a system (build, host, or target) which has been
1496 obsoleted, and you do not specify this flag, configure will halt with an
1499 All support for systems which have been obsoleted in one release of GCC
1500 is removed entirely in the next major release, unless someone steps
1501 forward to maintain the port.
1503 @item --enable-decimal-float
1504 @itemx --enable-decimal-float=yes
1505 @itemx --enable-decimal-float=no
1506 @itemx --enable-decimal-float=bid
1507 @itemx --enable-decimal-float=dpd
1508 @itemx --disable-decimal-float
1509 Enable (or disable) support for the C decimal floating point extension
1510 that is in the IEEE 754-2008 standard. This is enabled by default only
1511 on PowerPC, i386, and x86_64 GNU/Linux systems. Other systems may also
1512 support it, but require the user to specifically enable it. You can
1513 optionally control which decimal floating point format is used (either
1514 @samp{bid} or @samp{dpd}). The @samp{bid} (binary integer decimal)
1515 format is default on i386 and x86_64 systems, and the @samp{dpd}
1516 (densely packed decimal) format is default on PowerPC systems.
1518 @item --enable-fixed-point
1519 @itemx --disable-fixed-point
1520 Enable (or disable) support for C fixed-point arithmetic.
1521 This option is enabled by default for some targets (such as MIPS) which
1522 have hardware-support for fixed-point operations. On other targets, you
1523 may enable this option manually.
1525 @item --with-long-double-128
1526 Specify if @code{long double} type should be 128-bit by default on selected
1527 GNU/Linux architectures. If using @code{--without-long-double-128},
1528 @code{long double} will be by default 64-bit, the same as @code{double} type.
1529 When neither of these configure options are used, the default will be
1530 128-bit @code{long double} when built against GNU C Library 2.4 and later,
1531 64-bit @code{long double} otherwise.
1533 @item --with-gmp=@var{pathname}
1534 @itemx --with-gmp-include=@var{pathname}
1535 @itemx --with-gmp-lib=@var{pathname}
1536 @itemx --with-mpfr=@var{pathname}
1537 @itemx --with-mpfr-include=@var{pathname}
1538 @itemx --with-mpfr-lib=@var{pathname}
1539 @itemx --with-mpc=@var{pathname}
1540 @itemx --with-mpc-include=@var{pathname}
1541 @itemx --with-mpc-lib=@var{pathname}
1542 If you do not have GMP (the GNU Multiple Precision library), the MPFR
1543 library and/or the MPC library installed in a standard location and
1544 you want to build GCC, you can explicitly specify the directory where
1545 they are installed (@samp{--with-gmp=@var{gmpinstalldir}},
1546 @samp{--with-mpfr=@var{mpfrinstalldir}},
1547 @samp{--with-mpc=@var{mpcinstalldir}}). The
1548 @option{--with-gmp=@var{gmpinstalldir}} option is shorthand for
1549 @option{--with-gmp-lib=@var{gmpinstalldir}/lib} and
1550 @option{--with-gmp-include=@var{gmpinstalldir}/include}. Likewise the
1551 @option{--with-mpfr=@var{mpfrinstalldir}} option is shorthand for
1552 @option{--with-mpfr-lib=@var{mpfrinstalldir}/lib} and
1553 @option{--with-mpfr-include=@var{mpfrinstalldir}/include}, also the
1554 @option{--with-mpc=@var{mpcinstalldir}} option is shorthand for
1555 @option{--with-mpc-lib=@var{mpcinstalldir}/lib} and
1556 @option{--with-mpc-include=@var{mpcinstalldir}/include}. If these
1557 shorthand assumptions are not correct, you can use the explicit
1558 include and lib options directly.
1560 @item --with-ppl=@var{pathname}
1561 @itemx --with-ppl-include=@var{pathname}
1562 @itemx --with-ppl-lib=@var{pathname}
1563 @itemx --with-cloog=@var{pathname}
1564 @itemx --with-cloog-include=@var{pathname}
1565 @itemx --with-cloog-lib=@var{pathname}
1566 If you do not have PPL (the Parma Polyhedra Library) and the CLooG
1567 libraries installed in a standard location and you want to build GCC,
1568 you can explicitly specify the directory where they are installed
1569 (@samp{--with-ppl=@var{pplinstalldir}},
1570 @samp{--with-cloog=@var{clooginstalldir}}). The
1571 @option{--with-ppl=@var{pplinstalldir}} option is shorthand for
1572 @option{--with-ppl-lib=@var{pplinstalldir}/lib} and
1573 @option{--with-ppl-include=@var{pplinstalldir}/include}. Likewise the
1574 @option{--with-cloog=@var{clooginstalldir}} option is shorthand for
1575 @option{--with-cloog-lib=@var{clooginstalldir}/lib} and
1576 @option{--with-cloog-include=@var{clooginstalldir}/include}. If these
1577 shorthand assumptions are not correct, you can use the explicit
1578 include and lib options directly.
1580 @item --with-host-libstdcxx=@var{linker-args}
1581 If you are linking with a static copy of PPL, you can use this option
1582 to specify how the linker should find the standard C++ library used
1583 internally by PPL. Typical values of @var{linker-args} might be
1584 @samp{-lstdc++} or @samp{-Wl,-Bstatic,-lstdc++,-Bdynamic -lm}. If you are
1585 linking with a shared copy of PPL, you probably do not need this
1586 option; shared library dependencies will cause the linker to search
1587 for the standard C++ library automatically.
1589 @item --with-stage1-ldflags=@var{flags}
1590 This option may be used to set linker flags to be used when linking
1591 stage 1 of GCC. These are also used when linking GCC if configured with
1592 @option{--disable-bootstrap}. By default no special flags are used.
1594 @item --with-stage1-libs=@var{libs}
1595 This option may be used to set libraries to be used when linking stage 1
1596 of GCC. These are also used when linking GCC if configured with
1597 @option{--disable-bootstrap}. The default is the argument to
1598 @option{--with-host-libstdcxx}, if specified.
1600 @item --with-boot-ldflags=@var{flags}
1601 This option may be used to set linker flags to be used when linking
1602 stage 2 and later when bootstrapping GCC. By default no special flags
1605 @item --with-boot-libs=@var{libs}
1606 This option may be used to set libraries to be used when linking stage 2
1607 and later when bootstrapping GCC. The default is the argument to
1608 @option{--with-host-libstdcxx}, if specified.
1610 @item --with-debug-prefix-map=@var{map}
1611 Convert source directory names using @option{-fdebug-prefix-map} when
1612 building runtime libraries. @samp{@var{map}} is a space-separated
1613 list of maps of the form @samp{@var{old}=@var{new}}.
1615 @item --enable-linker-build-id
1616 Tells GCC to pass @option{--build-id} option to the linker for all final
1617 links (links performed without the @option{-r} or @option{--relocatable}
1618 option), if the linker supports it. If you specify
1619 @option{--enable-linker-build-id}, but your linker does not
1620 support @option{--build-id} option, a warning is issued and the
1621 @option{--enable-linker-build-id} option is ignored. The default is off.
1623 @item --enable-gnu-unique-object
1624 @itemx --disable-gnu-unique-object
1625 Tells GCC to use the gnu_unique_object relocation for C++ template
1626 static data members and inline function local statics. Enabled by
1627 default for a native toolchain with an assembler that accepts it and
1628 GLIBC 2.11 or above, otherwise disabled.
1632 @subheading Cross-Compiler-Specific Options
1633 The following options only apply to building cross compilers.
1636 @item --with-sysroot
1637 @itemx --with-sysroot=@var{dir}
1638 Tells GCC to consider @var{dir} as the root of a tree that contains a
1639 (subset of) the root filesystem of the target operating system.
1640 Target system headers, libraries and run-time object files will be
1641 searched in there. More specifically, this acts as if
1642 @option{--sysroot=@var{dir}} was added to the default options of the built
1643 compiler. The specified directory is not copied into the
1644 install tree, unlike the options @option{--with-headers} and
1645 @option{--with-libs} that this option obsoletes. The default value,
1646 in case @option{--with-sysroot} is not given an argument, is
1647 @option{$@{gcc_tooldir@}/sys-root}. If the specified directory is a
1648 subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to
1649 the GCC binaries if the installation tree is moved.
1651 This option affects the system root for the compiler used to build
1652 target libraries (which runs on the build system) and the compiler newly
1653 installed with @code{make install}; it does not affect the compiler which is
1654 used to build GCC itself.
1656 @item --with-build-sysroot
1657 @itemx --with-build-sysroot=@var{dir}
1658 Tells GCC to consider @var{dir} as the system root (see
1659 @option{--with-sysroot}) while building target libraries, instead of
1660 the directory specified with @option{--with-sysroot}. This option is
1661 only useful when you are already using @option{--with-sysroot}. You
1662 can use @option{--with-build-sysroot} when you are configuring with
1663 @option{--prefix} set to a directory that is different from the one in
1664 which you are installing GCC and your target libraries.
1666 This option affects the system root for the compiler used to build
1667 target libraries (which runs on the build system); it does not affect
1668 the compiler which is used to build GCC itself.
1670 @item --with-headers
1671 @itemx --with-headers=@var{dir}
1672 Deprecated in favor of @option{--with-sysroot}.
1673 Specifies that target headers are available when building a cross compiler.
1674 The @var{dir} argument specifies a directory which has the target include
1675 files. These include files will be copied into the @file{gcc} install
1676 directory. @emph{This option with the @var{dir} argument is required} when
1677 building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include}
1678 doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does
1679 pre-exist, the @var{dir} argument may be omitted. @command{fixincludes}
1680 will be run on these files to make them compatible with GCC@.
1682 @item --without-headers
1683 Tells GCC not use any target headers from a libc when building a cross
1684 compiler. When crossing to GNU/Linux, you need the headers so GCC
1685 can build the exception handling for libgcc.
1688 @itemx --with-libs="@var{dir1} @var{dir2} @dots{} @var{dirN}"
1689 Deprecated in favor of @option{--with-sysroot}.
1690 Specifies a list of directories which contain the target runtime
1691 libraries. These libraries will be copied into the @file{gcc} install
1692 directory. If the directory list is omitted, this option has no
1696 Specifies that @samp{newlib} is
1697 being used as the target C library. This causes @code{__eprintf} to be
1698 omitted from @file{libgcc.a} on the assumption that it will be provided by
1701 @item --with-build-time-tools=@var{dir}
1702 Specifies where to find the set of target tools (assembler, linker, etc.)
1703 that will be used while building GCC itself. This option can be useful
1704 if the directory layouts are different between the system you are building
1705 GCC on, and the system where you will deploy it.
1707 For example, on an @samp{ia64-hp-hpux} system, you may have the GNU
1708 assembler and linker in @file{/usr/bin}, and the native tools in a
1709 different path, and build a toolchain that expects to find the
1710 native tools in @file{/usr/bin}.
1712 When you use this option, you should ensure that @var{dir} includes
1713 @command{ar}, @command{as}, @command{ld}, @command{nm},
1714 @command{ranlib} and @command{strip} if necessary, and possibly
1715 @command{objdump}. Otherwise, GCC may use an inconsistent set of
1719 @subheading Java-Specific Options
1721 The following option applies to the build of the Java front end.
1724 @item --disable-libgcj
1725 Specify that the run-time libraries
1726 used by GCJ should not be built. This is useful in case you intend
1727 to use GCJ with some other run-time, or you're going to install it
1728 separately, or it just happens not to build on your particular
1729 machine. In general, if the Java front end is enabled, the GCJ
1730 libraries will be enabled too, unless they're known to not work on
1731 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
1732 may need to port it; in this case, before modifying the top-level
1733 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
1734 you may use @option{--enable-libgcj} to override the default.
1738 The following options apply to building @samp{libgcj}.
1740 @subsubheading General Options
1743 @item --enable-java-maintainer-mode
1744 By default the @samp{libjava} build will not attempt to compile the
1745 @file{.java} source files to @file{.class}. Instead, it will use the
1746 @file{.class} files from the source tree. If you use this option you
1747 must have executables named @command{ecj1} and @command{gjavah} in your path
1748 for use by the build. You must use this option if you intend to
1749 modify any @file{.java} files in @file{libjava}.
1751 @item --with-java-home=@var{dirname}
1752 This @samp{libjava} option overrides the default value of the
1753 @samp{java.home} system property. It is also used to set
1754 @samp{sun.boot.class.path} to @file{@var{dirname}/lib/rt.jar}. By
1755 default @samp{java.home} is set to @file{@var{prefix}} and
1756 @samp{sun.boot.class.path} to
1757 @file{@var{datadir}/java/libgcj-@var{version}.jar}.
1759 @item --with-ecj-jar=@var{filename}
1760 This option can be used to specify the location of an external jar
1761 file containing the Eclipse Java compiler. A specially modified
1762 version of this compiler is used by @command{gcj} to parse
1763 @file{.java} source files. If this option is given, the
1764 @samp{libjava} build will create and install an @file{ecj1} executable
1765 which uses this jar file at runtime.
1767 If this option is not given, but an @file{ecj.jar} file is found in
1768 the topmost source tree at configure time, then the @samp{libgcj}
1769 build will create and install @file{ecj1}, and will also install the
1770 discovered @file{ecj.jar} into a suitable place in the install tree.
1772 If @file{ecj1} is not installed, then the user will have to supply one
1773 on his path in order for @command{gcj} to properly parse @file{.java}
1774 source files. A suitable jar is available from
1775 @uref{ftp://sourceware.org/pub/java/}.
1777 @item --disable-getenv-properties
1778 Don't set system properties from @env{GCJ_PROPERTIES}.
1780 @item --enable-hash-synchronization
1781 Use a global hash table for monitor locks. Ordinarily,
1782 @samp{libgcj}'s @samp{configure} script automatically makes
1783 the correct choice for this option for your platform. Only use
1784 this if you know you need the library to be configured differently.
1786 @item --enable-interpreter
1787 Enable the Java interpreter. The interpreter is automatically
1788 enabled by default on all platforms that support it. This option
1789 is really only useful if you want to disable the interpreter
1790 (using @option{--disable-interpreter}).
1792 @item --disable-java-net
1793 Disable java.net. This disables the native part of java.net only,
1794 using non-functional stubs for native method implementations.
1796 @item --disable-jvmpi
1797 Disable JVMPI support.
1799 @item --disable-libgcj-bc
1800 Disable BC ABI compilation of certain parts of libgcj. By default,
1801 some portions of libgcj are compiled with @option{-findirect-dispatch}
1802 and @option{-fno-indirect-classes}, allowing them to be overridden at
1805 If @option{--disable-libgcj-bc} is specified, libgcj is built without
1806 these options. This allows the compile-time linker to resolve
1807 dependencies when statically linking to libgcj. However it makes it
1808 impossible to override the affected portions of libgcj at run-time.
1810 @item --enable-reduced-reflection
1811 Build most of libgcj with @option{-freduced-reflection}. This reduces
1812 the size of libgcj at the expense of not being able to do accurate
1813 reflection on the classes it contains. This option is safe if you
1814 know that code using libgcj will never use reflection on the standard
1815 runtime classes in libgcj (including using serialization, RMI or CORBA).
1818 Enable runtime eCos target support.
1820 @item --without-libffi
1821 Don't use @samp{libffi}. This will disable the interpreter and JNI
1822 support as well, as these require @samp{libffi} to work.
1824 @item --enable-libgcj-debug
1825 Enable runtime debugging code.
1827 @item --enable-libgcj-multifile
1828 If specified, causes all @file{.java} source files to be
1829 compiled into @file{.class} files in one invocation of
1830 @samp{gcj}. This can speed up build time, but is more
1831 resource-intensive. If this option is unspecified or
1832 disabled, @samp{gcj} is invoked once for each @file{.java}
1833 file to compile into a @file{.class} file.
1835 @item --with-libiconv-prefix=DIR
1836 Search for libiconv in @file{DIR/include} and @file{DIR/lib}.
1838 @item --enable-sjlj-exceptions
1839 Force use of the @code{setjmp}/@code{longjmp}-based scheme for exceptions.
1840 @samp{configure} ordinarily picks the correct value based on the platform.
1841 Only use this option if you are sure you need a different setting.
1843 @item --with-system-zlib
1844 Use installed @samp{zlib} rather than that included with GCC@.
1846 @item --with-win32-nlsapi=ansi, unicows or unicode
1847 Indicates how MinGW @samp{libgcj} translates between UNICODE
1848 characters and the Win32 API@.
1850 @item --enable-java-home
1851 If enabled, this creates a JPackage compatible SDK environment during install.
1852 Note that if --enable-java-home is used, --with-arch-directory=ARCH must also
1855 @item --with-arch-directory=ARCH
1856 Specifies the name to use for the @file{jre/lib/ARCH} directory in the SDK
1857 environment created when --enable-java-home is passed. Typical names for this
1858 directory include i386, amd64, ia64, etc.
1860 @item --with-os-directory=DIR
1861 Specifies the OS directory for the SDK include directory. This is set to auto
1862 detect, and is typically 'linux'.
1864 @item --with-origin-name=NAME
1865 Specifies the JPackage origin name. This defaults to the 'gcj' in
1868 @item --with-arch-suffix=SUFFIX
1869 Specifies the suffix for the sdk directory. Defaults to the empty string.
1870 Examples include '.x86_64' in 'java-1.5.0-gcj-1.5.0.0.x86_64'.
1872 @item --with-jvm-root-dir=DIR
1873 Specifies where to install the SDK. Default is $(prefix)/lib/jvm.
1875 @item --with-jvm-jar-dir=DIR
1876 Specifies where to install jars. Default is $(prefix)/lib/jvm-exports.
1878 @item --with-python-dir=DIR
1879 Specifies where to install the Python modules used for aot-compile. DIR should
1880 not include the prefix used in installation. For example, if the Python modules
1881 are to be installed in /usr/lib/python2.5/site-packages, then
1882 --with-python-dir=/lib/python2.5/site-packages should be passed. If this is
1883 not specified, then the Python modules are installed in $(prefix)/share/python.
1885 @item --enable-aot-compile-rpm
1886 Adds aot-compile-rpm to the list of installed scripts.
1888 @item --enable-browser-plugin
1889 Build the gcjwebplugin web browser plugin.
1893 Use the single-byte @code{char} and the Win32 A functions natively,
1894 translating to and from UNICODE when using these functions. If
1895 unspecified, this is the default.
1898 Use the @code{WCHAR} and Win32 W functions natively. Adds
1899 @code{-lunicows} to @file{libgcj.spec} to link with @samp{libunicows}.
1900 @file{unicows.dll} needs to be deployed on Microsoft Windows 9X machines
1901 running built executables. @file{libunicows.a}, an open-source
1902 import library around Microsoft's @code{unicows.dll}, is obtained from
1903 @uref{http://libunicows.sourceforge.net/}, which also gives details
1904 on getting @file{unicows.dll} from Microsoft.
1907 Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not}
1908 add @code{-lunicows} to @file{libgcj.spec}. The built executables will
1909 only run on Microsoft Windows NT and above.
1913 Enable support for link-time optimization (LTO). This is enabled by
1914 default if a working libelf implementation is found (see
1915 @option{--with-libelf}).
1917 @item --with-libelf=@var{pathname}
1918 @itemx --with-libelf-include=@var{pathname}
1919 @itemx --with-libelf-lib=@var{pathname}
1920 If you do not have libelf installed in a standard location and you
1921 want to enable support for link-time optimization (LTO), you can
1922 explicitly specify the directory where libelf is installed
1923 (@samp{--with-libelf=@var{libelfinstalldir}}). The
1924 @option{--with-libelf=@var{libelfinstalldir}} option is shorthand for
1925 @option{--with-libelf-include=@var{libelfinstalldir}/include}
1926 @option{--with-libelf-lib=@var{libelfinstalldir}/lib}.
1929 Enable support for using @command{gold} as the linker. If gold support is
1930 enabled together with @option{--enable-lto}, an additional directory
1931 @file{lto-plugin} will be built. The code in this directory is a
1932 plugin for gold that allows the link-time optimizer to extract object
1933 files with LTO information out of library archives. See
1934 @option{-flto} and @option{-fwhopr} for details.
1937 @subsubheading AWT-Specific Options
1941 Use the X Window System.
1943 @item --enable-java-awt=PEER(S)
1944 Specifies the AWT peer library or libraries to build alongside
1945 @samp{libgcj}. If this option is unspecified or disabled, AWT
1946 will be non-functional. Current valid values are @option{gtk} and
1947 @option{xlib}. Multiple libraries should be separated by a
1948 comma (i.e.@: @option{--enable-java-awt=gtk,xlib}).
1950 @item --enable-gtk-cairo
1951 Build the cairo Graphics2D implementation on GTK@.
1953 @item --enable-java-gc=TYPE
1954 Choose garbage collector. Defaults to @option{boehm} if unspecified.
1956 @item --disable-gtktest
1957 Do not try to compile and run a test GTK+ program.
1959 @item --disable-glibtest
1960 Do not try to compile and run a test GLIB program.
1962 @item --with-libart-prefix=PFX
1963 Prefix where libart is installed (optional).
1965 @item --with-libart-exec-prefix=PFX
1966 Exec prefix where libart is installed (optional).
1968 @item --disable-libarttest
1969 Do not try to compile and run a test libart program.
1978 @uref{./index.html,,Return to the GCC Installation page}
1982 @c ***Building****************************************************************
1984 @comment node-name, next, previous, up
1985 @node Building, Testing, Configuration, Installing GCC
1991 @cindex Installing GCC: Building
1993 Now that GCC is configured, you are ready to build the compiler and
1996 Some commands executed when making the compiler may fail (return a
1997 nonzero status) and be ignored by @command{make}. These failures, which
1998 are often due to files that were not found, are expected, and can safely
2001 It is normal to have compiler warnings when compiling certain files.
2002 Unless you are a GCC developer, you can generally ignore these warnings
2003 unless they cause compilation to fail. Developers should attempt to fix
2004 any warnings encountered, however they can temporarily continue past
2005 warnings-as-errors by specifying the configure flag
2006 @option{--disable-werror}.
2008 On certain old systems, defining certain environment variables such as
2009 @env{CC} can interfere with the functioning of @command{make}.
2011 If you encounter seemingly strange errors when trying to build the
2012 compiler in a directory other than the source directory, it could be
2013 because you have previously configured the compiler in the source
2014 directory. Make sure you have done all the necessary preparations.
2016 If you build GCC on a BSD system using a directory stored in an old System
2017 V file system, problems may occur in running @command{fixincludes} if the
2018 System V file system doesn't support symbolic links. These problems
2019 result in a failure to fix the declaration of @code{size_t} in
2020 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
2021 that type mismatches occur, this could be the cause.
2023 The solution is not to use such a directory for building GCC@.
2025 Similarly, when building from SVN or snapshots, or if you modify
2026 @file{*.l} files, you need the Flex lexical analyzer generator
2027 installed. If you do not modify @file{*.l} files, releases contain
2028 the Flex-generated files and you do not need Flex installed to build
2029 them. There is still one Flex-based lexical analyzer (part of the
2030 build machinery, not of GCC itself) that is used even if you only
2031 build the C front end.
2033 When building from SVN or snapshots, or if you modify Texinfo
2034 documentation, you need version 4.7 or later of Texinfo installed if you
2035 want Info documentation to be regenerated. Releases contain Info
2036 documentation pre-built for the unmodified documentation in the release.
2038 @section Building a native compiler
2040 For a native build, the default configuration is to perform
2041 a 3-stage bootstrap of the compiler when @samp{make} is invoked.
2042 This will build the entire GCC system and ensure that it compiles
2043 itself correctly. It can be disabled with the @option{--disable-bootstrap}
2044 parameter to @samp{configure}, but bootstrapping is suggested because
2045 the compiler will be tested more completely and could also have
2048 The bootstrapping process will complete the following steps:
2052 Build tools necessary to build the compiler.
2055 Perform a 3-stage bootstrap of the compiler. This includes building
2056 three times the target tools for use by the compiler such as binutils
2057 (bfd, binutils, gas, gprof, ld, and opcodes) if they have been
2058 individually linked or moved into the top level GCC source tree before
2062 Perform a comparison test of the stage2 and stage3 compilers.
2065 Build runtime libraries using the stage3 compiler from the previous step.
2069 If you are short on disk space you might consider @samp{make
2070 bootstrap-lean} instead. The sequence of compilation is the
2071 same described above, but object files from the stage1 and
2072 stage2 of the 3-stage bootstrap of the compiler are deleted as
2073 soon as they are no longer needed.
2075 If you wish to use non-default GCC flags when compiling the stage2
2076 and stage3 compilers, set @code{BOOT_CFLAGS} on the command line when
2077 doing @samp{make}. For example, if you want to save additional space
2078 during the bootstrap and in the final installation as well, you can
2079 build the compiler binaries without debugging information as in the
2080 following example. This will save roughly 40% of disk space both for
2081 the bootstrap and the final installation. (Libraries will still contain
2082 debugging information.)
2085 make BOOT_CFLAGS='-O' bootstrap
2088 You can place non-default optimization flags into @code{BOOT_CFLAGS}; they
2089 are less well tested here than the default of @samp{-g -O2}, but should
2090 still work. In a few cases, you may find that you need to specify special
2091 flags such as @option{-msoft-float} here to complete the bootstrap; or,
2092 if the native compiler miscompiles the stage1 compiler, you may need
2093 to work around this, by choosing @code{BOOT_CFLAGS} to avoid the parts
2094 of the stage1 compiler that were miscompiled, or by using @samp{make
2095 bootstrap4} to increase the number of stages of bootstrap.
2097 @code{BOOT_CFLAGS} does not apply to bootstrapped target libraries.
2098 Since these are always compiled with the compiler currently being
2099 bootstrapped, you can use @code{CFLAGS_FOR_TARGET} to modify their
2100 compilation flags, as for non-bootstrapped target libraries.
2101 Again, if the native compiler miscompiles the stage1 compiler, you may
2102 need to work around this by avoiding non-working parts of the stage1
2103 compiler. Use @code{STAGE1_TFLAGS} to this end.
2105 If you used the flag @option{--enable-languages=@dots{}} to restrict
2106 the compilers to be built, only those you've actually enabled will be
2107 built. This will of course only build those runtime libraries, for
2108 which the particular compiler has been built. Please note,
2109 that re-defining @env{LANGUAGES} when calling @samp{make}
2110 @strong{does not} work anymore!
2112 If the comparison of stage2 and stage3 fails, this normally indicates
2113 that the stage2 compiler has compiled GCC incorrectly, and is therefore
2114 a potentially serious bug which you should investigate and report. (On
2115 a few systems, meaningful comparison of object files is impossible; they
2116 always appear ``different''. If you encounter this problem, you will
2117 need to disable comparison in the @file{Makefile}.)
2119 If you do not want to bootstrap your compiler, you can configure with
2120 @option{--disable-bootstrap}. In particular cases, you may want to
2121 bootstrap your compiler even if the target system is not the same as
2122 the one you are building on: for example, you could build a
2123 @code{powerpc-unknown-linux-gnu} toolchain on a
2124 @code{powerpc64-unknown-linux-gnu} host. In this case, pass
2125 @option{--enable-bootstrap} to the configure script.
2127 @code{BUILD_CONFIG} can be used to bring in additional customization
2128 to the build. It can be set to a whitespace-separated list of names.
2129 For each such @code{NAME}, top-level @file{config/@code{NAME}.mk} will
2130 be included by the top-level @file{Makefile}, bringing in any settings
2131 it contains. The default @code{BUILD_CONFIG} can be set using the
2132 configure option @option{--with-build-config=@code{NAME}...}. Some
2133 examples of supported build configurations are:
2136 @item @samp{bootstrap-O1}
2137 Removes any @option{-O}-started option from @code{BOOT_CFLAGS}, and adds
2138 @option{-O1} to it. @samp{BUILD_CONFIG=bootstrap-O1} is equivalent to
2139 @samp{BOOT_CFLAGS='-g -O1'}.
2141 @item @samp{bootstrap-O3}
2142 Analogous to @code{bootstrap-O1}.
2144 @item @samp{bootstrap-debug}
2145 Verifies that the compiler generates the same executable code, whether
2146 or not it is asked to emit debug information. To this end, this
2147 option builds stage2 host programs without debug information, and uses
2148 @file{contrib/compare-debug} to compare them with the stripped stage3
2149 object files. If @code{BOOT_CFLAGS} is overridden so as to not enable
2150 debug information, stage2 will have it, and stage3 won't. This option
2151 is enabled by default when GCC bootstrapping is enabled, if
2152 @code{strip} can turn object files compiled with and without debug
2153 info into identical object files. In addition to better test
2154 coverage, this option makes default bootstraps faster and leaner.
2156 @item @samp{bootstrap-debug-big}
2157 Rather than comparing stripped object files, as in
2158 @code{bootstrap-debug}, this option saves internal compiler dumps
2159 during stage2 and stage3 and compares them as well, which helps catch
2160 additional potential problems, but at a great cost in terms of disk
2161 space. It can be specified in addition to @samp{bootstrap-debug}.
2163 @item @samp{bootstrap-debug-lean}
2164 This option saves disk space compared with @code{bootstrap-debug-big},
2165 but at the expense of some recompilation. Instead of saving the dumps
2166 of stage2 and stage3 until the final compare, it uses
2167 @option{-fcompare-debug} to generate, compare and remove the dumps
2168 during stage3, repeating the compilation that already took place in
2169 stage2, whose dumps were not saved.
2171 @item @samp{bootstrap-debug-lib}
2172 This option tests executable code invariance over debug information
2173 generation on target libraries, just like @code{bootstrap-debug-lean}
2174 tests it on host programs. It builds stage3 libraries with
2175 @option{-fcompare-debug}, and it can be used along with any of the
2176 @code{bootstrap-debug} options above.
2178 There aren't @code{-lean} or @code{-big} counterparts to this option
2179 because most libraries are only build in stage3, so bootstrap compares
2180 would not get significant coverage. Moreover, the few libraries built
2181 in stage2 are used in stage3 host programs, so we wouldn't want to
2182 compile stage2 libraries with different options for comparison purposes.
2184 @item @samp{bootstrap-debug-ckovw}
2185 Arranges for error messages to be issued if the compiler built on any
2186 stage is run without the option @option{-fcompare-debug}. This is
2187 useful to verify the full @option{-fcompare-debug} testing coverage. It
2188 must be used along with @code{bootstrap-debug-lean} and
2189 @code{bootstrap-debug-lib}.
2191 @item @samp{bootstrap-time}
2192 Arranges for the run time of each program started by the GCC driver,
2193 built in any stage, to be logged to @file{time.log}, in the top level of
2198 @section Building a cross compiler
2200 When building a cross compiler, it is not generally possible to do a
2201 3-stage bootstrap of the compiler. This makes for an interesting problem
2202 as parts of GCC can only be built with GCC@.
2204 To build a cross compiler, we recommend first building and installing a
2205 native compiler. You can then use the native GCC compiler to build the
2206 cross compiler. The installed native compiler needs to be GCC version
2209 If the cross compiler is to be built with support for the Java
2210 programming language and the ability to compile .java source files is
2211 desired, the installed native compiler used to build the cross
2212 compiler needs to be the same GCC version as the cross compiler. In
2213 addition the cross compiler needs to be configured with
2214 @option{--with-ecj-jar=@dots{}}.
2216 Assuming you have already installed a native copy of GCC and configured
2217 your cross compiler, issue the command @command{make}, which performs the
2222 Build host tools necessary to build the compiler.
2225 Build target tools for use by the compiler such as binutils (bfd,
2226 binutils, gas, gprof, ld, and opcodes)
2227 if they have been individually linked or moved into the top level GCC source
2228 tree before configuring.
2231 Build the compiler (single stage only).
2234 Build runtime libraries using the compiler from the previous step.
2237 Note that if an error occurs in any step the make process will exit.
2239 If you are not building GNU binutils in the same source tree as GCC,
2240 you will need a cross-assembler and cross-linker installed before
2241 configuring GCC@. Put them in the directory
2242 @file{@var{prefix}/@var{target}/bin}. Here is a table of the tools
2243 you should put in this directory:
2247 This should be the cross-assembler.
2250 This should be the cross-linker.
2253 This should be the cross-archiver: a program which can manipulate
2254 archive files (linker libraries) in the target machine's format.
2257 This should be a program to construct a symbol table in an archive file.
2260 The installation of GCC will find these programs in that directory,
2261 and copy or link them to the proper place to for the cross-compiler to
2262 find them when run later.
2264 The easiest way to provide these files is to build the Binutils package.
2265 Configure it with the same @option{--host} and @option{--target}
2266 options that you use for configuring GCC, then build and install
2267 them. They install their executables automatically into the proper
2268 directory. Alas, they do not support all the targets that GCC
2271 If you are not building a C library in the same source tree as GCC,
2272 you should also provide the target libraries and headers before
2273 configuring GCC, specifying the directories with
2274 @option{--with-sysroot} or @option{--with-headers} and
2275 @option{--with-libs}. Many targets also require ``start files'' such
2276 as @file{crt0.o} and
2277 @file{crtn.o} which are linked into each executable. There may be several
2278 alternatives for @file{crt0.o}, for use with profiling or other
2279 compilation options. Check your target's definition of
2280 @code{STARTFILE_SPEC} to find out what start files it uses.
2282 @section Building in parallel
2284 GNU Make 3.80 and above, which is necessary to build GCC, support
2285 building in parallel. To activate this, you can use @samp{make -j 2}
2286 instead of @samp{make}. You can also specify a bigger number, and
2287 in most cases using a value greater than the number of processors in
2288 your machine will result in fewer and shorter I/O latency hits, thus
2289 improving overall throughput; this is especially true for slow drives
2290 and network filesystems.
2292 @section Building the Ada compiler
2294 In order to build GNAT, the Ada compiler, you need a working GNAT
2295 compiler (GCC version 3.4 or later).
2296 This includes GNAT tools such as @command{gnatmake} and
2297 @command{gnatlink}, since the Ada front end is written in Ada and
2298 uses some GNAT-specific extensions.
2300 In order to build a cross compiler, it is suggested to install
2301 the new compiler as native first, and then use it to build the cross
2304 @command{configure} does not test whether the GNAT installation works
2305 and has a sufficiently recent version; if too old a GNAT version is
2306 installed, the build will fail unless @option{--enable-languages} is
2307 used to disable building the Ada front end.
2309 @env{ADA_INCLUDE_PATH} and @env{ADA_OBJECT_PATH} environment variables
2310 must not be set when building the Ada compiler, the Ada tools, or the
2311 Ada runtime libraries. You can check that your build environment is clean
2312 by verifying that @samp{gnatls -v} lists only one explicit path in each
2315 @section Building with profile feedback
2317 It is possible to use profile feedback to optimize the compiler itself. This
2318 should result in a faster compiler binary. Experiments done on x86 using gcc
2319 3.3 showed approximately 7 percent speedup on compiling C programs. To
2320 bootstrap the compiler with profile feedback, use @code{make profiledbootstrap}.
2322 When @samp{make profiledbootstrap} is run, it will first build a @code{stage1}
2323 compiler. This compiler is used to build a @code{stageprofile} compiler
2324 instrumented to collect execution counts of instruction and branch
2325 probabilities. Then runtime libraries are compiled with profile collected.
2326 Finally a @code{stagefeedback} compiler is built using the information collected.
2328 Unlike standard bootstrap, several additional restrictions apply. The
2329 compiler used to build @code{stage1} needs to support a 64-bit integral type.
2330 It is recommended to only use GCC for this. Also parallel make is currently
2331 not supported since collisions in profile collecting may occur.
2338 @uref{./index.html,,Return to the GCC Installation page}
2342 @c ***Testing*****************************************************************
2344 @comment node-name, next, previous, up
2345 @node Testing, Final install, Building, Installing GCC
2349 @chapter Installing GCC: Testing
2352 @cindex Installing GCC: Testing
2355 Before you install GCC, we encourage you to run the testsuites and to
2356 compare your results with results from a similar configuration that have
2357 been submitted to the
2358 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
2359 Some of these archived results are linked from the build status lists
2360 at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who
2361 reports a successful build runs the testsuites and submits the results.
2362 This step is optional and may require you to download additional software,
2363 but it can give you confidence in your new GCC installation or point out
2364 problems before you install and start using your new GCC@.
2366 First, you must have @uref{download.html,,downloaded the testsuites}.
2367 These are part of the full distribution, but if you downloaded the
2368 ``core'' compiler plus any front ends, you must download the testsuites
2371 Second, you must have the testing tools installed. This includes
2372 @uref{http://www.gnu.org/software/dejagnu/,,DejaGnu}, Tcl, and Expect;
2373 the DejaGnu site has links to these.
2375 If the directories where @command{runtest} and @command{expect} were
2376 installed are not in the @env{PATH}, you may need to set the following
2377 environment variables appropriately, as in the following example (which
2378 assumes that DejaGnu has been installed under @file{/usr/local}):
2381 TCL_LIBRARY = /usr/local/share/tcl8.0
2382 DEJAGNULIBS = /usr/local/share/dejagnu
2385 (On systems such as Cygwin, these paths are required to be actual
2386 paths, not mounts or links; presumably this is due to some lack of
2387 portability in the DejaGnu code.)
2390 Finally, you can run the testsuite (which may take a long time):
2392 cd @var{objdir}; make -k check
2395 This will test various components of GCC, such as compiler
2396 front ends and runtime libraries. While running the testsuite, DejaGnu
2397 might emit some harmless messages resembling
2398 @samp{WARNING: Couldn't find the global config file.} or
2399 @samp{WARNING: Couldn't find tool init file} that can be ignored.
2401 If you are testing a cross-compiler, you may want to run the testsuite
2402 on a simulator as described at @uref{http://gcc.gnu.org/simtest-howto.html}.
2404 @section How can you run the testsuite on selected tests?
2406 In order to run sets of tests selectively, there are targets
2407 @samp{make check-gcc} and @samp{make check-g++}
2408 in the @file{gcc} subdirectory of the object directory. You can also
2409 just run @samp{make check} in a subdirectory of the object directory.
2412 A more selective way to just run all @command{gcc} execute tests in the
2416 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
2419 Likewise, in order to run only the @command{g++} ``old-deja'' tests in
2420 the testsuite with filenames matching @samp{9805*}, you would use
2423 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
2426 The @file{*.exp} files are located in the testsuite directories of the GCC
2427 source, the most important ones being @file{compile.exp},
2428 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
2429 To get a list of the possible @file{*.exp} files, pipe the
2430 output of @samp{make check} into a file and look at the
2431 @samp{Running @dots{} .exp} lines.
2433 @section Passing options and running multiple testsuites
2435 You can pass multiple options to the testsuite using the
2436 @samp{--target_board} option of DejaGNU, either passed as part of
2437 @samp{RUNTESTFLAGS}, or directly to @command{runtest} if you prefer to
2438 work outside the makefiles. For example,
2441 make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants"
2444 will run the standard @command{g++} testsuites (``unix'' is the target name
2445 for a standard native testsuite situation), passing
2446 @samp{-O3 -fmerge-constants} to the compiler on every test, i.e.,
2447 slashes separate options.
2449 You can run the testsuites multiple times using combinations of options
2450 with a syntax similar to the brace expansion of popular shells:
2453 @dots{}"--target_board=arm-sim\@{-mhard-float,-msoft-float\@}\@{-O1,-O2,-O3,\@}"
2456 (Note the empty option caused by the trailing comma in the final group.)
2457 The following will run each testsuite eight times using the @samp{arm-sim}
2458 target, as if you had specified all possible combinations yourself:
2461 --target_board=arm-sim/-mhard-float/-O1
2462 --target_board=arm-sim/-mhard-float/-O2
2463 --target_board=arm-sim/-mhard-float/-O3
2464 --target_board=arm-sim/-mhard-float
2465 --target_board=arm-sim/-msoft-float/-O1
2466 --target_board=arm-sim/-msoft-float/-O2
2467 --target_board=arm-sim/-msoft-float/-O3
2468 --target_board=arm-sim/-msoft-float
2471 They can be combined as many times as you wish, in arbitrary ways. This
2475 @dots{}"--target_board=unix/-Wextra\@{-O3,-fno-strength\@}\@{-fomit-frame,\@}"
2478 will generate four combinations, all involving @samp{-Wextra}.
2480 The disadvantage to this method is that the testsuites are run in serial,
2481 which is a waste on multiprocessor systems. For users with GNU Make and
2482 a shell which performs brace expansion, you can run the testsuites in
2483 parallel by having the shell perform the combinations and @command{make}
2484 do the parallel runs. Instead of using @samp{--target_board}, use a
2485 special makefile target:
2488 make -j@var{N} check-@var{testsuite}//@var{test-target}/@var{option1}/@var{option2}/@dots{}
2494 make -j3 check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@}
2497 will run three concurrent ``make-gcc'' testsuites, eventually testing all
2498 ten combinations as described above. Note that this is currently only
2499 supported in the @file{gcc} subdirectory. (To see how this works, try
2500 typing @command{echo} before the example given here.)
2503 @section Additional testing for Java Class Libraries
2505 The Java runtime tests can be executed via @samp{make check}
2506 in the @file{@var{target}/libjava/testsuite} directory in
2509 The @uref{http://sourceware.org/mauve/,,Mauve Project} provides
2510 a suite of tests for the Java Class Libraries. This suite can be run
2511 as part of libgcj testing by placing the Mauve tree within the libjava
2512 testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by
2513 specifying the location of that tree when invoking @samp{make}, as in
2514 @samp{make MAUVEDIR=~/mauve check}.
2516 @section How to interpret test results
2518 The result of running the testsuite are various @file{*.sum} and @file{*.log}
2519 files in the testsuite subdirectories. The @file{*.log} files contain a
2520 detailed log of the compiler invocations and the corresponding
2521 results, the @file{*.sum} files summarize the results. These summaries
2522 contain status codes for all tests:
2526 PASS: the test passed as expected
2528 XPASS: the test unexpectedly passed
2530 FAIL: the test unexpectedly failed
2532 XFAIL: the test failed as expected
2534 UNSUPPORTED: the test is not supported on this platform
2536 ERROR: the testsuite detected an error
2538 WARNING: the testsuite detected a possible problem
2541 It is normal for some tests to report unexpected failures. At the
2542 current time the testing harness does not allow fine grained control
2543 over whether or not a test is expected to fail. This problem should
2544 be fixed in future releases.
2547 @section Submitting test results
2549 If you want to report the results to the GCC project, use the
2550 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
2553 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
2554 -m gcc-testresults@@gcc.gnu.org |sh
2557 This script uses the @command{Mail} program to send the results, so
2558 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
2559 prepended to the testsuite summary and should contain any special
2560 remarks you have on your results or your build environment. Please
2561 do not edit the testsuite result block or the subject line, as these
2562 messages may be automatically processed.
2569 @uref{./index.html,,Return to the GCC Installation page}
2573 @c ***Final install***********************************************************
2575 @comment node-name, next, previous, up
2576 @node Final install, , Testing, Installing GCC
2578 @ifset finalinstallhtml
2580 @chapter Installing GCC: Final installation
2583 Now that GCC has been built (and optionally tested), you can install it with
2585 cd @var{objdir}; make install
2588 We strongly recommend to install into a target directory where there is
2589 no previous version of GCC present. Also, the GNAT runtime should not
2590 be stripped, as this would break certain features of the debugger that
2591 depend on this debugging information (catching Ada exceptions for
2594 That step completes the installation of GCC; user level binaries can
2595 be found in @file{@var{prefix}/bin} where @var{prefix} is the value
2596 you specified with the @option{--prefix} to configure (or
2597 @file{/usr/local} by default). (If you specified @option{--bindir},
2598 that directory will be used instead; otherwise, if you specified
2599 @option{--exec-prefix}, @file{@var{exec-prefix}/bin} will be used.)
2600 Headers for the C++ and Java libraries are installed in
2601 @file{@var{prefix}/include}; libraries in @file{@var{libdir}}
2602 (normally @file{@var{prefix}/lib}); internal parts of the compiler in
2603 @file{@var{libdir}/gcc} and @file{@var{libexecdir}/gcc}; documentation
2604 in info format in @file{@var{infodir}} (normally
2605 @file{@var{prefix}/info}).
2607 When installing cross-compilers, GCC's executables
2608 are not only installed into @file{@var{bindir}}, that
2609 is, @file{@var{exec-prefix}/bin}, but additionally into
2610 @file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory
2611 exists. Typically, such @dfn{tooldirs} hold target-specific
2612 binutils, including assembler and linker.
2614 Installation into a temporary staging area or into a @command{chroot}
2615 jail can be achieved with the command
2618 make DESTDIR=@var{path-to-rootdir} install
2621 @noindent where @var{path-to-rootdir} is the absolute path of
2622 a directory relative to which all installation paths will be
2623 interpreted. Note that the directory specified by @code{DESTDIR}
2624 need not exist yet; it will be created if necessary.
2626 There is a subtle point with tooldirs and @code{DESTDIR}:
2627 If you relocate a cross-compiler installation with
2628 e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory
2629 @file{@var{rootdir}/@var{exec-prefix}/@var{target-alias}/bin} will
2630 be filled with duplicated GCC executables only if it already exists,
2631 it will not be created otherwise. This is regarded as a feature,
2632 not as a bug, because it gives slightly more control to the packagers
2633 using the @code{DESTDIR} feature.
2635 If you are bootstrapping a released version of GCC then please
2636 quickly review the build status page for your release, available from
2637 @uref{http://gcc.gnu.org/buildstat.html}.
2638 If your system is not listed for the version of GCC that you built,
2640 @email{gcc@@gcc.gnu.org} indicating
2641 that you successfully built and installed GCC@.
2642 Include the following information:
2646 Output from running @file{@var{srcdir}/config.guess}. Do not send
2647 that file itself, just the one-line output from running it.
2650 The output of @samp{gcc -v} for your newly installed @command{gcc}.
2651 This tells us which version of GCC you built and the options you passed to
2655 Whether you enabled all languages or a subset of them. If you used a
2656 full distribution then this information is part of the configure
2657 options in the output of @samp{gcc -v}, but if you downloaded the
2658 ``core'' compiler plus additional front ends then it isn't apparent
2659 which ones you built unless you tell us about it.
2662 If the build was for GNU/Linux, also include:
2665 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
2666 this information should be available from @file{/etc/issue}.
2669 The version of the Linux kernel, available from @samp{uname --version}
2673 The version of glibc you used; for RPM-based systems like Red Hat,
2674 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
2675 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
2677 For other systems, you can include similar information if you think it is
2681 Any other information that you think would be useful to people building
2682 GCC on the same configuration. The new entry in the build status list
2683 will include a link to the archived copy of your message.
2686 We'd also like to know if the
2688 @ref{Specific, host/target specific installation notes}
2691 @uref{specific.html,,host/target specific installation notes}
2693 didn't include your host/target information or if that information is
2694 incomplete or out of date. Send a note to
2695 @email{gcc@@gcc.gnu.org} detailing how the information should be changed.
2697 If you find a bug, please report it following the
2698 @uref{../bugs/,,bug reporting guidelines}.
2700 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
2701 dvi}. You will need to have @command{texi2dvi} (version at least 4.7)
2702 and @TeX{} installed. This creates a number of @file{.dvi} files in
2703 subdirectories of @file{@var{objdir}}; these may be converted for
2704 printing with programs such as @command{dvips}. Alternately, by using
2705 @samp{make pdf} in place of @samp{make dvi}, you can create documentation
2706 in the form of @file{.pdf} files; this requires @command{texi2pdf}, which
2707 is included with Texinfo version 4.8 and later. You can also
2708 @uref{http://shop.fsf.org/,,buy printed manuals from the
2709 Free Software Foundation}, though such manuals may not be for the most
2710 recent version of GCC@.
2712 If you would like to generate online HTML documentation, do @samp{cd
2713 @var{objdir}; make html} and HTML will be generated for the gcc manuals in
2714 @file{@var{objdir}/gcc/HTML}.
2721 @uref{./index.html,,Return to the GCC Installation page}
2725 @c ***Binaries****************************************************************
2727 @comment node-name, next, previous, up
2728 @node Binaries, Specific, Installing GCC, Top
2732 @chapter Installing GCC: Binaries
2735 @cindex Installing GCC: Binaries
2737 We are often asked about pre-compiled versions of GCC@. While we cannot
2738 provide these for all platforms, below you'll find links to binaries for
2739 various platforms where creating them by yourself is not easy due to various
2742 Please note that we did not create these binaries, nor do we
2743 support them. If you have any problems installing them, please
2744 contact their makers.
2751 @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX};
2754 @uref{http://pware.hvcc.edu,,Hudson Valley Community College Open Source Software for IBM System p};
2757 @uref{http://www.perzl.org/aix/,,AIX 5L and 6 Open Source Packages}.
2761 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}.
2764 Renesas H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
2765 Development Tools for the Renesas H8/300[HS] Series}.
2771 @uref{http://hpux.cs.utah.edu/,,HP-UX Porting Center};
2774 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
2778 Motorola 68HC11/68HC12---@uref{http://www.gnu-m68hc11.org,,GNU
2779 Development Tools for the Motorola 68HC11/68HC12}.
2782 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
2783 OpenServer/Unixware}.
2786 Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware}.
2789 SGI---@uref{http://freeware.sgi.com/,,SGI Freeware}.
2795 The @uref{http://sourceware.org/cygwin/,,Cygwin} project;
2797 The @uref{http://www.mingw.org/,,MinGW} project.
2801 @uref{ftp://ftp.thewrittenword.com/packages/by-name/,,The
2802 Written Word} offers binaries for
2803 AIX 4.3.3, 5.1 and 5.2,
2805 Tru64 UNIX 4.0D and 5.1,
2807 HP-UX 10.20, 11.00, and 11.11, and
2808 Solaris/SPARC 2.5.1, 2.6, 7, 8, 9 and 10.
2811 @uref{http://www.openpkg.org/,,OpenPKG} offers binaries for quite a
2812 number of platforms.
2815 The @uref{http://gcc.gnu.org/wiki/GFortranBinaries,,GFortran Wiki} has
2816 links to GNU Fortran binaries for several platforms.
2824 @uref{./index.html,,Return to the GCC Installation page}
2828 @c ***Specific****************************************************************
2830 @comment node-name, next, previous, up
2831 @node Specific, Old, Binaries, Top
2835 @chapter Host/target specific installation notes for GCC
2838 @cindex Specific installation notes
2839 @cindex Target specific installation
2840 @cindex Host specific installation
2841 @cindex Target specific installation notes
2843 Please read this document carefully @emph{before} installing the
2844 GNU Compiler Collection on your machine.
2846 Note that this list of install notes is @emph{not} a list of supported
2847 hosts or targets. Not all supported hosts and targets are listed
2848 here, only the ones that require host-specific or target-specific
2854 @uref{#alpha-x-x,,alpha*-*-*}
2856 @uref{#alpha-dec-osf,,alpha*-dec-osf*}
2858 @uref{#arc-x-elf,,arc-*-elf}
2860 @uref{#arm-x-elf,,arm-*-elf}
2864 @uref{#bfin,,Blackfin}
2868 @uref{#x-x-freebsd,,*-*-freebsd*}
2870 @uref{#h8300-hms,,h8300-hms}
2872 @uref{#hppa-hp-hpux,,hppa*-hp-hpux*}
2874 @uref{#hppa-hp-hpux10,,hppa*-hp-hpux10}
2876 @uref{#hppa-hp-hpux11,,hppa*-hp-hpux11}
2878 @uref{#x-x-linux-gnu,,*-*-linux-gnu}
2880 @uref{#ix86-x-linux,,i?86-*-linux*}
2882 @uref{#ix86-x-solaris210,,i?86-*-solaris2.10}
2884 @uref{#ia64-x-linux,,ia64-*-linux}
2886 @uref{#ia64-x-hpux,,ia64-*-hpux*}
2888 @uref{#x-ibm-aix,,*-ibm-aix*}
2890 @uref{#iq2000-x-elf,,iq2000-*-elf}
2892 @uref{#lm32-x-elf,,lm32-*-elf}
2894 @uref{#lm32-x-uclinux,,lm32-*-uclinux}
2896 @uref{#m32c-x-elf,,m32c-*-elf}
2898 @uref{#m32r-x-elf,,m32r-*-elf}
2900 @uref{#m6811-elf,,m6811-elf}
2902 @uref{#m6812-elf,,m6812-elf}
2904 @uref{#m68k-x-x,,m68k-*-*}
2906 @uref{#m68k-uclinux,,m68k-uclinux}
2908 @uref{#mep-x-elf,,mep-*-elf}
2910 @uref{#mips-x-x,,mips-*-*}
2912 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
2914 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
2916 @uref{#powerpc-x-x,,powerpc*-*-*}
2918 @uref{#powerpc-x-darwin,,powerpc-*-darwin*}
2920 @uref{#powerpc-x-elf,,powerpc-*-elf}
2922 @uref{#powerpc-x-linux-gnu,,powerpc*-*-linux-gnu*}
2924 @uref{#powerpc-x-netbsd,,powerpc-*-netbsd*}
2926 @uref{#powerpc-x-eabisim,,powerpc-*-eabisim}
2928 @uref{#powerpc-x-eabi,,powerpc-*-eabi}
2930 @uref{#powerpcle-x-elf,,powerpcle-*-elf}
2932 @uref{#powerpcle-x-eabisim,,powerpcle-*-eabisim}
2934 @uref{#powerpcle-x-eabi,,powerpcle-*-eabi}
2936 @uref{#s390-x-linux,,s390-*-linux*}
2938 @uref{#s390x-x-linux,,s390x-*-linux*}
2940 @uref{#s390x-ibm-tpf,,s390x-ibm-tpf*}
2942 @uref{#x-x-solaris2,,*-*-solaris2*}
2944 @uref{#sparc-sun-solaris2,,sparc-sun-solaris2*}
2946 @uref{#sparc-sun-solaris27,,sparc-sun-solaris2.7}
2948 @uref{#sparc-x-linux,,sparc-*-linux*}
2950 @uref{#sparc64-x-solaris2,,sparc64-*-solaris2*}
2952 @uref{#sparcv9-x-solaris2,,sparcv9-*-solaris2*}
2954 @uref{#x-x-vxworks,,*-*-vxworks*}
2956 @uref{#x86-64-x-x,,x86_64-*-*, amd64-*-*}
2958 @uref{#xtensa-x-elf,,xtensa*-*-elf}
2960 @uref{#xtensa-x-linux,,xtensa*-*-linux*}
2962 @uref{#windows,,Microsoft Windows}
2964 @uref{#x-x-cygwin,,*-*-cygwin}
2966 @uref{#x-x-interix,,*-*-interix}
2968 @uref{#x-x-mingw32,,*-*-mingw32}
2972 @uref{#older,,Older systems}
2977 @uref{#elf,,all ELF targets} (SVR4, Solaris 2, etc.)
2983 <!-- -------- host/target specific issues start here ---------------- -->
2986 @heading @anchor{alpha-x-x}alpha*-*-*
2988 This section contains general configuration information for all
2989 alpha-based platforms using ELF (in particular, ignore this section for
2990 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
2991 section, please read all other sections that match your target.
2993 We require binutils 2.11.2 or newer.
2994 Previous binutils releases had a number of problems with DWARF 2
2995 debugging information, not the least of which is incorrect linking of
3001 @heading @anchor{alpha-dec-osf}alpha*-dec-osf*
3002 Systems using processors that implement the DEC Alpha architecture and
3003 are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
3004 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
3006 As of GCC 3.2, versions before @code{alpha*-dec-osf4} are no longer
3007 supported. (These are the versions which identify themselves as DEC
3010 In Digital Unix V4.0, virtual memory exhausted bootstrap failures
3011 may be fixed by configuring with @option{--with-gc=simple},
3012 reconfiguring Kernel Virtual Memory and Swap parameters
3013 per the @command{/usr/sbin/sys_check} Tuning Suggestions,
3014 or applying the patch in
3015 @uref{http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html}.
3017 In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
3018 currently (2001-06-13) work with @command{mips-tfile}. As a workaround,
3019 we need to use the old assembler, invoked via the barely documented
3020 @option{-oldas} option. To bootstrap GCC, you either need to use the
3024 % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
3027 or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
3030 % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
3033 As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld}
3034 are supported on Tru64 UNIX, so you must not configure GCC with
3035 @option{--with-gnu-as} or @option{--with-gnu-ld}.
3037 GCC writes a @samp{.verstamp} directive to the assembler output file
3038 unless it is built as a cross-compiler. It gets the version to use from
3039 the system header file @file{/usr/include/stamp.h}. If you install a
3040 new version of DEC Unix, you should rebuild GCC to pick up the new version
3043 @samp{make compare} may fail on old versions of DEC Unix unless you add
3044 @option{-save-temps} to @code{BOOT_CFLAGS}. On these systems, the name
3045 of the assembler input file is stored in the object file, and that makes
3046 comparison fail if it differs between the @code{stage1} and
3047 @code{stage2} compilations. The option @option{-save-temps} forces a
3048 fixed name to be used for the assembler input file, instead of a
3049 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
3050 unless the comparisons fail without that option. If you add
3051 @option{-save-temps}, you will have to manually delete the @samp{.i} and
3052 @samp{.s} files after each series of compilations.
3054 GCC now supports both the native (ECOFF) debugging format used by DBX
3055 and GDB and an encapsulated STABS format for use only with GDB@. See the
3056 discussion of the @option{--with-stabs} option of @file{configure} above
3057 for more information on these formats and how to select them.
3059 There is a bug in DEC's assembler that produces incorrect line numbers
3060 for ECOFF format when the @samp{.align} directive is used. To work
3061 around this problem, GCC will not emit such alignment directives
3062 while writing ECOFF format debugging information even if optimization is
3063 being performed. Unfortunately, this has the very undesirable
3064 side-effect that code addresses when @option{-O} is specified are
3065 different depending on whether or not @option{-g} is also specified.
3067 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
3068 DBX@. DEC is now aware of this problem with the assembler and hopes to
3069 provide a fix shortly.
3074 @heading @anchor{arc-x-elf}arc-*-elf
3075 Argonaut ARC processor.
3076 This configuration is intended for embedded systems.
3081 @heading @anchor{arm-x-elf}arm-*-elf
3082 ARM-family processors. Subtargets that use the ELF object format
3083 require GNU binutils 2.13 or newer. Such subtargets include:
3084 @code{arm-*-freebsd}, @code{arm-*-netbsdelf}, @code{arm-*-*linux}
3085 and @code{arm-*-rtems}.
3090 @heading @anchor{avr}avr
3092 ATMEL AVR-family micro controllers. These are used in embedded
3093 applications. There are no standard Unix configurations.
3095 @xref{AVR Options,, AVR Options, gcc, Using the GNU Compiler
3099 See ``AVR Options'' in the main manual
3101 for the list of supported MCU types.
3103 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
3105 Further installation notes and other useful information about AVR tools
3106 can also be obtained from:
3110 @uref{http://www.nongnu.org/avr/,,http://www.nongnu.org/avr/}
3112 @uref{http://www.amelek.gda.pl/avr/,,http://www.amelek.gda.pl/avr/}
3115 We @emph{strongly} recommend using binutils 2.13 or newer.
3117 The following error:
3119 Error: register required
3122 indicates that you should upgrade to a newer version of the binutils.
3127 @heading @anchor{bfin}Blackfin
3129 The Blackfin processor, an Analog Devices DSP.
3131 @xref{Blackfin Options,, Blackfin Options, gcc, Using the GNU Compiler
3135 See ``Blackfin Options'' in the main manual
3138 More information, and a version of binutils with support for this processor,
3139 is available at @uref{http://blackfin.uclinux.org}
3144 @heading @anchor{cris}CRIS
3146 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
3147 series. These are used in embedded applications.
3150 @xref{CRIS Options,, CRIS Options, gcc, Using the GNU Compiler
3154 See ``CRIS Options'' in the main manual
3156 for a list of CRIS-specific options.
3158 There are a few different CRIS targets:
3161 Mainly for monolithic embedded systems. Includes a multilib for the
3162 @samp{v10} core used in @samp{ETRAX 100 LX}.
3163 @item cris-axis-linux-gnu
3164 A GNU/Linux port for the CRIS architecture, currently targeting
3165 @samp{ETRAX 100 LX} by default.
3168 For @code{cris-axis-elf} you need binutils 2.11
3169 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
3171 Pre-packaged tools can be obtained from
3172 @uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More
3173 information about this platform is available at
3174 @uref{http://developer.axis.com/}.
3179 @heading @anchor{crx}CRX
3181 The CRX CompactRISC architecture is a low-power 32-bit architecture with
3182 fast context switching and architectural extensibility features.
3185 @xref{CRX Options,, CRX Options, gcc, Using and Porting the GNU Compiler
3190 See ``CRX Options'' in the main manual for a list of CRX-specific options.
3193 Use @samp{configure --target=crx-elf --enable-languages=c,c++} to configure
3194 GCC@ for building a CRX cross-compiler. The option @samp{--target=crx-elf}
3195 is also used to build the @samp{newlib} C library for CRX.
3197 It is also possible to build libstdc++-v3 for the CRX architecture. This
3198 needs to be done in a separate step with the following configure settings:
3199 @samp{gcc/libstdc++-v3/configure --host=crx-elf --with-newlib
3200 --enable-sjlj-exceptions --enable-cxx-flags='-fexceptions -frtti'}
3205 @heading @anchor{dos}DOS
3207 Please have a look at the @uref{binaries.html,,binaries page}.
3209 You cannot install GCC by itself on MSDOS; it will not compile under
3210 any MSDOS compiler except itself. You need to get the complete
3211 compilation package DJGPP, which includes binaries as well as sources,
3212 and includes all the necessary compilation tools and libraries.
3217 @heading @anchor{x-x-freebsd}*-*-freebsd*
3219 Support for FreeBSD 1 was discontinued in GCC 3.2. Support for
3220 FreeBSD 2 (and any mutant a.out variants of FreeBSD 3) was
3221 discontinued in GCC 4.0.
3223 In GCC 4.5, we enabled the use of @code{dl_iterate_phdr} inside boehm-gc on
3224 FreeBSD 7 or later. In order to better match the configuration of the
3225 FreeBSD system compiler: We also enabled the check to see if libc
3226 provides SSP support (which it does on FreeBSD 7), the use of
3227 @code{dl_iterate_phdr} inside @file{libgcc_s.so.1} (on FreeBSD 7 or later)
3228 and the use of @code{__cxa_atexit} by default (on FreeBSD 6 or later).
3230 We support FreeBSD using the ELF file format with DWARF 2 debugging
3231 for all CPU architectures. You may use @option{-gstabs} instead of
3232 @option{-g}, if you really want the old debugging format. There are
3233 no known issues with mixing object files and libraries with different
3234 debugging formats. Otherwise, this release of GCC should now match
3235 more of the configuration used in the stock FreeBSD configuration of
3236 GCC@. In particular, @option{--enable-threads} is now configured by
3237 default. However, as a general user, do not attempt to replace the
3238 system compiler with this release. Known to bootstrap and check with
3239 good results on FreeBSD 7.2-STABLE@. In the past, known to bootstrap
3240 and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4,
3241 4.5, 4.8, 4.9 and 5-CURRENT@.
3243 The version of binutils installed in @file{/usr/bin} probably works
3244 with this release of GCC@. Bootstrapping against the latest GNU
3245 binutils and/or the version found in @file{/usr/ports/devel/binutils} has
3246 been known to enable additional features and improve overall testsuite
3247 results. However, it is currently known that boehm-gc (which itself
3248 is required for java) may not configure properly on FreeBSD prior to
3249 the FreeBSD 7.0 release with GNU binutils after 2.16.1.
3254 @heading @anchor{h8300-hms}h8300-hms
3255 Renesas H8/300 series of processors.
3257 Please have a look at the @uref{binaries.html,,binaries page}.
3259 The calling convention and structure layout has changed in release 2.6.
3260 All code must be recompiled. The calling convention now passes the
3261 first three arguments in function calls in registers. Structures are no
3262 longer a multiple of 2 bytes.
3267 @heading @anchor{hppa-hp-hpux}hppa*-hp-hpux*
3268 Support for HP-UX version 9 and older was discontinued in GCC 3.4.
3270 We require using gas/binutils on all hppa platforms. Version 2.19 or
3271 later is recommended.
3273 It may be helpful to configure GCC with the
3274 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
3275 @option{--with-as=@dots{}} options to ensure that GCC can find GAS@.
3277 The HP assembler should not be used with GCC. It is rarely tested and may
3278 not work. It shouldn't be used with any languages other than C due to its
3281 Specifically, @option{-g} does not work (HP-UX uses a peculiar debugging
3282 format which GCC does not know about). It also inserts timestamps
3283 into each object file it creates, causing the 3-stage comparison test to
3284 fail during a bootstrap. You should be able to continue by saying
3285 @samp{make all-host all-target} after getting the failure from @samp{make}.
3287 Various GCC features are not supported. For example, it does not support weak
3288 symbols or alias definitions. As a result, explicit template instantiations
3289 are required when using C++. This makes it difficult if not impossible to
3290 build many C++ applications.
3292 There are two default scheduling models for instructions. These are
3293 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
3294 architecture specified for the target machine when configuring.
3295 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
3296 the target is a @samp{hppa1*} machine.
3298 The PROCESSOR_8000 model is not well suited to older processors. Thus,
3299 it is important to completely specify the machine architecture when
3300 configuring if you want a model other than PROCESSOR_8000. The macro
3301 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
3302 default scheduling model is desired.
3304 As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
3305 through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
3306 This namespace change might cause problems when bootstrapping with
3307 an earlier version of GCC or the HP compiler as essentially the same
3308 namespace is required for an entire build. This problem can be avoided
3309 in a number of ways. With HP cc, @env{UNIX_STD} can be set to @samp{95}
3310 or @samp{98}. Another way is to add an appropriate set of predefines
3311 to @env{CC}. The description for the @option{munix=} option contains
3312 a list of the predefines used with each standard.
3314 More specific information to @samp{hppa*-hp-hpux*} targets follows.
3319 @heading @anchor{hppa-hp-hpux10}hppa*-hp-hpux10
3321 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
3322 @code{PHCO_19798} from HP@. HP has two sites which provide patches free of
3328 <a href="http://us.itrc.hp.com/service/home/home.do">US, Canada, Asia-Pacific, and
3332 @uref{http://us.itrc.hp.com/service/home/home.do,,} US, Canada, Asia-Pacific,
3336 @uref{http://europe.itrc.hp.com/service/home/home.do,,} Europe.
3339 The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are
3340 used for one-only code and data. This resolves many of the previous
3341 problems in using C++ on this target. However, the ABI is not compatible
3342 with the one implemented under HP-UX 11 using secondary definitions.
3347 @heading @anchor{hppa-hp-hpux11}hppa*-hp-hpux11
3349 GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
3350 be used to compile GCC 3.0 and up.
3352 The libffi and libjava libraries haven't been ported to 64-bit HP-UX@
3355 Refer to @uref{binaries.html,,binaries} for information about obtaining
3356 precompiled GCC binaries for HP-UX@. Precompiled binaries must be obtained
3357 to build the Ada language as it can't be bootstrapped using C@. Ada is
3358 only available for the 32-bit PA-RISC runtime.
3360 Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The
3361 bundled compiler supports only traditional C; you will need either HP's
3362 unbundled compiler, or a binary distribution of GCC@.
3364 It is possible to build GCC 3.3 starting with the bundled HP compiler,
3365 but the process requires several steps. GCC 3.3 can then be used to
3366 build later versions. The fastjar program contains ISO C code and
3367 can't be built with the HP bundled compiler. This problem can be
3368 avoided by not building the Java language. For example, use the
3369 @option{--enable-languages="c,c++,f77,objc"} option in your configure
3372 There are several possible approaches to building the distribution.
3373 Binutils can be built first using the HP tools. Then, the GCC
3374 distribution can be built. The second approach is to build GCC
3375 first using the HP tools, then build binutils, then rebuild GCC@.
3376 There have been problems with various binary distributions, so it
3377 is best not to start from a binary distribution.
3379 On 64-bit capable systems, there are two distinct targets. Different
3380 installation prefixes must be used if both are to be installed on
3381 the same system. The @samp{hppa[1-2]*-hp-hpux11*} target generates code
3382 for the 32-bit PA-RISC runtime architecture and uses the HP linker.
3383 The @samp{hppa64-hp-hpux11*} target generates 64-bit code for the
3384 PA-RISC 2.0 architecture.
3386 The script config.guess now selects the target type based on the compiler
3387 detected during configuration. You must define @env{PATH} or @env{CC} so
3388 that configure finds an appropriate compiler for the initial bootstrap.
3389 When @env{CC} is used, the definition should contain the options that are
3390 needed whenever @env{CC} is used.
3392 Specifically, options that determine the runtime architecture must be
3393 in @env{CC} to correctly select the target for the build. It is also
3394 convenient to place many other compiler options in @env{CC}. For example,
3395 @env{CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"}
3396 can be used to bootstrap the GCC 3.3 branch with the HP compiler in
3397 64-bit K&R/bundled mode. The @option{+DA2.0W} option will result in
3398 the automatic selection of the @samp{hppa64-hp-hpux11*} target. The
3399 macro definition table of cpp needs to be increased for a successful
3400 build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to
3401 be defined when building with the bundled compiler, or when using the
3402 @option{-Ac} option. These defines aren't necessary with @option{-Ae}.
3404 It is best to explicitly configure the @samp{hppa64-hp-hpux11*} target
3405 with the @option{--with-ld=@dots{}} option. This overrides the standard
3406 search for ld. The two linkers supported on this target require different
3407 commands. The default linker is determined during configuration. As a
3408 result, it's not possible to switch linkers in the middle of a GCC build.
3409 This has been reported to sometimes occur in unified builds of binutils
3412 A recent linker patch must be installed for the correct operation of
3413 GCC 3.3 and later. @code{PHSS_26559} and @code{PHSS_24304} are the
3414 oldest linker patches that are known to work. They are for HP-UX
3415 11.00 and 11.11, respectively. @code{PHSS_24303}, the companion to
3416 @code{PHSS_24304}, might be usable but it hasn't been tested. These
3417 patches have been superseded. Consult the HP patch database to obtain
3418 the currently recommended linker patch for your system.
3420 The patches are necessary for the support of weak symbols on the
3421 32-bit port, and for the running of initializers and finalizers. Weak
3422 symbols are implemented using SOM secondary definition symbols. Prior
3423 to HP-UX 11, there are bugs in the linker support for secondary symbols.
3424 The patches correct a problem of linker core dumps creating shared
3425 libraries containing secondary symbols, as well as various other
3426 linking issues involving secondary symbols.
3428 GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
3429 run initializers and finalizers on the 64-bit port. The 32-bit port
3430 uses the linker @option{+init} and @option{+fini} options for the same
3431 purpose. The patches correct various problems with the +init/+fini
3432 options, including program core dumps. Binutils 2.14 corrects a
3433 problem on the 64-bit port resulting from HP's non-standard use of
3434 the .init and .fini sections for array initializers and finalizers.
3436 Although the HP and GNU linkers are both supported for the
3437 @samp{hppa64-hp-hpux11*} target, it is strongly recommended that the
3438 HP linker be used for link editing on this target.
3440 At this time, the GNU linker does not support the creation of long
3441 branch stubs. As a result, it can't successfully link binaries
3442 containing branch offsets larger than 8 megabytes. In addition,
3443 there are problems linking shared libraries, linking executables
3444 with @option{-static}, and with dwarf2 unwind and exception support.
3445 It also doesn't provide stubs for internal calls to global functions
3446 in shared libraries, so these calls can't be overloaded.
3448 The HP dynamic loader does not support GNU symbol versioning, so symbol
3449 versioning is not supported. It may be necessary to disable symbol
3450 versioning with @option{--disable-symvers} when using GNU ld.
3452 POSIX threads are the default. The optional DCE thread library is not
3453 supported, so @option{--enable-threads=dce} does not work.
3458 @heading @anchor{x-x-linux-gnu}*-*-linux-gnu
3460 Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present
3461 in glibc 2.2.5 and later. More information is available in the
3462 libstdc++-v3 documentation.
3467 @heading @anchor{ix86-x-linux}i?86-*-linux*
3469 As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
3470 See @uref{http://gcc.gnu.org/PR10877,,bug 10877} for more information.
3472 If you receive Signal 11 errors when building on GNU/Linux, then it is
3473 possible you have a hardware problem. Further information on this can be
3474 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
3479 @heading @anchor{ix86-x-solaris210}i?86-*-solaris2.10
3480 Use this for Solaris 10 or later on x86 and x86-64 systems. This
3481 configuration is supported by GCC 4.0 and later versions only.
3483 It is recommended that you configure GCC to use the GNU assembler in
3484 @file{/usr/sfw/bin/gas} but the Sun linker, using the options
3485 @option{--with-gnu-as --with-as=/usr/sfw/bin/gas --without-gnu-ld
3486 --with-ld=/usr/ccs/bin/ld}.
3491 @heading @anchor{ia64-x-linux}ia64-*-linux
3492 IA-64 processor (also known as IPF, or Itanium Processor Family)
3495 If you are using the installed system libunwind library with
3496 @option{--with-system-libunwind}, then you must use libunwind 0.98 or
3499 None of the following versions of GCC has an ABI that is compatible
3500 with any of the other versions in this list, with the exception that
3501 Red Hat 2.96 and Trillian 000171 are compatible with each other:
3502 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
3503 This primarily affects C++ programs and programs that create shared libraries.
3504 GCC 3.1 or later is recommended for compiling linux, the kernel.
3505 As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
3506 more major ABI changes are expected.
3511 @heading @anchor{ia64-x-hpux}ia64-*-hpux*
3512 Building GCC on this target requires the GNU Assembler. The bundled HP
3513 assembler will not work. To prevent GCC from using the wrong assembler,
3514 the option @option{--with-gnu-as} may be necessary.
3516 The GCC libunwind library has not been ported to HPUX@. This means that for
3517 GCC versions 3.2.3 and earlier, @option{--enable-libunwind-exceptions}
3518 is required to build GCC@. For GCC 3.3 and later, this is the default.
3519 For gcc 3.4.3 and later, @option{--enable-libunwind-exceptions} is
3520 removed and the system libunwind library will always be used.
3524 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
3526 @heading @anchor{x-ibm-aix}*-ibm-aix*
3527 Support for AIX version 3 and older was discontinued in GCC 3.4.
3528 Support for AIX version 4.2 and older was discontinued in GCC 4.5.
3530 ``out of memory'' bootstrap failures may indicate a problem with
3531 process resource limits (ulimit). Hard limits are configured in the
3532 @file{/etc/security/limits} system configuration file.
3534 GCC can bootstrap with recent versions of IBM XLC, but bootstrapping
3535 with an earlier release of GCC is recommended. Bootstrapping with XLC
3536 requires a larger data segment, which can be enabled through the
3537 @var{LDR_CNTRL} environment variable, e.g.,
3540 % LDR_CNTRL=MAXDATA=0x50000000
3544 One can start with a pre-compiled version of GCC to build from
3545 sources. One may delete GCC's ``fixed'' header files when starting
3546 with a version of GCC built for an earlier release of AIX.
3548 To speed up the configuration phases of bootstrapping and installing GCC,
3549 one may use GNU Bash instead of AIX @command{/bin/sh}, e.g.,
3552 % CONFIG_SHELL=/opt/freeware/bin/bash
3553 % export CONFIG_SHELL
3556 and then proceed as described in @uref{build.html,,the build
3557 instructions}, where we strongly recommend specifying an absolute path
3558 to invoke @var{srcdir}/configure.
3560 Because GCC on AIX is built as a 32-bit executable by default,
3561 (although it can generate 64-bit programs) the GMP and MPFR libraries
3562 required by gfortran must be 32-bit libraries. Building GMP and MPFR
3563 as static archive libraries works better than shared libraries.
3565 Errors involving @code{alloca} when building GCC generally are due
3566 to an incorrect definition of @code{CC} in the Makefile or mixing files
3567 compiled with the native C compiler and GCC@. During the stage1 phase of
3568 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
3569 (not @command{xlc}). Once @command{configure} has been informed of
3570 @command{xlc}, one needs to use @samp{make distclean} to remove the
3571 configure cache files and ensure that @env{CC} environment variable
3572 does not provide a definition that will confuse @command{configure}.
3573 If this error occurs during stage2 or later, then the problem most likely
3574 is the version of Make (see above).
3576 The native @command{as} and @command{ld} are recommended for bootstrapping
3577 on AIX@. The GNU Assembler, GNU Linker, and GNU Binutils version 2.20
3578 is required to bootstrap on AIX 5@. The native AIX tools do
3579 interoperate with GCC@.
3581 Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
3582 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
3583 fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
3584 referenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1)
3586 @samp{libstdc++} in GCC 3.4 increments the major version number of the
3587 shared object and GCC installation places the @file{libstdc++.a}
3588 shared library in a common location which will overwrite the and GCC
3589 3.3 version of the shared library. Applications either need to be
3590 re-linked against the new shared library or the GCC 3.1 and GCC 3.3
3591 versions of the @samp{libstdc++} shared object needs to be available
3592 to the AIX runtime loader. The GCC 3.1 @samp{libstdc++.so.4}, if
3593 present, and GCC 3.3 @samp{libstdc++.so.5} shared objects can be
3594 installed for runtime dynamic loading using the following steps to set
3595 the @samp{F_LOADONLY} flag in the shared object for @emph{each}
3596 multilib @file{libstdc++.a} installed:
3598 Extract the shared objects from the currently installed
3599 @file{libstdc++.a} archive:
3601 % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
3604 Enable the @samp{F_LOADONLY} flag so that the shared object will be
3605 available for runtime dynamic loading, but not linking:
3607 % strip -e libstdc++.so.4 libstdc++.so.5
3610 Archive the runtime-only shared object in the GCC 3.4
3611 @file{libstdc++.a} archive:
3613 % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
3616 Linking executables and shared libraries may produce warnings of
3617 duplicate symbols. The assembly files generated by GCC for AIX always
3618 have included multiple symbol definitions for certain global variable
3619 and function declarations in the original program. The warnings should
3620 not prevent the linker from producing a correct library or runnable
3623 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
3624 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
3625 to parse archive libraries did not handle the new format correctly.
3626 These routines are used by GCC and result in error messages during
3627 linking such as ``not a COFF file''. The version of the routines shipped
3628 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
3629 option of the archive command may be used to create archives of 32-bit
3630 objects using the original ``small format''. A correct version of the
3631 routines is shipped with AIX 4.3.2 and above.
3633 Some versions of the AIX binder (linker) can fail with a relocation
3634 overflow severe error when the @option{-bbigtoc} option is used to link
3635 GCC-produced object files into an executable that overflows the TOC@. A fix
3636 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
3637 available from IBM Customer Support and from its
3638 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3639 website as PTF U455193.
3641 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
3642 with a segmentation fault when invoked by any version of GCC@. A fix for
3643 APAR IX87327 is available from IBM Customer Support and from its
3644 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3645 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
3647 The initial assembler shipped with AIX 4.3.0 generates incorrect object
3648 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
3649 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
3650 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3651 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
3653 AIX provides National Language Support (NLS)@. Compilers and assemblers
3654 use NLS to support locale-specific representations of various data
3655 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
3656 separating decimal fractions). There have been problems reported where
3657 GCC does not produce the same floating-point formats that the assembler
3658 expects. If one encounters this problem, set the @env{LANG}
3659 environment variable to @samp{C} or @samp{En_US}.
3661 A default can be specified with the @option{-mcpu=@var{cpu_type}}
3662 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
3667 @heading @anchor{iq2000-x-elf}iq2000-*-elf
3668 Vitesse IQ2000 processors. These are used in embedded
3669 applications. There are no standard Unix configurations.
3674 @heading @anchor{lm32-x-elf}lm32-*-elf
3675 Lattice Mico32 processor.
3676 This configuration is intended for embedded systems.
3681 @heading @anchor{lm32-x-uclinux}lm32-*-uclinux
3682 Lattice Mico32 processor.
3683 This configuration is intended for embedded systems running uClinux.
3688 @heading @anchor{m32c-x-elf}m32c-*-elf
3689 Renesas M32C processor.
3690 This configuration is intended for embedded systems.
3695 @heading @anchor{m32r-x-elf}m32r-*-elf
3696 Renesas M32R processor.
3697 This configuration is intended for embedded systems.
3702 @heading @anchor{m6811-elf}m6811-elf
3703 Motorola 68HC11 family micro controllers. These are used in embedded
3704 applications. There are no standard Unix configurations.
3709 @heading @anchor{m6812-elf}m6812-elf
3710 Motorola 68HC12 family micro controllers. These are used in embedded
3711 applications. There are no standard Unix configurations.
3716 @heading @anchor{m68k-x-x}m68k-*-*
3718 @samp{m68k-*-elf*}, @samp{m68k-*-rtems}, @samp{m68k-*-uclinux} and
3720 build libraries for both M680x0 and ColdFire processors. If you only
3721 need the M680x0 libraries, you can omit the ColdFire ones by passing
3722 @option{--with-arch=m68k} to @command{configure}. Alternatively, you
3723 can omit the M680x0 libraries by passing @option{--with-arch=cf} to
3724 @command{configure}. These targets default to 5206 or 5475 code as
3725 appropriate for the target system when
3726 configured with @option{--with-arch=cf} and 68020 code otherwise.
3728 The @samp{m68k-*-netbsd} and
3729 @samp{m68k-*-openbsd} targets also support the @option{--with-arch}
3730 option. They will generate ColdFire CFV4e code when configured with
3731 @option{--with-arch=cf} and 68020 code otherwise.
3733 You can override the default processors listed above by configuring
3734 with @option{--with-cpu=@var{target}}. This @var{target} can either
3735 be a @option{-mcpu} argument or one of the following values:
3736 @samp{m68000}, @samp{m68010}, @samp{m68020}, @samp{m68030},
3737 @samp{m68040}, @samp{m68060}, @samp{m68020-40} and @samp{m68020-60}.
3742 @heading @anchor{m68k-x-uclinux}m68k-*-uclinux
3743 GCC 4.3 changed the uClinux configuration so that it uses the
3744 @samp{m68k-linux-gnu} ABI rather than the @samp{m68k-elf} ABI.
3745 It also added improved support for C++ and flat shared libraries,
3746 both of which were ABI changes. However, you can still use the
3747 original ABI by configuring for @samp{m68k-uclinuxoldabi} or
3748 @samp{m68k-@var{vendor}-uclinuxoldabi}.
3754 @heading @anchor{mep-x-elf}mep-*-elf
3755 Toshiba Media embedded Processor.
3756 This configuration is intended for embedded systems.
3761 @heading @anchor{mips-x-x}mips-*-*
3762 If on a MIPS system you get an error message saying ``does not have gp
3763 sections for all it's [sic] sectons [sic]'', don't worry about it. This
3764 happens whenever you use GAS with the MIPS linker, but there is not
3765 really anything wrong, and it is okay to use the output file. You can
3766 stop such warnings by installing the GNU linker.
3768 It would be nice to extend GAS to produce the gp tables, but they are
3769 optional, and there should not be a warning about their absence.
3771 The libstdc++ atomic locking routines for MIPS targets requires MIPS II
3772 and later. A patch went in just after the GCC 3.3 release to
3773 make @samp{mips*-*-*} use the generic implementation instead. You can also
3774 configure for @samp{mipsel-elf} as a workaround. The
3775 @samp{mips*-*-linux*} target continues to use the MIPS II routines. More
3776 work on this is expected in future releases.
3778 @c If you make --with-llsc the default for another target, please also
3779 @c update the description of the --with-llsc option.
3781 The built-in @code{__sync_*} functions are available on MIPS II and
3782 later systems and others that support the @samp{ll}, @samp{sc} and
3783 @samp{sync} instructions. This can be overridden by passing
3784 @option{--with-llsc} or @option{--without-llsc} when configuring GCC.
3785 Since the Linux kernel emulates these instructions if they are
3786 missing, the default for @samp{mips*-*-linux*} targets is
3787 @option{--with-llsc}. The @option{--with-llsc} and
3788 @option{--without-llsc} configure options may be overridden at compile
3789 time by passing the @option{-mllsc} or @option{-mno-llsc} options to
3792 MIPS systems check for division by zero (unless
3793 @option{-mno-check-zero-division} is passed to the compiler) by
3794 generating either a conditional trap or a break instruction. Using
3795 trap results in smaller code, but is only supported on MIPS II and
3796 later. Also, some versions of the Linux kernel have a bug that
3797 prevents trap from generating the proper signal (@code{SIGFPE}). To enable
3798 the use of break, use the @option{--with-divide=breaks}
3799 @command{configure} option when configuring GCC@. The default is to
3800 use traps on systems that support them.
3802 Cross-compilers for the MIPS as target using the MIPS assembler
3803 currently do not work, because the auxiliary programs
3804 @file{mips-tdump.c} and @file{mips-tfile.c} can't be compiled on
3805 anything but a MIPS@. It does work to cross compile for a MIPS
3806 if you use the GNU assembler and linker.
3808 The assembler from GNU binutils 2.17 and earlier has a bug in the way
3809 it sorts relocations for REL targets (o32, o64, EABI). This can cause
3810 bad code to be generated for simple C++ programs. Also the linker
3811 from GNU binutils versions prior to 2.17 has a bug which causes the
3812 runtime linker stubs in very large programs, like @file{libgcj.so}, to
3813 be incorrectly generated. GNU Binutils 2.18 and later (and snapshots
3814 made after Nov. 9, 2006) should be free from both of these problems.
3819 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
3821 In order to compile GCC on an SGI running IRIX 5, the @samp{compiler_dev.hdr}
3822 subsystem must be installed from the IDO CD-ROM supplied by SGI@.
3823 It is also available for download from
3824 @uref{ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist}.
3826 If you use the MIPS C compiler to bootstrap, it may be necessary
3827 to increase its table size for switch statements with the
3828 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
3829 optimization option, you also need to use @option{-Olimit 3000}.
3831 To enable debugging under IRIX 5, you must use GNU binutils 2.15 or
3832 later, and use the @option{--with-gnu-ld} @command{configure} option
3833 when configuring GCC@. You need to use GNU @command{ar} and @command{nm},
3834 also distributed with GNU binutils.
3836 Some users have reported that @command{/bin/sh} will hang during bootstrap.
3837 This problem can be avoided by running the commands:
3840 % CONFIG_SHELL=/bin/ksh
3841 % export CONFIG_SHELL
3845 before starting the build.
3850 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
3852 If you are using SGI's MIPSpro @command{cc} as your bootstrap compiler, you must
3853 ensure that the N32 ABI is in use. To test this, compile a simple C
3854 file with @command{cc} and then run @command{file} on the
3855 resulting object file. The output should look like:
3858 test.o: ELF N32 MSB @dots{}
3865 test.o: ELF 32-bit MSB @dots{}
3872 test.o: ELF 64-bit MSB @dots{}
3876 then your version of @command{cc} uses the O32 or N64 ABI by default. You
3877 should set the environment variable @env{CC} to @samp{cc -n32}
3878 before configuring GCC@.
3880 If you want the resulting @command{gcc} to run on old 32-bit systems
3881 with the MIPS R4400 CPU, you need to ensure that only code for the @samp{mips3}
3882 instruction set architecture (ISA) is generated. While GCC 3.x does
3883 this correctly, both GCC 2.95 and SGI's MIPSpro @command{cc} may change
3884 the ISA depending on the machine where GCC is built. Using one of them
3885 as the bootstrap compiler may result in @samp{mips4} code, which won't run at
3886 all on @samp{mips3}-only systems. For the test program above, you should see:
3889 test.o: ELF N32 MSB mips-3 @dots{}
3896 test.o: ELF N32 MSB mips-4 @dots{}
3900 instead, you should set the environment variable @env{CC} to @samp{cc
3901 -n32 -mips3} or @samp{gcc -mips3} respectively before configuring GCC@.
3903 MIPSpro C 7.4 may cause bootstrap failures, due to a bug when inlining
3904 @code{memcmp}. Either add @code{-U__INLINE_INTRINSICS} to the @env{CC}
3905 environment variable as a workaround or upgrade to MIPSpro C 7.4.1m.
3907 GCC on IRIX 6 is usually built to support the N32, O32 and N64 ABIs. If
3908 you build GCC on a system that doesn't have the N64 libraries installed
3909 or cannot run 64-bit binaries,
3910 you need to configure with @option{--disable-multilib} so GCC doesn't
3911 try to use them. This will disable building the O32 libraries, too.
3912 Look for @file{/usr/lib64/libc.so.1} to see if you
3913 have the 64-bit libraries installed.
3915 To enable debugging for the O32 ABI, you must use GNU @command{as} from
3916 GNU binutils 2.15 or later. You may also use GNU @command{ld}, but
3917 this is not required and currently causes some problems with Ada.
3919 The @option{--enable-libgcj}
3920 option is disabled by default: IRIX 6 uses a very low default limit
3921 (20480) for the command line length. Although @command{libtool} contains a
3922 workaround for this problem, at least the N64 @samp{libgcj} is known not
3923 to build despite this, running into an internal error of the native
3924 @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
3925 its maximum of 262144 bytes. If you have root access, you can use the
3926 @command{systune} command to do this.
3928 @code{wchar_t} support in @samp{libstdc++} is not available for old
3929 IRIX 6.5.x releases, @math{x < 19}. The problem cannot be autodetected
3930 and in order to build GCC for such targets you need to configure with
3931 @option{--disable-wchar_t}.
3933 See @uref{http://freeware.sgi.com/} for more
3934 information about using GCC on IRIX platforms.
3939 @heading @anchor{moxie-x-elf}moxie-*-elf
3940 The moxie processor. See @uref{http://moxielogic.org/} for more
3941 information about this processor.
3946 @heading @anchor{powerpc-x-x}powerpc-*-*
3948 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
3949 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
3952 @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.15}
3953 or newer for a working GCC@.
3958 @heading @anchor{powerpc-x-darwin}powerpc-*-darwin*
3959 PowerPC running Darwin (Mac OS X kernel).
3961 Pre-installed versions of Mac OS X may not include any developer tools,
3962 meaning that you will not be able to build GCC from source. Tool
3963 binaries are available at
3964 @uref{http://developer.apple.com/darwin/projects/compiler/} (free
3965 registration required).
3967 This version of GCC requires at least cctools-590.36. The
3968 cctools-590.36 package referenced from
3969 @uref{http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html} will not work
3970 on systems older than 10.3.9 (aka darwin7.9.0).
3975 @heading @anchor{powerpc-x-elf}powerpc-*-elf
3976 PowerPC system in big endian mode, running System V.4.
3981 @heading @anchor{powerpc-x-linux-gnu}powerpc*-*-linux-gnu*
3983 PowerPC system in big endian mode running Linux.
3988 @heading @anchor{powerpc-x-netbsd}powerpc-*-netbsd*
3989 PowerPC system in big endian mode running NetBSD@.
3994 @heading @anchor{powerpc-x-eabisim}powerpc-*-eabisim
3995 Embedded PowerPC system in big endian mode for use in running under the
4001 @heading @anchor{powerpc-x-eabi}powerpc-*-eabi
4002 Embedded PowerPC system in big endian mode.
4007 @heading @anchor{powerpcle-x-elf}powerpcle-*-elf
4008 PowerPC system in little endian mode, running System V.4.
4013 @heading @anchor{powerpcle-x-eabisim}powerpcle-*-eabisim
4014 Embedded PowerPC system in little endian mode for use in running under
4020 @heading @anchor{powerpcle-x-eabi}powerpcle-*-eabi
4021 Embedded PowerPC system in little endian mode.
4026 @heading @anchor{rx-x-elf}rx-*-elf
4027 The Renesas RX processor. See
4028 @uref{http://eu.renesas.com/fmwk.jsp?cnt=rx600_series_landing.jsp&fp=/products/mpumcu/rx_family/rx600_series}
4029 for more information about this processor.
4034 @heading @anchor{s390-x-linux}s390-*-linux*
4035 S/390 system running GNU/Linux for S/390@.
4040 @heading @anchor{s390x-x-linux}s390x-*-linux*
4041 zSeries system (64-bit) running GNU/Linux for zSeries@.
4046 @heading @anchor{s390x-ibm-tpf}s390x-ibm-tpf*
4047 zSeries system (64-bit) running TPF@. This platform is
4048 supported as cross-compilation target only.
4053 @c Please use Solaris 2 to refer to all release of Solaris, starting
4054 @c with 2.0 until 2.6, 7, 8, etc. Solaris 1 was a marketing name for
4055 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
4056 @c alone is too unspecific and must be avoided.
4057 @heading @anchor{x-x-solaris2}*-*-solaris2*
4059 Sun does not ship a C compiler with Solaris 2. To bootstrap and install
4060 GCC you first have to install a pre-built compiler, see the
4061 @uref{binaries.html,,binaries page} for details.
4063 The Solaris 2 @command{/bin/sh} will often fail to configure
4064 @file{libstdc++-v3}, @file{boehm-gc} or @file{libjava}. We therefore
4065 recommend using the following initial sequence of commands
4068 % CONFIG_SHELL=/bin/ksh
4069 % export CONFIG_SHELL
4072 and proceed as described in @uref{configure.html,,the configure instructions}.
4073 In addition we strongly recommend specifying an absolute path to invoke
4074 @var{srcdir}/configure.
4076 Solaris 2 comes with a number of optional OS packages. Some of these
4077 are needed to use GCC fully, namely @code{SUNWarc},
4078 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
4079 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
4080 optional packages when installing Solaris 2, you will need to verify that
4081 the packages that GCC needs are installed.
4083 To check whether an optional package is installed, use
4084 the @command{pkginfo} command. To add an optional package, use the
4085 @command{pkgadd} command. For further details, see the Solaris 2
4088 Trying to use the linker and other tools in
4089 @file{/usr/ucb} to install GCC has been observed to cause trouble.
4090 For example, the linker may hang indefinitely. The fix is to remove
4091 @file{/usr/ucb} from your @env{PATH}.
4093 The build process works more smoothly with the legacy Sun tools so, if you
4094 have @file{/usr/xpg4/bin} in your @env{PATH}, we recommend that you place
4095 @file{/usr/bin} before @file{/usr/xpg4/bin} for the duration of the build.
4097 We recommend the use of GNU binutils 2.14 or later, or the vendor tools
4098 (Sun @command{as}, Sun @command{ld}). Note that your mileage may vary
4099 if you use a combination of the GNU tools and the Sun tools: while the
4100 combination GNU @command{as} + Sun @command{ld} should reasonably work,
4101 the reverse combination Sun @command{as} + GNU @command{ld} is known to
4102 cause memory corruption at runtime in some cases for C++ programs.
4104 The stock GNU binutils 2.15 release is broken on this platform because of a
4105 single bug. It has been fixed on the 2.15 branch in the CVS repository.
4106 You can obtain a working version by checking out the binutils-2_15-branch
4107 from the CVS repository or applying the patch
4108 @uref{http://sourceware.org/ml/binutils-cvs/2004-09/msg00036.html} to the
4111 We recommend the use of GNU binutils 2.16 or later in conjunction with GCC
4112 4.x, or the vendor tools (Sun @command{as}, Sun @command{ld}). However,
4113 for Solaris 10 and above, an additional patch is required in order for the
4114 GNU linker to be able to cope with a new flavor of shared libraries. You
4115 can obtain a working version by checking out the binutils-2_16-branch from
4116 the CVS repository or applying the patch
4117 @uref{http://sourceware.org/ml/binutils-cvs/2005-07/msg00122.html} to the
4120 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
4121 newer: @command{g++} will complain that types are missing. These headers
4122 assume that omitting the type means @code{int}; this assumption worked for
4123 C89 but is wrong for C++, and is now wrong for C99 also.
4125 @command{g++} accepts such (invalid) constructs with the option
4126 @option{-fpermissive}; it will assume that any missing type is @code{int}
4127 (as defined by C89).
4129 There are patches for Solaris 7 (108376-21 or newer for SPARC,
4130 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
4131 108653-22 for Intel) that fix this bug.
4133 Sun bug 4927647 sometimes causes random spurious testsuite failures
4134 related to missing diagnostic output. This bug doesn't affect GCC
4135 itself, rather it is a kernel bug triggered by the @command{expect}
4136 program which is used only by the GCC testsuite driver. When the bug
4137 causes the @command{expect} program to miss anticipated output, extra
4138 testsuite failures appear.
4140 There are patches for Solaris 8 (117350-12 or newer for SPARC,
4141 117351-12 or newer for Intel) and Solaris 9 (117171-11 or newer for
4142 SPARC, 117172-11 or newer for Intel) that address this problem.
4147 @heading @anchor{sparc-sun-solaris2}sparc-sun-solaris2*
4149 When GCC is configured to use binutils 2.14 or later the binaries
4150 produced are smaller than the ones produced using Sun's native tools;
4151 this difference is quite significant for binaries containing debugging
4154 Starting with Solaris 7, the operating system is capable of executing
4155 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
4156 this; the @option{-m64} option enables 64-bit code generation.
4157 However, if all you want is code tuned for the UltraSPARC CPU, you
4158 should try the @option{-mtune=ultrasparc} option instead, which produces
4159 code that, unlike full 64-bit code, can still run on non-UltraSPARC
4162 When configuring on a Solaris 7 or later system that is running a kernel
4163 that supports only 32-bit binaries, one must configure with
4164 @option{--disable-multilib}, since we will not be able to build the
4165 64-bit target libraries.
4167 GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of
4168 the GNU compiler (especially GCC 3.0.x versions), which lead to the
4169 miscompilation of the stage1 compiler and the subsequent failure of the
4170 bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary
4171 stage, i.e.@: to bootstrap that compiler with the base compiler and then
4172 use it to bootstrap the final compiler.
4174 GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7)
4175 and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap
4176 failure in form of a miscompilation of the stage1 compiler by the Sun
4177 compiler. This is Sun bug 4974440. This is fixed with patch 112760-07.
4179 GCC 3.4 changed the default debugging format from STABS to DWARF-2 for
4180 32-bit code on Solaris 7 and later. If you use the Sun assembler, this
4181 change apparently runs afoul of Sun bug 4910101 (which is referenced as
4182 an x86-only problem by Sun, probably because they do not use DWARF-2).
4183 A symptom of the problem is that you cannot compile C++ programs like
4184 @command{groff} 1.19.1 without getting messages similar to the following:
4187 ld: warning: relocation error: R_SPARC_UA32: @dots{}
4188 external symbolic relocation against non-allocatable section
4189 .debug_info cannot be processed at runtime: relocation ignored.
4192 To work around this problem, compile with @option{-gstabs+} instead of
4195 When configuring the GNU Multiple Precision Library (GMP) or the MPFR
4196 library on a Solaris 7 or later system, the canonical target triplet
4197 must be specified as the @command{build} parameter on the configure
4198 line. This triplet can be obtained by invoking ./config.guess in
4199 the toplevel source directory of GCC (and not that of GMP or MPFR).
4200 For example on a Solaris 7 system:
4203 % ./configure --build=sparc-sun-solaris2.7 --prefix=xxx
4209 @heading @anchor{sparc-sun-solaris27}sparc-sun-solaris2.7
4211 Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
4212 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
4213 and later, including all EGCS releases. Sun formerly recommended
4214 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
4215 recommend it only for people who use Sun's compilers.
4217 Here are some workarounds to this problem:
4220 Do not install Sun patch 107058-01 until after Sun releases a
4221 complete patch for bug 4210064. This is the simplest course to take,
4222 unless you must also use Sun's C compiler. Unfortunately 107058-01
4223 is preinstalled on some new Solaris 7-based hosts, so you may have to
4227 Copy the original, unpatched Solaris 7
4228 @command{/usr/ccs/bin/as} into
4229 @command{/usr/local/libexec/gcc/sparc-sun-solaris2.7/3.4/as},
4230 adjusting the latter name to fit your local conventions and software
4234 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
4235 both 107058-01 and 106950-03 installed has reported the bug with GCC
4236 and Sun's dynamic linker. This last course of action is riskiest,
4237 for two reasons. First, you must install 106950 on all hosts that
4238 run code generated by GCC; it doesn't suffice to install it only on
4239 the hosts that run GCC itself. Second, Sun says that 106950-03 is
4240 only a partial fix for bug 4210064, but Sun doesn't know whether the
4241 partial fix is adequate for GCC@. Revision -08 or later should fix
4242 the bug. The current (as of 2004-05-23) revision is -24, and is included in
4243 the Solaris 7 Recommended Patch Cluster.
4246 GCC 3.3 triggers a bug in version 5.0 Alpha 03/27/98 of the Sun assembler,
4247 which causes a bootstrap failure when linking the 64-bit shared version of
4248 libgcc. A typical error message is:
4251 ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o:
4252 symbol <unknown>: offset 0xffffffff7ec133e7 is non-aligned.
4255 This bug has been fixed in the final 5.0 version of the assembler.
4257 A similar problem was reported for version Sun WorkShop 6 99/08/18 of the
4258 Sun assembler, which causes a bootstrap failure with GCC 4.0.0:
4261 ld: fatal: relocation error: R_SPARC_DISP32:
4262 file .libs/libstdc++.lax/libsupc++convenience.a/vterminate.o:
4263 symbol <unknown>: offset 0xfccd33ad is non-aligned
4266 This bug has been fixed in more recent revisions of the assembler.
4271 @heading @anchor{sparc-x-linux}sparc-*-linux*
4273 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
4274 or newer on this platform. All earlier binutils and glibc
4275 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
4281 @heading @anchor{sparc64-x-solaris2}sparc64-*-solaris2*
4283 When configuring the GNU Multiple Precision Library (GMP) or the
4284 MPFR library, the canonical target triplet must be specified as
4285 the @command{build} parameter on the configure line. For example
4286 on a Solaris 7 system:
4289 % ./configure --build=sparc64-sun-solaris2.7 --prefix=xxx
4292 The following compiler flags must be specified in the configure
4293 step in order to bootstrap this target with the Sun compiler:
4296 % CC="cc -xarch=v9 -xildoff" @var{srcdir}/configure [@var{options}] [@var{target}]
4299 @option{-xarch=v9} specifies the SPARC-V9 architecture to the Sun toolchain
4300 and @option{-xildoff} turns off the incremental linker.
4305 @heading @anchor{sparcv9-x-solaris2}sparcv9-*-solaris2*
4307 This is a synonym for sparc64-*-solaris2*.
4312 @heading @anchor{x-x-vxworks}*-*-vxworks*
4313 Support for VxWorks is in flux. At present GCC supports @emph{only} the
4314 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC@.
4315 We welcome patches for other architectures supported by VxWorks 5.5.
4316 Support for VxWorks AE would also be welcome; we believe this is merely
4317 a matter of writing an appropriate ``configlette'' (see below). We are
4318 not interested in supporting older, a.out or COFF-based, versions of
4321 VxWorks comes with an older version of GCC installed in
4322 @file{@var{$WIND_BASE}/host}; we recommend you do not overwrite it.
4323 Choose an installation @var{prefix} entirely outside @var{$WIND_BASE}.
4324 Before running @command{configure}, create the directories @file{@var{prefix}}
4325 and @file{@var{prefix}/bin}. Link or copy the appropriate assembler,
4326 linker, etc.@: into @file{@var{prefix}/bin}, and set your @var{PATH} to
4327 include that directory while running both @command{configure} and
4330 You must give @command{configure} the
4331 @option{--with-headers=@var{$WIND_BASE}/target/h} switch so that it can
4332 find the VxWorks system headers. Since VxWorks is a cross compilation
4333 target only, you must also specify @option{--target=@var{target}}.
4334 @command{configure} will attempt to create the directory
4335 @file{@var{prefix}/@var{target}/sys-include} and copy files into it;
4336 make sure the user running @command{configure} has sufficient privilege
4339 GCC's exception handling runtime requires a special ``configlette''
4340 module, @file{contrib/gthr_supp_vxw_5x.c}. Follow the instructions in
4341 that file to add the module to your kernel build. (Future versions of
4342 VxWorks will incorporate this module.)
4347 @heading @anchor{x86-64-x-x}x86_64-*-*, amd64-*-*
4349 GCC supports the x86-64 architecture implemented by the AMD64 processor
4350 (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD@.
4351 On GNU/Linux the default is a bi-arch compiler which is able to generate
4352 both 64-bit x86-64 and 32-bit x86 code (via the @option{-m32} switch).
4357 @heading @anchor{xtensa-x-elf}xtensa*-*-elf
4359 This target is intended for embedded Xtensa systems using the
4360 @samp{newlib} C library. It uses ELF but does not support shared
4361 objects. Designed-defined instructions specified via the
4362 Tensilica Instruction Extension (TIE) language are only supported
4363 through inline assembly.
4365 The Xtensa configuration information must be specified prior to
4366 building GCC@. The @file{include/xtensa-config.h} header
4367 file contains the configuration information. If you created your
4368 own Xtensa configuration with the Xtensa Processor Generator, the
4369 downloaded files include a customized copy of this header file,
4370 which you can use to replace the default header file.
4375 @heading @anchor{xtensa-x-linux}xtensa*-*-linux*
4377 This target is for Xtensa systems running GNU/Linux. It supports ELF
4378 shared objects and the GNU C library (glibc). It also generates
4379 position-independent code (PIC) regardless of whether the
4380 @option{-fpic} or @option{-fPIC} options are used. In other
4381 respects, this target is the same as the
4382 @uref{#xtensa*-*-elf,,@samp{xtensa*-*-elf}} target.
4387 @heading @anchor{windows}Microsoft Windows
4389 @subheading Intel 16-bit versions
4390 The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not
4393 However, the 32-bit port has limited support for Microsoft
4394 Windows 3.11 in the Win32s environment, as a target only. See below.
4396 @subheading Intel 32-bit versions
4398 The 32-bit versions of Windows, including Windows 95, Windows NT, Windows
4399 XP, and Windows Vista, are supported by several different target
4400 platforms. These targets differ in which Windows subsystem they target
4401 and which C libraries are used.
4404 @item Cygwin @uref{#x-x-cygwin,,*-*-cygwin}: Cygwin provides a user-space
4405 Linux API emulation layer in the Win32 subsystem.
4406 @item Interix @uref{#x-x-interix,,*-*-interix}: The Interix subsystem
4407 provides native support for POSIX.
4408 @item MinGW @uref{#x-x-mingw32,,*-*-mingw32}: MinGW is a native GCC port for
4409 the Win32 subsystem that provides a subset of POSIX.
4410 @item MKS i386-pc-mks: NuTCracker from MKS. See
4411 @uref{http://www.mkssoftware.com/} for more information.
4414 @subheading Intel 64-bit versions
4416 GCC contains support for x86-64 using the mingw-w64
4417 runtime library, available from @uref{http://mingw-w64.sourceforge.net/}.
4418 This library should be used with the target triple x86_64-pc-mingw32.
4420 Presently Windows for Itanium is not supported.
4422 @subheading Windows CE
4424 Windows CE is supported as a target only on ARM (arm-wince-pe), Hitachi
4425 SuperH (sh-wince-pe), and MIPS (mips-wince-pe).
4427 @subheading Other Windows Platforms
4429 GCC no longer supports Windows NT on the Alpha or PowerPC.
4431 GCC no longer supports the Windows POSIX subsystem. However, it does
4432 support the Interix subsystem. See above.
4434 Old target names including *-*-winnt and *-*-windowsnt are no longer used.
4436 PW32 (i386-pc-pw32) support was never completed, and the project seems to
4437 be inactive. See @uref{http://pw32.sourceforge.net/} for more information.
4439 UWIN support has been removed due to a lack of maintenance.
4444 @heading @anchor{x-x-cygwin}*-*-cygwin
4446 Ports of GCC are included with the
4447 @uref{http://www.cygwin.com/,,Cygwin environment}.
4449 GCC will build under Cygwin without modification; it does not build
4450 with Microsoft's C++ compiler and there are no plans to make it do so.
4452 Cygwin can be compiled with i?86-pc-cygwin.
4457 @heading @anchor{x-x-interix}*-*-interix
4459 The Interix target is used by OpenNT, Interix, Services For UNIX (SFU),
4460 and Subsystem for UNIX-based Applications (SUA). Applications compiled
4461 with this target run in the Interix subsystem, which is separate from
4462 the Win32 subsystem. This target was last known to work in GCC 3.3.
4464 For more information, see @uref{http://www.interix.com/}.
4469 @heading @anchor{x-x-mingw32}*-*-mingw32
4471 GCC will build with and support only MinGW runtime 3.12 and later.
4472 Earlier versions of headers are incompatible with the new default semantics
4473 of @code{extern inline} in @code{-std=c99} and @code{-std=gnu99} modes.
4478 @heading @anchor{older}Older systems
4480 GCC contains support files for many older (1980s and early
4481 1990s) Unix variants. For the most part, support for these systems
4482 has not been deliberately removed, but it has not been maintained for
4483 several years and may suffer from bitrot.
4485 Starting with GCC 3.1, each release has a list of ``obsoleted'' systems.
4486 Support for these systems is still present in that release, but
4487 @command{configure} will fail unless the @option{--enable-obsolete}
4488 option is given. Unless a maintainer steps forward, support for these
4489 systems will be removed from the next release of GCC@.
4491 Support for old systems as hosts for GCC can cause problems if the
4492 workarounds for compiler, library and operating system bugs affect the
4493 cleanliness or maintainability of the rest of GCC@. In some cases, to
4494 bring GCC up on such a system, if still possible with current GCC, may
4495 require first installing an old version of GCC which did work on that
4496 system, and using it to compile a more recent GCC, to avoid bugs in the
4497 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
4498 @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror
4499 sites}. Header bugs may generally be avoided using
4500 @command{fixincludes}, but bugs or deficiencies in libraries and the
4501 operating system may still cause problems.
4503 Support for older systems as targets for cross-compilation is less
4504 problematic than support for them as hosts for GCC; if an enthusiast
4505 wishes to make such a target work again (including resurrecting any of
4506 the targets that never worked with GCC 2, starting from the last
4507 version before they were removed), patches
4508 @uref{../contribute.html,,following the usual requirements} would be
4509 likely to be accepted, since they should not affect the support for more
4512 For some systems, old versions of GNU binutils may also be useful,
4513 and are available from @file{pub/binutils/old-releases} on
4514 @uref{http://sourceware.org/mirrors.html,,sourceware.org mirror sites}.
4516 Some of the information on specific systems above relates to
4517 such older systems, but much of the information
4518 about GCC on such systems (which may no longer be applicable to
4519 current GCC) is to be found in the GCC texinfo manual.
4524 @heading @anchor{elf}all ELF targets (SVR4, Solaris 2, etc.)
4526 C++ support is significantly better on ELF targets if you use the
4527 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
4528 inlines, vtables and template instantiations will be discarded
4537 @uref{./index.html,,Return to the GCC Installation page}
4541 @c ***Old documentation******************************************************
4543 @include install-old.texi
4549 @uref{./index.html,,Return to the GCC Installation page}
4553 @c ***GFDL********************************************************************
4561 @uref{./index.html,,Return to the GCC Installation page}
4565 @c ***************************************************************************
4566 @c Part 6 The End of the Document
4568 @comment node-name, next, previous, up
4569 @node Concept Index, , GNU Free Documentation License, Top
4573 @unnumbered Concept Index