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.6.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
361 @heading Tools/packages necessary for modifying GCC
363 @item autoconf version 2.59
364 @itemx GNU m4 version 1.4 (or later)
366 Necessary when modifying @file{configure.ac}, @file{aclocal.m4}, etc.@:
367 to regenerate @file{configure} and @file{config.in} files.
369 @item automake version 1.9.6
371 Necessary when modifying a @file{Makefile.am} file to regenerate its
372 associated @file{Makefile.in}.
374 Much of GCC does not use automake, so directly edit the @file{Makefile.in}
375 file. Specifically this applies to the @file{gcc}, @file{intl},
376 @file{libcpp}, @file{libiberty}, @file{libobjc} directories as well
377 as any of their subdirectories.
379 For directories that use automake, GCC requires the latest release in
380 the 1.9.x series, which is currently 1.9.6. When regenerating a directory
381 to a newer version, please update all the directories using an older 1.9.x
382 to the latest released version.
384 @item gettext version 0.14.5 (or later)
386 Needed to regenerate @file{gcc.pot}.
388 @item gperf version 2.7.2 (or later)
390 Necessary when modifying @command{gperf} input files, e.g.@:
391 @file{gcc/cp/cfns.gperf} to regenerate its associated header file, e.g.@:
392 @file{gcc/cp/cfns.h}.
398 Necessary to run the GCC testsuite; see the section on testing for details.
400 @item autogen version 5.5.4 (or later) and
401 @itemx guile version 1.4.1 (or later)
403 Necessary to regenerate @file{fixinc/fixincl.x} from
404 @file{fixinc/inclhack.def} and @file{fixinc/*.tpl}.
406 Necessary to run @samp{make check} for @file{fixinc}.
408 Necessary to regenerate the top level @file{Makefile.in} file from
409 @file{Makefile.tpl} and @file{Makefile.def}.
411 @item Flex version 2.5.4 (or later)
413 Necessary when modifying @file{*.l} files.
415 Necessary to build GCC during development because the generated output
416 files are not included in the SVN repository. They are included in
419 @item Texinfo version 4.7 (or later)
421 Necessary for running @command{makeinfo} when modifying @file{*.texi}
422 files to test your changes.
424 Necessary for running @command{make dvi} or @command{make pdf} to
425 create printable documentation in DVI or PDF format. Texinfo version
426 4.8 or later is required for @command{make pdf}.
428 Necessary to build GCC documentation during development because the
429 generated output files are not included in the SVN repository. They are
430 included in releases.
432 @item @TeX{} (any working version)
434 Necessary for running @command{texi2dvi} and @command{texi2pdf}, which
435 are used when running @command{make dvi} or @command{make pdf} to create
436 DVI or PDF files, respectively.
438 @item SVN (any version)
439 @itemx SSH (any version)
441 Necessary to access the SVN repository. Public releases and weekly
442 snapshots of the development sources are also available via FTP@.
444 @item Perl version 5.6.1 (or later)
446 Necessary when regenerating @file{Makefile} dependencies in libiberty.
447 Necessary when regenerating @file{libiberty/functions.texi}.
448 Necessary when generating manpages from Texinfo manuals.
449 Necessary when targetting Darwin, building libstdc++,
450 and not using @option{--disable-symvers}.
451 Used by various scripts to generate some files included in SVN (mainly
452 Unicode-related and rarely changing) from source tables.
454 @item GNU diffutils version 2.7 (or later)
456 Useful when submitting patches for the GCC source code.
458 @item patch version 2.5.4 (or later)
460 Necessary when applying patches, created with @command{diff}, to one's
466 If you wish to modify @file{.java} files in libjava, you will need to
467 configure with @option{--enable-java-maintainer-mode}, and you will need
468 to have executables named @command{ecj1} and @command{gjavah} in your path.
469 The @command{ecj1} executable should run the Eclipse Java compiler via
470 the GCC-specific entry point. You can download a suitable jar from
471 @uref{ftp://sourceware.org/pub/java/}, or by running the script
472 @command{contrib/download_ecj}.
474 @item antlr.jar version 2.7.1 (or later)
477 If you wish to build the @command{gjdoc} binary in libjava, you will
478 need to have an @file{antlr.jar} library available. The library is
479 searched in system locations but can be configured with
480 @option{--with-antlr-jar=} instead. When configuring with
481 @option{--enable-java-maintainer-mode}, you will need to have one of
482 the executables named @command{cantlr}, @command{runantlr} or
483 @command{antlr} in your path.
492 @uref{./index.html,,Return to the GCC Installation page}
496 @c ***Downloading the source**************************************************
498 @comment node-name, next, previous, up
499 @node Downloading the source, Configuration, Prerequisites, Installing GCC
503 @chapter Downloading GCC
505 @cindex Downloading GCC
506 @cindex Downloading the Source
508 GCC is distributed via @uref{http://gcc.gnu.org/svn.html,,SVN} and FTP
509 tarballs compressed with @command{gzip} or
510 @command{bzip2}. It is possible to download a full distribution or specific
513 Please refer to the @uref{http://gcc.gnu.org/releases.html,,releases web page}
514 for information on how to obtain GCC@.
516 The full distribution includes the C, C++, Objective-C, Fortran, Java,
517 and Ada (in the case of GCC 3.1 and later) compilers. The full
518 distribution also includes runtime libraries for C++, Objective-C,
519 Fortran, and Java. In GCC 3.0 and later versions, the GNU compiler
520 testsuites are also included in the full distribution.
522 If you choose to download specific components, you must download the core
523 GCC distribution plus any language specific distributions you wish to
524 use. The core distribution includes the C language front end as well as the
525 shared components. Each language has a tarball which includes the language
526 front end as well as the language runtime (when appropriate).
528 Unpack the core distribution as well as any language specific
529 distributions in the same directory.
531 If you also intend to build binutils (either to upgrade an existing
532 installation or for use in place of the corresponding tools of your
533 OS), unpack the binutils distribution either in the same directory or
534 a separate one. In the latter case, add symbolic links to any
535 components of the binutils you intend to build alongside the compiler
536 (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
537 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
539 Likewise the GMP, MPFR and MPC libraries can be automatically built
540 together with GCC. Unpack the GMP, MPFR and/or MPC source
541 distributions in the directory containing the GCC sources and rename
542 their directories to @file{gmp}, @file{mpfr} and @file{mpc},
543 respectively (or use symbolic links with the same name).
550 @uref{./index.html,,Return to the GCC Installation page}
554 @c ***Configuration***********************************************************
556 @comment node-name, next, previous, up
557 @node Configuration, Building, Downloading the source, Installing GCC
561 @chapter Installing GCC: Configuration
563 @cindex Configuration
564 @cindex Installing GCC: Configuration
566 Like most GNU software, GCC must be configured before it can be built.
567 This document describes the recommended configuration procedure
568 for both native and cross targets.
570 We use @var{srcdir} to refer to the toplevel source directory for
571 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
573 If you obtained the sources via SVN, @var{srcdir} must refer to the top
574 @file{gcc} directory, the one where the @file{MAINTAINERS} can be found,
575 and not its @file{gcc} subdirectory, otherwise the build will fail.
577 If either @var{srcdir} or @var{objdir} is located on an automounted NFS
578 file system, the shell's built-in @command{pwd} command will return
579 temporary pathnames. Using these can lead to various sorts of build
580 problems. To avoid this issue, set the @env{PWDCMD} environment
581 variable to an automounter-aware @command{pwd} command, e.g.,
582 @command{pawd} or @samp{amq -w}, during the configuration and build
585 First, we @strong{highly} recommend that GCC be built into a
586 separate directory than the sources which does @strong{not} reside
587 within the source tree. This is how we generally build GCC; building
588 where @var{srcdir} == @var{objdir} should still work, but doesn't
589 get extensive testing; building where @var{objdir} is a subdirectory
590 of @var{srcdir} is unsupported.
592 If you have previously built GCC in the same directory for a
593 different target machine, do @samp{make distclean} to delete all files
594 that might be invalid. One of the files this deletes is @file{Makefile};
595 if @samp{make distclean} complains that @file{Makefile} does not exist
596 or issues a message like ``don't know how to make distclean'' it probably
597 means that the directory is already suitably clean. However, with the
598 recommended method of building in a separate @var{objdir}, you should
599 simply use a different @var{objdir} for each target.
601 Second, when configuring a native system, either @command{cc} or
602 @command{gcc} must be in your path or you must set @env{CC} in
603 your environment before running configure. Otherwise the configuration
607 Note that the bootstrap compiler and the resulting GCC must be link
608 compatible, else the bootstrap will fail with linker errors about
609 incompatible object file formats. Several multilibed targets are
610 affected by this requirement, see
612 @ref{Specific, host/target specific installation notes}.
615 @uref{specific.html,,host/target specific installation notes}.
624 % @var{srcdir}/configure [@var{options}] [@var{target}]
627 @heading Distributor options
629 If you will be distributing binary versions of GCC, with modifications
630 to the source code, you should use the options described in this
631 section to make clear that your version contains modifications.
634 @item --with-pkgversion=@var{version}
635 Specify a string that identifies your package. You may wish
636 to include a build number or build date. This version string will be
637 included in the output of @command{gcc --version}. This suffix does
638 not replace the default version string, only the @samp{GCC} part.
640 The default value is @samp{GCC}.
642 @item --with-bugurl=@var{url}
643 Specify the URL that users should visit if they wish to report a bug.
644 You are of course welcome to forward bugs reported to you to the FSF,
645 if you determine that they are not bugs in your modifications.
647 The default value refers to the FSF's GCC bug tracker.
651 @heading Target specification
654 GCC has code to correctly determine the correct value for @var{target}
655 for nearly all native systems. Therefore, we highly recommend you not
656 provide a configure target when configuring a native compiler.
659 @var{target} must be specified as @option{--target=@var{target}}
660 when configuring a cross compiler; examples of valid targets would be
661 m68k-elf, sh-elf, etc.
664 Specifying just @var{target} instead of @option{--target=@var{target}}
665 implies that the host defaults to @var{target}.
669 @heading Options specification
671 Use @var{options} to override several configure time options for
672 GCC@. A list of supported @var{options} follows; @samp{configure
673 --help} may list other options, but those not listed below may not
674 work and should not normally be used.
676 Note that each @option{--enable} option has a corresponding
677 @option{--disable} option and that each @option{--with} option has a
678 corresponding @option{--without} option.
681 @item --prefix=@var{dirname}
682 Specify the toplevel installation
683 directory. This is the recommended way to install the tools into a directory
684 other than the default. The toplevel installation directory defaults to
687 We @strong{highly} recommend against @var{dirname} being the same or a
688 subdirectory of @var{objdir} or vice versa. If specifying a directory
689 beneath a user's home directory tree, some shells will not expand
690 @var{dirname} correctly if it contains the @samp{~} metacharacter; use
693 The following standard @command{autoconf} options are supported. Normally you
694 should not need to use these options.
696 @item --exec-prefix=@var{dirname}
697 Specify the toplevel installation directory for architecture-dependent
698 files. The default is @file{@var{prefix}}.
700 @item --bindir=@var{dirname}
701 Specify the installation directory for the executables called by users
702 (such as @command{gcc} and @command{g++}). The default is
703 @file{@var{exec-prefix}/bin}.
705 @item --libdir=@var{dirname}
706 Specify the installation directory for object code libraries and
707 internal data files of GCC@. The default is @file{@var{exec-prefix}/lib}.
709 @item --libexecdir=@var{dirname}
710 Specify the installation directory for internal executables of GCC@.
711 The default is @file{@var{exec-prefix}/libexec}.
713 @item --with-slibdir=@var{dirname}
714 Specify the installation directory for the shared libgcc library. The
715 default is @file{@var{libdir}}.
717 @item --infodir=@var{dirname}
718 Specify the installation directory for documentation in info format.
719 The default is @file{@var{prefix}/info}.
721 @item --datadir=@var{dirname}
722 Specify the installation directory for some architecture-independent
723 data files referenced by GCC@. The default is @file{@var{prefix}/share}.
725 @item --mandir=@var{dirname}
726 Specify the installation directory for manual pages. The default is
727 @file{@var{prefix}/man}. (Note that the manual pages are only extracts from
728 the full GCC manuals, which are provided in Texinfo format. The manpages
729 are derived by an automatic conversion process from parts of the full
732 @item --with-gxx-include-dir=@var{dirname}
734 the installation directory for G++ header files. The default depends
735 on other configuration options, and differs between cross and native
740 @item --program-prefix=@var{prefix}
741 GCC supports some transformations of the names of its programs when
742 installing them. This option prepends @var{prefix} to the names of
743 programs to install in @var{bindir} (see above). For example, specifying
744 @option{--program-prefix=foo-} would result in @samp{gcc}
745 being installed as @file{/usr/local/bin/foo-gcc}.
747 @item --program-suffix=@var{suffix}
748 Appends @var{suffix} to the names of programs to install in @var{bindir}
749 (see above). For example, specifying @option{--program-suffix=-3.1}
750 would result in @samp{gcc} being installed as
751 @file{/usr/local/bin/gcc-3.1}.
753 @item --program-transform-name=@var{pattern}
754 Applies the @samp{sed} script @var{pattern} to be applied to the names
755 of programs to install in @var{bindir} (see above). @var{pattern} has to
756 consist of one or more basic @samp{sed} editing commands, separated by
757 semicolons. For example, if you want the @samp{gcc} program name to be
758 transformed to the installed program @file{/usr/local/bin/myowngcc} and
759 the @samp{g++} program name to be transformed to
760 @file{/usr/local/bin/gspecial++} without changing other program names,
761 you could use the pattern
762 @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}
763 to achieve this effect.
765 All three options can be combined and used together, resulting in more
766 complex conversion patterns. As a basic rule, @var{prefix} (and
767 @var{suffix}) are prepended (appended) before further transformations
768 can happen with a special transformation script @var{pattern}.
770 As currently implemented, this option only takes effect for native
771 builds; cross compiler binaries' names are not transformed even when a
772 transformation is explicitly asked for by one of these options.
774 For native builds, some of the installed programs are also installed
775 with the target alias in front of their name, as in
776 @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
777 before the target alias is prepended to the name---so, specifying
778 @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
779 resulting binary would be installed as
780 @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.
782 As a last shortcoming, none of the installed Ada programs are
783 transformed yet, which will be fixed in some time.
785 @item --with-local-prefix=@var{dirname}
787 installation directory for local include files. The default is
788 @file{/usr/local}. Specify this option if you want the compiler to
789 search directory @file{@var{dirname}/include} for locally installed
790 header files @emph{instead} of @file{/usr/local/include}.
792 You should specify @option{--with-local-prefix} @strong{only} if your
793 site has a different convention (not @file{/usr/local}) for where to put
796 The default value for @option{--with-local-prefix} is @file{/usr/local}
797 regardless of the value of @option{--prefix}. Specifying
798 @option{--prefix} has no effect on which directory GCC searches for
799 local header files. This may seem counterintuitive, but actually it is
802 The purpose of @option{--prefix} is to specify where to @emph{install
803 GCC}. The local header files in @file{/usr/local/include}---if you put
804 any in that directory---are not part of GCC@. They are part of other
805 programs---perhaps many others. (GCC installs its own header files in
806 another directory which is based on the @option{--prefix} value.)
808 Both the local-prefix include directory and the GCC-prefix include
809 directory are part of GCC's ``system include'' directories. Although these
810 two directories are not fixed, they need to be searched in the proper
811 order for the correct processing of the include_next directive. The
812 local-prefix include directory is searched before the GCC-prefix
813 include directory. Another characteristic of system include directories
814 is that pedantic warnings are turned off for headers in these directories.
816 Some autoconf macros add @option{-I @var{directory}} options to the
817 compiler command line, to ensure that directories containing installed
818 packages' headers are searched. When @var{directory} is one of GCC's
819 system include directories, GCC will ignore the option so that system
820 directories continue to be processed in the correct order. This
821 may result in a search order different from what was specified but the
822 directory will still be searched.
824 GCC automatically searches for ordinary libraries using
825 @env{GCC_EXEC_PREFIX}. Thus, when the same installation prefix is
826 used for both GCC and packages, GCC will automatically search for
827 both headers and libraries. This provides a configuration that is
828 easy to use. GCC behaves in a manner similar to that when it is
829 installed as a system compiler in @file{/usr}.
831 Sites that need to install multiple versions of GCC may not want to
832 use the above simple configuration. It is possible to use the
833 @option{--program-prefix}, @option{--program-suffix} and
834 @option{--program-transform-name} options to install multiple versions
835 into a single directory, but it may be simpler to use different prefixes
836 and the @option{--with-local-prefix} option to specify the location of the
837 site-specific files for each version. It will then be necessary for
838 users to specify explicitly the location of local site libraries
839 (e.g., with @env{LIBRARY_PATH}).
841 The same value can be used for both @option{--with-local-prefix} and
842 @option{--prefix} provided it is not @file{/usr}. This can be used
843 to avoid the default search of @file{/usr/local/include}.
845 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
846 The directory you use for @option{--with-local-prefix} @strong{must not}
847 contain any of the system's standard header files. If it did contain
848 them, certain programs would be miscompiled (including GNU Emacs, on
849 certain targets), because this would override and nullify the header
850 file corrections made by the @command{fixincludes} script.
852 Indications are that people who use this option use it based on mistaken
853 ideas of what it is for. People use it as if it specified where to
854 install part of GCC@. Perhaps they make this assumption because
855 installing GCC creates the directory.
857 @item --enable-shared[=@var{package}[,@dots{}]]
858 Build shared versions of libraries, if shared libraries are supported on
859 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
860 are enabled by default on all platforms that support shared libraries.
862 If a list of packages is given as an argument, build shared libraries
863 only for the listed packages. For other packages, only static libraries
864 will be built. Package names currently recognized in the GCC tree are
865 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
866 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc},
867 @samp{ada}, @samp{libada}, @samp{libjava} and @samp{libobjc}.
868 Note @samp{libiberty} does not support shared libraries at all.
870 Use @option{--disable-shared} to build only static libraries. Note that
871 @option{--disable-shared} does not accept a list of package names as
872 argument, only @option{--enable-shared} does.
874 @item @anchor{with-gnu-as}--with-gnu-as
875 Specify that the compiler should assume that the
876 assembler it finds is the GNU assembler. However, this does not modify
877 the rules to find an assembler and will result in confusion if the
878 assembler found is not actually the GNU assembler. (Confusion may also
879 result if the compiler finds the GNU assembler but has not been
880 configured with @option{--with-gnu-as}.) If you have more than one
881 assembler installed on your system, you may want to use this option in
882 connection with @option{--with-as=@var{pathname}} or
883 @option{--with-build-time-tools=@var{pathname}}.
885 The following systems are the only ones where it makes a difference
886 whether you use the GNU assembler. On any other system,
887 @option{--with-gnu-as} has no effect.
890 @item @samp{hppa1.0-@var{any}-@var{any}}
891 @item @samp{hppa1.1-@var{any}-@var{any}}
892 @item @samp{sparc-sun-solaris2.@var{any}}
893 @item @samp{sparc64-@var{any}-solaris2.@var{any}}
896 @item @anchor{with-as}--with-as=@var{pathname}
897 Specify that the compiler should use the assembler pointed to by
898 @var{pathname}, rather than the one found by the standard rules to find
899 an assembler, which are:
902 Unless GCC is being built with a cross compiler, check the
903 @file{@var{libexec}/gcc/@var{target}/@var{version}} directory.
904 @var{libexec} defaults to @file{@var{exec-prefix}/libexec};
905 @var{exec-prefix} defaults to @var{prefix}, which
906 defaults to @file{/usr/local} unless overridden by the
907 @option{--prefix=@var{pathname}} switch described above. @var{target}
908 is the target system triple, such as @samp{sparc-sun-solaris2.7}, and
909 @var{version} denotes the GCC version, such as 3.0.
912 If the target system is the same that you are building on, check
913 operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
917 Check in the @env{PATH} for a tool whose name is prefixed by the
918 target system triple.
921 Check in the @env{PATH} for a tool whose name is not prefixed by the
922 target system triple, if the host and target system triple are
923 the same (in other words, we use a host tool if it can be used for
927 You may want to use @option{--with-as} if no assembler
928 is installed in the directories listed above, or if you have multiple
929 assemblers installed and want to choose one that is not found by the
932 @item @anchor{with-gnu-ld}--with-gnu-ld
933 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
936 @item --with-ld=@var{pathname}
937 Same as @uref{#with-as,,@option{--with-as}}
941 Specify that stabs debugging
942 information should be used instead of whatever format the host normally
943 uses. Normally GCC uses the same debug format as the host system.
945 On MIPS based systems and on Alphas, you must specify whether you want
946 GCC to create the normal ECOFF debugging format, or to use BSD-style
947 stabs passed through the ECOFF symbol table. The normal ECOFF debug
948 format cannot fully handle languages other than C@. BSD stabs format can
949 handle other languages, but it only works with the GNU debugger GDB@.
951 Normally, GCC uses the ECOFF debugging format by default; if you
952 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
954 No matter which default you choose when you configure GCC, the user
955 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
956 the debug format for a particular compilation.
958 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
959 @option{--with-gas} is used. It selects use of stabs debugging
960 information embedded in COFF output. This kind of debugging information
961 supports C++ well; ordinary COFF debugging information does not.
963 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
964 selects use of stabs debugging information embedded in ELF output. The
965 C++ compiler currently (2.6.0) does not support the DWARF debugging
966 information normally used on 386 SVR4 platforms; stabs provide a
967 workable alternative. This requires gas and gdb, as the normal SVR4
968 tools can not generate or interpret stabs.
970 @item --disable-multilib
971 Specify that multiple target
972 libraries to support different target variants, calling
973 conventions, etc.@: should not be built. The default is to build a
974 predefined set of them.
976 Some targets provide finer-grained control over which multilibs are built
977 (e.g., @option{--disable-softfloat}):
983 fpu, 26bit, underscore, interwork, biendian, nofmult.
986 softfloat, m68881, m68000, m68020.
989 single-float, biendian, softfloat.
991 @item powerpc*-*-*, rs6000*-*-*
992 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
997 @item --with-multilib-list=@var{list}
998 @itemx --without-multilib-list
999 Specify what multilibs to build.
1000 Currently only implemented for sh*-*-*.
1002 @var{list} is a comma separated list of CPU names. These must be of the
1003 form @code{sh*} or @code{m*} (in which case they match the compiler option
1004 for that processor). The list should not contain any endian options -
1005 these are handled by @option{--with-endian}.
1007 If @var{list} is empty, then there will be no multilibs for extra
1008 processors. The multilib for the secondary endian remains enabled.
1010 As a special case, if an entry in the list starts with a @code{!}
1011 (exclamation point), then it is added to the list of excluded multilibs.
1012 Entries of this sort should be compatible with @samp{MULTILIB_EXCLUDES}
1013 (once the leading @code{!} has been stripped).
1015 If @option{--with-multilib-list} is not given, then a default set of
1016 multilibs is selected based on the value of @option{--target}. This is
1017 usually the complete set of libraries, but some targets imply a more
1020 Example 1: to configure a compiler for SH4A only, but supporting both
1021 endians, with little endian being the default:
1023 --with-cpu=sh4a --with-endian=little,big --with-multilib-list=
1026 Example 2: to configure a compiler for both SH4A and SH4AL-DSP, but with
1027 only little endian SH4AL:
1029 --with-cpu=sh4a --with-endian=little,big --with-multilib-list=sh4al,!mb/m4al
1032 @item --with-endian=@var{endians}
1033 Specify what endians to use.
1034 Currently only implemented for sh*-*-*.
1036 @var{endians} may be one of the following:
1039 Use big endian exclusively.
1041 Use little endian exclusively.
1043 Use big endian by default. Provide a multilib for little endian.
1045 Use little endian by default. Provide a multilib for big endian.
1048 @item --enable-threads
1049 Specify that the target
1050 supports threads. This affects the Objective-C compiler and runtime
1051 library, and exception handling for other languages like C++ and Java.
1052 On some systems, this is the default.
1054 In general, the best (and, in many cases, the only known) threading
1055 model available will be configured for use. Beware that on some
1056 systems, GCC has not been taught what threading models are generally
1057 available for the system. In this case, @option{--enable-threads} is an
1058 alias for @option{--enable-threads=single}.
1060 @item --disable-threads
1061 Specify that threading support should be disabled for the system.
1062 This is an alias for @option{--enable-threads=single}.
1064 @item --enable-threads=@var{lib}
1066 @var{lib} is the thread support library. This affects the Objective-C
1067 compiler and runtime library, and exception handling for other languages
1068 like C++ and Java. The possibilities for @var{lib} are:
1076 Ada tasking support. For non-Ada programs, this setting is equivalent
1077 to @samp{single}. When used in conjunction with the Ada run time, it
1078 causes GCC to use the same thread primitives as Ada uses. This option
1079 is necessary when using both Ada and the back end exception handling,
1080 which is the default for most Ada targets.
1082 Generic MACH thread support, known to work on NeXTSTEP@. (Please note
1083 that the file needed to support this configuration, @file{gthr-mach.h}, is
1084 missing and thus this setting will cause a known bootstrap failure.)
1086 This is an alias for @samp{single}.
1088 Generic POSIX/Unix98 thread support.
1090 Generic POSIX/Unix95 thread support.
1092 RTEMS thread support.
1094 Disable thread support, should work for all platforms.
1096 Sun Solaris 2 thread support.
1098 VxWorks thread support.
1100 Microsoft Win32 API thread support.
1102 Novell Kernel Services thread support.
1106 Specify that the target supports TLS (Thread Local Storage). Usually
1107 configure can correctly determine if TLS is supported. In cases where
1108 it guesses incorrectly, TLS can be explicitly enabled or disabled with
1109 @option{--enable-tls} or @option{--disable-tls}. This can happen if
1110 the assembler supports TLS but the C library does not, or if the
1111 assumptions made by the configure test are incorrect.
1114 Specify that the target does not support TLS.
1115 This is an alias for @option{--enable-tls=no}.
1117 @item --with-cpu=@var{cpu}
1118 @itemx --with-cpu-32=@var{cpu}
1119 @itemx --with-cpu-64=@var{cpu}
1120 Specify which cpu variant the compiler should generate code for by default.
1121 @var{cpu} will be used as the default value of the @option{-mcpu=} switch.
1122 This option is only supported on some targets, including ARM, i386, M68k,
1123 PowerPC, and SPARC@. The @option{--with-cpu-32} and
1124 @option{--with-cpu-64} options specify separate default CPUs for
1125 32-bit and 64-bit modes; these options are only supported for i386,
1128 @item --with-schedule=@var{cpu}
1129 @itemx --with-arch=@var{cpu}
1130 @itemx --with-arch-32=@var{cpu}
1131 @itemx --with-arch-64=@var{cpu}
1132 @itemx --with-tune=@var{cpu}
1133 @itemx --with-tune-32=@var{cpu}
1134 @itemx --with-tune-64=@var{cpu}
1135 @itemx --with-abi=@var{abi}
1136 @itemx --with-fpu=@var{type}
1137 @itemx --with-float=@var{type}
1138 These configure options provide default values for the @option{-mschedule=},
1139 @option{-march=}, @option{-mtune=}, @option{-mabi=}, and @option{-mfpu=}
1140 options and for @option{-mhard-float} or @option{-msoft-float}. As with
1141 @option{--with-cpu}, which switches will be accepted and acceptable values
1142 of the arguments depend on the target.
1144 @item --with-mode=@var{mode}
1145 Specify if the compiler should default to @option{-marm} or @option{-mthumb}.
1146 This option is only supported on ARM targets.
1148 @item --with-divide=@var{type}
1149 Specify how the compiler should generate code for checking for
1150 division by zero. This option is only supported on the MIPS target.
1151 The possibilities for @var{type} are:
1154 Division by zero checks use conditional traps (this is the default on
1155 systems that support conditional traps).
1157 Division by zero checks use the break instruction.
1160 @c If you make --with-llsc the default for additional targets,
1161 @c update the --with-llsc description in the MIPS section below.
1164 On MIPS targets, make @option{-mllsc} the default when no
1165 @option{-mno-lsc} option is passed. This is the default for
1166 Linux-based targets, as the kernel will emulate them if the ISA does
1169 @item --without-llsc
1170 On MIPS targets, make @option{-mno-llsc} the default when no
1171 @option{-mllsc} option is passed.
1173 @item --with-mips-plt
1174 On MIPS targets, make use of copy relocations and PLTs.
1175 These features are extensions to the traditional
1176 SVR4-based MIPS ABIs and require support from GNU binutils
1177 and the runtime C library.
1179 @item --enable-__cxa_atexit
1180 Define if you want to use __cxa_atexit, rather than atexit, to
1181 register C++ destructors for local statics and global objects.
1182 This is essential for fully standards-compliant handling of
1183 destructors, but requires __cxa_atexit in libc. This option is currently
1184 only available on systems with GNU libc. When enabled, this will cause
1185 @option{-fuse-cxa-atexit} to be passed by default.
1187 @item --enable-target-optspace
1189 libraries should be optimized for code space instead of code speed.
1190 This is the default for the m32r platform.
1193 Specify that a user visible @command{cpp} program should not be installed.
1195 @item --with-cpp-install-dir=@var{dirname}
1196 Specify that the user visible @command{cpp} program should be installed
1197 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
1199 @item --enable-initfini-array
1200 Force the use of sections @code{.init_array} and @code{.fini_array}
1201 (instead of @code{.init} and @code{.fini}) for constructors and
1202 destructors. Option @option{--disable-initfini-array} has the
1203 opposite effect. If neither option is specified, the configure script
1204 will try to guess whether the @code{.init_array} and
1205 @code{.fini_array} sections are supported and, if they are, use them.
1207 @item --enable-maintainer-mode
1208 The build rules that
1209 regenerate the GCC master message catalog @file{gcc.pot} are normally
1210 disabled. This is because it can only be rebuilt if the complete source
1211 tree is present. If you have changed the sources and want to rebuild the
1212 catalog, configuring with @option{--enable-maintainer-mode} will enable
1213 this. Note that you need a recent version of the @code{gettext} tools
1216 @item --disable-bootstrap
1217 For a native build, the default configuration is to perform
1218 a 3-stage bootstrap of the compiler when @samp{make} is invoked,
1219 testing that GCC can compile itself correctly. If you want to disable
1220 this process, you can configure with @option{--disable-bootstrap}.
1222 @item --enable-bootstrap
1223 In special cases, you may want to perform a 3-stage build
1224 even if the target and host triplets are different.
1225 This could happen when the host can run code compiled for
1226 the target (e.g.@: host is i686-linux, target is i486-linux).
1227 Starting from GCC 4.2, to do this you have to configure explicitly
1228 with @option{--enable-bootstrap}.
1230 @item --enable-generated-files-in-srcdir
1231 Neither the .c and .h files that are generated from Bison and flex nor the
1232 info manuals and man pages that are built from the .texi files are present
1233 in the SVN development tree. When building GCC from that development tree,
1234 or from one of our snapshots, those generated files are placed in your
1235 build directory, which allows for the source to be in a readonly
1238 If you configure with @option{--enable-generated-files-in-srcdir} then those
1239 generated files will go into the source directory. This is mainly intended
1240 for generating release or prerelease tarballs of the GCC sources, since it
1241 is not a requirement that the users of source releases to have flex, Bison,
1244 @item --enable-version-specific-runtime-libs
1246 that runtime libraries should be installed in the compiler specific
1247 subdirectory (@file{@var{libdir}/gcc}) rather than the usual places. In
1248 addition, @samp{libstdc++}'s include files will be installed into
1249 @file{@var{libdir}} unless you overruled it by using
1250 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
1251 particularly useful if you intend to use several versions of GCC in
1252 parallel. This is currently supported by @samp{libgfortran},
1253 @samp{libjava}, @samp{libmudflap}, @samp{libstdc++}, and @samp{libobjc}.
1255 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
1256 Specify that only a particular subset of compilers and
1257 their runtime libraries should be built. For a list of valid values for
1258 @var{langN} you can issue the following command in the
1259 @file{gcc} directory of your GCC source tree:@*
1261 grep language= */config-lang.in
1263 Currently, you can use any of the following:
1264 @code{all}, @code{ada}, @code{c}, @code{c++}, @code{fortran}, @code{java},
1265 @code{objc}, @code{obj-c++}.
1266 Building the Ada compiler has special requirements, see below.
1267 If you do not pass this flag, or specify the option @code{all}, then all
1268 default languages available in the @file{gcc} sub-tree will be configured.
1269 Ada and Objective-C++ are not default languages; the rest are.
1270 Re-defining @code{LANGUAGES} when calling @samp{make} @strong{does not}
1271 work anymore, as those language sub-directories might not have been
1274 @item --enable-stage1-languages=@var{lang1},@var{lang2},@dots{}
1275 Specify that a particular subset of compilers and their runtime
1276 libraries should be built with the system C compiler during stage 1 of
1277 the bootstrap process, rather than only in later stages with the
1278 bootstrapped C compiler. The list of valid values is the same as for
1279 @option{--enable-languages}, and the option @code{all} will select all
1280 of the languages enabled by @option{--enable-languages}. This option is
1281 primarily useful for GCC development; for instance, when a development
1282 version of the compiler cannot bootstrap due to compiler bugs, or when
1283 one is debugging front ends other than the C front end. When this
1284 option is used, one can then build the target libraries for the
1285 specified languages with the stage-1 compiler by using @command{make
1286 stage1-bubble all-target}, or run the testsuite on the stage-1 compiler
1287 for the specified languages using @command{make stage1-start check-gcc}.
1289 @item --disable-libada
1290 Specify that the run-time libraries and tools used by GNAT should not
1291 be built. This can be useful for debugging, or for compatibility with
1292 previous Ada build procedures, when it was required to explicitly
1293 do a @samp{make -C gcc gnatlib_and_tools}.
1295 @item --disable-libssp
1296 Specify that the run-time libraries for stack smashing protection
1297 should not be built.
1299 @item --disable-libgomp
1300 Specify that the run-time libraries used by GOMP should not be built.
1303 Specify that the compiler should
1304 use DWARF 2 debugging information as the default.
1306 @item --enable-targets=all
1307 @itemx --enable-targets=@var{target_list}
1308 Some GCC targets, e.g.@: powerpc64-linux, build bi-arch compilers.
1309 These are compilers that are able to generate either 64-bit or 32-bit
1310 code. Typically, the corresponding 32-bit target, e.g.@:
1311 powerpc-linux for powerpc64-linux, only generates 32-bit code. This
1312 option enables the 32-bit target to be a bi-arch compiler, which is
1313 useful when you want a bi-arch compiler that defaults to 32-bit, and
1314 you are building a bi-arch or multi-arch binutils in a combined tree.
1315 Currently, this option only affects sparc-linux, powerpc-linux and
1318 @item --enable-secureplt
1319 This option enables @option{-msecure-plt} by default for powerpc-linux.
1321 @xref{RS/6000 and PowerPC Options,, RS/6000 and PowerPC Options, gcc,
1322 Using the GNU Compiler Collection (GCC)},
1325 See ``RS/6000 and PowerPC Options'' in the main manual
1329 This option enables @option{-mcld} by default for 32-bit x86 targets.
1331 @xref{i386 and x86-64 Options,, i386 and x86-64 Options, gcc,
1332 Using the GNU Compiler Collection (GCC)},
1335 See ``i386 and x86-64 Options'' in the main manual
1338 @item --enable-win32-registry
1339 @itemx --enable-win32-registry=@var{key}
1340 @itemx --disable-win32-registry
1341 The @option{--enable-win32-registry} option enables Microsoft Windows-hosted GCC
1342 to look up installations paths in the registry using the following key:
1345 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
1348 @var{key} defaults to GCC version number, and can be overridden by the
1349 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
1350 who use custom installers are encouraged to provide a different key,
1351 perhaps one comprised of vendor name and GCC version number, to
1352 avoid conflict with existing installations. This feature is enabled
1353 by default, and can be disabled by @option{--disable-win32-registry}
1354 option. This option has no effect on the other hosts.
1357 Specify that the machine does not have a floating point unit. This
1358 option only applies to @samp{m68k-sun-sunos@var{n}}. On any other
1359 system, @option{--nfp} has no effect.
1361 @item --enable-werror
1362 @itemx --disable-werror
1363 @itemx --enable-werror=yes
1364 @itemx --enable-werror=no
1365 When you specify this option, it controls whether certain files in the
1366 compiler are built with @option{-Werror} in bootstrap stage2 and later.
1367 If you don't specify it, @option{-Werror} is turned on for the main
1368 development trunk. However it defaults to off for release branches and
1369 final releases. The specific files which get @option{-Werror} are
1370 controlled by the Makefiles.
1372 @item --enable-checking
1373 @itemx --enable-checking=@var{list}
1374 When you specify this option, the compiler is built to perform internal
1375 consistency checks of the requested complexity. This does not change the
1376 generated code, but adds error checking within the compiler. This will
1377 slow down the compiler and may only work properly if you are building
1378 the compiler with GCC@. This is @samp{yes} by default when building
1379 from SVN or snapshots, but @samp{release} for releases. The default
1380 for building the stage1 compiler is @samp{yes}. More control
1381 over the checks may be had by specifying @var{list}. The categories of
1382 checks available are @samp{yes} (most common checks
1383 @samp{assert,misc,tree,gc,rtlflag,runtime}), @samp{no} (no checks at
1384 all), @samp{all} (all but @samp{valgrind}), @samp{release} (cheapest
1385 checks @samp{assert,runtime}) or @samp{none} (same as @samp{no}).
1386 Individual checks can be enabled with these flags @samp{assert},
1387 @samp{df}, @samp{fold}, @samp{gc}, @samp{gcac} @samp{misc}, @samp{rtl},
1388 @samp{rtlflag}, @samp{runtime}, @samp{tree}, and @samp{valgrind}.
1390 The @samp{valgrind} check requires the external @command{valgrind}
1391 simulator, available from @uref{http://valgrind.org/}. The
1392 @samp{df}, @samp{rtl}, @samp{gcac} and @samp{valgrind} checks are very expensive.
1393 To disable all checking, @samp{--disable-checking} or
1394 @samp{--enable-checking=none} must be explicitly requested. Disabling
1395 assertions will make the compiler and runtime slightly faster but
1396 increase the risk of undetected internal errors causing wrong code to be
1399 @item --disable-stage1-checking
1400 @item --enable-stage1-checking
1401 @itemx --enable-stage1-checking=@var{list}
1402 If no @option{--enable-checking} option is specified the stage1
1403 compiler will be built with @samp{yes} checking enabled, otherwise
1404 the stage1 checking flags are the same as specified by
1405 @option{--enable-checking}. To build the stage1 compiler with
1406 different checking options use @option{--enable-stage1-checking}.
1407 The list of checking options is the same as for @option{--enable-checking}.
1408 If your system is too slow or too small to bootstrap a released compiler
1409 with checking for stage1 enabled, you can use @samp{--disable-stage1-checking}
1410 to disable checking for the stage1 compiler.
1412 @item --enable-coverage
1413 @itemx --enable-coverage=@var{level}
1414 With this option, the compiler is built to collect self coverage
1415 information, every time it is run. This is for internal development
1416 purposes, and only works when the compiler is being built with gcc. The
1417 @var{level} argument controls whether the compiler is built optimized or
1418 not, values are @samp{opt} and @samp{noopt}. For coverage analysis you
1419 want to disable optimization, for performance analysis you want to
1420 enable optimization. When coverage is enabled, the default level is
1421 without optimization.
1423 @item --enable-gather-detailed-mem-stats
1424 When this option is specified more detailed information on memory
1425 allocation is gathered. This information is printed when using
1426 @option{-fmem-report}.
1429 @itemx --with-gc=@var{choice}
1430 With this option you can specify the garbage collector implementation
1431 used during the compilation process. @var{choice} can be one of
1432 @samp{page} and @samp{zone}, where @samp{page} is the default.
1435 @itemx --disable-nls
1436 The @option{--enable-nls} option enables Native Language Support (NLS),
1437 which lets GCC output diagnostics in languages other than American
1438 English. Native Language Support is enabled by default if not doing a
1439 canadian cross build. The @option{--disable-nls} option disables NLS@.
1441 @item --with-included-gettext
1442 If NLS is enabled, the @option{--with-included-gettext} option causes the build
1443 procedure to prefer its copy of GNU @command{gettext}.
1445 @item --with-catgets
1446 If NLS is enabled, and if the host lacks @code{gettext} but has the
1447 inferior @code{catgets} interface, the GCC build procedure normally
1448 ignores @code{catgets} and instead uses GCC's copy of the GNU
1449 @code{gettext} library. The @option{--with-catgets} option causes the
1450 build procedure to use the host's @code{catgets} in this situation.
1452 @item --with-libiconv-prefix=@var{dir}
1453 Search for libiconv header files in @file{@var{dir}/include} and
1454 libiconv library files in @file{@var{dir}/lib}.
1456 @item --enable-obsolete
1457 Enable configuration for an obsoleted system. If you attempt to
1458 configure GCC for a system (build, host, or target) which has been
1459 obsoleted, and you do not specify this flag, configure will halt with an
1462 All support for systems which have been obsoleted in one release of GCC
1463 is removed entirely in the next major release, unless someone steps
1464 forward to maintain the port.
1466 @item --enable-decimal-float
1467 @itemx --enable-decimal-float=yes
1468 @itemx --enable-decimal-float=no
1469 @itemx --enable-decimal-float=bid
1470 @itemx --enable-decimal-float=dpd
1471 @itemx --disable-decimal-float
1472 Enable (or disable) support for the C decimal floating point extension
1473 that is in the IEEE 754-2008 standard. This is enabled by default only
1474 on PowerPC, i386, and x86_64 GNU/Linux systems. Other systems may also
1475 support it, but require the user to specifically enable it. You can
1476 optionally control which decimal floating point format is used (either
1477 @samp{bid} or @samp{dpd}). The @samp{bid} (binary integer decimal)
1478 format is default on i386 and x86_64 systems, and the @samp{dpd}
1479 (densely packed decimal) format is default on PowerPC systems.
1481 @item --enable-fixed-point
1482 @itemx --disable-fixed-point
1483 Enable (or disable) support for C fixed-point arithmetic.
1484 This option is enabled by default for some targets (such as MIPS) which
1485 have hardware-support for fixed-point operations. On other targets, you
1486 may enable this option manually.
1488 @item --with-long-double-128
1489 Specify if @code{long double} type should be 128-bit by default on selected
1490 GNU/Linux architectures. If using @code{--without-long-double-128},
1491 @code{long double} will be by default 64-bit, the same as @code{double} type.
1492 When neither of these configure options are used, the default will be
1493 128-bit @code{long double} when built against GNU C Library 2.4 and later,
1494 64-bit @code{long double} otherwise.
1496 @item --with-gmp=@var{pathname}
1497 @itemx --with-gmp-include=@var{pathname}
1498 @itemx --with-gmp-lib=@var{pathname}
1499 @itemx --with-mpfr=@var{pathname}
1500 @itemx --with-mpfr-include=@var{pathname}
1501 @itemx --with-mpfr-lib=@var{pathname}
1502 @itemx --with-mpc=@var{pathname}
1503 @itemx --with-mpc-include=@var{pathname}
1504 @itemx --with-mpc-lib=@var{pathname}
1505 If you do not have GMP (the GNU Multiple Precision library), the MPFR
1506 library and/or the MPC library installed in a standard location and
1507 you want to build GCC, you can explicitly specify the directory where
1508 they are installed (@samp{--with-gmp=@var{gmpinstalldir}},
1509 @samp{--with-mpfr=@var{mpfrinstalldir}},
1510 @samp{--with-mpc=@var{mpcinstalldir}}). The
1511 @option{--with-gmp=@var{gmpinstalldir}} option is shorthand for
1512 @option{--with-gmp-lib=@var{gmpinstalldir}/lib} and
1513 @option{--with-gmp-include=@var{gmpinstalldir}/include}. Likewise the
1514 @option{--with-mpfr=@var{mpfrinstalldir}} option is shorthand for
1515 @option{--with-mpfr-lib=@var{mpfrinstalldir}/lib} and
1516 @option{--with-mpfr-include=@var{mpfrinstalldir}/include}, also the
1517 @option{--with-mpc=@var{mpcinstalldir}} option is shorthand for
1518 @option{--with-mpc-lib=@var{mpcinstalldir}/lib} and
1519 @option{--with-mpc-include=@var{mpcinstalldir}/include}. If these
1520 shorthand assumptions are not correct, you can use the explicit
1521 include and lib options directly.
1523 @item --with-ppl=@var{pathname}
1524 @itemx --with-ppl-include=@var{pathname}
1525 @itemx --with-ppl-lib=@var{pathname}
1526 @itemx --with-cloog=@var{pathname}
1527 @itemx --with-cloog-include=@var{pathname}
1528 @itemx --with-cloog-lib=@var{pathname}
1529 If you do not have PPL (the Parma Polyhedra Library) and the CLooG
1530 libraries installed in a standard location and you want to build GCC,
1531 you can explicitly specify the directory where they are installed
1532 (@samp{--with-ppl=@var{pplinstalldir}},
1533 @samp{--with-cloog=@var{clooginstalldir}}). The
1534 @option{--with-ppl=@var{pplinstalldir}} option is shorthand for
1535 @option{--with-ppl-lib=@var{pplinstalldir}/lib} and
1536 @option{--with-ppl-include=@var{pplinstalldir}/include}. Likewise the
1537 @option{--with-cloog=@var{clooginstalldir}} option is shorthand for
1538 @option{--with-cloog-lib=@var{clooginstalldir}/lib} and
1539 @option{--with-cloog-include=@var{clooginstalldir}/include}. If these
1540 shorthand assumptions are not correct, you can use the explicit
1541 include and lib options directly.
1543 @item --with-host-libstdcxx=@var{linker-args}
1544 If you are linking with a static copy of PPL, you can use this option
1545 to specify how the linker should find the standard C++ library used
1546 internally by PPL. Typical values of @var{linker-args} might be
1547 @samp{-lstdc++} or @samp{-Wl,-Bstatic,-lstdc++,-Bdynamic -lm}. If you are
1548 linking with a shared copy of PPL, you probably do not need this
1549 option; shared library dependencies will cause the linker to search
1550 for the standard C++ library automatically.
1552 @item --with-debug-prefix-map=@var{map}
1553 Convert source directory names using @option{-fdebug-prefix-map} when
1554 building runtime libraries. @samp{@var{map}} is a space-separated
1555 list of maps of the form @samp{@var{old}=@var{new}}.
1557 @item --enable-linker-build-id
1558 Tells GCC to pass @option{--build-id} option to the linker for all final
1559 links (links performed without the @option{-r} or @option{--relocatable}
1560 option), if the linker supports it. If you specify
1561 @option{--enable-linker-build-id}, but your linker does not
1562 support @option{--build-id} option, a warning is issued and the
1563 @option{--enable-linker-build-id} option is ignored. The default is off.
1567 @subheading Cross-Compiler-Specific Options
1568 The following options only apply to building cross compilers.
1570 @item --with-sysroot
1571 @itemx --with-sysroot=@var{dir}
1572 Tells GCC to consider @var{dir} as the root of a tree that contains a
1573 (subset of) the root filesystem of the target operating system.
1574 Target system headers, libraries and run-time object files will be
1575 searched in there. The specified directory is not copied into the
1576 install tree, unlike the options @option{--with-headers} and
1577 @option{--with-libs} that this option obsoletes. The default value,
1578 in case @option{--with-sysroot} is not given an argument, is
1579 @option{$@{gcc_tooldir@}/sys-root}. If the specified directory is a
1580 subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to
1581 the GCC binaries if the installation tree is moved.
1583 @item --with-build-sysroot
1584 @itemx --with-build-sysroot=@var{dir}
1585 Tells GCC to consider @var{dir} as the system root (see
1586 @option{--with-sysroot}) while building target libraries, instead of
1587 the directory specified with @option{--with-sysroot}. This option is
1588 only useful when you are already using @option{--with-sysroot}. You
1589 can use @option{--with-build-sysroot} when you are configuring with
1590 @option{--prefix} set to a directory that is different from the one in
1591 which you are installing GCC and your target libraries.
1593 This option affects the system root for the compiler used to build
1594 target libraries (which runs on the build system); it does not affect
1595 the compiler which is used to build GCC itself.
1597 @item --with-headers
1598 @itemx --with-headers=@var{dir}
1599 Deprecated in favor of @option{--with-sysroot}.
1600 Specifies that target headers are available when building a cross compiler.
1601 The @var{dir} argument specifies a directory which has the target include
1602 files. These include files will be copied into the @file{gcc} install
1603 directory. @emph{This option with the @var{dir} argument is required} when
1604 building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include}
1605 doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does
1606 pre-exist, the @var{dir} argument may be omitted. @command{fixincludes}
1607 will be run on these files to make them compatible with GCC@.
1609 @item --without-headers
1610 Tells GCC not use any target headers from a libc when building a cross
1611 compiler. When crossing to GNU/Linux, you need the headers so GCC
1612 can build the exception handling for libgcc.
1615 @itemx --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
1616 Deprecated in favor of @option{--with-sysroot}.
1617 Specifies a list of directories which contain the target runtime
1618 libraries. These libraries will be copied into the @file{gcc} install
1619 directory. If the directory list is omitted, this option has no
1623 Specifies that @samp{newlib} is
1624 being used as the target C library. This causes @code{__eprintf} to be
1625 omitted from @file{libgcc.a} on the assumption that it will be provided by
1628 @item --with-build-time-tools=@var{dir}
1629 Specifies where to find the set of target tools (assembler, linker, etc.)
1630 that will be used while building GCC itself. This option can be useful
1631 if the directory layouts are different between the system you are building
1632 GCC on, and the system where you will deploy it.
1634 For example, on an @samp{ia64-hp-hpux} system, you may have the GNU
1635 assembler and linker in @file{/usr/bin}, and the native tools in a
1636 different path, and build a toolchain that expects to find the
1637 native tools in @file{/usr/bin}.
1639 When you use this option, you should ensure that @var{dir} includes
1640 @command{ar}, @command{as}, @command{ld}, @command{nm},
1641 @command{ranlib} and @command{strip} if necessary, and possibly
1642 @command{objdump}. Otherwise, GCC may use an inconsistent set of
1646 @subheading Java-Specific Options
1648 The following option applies to the build of the Java front end.
1651 @item --disable-libgcj
1652 Specify that the run-time libraries
1653 used by GCJ should not be built. This is useful in case you intend
1654 to use GCJ with some other run-time, or you're going to install it
1655 separately, or it just happens not to build on your particular
1656 machine. In general, if the Java front end is enabled, the GCJ
1657 libraries will be enabled too, unless they're known to not work on
1658 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
1659 may need to port it; in this case, before modifying the top-level
1660 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
1661 you may use @option{--enable-libgcj} to override the default.
1665 The following options apply to building @samp{libgcj}.
1667 @subsubheading General Options
1670 @item --enable-java-maintainer-mode
1671 By default the @samp{libjava} build will not attempt to compile the
1672 @file{.java} source files to @file{.class}. Instead, it will use the
1673 @file{.class} files from the source tree. If you use this option you
1674 must have executables named @command{ecj1} and @command{gjavah} in your path
1675 for use by the build. You must use this option if you intend to
1676 modify any @file{.java} files in @file{libjava}.
1678 @item --with-java-home=@var{dirname}
1679 This @samp{libjava} option overrides the default value of the
1680 @samp{java.home} system property. It is also used to set
1681 @samp{sun.boot.class.path} to @file{@var{dirname}/lib/rt.jar}. By
1682 default @samp{java.home} is set to @file{@var{prefix}} and
1683 @samp{sun.boot.class.path} to
1684 @file{@var{datadir}/java/libgcj-@var{version}.jar}.
1686 @item --with-ecj-jar=@var{filename}
1687 This option can be used to specify the location of an external jar
1688 file containing the Eclipse Java compiler. A specially modified
1689 version of this compiler is used by @command{gcj} to parse
1690 @file{.java} source files. If this option is given, the
1691 @samp{libjava} build will create and install an @file{ecj1} executable
1692 which uses this jar file at runtime.
1694 If this option is not given, but an @file{ecj.jar} file is found in
1695 the topmost source tree at configure time, then the @samp{libgcj}
1696 build will create and install @file{ecj1}, and will also install the
1697 discovered @file{ecj.jar} into a suitable place in the install tree.
1699 If @file{ecj1} is not installed, then the user will have to supply one
1700 on his path in order for @command{gcj} to properly parse @file{.java}
1701 source files. A suitable jar is available from
1702 @uref{ftp://sourceware.org/pub/java/}.
1704 @item --disable-getenv-properties
1705 Don't set system properties from @env{GCJ_PROPERTIES}.
1707 @item --enable-hash-synchronization
1708 Use a global hash table for monitor locks. Ordinarily,
1709 @samp{libgcj}'s @samp{configure} script automatically makes
1710 the correct choice for this option for your platform. Only use
1711 this if you know you need the library to be configured differently.
1713 @item --enable-interpreter
1714 Enable the Java interpreter. The interpreter is automatically
1715 enabled by default on all platforms that support it. This option
1716 is really only useful if you want to disable the interpreter
1717 (using @option{--disable-interpreter}).
1719 @item --disable-java-net
1720 Disable java.net. This disables the native part of java.net only,
1721 using non-functional stubs for native method implementations.
1723 @item --disable-jvmpi
1724 Disable JVMPI support.
1726 @item --disable-libgcj-bc
1727 Disable BC ABI compilation of certain parts of libgcj. By default,
1728 some portions of libgcj are compiled with @option{-findirect-dispatch}
1729 and @option{-fno-indirect-classes}, allowing them to be overridden at
1732 If @option{--disable-libgcj-bc} is specified, libgcj is built without
1733 these options. This allows the compile-time linker to resolve
1734 dependencies when statically linking to libgcj. However it makes it
1735 impossible to override the affected portions of libgcj at run-time.
1737 @item --enable-reduced-reflection
1738 Build most of libgcj with @option{-freduced-reflection}. This reduces
1739 the size of libgcj at the expense of not being able to do accurate
1740 reflection on the classes it contains. This option is safe if you
1741 know that code using libgcj will never use reflection on the standard
1742 runtime classes in libgcj (including using serialization, RMI or CORBA).
1745 Enable runtime eCos target support.
1747 @item --without-libffi
1748 Don't use @samp{libffi}. This will disable the interpreter and JNI
1749 support as well, as these require @samp{libffi} to work.
1751 @item --enable-libgcj-debug
1752 Enable runtime debugging code.
1754 @item --enable-libgcj-multifile
1755 If specified, causes all @file{.java} source files to be
1756 compiled into @file{.class} files in one invocation of
1757 @samp{gcj}. This can speed up build time, but is more
1758 resource-intensive. If this option is unspecified or
1759 disabled, @samp{gcj} is invoked once for each @file{.java}
1760 file to compile into a @file{.class} file.
1762 @item --with-libiconv-prefix=DIR
1763 Search for libiconv in @file{DIR/include} and @file{DIR/lib}.
1765 @item --enable-sjlj-exceptions
1766 Force use of the @code{setjmp}/@code{longjmp}-based scheme for exceptions.
1767 @samp{configure} ordinarily picks the correct value based on the platform.
1768 Only use this option if you are sure you need a different setting.
1770 @item --with-system-zlib
1771 Use installed @samp{zlib} rather than that included with GCC@.
1773 @item --with-win32-nlsapi=ansi, unicows or unicode
1774 Indicates how MinGW @samp{libgcj} translates between UNICODE
1775 characters and the Win32 API@.
1777 @item --enable-java-home
1778 If enabled, this creates a JPackage compatible SDK environment during install.
1779 Note that if --enable-java-home is used, --with-arch-directory=ARCH must also
1782 @item --with-arch-directory=ARCH
1783 Specifies the name to use for the @file{jre/lib/ARCH} directory in the SDK
1784 environment created when --enable-java-home is passed. Typical names for this
1785 directory include i386, amd64, ia64, etc.
1787 @item --with-os-directory=DIR
1788 Specifies the OS directory for the SDK include directory. This is set to auto
1789 detect, and is typically 'linux'.
1791 @item --with-origin-name=NAME
1792 Specifies the JPackage origin name. This defaults to the 'gcj' in
1795 @item --with-arch-suffix=SUFFIX
1796 Specifies the suffix for the sdk directory. Defaults to the empty string.
1797 Examples include '.x86_64' in 'java-1.5.0-gcj-1.5.0.0.x86_64'.
1799 @item --with-jvm-root-dir=DIR
1800 Specifies where to install the SDK. Default is $(prefix)/lib/jvm.
1802 @item --with-jvm-jar-dir=DIR
1803 Specifies where to install jars. Default is $(prefix)/lib/jvm-exports.
1805 @item --with-python-dir=DIR
1806 Specifies where to install the Python modules used for aot-compile. DIR should
1807 not include the prefix used in installation. For example, if the Python modules
1808 are to be installed in /usr/lib/python2.5/site-packages, then
1809 --with-python-dir=/lib/python2.5/site-packages should be passed. If this is
1810 not specified, then the Python modules are installed in $(prefix)/share/python.
1812 @item --enable-aot-compile-rpm
1813 Adds aot-compile-rpm to the list of installed scripts.
1817 Use the single-byte @code{char} and the Win32 A functions natively,
1818 translating to and from UNICODE when using these functions. If
1819 unspecified, this is the default.
1822 Use the @code{WCHAR} and Win32 W functions natively. Adds
1823 @code{-lunicows} to @file{libgcj.spec} to link with @samp{libunicows}.
1824 @file{unicows.dll} needs to be deployed on Microsoft Windows 9X machines
1825 running built executables. @file{libunicows.a}, an open-source
1826 import library around Microsoft's @code{unicows.dll}, is obtained from
1827 @uref{http://libunicows.sourceforge.net/}, which also gives details
1828 on getting @file{unicows.dll} from Microsoft.
1831 Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not}
1832 add @code{-lunicows} to @file{libgcj.spec}. The built executables will
1833 only run on Microsoft Windows NT and above.
1837 @subsubheading AWT-Specific Options
1841 Use the X Window System.
1843 @item --enable-java-awt=PEER(S)
1844 Specifies the AWT peer library or libraries to build alongside
1845 @samp{libgcj}. If this option is unspecified or disabled, AWT
1846 will be non-functional. Current valid values are @option{gtk} and
1847 @option{xlib}. Multiple libraries should be separated by a
1848 comma (i.e.@: @option{--enable-java-awt=gtk,xlib}).
1850 @item --enable-gtk-cairo
1851 Build the cairo Graphics2D implementation on GTK@.
1853 @item --enable-java-gc=TYPE
1854 Choose garbage collector. Defaults to @option{boehm} if unspecified.
1856 @item --disable-gtktest
1857 Do not try to compile and run a test GTK+ program.
1859 @item --disable-glibtest
1860 Do not try to compile and run a test GLIB program.
1862 @item --with-libart-prefix=PFX
1863 Prefix where libart is installed (optional).
1865 @item --with-libart-exec-prefix=PFX
1866 Exec prefix where libart is installed (optional).
1868 @item --disable-libarttest
1869 Do not try to compile and run a test libart program.
1878 @uref{./index.html,,Return to the GCC Installation page}
1882 @c ***Building****************************************************************
1884 @comment node-name, next, previous, up
1885 @node Building, Testing, Configuration, Installing GCC
1891 @cindex Installing GCC: Building
1893 Now that GCC is configured, you are ready to build the compiler and
1896 Some commands executed when making the compiler may fail (return a
1897 nonzero status) and be ignored by @command{make}. These failures, which
1898 are often due to files that were not found, are expected, and can safely
1901 It is normal to have compiler warnings when compiling certain files.
1902 Unless you are a GCC developer, you can generally ignore these warnings
1903 unless they cause compilation to fail. Developers should attempt to fix
1904 any warnings encountered, however they can temporarily continue past
1905 warnings-as-errors by specifying the configure flag
1906 @option{--disable-werror}.
1908 On certain old systems, defining certain environment variables such as
1909 @env{CC} can interfere with the functioning of @command{make}.
1911 If you encounter seemingly strange errors when trying to build the
1912 compiler in a directory other than the source directory, it could be
1913 because you have previously configured the compiler in the source
1914 directory. Make sure you have done all the necessary preparations.
1916 If you build GCC on a BSD system using a directory stored in an old System
1917 V file system, problems may occur in running @command{fixincludes} if the
1918 System V file system doesn't support symbolic links. These problems
1919 result in a failure to fix the declaration of @code{size_t} in
1920 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
1921 that type mismatches occur, this could be the cause.
1923 The solution is not to use such a directory for building GCC@.
1925 Similarly, when building from SVN or snapshots, or if you modify
1926 @file{*.l} files, you need the Flex lexical analyzer generator
1927 installed. If you do not modify @file{*.l} files, releases contain
1928 the Flex-generated files and you do not need Flex installed to build
1929 them. There is still one Flex-based lexical analyzer (part of the
1930 build machinery, not of GCC itself) that is used even if you only
1931 build the C front end.
1933 When building from SVN or snapshots, or if you modify Texinfo
1934 documentation, you need version 4.7 or later of Texinfo installed if you
1935 want Info documentation to be regenerated. Releases contain Info
1936 documentation pre-built for the unmodified documentation in the release.
1938 @section Building a native compiler
1940 For a native build, the default configuration is to perform
1941 a 3-stage bootstrap of the compiler when @samp{make} is invoked.
1942 This will build the entire GCC system and ensure that it compiles
1943 itself correctly. It can be disabled with the @option{--disable-bootstrap}
1944 parameter to @samp{configure}, but bootstrapping is suggested because
1945 the compiler will be tested more completely and could also have
1948 The bootstrapping process will complete the following steps:
1952 Build tools necessary to build the compiler.
1955 Perform a 3-stage bootstrap of the compiler. This includes building
1956 three times the target tools for use by the compiler such as binutils
1957 (bfd, binutils, gas, gprof, ld, and opcodes) if they have been
1958 individually linked or moved into the top level GCC source tree before
1962 Perform a comparison test of the stage2 and stage3 compilers.
1965 Build runtime libraries using the stage3 compiler from the previous step.
1969 If you are short on disk space you might consider @samp{make
1970 bootstrap-lean} instead. The sequence of compilation is the
1971 same described above, but object files from the stage1 and
1972 stage2 of the 3-stage bootstrap of the compiler are deleted as
1973 soon as they are no longer needed.
1975 If you wish to use non-default GCC flags when compiling the stage2
1976 and stage3 compilers, set @code{BOOT_CFLAGS} on the command line when
1977 doing @samp{make}. For example, if you want to save additional space
1978 during the bootstrap and in the final installation as well, you can
1979 build the compiler binaries without debugging information as in the
1980 following example. This will save roughly 40% of disk space both for
1981 the bootstrap and the final installation. (Libraries will still contain
1982 debugging information.)
1985 make BOOT_CFLAGS='-O' bootstrap
1988 You can place non-default optimization flags into @code{BOOT_CFLAGS}; they
1989 are less well tested here than the default of @samp{-g -O2}, but should
1990 still work. In a few cases, you may find that you need to specify special
1991 flags such as @option{-msoft-float} here to complete the bootstrap; or,
1992 if the native compiler miscompiles the stage1 compiler, you may need
1993 to work around this, by choosing @code{BOOT_CFLAGS} to avoid the parts
1994 of the stage1 compiler that were miscompiled, or by using @samp{make
1995 bootstrap4} to increase the number of stages of bootstrap.
1997 @code{BOOT_CFLAGS} does not apply to bootstrapped target libraries.
1998 Since these are always compiled with the compiler currently being
1999 bootstrapped, you can use @code{CFLAGS_FOR_TARGET} to modify their
2000 compilation flags, as for non-bootstrapped target libraries.
2001 Again, if the native compiler miscompiles the stage1 compiler, you may
2002 need to work around this by avoiding non-working parts of the stage1
2003 compiler. Use @code{STAGE1_TFLAGS} to this end.
2005 If you used the flag @option{--enable-languages=@dots{}} to restrict
2006 the compilers to be built, only those you've actually enabled will be
2007 built. This will of course only build those runtime libraries, for
2008 which the particular compiler has been built. Please note,
2009 that re-defining @env{LANGUAGES} when calling @samp{make}
2010 @strong{does not} work anymore!
2012 If the comparison of stage2 and stage3 fails, this normally indicates
2013 that the stage2 compiler has compiled GCC incorrectly, and is therefore
2014 a potentially serious bug which you should investigate and report. (On
2015 a few systems, meaningful comparison of object files is impossible; they
2016 always appear ``different''. If you encounter this problem, you will
2017 need to disable comparison in the @file{Makefile}.)
2019 If you do not want to bootstrap your compiler, you can configure with
2020 @option{--disable-bootstrap}. In particular cases, you may want to
2021 bootstrap your compiler even if the target system is not the same as
2022 the one you are building on: for example, you could build a
2023 @code{powerpc-unknown-linux-gnu} toolchain on a
2024 @code{powerpc64-unknown-linux-gnu} host. In this case, pass
2025 @option{--enable-bootstrap} to the configure script.
2027 @code{BUILD_CONFIG} can be used to bring in additional customization to
2028 the build. It can be set to a whitespace-separated list of names. For
2029 each such @code{NAME}, top-level @file{config/@code{NAME}.mk} will be
2030 included by the top-level @file{Makefile}, bringing in any settings it
2031 contains. Some examples are:
2034 @item @samp{bootstrap-O1}
2035 Removes any @option{-O}-started option from @code{BOOT_CFLAGS}, and adds
2036 @option{-O1} to it. @samp{BUILD_CONFIG=bootstrap-O1} is equivalent to
2037 @samp{BOOT_CFLAGS='-g -O1'}.
2039 @item @samp{bootstrap-O3}
2040 Analogous to @code{bootstrap-O1}.
2042 @item @samp{bootstrap-debug}
2043 Builds stage2 without debug information, and uses
2044 @file{contrib/compare-debug} to compare object files.
2048 @section Building a cross compiler
2050 When building a cross compiler, it is not generally possible to do a
2051 3-stage bootstrap of the compiler. This makes for an interesting problem
2052 as parts of GCC can only be built with GCC@.
2054 To build a cross compiler, we first recommend building and installing a
2055 native compiler. You can then use the native GCC compiler to build the
2056 cross compiler. The installed native compiler needs to be GCC version
2059 If the cross compiler is to be built with support for the Java
2060 programming language and the ability to compile .java source files is
2061 desired, the installed native compiler used to build the cross
2062 compiler needs to be the same GCC version as the cross compiler. In
2063 addition the cross compiler needs to be configured with
2064 @option{--with-ecj-jar=@dots{}}.
2066 Assuming you have already installed a native copy of GCC and configured
2067 your cross compiler, issue the command @command{make}, which performs the
2072 Build host tools necessary to build the compiler.
2075 Build target tools for use by the compiler such as binutils (bfd,
2076 binutils, gas, gprof, ld, and opcodes)
2077 if they have been individually linked or moved into the top level GCC source
2078 tree before configuring.
2081 Build the compiler (single stage only).
2084 Build runtime libraries using the compiler from the previous step.
2087 Note that if an error occurs in any step the make process will exit.
2089 If you are not building GNU binutils in the same source tree as GCC,
2090 you will need a cross-assembler and cross-linker installed before
2091 configuring GCC@. Put them in the directory
2092 @file{@var{prefix}/@var{target}/bin}. Here is a table of the tools
2093 you should put in this directory:
2097 This should be the cross-assembler.
2100 This should be the cross-linker.
2103 This should be the cross-archiver: a program which can manipulate
2104 archive files (linker libraries) in the target machine's format.
2107 This should be a program to construct a symbol table in an archive file.
2110 The installation of GCC will find these programs in that directory,
2111 and copy or link them to the proper place to for the cross-compiler to
2112 find them when run later.
2114 The easiest way to provide these files is to build the Binutils package.
2115 Configure it with the same @option{--host} and @option{--target}
2116 options that you use for configuring GCC, then build and install
2117 them. They install their executables automatically into the proper
2118 directory. Alas, they do not support all the targets that GCC
2121 If you are not building a C library in the same source tree as GCC,
2122 you should also provide the target libraries and headers before
2123 configuring GCC, specifying the directories with
2124 @option{--with-sysroot} or @option{--with-headers} and
2125 @option{--with-libs}. Many targets also require ``start files'' such
2126 as @file{crt0.o} and
2127 @file{crtn.o} which are linked into each executable. There may be several
2128 alternatives for @file{crt0.o}, for use with profiling or other
2129 compilation options. Check your target's definition of
2130 @code{STARTFILE_SPEC} to find out what start files it uses.
2132 @section Building in parallel
2134 GNU Make 3.79 and above, which is necessary to build GCC, support
2135 building in parallel. To activate this, you can use @samp{make -j 2}
2136 instead of @samp{make}. You can also specify a bigger number, and
2137 in most cases using a value greater than the number of processors in
2138 your machine will result in fewer and shorter I/O latency hits, thus
2139 improving overall throughput; this is especially true for slow drives
2140 and network filesystems.
2142 @section Building the Ada compiler
2144 In order to build GNAT, the Ada compiler, you need a working GNAT
2145 compiler (GCC version 3.4 or later).
2146 This includes GNAT tools such as @command{gnatmake} and
2147 @command{gnatlink}, since the Ada front end is written in Ada and
2148 uses some GNAT-specific extensions.
2150 In order to build a cross compiler, it is suggested to install
2151 the new compiler as native first, and then use it to build the cross
2154 @command{configure} does not test whether the GNAT installation works
2155 and has a sufficiently recent version; if too old a GNAT version is
2156 installed, the build will fail unless @option{--enable-languages} is
2157 used to disable building the Ada front end.
2159 @env{ADA_INCLUDE_PATH} and @env{ADA_OBJECT_PATH} environment variables
2160 must not be set when building the Ada compiler, the Ada tools, or the
2161 Ada runtime libraries. You can check that your build environment is clean
2162 by verifying that @samp{gnatls -v} lists only one explicit path in each
2165 @section Building with profile feedback
2167 It is possible to use profile feedback to optimize the compiler itself. This
2168 should result in a faster compiler binary. Experiments done on x86 using gcc
2169 3.3 showed approximately 7 percent speedup on compiling C programs. To
2170 bootstrap the compiler with profile feedback, use @code{make profiledbootstrap}.
2172 When @samp{make profiledbootstrap} is run, it will first build a @code{stage1}
2173 compiler. This compiler is used to build a @code{stageprofile} compiler
2174 instrumented to collect execution counts of instruction and branch
2175 probabilities. Then runtime libraries are compiled with profile collected.
2176 Finally a @code{stagefeedback} compiler is built using the information collected.
2178 Unlike standard bootstrap, several additional restrictions apply. The
2179 compiler used to build @code{stage1} needs to support a 64-bit integral type.
2180 It is recommended to only use GCC for this. Also parallel make is currently
2181 not supported since collisions in profile collecting may occur.
2188 @uref{./index.html,,Return to the GCC Installation page}
2192 @c ***Testing*****************************************************************
2194 @comment node-name, next, previous, up
2195 @node Testing, Final install, Building, Installing GCC
2199 @chapter Installing GCC: Testing
2202 @cindex Installing GCC: Testing
2205 Before you install GCC, we encourage you to run the testsuites and to
2206 compare your results with results from a similar configuration that have
2207 been submitted to the
2208 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
2209 Some of these archived results are linked from the build status lists
2210 at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who
2211 reports a successful build runs the testsuites and submits the results.
2212 This step is optional and may require you to download additional software,
2213 but it can give you confidence in your new GCC installation or point out
2214 problems before you install and start using your new GCC@.
2216 First, you must have @uref{download.html,,downloaded the testsuites}.
2217 These are part of the full distribution, but if you downloaded the
2218 ``core'' compiler plus any front ends, you must download the testsuites
2221 Second, you must have the testing tools installed. This includes
2222 @uref{http://www.gnu.org/software/dejagnu/,,DejaGnu}, Tcl, and Expect;
2223 the DejaGnu site has links to these.
2225 If the directories where @command{runtest} and @command{expect} were
2226 installed are not in the @env{PATH}, you may need to set the following
2227 environment variables appropriately, as in the following example (which
2228 assumes that DejaGnu has been installed under @file{/usr/local}):
2231 TCL_LIBRARY = /usr/local/share/tcl8.0
2232 DEJAGNULIBS = /usr/local/share/dejagnu
2235 (On systems such as Cygwin, these paths are required to be actual
2236 paths, not mounts or links; presumably this is due to some lack of
2237 portability in the DejaGnu code.)
2240 Finally, you can run the testsuite (which may take a long time):
2242 cd @var{objdir}; make -k check
2245 This will test various components of GCC, such as compiler
2246 front ends and runtime libraries. While running the testsuite, DejaGnu
2247 might emit some harmless messages resembling
2248 @samp{WARNING: Couldn't find the global config file.} or
2249 @samp{WARNING: Couldn't find tool init file} that can be ignored.
2251 If you are testing a cross-compiler, you may want to run the testsuite
2252 on a simulator as described at @uref{http://gcc.gnu.org/simtest-howto.html}.
2254 @section How can you run the testsuite on selected tests?
2256 In order to run sets of tests selectively, there are targets
2257 @samp{make check-gcc} and @samp{make check-g++}
2258 in the @file{gcc} subdirectory of the object directory. You can also
2259 just run @samp{make check} in a subdirectory of the object directory.
2262 A more selective way to just run all @command{gcc} execute tests in the
2266 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
2269 Likewise, in order to run only the @command{g++} ``old-deja'' tests in
2270 the testsuite with filenames matching @samp{9805*}, you would use
2273 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
2276 The @file{*.exp} files are located in the testsuite directories of the GCC
2277 source, the most important ones being @file{compile.exp},
2278 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
2279 To get a list of the possible @file{*.exp} files, pipe the
2280 output of @samp{make check} into a file and look at the
2281 @samp{Running @dots{} .exp} lines.
2283 @section Passing options and running multiple testsuites
2285 You can pass multiple options to the testsuite using the
2286 @samp{--target_board} option of DejaGNU, either passed as part of
2287 @samp{RUNTESTFLAGS}, or directly to @command{runtest} if you prefer to
2288 work outside the makefiles. For example,
2291 make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants"
2294 will run the standard @command{g++} testsuites (``unix'' is the target name
2295 for a standard native testsuite situation), passing
2296 @samp{-O3 -fmerge-constants} to the compiler on every test, i.e.,
2297 slashes separate options.
2299 You can run the testsuites multiple times using combinations of options
2300 with a syntax similar to the brace expansion of popular shells:
2303 @dots{}"--target_board=arm-sim\@{-mhard-float,-msoft-float\@}\@{-O1,-O2,-O3,\@}"
2306 (Note the empty option caused by the trailing comma in the final group.)
2307 The following will run each testsuite eight times using the @samp{arm-sim}
2308 target, as if you had specified all possible combinations yourself:
2311 --target_board=arm-sim/-mhard-float/-O1
2312 --target_board=arm-sim/-mhard-float/-O2
2313 --target_board=arm-sim/-mhard-float/-O3
2314 --target_board=arm-sim/-mhard-float
2315 --target_board=arm-sim/-msoft-float/-O1
2316 --target_board=arm-sim/-msoft-float/-O2
2317 --target_board=arm-sim/-msoft-float/-O3
2318 --target_board=arm-sim/-msoft-float
2321 They can be combined as many times as you wish, in arbitrary ways. This
2325 @dots{}"--target_board=unix/-Wextra\@{-O3,-fno-strength\@}\@{-fomit-frame,\@}"
2328 will generate four combinations, all involving @samp{-Wextra}.
2330 The disadvantage to this method is that the testsuites are run in serial,
2331 which is a waste on multiprocessor systems. For users with GNU Make and
2332 a shell which performs brace expansion, you can run the testsuites in
2333 parallel by having the shell perform the combinations and @command{make}
2334 do the parallel runs. Instead of using @samp{--target_board}, use a
2335 special makefile target:
2338 make -j@var{N} check-@var{testsuite}//@var{test-target}/@var{option1}/@var{option2}/@dots{}
2344 make -j3 check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@}
2347 will run three concurrent ``make-gcc'' testsuites, eventually testing all
2348 ten combinations as described above. Note that this is currently only
2349 supported in the @file{gcc} subdirectory. (To see how this works, try
2350 typing @command{echo} before the example given here.)
2353 @section Additional testing for Java Class Libraries
2355 The Java runtime tests can be executed via @samp{make check}
2356 in the @file{@var{target}/libjava/testsuite} directory in
2359 The @uref{http://sourceware.org/mauve/,,Mauve Project} provides
2360 a suite of tests for the Java Class Libraries. This suite can be run
2361 as part of libgcj testing by placing the Mauve tree within the libjava
2362 testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by
2363 specifying the location of that tree when invoking @samp{make}, as in
2364 @samp{make MAUVEDIR=~/mauve check}.
2366 @section How to interpret test results
2368 The result of running the testsuite are various @file{*.sum} and @file{*.log}
2369 files in the testsuite subdirectories. The @file{*.log} files contain a
2370 detailed log of the compiler invocations and the corresponding
2371 results, the @file{*.sum} files summarize the results. These summaries
2372 contain status codes for all tests:
2376 PASS: the test passed as expected
2378 XPASS: the test unexpectedly passed
2380 FAIL: the test unexpectedly failed
2382 XFAIL: the test failed as expected
2384 UNSUPPORTED: the test is not supported on this platform
2386 ERROR: the testsuite detected an error
2388 WARNING: the testsuite detected a possible problem
2391 It is normal for some tests to report unexpected failures. At the
2392 current time the testing harness does not allow fine grained control
2393 over whether or not a test is expected to fail. This problem should
2394 be fixed in future releases.
2397 @section Submitting test results
2399 If you want to report the results to the GCC project, use the
2400 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
2403 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
2404 -m gcc-testresults@@gcc.gnu.org |sh
2407 This script uses the @command{Mail} program to send the results, so
2408 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
2409 prepended to the testsuite summary and should contain any special
2410 remarks you have on your results or your build environment. Please
2411 do not edit the testsuite result block or the subject line, as these
2412 messages may be automatically processed.
2419 @uref{./index.html,,Return to the GCC Installation page}
2423 @c ***Final install***********************************************************
2425 @comment node-name, next, previous, up
2426 @node Final install, , Testing, Installing GCC
2428 @ifset finalinstallhtml
2430 @chapter Installing GCC: Final installation
2433 Now that GCC has been built (and optionally tested), you can install it with
2435 cd @var{objdir}; make install
2438 We strongly recommend to install into a target directory where there is
2439 no previous version of GCC present. Also, the GNAT runtime should not
2440 be stripped, as this would break certain features of the debugger that
2441 depend on this debugging information (catching Ada exceptions for
2444 That step completes the installation of GCC; user level binaries can
2445 be found in @file{@var{prefix}/bin} where @var{prefix} is the value
2446 you specified with the @option{--prefix} to configure (or
2447 @file{/usr/local} by default). (If you specified @option{--bindir},
2448 that directory will be used instead; otherwise, if you specified
2449 @option{--exec-prefix}, @file{@var{exec-prefix}/bin} will be used.)
2450 Headers for the C++ and Java libraries are installed in
2451 @file{@var{prefix}/include}; libraries in @file{@var{libdir}}
2452 (normally @file{@var{prefix}/lib}); internal parts of the compiler in
2453 @file{@var{libdir}/gcc} and @file{@var{libexecdir}/gcc}; documentation
2454 in info format in @file{@var{infodir}} (normally
2455 @file{@var{prefix}/info}).
2457 When installing cross-compilers, GCC's executables
2458 are not only installed into @file{@var{bindir}}, that
2459 is, @file{@var{exec-prefix}/bin}, but additionally into
2460 @file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory
2461 exists. Typically, such @dfn{tooldirs} hold target-specific
2462 binutils, including assembler and linker.
2464 Installation into a temporary staging area or into a @command{chroot}
2465 jail can be achieved with the command
2468 make DESTDIR=@var{path-to-rootdir} install
2471 @noindent where @var{path-to-rootdir} is the absolute path of
2472 a directory relative to which all installation paths will be
2473 interpreted. Note that the directory specified by @code{DESTDIR}
2474 need not exist yet; it will be created if necessary.
2476 There is a subtle point with tooldirs and @code{DESTDIR}:
2477 If you relocate a cross-compiler installation with
2478 e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory
2479 @file{@var{rootdir}/@var{exec-prefix}/@var{target-alias}/bin} will
2480 be filled with duplicated GCC executables only if it already exists,
2481 it will not be created otherwise. This is regarded as a feature,
2482 not as a bug, because it gives slightly more control to the packagers
2483 using the @code{DESTDIR} feature.
2485 If you are bootstrapping a released version of GCC then please
2486 quickly review the build status page for your release, available from
2487 @uref{http://gcc.gnu.org/buildstat.html}.
2488 If your system is not listed for the version of GCC that you built,
2490 @email{gcc@@gcc.gnu.org} indicating
2491 that you successfully built and installed GCC@.
2492 Include the following information:
2496 Output from running @file{@var{srcdir}/config.guess}. Do not send
2497 that file itself, just the one-line output from running it.
2500 The output of @samp{gcc -v} for your newly installed @command{gcc}.
2501 This tells us which version of GCC you built and the options you passed to
2505 Whether you enabled all languages or a subset of them. If you used a
2506 full distribution then this information is part of the configure
2507 options in the output of @samp{gcc -v}, but if you downloaded the
2508 ``core'' compiler plus additional front ends then it isn't apparent
2509 which ones you built unless you tell us about it.
2512 If the build was for GNU/Linux, also include:
2515 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
2516 this information should be available from @file{/etc/issue}.
2519 The version of the Linux kernel, available from @samp{uname --version}
2523 The version of glibc you used; for RPM-based systems like Red Hat,
2524 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
2525 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
2527 For other systems, you can include similar information if you think it is
2531 Any other information that you think would be useful to people building
2532 GCC on the same configuration. The new entry in the build status list
2533 will include a link to the archived copy of your message.
2536 We'd also like to know if the
2538 @ref{Specific, host/target specific installation notes}
2541 @uref{specific.html,,host/target specific installation notes}
2543 didn't include your host/target information or if that information is
2544 incomplete or out of date. Send a note to
2545 @email{gcc@@gcc.gnu.org} detailing how the information should be changed.
2547 If you find a bug, please report it following the
2548 @uref{../bugs.html,,bug reporting guidelines}.
2550 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
2551 dvi}. You will need to have @command{texi2dvi} (version at least 4.7)
2552 and @TeX{} installed. This creates a number of @file{.dvi} files in
2553 subdirectories of @file{@var{objdir}}; these may be converted for
2554 printing with programs such as @command{dvips}. Alternately, by using
2555 @samp{make pdf} in place of @samp{make dvi}, you can create documentation
2556 in the form of @file{.pdf} files; this requires @command{texi2pdf}, which
2557 is included with Texinfo version 4.8 and later. You can also
2558 @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the
2559 Free Software Foundation}, though such manuals may not be for the most
2560 recent version of GCC@.
2562 If you would like to generate online HTML documentation, do @samp{cd
2563 @var{objdir}; make html} and HTML will be generated for the gcc manuals in
2564 @file{@var{objdir}/gcc/HTML}.
2571 @uref{./index.html,,Return to the GCC Installation page}
2575 @c ***Binaries****************************************************************
2577 @comment node-name, next, previous, up
2578 @node Binaries, Specific, Installing GCC, Top
2582 @chapter Installing GCC: Binaries
2585 @cindex Installing GCC: Binaries
2587 We are often asked about pre-compiled versions of GCC@. While we cannot
2588 provide these for all platforms, below you'll find links to binaries for
2589 various platforms where creating them by yourself is not easy due to various
2592 Please note that we did not create these binaries, nor do we
2593 support them. If you have any problems installing them, please
2594 contact their makers.
2601 @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX};
2604 @uref{http://pware.hvcc.edu,,Hudson Valley Community College Open Source Software for IBM System p};
2607 @uref{http://www.perzl.org/aix,,AIX 5L and 6 Open Source Packages}.
2611 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}.
2614 Renesas H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
2615 Development Tools for the Renesas H8/300[HS] Series}.
2621 @uref{http://hpux.cs.utah.edu/,,HP-UX Porting Center};
2624 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
2628 Motorola 68HC11/68HC12---@uref{http://www.gnu-m68hc11.org,,GNU
2629 Development Tools for the Motorola 68HC11/68HC12}.
2632 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
2633 OpenServer/Unixware}.
2636 Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware}.
2639 SGI---@uref{http://freeware.sgi.com/,,SGI Freeware}.
2645 The @uref{http://sourceware.org/cygwin/,,Cygwin} project;
2647 The @uref{http://www.mingw.org/,,MinGW} project.
2651 @uref{ftp://ftp.thewrittenword.com/packages/by-name/,,The
2652 Written Word} offers binaries for
2653 AIX 4.3.3, 5.1 and 5.2,
2655 Tru64 UNIX 4.0D and 5.1,
2657 HP-UX 10.20, 11.00, and 11.11, and
2658 Solaris/SPARC 2.5.1, 2.6, 7, 8, 9 and 10.
2661 @uref{http://www.openpkg.org/,,OpenPKG} offers binaries for quite a
2662 number of platforms.
2665 The @uref{http://gcc.gnu.org/wiki/GFortranBinaries,,GFortran Wiki} has
2666 links to GNU Fortran binaries for several platforms.
2669 In addition to those specific offerings, you can get a binary
2670 distribution CD-ROM from the
2671 @uref{http://www.gnu.org/order/order.html,,Free Software Foundation}.
2672 It contains binaries for a number of platforms, and
2673 includes not only GCC, but other stuff as well. The current CD does
2674 not contain the latest version of GCC, but it should allow
2675 bootstrapping the compiler. An updated version of that disk is in the
2683 @uref{./index.html,,Return to the GCC Installation page}
2687 @c ***Specific****************************************************************
2689 @comment node-name, next, previous, up
2690 @node Specific, Old, Binaries, Top
2694 @chapter Host/target specific installation notes for GCC
2697 @cindex Specific installation notes
2698 @cindex Target specific installation
2699 @cindex Host specific installation
2700 @cindex Target specific installation notes
2702 Please read this document carefully @emph{before} installing the
2703 GNU Compiler Collection on your machine.
2705 Note that this list of install notes is @emph{not} a list of supported
2706 hosts or targets. Not all supported hosts and targets are listed
2707 here, only the ones that require host-specific or target-specific
2713 @uref{#alpha-x-x,,alpha*-*-*}
2715 @uref{#alpha-dec-osf,,alpha*-dec-osf*}
2717 @uref{#arc-x-elf,,arc-*-elf}
2719 @uref{#arm-x-elf,,arm-*-elf}
2723 @uref{#bfin,,Blackfin}
2727 @uref{#x-x-freebsd,,*-*-freebsd*}
2729 @uref{#h8300-hms,,h8300-hms}
2731 @uref{#hppa-hp-hpux,,hppa*-hp-hpux*}
2733 @uref{#hppa-hp-hpux10,,hppa*-hp-hpux10}
2735 @uref{#hppa-hp-hpux11,,hppa*-hp-hpux11}
2737 @uref{#x-x-linux-gnu,,*-*-linux-gnu}
2739 @uref{#ix86-x-linux,,i?86-*-linux*}
2741 @uref{#ix86-x-solaris210,,i?86-*-solaris2.10}
2743 @uref{#ia64-x-linux,,ia64-*-linux}
2745 @uref{#ia64-x-hpux,,ia64-*-hpux*}
2747 @uref{#x-ibm-aix,,*-ibm-aix*}
2749 @uref{#iq2000-x-elf,,iq2000-*-elf}
2751 @uref{#m32c-x-elf,,m32c-*-elf}
2753 @uref{#m32r-x-elf,,m32r-*-elf}
2755 @uref{#m6811-elf,,m6811-elf}
2757 @uref{#m6812-elf,,m6812-elf}
2759 @uref{#m68k-x-x,,m68k-*-*}
2761 @uref{#m68k-uclinux,,m68k-uclinux}
2763 @uref{#mips-x-x,,mips-*-*}
2765 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
2767 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
2769 @uref{#powerpc-x-x,,powerpc*-*-*}
2771 @uref{#powerpc-x-darwin,,powerpc-*-darwin*}
2773 @uref{#powerpc-x-elf,,powerpc-*-elf}
2775 @uref{#powerpc-x-linux-gnu,,powerpc*-*-linux-gnu*}
2777 @uref{#powerpc-x-netbsd,,powerpc-*-netbsd*}
2779 @uref{#powerpc-x-eabisim,,powerpc-*-eabisim}
2781 @uref{#powerpc-x-eabi,,powerpc-*-eabi}
2783 @uref{#powerpcle-x-elf,,powerpcle-*-elf}
2785 @uref{#powerpcle-x-eabisim,,powerpcle-*-eabisim}
2787 @uref{#powerpcle-x-eabi,,powerpcle-*-eabi}
2789 @uref{#s390-x-linux,,s390-*-linux*}
2791 @uref{#s390x-x-linux,,s390x-*-linux*}
2793 @uref{#s390x-ibm-tpf,,s390x-ibm-tpf*}
2795 @uref{#x-x-solaris2,,*-*-solaris2*}
2797 @uref{#sparc-sun-solaris2,,sparc-sun-solaris2*}
2799 @uref{#sparc-sun-solaris27,,sparc-sun-solaris2.7}
2801 @uref{#sparc-x-linux,,sparc-*-linux*}
2803 @uref{#sparc64-x-solaris2,,sparc64-*-solaris2*}
2805 @uref{#sparcv9-x-solaris2,,sparcv9-*-solaris2*}
2807 @uref{#x-x-vxworks,,*-*-vxworks*}
2809 @uref{#x86-64-x-x,,x86_64-*-*, amd64-*-*}
2811 @uref{#xtensa-x-elf,,xtensa*-*-elf}
2813 @uref{#xtensa-x-linux,,xtensa*-*-linux*}
2815 @uref{#windows,,Microsoft Windows}
2817 @uref{#x-x-cygwin,,*-*-cygwin}
2819 @uref{#x-x-interix,,*-*-interix}
2821 @uref{#x-x-mingw32,,*-*-mingw32}
2825 @uref{#older,,Older systems}
2830 @uref{#elf,,all ELF targets} (SVR4, Solaris 2, etc.)
2836 <!-- -------- host/target specific issues start here ---------------- -->
2839 @heading @anchor{alpha-x-x}alpha*-*-*
2841 This section contains general configuration information for all
2842 alpha-based platforms using ELF (in particular, ignore this section for
2843 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
2844 section, please read all other sections that match your target.
2846 We require binutils 2.11.2 or newer.
2847 Previous binutils releases had a number of problems with DWARF 2
2848 debugging information, not the least of which is incorrect linking of
2854 @heading @anchor{alpha-dec-osf}alpha*-dec-osf*
2855 Systems using processors that implement the DEC Alpha architecture and
2856 are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
2857 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
2859 As of GCC 3.2, versions before @code{alpha*-dec-osf4} are no longer
2860 supported. (These are the versions which identify themselves as DEC
2863 In Digital Unix V4.0, virtual memory exhausted bootstrap failures
2864 may be fixed by configuring with @option{--with-gc=simple},
2865 reconfiguring Kernel Virtual Memory and Swap parameters
2866 per the @command{/usr/sbin/sys_check} Tuning Suggestions,
2867 or applying the patch in
2868 @uref{http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html}.
2870 In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
2871 currently (2001-06-13) work with @command{mips-tfile}. As a workaround,
2872 we need to use the old assembler, invoked via the barely documented
2873 @option{-oldas} option. To bootstrap GCC, you either need to use the
2877 % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
2880 or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
2883 % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
2886 As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld}
2887 are supported on Tru64 UNIX, so you must not configure GCC with
2888 @option{--with-gnu-as} or @option{--with-gnu-ld}.
2890 GCC writes a @samp{.verstamp} directive to the assembler output file
2891 unless it is built as a cross-compiler. It gets the version to use from
2892 the system header file @file{/usr/include/stamp.h}. If you install a
2893 new version of DEC Unix, you should rebuild GCC to pick up the new version
2896 @samp{make compare} may fail on old versions of DEC Unix unless you add
2897 @option{-save-temps} to @code{BOOT_CFLAGS}. On these systems, the name
2898 of the assembler input file is stored in the object file, and that makes
2899 comparison fail if it differs between the @code{stage1} and
2900 @code{stage2} compilations. The option @option{-save-temps} forces a
2901 fixed name to be used for the assembler input file, instead of a
2902 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
2903 unless the comparisons fail without that option. If you add
2904 @option{-save-temps}, you will have to manually delete the @samp{.i} and
2905 @samp{.s} files after each series of compilations.
2907 GCC now supports both the native (ECOFF) debugging format used by DBX
2908 and GDB and an encapsulated STABS format for use only with GDB@. See the
2909 discussion of the @option{--with-stabs} option of @file{configure} above
2910 for more information on these formats and how to select them.
2912 There is a bug in DEC's assembler that produces incorrect line numbers
2913 for ECOFF format when the @samp{.align} directive is used. To work
2914 around this problem, GCC will not emit such alignment directives
2915 while writing ECOFF format debugging information even if optimization is
2916 being performed. Unfortunately, this has the very undesirable
2917 side-effect that code addresses when @option{-O} is specified are
2918 different depending on whether or not @option{-g} is also specified.
2920 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
2921 DBX@. DEC is now aware of this problem with the assembler and hopes to
2922 provide a fix shortly.
2927 @heading @anchor{arc-x-elf}arc-*-elf
2928 Argonaut ARC processor.
2929 This configuration is intended for embedded systems.
2934 @heading @anchor{arm-x-elf}arm-*-elf
2935 ARM-family processors. Subtargets that use the ELF object format
2936 require GNU binutils 2.13 or newer. Such subtargets include:
2937 @code{arm-*-freebsd}, @code{arm-*-netbsdelf}, @code{arm-*-*linux}
2938 and @code{arm-*-rtems}.
2943 @heading @anchor{avr}avr
2945 ATMEL AVR-family micro controllers. These are used in embedded
2946 applications. There are no standard Unix configurations.
2948 @xref{AVR Options,, AVR Options, gcc, Using the GNU Compiler
2952 See ``AVR Options'' in the main manual
2954 for the list of supported MCU types.
2956 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
2958 Further installation notes and other useful information about AVR tools
2959 can also be obtained from:
2963 @uref{http://www.nongnu.org/avr/,,http://www.nongnu.org/avr/}
2965 @uref{http://home.overta.ru/users/denisc/,,http://home.overta.ru/users/denisc/}
2967 @uref{http://www.amelek.gda.pl/avr/,,http://www.amelek.gda.pl/avr/}
2970 We @emph{strongly} recommend using binutils 2.13 or newer.
2972 The following error:
2974 Error: register required
2977 indicates that you should upgrade to a newer version of the binutils.
2982 @heading @anchor{bfin}Blackfin
2984 The Blackfin processor, an Analog Devices DSP.
2986 @xref{Blackfin Options,, Blackfin Options, gcc, Using the GNU Compiler
2990 See ``Blackfin Options'' in the main manual
2993 More information, and a version of binutils with support for this processor,
2994 is available at @uref{http://blackfin.uclinux.org}
2999 @heading @anchor{cris}CRIS
3001 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
3002 series. These are used in embedded applications.
3005 @xref{CRIS Options,, CRIS Options, gcc, Using the GNU Compiler
3009 See ``CRIS Options'' in the main manual
3011 for a list of CRIS-specific options.
3013 There are a few different CRIS targets:
3016 Mainly for monolithic embedded systems. Includes a multilib for the
3017 @samp{v10} core used in @samp{ETRAX 100 LX}.
3018 @item cris-axis-linux-gnu
3019 A GNU/Linux port for the CRIS architecture, currently targeting
3020 @samp{ETRAX 100 LX} by default.
3023 For @code{cris-axis-elf} you need binutils 2.11
3024 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
3026 Pre-packaged tools can be obtained from
3027 @uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More
3028 information about this platform is available at
3029 @uref{http://developer.axis.com/}.
3034 @heading @anchor{crx}CRX
3036 The CRX CompactRISC architecture is a low-power 32-bit architecture with
3037 fast context switching and architectural extensibility features.
3040 @xref{CRX Options,, CRX Options, gcc, Using and Porting the GNU Compiler
3045 See ``CRX Options'' in the main manual for a list of CRX-specific options.
3048 Use @samp{configure --target=crx-elf --enable-languages=c,c++} to configure
3049 GCC@ for building a CRX cross-compiler. The option @samp{--target=crx-elf}
3050 is also used to build the @samp{newlib} C library for CRX.
3052 It is also possible to build libstdc++-v3 for the CRX architecture. This
3053 needs to be done in a separate step with the following configure settings:
3054 @samp{gcc/libstdc++-v3/configure --host=crx-elf --with-newlib
3055 --enable-sjlj-exceptions --enable-cxx-flags='-fexceptions -frtti'}
3060 @heading @anchor{dos}DOS
3062 Please have a look at the @uref{binaries.html,,binaries page}.
3064 You cannot install GCC by itself on MSDOS; it will not compile under
3065 any MSDOS compiler except itself. You need to get the complete
3066 compilation package DJGPP, which includes binaries as well as sources,
3067 and includes all the necessary compilation tools and libraries.
3072 @heading @anchor{x-x-freebsd}*-*-freebsd*
3074 The version of binutils installed in @file{/usr/bin} probably works with
3075 this release of GCC@. However, on FreeBSD 4, bootstrapping against the
3076 latest FSF binutils is known to improve overall testsuite results; and,
3077 on FreeBSD/alpha, using binutils 2.14 or later is required to build libjava.
3079 Support for FreeBSD 1 was discontinued in GCC 3.2.
3081 Support for FreeBSD 2 will be discontinued after GCC 3.4. The
3082 following was true for GCC 3.1 but the current status is unknown.
3083 For FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
3084 configuration support and files as shipped with GCC 2.95 are still in
3085 place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
3086 it is unknown which version of binutils was used (it is assumed that it
3087 was the system copy in @file{/usr/bin}) and C++ EH failures were noted.
3089 For FreeBSD using the ELF file format: DWARF 2 debugging is now the
3090 default for all CPU architectures. It had been the default on
3091 FreeBSD/alpha since its inception. You may use @option{-gstabs} instead
3092 of @option{-g}, if you really want the old debugging format. There are
3093 no known issues with mixing object files and libraries with different
3094 debugging formats. Otherwise, this release of GCC should now match more
3095 of the configuration used in the stock FreeBSD configuration of GCC@. In
3096 particular, @option{--enable-threads} is now configured by default.
3097 However, as a general user, do not attempt to replace the system
3098 compiler with this release. Known to bootstrap and check with good
3099 results on FreeBSD 4.9-STABLE and 5-CURRENT@. In the past, known to
3100 bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2,
3101 4.3, 4.4, 4.5, 4.8-STABLE@.
3103 In principle, @option{--enable-threads} is now compatible with
3104 @option{--enable-libgcj} on FreeBSD@. However, it has only been built
3105 and tested on @samp{i386-*-freebsd[45]} and @samp{alpha-*-freebsd[45]}.
3107 library may be incorrectly built (symbols are missing at link time).
3108 There is a rare timing-based startup hang (probably involves an
3109 assumption about the thread library). Multi-threaded boehm-gc (required for
3110 libjava) exposes severe threaded signal-handling bugs on FreeBSD before
3111 4.5-RELEASE@. Other CPU architectures
3112 supported by FreeBSD will require additional configuration tuning in, at
3113 the very least, both boehm-gc and libffi.
3115 Shared @file{libgcc_s.so} is now built and installed by default.
3120 @heading @anchor{h8300-hms}h8300-hms
3121 Renesas H8/300 series of processors.
3123 Please have a look at the @uref{binaries.html,,binaries page}.
3125 The calling convention and structure layout has changed in release 2.6.
3126 All code must be recompiled. The calling convention now passes the
3127 first three arguments in function calls in registers. Structures are no
3128 longer a multiple of 2 bytes.
3133 @heading @anchor{hppa-hp-hpux}hppa*-hp-hpux*
3134 Support for HP-UX version 9 and older was discontinued in GCC 3.4.
3136 We require using gas/binutils on all hppa platforms. Version 2.19 or
3137 later is recommended.
3139 It may be helpful to configure GCC with the
3140 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
3141 @option{--with-as=@dots{}} options to ensure that GCC can find GAS@.
3143 The HP assembler should not be used with GCC. It is rarely tested and may
3144 not work. It shouldn't be used with any languages other than C due to its
3147 Specifically, @option{-g} does not work (HP-UX uses a peculiar debugging
3148 format which GCC does not know about). It also inserts timestamps
3149 into each object file it creates, causing the 3-stage comparison test to
3150 fail during a bootstrap. You should be able to continue by saying
3151 @samp{make all-host all-target} after getting the failure from @samp{make}.
3153 Various GCC features are not supported. For example, it does not support weak
3154 symbols or alias definitions. As a result, explicit template instantiations
3155 are required when using C++. This makes it difficult if not impossible to
3156 build many C++ applications.
3158 There are two default scheduling models for instructions. These are
3159 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
3160 architecture specified for the target machine when configuring.
3161 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
3162 the target is a @samp{hppa1*} machine.
3164 The PROCESSOR_8000 model is not well suited to older processors. Thus,
3165 it is important to completely specify the machine architecture when
3166 configuring if you want a model other than PROCESSOR_8000. The macro
3167 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
3168 default scheduling model is desired.
3170 As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
3171 through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
3172 This namespace change might cause problems when bootstrapping with
3173 an earlier version of GCC or the HP compiler as essentially the same
3174 namespace is required for an entire build. This problem can be avoided
3175 in a number of ways. With HP cc, @env{UNIX_STD} can be set to @samp{95}
3176 or @samp{98}. Another way is to add an appropriate set of predefines
3177 to @env{CC}. The description for the @option{munix=} option contains
3178 a list of the predefines used with each standard.
3180 More specific information to @samp{hppa*-hp-hpux*} targets follows.
3185 @heading @anchor{hppa-hp-hpux10}hppa*-hp-hpux10
3187 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
3188 @code{PHCO_19798} from HP@. HP has two sites which provide patches free of
3194 <a href="http://us.itrc.hp.com/service/home/home.do">US, Canada, Asia-Pacific, and
3198 @uref{http://us.itrc.hp.com/service/home/home.do,,} US, Canada, Asia-Pacific,
3202 @uref{http://europe.itrc.hp.com/service/home/home.do,,} Europe.
3205 The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are
3206 used for one-only code and data. This resolves many of the previous
3207 problems in using C++ on this target. However, the ABI is not compatible
3208 with the one implemented under HP-UX 11 using secondary definitions.
3213 @heading @anchor{hppa-hp-hpux11}hppa*-hp-hpux11
3215 GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
3216 be used to compile GCC 3.0 and up.
3218 The libffi and libjava libraries haven't been ported to 64-bit HP-UX@
3221 Refer to @uref{binaries.html,,binaries} for information about obtaining
3222 precompiled GCC binaries for HP-UX@. Precompiled binaries must be obtained
3223 to build the Ada language as it can't be bootstrapped using C@. Ada is
3224 only available for the 32-bit PA-RISC runtime.
3226 Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The
3227 bundled compiler supports only traditional C; you will need either HP's
3228 unbundled compiler, or a binary distribution of GCC@.
3230 It is possible to build GCC 3.3 starting with the bundled HP compiler,
3231 but the process requires several steps. GCC 3.3 can then be used to
3232 build later versions. The fastjar program contains ISO C code and
3233 can't be built with the HP bundled compiler. This problem can be
3234 avoided by not building the Java language. For example, use the
3235 @option{--enable-languages="c,c++,f77,objc"} option in your configure
3238 There are several possible approaches to building the distribution.
3239 Binutils can be built first using the HP tools. Then, the GCC
3240 distribution can be built. The second approach is to build GCC
3241 first using the HP tools, then build binutils, then rebuild GCC@.
3242 There have been problems with various binary distributions, so it
3243 is best not to start from a binary distribution.
3245 On 64-bit capable systems, there are two distinct targets. Different
3246 installation prefixes must be used if both are to be installed on
3247 the same system. The @samp{hppa[1-2]*-hp-hpux11*} target generates code
3248 for the 32-bit PA-RISC runtime architecture and uses the HP linker.
3249 The @samp{hppa64-hp-hpux11*} target generates 64-bit code for the
3250 PA-RISC 2.0 architecture.
3252 The script config.guess now selects the target type based on the compiler
3253 detected during configuration. You must define @env{PATH} or @env{CC} so
3254 that configure finds an appropriate compiler for the initial bootstrap.
3255 When @env{CC} is used, the definition should contain the options that are
3256 needed whenever @env{CC} is used.
3258 Specifically, options that determine the runtime architecture must be
3259 in @env{CC} to correctly select the target for the build. It is also
3260 convenient to place many other compiler options in @env{CC}. For example,
3261 @env{CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"}
3262 can be used to bootstrap the GCC 3.3 branch with the HP compiler in
3263 64-bit K&R/bundled mode. The @option{+DA2.0W} option will result in
3264 the automatic selection of the @samp{hppa64-hp-hpux11*} target. The
3265 macro definition table of cpp needs to be increased for a successful
3266 build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to
3267 be defined when building with the bundled compiler, or when using the
3268 @option{-Ac} option. These defines aren't necessary with @option{-Ae}.
3270 It is best to explicitly configure the @samp{hppa64-hp-hpux11*} target
3271 with the @option{--with-ld=@dots{}} option. This overrides the standard
3272 search for ld. The two linkers supported on this target require different
3273 commands. The default linker is determined during configuration. As a
3274 result, it's not possible to switch linkers in the middle of a GCC build.
3275 This has been reported to sometimes occur in unified builds of binutils
3278 A recent linker patch must be installed for the correct operation of
3279 GCC 3.3 and later. @code{PHSS_26559} and @code{PHSS_24304} are the
3280 oldest linker patches that are known to work. They are for HP-UX
3281 11.00 and 11.11, respectively. @code{PHSS_24303}, the companion to
3282 @code{PHSS_24304}, might be usable but it hasn't been tested. These
3283 patches have been superseded. Consult the HP patch database to obtain
3284 the currently recommended linker patch for your system.
3286 The patches are necessary for the support of weak symbols on the
3287 32-bit port, and for the running of initializers and finalizers. Weak
3288 symbols are implemented using SOM secondary definition symbols. Prior
3289 to HP-UX 11, there are bugs in the linker support for secondary symbols.
3290 The patches correct a problem of linker core dumps creating shared
3291 libraries containing secondary symbols, as well as various other
3292 linking issues involving secondary symbols.
3294 GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
3295 run initializers and finalizers on the 64-bit port. The 32-bit port
3296 uses the linker @option{+init} and @option{+fini} options for the same
3297 purpose. The patches correct various problems with the +init/+fini
3298 options, including program core dumps. Binutils 2.14 corrects a
3299 problem on the 64-bit port resulting from HP's non-standard use of
3300 the .init and .fini sections for array initializers and finalizers.
3302 Although the HP and GNU linkers are both supported for the
3303 @samp{hppa64-hp-hpux11*} target, it is strongly recommended that the
3304 HP linker be used for link editing on this target.
3306 At this time, the GNU linker does not support the creation of long
3307 branch stubs. As a result, it can't successfully link binaries
3308 containing branch offsets larger than 8 megabytes. In addition,
3309 there are problems linking shared libraries, linking executables
3310 with @option{-static}, and with dwarf2 unwind and exception support.
3311 It also doesn't provide stubs for internal calls to global functions
3312 in shared libraries, so these calls can't be overloaded.
3314 The HP dynamic loader does not support GNU symbol versioning, so symbol
3315 versioning is not supported. It may be necessary to disable symbol
3316 versioning with @option{--disable-symvers} when using GNU ld.
3318 POSIX threads are the default. The optional DCE thread library is not
3319 supported, so @option{--enable-threads=dce} does not work.
3324 @heading @anchor{x-x-linux-gnu}*-*-linux-gnu
3326 Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present
3327 in glibc 2.2.5 and later. More information is available in the
3328 libstdc++-v3 documentation.
3333 @heading @anchor{ix86-x-linux}i?86-*-linux*
3335 As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
3336 See @uref{http://gcc.gnu.org/PR10877,,bug 10877} for more information.
3338 If you receive Signal 11 errors when building on GNU/Linux, then it is
3339 possible you have a hardware problem. Further information on this can be
3340 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
3345 @heading @anchor{ix86-x-solaris210}i?86-*-solaris2.10
3346 Use this for Solaris 10 or later on x86 and x86-64 systems. This
3347 configuration is supported by GCC 4.0 and later versions only.
3349 It is recommended that you configure GCC to use the GNU assembler in
3350 @file{/usr/sfw/bin/gas} but the Sun linker, using the options
3351 @option{--with-gnu-as --with-as=/usr/sfw/bin/gas --without-gnu-ld
3352 --with-ld=/usr/ccs/bin/ld}.
3357 @heading @anchor{ia64-x-linux}ia64-*-linux
3358 IA-64 processor (also known as IPF, or Itanium Processor Family)
3361 If you are using the installed system libunwind library with
3362 @option{--with-system-libunwind}, then you must use libunwind 0.98 or
3365 None of the following versions of GCC has an ABI that is compatible
3366 with any of the other versions in this list, with the exception that
3367 Red Hat 2.96 and Trillian 000171 are compatible with each other:
3368 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
3369 This primarily affects C++ programs and programs that create shared libraries.
3370 GCC 3.1 or later is recommended for compiling linux, the kernel.
3371 As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
3372 more major ABI changes are expected.
3377 @heading @anchor{ia64-x-hpux}ia64-*-hpux*
3378 Building GCC on this target requires the GNU Assembler. The bundled HP
3379 assembler will not work. To prevent GCC from using the wrong assembler,
3380 the option @option{--with-gnu-as} may be necessary.
3382 The GCC libunwind library has not been ported to HPUX@. This means that for
3383 GCC versions 3.2.3 and earlier, @option{--enable-libunwind-exceptions}
3384 is required to build GCC@. For GCC 3.3 and later, this is the default.
3385 For gcc 3.4.3 and later, @option{--enable-libunwind-exceptions} is
3386 removed and the system libunwind library will always be used.
3390 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
3392 @heading @anchor{x-ibm-aix}*-ibm-aix*
3393 Support for AIX version 3 and older was discontinued in GCC 3.4.
3394 Support for AIX version 4.2 and older was discontinued in GCC 4.5.
3396 ``out of memory'' bootstrap failures may indicate a problem with
3397 process resource limits (ulimit). Hard limits are configured in the
3398 @file{/etc/security/limits} system configuration file.
3400 To speed up the configuration phases of bootstrapping and installing GCC,
3401 one may use GNU Bash instead of AIX @command{/bin/sh}, e.g.,
3404 % CONFIG_SHELL=/opt/freeware/bin/bash
3405 % export CONFIG_SHELL
3408 and then proceed as described in @uref{build.html,,the build
3409 instructions}, where we strongly recommend specifying an absolute path
3410 to invoke @var{srcdir}/configure.
3412 Because GCC on AIX is built as a 32-bit executable by default,
3413 (although it can generate 64-bit programs) the GMP and MPFR libraries
3414 required by gfortran must be 32-bit libraries. Building GMP and MPFR
3415 as static archive libraries works better than shared libraries.
3417 Errors involving @code{alloca} when building GCC generally are due
3418 to an incorrect definition of @code{CC} in the Makefile or mixing files
3419 compiled with the native C compiler and GCC@. During the stage1 phase of
3420 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
3421 (not @command{xlc}). Once @command{configure} has been informed of
3422 @command{xlc}, one needs to use @samp{make distclean} to remove the
3423 configure cache files and ensure that @env{CC} environment variable
3424 does not provide a definition that will confuse @command{configure}.
3425 If this error occurs during stage2 or later, then the problem most likely
3426 is the version of Make (see above).
3428 The native @command{as} and @command{ld} are recommended for bootstrapping
3429 on AIX 4 and required for bootstrapping on AIX 5L@. The GNU Assembler
3430 reports that it supports WEAK symbols on AIX 4, which causes GCC to try to
3431 utilize weak symbol functionality although it is not supported. The GNU
3432 Assembler and Linker do not support AIX 5L sufficiently to bootstrap GCC@.
3433 The native AIX tools do interoperate with GCC@.
3435 Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
3436 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
3437 fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
3438 referenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1)
3440 @samp{libstdc++} in GCC 3.4 increments the major version number of the
3441 shared object and GCC installation places the @file{libstdc++.a}
3442 shared library in a common location which will overwrite the and GCC
3443 3.3 version of the shared library. Applications either need to be
3444 re-linked against the new shared library or the GCC 3.1 and GCC 3.3
3445 versions of the @samp{libstdc++} shared object needs to be available
3446 to the AIX runtime loader. The GCC 3.1 @samp{libstdc++.so.4}, if
3447 present, and GCC 3.3 @samp{libstdc++.so.5} shared objects can be
3448 installed for runtime dynamic loading using the following steps to set
3449 the @samp{F_LOADONLY} flag in the shared object for @emph{each}
3450 multilib @file{libstdc++.a} installed:
3452 Extract the shared objects from the currently installed
3453 @file{libstdc++.a} archive:
3455 % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
3458 Enable the @samp{F_LOADONLY} flag so that the shared object will be
3459 available for runtime dynamic loading, but not linking:
3461 % strip -e libstdc++.so.4 libstdc++.so.5
3464 Archive the runtime-only shared object in the GCC 3.4
3465 @file{libstdc++.a} archive:
3467 % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
3470 Linking executables and shared libraries may produce warnings of
3471 duplicate symbols. The assembly files generated by GCC for AIX always
3472 have included multiple symbol definitions for certain global variable
3473 and function declarations in the original program. The warnings should
3474 not prevent the linker from producing a correct library or runnable
3477 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
3478 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
3479 to parse archive libraries did not handle the new format correctly.
3480 These routines are used by GCC and result in error messages during
3481 linking such as ``not a COFF file''. The version of the routines shipped
3482 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
3483 option of the archive command may be used to create archives of 32-bit
3484 objects using the original ``small format''. A correct version of the
3485 routines is shipped with AIX 4.3.2 and above.
3487 Some versions of the AIX binder (linker) can fail with a relocation
3488 overflow severe error when the @option{-bbigtoc} option is used to link
3489 GCC-produced object files into an executable that overflows the TOC@. A fix
3490 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
3491 available from IBM Customer Support and from its
3492 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3493 website as PTF U455193.
3495 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
3496 with a segmentation fault when invoked by any version of GCC@. A fix for
3497 APAR IX87327 is available from IBM Customer Support and from its
3498 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3499 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
3501 The initial assembler shipped with AIX 4.3.0 generates incorrect object
3502 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
3503 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
3504 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3505 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
3507 AIX provides National Language Support (NLS)@. Compilers and assemblers
3508 use NLS to support locale-specific representations of various data
3509 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
3510 separating decimal fractions). There have been problems reported where
3511 GCC does not produce the same floating-point formats that the assembler
3512 expects. If one encounters this problem, set the @env{LANG}
3513 environment variable to @samp{C} or @samp{En_US}.
3515 A default can be specified with the @option{-mcpu=@var{cpu_type}}
3516 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
3521 @heading @anchor{iq2000-x-elf}iq2000-*-elf
3522 Vitesse IQ2000 processors. These are used in embedded
3523 applications. There are no standard Unix configurations.
3528 @heading @anchor{m32c-x-elf}m32c-*-elf
3529 Renesas M32C processor.
3530 This configuration is intended for embedded systems.
3535 @heading @anchor{m32r-x-elf}m32r-*-elf
3536 Renesas M32R processor.
3537 This configuration is intended for embedded systems.
3542 @heading @anchor{m6811-elf}m6811-elf
3543 Motorola 68HC11 family micro controllers. These are used in embedded
3544 applications. There are no standard Unix configurations.
3549 @heading @anchor{m6812-elf}m6812-elf
3550 Motorola 68HC12 family micro controllers. These are used in embedded
3551 applications. There are no standard Unix configurations.
3556 @heading @anchor{m68k-x-x}m68k-*-*
3558 @samp{m68k-*-elf*}, @samp{m68k-*-rtems}, @samp{m68k-*-uclinux} and
3560 build libraries for both M680x0 and ColdFire processors. If you only
3561 need the M680x0 libraries, you can omit the ColdFire ones by passing
3562 @option{--with-arch=m68k} to @command{configure}. Alternatively, you
3563 can omit the M680x0 libraries by passing @option{--with-arch=cf} to
3564 @command{configure}. These targets default to 5206 or 5475 code as
3565 appropriate for the target system when
3566 configured with @option{--with-arch=cf} and 68020 code otherwise.
3568 The @samp{m68k-*-netbsd} and
3569 @samp{m68k-*-openbsd} targets also support the @option{--with-arch}
3570 option. They will generate ColdFire CFV4e code when configured with
3571 @option{--with-arch=cf} and 68020 code otherwise.
3573 You can override the default processors listed above by configuring
3574 with @option{--with-cpu=@var{target}}. This @var{target} can either
3575 be a @option{-mcpu} argument or one of the following values:
3576 @samp{m68000}, @samp{m68010}, @samp{m68020}, @samp{m68030},
3577 @samp{m68040}, @samp{m68060}, @samp{m68020-40} and @samp{m68020-60}.
3582 @heading @anchor{m68k-x-uclinux}m68k-*-uclinux
3583 GCC 4.3 changed the uClinux configuration so that it uses the
3584 @samp{m68k-linux-gnu} ABI rather than the @samp{m68k-elf} ABI.
3585 It also added improved support for C++ and flat shared libraries,
3586 both of which were ABI changes. However, you can still use the
3587 original ABI by configuring for @samp{m68k-uclinuxoldabi} or
3588 @samp{m68k-@var{vendor}-uclinuxoldabi}.
3593 @heading @anchor{mips-x-x}mips-*-*
3594 If on a MIPS system you get an error message saying ``does not have gp
3595 sections for all it's [sic] sectons [sic]'', don't worry about it. This
3596 happens whenever you use GAS with the MIPS linker, but there is not
3597 really anything wrong, and it is okay to use the output file. You can
3598 stop such warnings by installing the GNU linker.
3600 It would be nice to extend GAS to produce the gp tables, but they are
3601 optional, and there should not be a warning about their absence.
3603 The libstdc++ atomic locking routines for MIPS targets requires MIPS II
3604 and later. A patch went in just after the GCC 3.3 release to
3605 make @samp{mips*-*-*} use the generic implementation instead. You can also
3606 configure for @samp{mipsel-elf} as a workaround. The
3607 @samp{mips*-*-linux*} target continues to use the MIPS II routines. More
3608 work on this is expected in future releases.
3610 @c If you make --with-llsc the default for another target, please also
3611 @c update the description of the --with-llsc option.
3613 The built-in @code{__sync_*} functions are available on MIPS II and
3614 later systems and others that support the @samp{ll}, @samp{sc} and
3615 @samp{sync} instructions. This can be overridden by passing
3616 @option{--with-llsc} or @option{--without-llsc} when configuring GCC.
3617 Since the Linux kernel emulates these instructions if they are
3618 missing, the default for @samp{mips*-*-linux*} targets is
3619 @option{--with-llsc}. The @option{--with-llsc} and
3620 @option{--without-llsc} configure options may be overridden at compile
3621 time by passing the @option{-mllsc} or @option{-mno-llsc} options to
3624 MIPS systems check for division by zero (unless
3625 @option{-mno-check-zero-division} is passed to the compiler) by
3626 generating either a conditional trap or a break instruction. Using
3627 trap results in smaller code, but is only supported on MIPS II and
3628 later. Also, some versions of the Linux kernel have a bug that
3629 prevents trap from generating the proper signal (@code{SIGFPE}). To enable
3630 the use of break, use the @option{--with-divide=breaks}
3631 @command{configure} option when configuring GCC@. The default is to
3632 use traps on systems that support them.
3634 Cross-compilers for the MIPS as target using the MIPS assembler
3635 currently do not work, because the auxiliary programs
3636 @file{mips-tdump.c} and @file{mips-tfile.c} can't be compiled on
3637 anything but a MIPS@. It does work to cross compile for a MIPS
3638 if you use the GNU assembler and linker.
3640 The assembler from GNU binutils 2.17 and earlier has a bug in the way
3641 it sorts relocations for REL targets (o32, o64, EABI). This can cause
3642 bad code to be generated for simple C++ programs. Also the linker
3643 from GNU binutils versions prior to 2.17 has a bug which causes the
3644 runtime linker stubs in very large programs, like @file{libgcj.so}, to
3645 be incorrectly generated. GNU Binutils 2.18 and later (and snapshots
3646 made after Nov. 9, 2006) should be free from both of these problems.
3651 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
3653 In order to compile GCC on an SGI running IRIX 5, the @samp{compiler_dev.hdr}
3654 subsystem must be installed from the IDO CD-ROM supplied by SGI@.
3655 It is also available for download from
3656 @uref{ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist}.
3658 If you use the MIPS C compiler to bootstrap, it may be necessary
3659 to increase its table size for switch statements with the
3660 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
3661 optimization option, you also need to use @option{-Olimit 3000}.
3663 To enable debugging under IRIX 5, you must use GNU binutils 2.15 or
3664 later, and use the @option{--with-gnu-ld} @command{configure} option
3665 when configuring GCC@. You need to use GNU @command{ar} and @command{nm},
3666 also distributed with GNU binutils.
3668 Some users have reported that @command{/bin/sh} will hang during bootstrap.
3669 This problem can be avoided by running the commands:
3672 % CONFIG_SHELL=/bin/ksh
3673 % export CONFIG_SHELL
3676 before starting the build.
3681 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
3683 If you are using SGI's MIPSpro @command{cc} as your bootstrap compiler, you must
3684 ensure that the N32 ABI is in use. To test this, compile a simple C
3685 file with @command{cc} and then run @command{file} on the
3686 resulting object file. The output should look like:
3689 test.o: ELF N32 MSB @dots{}
3695 test.o: ELF 32-bit MSB @dots{}
3701 test.o: ELF 64-bit MSB @dots{}
3704 then your version of @command{cc} uses the O32 or N64 ABI by default. You
3705 should set the environment variable @env{CC} to @samp{cc -n32}
3706 before configuring GCC@.
3708 If you want the resulting @command{gcc} to run on old 32-bit systems
3709 with the MIPS R4400 CPU, you need to ensure that only code for the @samp{mips3}
3710 instruction set architecture (ISA) is generated. While GCC 3.x does
3711 this correctly, both GCC 2.95 and SGI's MIPSpro @command{cc} may change
3712 the ISA depending on the machine where GCC is built. Using one of them
3713 as the bootstrap compiler may result in @samp{mips4} code, which won't run at
3714 all on @samp{mips3}-only systems. For the test program above, you should see:
3717 test.o: ELF N32 MSB mips-3 @dots{}
3723 test.o: ELF N32 MSB mips-4 @dots{}
3726 instead, you should set the environment variable @env{CC} to @samp{cc
3727 -n32 -mips3} or @samp{gcc -mips3} respectively before configuring GCC@.
3729 MIPSpro C 7.4 may cause bootstrap failures, due to a bug when inlining
3730 @code{memcmp}. Either add @code{-U__INLINE_INTRINSICS} to the @env{CC}
3731 environment variable as a workaround or upgrade to MIPSpro C 7.4.1m.
3733 GCC on IRIX 6 is usually built to support the N32, O32 and N64 ABIs. If
3734 you build GCC on a system that doesn't have the N64 libraries installed
3735 or cannot run 64-bit binaries,
3736 you need to configure with @option{--disable-multilib} so GCC doesn't
3737 try to use them. This will disable building the O32 libraries, too.
3738 Look for @file{/usr/lib64/libc.so.1} to see if you
3739 have the 64-bit libraries installed.
3741 To enable debugging for the O32 ABI, you must use GNU @command{as} from
3742 GNU binutils 2.15 or later. You may also use GNU @command{ld}, but
3743 this is not required and currently causes some problems with Ada.
3745 The @option{--enable-libgcj}
3746 option is disabled by default: IRIX 6 uses a very low default limit
3747 (20480) for the command line length. Although @command{libtool} contains a
3748 workaround for this problem, at least the N64 @samp{libgcj} is known not
3749 to build despite this, running into an internal error of the native
3750 @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
3751 its maximum of 262144 bytes. If you have root access, you can use the
3752 @command{systune} command to do this.
3754 @code{wchar_t} support in @samp{libstdc++} is not available for old
3755 IRIX 6.5.x releases, @math{x < 19}. The problem cannot be autodetected
3756 and in order to build GCC for such targets you need to configure with
3757 @option{--disable-wchar_t}.
3759 See @uref{http://freeware.sgi.com/} for more
3760 information about using GCC on IRIX platforms.
3765 @heading @anchor{moxie-x-elf}moxie-*-elf
3766 The moxie processor. See @uref{http://moxielogic.org/} for more
3767 information about this processor.
3772 @heading @anchor{powerpc-x-x}powerpc-*-*
3774 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
3775 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
3778 @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.15}
3779 or newer for a working GCC@.
3784 @heading @anchor{powerpc-x-darwin}powerpc-*-darwin*
3785 PowerPC running Darwin (Mac OS X kernel).
3787 Pre-installed versions of Mac OS X may not include any developer tools,
3788 meaning that you will not be able to build GCC from source. Tool
3789 binaries are available at
3790 @uref{http://developer.apple.com/darwin/projects/compiler/} (free
3791 registration required).
3793 This version of GCC requires at least cctools-590.36. The
3794 cctools-590.36 package referenced from
3795 @uref{http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html} will not work
3796 on systems older than 10.3.9 (aka darwin7.9.0).
3801 @heading @anchor{powerpc-x-elf}powerpc-*-elf
3802 PowerPC system in big endian mode, running System V.4.
3807 @heading @anchor{powerpc-x-linux-gnu}powerpc*-*-linux-gnu*
3809 PowerPC system in big endian mode running Linux.
3814 @heading @anchor{powerpc-x-netbsd}powerpc-*-netbsd*
3815 PowerPC system in big endian mode running NetBSD@.
3820 @heading @anchor{powerpc-x-eabisim}powerpc-*-eabisim
3821 Embedded PowerPC system in big endian mode for use in running under the
3827 @heading @anchor{powerpc-x-eabi}powerpc-*-eabi
3828 Embedded PowerPC system in big endian mode.
3833 @heading @anchor{powerpcle-x-elf}powerpcle-*-elf
3834 PowerPC system in little endian mode, running System V.4.
3839 @heading @anchor{powerpcle-x-eabisim}powerpcle-*-eabisim
3840 Embedded PowerPC system in little endian mode for use in running under
3846 @heading @anchor{powerpcle-x-eabi}powerpcle-*-eabi
3847 Embedded PowerPC system in little endian mode.
3852 @heading @anchor{s390-x-linux}s390-*-linux*
3853 S/390 system running GNU/Linux for S/390@.
3858 @heading @anchor{s390x-x-linux}s390x-*-linux*
3859 zSeries system (64-bit) running GNU/Linux for zSeries@.
3864 @heading @anchor{s390x-ibm-tpf}s390x-ibm-tpf*
3865 zSeries system (64-bit) running TPF@. This platform is
3866 supported as cross-compilation target only.
3871 @c Please use Solaris 2 to refer to all release of Solaris, starting
3872 @c with 2.0 until 2.6, 7, 8, etc. Solaris 1 was a marketing name for
3873 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
3874 @c alone is too unspecific and must be avoided.
3875 @heading @anchor{x-x-solaris2}*-*-solaris2*
3877 Sun does not ship a C compiler with Solaris 2. To bootstrap and install
3878 GCC you first have to install a pre-built compiler, see the
3879 @uref{binaries.html,,binaries page} for details.
3881 The Solaris 2 @command{/bin/sh} will often fail to configure
3882 @file{libstdc++-v3}, @file{boehm-gc} or @file{libjava}. We therefore
3883 recommend using the following initial sequence of commands
3886 % CONFIG_SHELL=/bin/ksh
3887 % export CONFIG_SHELL
3890 and proceed as described in @uref{configure.html,,the configure instructions}.
3891 In addition we strongly recommend specifying an absolute path to invoke
3892 @var{srcdir}/configure.
3894 Solaris 2 comes with a number of optional OS packages. Some of these
3895 are needed to use GCC fully, namely @code{SUNWarc},
3896 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
3897 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
3898 optional packages when installing Solaris 2, you will need to verify that
3899 the packages that GCC needs are installed.
3901 To check whether an optional package is installed, use
3902 the @command{pkginfo} command. To add an optional package, use the
3903 @command{pkgadd} command. For further details, see the Solaris 2
3906 Trying to use the linker and other tools in
3907 @file{/usr/ucb} to install GCC has been observed to cause trouble.
3908 For example, the linker may hang indefinitely. The fix is to remove
3909 @file{/usr/ucb} from your @env{PATH}.
3911 The build process works more smoothly with the legacy Sun tools so, if you
3912 have @file{/usr/xpg4/bin} in your @env{PATH}, we recommend that you place
3913 @file{/usr/bin} before @file{/usr/xpg4/bin} for the duration of the build.
3915 We recommend the use of GNU binutils 2.14 or later, or the vendor tools
3916 (Sun @command{as}, Sun @command{ld}). Note that your mileage may vary
3917 if you use a combination of the GNU tools and the Sun tools: while the
3918 combination GNU @command{as} + Sun @command{ld} should reasonably work,
3919 the reverse combination Sun @command{as} + GNU @command{ld} is known to
3920 cause memory corruption at runtime in some cases for C++ programs.
3922 The stock GNU binutils 2.15 release is broken on this platform because of a
3923 single bug. It has been fixed on the 2.15 branch in the CVS repository.
3924 You can obtain a working version by checking out the binutils-2_15-branch
3925 from the CVS repository or applying the patch
3926 @uref{http://sourceware.org/ml/binutils-cvs/2004-09/msg00036.html} to the
3929 We recommend the use of GNU binutils 2.16 or later in conjunction with GCC
3930 4.x, or the vendor tools (Sun @command{as}, Sun @command{ld}). However,
3931 for Solaris 10 and above, an additional patch is required in order for the
3932 GNU linker to be able to cope with a new flavor of shared libraries. You
3933 can obtain a working version by checking out the binutils-2_16-branch from
3934 the CVS repository or applying the patch
3935 @uref{http://sourceware.org/ml/binutils-cvs/2005-07/msg00122.html} to the
3938 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3939 newer: @command{g++} will complain that types are missing. These headers
3940 assume that omitting the type means @code{int}; this assumption worked for
3941 C89 but is wrong for C++, and is now wrong for C99 also.
3943 @command{g++} accepts such (invalid) constructs with the option
3944 @option{-fpermissive}; it will assume that any missing type is @code{int}
3945 (as defined by C89).
3947 There are patches for Solaris 7 (108376-21 or newer for SPARC,
3948 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
3949 108653-22 for Intel) that fix this bug.
3951 Sun bug 4927647 sometimes causes random spurious testsuite failures
3952 related to missing diagnostic output. This bug doesn't affect GCC
3953 itself, rather it is a kernel bug triggered by the @command{expect}
3954 program which is used only by the GCC testsuite driver. When the bug
3955 causes the @command{expect} program to miss anticipated output, extra
3956 testsuite failures appear.
3958 There are patches for Solaris 8 (117350-12 or newer for SPARC,
3959 117351-12 or newer for Intel) and Solaris 9 (117171-11 or newer for
3960 SPARC, 117172-11 or newer for Intel) that address this problem.
3965 @heading @anchor{sparc-sun-solaris2}sparc-sun-solaris2*
3967 When GCC is configured to use binutils 2.14 or later the binaries
3968 produced are smaller than the ones produced using Sun's native tools;
3969 this difference is quite significant for binaries containing debugging
3972 Starting with Solaris 7, the operating system is capable of executing
3973 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
3974 this; the @option{-m64} option enables 64-bit code generation.
3975 However, if all you want is code tuned for the UltraSPARC CPU, you
3976 should try the @option{-mtune=ultrasparc} option instead, which produces
3977 code that, unlike full 64-bit code, can still run on non-UltraSPARC
3980 When configuring on a Solaris 7 or later system that is running a kernel
3981 that supports only 32-bit binaries, one must configure with
3982 @option{--disable-multilib}, since we will not be able to build the
3983 64-bit target libraries.
3985 GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of
3986 the GNU compiler (especially GCC 3.0.x versions), which lead to the
3987 miscompilation of the stage1 compiler and the subsequent failure of the
3988 bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary
3989 stage, i.e.@: to bootstrap that compiler with the base compiler and then
3990 use it to bootstrap the final compiler.
3992 GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7)
3993 and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap
3994 failure in form of a miscompilation of the stage1 compiler by the Sun
3995 compiler. This is Sun bug 4974440. This is fixed with patch 112760-07.
3997 GCC 3.4 changed the default debugging format from STABS to DWARF-2 for
3998 32-bit code on Solaris 7 and later. If you use the Sun assembler, this
3999 change apparently runs afoul of Sun bug 4910101 (which is referenced as
4000 an x86-only problem by Sun, probably because they do not use DWARF-2).
4001 A symptom of the problem is that you cannot compile C++ programs like
4002 @command{groff} 1.19.1 without getting messages similar to the following:
4005 ld: warning: relocation error: R_SPARC_UA32: @dots{}
4006 external symbolic relocation against non-allocatable section
4007 .debug_info cannot be processed at runtime: relocation ignored.
4010 To work around this problem, compile with @option{-gstabs+} instead of
4013 When configuring the GNU Multiple Precision Library (GMP) or the MPFR
4014 library on a Solaris 7 or later system, the canonical target triplet
4015 must be specified as the @command{build} parameter on the configure
4016 line. This triplet can be obtained by invoking ./config.guess in
4017 the toplevel source directory of GCC (and not that of GMP or MPFR).
4018 For example on a Solaris 7 system:
4021 % ./configure --build=sparc-sun-solaris2.7 --prefix=xxx
4027 @heading @anchor{sparc-sun-solaris27}sparc-sun-solaris2.7
4029 Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
4030 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
4031 and later, including all EGCS releases. Sun formerly recommended
4032 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
4033 recommend it only for people who use Sun's compilers.
4035 Here are some workarounds to this problem:
4038 Do not install Sun patch 107058-01 until after Sun releases a
4039 complete patch for bug 4210064. This is the simplest course to take,
4040 unless you must also use Sun's C compiler. Unfortunately 107058-01
4041 is preinstalled on some new Solaris 7-based hosts, so you may have to
4045 Copy the original, unpatched Solaris 7
4046 @command{/usr/ccs/bin/as} into
4047 @command{/usr/local/libexec/gcc/sparc-sun-solaris2.7/3.4/as},
4048 adjusting the latter name to fit your local conventions and software
4052 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
4053 both 107058-01 and 106950-03 installed has reported the bug with GCC
4054 and Sun's dynamic linker. This last course of action is riskiest,
4055 for two reasons. First, you must install 106950 on all hosts that
4056 run code generated by GCC; it doesn't suffice to install it only on
4057 the hosts that run GCC itself. Second, Sun says that 106950-03 is
4058 only a partial fix for bug 4210064, but Sun doesn't know whether the
4059 partial fix is adequate for GCC@. Revision -08 or later should fix
4060 the bug. The current (as of 2004-05-23) revision is -24, and is included in
4061 the Solaris 7 Recommended Patch Cluster.
4064 GCC 3.3 triggers a bug in version 5.0 Alpha 03/27/98 of the Sun assembler,
4065 which causes a bootstrap failure when linking the 64-bit shared version of
4066 libgcc. A typical error message is:
4069 ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o:
4070 symbol <unknown>: offset 0xffffffff7ec133e7 is non-aligned.
4073 This bug has been fixed in the final 5.0 version of the assembler.
4075 A similar problem was reported for version Sun WorkShop 6 99/08/18 of the
4076 Sun assembler, which causes a bootstrap failure with GCC 4.0.0:
4079 ld: fatal: relocation error: R_SPARC_DISP32:
4080 file .libs/libstdc++.lax/libsupc++convenience.a/vterminate.o:
4081 symbol <unknown>: offset 0xfccd33ad is non-aligned
4084 This bug has been fixed in more recent revisions of the assembler.
4089 @heading @anchor{sparc-x-linux}sparc-*-linux*
4091 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
4092 or newer on this platform. All earlier binutils and glibc
4093 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
4099 @heading @anchor{sparc64-x-solaris2}sparc64-*-solaris2*
4101 When configuring the GNU Multiple Precision Library (GMP) or the
4102 MPFR library, the canonical target triplet must be specified as
4103 the @command{build} parameter on the configure line. For example
4104 on a Solaris 7 system:
4107 % ./configure --build=sparc64-sun-solaris2.7 --prefix=xxx
4110 The following compiler flags must be specified in the configure
4111 step in order to bootstrap this target with the Sun compiler:
4114 % CC="cc -xarch=v9 -xildoff" @var{srcdir}/configure [@var{options}] [@var{target}]
4117 @option{-xarch=v9} specifies the SPARC-V9 architecture to the Sun toolchain
4118 and @option{-xildoff} turns off the incremental linker.
4123 @heading @anchor{sparcv9-x-solaris2}sparcv9-*-solaris2*
4125 This is a synonym for sparc64-*-solaris2*.
4130 @heading @anchor{x-x-vxworks}*-*-vxworks*
4131 Support for VxWorks is in flux. At present GCC supports @emph{only} the
4132 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC@.
4133 We welcome patches for other architectures supported by VxWorks 5.5.
4134 Support for VxWorks AE would also be welcome; we believe this is merely
4135 a matter of writing an appropriate ``configlette'' (see below). We are
4136 not interested in supporting older, a.out or COFF-based, versions of
4139 VxWorks comes with an older version of GCC installed in
4140 @file{@var{$WIND_BASE}/host}; we recommend you do not overwrite it.
4141 Choose an installation @var{prefix} entirely outside @var{$WIND_BASE}.
4142 Before running @command{configure}, create the directories @file{@var{prefix}}
4143 and @file{@var{prefix}/bin}. Link or copy the appropriate assembler,
4144 linker, etc.@: into @file{@var{prefix}/bin}, and set your @var{PATH} to
4145 include that directory while running both @command{configure} and
4148 You must give @command{configure} the
4149 @option{--with-headers=@var{$WIND_BASE}/target/h} switch so that it can
4150 find the VxWorks system headers. Since VxWorks is a cross compilation
4151 target only, you must also specify @option{--target=@var{target}}.
4152 @command{configure} will attempt to create the directory
4153 @file{@var{prefix}/@var{target}/sys-include} and copy files into it;
4154 make sure the user running @command{configure} has sufficient privilege
4157 GCC's exception handling runtime requires a special ``configlette''
4158 module, @file{contrib/gthr_supp_vxw_5x.c}. Follow the instructions in
4159 that file to add the module to your kernel build. (Future versions of
4160 VxWorks will incorporate this module.)
4165 @heading @anchor{x86-64-x-x}x86_64-*-*, amd64-*-*
4167 GCC supports the x86-64 architecture implemented by the AMD64 processor
4168 (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD@.
4169 On GNU/Linux the default is a bi-arch compiler which is able to generate
4170 both 64-bit x86-64 and 32-bit x86 code (via the @option{-m32} switch).
4175 @heading @anchor{xtensa-x-elf}xtensa*-*-elf
4177 This target is intended for embedded Xtensa systems using the
4178 @samp{newlib} C library. It uses ELF but does not support shared
4179 objects. Designed-defined instructions specified via the
4180 Tensilica Instruction Extension (TIE) language are only supported
4181 through inline assembly.
4183 The Xtensa configuration information must be specified prior to
4184 building GCC@. The @file{include/xtensa-config.h} header
4185 file contains the configuration information. If you created your
4186 own Xtensa configuration with the Xtensa Processor Generator, the
4187 downloaded files include a customized copy of this header file,
4188 which you can use to replace the default header file.
4193 @heading @anchor{xtensa-x-linux}xtensa*-*-linux*
4195 This target is for Xtensa systems running GNU/Linux. It supports ELF
4196 shared objects and the GNU C library (glibc). It also generates
4197 position-independent code (PIC) regardless of whether the
4198 @option{-fpic} or @option{-fPIC} options are used. In other
4199 respects, this target is the same as the
4200 @uref{#xtensa*-*-elf,,@samp{xtensa*-*-elf}} target.
4205 @heading @anchor{windows}Microsoft Windows
4207 @subheading Intel 16-bit versions
4208 The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not
4211 However, the 32-bit port has limited support for Microsoft
4212 Windows 3.11 in the Win32s environment, as a target only. See below.
4214 @subheading Intel 32-bit versions
4216 The 32-bit versions of Windows, including Windows 95, Windows NT, Windows
4217 XP, and Windows Vista, are supported by several different target
4218 platforms. These targets differ in which Windows subsystem they target
4219 and which C libraries are used.
4222 @item Cygwin @uref{#x-x-cygwin,,*-*-cygwin}: Cygwin provides a user-space
4223 Linux API emulation layer in the Win32 subsystem.
4224 @item Interix @uref{#x-x-interix,,*-*-interix}: The Interix subsystem
4225 provides native support for POSIX.
4226 @item MinGW @uref{#x-x-mingw32,,*-*-mingw32}: MinGW is a native GCC port for
4227 the Win32 subsystem that provides a subset of POSIX.
4228 @item MKS i386-pc-mks: NuTCracker from MKS. See
4229 @uref{http://www.mkssoftware.com/} for more information.
4232 @subheading Intel 64-bit versions
4234 GCC contains support for x86-64 using the mingw-w64
4235 runtime library, available from @uref{http://mingw-w64.sourceforge.net/}.
4236 This library should be used with the target triple x86_64-pc-mingw32.
4238 Presently Windows for Itanium is not supported.
4240 @subheading Windows CE
4242 Windows CE is supported as a target only on ARM (arm-wince-pe), Hitachi
4243 SuperH (sh-wince-pe), and MIPS (mips-wince-pe).
4245 @subheading Other Windows Platforms
4247 GCC no longer supports Windows NT on the Alpha or PowerPC.
4249 GCC no longer supports the Windows POSIX subsystem. However, it does
4250 support the Interix subsystem. See above.
4252 Old target names including *-*-winnt and *-*-windowsnt are no longer used.
4254 PW32 (i386-pc-pw32) support was never completed, and the project seems to
4255 be inactive. See @uref{http://pw32.sourceforge.net/} for more information.
4257 UWIN support has been removed due to a lack of maintenance.
4262 @heading @anchor{x-x-cygwin}*-*-cygwin
4264 Ports of GCC are included with the
4265 @uref{http://www.cygwin.com/,,Cygwin environment}.
4267 GCC will build under Cygwin without modification; it does not build
4268 with Microsoft's C++ compiler and there are no plans to make it do so.
4270 Cygwin can be compiled with i?86-pc-cygwin.
4275 @heading @anchor{x-x-interix}*-*-interix
4277 The Interix target is used by OpenNT, Interix, Services For UNIX (SFU),
4278 and Subsystem for UNIX-based Applications (SUA). Applications compiled
4279 with this target run in the Interix subsystem, which is separate from
4280 the Win32 subsystem. This target was last known to work in GCC 3.3.
4282 For more information, see @uref{http://www.interix.com/}.
4287 @heading @anchor{x-x-mingw32}*-*-mingw32
4289 GCC will build with and support only MinGW runtime 3.12 and later.
4290 Earlier versions of headers are incompatible with the new default semantics
4291 of @code{extern inline} in @code{-std=c99} and @code{-std=gnu99} modes.
4296 @heading @anchor{os2}OS/2
4298 GCC does not currently support OS/2. However, Andrew Zabolotny has been
4299 working on a generic OS/2 port with pgcc. The current code can be found
4300 at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
4305 @heading @anchor{older}Older systems
4307 GCC contains support files for many older (1980s and early
4308 1990s) Unix variants. For the most part, support for these systems
4309 has not been deliberately removed, but it has not been maintained for
4310 several years and may suffer from bitrot.
4312 Starting with GCC 3.1, each release has a list of ``obsoleted'' systems.
4313 Support for these systems is still present in that release, but
4314 @command{configure} will fail unless the @option{--enable-obsolete}
4315 option is given. Unless a maintainer steps forward, support for these
4316 systems will be removed from the next release of GCC@.
4318 Support for old systems as hosts for GCC can cause problems if the
4319 workarounds for compiler, library and operating system bugs affect the
4320 cleanliness or maintainability of the rest of GCC@. In some cases, to
4321 bring GCC up on such a system, if still possible with current GCC, may
4322 require first installing an old version of GCC which did work on that
4323 system, and using it to compile a more recent GCC, to avoid bugs in the
4324 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
4325 @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror
4326 sites}. Header bugs may generally be avoided using
4327 @command{fixincludes}, but bugs or deficiencies in libraries and the
4328 operating system may still cause problems.
4330 Support for older systems as targets for cross-compilation is less
4331 problematic than support for them as hosts for GCC; if an enthusiast
4332 wishes to make such a target work again (including resurrecting any of
4333 the targets that never worked with GCC 2, starting from the last
4334 version before they were removed), patches
4335 @uref{../contribute.html,,following the usual requirements} would be
4336 likely to be accepted, since they should not affect the support for more
4339 For some systems, old versions of GNU binutils may also be useful,
4340 and are available from @file{pub/binutils/old-releases} on
4341 @uref{http://sourceware.org/mirrors.html,,sourceware.org mirror sites}.
4343 Some of the information on specific systems above relates to
4344 such older systems, but much of the information
4345 about GCC on such systems (which may no longer be applicable to
4346 current GCC) is to be found in the GCC texinfo manual.
4351 @heading @anchor{elf}all ELF targets (SVR4, Solaris 2, etc.)
4353 C++ support is significantly better on ELF targets if you use the
4354 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
4355 inlines, vtables and template instantiations will be discarded
4364 @uref{./index.html,,Return to the GCC Installation page}
4368 @c ***Old documentation******************************************************
4370 @include install-old.texi
4376 @uref{./index.html,,Return to the GCC Installation page}
4380 @c ***GFDL********************************************************************
4388 @uref{./index.html,,Return to the GCC Installation page}
4392 @c ***************************************************************************
4393 @c Part 6 The End of the Document
4395 @comment node-name, next, previous, up
4396 @node Concept Index, , GNU Free Documentation License, Top
4400 @unnumbered Concept Index