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,
49 @c 2010, 2011 Free Software Foundation, Inc.
50 @c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com
52 @c IMPORTANT: whenever you modify this file, run `install.texi2html' to
53 @c test the generation of HTML documents for the gcc.gnu.org web pages.
55 @c Do not use @footnote{} in this file as it breaks install.texi2html!
57 @c Include everything if we're not making html
61 @set prerequisiteshtml
72 @c Part 2 Summary Description and Copyright
74 Copyright @copyright{} 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
75 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
76 2010 Free Software Foundation, Inc.
78 Permission is granted to copy, distribute and/or modify this document
79 under the terms of the GNU Free Documentation License, Version 1.3 or
80 any later version published by the Free Software Foundation; with no
81 Invariant Sections, the Front-Cover texts being (a) (see below), and
82 with the Back-Cover Texts being (b) (see below). A copy of the
83 license is included in the section entitled ``@uref{./gfdl.html,,GNU
84 Free Documentation License}''.
86 (a) The FSF's Front-Cover Text is:
90 (b) The FSF's Back-Cover Text is:
92 You have freedom to copy and modify this GNU Manual, like GNU
93 software. Copies published by the Free Software Foundation raise
94 funds for GNU development.
99 @dircategory Software development
101 * gccinstall: (gccinstall). Installing the GNU Compiler Collection.
104 @c Part 3 Titlepage and Copyright
106 @title Installing GCC
109 @c The following two commands start the copyright page.
111 @vskip 0pt plus 1filll
115 @c Part 4 Top node, Master Menu, and/or Table of Contents
118 @comment node-name, next, Previous, up
121 * Installing GCC:: This document describes the generic installation
122 procedure for GCC as well as detailing some target
123 specific installation instructions.
125 * Specific:: Host/target specific installation notes for GCC.
126 * Binaries:: Where to get pre-compiled binaries.
128 * Old:: Old installation documentation.
130 * GNU Free Documentation License:: How you can copy and share this manual.
131 * Concept Index:: This index has two entries.
139 @c Part 5 The Body of the Document
140 @c ***Installing GCC**********************************************************
142 @comment node-name, next, previous, up
143 @node Installing GCC, Binaries, , Top
147 @chapter Installing GCC
150 The latest version of this document is always available at
151 @uref{http://gcc.gnu.org/install/,,http://gcc.gnu.org/install/}.
153 This document describes the generic installation procedure for GCC as well
154 as detailing some target specific installation instructions.
156 GCC includes several components that previously were separate distributions
157 with their own installation instructions. This document supersedes all
158 package specific installation instructions.
160 @emph{Before} starting the build/install procedure please check the
162 @ref{Specific, host/target specific installation notes}.
165 @uref{specific.html,,host/target specific installation notes}.
167 We recommend you browse the entire generic installation instructions before
170 Lists of successful builds for released versions of GCC are
171 available at @uref{http://gcc.gnu.org/buildstat.html}.
172 These lists are updated as new information becomes available.
174 The installation procedure itself is broken into five steps.
179 * Downloading the source::
182 * Testing:: (optional)
189 @uref{prerequisites.html,,Prerequisites}
191 @uref{download.html,,Downloading the source}
193 @uref{configure.html,,Configuration}
195 @uref{build.html,,Building}
197 @uref{test.html,,Testing} (optional)
199 @uref{finalinstall.html,,Final install}
203 Please note that GCC does not support @samp{make uninstall} and probably
204 won't do so in the near future as this would open a can of worms. Instead,
205 we suggest that you install GCC into a directory of its own and simply
206 remove that directory when you do not need that specific version of GCC
207 any longer, and, if shared libraries are installed there as well, no
208 more binaries exist that use them.
211 There are also some @uref{old.html,,old installation instructions},
212 which are mostly obsolete but still contain some information which has
213 not yet been merged into the main part of this manual.
221 @uref{./index.html,,Return to the GCC Installation page}
227 @c ***Prerequisites**************************************************
229 @comment node-name, next, previous, up
230 @node Prerequisites, Downloading the source, , Installing GCC
232 @ifset prerequisiteshtml
234 @chapter Prerequisites
236 @cindex Prerequisites
238 GCC requires that various tools and packages be available for use in the
239 build procedure. Modifying GCC sources requires additional tools
242 @heading Tools/packages necessary for building GCC
244 @item ISO C90 compiler
245 Necessary to bootstrap GCC, although versions of GCC prior
246 to 3.4 also allow bootstrapping with a traditional (K&R) C compiler.
248 To build all languages in a cross-compiler or other configuration where
249 3-stage bootstrap is not performed, you need to start with an existing
250 GCC binary (version 2.95 or later) because source code for language
251 frontends other than C might use GCC extensions.
255 In order to build the Ada compiler (GNAT) you must already have GNAT
256 installed because portions of the Ada frontend are written in Ada (with
257 GNAT extensions.) Refer to the Ada installation instructions for more
258 specific information.
260 @item A ``working'' POSIX compatible shell, or GNU bash
262 Necessary when running @command{configure} because some
263 @command{/bin/sh} shells have bugs and may crash when configuring the
264 target libraries. In other cases, @command{/bin/sh} or @command{ksh}
265 have disastrous corner-case performance problems. This
266 can cause target @command{configure} runs to literally take days to
267 complete in some cases.
269 So on some platforms @command{/bin/ksh} is sufficient, on others it
270 isn't. See the host/target specific instructions for your platform, or
271 use @command{bash} to be sure. Then set @env{CONFIG_SHELL} in your
272 environment to your ``good'' shell prior to running
273 @command{configure}/@command{make}.
275 @command{zsh} is not a fully compliant POSIX shell and will not
276 work when configuring GCC@.
278 @item A POSIX or SVR4 awk
280 Necessary for creating some of the generated source files for GCC@.
281 If in doubt, use a recent GNU awk version, as some of the older ones
282 are broken. GNU awk version 3.1.5 is known to work.
286 Necessary in some circumstances, optional in others. See the
287 host/target specific instructions for your platform for the exact
290 @item gzip version 1.2.4 (or later) or
291 @itemx bzip2 version 1.0.2 (or later)
293 Necessary to uncompress GCC @command{tar} files when source code is
294 obtained via FTP mirror sites.
296 @item GNU make version 3.80 (or later)
298 You must have GNU make installed to build GCC@.
300 @item GNU tar version 1.14 (or later)
302 Necessary (only on some platforms) to untar the source code. Many
303 systems' @command{tar} programs will also work, only try GNU
304 @command{tar} if you have problems.
306 @item Perl version 5.6.1 (or later)
308 Necessary when targetting Darwin, building @samp{libstdc++},
309 and not using @option{--disable-symvers}.
310 Necessary when targetting Solaris 2 with Sun @command{ld} and not using
311 @option{--disable-symvers}. The bundled @command{perl} in Solaris@tie{}8
314 Necessary when regenerating @file{Makefile} dependencies in libiberty.
315 Necessary when regenerating @file{libiberty/functions.texi}.
316 Necessary when generating manpages from Texinfo manuals.
317 Used by various scripts to generate some files included in SVN (mainly
318 Unicode-related and rarely changing) from source tables.
320 @item @command{jar}, or InfoZIP (@command{zip} and @command{unzip})
322 Necessary to build libgcj, the GCJ runtime.
326 Several support libraries are necessary to build GCC, some are required,
327 others optional. While any sufficiently new version of required tools
328 usually work, library requirements are generally stricter. Newer
329 versions may work in some cases, but it's safer to use the exact
330 versions documented. We appreciate bug reports about problems with
331 newer versions, though.
334 @item GNU Multiple Precision Library (GMP) version 4.3.2 (or later)
336 Necessary to build GCC@. If you do not have it installed in your
337 library search path, you will have to configure with the
338 @option{--with-gmp} configure option. See also @option{--with-gmp-lib}
339 and @option{--with-gmp-include}. Alternatively, if a GMP source
340 distribution is found in a subdirectory of your GCC sources named
341 @file{gmp}, it will be built together with GCC@.
343 @item MPFR Library version 2.4.2 (or later)
345 Necessary to build GCC@. It can be downloaded from
346 @uref{http://www.mpfr.org/}. The @option{--with-mpfr} configure
347 option should be used if your MPFR Library is not installed in your
348 default library search path. See also @option{--with-mpfr-lib} and
349 @option{--with-mpfr-include}. Alternatively, if a MPFR source
350 distribution is found in a subdirectory of your GCC sources named
351 @file{mpfr}, it will be built together with GCC@.
353 @item MPC Library version 0.8.1 (or later)
355 Necessary to build GCC@. It can be downloaded from
356 @uref{http://www.multiprecision.org/}. The @option{--with-mpc}
357 configure option should be used if your MPC Library is not installed
358 in your default library search path. See also @option{--with-mpc-lib}
359 and @option{--with-mpc-include}. Alternatively, if an MPC source
360 distribution is found in a subdirectory of your GCC sources named
361 @file{mpc}, it will be built together with GCC@.
363 @item Parma Polyhedra Library (PPL) version 0.11
365 Necessary to build GCC with the Graphite loop optimizations.
366 It can be downloaded from @uref{http://www.cs.unipr.it/ppl/Download/}.
368 The @option{--with-ppl} configure option should be used if PPL is not
369 installed in your default library search path.
371 @item CLooG-PPL version 0.15 or CLooG 0.16
373 Necessary to build GCC with the Graphite loop optimizations. There
374 are two versions available. CLooG-PPL 0.15 as well as CLooG 0.16.
375 The former is the default right now. It can be downloaded from
376 @uref{ftp://gcc.gnu.org/pub/gcc/infrastructure/} as
377 @file{cloog-ppl-0.15.tar.gz}.
379 CLooG 0.16 support is still in testing stage, but will be the
380 default in future GCC releases. It is also available at
381 @uref{ftp://gcc.gnu.org/pub/gcc/infrastructure/} as
382 @file{cloog-0.16.1.tar.gz}. To use it add the additional configure
383 option @option{--enable-cloog-backend=isl}. Even if CLooG 0.16
384 does not use PPL, PPL is still required for Graphite.
386 In both cases @option{--with-cloog} configure option should be used
387 if CLooG is not installed in your default library search path.
391 @heading Tools/packages necessary for modifying GCC
393 @item autoconf version 2.64
394 @itemx GNU m4 version 1.4.6 (or later)
396 Necessary when modifying @file{configure.ac}, @file{aclocal.m4}, etc.@:
397 to regenerate @file{configure} and @file{config.in} files.
399 @item automake version 1.11.1
401 Necessary when modifying a @file{Makefile.am} file to regenerate its
402 associated @file{Makefile.in}.
404 Much of GCC does not use automake, so directly edit the @file{Makefile.in}
405 file. Specifically this applies to the @file{gcc}, @file{intl},
406 @file{libcpp}, @file{libiberty}, @file{libobjc} directories as well
407 as any of their subdirectories.
409 For directories that use automake, GCC requires the latest release in
410 the 1.11 series, which is currently 1.11.1. When regenerating a directory
411 to a newer version, please update all the directories using an older 1.11
412 to the latest released version.
414 @item gettext version 0.14.5 (or later)
416 Needed to regenerate @file{gcc.pot}.
418 @item gperf version 2.7.2 (or later)
420 Necessary when modifying @command{gperf} input files, e.g.@:
421 @file{gcc/cp/cfns.gperf} to regenerate its associated header file, e.g.@:
422 @file{gcc/cp/cfns.h}.
428 Necessary to run the GCC testsuite; see the section on testing for details.
430 @item autogen version 5.5.4 (or later) and
431 @itemx guile version 1.4.1 (or later)
433 Necessary to regenerate @file{fixinc/fixincl.x} from
434 @file{fixinc/inclhack.def} and @file{fixinc/*.tpl}.
436 Necessary to run @samp{make check} for @file{fixinc}.
438 Necessary to regenerate the top level @file{Makefile.in} file from
439 @file{Makefile.tpl} and @file{Makefile.def}.
441 @item Flex version 2.5.4 (or later)
443 Necessary when modifying @file{*.l} files.
445 Necessary to build GCC during development because the generated output
446 files are not included in the SVN repository. They are included in
449 @item Texinfo version 4.7 (or later)
451 Necessary for running @command{makeinfo} when modifying @file{*.texi}
452 files to test your changes.
454 Necessary for running @command{make dvi} or @command{make pdf} to
455 create printable documentation in DVI or PDF format. Texinfo version
456 4.8 or later is required for @command{make pdf}.
458 Necessary to build GCC documentation during development because the
459 generated output files are not included in the SVN repository. They are
460 included in releases.
462 @item @TeX{} (any working version)
464 Necessary for running @command{texi2dvi} and @command{texi2pdf}, which
465 are used when running @command{make dvi} or @command{make pdf} to create
466 DVI or PDF files, respectively.
468 @item SVN (any version)
469 @itemx SSH (any version)
471 Necessary to access the SVN repository. Public releases and weekly
472 snapshots of the development sources are also available via FTP@.
474 @item GNU diffutils version 2.7 (or later)
476 Useful when submitting patches for the GCC source code.
478 @item patch version 2.5.4 (or later)
480 Necessary when applying patches, created with @command{diff}, to one's
486 If you wish to modify @file{.java} files in libjava, you will need to
487 configure with @option{--enable-java-maintainer-mode}, and you will need
488 to have executables named @command{ecj1} and @command{gjavah} in your path.
489 The @command{ecj1} executable should run the Eclipse Java compiler via
490 the GCC-specific entry point. You can download a suitable jar from
491 @uref{ftp://sourceware.org/pub/java/}, or by running the script
492 @command{contrib/download_ecj}.
494 @item antlr.jar version 2.7.1 (or later)
497 If you wish to build the @command{gjdoc} binary in libjava, you will
498 need to have an @file{antlr.jar} library available. The library is
499 searched in system locations but can be configured with
500 @option{--with-antlr-jar=} instead. When configuring with
501 @option{--enable-java-maintainer-mode}, you will need to have one of
502 the executables named @command{cantlr}, @command{runantlr} or
503 @command{antlr} in your path.
512 @uref{./index.html,,Return to the GCC Installation page}
516 @c ***Downloading the source**************************************************
518 @comment node-name, next, previous, up
519 @node Downloading the source, Configuration, Prerequisites, Installing GCC
523 @chapter Downloading GCC
525 @cindex Downloading GCC
526 @cindex Downloading the Source
528 GCC is distributed via @uref{http://gcc.gnu.org/svn.html,,SVN} and FTP
529 tarballs compressed with @command{gzip} or
530 @command{bzip2}. It is possible to download a full distribution or specific
533 Please refer to the @uref{http://gcc.gnu.org/releases.html,,releases web page}
534 for information on how to obtain GCC@.
536 The full distribution includes the C, C++, Objective-C, Fortran, Java,
537 and Ada (in the case of GCC 3.1 and later) compilers. The full
538 distribution also includes runtime libraries for C++, Objective-C,
539 Fortran, and Java. In GCC 3.0 and later versions, the GNU compiler
540 testsuites are also included in the full distribution.
542 If you choose to download specific components, you must download the core
543 GCC distribution plus any language specific distributions you wish to
544 use. The core distribution includes the C language front end as well as the
545 shared components. Each language has a tarball which includes the language
546 front end as well as the language runtime (when appropriate).
548 Unpack the core distribution as well as any language specific
549 distributions in the same directory.
551 If you also intend to build binutils (either to upgrade an existing
552 installation or for use in place of the corresponding tools of your
553 OS), unpack the binutils distribution either in the same directory or
554 a separate one. In the latter case, add symbolic links to any
555 components of the binutils you intend to build alongside the compiler
556 (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
557 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
559 Likewise the GMP, MPFR and MPC libraries can be automatically built
560 together with GCC. Unpack the GMP, MPFR and/or MPC source
561 distributions in the directory containing the GCC sources and rename
562 their directories to @file{gmp}, @file{mpfr} and @file{mpc},
563 respectively (or use symbolic links with the same name).
570 @uref{./index.html,,Return to the GCC Installation page}
574 @c ***Configuration***********************************************************
576 @comment node-name, next, previous, up
577 @node Configuration, Building, Downloading the source, Installing GCC
581 @chapter Installing GCC: Configuration
583 @cindex Configuration
584 @cindex Installing GCC: Configuration
586 Like most GNU software, GCC must be configured before it can be built.
587 This document describes the recommended configuration procedure
588 for both native and cross targets.
590 We use @var{srcdir} to refer to the toplevel source directory for
591 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
593 If you obtained the sources via SVN, @var{srcdir} must refer to the top
594 @file{gcc} directory, the one where the @file{MAINTAINERS} file can be
595 found, and not its @file{gcc} subdirectory, otherwise the build will fail.
597 If either @var{srcdir} or @var{objdir} is located on an automounted NFS
598 file system, the shell's built-in @command{pwd} command will return
599 temporary pathnames. Using these can lead to various sorts of build
600 problems. To avoid this issue, set the @env{PWDCMD} environment
601 variable to an automounter-aware @command{pwd} command, e.g.,
602 @command{pawd} or @samp{amq -w}, during the configuration and build
605 First, we @strong{highly} recommend that GCC be built into a
606 separate directory from the sources which does @strong{not} reside
607 within the source tree. This is how we generally build GCC; building
608 where @var{srcdir} == @var{objdir} should still work, but doesn't
609 get extensive testing; building where @var{objdir} is a subdirectory
610 of @var{srcdir} is unsupported.
612 If you have previously built GCC in the same directory for a
613 different target machine, do @samp{make distclean} to delete all files
614 that might be invalid. One of the files this deletes is @file{Makefile};
615 if @samp{make distclean} complains that @file{Makefile} does not exist
616 or issues a message like ``don't know how to make distclean'' it probably
617 means that the directory is already suitably clean. However, with the
618 recommended method of building in a separate @var{objdir}, you should
619 simply use a different @var{objdir} for each target.
621 Second, when configuring a native system, either @command{cc} or
622 @command{gcc} must be in your path or you must set @env{CC} in
623 your environment before running configure. Otherwise the configuration
627 Note that the bootstrap compiler and the resulting GCC must be link
628 compatible, else the bootstrap will fail with linker errors about
629 incompatible object file formats. Several multilibed targets are
630 affected by this requirement, see
632 @ref{Specific, host/target specific installation notes}.
635 @uref{specific.html,,host/target specific installation notes}.
644 % @var{srcdir}/configure [@var{options}] [@var{target}]
647 @heading Distributor options
649 If you will be distributing binary versions of GCC, with modifications
650 to the source code, you should use the options described in this
651 section to make clear that your version contains modifications.
654 @item --with-pkgversion=@var{version}
655 Specify a string that identifies your package. You may wish
656 to include a build number or build date. This version string will be
657 included in the output of @command{gcc --version}. This suffix does
658 not replace the default version string, only the @samp{GCC} part.
660 The default value is @samp{GCC}.
662 @item --with-bugurl=@var{url}
663 Specify the URL that users should visit if they wish to report a bug.
664 You are of course welcome to forward bugs reported to you to the FSF,
665 if you determine that they are not bugs in your modifications.
667 The default value refers to the FSF's GCC bug tracker.
671 @heading Target specification
674 GCC has code to correctly determine the correct value for @var{target}
675 for nearly all native systems. Therefore, we highly recommend you do
676 not provide a configure target when configuring a native compiler.
679 @var{target} must be specified as @option{--target=@var{target}}
680 when configuring a cross compiler; examples of valid targets would be
681 m68k-elf, sh-elf, etc.
684 Specifying just @var{target} instead of @option{--target=@var{target}}
685 implies that the host defaults to @var{target}.
689 @heading Options specification
691 Use @var{options} to override several configure time options for
692 GCC@. A list of supported @var{options} follows; @samp{configure
693 --help} may list other options, but those not listed below may not
694 work and should not normally be used.
696 Note that each @option{--enable} option has a corresponding
697 @option{--disable} option and that each @option{--with} option has a
698 corresponding @option{--without} option.
701 @item --prefix=@var{dirname}
702 Specify the toplevel installation
703 directory. This is the recommended way to install the tools into a directory
704 other than the default. The toplevel installation directory defaults to
707 We @strong{highly} recommend against @var{dirname} being the same or a
708 subdirectory of @var{objdir} or vice versa. If specifying a directory
709 beneath a user's home directory tree, some shells will not expand
710 @var{dirname} correctly if it contains the @samp{~} metacharacter; use
713 The following standard @command{autoconf} options are supported. Normally you
714 should not need to use these options.
716 @item --exec-prefix=@var{dirname}
717 Specify the toplevel installation directory for architecture-dependent
718 files. The default is @file{@var{prefix}}.
720 @item --bindir=@var{dirname}
721 Specify the installation directory for the executables called by users
722 (such as @command{gcc} and @command{g++}). The default is
723 @file{@var{exec-prefix}/bin}.
725 @item --libdir=@var{dirname}
726 Specify the installation directory for object code libraries and
727 internal data files of GCC@. The default is @file{@var{exec-prefix}/lib}.
729 @item --libexecdir=@var{dirname}
730 Specify the installation directory for internal executables of GCC@.
731 The default is @file{@var{exec-prefix}/libexec}.
733 @item --with-slibdir=@var{dirname}
734 Specify the installation directory for the shared libgcc library. The
735 default is @file{@var{libdir}}.
737 @item --datarootdir=@var{dirname}
738 Specify the root of the directory tree for read-only architecture-independent
739 data files referenced by GCC@. The default is @file{@var{prefix}/share}.
741 @item --infodir=@var{dirname}
742 Specify the installation directory for documentation in info format.
743 The default is @file{@var{datarootdir}/info}.
745 @item --datadir=@var{dirname}
746 Specify the installation directory for some architecture-independent
747 data files referenced by GCC@. The default is @file{@var{datarootdir}}.
749 @item --docdir=@var{dirname}
750 Specify the installation directory for documentation files (other
751 than Info) for GCC@. The default is @file{@var{datarootdir}/doc}.
753 @item --htmldir=@var{dirname}
754 Specify the installation directory for HTML documentation files.
755 The default is @file{@var{docdir}}.
757 @item --pdfdir=@var{dirname}
758 Specify the installation directory for PDF documentation files.
759 The default is @file{@var{docdir}}.
761 @item --mandir=@var{dirname}
762 Specify the installation directory for manual pages. The default is
763 @file{@var{datarootdir}/man}. (Note that the manual pages are only extracts
764 from the full GCC manuals, which are provided in Texinfo format. The manpages
765 are derived by an automatic conversion process from parts of the full
768 @item --with-gxx-include-dir=@var{dirname}
770 the installation directory for G++ header files. The default depends
771 on other configuration options, and differs between cross and native
774 @item --with-specs=@var{specs}
775 Specify additional command line driver SPECS.
776 This can be useful if you need to turn on a non-standard feature by
777 default without modifying the compiler's source code, for instance
778 @option{--with-specs=%@{!fcommon:%@{!fno-common:-fno-common@}@}}.
780 @xref{Spec Files,, Specifying subprocesses and the switches to pass to them,
781 gcc, Using the GNU Compiler Collection (GCC)},
784 See ``Spec Files'' in the main manual
789 @item --program-prefix=@var{prefix}
790 GCC supports some transformations of the names of its programs when
791 installing them. This option prepends @var{prefix} to the names of
792 programs to install in @var{bindir} (see above). For example, specifying
793 @option{--program-prefix=foo-} would result in @samp{gcc}
794 being installed as @file{/usr/local/bin/foo-gcc}.
796 @item --program-suffix=@var{suffix}
797 Appends @var{suffix} to the names of programs to install in @var{bindir}
798 (see above). For example, specifying @option{--program-suffix=-3.1}
799 would result in @samp{gcc} being installed as
800 @file{/usr/local/bin/gcc-3.1}.
802 @item --program-transform-name=@var{pattern}
803 Applies the @samp{sed} script @var{pattern} to be applied to the names
804 of programs to install in @var{bindir} (see above). @var{pattern} has to
805 consist of one or more basic @samp{sed} editing commands, separated by
806 semicolons. For example, if you want the @samp{gcc} program name to be
807 transformed to the installed program @file{/usr/local/bin/myowngcc} and
808 the @samp{g++} program name to be transformed to
809 @file{/usr/local/bin/gspecial++} without changing other program names,
810 you could use the pattern
811 @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}
812 to achieve this effect.
814 All three options can be combined and used together, resulting in more
815 complex conversion patterns. As a basic rule, @var{prefix} (and
816 @var{suffix}) are prepended (appended) before further transformations
817 can happen with a special transformation script @var{pattern}.
819 As currently implemented, this option only takes effect for native
820 builds; cross compiler binaries' names are not transformed even when a
821 transformation is explicitly asked for by one of these options.
823 For native builds, some of the installed programs are also installed
824 with the target alias in front of their name, as in
825 @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
826 before the target alias is prepended to the name---so, specifying
827 @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
828 resulting binary would be installed as
829 @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.
831 As a last shortcoming, none of the installed Ada programs are
832 transformed yet, which will be fixed in some time.
834 @item --with-local-prefix=@var{dirname}
836 installation directory for local include files. The default is
837 @file{/usr/local}. Specify this option if you want the compiler to
838 search directory @file{@var{dirname}/include} for locally installed
839 header files @emph{instead} of @file{/usr/local/include}.
841 You should specify @option{--with-local-prefix} @strong{only} if your
842 site has a different convention (not @file{/usr/local}) for where to put
845 The default value for @option{--with-local-prefix} is @file{/usr/local}
846 regardless of the value of @option{--prefix}. Specifying
847 @option{--prefix} has no effect on which directory GCC searches for
848 local header files. This may seem counterintuitive, but actually it is
851 The purpose of @option{--prefix} is to specify where to @emph{install
852 GCC}. The local header files in @file{/usr/local/include}---if you put
853 any in that directory---are not part of GCC@. They are part of other
854 programs---perhaps many others. (GCC installs its own header files in
855 another directory which is based on the @option{--prefix} value.)
857 Both the local-prefix include directory and the GCC-prefix include
858 directory are part of GCC's ``system include'' directories. Although these
859 two directories are not fixed, they need to be searched in the proper
860 order for the correct processing of the include_next directive. The
861 local-prefix include directory is searched before the GCC-prefix
862 include directory. Another characteristic of system include directories
863 is that pedantic warnings are turned off for headers in these directories.
865 Some autoconf macros add @option{-I @var{directory}} options to the
866 compiler command line, to ensure that directories containing installed
867 packages' headers are searched. When @var{directory} is one of GCC's
868 system include directories, GCC will ignore the option so that system
869 directories continue to be processed in the correct order. This
870 may result in a search order different from what was specified but the
871 directory will still be searched.
873 GCC automatically searches for ordinary libraries using
874 @env{GCC_EXEC_PREFIX}. Thus, when the same installation prefix is
875 used for both GCC and packages, GCC will automatically search for
876 both headers and libraries. This provides a configuration that is
877 easy to use. GCC behaves in a manner similar to that when it is
878 installed as a system compiler in @file{/usr}.
880 Sites that need to install multiple versions of GCC may not want to
881 use the above simple configuration. It is possible to use the
882 @option{--program-prefix}, @option{--program-suffix} and
883 @option{--program-transform-name} options to install multiple versions
884 into a single directory, but it may be simpler to use different prefixes
885 and the @option{--with-local-prefix} option to specify the location of the
886 site-specific files for each version. It will then be necessary for
887 users to specify explicitly the location of local site libraries
888 (e.g., with @env{LIBRARY_PATH}).
890 The same value can be used for both @option{--with-local-prefix} and
891 @option{--prefix} provided it is not @file{/usr}. This can be used
892 to avoid the default search of @file{/usr/local/include}.
894 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
895 The directory you use for @option{--with-local-prefix} @strong{must not}
896 contain any of the system's standard header files. If it did contain
897 them, certain programs would be miscompiled (including GNU Emacs, on
898 certain targets), because this would override and nullify the header
899 file corrections made by the @command{fixincludes} script.
901 Indications are that people who use this option use it based on mistaken
902 ideas of what it is for. People use it as if it specified where to
903 install part of GCC@. Perhaps they make this assumption because
904 installing GCC creates the directory.
906 @item --enable-shared[=@var{package}[,@dots{}]]
907 Build shared versions of libraries, if shared libraries are supported on
908 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
909 are enabled by default on all platforms that support shared libraries.
911 If a list of packages is given as an argument, build shared libraries
912 only for the listed packages. For other packages, only static libraries
913 will be built. Package names currently recognized in the GCC tree are
914 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
915 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc},
916 @samp{ada}, @samp{libada}, @samp{libjava}, @samp{libgo}, and @samp{libobjc}.
917 Note @samp{libiberty} does not support shared libraries at all.
919 Use @option{--disable-shared} to build only static libraries. Note that
920 @option{--disable-shared} does not accept a list of package names as
921 argument, only @option{--enable-shared} does.
923 @item @anchor{with-gnu-as}--with-gnu-as
924 Specify that the compiler should assume that the
925 assembler it finds is the GNU assembler. However, this does not modify
926 the rules to find an assembler and will result in confusion if the
927 assembler found is not actually the GNU assembler. (Confusion may also
928 result if the compiler finds the GNU assembler but has not been
929 configured with @option{--with-gnu-as}.) If you have more than one
930 assembler installed on your system, you may want to use this option in
931 connection with @option{--with-as=@var{pathname}} or
932 @option{--with-build-time-tools=@var{pathname}}.
934 The following systems are the only ones where it makes a difference
935 whether you use the GNU assembler. On any other system,
936 @option{--with-gnu-as} has no effect.
939 @item @samp{hppa1.0-@var{any}-@var{any}}
940 @item @samp{hppa1.1-@var{any}-@var{any}}
941 @item @samp{sparc-sun-solaris2.@var{any}}
942 @item @samp{sparc64-@var{any}-solaris2.@var{any}}
945 @item @anchor{with-as}--with-as=@var{pathname}
946 Specify that the compiler should use the assembler pointed to by
947 @var{pathname}, rather than the one found by the standard rules to find
948 an assembler, which are:
951 Unless GCC is being built with a cross compiler, check the
952 @file{@var{libexec}/gcc/@var{target}/@var{version}} directory.
953 @var{libexec} defaults to @file{@var{exec-prefix}/libexec};
954 @var{exec-prefix} defaults to @var{prefix}, which
955 defaults to @file{/usr/local} unless overridden by the
956 @option{--prefix=@var{pathname}} switch described above. @var{target}
957 is the target system triple, such as @samp{sparc-sun-solaris2.7}, and
958 @var{version} denotes the GCC version, such as 3.0.
961 If the target system is the same that you are building on, check
962 operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
966 Check in the @env{PATH} for a tool whose name is prefixed by the
967 target system triple.
970 Check in the @env{PATH} for a tool whose name is not prefixed by the
971 target system triple, if the host and target system triple are
972 the same (in other words, we use a host tool if it can be used for
976 You may want to use @option{--with-as} if no assembler
977 is installed in the directories listed above, or if you have multiple
978 assemblers installed and want to choose one that is not found by the
981 @item @anchor{with-gnu-ld}--with-gnu-ld
982 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
985 @item --with-ld=@var{pathname}
986 Same as @uref{#with-as,,@option{--with-as}}
990 Specify that stabs debugging
991 information should be used instead of whatever format the host normally
992 uses. Normally GCC uses the same debug format as the host system.
994 On MIPS based systems and on Alphas, you must specify whether you want
995 GCC to create the normal ECOFF debugging format, or to use BSD-style
996 stabs passed through the ECOFF symbol table. The normal ECOFF debug
997 format cannot fully handle languages other than C@. BSD stabs format can
998 handle other languages, but it only works with the GNU debugger GDB@.
1000 Normally, GCC uses the ECOFF debugging format by default; if you
1001 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
1003 No matter which default you choose when you configure GCC, the user
1004 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
1005 the debug format for a particular compilation.
1007 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
1008 @option{--with-gas} is used. It selects use of stabs debugging
1009 information embedded in COFF output. This kind of debugging information
1010 supports C++ well; ordinary COFF debugging information does not.
1012 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
1013 selects use of stabs debugging information embedded in ELF output. The
1014 C++ compiler currently (2.6.0) does not support the DWARF debugging
1015 information normally used on 386 SVR4 platforms; stabs provide a
1016 workable alternative. This requires gas and gdb, as the normal SVR4
1017 tools can not generate or interpret stabs.
1019 @item --with-tls=@var{dialect}
1020 Specify the default TLS dialect, for systems were there is a choice.
1021 For ARM targets, possible values for @var{dialect} are @code{gnu} or
1022 @code{gnu2}, which select between the original GNU dialect and the GNU TLS
1023 descriptor-based dialect.
1025 @item --disable-multilib
1026 Specify that multiple target
1027 libraries to support different target variants, calling
1028 conventions, etc.@: should not be built. The default is to build a
1029 predefined set of them.
1031 Some targets provide finer-grained control over which multilibs are built
1032 (e.g., @option{--disable-softfloat}):
1035 fpu, 26bit, underscore, interwork, biendian, nofmult.
1038 softfloat, m68881, m68000, m68020.
1041 single-float, biendian, softfloat.
1043 @item powerpc*-*-*, rs6000*-*-*
1044 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
1049 @item --with-multilib-list=@var{list}
1050 @itemx --without-multilib-list
1051 Specify what multilibs to build.
1052 Currently only implemented for sh*-*-*.
1054 @var{list} is a comma separated list of CPU names. These must be of the
1055 form @code{sh*} or @code{m*} (in which case they match the compiler option
1056 for that processor). The list should not contain any endian options -
1057 these are handled by @option{--with-endian}.
1059 If @var{list} is empty, then there will be no multilibs for extra
1060 processors. The multilib for the secondary endian remains enabled.
1062 As a special case, if an entry in the list starts with a @code{!}
1063 (exclamation point), then it is added to the list of excluded multilibs.
1064 Entries of this sort should be compatible with @samp{MULTILIB_EXCLUDES}
1065 (once the leading @code{!} has been stripped).
1067 If @option{--with-multilib-list} is not given, then a default set of
1068 multilibs is selected based on the value of @option{--target}. This is
1069 usually the complete set of libraries, but some targets imply a more
1072 Example 1: to configure a compiler for SH4A only, but supporting both
1073 endians, with little endian being the default:
1075 --with-cpu=sh4a --with-endian=little,big --with-multilib-list=
1078 Example 2: to configure a compiler for both SH4A and SH4AL-DSP, but with
1079 only little endian SH4AL:
1081 --with-cpu=sh4a --with-endian=little,big \
1082 --with-multilib-list=sh4al,!mb/m4al
1085 @item --with-endian=@var{endians}
1086 Specify what endians to use.
1087 Currently only implemented for sh*-*-*.
1089 @var{endians} may be one of the following:
1092 Use big endian exclusively.
1094 Use little endian exclusively.
1096 Use big endian by default. Provide a multilib for little endian.
1098 Use little endian by default. Provide a multilib for big endian.
1101 @item --enable-threads
1102 Specify that the target
1103 supports threads. This affects the Objective-C compiler and runtime
1104 library, and exception handling for other languages like C++ and Java.
1105 On some systems, this is the default.
1107 In general, the best (and, in many cases, the only known) threading
1108 model available will be configured for use. Beware that on some
1109 systems, GCC has not been taught what threading models are generally
1110 available for the system. In this case, @option{--enable-threads} is an
1111 alias for @option{--enable-threads=single}.
1113 @item --disable-threads
1114 Specify that threading support should be disabled for the system.
1115 This is an alias for @option{--enable-threads=single}.
1117 @item --enable-threads=@var{lib}
1119 @var{lib} is the thread support library. This affects the Objective-C
1120 compiler and runtime library, and exception handling for other languages
1121 like C++ and Java. The possibilities for @var{lib} are:
1129 LynxOS thread support.
1131 MIPS SDE thread support.
1133 Novell Kernel Services thread support.
1135 This is an alias for @samp{single}.
1137 Generic POSIX/Unix98 thread support.
1139 Generic POSIX/Unix95 thread support.
1141 RTEMS thread support.
1143 Disable thread support, should work for all platforms.
1147 VxWorks thread support.
1149 Microsoft Win32 API thread support.
1153 Specify that the target supports TLS (Thread Local Storage). Usually
1154 configure can correctly determine if TLS is supported. In cases where
1155 it guesses incorrectly, TLS can be explicitly enabled or disabled with
1156 @option{--enable-tls} or @option{--disable-tls}. This can happen if
1157 the assembler supports TLS but the C library does not, or if the
1158 assumptions made by the configure test are incorrect.
1161 Specify that the target does not support TLS.
1162 This is an alias for @option{--enable-tls=no}.
1164 @item --with-cpu=@var{cpu}
1165 @itemx --with-cpu-32=@var{cpu}
1166 @itemx --with-cpu-64=@var{cpu}
1167 Specify which cpu variant the compiler should generate code for by default.
1168 @var{cpu} will be used as the default value of the @option{-mcpu=} switch.
1169 This option is only supported on some targets, including ARM, i386, M68k,
1170 PowerPC, and SPARC@. The @option{--with-cpu-32} and
1171 @option{--with-cpu-64} options specify separate default CPUs for
1172 32-bit and 64-bit modes; these options are only supported for i386,
1175 @item --with-schedule=@var{cpu}
1176 @itemx --with-arch=@var{cpu}
1177 @itemx --with-arch-32=@var{cpu}
1178 @itemx --with-arch-64=@var{cpu}
1179 @itemx --with-tune=@var{cpu}
1180 @itemx --with-tune-32=@var{cpu}
1181 @itemx --with-tune-64=@var{cpu}
1182 @itemx --with-abi=@var{abi}
1183 @itemx --with-fpu=@var{type}
1184 @itemx --with-float=@var{type}
1185 These configure options provide default values for the @option{-mschedule=},
1186 @option{-march=}, @option{-mtune=}, @option{-mabi=}, and @option{-mfpu=}
1187 options and for @option{-mhard-float} or @option{-msoft-float}. As with
1188 @option{--with-cpu}, which switches will be accepted and acceptable values
1189 of the arguments depend on the target.
1191 @item --with-mode=@var{mode}
1192 Specify if the compiler should default to @option{-marm} or @option{-mthumb}.
1193 This option is only supported on ARM targets.
1195 @item --with-fpmath=@var{isa}
1196 This options sets @option{-mfpmath=sse} by default and specifies the default
1197 ISA for floating-point arithmetics. You can select either @samp{sse} which
1198 enables @option{-msse2} or @samp{avx} which enables @option{-mavx} by default.
1199 This option is only supported on i386 and x86-64 targets.
1201 @item --with-divide=@var{type}
1202 Specify how the compiler should generate code for checking for
1203 division by zero. This option is only supported on the MIPS target.
1204 The possibilities for @var{type} are:
1207 Division by zero checks use conditional traps (this is the default on
1208 systems that support conditional traps).
1210 Division by zero checks use the break instruction.
1213 @c If you make --with-llsc the default for additional targets,
1214 @c update the --with-llsc description in the MIPS section below.
1217 On MIPS targets, make @option{-mllsc} the default when no
1218 @option{-mno-lsc} option is passed. This is the default for
1219 Linux-based targets, as the kernel will emulate them if the ISA does
1222 @item --without-llsc
1223 On MIPS targets, make @option{-mno-llsc} the default when no
1224 @option{-mllsc} option is passed.
1227 On MIPS targets, make @option{-msynci} the default when no
1228 @option{-mno-synci} option is passed.
1230 @item --without-synci
1231 On MIPS targets, make @option{-mno-synci} the default when no
1232 @option{-msynci} option is passed. This is the default.
1234 @item --with-mips-plt
1235 On MIPS targets, make use of copy relocations and PLTs.
1236 These features are extensions to the traditional
1237 SVR4-based MIPS ABIs and require support from GNU binutils
1238 and the runtime C library.
1240 @item --enable-__cxa_atexit
1241 Define if you want to use __cxa_atexit, rather than atexit, to
1242 register C++ destructors for local statics and global objects.
1243 This is essential for fully standards-compliant handling of
1244 destructors, but requires __cxa_atexit in libc. This option is currently
1245 only available on systems with GNU libc. When enabled, this will cause
1246 @option{-fuse-cxa-atexit} to be passed by default.
1248 @item --enable-indirect-function
1249 Define if you want to enable the @code{ifunc} attribute. This option is
1250 currently only available on systems with GNU libc on certain targets.
1252 @item --enable-target-optspace
1254 libraries should be optimized for code space instead of code speed.
1255 This is the default for the m32r platform.
1257 @item --with-cpp-install-dir=@var{dirname}
1258 Specify that the user visible @command{cpp} program should be installed
1259 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
1261 @item --enable-comdat
1262 Enable COMDAT group support. This is primarily used to override the
1263 automatically detected value.
1265 @item --enable-initfini-array
1266 Force the use of sections @code{.init_array} and @code{.fini_array}
1267 (instead of @code{.init} and @code{.fini}) for constructors and
1268 destructors. Option @option{--disable-initfini-array} has the
1269 opposite effect. If neither option is specified, the configure script
1270 will try to guess whether the @code{.init_array} and
1271 @code{.fini_array} sections are supported and, if they are, use them.
1273 @item --enable-build-with-cxx
1274 Build GCC using a C++ compiler rather than a C compiler. This is an
1275 experimental option which may become the default in a later release.
1277 @item --enable-maintainer-mode
1278 The build rules that regenerate the Autoconf and Automake output files as
1279 well as the GCC master message catalog @file{gcc.pot} are normally
1280 disabled. This is because it can only be rebuilt if the complete source
1281 tree is present. If you have changed the sources and want to rebuild the
1282 catalog, configuring with @option{--enable-maintainer-mode} will enable
1283 this. Note that you need a recent version of the @code{gettext} tools
1286 @item --disable-bootstrap
1287 For a native build, the default configuration is to perform
1288 a 3-stage bootstrap of the compiler when @samp{make} is invoked,
1289 testing that GCC can compile itself correctly. If you want to disable
1290 this process, you can configure with @option{--disable-bootstrap}.
1292 @item --enable-bootstrap
1293 In special cases, you may want to perform a 3-stage build
1294 even if the target and host triplets are different.
1295 This is possible when the host can run code compiled for
1296 the target (e.g.@: host is i686-linux, target is i486-linux).
1297 Starting from GCC 4.2, to do this you have to configure explicitly
1298 with @option{--enable-bootstrap}.
1300 @item --enable-generated-files-in-srcdir
1301 Neither the .c and .h files that are generated from Bison and flex nor the
1302 info manuals and man pages that are built from the .texi files are present
1303 in the SVN development tree. When building GCC from that development tree,
1304 or from one of our snapshots, those generated files are placed in your
1305 build directory, which allows for the source to be in a readonly
1308 If you configure with @option{--enable-generated-files-in-srcdir} then those
1309 generated files will go into the source directory. This is mainly intended
1310 for generating release or prerelease tarballs of the GCC sources, since it
1311 is not a requirement that the users of source releases to have flex, Bison,
1314 @item --enable-version-specific-runtime-libs
1316 that runtime libraries should be installed in the compiler specific
1317 subdirectory (@file{@var{libdir}/gcc}) rather than the usual places. In
1318 addition, @samp{libstdc++}'s include files will be installed into
1319 @file{@var{libdir}} unless you overruled it by using
1320 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
1321 particularly useful if you intend to use several versions of GCC in
1322 parallel. This is currently supported by @samp{libgfortran},
1323 @samp{libjava}, @samp{libmudflap}, @samp{libstdc++}, and @samp{libobjc}.
1325 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
1326 Specify that only a particular subset of compilers and
1327 their runtime libraries should be built. For a list of valid values for
1328 @var{langN} you can issue the following command in the
1329 @file{gcc} directory of your GCC source tree:@*
1331 grep language= */config-lang.in
1333 Currently, you can use any of the following:
1334 @code{all}, @code{ada}, @code{c}, @code{c++}, @code{fortran},
1335 @code{go}, @code{java}, @code{objc}, @code{obj-c++}.
1336 Building the Ada compiler has special requirements, see below.
1337 If you do not pass this flag, or specify the option @code{all}, then all
1338 default languages available in the @file{gcc} sub-tree will be configured.
1339 Ada, Go and Objective-C++ are not default languages; the rest are.
1341 @item --enable-stage1-languages=@var{lang1},@var{lang2},@dots{}
1342 Specify that a particular subset of compilers and their runtime
1343 libraries should be built with the system C compiler during stage 1 of
1344 the bootstrap process, rather than only in later stages with the
1345 bootstrapped C compiler. The list of valid values is the same as for
1346 @option{--enable-languages}, and the option @code{all} will select all
1347 of the languages enabled by @option{--enable-languages}. This option is
1348 primarily useful for GCC development; for instance, when a development
1349 version of the compiler cannot bootstrap due to compiler bugs, or when
1350 one is debugging front ends other than the C front end. When this
1351 option is used, one can then build the target libraries for the
1352 specified languages with the stage-1 compiler by using @command{make
1353 stage1-bubble all-target}, or run the testsuite on the stage-1 compiler
1354 for the specified languages using @command{make stage1-start check-gcc}.
1356 @item --disable-libada
1357 Specify that the run-time libraries and tools used by GNAT should not
1358 be built. This can be useful for debugging, or for compatibility with
1359 previous Ada build procedures, when it was required to explicitly
1360 do a @samp{make -C gcc gnatlib_and_tools}.
1362 @item --disable-libssp
1363 Specify that the run-time libraries for stack smashing protection
1364 should not be built.
1366 @item --disable-libquadmath
1367 Specify that the GCC quad-precision math library should not be built.
1368 On some systems, the library is required to be linkable when building
1369 the Fortran front end, unless @option{--disable-libquadmath-support}
1372 @item --disable-libquadmath-support
1373 Specify that the Fortran front end and @code{libgfortran} do not add
1374 support for @code{libquadmath} on systems supporting it.
1376 @item --disable-libgomp
1377 Specify that the run-time libraries used by GOMP should not be built.
1380 Specify that the compiler should
1381 use DWARF 2 debugging information as the default.
1383 @item --enable-targets=all
1384 @itemx --enable-targets=@var{target_list}
1385 Some GCC targets, e.g.@: powerpc64-linux, build bi-arch compilers.
1386 These are compilers that are able to generate either 64-bit or 32-bit
1387 code. Typically, the corresponding 32-bit target, e.g.@:
1388 powerpc-linux for powerpc64-linux, only generates 32-bit code. This
1389 option enables the 32-bit target to be a bi-arch compiler, which is
1390 useful when you want a bi-arch compiler that defaults to 32-bit, and
1391 you are building a bi-arch or multi-arch binutils in a combined tree.
1392 On mips-linux, this will build a tri-arch compiler (ABI o32/n32/64),
1394 Currently, this option only affects sparc-linux, powerpc-linux, x86-linux
1397 @item --enable-secureplt
1398 This option enables @option{-msecure-plt} by default for powerpc-linux.
1400 @xref{RS/6000 and PowerPC Options,, RS/6000 and PowerPC Options, gcc,
1401 Using the GNU Compiler Collection (GCC)},
1404 See ``RS/6000 and PowerPC Options'' in the main manual
1408 This option enables @option{-mcld} by default for 32-bit x86 targets.
1410 @xref{i386 and x86-64 Options,, i386 and x86-64 Options, gcc,
1411 Using the GNU Compiler Collection (GCC)},
1414 See ``i386 and x86-64 Options'' in the main manual
1417 @item --enable-win32-registry
1418 @itemx --enable-win32-registry=@var{key}
1419 @itemx --disable-win32-registry
1420 The @option{--enable-win32-registry} option enables Microsoft Windows-hosted GCC
1421 to look up installations paths in the registry using the following key:
1424 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
1427 @var{key} defaults to GCC version number, and can be overridden by the
1428 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
1429 who use custom installers are encouraged to provide a different key,
1430 perhaps one comprised of vendor name and GCC version number, to
1431 avoid conflict with existing installations. This feature is enabled
1432 by default, and can be disabled by @option{--disable-win32-registry}
1433 option. This option has no effect on the other hosts.
1436 Specify that the machine does not have a floating point unit. This
1437 option only applies to @samp{m68k-sun-sunos@var{n}}. On any other
1438 system, @option{--nfp} has no effect.
1440 @item --enable-werror
1441 @itemx --disable-werror
1442 @itemx --enable-werror=yes
1443 @itemx --enable-werror=no
1444 When you specify this option, it controls whether certain files in the
1445 compiler are built with @option{-Werror} in bootstrap stage2 and later.
1446 If you don't specify it, @option{-Werror} is turned on for the main
1447 development trunk. However it defaults to off for release branches and
1448 final releases. The specific files which get @option{-Werror} are
1449 controlled by the Makefiles.
1451 @item --enable-checking
1452 @itemx --enable-checking=@var{list}
1453 When you specify this option, the compiler is built to perform internal
1454 consistency checks of the requested complexity. This does not change the
1455 generated code, but adds error checking within the compiler. This will
1456 slow down the compiler and may only work properly if you are building
1457 the compiler with GCC@. This is @samp{yes} by default when building
1458 from SVN or snapshots, but @samp{release} for releases. The default
1459 for building the stage1 compiler is @samp{yes}. More control
1460 over the checks may be had by specifying @var{list}. The categories of
1461 checks available are @samp{yes} (most common checks
1462 @samp{assert,misc,tree,gc,rtlflag,runtime}), @samp{no} (no checks at
1463 all), @samp{all} (all but @samp{valgrind}), @samp{release} (cheapest
1464 checks @samp{assert,runtime}) or @samp{none} (same as @samp{no}).
1465 Individual checks can be enabled with these flags @samp{assert},
1466 @samp{df}, @samp{fold}, @samp{gc}, @samp{gcac} @samp{misc}, @samp{rtl},
1467 @samp{rtlflag}, @samp{runtime}, @samp{tree}, and @samp{valgrind}.
1469 The @samp{valgrind} check requires the external @command{valgrind}
1470 simulator, available from @uref{http://valgrind.org/}. The
1471 @samp{df}, @samp{rtl}, @samp{gcac} and @samp{valgrind} checks are very expensive.
1472 To disable all checking, @samp{--disable-checking} or
1473 @samp{--enable-checking=none} must be explicitly requested. Disabling
1474 assertions will make the compiler and runtime slightly faster but
1475 increase the risk of undetected internal errors causing wrong code to be
1478 @item --disable-stage1-checking
1479 @itemx --enable-stage1-checking
1480 @itemx --enable-stage1-checking=@var{list}
1481 If no @option{--enable-checking} option is specified the stage1
1482 compiler will be built with @samp{yes} checking enabled, otherwise
1483 the stage1 checking flags are the same as specified by
1484 @option{--enable-checking}. To build the stage1 compiler with
1485 different checking options use @option{--enable-stage1-checking}.
1486 The list of checking options is the same as for @option{--enable-checking}.
1487 If your system is too slow or too small to bootstrap a released compiler
1488 with checking for stage1 enabled, you can use @samp{--disable-stage1-checking}
1489 to disable checking for the stage1 compiler.
1491 @item --enable-coverage
1492 @itemx --enable-coverage=@var{level}
1493 With this option, the compiler is built to collect self coverage
1494 information, every time it is run. This is for internal development
1495 purposes, and only works when the compiler is being built with gcc. The
1496 @var{level} argument controls whether the compiler is built optimized or
1497 not, values are @samp{opt} and @samp{noopt}. For coverage analysis you
1498 want to disable optimization, for performance analysis you want to
1499 enable optimization. When coverage is enabled, the default level is
1500 without optimization.
1502 @item --enable-gather-detailed-mem-stats
1503 When this option is specified more detailed information on memory
1504 allocation is gathered. This information is printed when using
1505 @option{-fmem-report}.
1508 @itemx --with-gc=@var{choice}
1509 With this option you can specify the garbage collector implementation
1510 used during the compilation process. @var{choice} can be one of
1511 @samp{page} and @samp{zone}, where @samp{page} is the default.
1514 @itemx --disable-nls
1515 The @option{--enable-nls} option enables Native Language Support (NLS),
1516 which lets GCC output diagnostics in languages other than American
1517 English. Native Language Support is enabled by default if not doing a
1518 canadian cross build. The @option{--disable-nls} option disables NLS@.
1520 @item --with-included-gettext
1521 If NLS is enabled, the @option{--with-included-gettext} option causes the build
1522 procedure to prefer its copy of GNU @command{gettext}.
1524 @item --with-catgets
1525 If NLS is enabled, and if the host lacks @code{gettext} but has the
1526 inferior @code{catgets} interface, the GCC build procedure normally
1527 ignores @code{catgets} and instead uses GCC's copy of the GNU
1528 @code{gettext} library. The @option{--with-catgets} option causes the
1529 build procedure to use the host's @code{catgets} in this situation.
1531 @item --with-libiconv-prefix=@var{dir}
1532 Search for libiconv header files in @file{@var{dir}/include} and
1533 libiconv library files in @file{@var{dir}/lib}.
1535 @item --enable-obsolete
1536 Enable configuration for an obsoleted system. If you attempt to
1537 configure GCC for a system (build, host, or target) which has been
1538 obsoleted, and you do not specify this flag, configure will halt with an
1541 All support for systems which have been obsoleted in one release of GCC
1542 is removed entirely in the next major release, unless someone steps
1543 forward to maintain the port.
1545 @item --enable-decimal-float
1546 @itemx --enable-decimal-float=yes
1547 @itemx --enable-decimal-float=no
1548 @itemx --enable-decimal-float=bid
1549 @itemx --enable-decimal-float=dpd
1550 @itemx --disable-decimal-float
1551 Enable (or disable) support for the C decimal floating point extension
1552 that is in the IEEE 754-2008 standard. This is enabled by default only
1553 on PowerPC, i386, and x86_64 GNU/Linux systems. Other systems may also
1554 support it, but require the user to specifically enable it. You can
1555 optionally control which decimal floating point format is used (either
1556 @samp{bid} or @samp{dpd}). The @samp{bid} (binary integer decimal)
1557 format is default on i386 and x86_64 systems, and the @samp{dpd}
1558 (densely packed decimal) format is default on PowerPC systems.
1560 @item --enable-fixed-point
1561 @itemx --disable-fixed-point
1562 Enable (or disable) support for C fixed-point arithmetic.
1563 This option is enabled by default for some targets (such as MIPS) which
1564 have hardware-support for fixed-point operations. On other targets, you
1565 may enable this option manually.
1567 @item --with-long-double-128
1568 Specify if @code{long double} type should be 128-bit by default on selected
1569 GNU/Linux architectures. If using @code{--without-long-double-128},
1570 @code{long double} will be by default 64-bit, the same as @code{double} type.
1571 When neither of these configure options are used, the default will be
1572 128-bit @code{long double} when built against GNU C Library 2.4 and later,
1573 64-bit @code{long double} otherwise.
1575 @item --with-gmp=@var{pathname}
1576 @itemx --with-gmp-include=@var{pathname}
1577 @itemx --with-gmp-lib=@var{pathname}
1578 @itemx --with-mpfr=@var{pathname}
1579 @itemx --with-mpfr-include=@var{pathname}
1580 @itemx --with-mpfr-lib=@var{pathname}
1581 @itemx --with-mpc=@var{pathname}
1582 @itemx --with-mpc-include=@var{pathname}
1583 @itemx --with-mpc-lib=@var{pathname}
1584 If you do not have GMP (the GNU Multiple Precision library), the MPFR
1585 library and/or the MPC library installed in a standard location and
1586 you want to build GCC, you can explicitly specify the directory where
1587 they are installed (@samp{--with-gmp=@var{gmpinstalldir}},
1588 @samp{--with-mpfr=@/@var{mpfrinstalldir}},
1589 @samp{--with-mpc=@/@var{mpcinstalldir}}). The
1590 @option{--with-gmp=@/@var{gmpinstalldir}} option is shorthand for
1591 @option{--with-gmp-lib=@/@var{gmpinstalldir}/lib} and
1592 @option{--with-gmp-include=@/@var{gmpinstalldir}/include}. Likewise the
1593 @option{--with-mpfr=@/@var{mpfrinstalldir}} option is shorthand for
1594 @option{--with-mpfr-lib=@/@var{mpfrinstalldir}/lib} and
1595 @option{--with-mpfr-include=@/@var{mpfrinstalldir}/include}, also the
1596 @option{--with-mpc=@/@var{mpcinstalldir}} option is shorthand for
1597 @option{--with-mpc-lib=@/@var{mpcinstalldir}/lib} and
1598 @option{--with-mpc-include=@/@var{mpcinstalldir}/include}. If these
1599 shorthand assumptions are not correct, you can use the explicit
1600 include and lib options directly. You might also need to ensure the
1601 shared libraries can be found by the dynamic linker when building and
1602 using GCC, for example by setting the runtime shared library path
1603 variable (@env{LD_LIBRARY_PATH} on GNU/Linux and Solaris systems).
1605 These flags are applicable to the host platform only. When building
1606 a cross compiler, they will not be used to configure target libraries.
1608 @item --with-ppl=@var{pathname}
1609 @itemx --with-ppl-include=@var{pathname}
1610 @itemx --with-ppl-lib=@var{pathname}
1611 @itemx --with-cloog=@var{pathname}
1612 @itemx --with-cloog-include=@var{pathname}
1613 @itemx --with-cloog-lib=@var{pathname}
1614 If you do not have PPL (the Parma Polyhedra Library) and the CLooG
1615 libraries installed in a standard location and you want to build GCC,
1616 you can explicitly specify the directory where they are installed
1617 (@samp{--with-ppl=@/@var{pplinstalldir}},
1618 @samp{--with-cloog=@/@var{clooginstalldir}}). The
1619 @option{--with-ppl=@/@var{pplinstalldir}} option is shorthand for
1620 @option{--with-ppl-lib=@/@var{pplinstalldir}/lib} and
1621 @option{--with-ppl-include=@/@var{pplinstalldir}/include}. Likewise the
1622 @option{--with-cloog=@/@var{clooginstalldir}} option is shorthand for
1623 @option{--with-cloog-lib=@/@var{clooginstalldir}/lib} and
1624 @option{--with-cloog-include=@/@var{clooginstalldir}/include}. If these
1625 shorthand assumptions are not correct, you can use the explicit
1626 include and lib options directly.
1628 These flags are applicable to the host platform only. When building
1629 a cross compiler, they will not be used to configure target libraries.
1631 @item --with-host-libstdcxx=@var{linker-args}
1632 If you are linking with a static copy of PPL, you can use this option
1633 to specify how the linker should find the standard C++ library used
1634 internally by PPL. Typical values of @var{linker-args} might be
1635 @samp{-lstdc++} or @samp{-Wl,-Bstatic,-lstdc++,-Bdynamic -lm}. If you are
1636 linking with a shared copy of PPL, you probably do not need this
1637 option; shared library dependencies will cause the linker to search
1638 for the standard C++ library automatically.
1640 @item --with-stage1-ldflags=@var{flags}
1641 This option may be used to set linker flags to be used when linking
1642 stage 1 of GCC. These are also used when linking GCC if configured with
1643 @option{--disable-bootstrap}. By default no special flags are used.
1645 @item --with-stage1-libs=@var{libs}
1646 This option may be used to set libraries to be used when linking stage 1
1647 of GCC. These are also used when linking GCC if configured with
1648 @option{--disable-bootstrap}. The default is the argument to
1649 @option{--with-host-libstdcxx}, if specified.
1651 @item --with-boot-ldflags=@var{flags}
1652 This option may be used to set linker flags to be used when linking
1653 stage 2 and later when bootstrapping GCC. If neither --with-boot-libs
1654 nor --with-host-libstdcxx is set to a value, then the default is
1655 @samp{-static-libstdc++ -static-libgcc}.
1657 @item --with-boot-libs=@var{libs}
1658 This option may be used to set libraries to be used when linking stage 2
1659 and later when bootstrapping GCC. The default is the argument to
1660 @option{--with-host-libstdcxx}, if specified.
1662 @item --with-debug-prefix-map=@var{map}
1663 Convert source directory names using @option{-fdebug-prefix-map} when
1664 building runtime libraries. @samp{@var{map}} is a space-separated
1665 list of maps of the form @samp{@var{old}=@var{new}}.
1667 @item --enable-linker-build-id
1668 Tells GCC to pass @option{--build-id} option to the linker for all final
1669 links (links performed without the @option{-r} or @option{--relocatable}
1670 option), if the linker supports it. If you specify
1671 @option{--enable-linker-build-id}, but your linker does not
1672 support @option{--build-id} option, a warning is issued and the
1673 @option{--enable-linker-build-id} option is ignored. The default is off.
1675 @item --with-linker-hash-style=@var{choice}
1676 Tells GCC to pass @option{--hash-style=@var{choice}} option to the
1677 linker for all final links. @var{choice} can be one of
1678 @samp{sysv}, @samp{gnu}, and @samp{both} where @samp{sysv} is the default.
1680 @item --enable-gnu-unique-object
1681 @itemx --disable-gnu-unique-object
1682 Tells GCC to use the gnu_unique_object relocation for C++ template
1683 static data members and inline function local statics. Enabled by
1684 default for a native toolchain with an assembler that accepts it and
1685 GLIBC 2.11 or above, otherwise disabled.
1688 @itemx --disable-lto
1689 Enable support for link-time optimization (LTO). This is enabled by
1690 default, and may be disabled using @option{--disable-lto}.
1692 @item --with-plugin-ld=@var{pathname}
1693 Enable an alternate linker to be used at link-time optimization (LTO)
1694 link time when @option{-fuse-linker-plugin} is enabled.
1695 This linker should have plugin support such as gold starting with
1696 version 2.20 or GNU ld starting with version 2.21.
1697 See @option{-fuse-linker-plugin} for details.
1700 @subheading Cross-Compiler-Specific Options
1701 The following options only apply to building cross compilers.
1704 @item --with-sysroot
1705 @itemx --with-sysroot=@var{dir}
1706 Tells GCC to consider @var{dir} as the root of a tree that contains
1707 (a subset of) the root filesystem of the target operating system.
1708 Target system headers, libraries and run-time object files will be
1709 searched in there. More specifically, this acts as if
1710 @option{--sysroot=@var{dir}} was added to the default options of the built
1711 compiler. The specified directory is not copied into the
1712 install tree, unlike the options @option{--with-headers} and
1713 @option{--with-libs} that this option obsoletes. The default value,
1714 in case @option{--with-sysroot} is not given an argument, is
1715 @option{$@{gcc_tooldir@}/sys-root}. If the specified directory is a
1716 subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to
1717 the GCC binaries if the installation tree is moved.
1719 This option affects the system root for the compiler used to build
1720 target libraries (which runs on the build system) and the compiler newly
1721 installed with @code{make install}; it does not affect the compiler which is
1722 used to build GCC itself.
1724 @item --with-build-sysroot
1725 @itemx --with-build-sysroot=@var{dir}
1726 Tells GCC to consider @var{dir} as the system root (see
1727 @option{--with-sysroot}) while building target libraries, instead of
1728 the directory specified with @option{--with-sysroot}. This option is
1729 only useful when you are already using @option{--with-sysroot}. You
1730 can use @option{--with-build-sysroot} when you are configuring with
1731 @option{--prefix} set to a directory that is different from the one in
1732 which you are installing GCC and your target libraries.
1734 This option affects the system root for the compiler used to build
1735 target libraries (which runs on the build system); it does not affect
1736 the compiler which is used to build GCC itself.
1738 @item --with-headers
1739 @itemx --with-headers=@var{dir}
1740 Deprecated in favor of @option{--with-sysroot}.
1741 Specifies that target headers are available when building a cross compiler.
1742 The @var{dir} argument specifies a directory which has the target include
1743 files. These include files will be copied into the @file{gcc} install
1744 directory. @emph{This option with the @var{dir} argument is required} when
1745 building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include}
1746 doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does
1747 pre-exist, the @var{dir} argument may be omitted. @command{fixincludes}
1748 will be run on these files to make them compatible with GCC@.
1750 @item --without-headers
1751 Tells GCC not use any target headers from a libc when building a cross
1752 compiler. When crossing to GNU/Linux, you need the headers so GCC
1753 can build the exception handling for libgcc.
1756 @itemx --with-libs="@var{dir1} @var{dir2} @dots{} @var{dirN}"
1757 Deprecated in favor of @option{--with-sysroot}.
1758 Specifies a list of directories which contain the target runtime
1759 libraries. These libraries will be copied into the @file{gcc} install
1760 directory. If the directory list is omitted, this option has no
1764 Specifies that @samp{newlib} is
1765 being used as the target C library. This causes @code{__eprintf} to be
1766 omitted from @file{libgcc.a} on the assumption that it will be provided by
1769 @item --with-build-time-tools=@var{dir}
1770 Specifies where to find the set of target tools (assembler, linker, etc.)
1771 that will be used while building GCC itself. This option can be useful
1772 if the directory layouts are different between the system you are building
1773 GCC on, and the system where you will deploy it.
1775 For example, on an @samp{ia64-hp-hpux} system, you may have the GNU
1776 assembler and linker in @file{/usr/bin}, and the native tools in a
1777 different path, and build a toolchain that expects to find the
1778 native tools in @file{/usr/bin}.
1780 When you use this option, you should ensure that @var{dir} includes
1781 @command{ar}, @command{as}, @command{ld}, @command{nm},
1782 @command{ranlib} and @command{strip} if necessary, and possibly
1783 @command{objdump}. Otherwise, GCC may use an inconsistent set of
1787 @subheading Java-Specific Options
1789 The following option applies to the build of the Java front end.
1792 @item --disable-libgcj
1793 Specify that the run-time libraries
1794 used by GCJ should not be built. This is useful in case you intend
1795 to use GCJ with some other run-time, or you're going to install it
1796 separately, or it just happens not to build on your particular
1797 machine. In general, if the Java front end is enabled, the GCJ
1798 libraries will be enabled too, unless they're known to not work on
1799 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
1800 may need to port it; in this case, before modifying the top-level
1801 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
1802 you may use @option{--enable-libgcj} to override the default.
1806 The following options apply to building @samp{libgcj}.
1808 @subsubheading General Options
1811 @item --enable-java-maintainer-mode
1812 By default the @samp{libjava} build will not attempt to compile the
1813 @file{.java} source files to @file{.class}. Instead, it will use the
1814 @file{.class} files from the source tree. If you use this option you
1815 must have executables named @command{ecj1} and @command{gjavah} in your path
1816 for use by the build. You must use this option if you intend to
1817 modify any @file{.java} files in @file{libjava}.
1819 @item --with-java-home=@var{dirname}
1820 This @samp{libjava} option overrides the default value of the
1821 @samp{java.home} system property. It is also used to set
1822 @samp{sun.boot.class.path} to @file{@var{dirname}/lib/rt.jar}. By
1823 default @samp{java.home} is set to @file{@var{prefix}} and
1824 @samp{sun.boot.class.path} to
1825 @file{@var{datadir}/java/libgcj-@var{version}.jar}.
1827 @item --with-ecj-jar=@var{filename}
1828 This option can be used to specify the location of an external jar
1829 file containing the Eclipse Java compiler. A specially modified
1830 version of this compiler is used by @command{gcj} to parse
1831 @file{.java} source files. If this option is given, the
1832 @samp{libjava} build will create and install an @file{ecj1} executable
1833 which uses this jar file at runtime.
1835 If this option is not given, but an @file{ecj.jar} file is found in
1836 the topmost source tree at configure time, then the @samp{libgcj}
1837 build will create and install @file{ecj1}, and will also install the
1838 discovered @file{ecj.jar} into a suitable place in the install tree.
1840 If @file{ecj1} is not installed, then the user will have to supply one
1841 on his path in order for @command{gcj} to properly parse @file{.java}
1842 source files. A suitable jar is available from
1843 @uref{ftp://sourceware.org/pub/java/}.
1845 @item --disable-getenv-properties
1846 Don't set system properties from @env{GCJ_PROPERTIES}.
1848 @item --enable-hash-synchronization
1849 Use a global hash table for monitor locks. Ordinarily,
1850 @samp{libgcj}'s @samp{configure} script automatically makes
1851 the correct choice for this option for your platform. Only use
1852 this if you know you need the library to be configured differently.
1854 @item --enable-interpreter
1855 Enable the Java interpreter. The interpreter is automatically
1856 enabled by default on all platforms that support it. This option
1857 is really only useful if you want to disable the interpreter
1858 (using @option{--disable-interpreter}).
1860 @item --disable-java-net
1861 Disable java.net. This disables the native part of java.net only,
1862 using non-functional stubs for native method implementations.
1864 @item --disable-jvmpi
1865 Disable JVMPI support.
1867 @item --disable-libgcj-bc
1868 Disable BC ABI compilation of certain parts of libgcj. By default,
1869 some portions of libgcj are compiled with @option{-findirect-dispatch}
1870 and @option{-fno-indirect-classes}, allowing them to be overridden at
1873 If @option{--disable-libgcj-bc} is specified, libgcj is built without
1874 these options. This allows the compile-time linker to resolve
1875 dependencies when statically linking to libgcj. However it makes it
1876 impossible to override the affected portions of libgcj at run-time.
1878 @item --enable-reduced-reflection
1879 Build most of libgcj with @option{-freduced-reflection}. This reduces
1880 the size of libgcj at the expense of not being able to do accurate
1881 reflection on the classes it contains. This option is safe if you
1882 know that code using libgcj will never use reflection on the standard
1883 runtime classes in libgcj (including using serialization, RMI or CORBA).
1886 Enable runtime eCos target support.
1888 @item --without-libffi
1889 Don't use @samp{libffi}. This will disable the interpreter and JNI
1890 support as well, as these require @samp{libffi} to work.
1892 @item --enable-libgcj-debug
1893 Enable runtime debugging code.
1895 @item --enable-libgcj-multifile
1896 If specified, causes all @file{.java} source files to be
1897 compiled into @file{.class} files in one invocation of
1898 @samp{gcj}. This can speed up build time, but is more
1899 resource-intensive. If this option is unspecified or
1900 disabled, @samp{gcj} is invoked once for each @file{.java}
1901 file to compile into a @file{.class} file.
1903 @item --with-libiconv-prefix=DIR
1904 Search for libiconv in @file{DIR/include} and @file{DIR/lib}.
1906 @item --enable-sjlj-exceptions
1907 Force use of the @code{setjmp}/@code{longjmp}-based scheme for exceptions.
1908 @samp{configure} ordinarily picks the correct value based on the platform.
1909 Only use this option if you are sure you need a different setting.
1911 @item --with-system-zlib
1912 Use installed @samp{zlib} rather than that included with GCC@.
1914 @item --with-win32-nlsapi=ansi, unicows or unicode
1915 Indicates how MinGW @samp{libgcj} translates between UNICODE
1916 characters and the Win32 API@.
1918 @item --enable-java-home
1919 If enabled, this creates a JPackage compatible SDK environment during install.
1920 Note that if --enable-java-home is used, --with-arch-directory=ARCH must also
1923 @item --with-arch-directory=ARCH
1924 Specifies the name to use for the @file{jre/lib/ARCH} directory in the SDK
1925 environment created when --enable-java-home is passed. Typical names for this
1926 directory include i386, amd64, ia64, etc.
1928 @item --with-os-directory=DIR
1929 Specifies the OS directory for the SDK include directory. This is set to auto
1930 detect, and is typically 'linux'.
1932 @item --with-origin-name=NAME
1933 Specifies the JPackage origin name. This defaults to the 'gcj' in
1936 @item --with-arch-suffix=SUFFIX
1937 Specifies the suffix for the sdk directory. Defaults to the empty string.
1938 Examples include '.x86_64' in 'java-1.5.0-gcj-1.5.0.0.x86_64'.
1940 @item --with-jvm-root-dir=DIR
1941 Specifies where to install the SDK. Default is $(prefix)/lib/jvm.
1943 @item --with-jvm-jar-dir=DIR
1944 Specifies where to install jars. Default is $(prefix)/lib/jvm-exports.
1946 @item --with-python-dir=DIR
1947 Specifies where to install the Python modules used for aot-compile. DIR should
1948 not include the prefix used in installation. For example, if the Python modules
1949 are to be installed in /usr/lib/python2.5/site-packages, then
1950 --with-python-dir=/lib/python2.5/site-packages should be passed. If this is
1951 not specified, then the Python modules are installed in $(prefix)/share/python.
1953 @item --enable-aot-compile-rpm
1954 Adds aot-compile-rpm to the list of installed scripts.
1956 @item --enable-browser-plugin
1957 Build the gcjwebplugin web browser plugin.
1961 Use the single-byte @code{char} and the Win32 A functions natively,
1962 translating to and from UNICODE when using these functions. If
1963 unspecified, this is the default.
1966 Use the @code{WCHAR} and Win32 W functions natively. Adds
1967 @code{-lunicows} to @file{libgcj.spec} to link with @samp{libunicows}.
1968 @file{unicows.dll} needs to be deployed on Microsoft Windows 9X machines
1969 running built executables. @file{libunicows.a}, an open-source
1970 import library around Microsoft's @code{unicows.dll}, is obtained from
1971 @uref{http://libunicows.sourceforge.net/}, which also gives details
1972 on getting @file{unicows.dll} from Microsoft.
1975 Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not}
1976 add @code{-lunicows} to @file{libgcj.spec}. The built executables will
1977 only run on Microsoft Windows NT and above.
1981 @subsubheading AWT-Specific Options
1985 Use the X Window System.
1987 @item --enable-java-awt=PEER(S)
1988 Specifies the AWT peer library or libraries to build alongside
1989 @samp{libgcj}. If this option is unspecified or disabled, AWT
1990 will be non-functional. Current valid values are @option{gtk} and
1991 @option{xlib}. Multiple libraries should be separated by a
1992 comma (i.e.@: @option{--enable-java-awt=gtk,xlib}).
1994 @item --enable-gtk-cairo
1995 Build the cairo Graphics2D implementation on GTK@.
1997 @item --enable-java-gc=TYPE
1998 Choose garbage collector. Defaults to @option{boehm} if unspecified.
2000 @item --disable-gtktest
2001 Do not try to compile and run a test GTK+ program.
2003 @item --disable-glibtest
2004 Do not try to compile and run a test GLIB program.
2006 @item --with-libart-prefix=PFX
2007 Prefix where libart is installed (optional).
2009 @item --with-libart-exec-prefix=PFX
2010 Exec prefix where libart is installed (optional).
2012 @item --disable-libarttest
2013 Do not try to compile and run a test libart program.
2017 @subsubheading Overriding @command{configure} test results
2019 Sometimes, it might be necessary to override the result of some
2020 @command{configure} test, for example in order to ease porting to a new
2021 system or work around a bug in a test. The toplevel @command{configure}
2022 script provides three variables for this:
2026 @item build_configargs
2027 @cindex @code{build_configargs}
2028 The contents of this variable is passed to all build @command{configure}
2031 @item host_configargs
2032 @cindex @code{host_configargs}
2033 The contents of this variable is passed to all host @command{configure}
2036 @item target_configargs
2037 @cindex @code{target_configargs}
2038 The contents of this variable is passed to all target @command{configure}
2043 In order to avoid shell and @command{make} quoting issues for complex
2044 overrides, you can pass a setting for @env{CONFIG_SITE} and set
2045 variables in the site file.
2052 @uref{./index.html,,Return to the GCC Installation page}
2056 @c ***Building****************************************************************
2058 @comment node-name, next, previous, up
2059 @node Building, Testing, Configuration, Installing GCC
2065 @cindex Installing GCC: Building
2067 Now that GCC is configured, you are ready to build the compiler and
2070 Some commands executed when making the compiler may fail (return a
2071 nonzero status) and be ignored by @command{make}. These failures, which
2072 are often due to files that were not found, are expected, and can safely
2075 It is normal to have compiler warnings when compiling certain files.
2076 Unless you are a GCC developer, you can generally ignore these warnings
2077 unless they cause compilation to fail. Developers should attempt to fix
2078 any warnings encountered, however they can temporarily continue past
2079 warnings-as-errors by specifying the configure flag
2080 @option{--disable-werror}.
2082 On certain old systems, defining certain environment variables such as
2083 @env{CC} can interfere with the functioning of @command{make}.
2085 If you encounter seemingly strange errors when trying to build the
2086 compiler in a directory other than the source directory, it could be
2087 because you have previously configured the compiler in the source
2088 directory. Make sure you have done all the necessary preparations.
2090 If you build GCC on a BSD system using a directory stored in an old System
2091 V file system, problems may occur in running @command{fixincludes} if the
2092 System V file system doesn't support symbolic links. These problems
2093 result in a failure to fix the declaration of @code{size_t} in
2094 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
2095 that type mismatches occur, this could be the cause.
2097 The solution is not to use such a directory for building GCC@.
2099 Similarly, when building from SVN or snapshots, or if you modify
2100 @file{*.l} files, you need the Flex lexical analyzer generator
2101 installed. If you do not modify @file{*.l} files, releases contain
2102 the Flex-generated files and you do not need Flex installed to build
2103 them. There is still one Flex-based lexical analyzer (part of the
2104 build machinery, not of GCC itself) that is used even if you only
2105 build the C front end.
2107 When building from SVN or snapshots, or if you modify Texinfo
2108 documentation, you need version 4.7 or later of Texinfo installed if you
2109 want Info documentation to be regenerated. Releases contain Info
2110 documentation pre-built for the unmodified documentation in the release.
2112 @section Building a native compiler
2114 For a native build, the default configuration is to perform
2115 a 3-stage bootstrap of the compiler when @samp{make} is invoked.
2116 This will build the entire GCC system and ensure that it compiles
2117 itself correctly. It can be disabled with the @option{--disable-bootstrap}
2118 parameter to @samp{configure}, but bootstrapping is suggested because
2119 the compiler will be tested more completely and could also have
2122 The bootstrapping process will complete the following steps:
2126 Build tools necessary to build the compiler.
2129 Perform a 3-stage bootstrap of the compiler. This includes building
2130 three times the target tools for use by the compiler such as binutils
2131 (bfd, binutils, gas, gprof, ld, and opcodes) if they have been
2132 individually linked or moved into the top level GCC source tree before
2136 Perform a comparison test of the stage2 and stage3 compilers.
2139 Build runtime libraries using the stage3 compiler from the previous step.
2143 If you are short on disk space you might consider @samp{make
2144 bootstrap-lean} instead. The sequence of compilation is the
2145 same described above, but object files from the stage1 and
2146 stage2 of the 3-stage bootstrap of the compiler are deleted as
2147 soon as they are no longer needed.
2149 If you wish to use non-default GCC flags when compiling the stage2
2150 and stage3 compilers, set @code{BOOT_CFLAGS} on the command line when
2151 doing @samp{make}. For example, if you want to save additional space
2152 during the bootstrap and in the final installation as well, you can
2153 build the compiler binaries without debugging information as in the
2154 following example. This will save roughly 40% of disk space both for
2155 the bootstrap and the final installation. (Libraries will still contain
2156 debugging information.)
2159 make BOOT_CFLAGS='-O' bootstrap
2162 You can place non-default optimization flags into @code{BOOT_CFLAGS}; they
2163 are less well tested here than the default of @samp{-g -O2}, but should
2164 still work. In a few cases, you may find that you need to specify special
2165 flags such as @option{-msoft-float} here to complete the bootstrap; or,
2166 if the native compiler miscompiles the stage1 compiler, you may need
2167 to work around this, by choosing @code{BOOT_CFLAGS} to avoid the parts
2168 of the stage1 compiler that were miscompiled, or by using @samp{make
2169 bootstrap4} to increase the number of stages of bootstrap.
2171 @code{BOOT_CFLAGS} does not apply to bootstrapped target libraries.
2172 Since these are always compiled with the compiler currently being
2173 bootstrapped, you can use @code{CFLAGS_FOR_TARGET} to modify their
2174 compilation flags, as for non-bootstrapped target libraries.
2175 Again, if the native compiler miscompiles the stage1 compiler, you may
2176 need to work around this by avoiding non-working parts of the stage1
2177 compiler. Use @code{STAGE1_TFLAGS} to this end.
2179 If you used the flag @option{--enable-languages=@dots{}} to restrict
2180 the compilers to be built, only those you've actually enabled will be
2181 built. This will of course only build those runtime libraries, for
2182 which the particular compiler has been built. Please note,
2183 that re-defining @env{LANGUAGES} when calling @samp{make}
2184 @strong{does not} work anymore!
2186 If the comparison of stage2 and stage3 fails, this normally indicates
2187 that the stage2 compiler has compiled GCC incorrectly, and is therefore
2188 a potentially serious bug which you should investigate and report. (On
2189 a few systems, meaningful comparison of object files is impossible; they
2190 always appear ``different''. If you encounter this problem, you will
2191 need to disable comparison in the @file{Makefile}.)
2193 If you do not want to bootstrap your compiler, you can configure with
2194 @option{--disable-bootstrap}. In particular cases, you may want to
2195 bootstrap your compiler even if the target system is not the same as
2196 the one you are building on: for example, you could build a
2197 @code{powerpc-unknown-linux-gnu} toolchain on a
2198 @code{powerpc64-unknown-linux-gnu} host. In this case, pass
2199 @option{--enable-bootstrap} to the configure script.
2201 @code{BUILD_CONFIG} can be used to bring in additional customization
2202 to the build. It can be set to a whitespace-separated list of names.
2203 For each such @code{NAME}, top-level @file{config/@code{NAME}.mk} will
2204 be included by the top-level @file{Makefile}, bringing in any settings
2205 it contains. The default @code{BUILD_CONFIG} can be set using the
2206 configure option @option{--with-build-config=@code{NAME}...}. Some
2207 examples of supported build configurations are:
2210 @item @samp{bootstrap-O1}
2211 Removes any @option{-O}-started option from @code{BOOT_CFLAGS}, and adds
2212 @option{-O1} to it. @samp{BUILD_CONFIG=bootstrap-O1} is equivalent to
2213 @samp{BOOT_CFLAGS='-g -O1'}.
2215 @item @samp{bootstrap-O3}
2216 Analogous to @code{bootstrap-O1}.
2218 @item @samp{bootstrap-lto}
2219 Enables Link-Time Optimization for host tools during bootstrapping.
2220 @samp{BUILD_CONFIG=bootstrap-lto} is equivalent to adding
2221 @option{-flto} to @samp{BOOT_CFLAGS}.
2223 @item @samp{bootstrap-debug}
2224 Verifies that the compiler generates the same executable code, whether
2225 or not it is asked to emit debug information. To this end, this
2226 option builds stage2 host programs without debug information, and uses
2227 @file{contrib/compare-debug} to compare them with the stripped stage3
2228 object files. If @code{BOOT_CFLAGS} is overridden so as to not enable
2229 debug information, stage2 will have it, and stage3 won't. This option
2230 is enabled by default when GCC bootstrapping is enabled, if
2231 @code{strip} can turn object files compiled with and without debug
2232 info into identical object files. In addition to better test
2233 coverage, this option makes default bootstraps faster and leaner.
2235 @item @samp{bootstrap-debug-big}
2236 Rather than comparing stripped object files, as in
2237 @code{bootstrap-debug}, this option saves internal compiler dumps
2238 during stage2 and stage3 and compares them as well, which helps catch
2239 additional potential problems, but at a great cost in terms of disk
2240 space. It can be specified in addition to @samp{bootstrap-debug}.
2242 @item @samp{bootstrap-debug-lean}
2243 This option saves disk space compared with @code{bootstrap-debug-big},
2244 but at the expense of some recompilation. Instead of saving the dumps
2245 of stage2 and stage3 until the final compare, it uses
2246 @option{-fcompare-debug} to generate, compare and remove the dumps
2247 during stage3, repeating the compilation that already took place in
2248 stage2, whose dumps were not saved.
2250 @item @samp{bootstrap-debug-lib}
2251 This option tests executable code invariance over debug information
2252 generation on target libraries, just like @code{bootstrap-debug-lean}
2253 tests it on host programs. It builds stage3 libraries with
2254 @option{-fcompare-debug}, and it can be used along with any of the
2255 @code{bootstrap-debug} options above.
2257 There aren't @code{-lean} or @code{-big} counterparts to this option
2258 because most libraries are only build in stage3, so bootstrap compares
2259 would not get significant coverage. Moreover, the few libraries built
2260 in stage2 are used in stage3 host programs, so we wouldn't want to
2261 compile stage2 libraries with different options for comparison purposes.
2263 @item @samp{bootstrap-debug-ckovw}
2264 Arranges for error messages to be issued if the compiler built on any
2265 stage is run without the option @option{-fcompare-debug}. This is
2266 useful to verify the full @option{-fcompare-debug} testing coverage. It
2267 must be used along with @code{bootstrap-debug-lean} and
2268 @code{bootstrap-debug-lib}.
2270 @item @samp{bootstrap-time}
2271 Arranges for the run time of each program started by the GCC driver,
2272 built in any stage, to be logged to @file{time.log}, in the top level of
2277 @section Building a cross compiler
2279 When building a cross compiler, it is not generally possible to do a
2280 3-stage bootstrap of the compiler. This makes for an interesting problem
2281 as parts of GCC can only be built with GCC@.
2283 To build a cross compiler, we recommend first building and installing a
2284 native compiler. You can then use the native GCC compiler to build the
2285 cross compiler. The installed native compiler needs to be GCC version
2288 If the cross compiler is to be built with support for the Java
2289 programming language and the ability to compile .java source files is
2290 desired, the installed native compiler used to build the cross
2291 compiler needs to be the same GCC version as the cross compiler. In
2292 addition the cross compiler needs to be configured with
2293 @option{--with-ecj-jar=@dots{}}.
2295 Assuming you have already installed a native copy of GCC and configured
2296 your cross compiler, issue the command @command{make}, which performs the
2301 Build host tools necessary to build the compiler.
2304 Build target tools for use by the compiler such as binutils (bfd,
2305 binutils, gas, gprof, ld, and opcodes)
2306 if they have been individually linked or moved into the top level GCC source
2307 tree before configuring.
2310 Build the compiler (single stage only).
2313 Build runtime libraries using the compiler from the previous step.
2316 Note that if an error occurs in any step the make process will exit.
2318 If you are not building GNU binutils in the same source tree as GCC,
2319 you will need a cross-assembler and cross-linker installed before
2320 configuring GCC@. Put them in the directory
2321 @file{@var{prefix}/@var{target}/bin}. Here is a table of the tools
2322 you should put in this directory:
2326 This should be the cross-assembler.
2329 This should be the cross-linker.
2332 This should be the cross-archiver: a program which can manipulate
2333 archive files (linker libraries) in the target machine's format.
2336 This should be a program to construct a symbol table in an archive file.
2339 The installation of GCC will find these programs in that directory,
2340 and copy or link them to the proper place to for the cross-compiler to
2341 find them when run later.
2343 The easiest way to provide these files is to build the Binutils package.
2344 Configure it with the same @option{--host} and @option{--target}
2345 options that you use for configuring GCC, then build and install
2346 them. They install their executables automatically into the proper
2347 directory. Alas, they do not support all the targets that GCC
2350 If you are not building a C library in the same source tree as GCC,
2351 you should also provide the target libraries and headers before
2352 configuring GCC, specifying the directories with
2353 @option{--with-sysroot} or @option{--with-headers} and
2354 @option{--with-libs}. Many targets also require ``start files'' such
2355 as @file{crt0.o} and
2356 @file{crtn.o} which are linked into each executable. There may be several
2357 alternatives for @file{crt0.o}, for use with profiling or other
2358 compilation options. Check your target's definition of
2359 @code{STARTFILE_SPEC} to find out what start files it uses.
2361 @section Building in parallel
2363 GNU Make 3.80 and above, which is necessary to build GCC, support
2364 building in parallel. To activate this, you can use @samp{make -j 2}
2365 instead of @samp{make}. You can also specify a bigger number, and
2366 in most cases using a value greater than the number of processors in
2367 your machine will result in fewer and shorter I/O latency hits, thus
2368 improving overall throughput; this is especially true for slow drives
2369 and network filesystems.
2371 @section Building the Ada compiler
2373 In order to build GNAT, the Ada compiler, you need a working GNAT
2374 compiler (GCC version 4.0 or later).
2375 This includes GNAT tools such as @command{gnatmake} and
2376 @command{gnatlink}, since the Ada front end is written in Ada and
2377 uses some GNAT-specific extensions.
2379 In order to build a cross compiler, it is suggested to install
2380 the new compiler as native first, and then use it to build the cross
2383 @command{configure} does not test whether the GNAT installation works
2384 and has a sufficiently recent version; if too old a GNAT version is
2385 installed, the build will fail unless @option{--enable-languages} is
2386 used to disable building the Ada front end.
2388 @env{ADA_INCLUDE_PATH} and @env{ADA_OBJECT_PATH} environment variables
2389 must not be set when building the Ada compiler, the Ada tools, or the
2390 Ada runtime libraries. You can check that your build environment is clean
2391 by verifying that @samp{gnatls -v} lists only one explicit path in each
2394 @section Building with profile feedback
2396 It is possible to use profile feedback to optimize the compiler itself. This
2397 should result in a faster compiler binary. Experiments done on x86 using gcc
2398 3.3 showed approximately 7 percent speedup on compiling C programs. To
2399 bootstrap the compiler with profile feedback, use @code{make profiledbootstrap}.
2401 When @samp{make profiledbootstrap} is run, it will first build a @code{stage1}
2402 compiler. This compiler is used to build a @code{stageprofile} compiler
2403 instrumented to collect execution counts of instruction and branch
2404 probabilities. Then runtime libraries are compiled with profile collected.
2405 Finally a @code{stagefeedback} compiler is built using the information collected.
2407 Unlike standard bootstrap, several additional restrictions apply. The
2408 compiler used to build @code{stage1} needs to support a 64-bit integral type.
2409 It is recommended to only use GCC for this. Also parallel make is currently
2410 not supported since collisions in profile collecting may occur.
2417 @uref{./index.html,,Return to the GCC Installation page}
2421 @c ***Testing*****************************************************************
2423 @comment node-name, next, previous, up
2424 @node Testing, Final install, Building, Installing GCC
2428 @chapter Installing GCC: Testing
2431 @cindex Installing GCC: Testing
2434 Before you install GCC, we encourage you to run the testsuites and to
2435 compare your results with results from a similar configuration that have
2436 been submitted to the
2437 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
2438 Some of these archived results are linked from the build status lists
2439 at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who
2440 reports a successful build runs the testsuites and submits the results.
2441 This step is optional and may require you to download additional software,
2442 but it can give you confidence in your new GCC installation or point out
2443 problems before you install and start using your new GCC@.
2445 First, you must have @uref{download.html,,downloaded the testsuites}.
2446 These are part of the full distribution, but if you downloaded the
2447 ``core'' compiler plus any front ends, you must download the testsuites
2450 Second, you must have the testing tools installed. This includes
2451 @uref{http://www.gnu.org/software/dejagnu/,,DejaGnu}, Tcl, and Expect;
2452 the DejaGnu site has links to these.
2454 If the directories where @command{runtest} and @command{expect} were
2455 installed are not in the @env{PATH}, you may need to set the following
2456 environment variables appropriately, as in the following example (which
2457 assumes that DejaGnu has been installed under @file{/usr/local}):
2460 TCL_LIBRARY = /usr/local/share/tcl8.0
2461 DEJAGNULIBS = /usr/local/share/dejagnu
2464 (On systems such as Cygwin, these paths are required to be actual
2465 paths, not mounts or links; presumably this is due to some lack of
2466 portability in the DejaGnu code.)
2469 Finally, you can run the testsuite (which may take a long time):
2471 cd @var{objdir}; make -k check
2474 This will test various components of GCC, such as compiler
2475 front ends and runtime libraries. While running the testsuite, DejaGnu
2476 might emit some harmless messages resembling
2477 @samp{WARNING: Couldn't find the global config file.} or
2478 @samp{WARNING: Couldn't find tool init file} that can be ignored.
2480 If you are testing a cross-compiler, you may want to run the testsuite
2481 on a simulator as described at @uref{http://gcc.gnu.org/simtest-howto.html}.
2483 @section How can you run the testsuite on selected tests?
2485 In order to run sets of tests selectively, there are targets
2486 @samp{make check-gcc} and @samp{make check-g++}
2487 in the @file{gcc} subdirectory of the object directory. You can also
2488 just run @samp{make check} in a subdirectory of the object directory.
2491 A more selective way to just run all @command{gcc} execute tests in the
2495 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
2498 Likewise, in order to run only the @command{g++} ``old-deja'' tests in
2499 the testsuite with filenames matching @samp{9805*}, you would use
2502 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
2505 The @file{*.exp} files are located in the testsuite directories of the GCC
2506 source, the most important ones being @file{compile.exp},
2507 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
2508 To get a list of the possible @file{*.exp} files, pipe the
2509 output of @samp{make check} into a file and look at the
2510 @samp{Running @dots{} .exp} lines.
2512 @section Passing options and running multiple testsuites
2514 You can pass multiple options to the testsuite using the
2515 @samp{--target_board} option of DejaGNU, either passed as part of
2516 @samp{RUNTESTFLAGS}, or directly to @command{runtest} if you prefer to
2517 work outside the makefiles. For example,
2520 make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants"
2523 will run the standard @command{g++} testsuites (``unix'' is the target name
2524 for a standard native testsuite situation), passing
2525 @samp{-O3 -fmerge-constants} to the compiler on every test, i.e.,
2526 slashes separate options.
2528 You can run the testsuites multiple times using combinations of options
2529 with a syntax similar to the brace expansion of popular shells:
2532 @dots{}"--target_board=arm-sim\@{-mhard-float,-msoft-float\@}\@{-O1,-O2,-O3,\@}"
2535 (Note the empty option caused by the trailing comma in the final group.)
2536 The following will run each testsuite eight times using the @samp{arm-sim}
2537 target, as if you had specified all possible combinations yourself:
2540 --target_board=arm-sim/-mhard-float/-O1
2541 --target_board=arm-sim/-mhard-float/-O2
2542 --target_board=arm-sim/-mhard-float/-O3
2543 --target_board=arm-sim/-mhard-float
2544 --target_board=arm-sim/-msoft-float/-O1
2545 --target_board=arm-sim/-msoft-float/-O2
2546 --target_board=arm-sim/-msoft-float/-O3
2547 --target_board=arm-sim/-msoft-float
2550 They can be combined as many times as you wish, in arbitrary ways. This
2554 @dots{}"--target_board=unix/-Wextra\@{-O3,-fno-strength\@}\@{-fomit-frame,\@}"
2557 will generate four combinations, all involving @samp{-Wextra}.
2559 The disadvantage to this method is that the testsuites are run in serial,
2560 which is a waste on multiprocessor systems. For users with GNU Make and
2561 a shell which performs brace expansion, you can run the testsuites in
2562 parallel by having the shell perform the combinations and @command{make}
2563 do the parallel runs. Instead of using @samp{--target_board}, use a
2564 special makefile target:
2567 make -j@var{N} check-@var{testsuite}//@var{test-target}/@var{option1}/@var{option2}/@dots{}
2573 make -j3 check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@}
2576 will run three concurrent ``make-gcc'' testsuites, eventually testing all
2577 ten combinations as described above. Note that this is currently only
2578 supported in the @file{gcc} subdirectory. (To see how this works, try
2579 typing @command{echo} before the example given here.)
2582 @section Additional testing for Java Class Libraries
2584 The Java runtime tests can be executed via @samp{make check}
2585 in the @file{@var{target}/libjava/testsuite} directory in
2588 The @uref{http://sourceware.org/mauve/,,Mauve Project} provides
2589 a suite of tests for the Java Class Libraries. This suite can be run
2590 as part of libgcj testing by placing the Mauve tree within the libjava
2591 testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by
2592 specifying the location of that tree when invoking @samp{make}, as in
2593 @samp{make MAUVEDIR=~/mauve check}.
2595 @section How to interpret test results
2597 The result of running the testsuite are various @file{*.sum} and @file{*.log}
2598 files in the testsuite subdirectories. The @file{*.log} files contain a
2599 detailed log of the compiler invocations and the corresponding
2600 results, the @file{*.sum} files summarize the results. These summaries
2601 contain status codes for all tests:
2605 PASS: the test passed as expected
2607 XPASS: the test unexpectedly passed
2609 FAIL: the test unexpectedly failed
2611 XFAIL: the test failed as expected
2613 UNSUPPORTED: the test is not supported on this platform
2615 ERROR: the testsuite detected an error
2617 WARNING: the testsuite detected a possible problem
2620 It is normal for some tests to report unexpected failures. At the
2621 current time the testing harness does not allow fine grained control
2622 over whether or not a test is expected to fail. This problem should
2623 be fixed in future releases.
2626 @section Submitting test results
2628 If you want to report the results to the GCC project, use the
2629 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
2632 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
2633 -m gcc-testresults@@gcc.gnu.org |sh
2636 This script uses the @command{Mail} program to send the results, so
2637 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
2638 prepended to the testsuite summary and should contain any special
2639 remarks you have on your results or your build environment. Please
2640 do not edit the testsuite result block or the subject line, as these
2641 messages may be automatically processed.
2648 @uref{./index.html,,Return to the GCC Installation page}
2652 @c ***Final install***********************************************************
2654 @comment node-name, next, previous, up
2655 @node Final install, , Testing, Installing GCC
2657 @ifset finalinstallhtml
2659 @chapter Installing GCC: Final installation
2662 Now that GCC has been built (and optionally tested), you can install it with
2664 cd @var{objdir} && make install
2667 We strongly recommend to install into a target directory where there is
2668 no previous version of GCC present. Also, the GNAT runtime should not
2669 be stripped, as this would break certain features of the debugger that
2670 depend on this debugging information (catching Ada exceptions for
2673 That step completes the installation of GCC; user level binaries can
2674 be found in @file{@var{prefix}/bin} where @var{prefix} is the value
2675 you specified with the @option{--prefix} to configure (or
2676 @file{/usr/local} by default). (If you specified @option{--bindir},
2677 that directory will be used instead; otherwise, if you specified
2678 @option{--exec-prefix}, @file{@var{exec-prefix}/bin} will be used.)
2679 Headers for the C++ and Java libraries are installed in
2680 @file{@var{prefix}/include}; libraries in @file{@var{libdir}}
2681 (normally @file{@var{prefix}/lib}); internal parts of the compiler in
2682 @file{@var{libdir}/gcc} and @file{@var{libexecdir}/gcc}; documentation
2683 in info format in @file{@var{infodir}} (normally
2684 @file{@var{prefix}/info}).
2686 When installing cross-compilers, GCC's executables
2687 are not only installed into @file{@var{bindir}}, that
2688 is, @file{@var{exec-prefix}/bin}, but additionally into
2689 @file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory
2690 exists. Typically, such @dfn{tooldirs} hold target-specific
2691 binutils, including assembler and linker.
2693 Installation into a temporary staging area or into a @command{chroot}
2694 jail can be achieved with the command
2697 make DESTDIR=@var{path-to-rootdir} install
2701 where @var{path-to-rootdir} is the absolute path of
2702 a directory relative to which all installation paths will be
2703 interpreted. Note that the directory specified by @code{DESTDIR}
2704 need not exist yet; it will be created if necessary.
2706 There is a subtle point with tooldirs and @code{DESTDIR}:
2707 If you relocate a cross-compiler installation with
2708 e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory
2709 @file{@var{rootdir}/@var{exec-prefix}/@var{target-alias}/bin} will
2710 be filled with duplicated GCC executables only if it already exists,
2711 it will not be created otherwise. This is regarded as a feature,
2712 not as a bug, because it gives slightly more control to the packagers
2713 using the @code{DESTDIR} feature.
2715 You can install stripped programs and libraries with
2721 If you are bootstrapping a released version of GCC then please
2722 quickly review the build status page for your release, available from
2723 @uref{http://gcc.gnu.org/buildstat.html}.
2724 If your system is not listed for the version of GCC that you built,
2726 @email{gcc@@gcc.gnu.org} indicating
2727 that you successfully built and installed GCC@.
2728 Include the following information:
2732 Output from running @file{@var{srcdir}/config.guess}. Do not send
2733 that file itself, just the one-line output from running it.
2736 The output of @samp{gcc -v} for your newly installed @command{gcc}.
2737 This tells us which version of GCC you built and the options you passed to
2741 Whether you enabled all languages or a subset of them. If you used a
2742 full distribution then this information is part of the configure
2743 options in the output of @samp{gcc -v}, but if you downloaded the
2744 ``core'' compiler plus additional front ends then it isn't apparent
2745 which ones you built unless you tell us about it.
2748 If the build was for GNU/Linux, also include:
2751 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
2752 this information should be available from @file{/etc/issue}.
2755 The version of the Linux kernel, available from @samp{uname --version}
2759 The version of glibc you used; for RPM-based systems like Red Hat,
2760 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
2761 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
2763 For other systems, you can include similar information if you think it is
2767 Any other information that you think would be useful to people building
2768 GCC on the same configuration. The new entry in the build status list
2769 will include a link to the archived copy of your message.
2772 We'd also like to know if the
2774 @ref{Specific, host/target specific installation notes}
2777 @uref{specific.html,,host/target specific installation notes}
2779 didn't include your host/target information or if that information is
2780 incomplete or out of date. Send a note to
2781 @email{gcc@@gcc.gnu.org} detailing how the information should be changed.
2783 If you find a bug, please report it following the
2784 @uref{../bugs/,,bug reporting guidelines}.
2786 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
2787 dvi}. You will need to have @command{texi2dvi} (version at least 4.7)
2788 and @TeX{} installed. This creates a number of @file{.dvi} files in
2789 subdirectories of @file{@var{objdir}}; these may be converted for
2790 printing with programs such as @command{dvips}. Alternately, by using
2791 @samp{make pdf} in place of @samp{make dvi}, you can create documentation
2792 in the form of @file{.pdf} files; this requires @command{texi2pdf}, which
2793 is included with Texinfo version 4.8 and later. You can also
2794 @uref{http://shop.fsf.org/,,buy printed manuals from the
2795 Free Software Foundation}, though such manuals may not be for the most
2796 recent version of GCC@.
2798 If you would like to generate online HTML documentation, do @samp{cd
2799 @var{objdir}; make html} and HTML will be generated for the gcc manuals in
2800 @file{@var{objdir}/gcc/HTML}.
2807 @uref{./index.html,,Return to the GCC Installation page}
2811 @c ***Binaries****************************************************************
2813 @comment node-name, next, previous, up
2814 @node Binaries, Specific, Installing GCC, Top
2818 @chapter Installing GCC: Binaries
2821 @cindex Installing GCC: Binaries
2823 We are often asked about pre-compiled versions of GCC@. While we cannot
2824 provide these for all platforms, below you'll find links to binaries for
2825 various platforms where creating them by yourself is not easy due to various
2828 Please note that we did not create these binaries, nor do we
2829 support them. If you have any problems installing them, please
2830 contact their makers.
2837 @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX};
2840 @uref{http://pware.hvcc.edu,,Hudson Valley Community College Open Source Software for IBM System p};
2843 @uref{http://www.perzl.org/aix/,,AIX 5L and 6 Open Source Packages}.
2847 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}.
2850 Renesas H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
2851 Development Tools for the Renesas H8/300[HS] Series}.
2857 @uref{http://hpux.connect.org.uk/,,HP-UX Porting Center};
2860 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
2864 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
2865 OpenServer/Unixware}.
2868 Solaris 2 (SPARC, Intel):
2871 @uref{http://www.sunfreeware.com/,,Sunfreeware}
2874 @uref{http://www.blastwave.org/,,Blastwave}
2877 @uref{http://www.opencsw.org/,,OpenCSW}
2880 @uref{http://jupiterrise.com/tgcware/,,TGCware}
2887 @uref{http://nekochan.net/,,Nekoware}
2890 @uref{http://jupiterrise.com/tgcware/,,TGCware}
2897 The @uref{http://sourceware.org/cygwin/,,Cygwin} project;
2899 The @uref{http://www.mingw.org/,,MinGW} project.
2903 @uref{ftp://ftp.thewrittenword.com/packages/by-name/,,The
2904 Written Word} offers binaries for
2905 AIX 4.3.3, 5.1 and 5.2,
2907 Tru64 UNIX 4.0D and 5.1,
2909 HP-UX 10.20, 11.00, and 11.11, and
2910 Solaris/SPARC 2.5.1, 2.6, 7, 8, 9 and 10.
2913 @uref{http://www.openpkg.org/,,OpenPKG} offers binaries for quite a
2914 number of platforms.
2917 The @uref{http://gcc.gnu.org/wiki/GFortranBinaries,,GFortran Wiki} has
2918 links to GNU Fortran binaries for several platforms.
2926 @uref{./index.html,,Return to the GCC Installation page}
2930 @c ***Specific****************************************************************
2932 @comment node-name, next, previous, up
2933 @node Specific, Old, Binaries, Top
2937 @chapter Host/target specific installation notes for GCC
2940 @cindex Specific installation notes
2941 @cindex Target specific installation
2942 @cindex Host specific installation
2943 @cindex Target specific installation notes
2945 Please read this document carefully @emph{before} installing the
2946 GNU Compiler Collection on your machine.
2948 Note that this list of install notes is @emph{not} a list of supported
2949 hosts or targets. Not all supported hosts and targets are listed
2950 here, only the ones that require host-specific or target-specific
2956 @uref{#alpha-x-x,,alpha*-*-*}
2958 @uref{#alpha-dec-osf51,,alpha*-dec-osf5.1}
2960 @uref{#arm-x-elf,,arm-*-elf}
2964 @uref{#bfin,,Blackfin}
2968 @uref{#x-x-freebsd,,*-*-freebsd*}
2970 @uref{#h8300-hms,,h8300-hms}
2972 @uref{#hppa-hp-hpux,,hppa*-hp-hpux*}
2974 @uref{#hppa-hp-hpux10,,hppa*-hp-hpux10}
2976 @uref{#hppa-hp-hpux11,,hppa*-hp-hpux11}
2978 @uref{#x-x-linux-gnu,,*-*-linux-gnu}
2980 @uref{#ix86-x-linux,,i?86-*-linux*}
2982 @uref{#ix86-x-solaris289,,i?86-*-solaris2.[89]}
2984 @uref{#ix86-x-solaris210,,i?86-*-solaris2.10}
2986 @uref{#ia64-x-linux,,ia64-*-linux}
2988 @uref{#ia64-x-hpux,,ia64-*-hpux*}
2990 @uref{#x-ibm-aix,,*-ibm-aix*}
2992 @uref{#iq2000-x-elf,,iq2000-*-elf}
2994 @uref{#lm32-x-elf,,lm32-*-elf}
2996 @uref{#lm32-x-uclinux,,lm32-*-uclinux}
2998 @uref{#m32c-x-elf,,m32c-*-elf}
3000 @uref{#m32r-x-elf,,m32r-*-elf}
3002 @uref{#m68k-x-x,,m68k-*-*}
3004 @uref{#m68k-uclinux,,m68k-uclinux}
3006 @uref{#mep-x-elf,,mep-*-elf}
3008 @uref{#microblaze-x-elf,,microblaze-*-elf}
3010 @uref{#mips-x-x,,mips-*-*}
3012 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
3014 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
3016 @uref{#powerpc-x-x,,powerpc*-*-*}
3018 @uref{#powerpc-x-darwin,,powerpc-*-darwin*}
3020 @uref{#powerpc-x-elf,,powerpc-*-elf}
3022 @uref{#powerpc-x-linux-gnu,,powerpc*-*-linux-gnu*}
3024 @uref{#powerpc-x-netbsd,,powerpc-*-netbsd*}
3026 @uref{#powerpc-x-eabisim,,powerpc-*-eabisim}
3028 @uref{#powerpc-x-eabi,,powerpc-*-eabi}
3030 @uref{#powerpcle-x-elf,,powerpcle-*-elf}
3032 @uref{#powerpcle-x-eabisim,,powerpcle-*-eabisim}
3034 @uref{#powerpcle-x-eabi,,powerpcle-*-eabi}
3036 @uref{#s390-x-linux,,s390-*-linux*}
3038 @uref{#s390x-x-linux,,s390x-*-linux*}
3040 @uref{#s390x-ibm-tpf,,s390x-ibm-tpf*}
3042 @uref{#x-x-solaris2,,*-*-solaris2*}
3044 @uref{#sparc-x-x,,sparc*-*-*}
3046 @uref{#sparc-sun-solaris2,,sparc-sun-solaris2*}
3048 @uref{#sparc-sun-solaris210,,sparc-sun-solaris2.10}
3050 @uref{#sparc-x-linux,,sparc-*-linux*}
3052 @uref{#sparc64-x-solaris2,,sparc64-*-solaris2*}
3054 @uref{#sparcv9-x-solaris2,,sparcv9-*-solaris2*}
3056 @uref{#x-x-vxworks,,*-*-vxworks*}
3058 @uref{#x86-64-x-x,,x86_64-*-*, amd64-*-*}
3060 @uref{#xtensa-x-elf,,xtensa*-*-elf}
3062 @uref{#xtensa-x-linux,,xtensa*-*-linux*}
3064 @uref{#windows,,Microsoft Windows}
3066 @uref{#x-x-cygwin,,*-*-cygwin}
3068 @uref{#x-x-interix,,*-*-interix}
3070 @uref{#x-x-mingw32,,*-*-mingw32}
3074 @uref{#older,,Older systems}
3079 @uref{#elf,,all ELF targets} (SVR4, Solaris 2, etc.)
3085 <!-- -------- host/target specific issues start here ---------------- -->
3088 @heading @anchor{alpha-x-x}alpha*-*-*
3090 This section contains general configuration information for all
3091 alpha-based platforms using ELF (in particular, ignore this section for
3092 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
3093 section, please read all other sections that match your target.
3095 We require binutils 2.11.2 or newer.
3096 Previous binutils releases had a number of problems with DWARF 2
3097 debugging information, not the least of which is incorrect linking of
3103 @heading @anchor{alpha-dec-osf51}alpha*-dec-osf5.1
3104 Systems using processors that implement the DEC Alpha architecture and
3105 are running the DEC/Compaq/HP Unix (DEC OSF/1, Digital UNIX, or Compaq/HP
3106 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
3108 As of GCC 3.2, versions before @code{alpha*-dec-osf4} are no longer
3109 supported. (These are the versions which identify themselves as DEC
3110 OSF/1.) As of GCC 4.6, support for Tru64 UNIX V4.0 and V5.0 has been
3113 On Tru64 UNIX, virtual memory exhausted bootstrap failures
3114 may be fixed by reconfiguring Kernel Virtual Memory and Swap parameters
3115 per the @command{/usr/sbin/sys_check} Tuning Suggestions,
3116 or applying the patch in
3117 @uref{http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html}. Depending on
3118 the OS version used, you need a data segment size between 512 MB and
3119 1 GB, so simply use @command{ulimit -Sd unlimited}.
3121 As of GNU binutils 2.21, neither GNU @command{as} nor GNU @command{ld}
3122 are supported on Tru64 UNIX, so you must not configure GCC with
3123 @option{--with-gnu-as} or @option{--with-gnu-ld}.
3125 Cross-compilers for the Tru64 UNIX target currently do not work because
3126 the auxiliary programs @command{mips-tdump} and @command{mips-tfile} can't
3127 be compiled on anything but Tru64 UNIX.
3129 GCC writes a @samp{.verstamp} directive to the assembler output file
3130 unless it is built as a cross-compiler. It gets the version to use from
3131 the system header file @file{/usr/include/stamp.h}. If you install a
3132 new version of Tru64 UNIX, you should rebuild GCC to pick up the new version
3135 GCC now supports both the native (ECOFF) debugging format used by DBX
3136 and GDB and an encapsulated STABS format for use only with GDB@. See the
3137 discussion of the @option{--with-stabs} option of @file{configure} above
3138 for more information on these formats and how to select them.
3139 @c FIXME: does this work at all? If so, perhaps make default.
3141 There is a bug in DEC's assembler that produces incorrect line numbers
3142 for ECOFF format when the @samp{.align} directive is used. To work
3143 around this problem, GCC will not emit such alignment directives
3144 while writing ECOFF format debugging information even if optimization is
3145 being performed. Unfortunately, this has the very undesirable
3146 side-effect that code addresses when @option{-O} is specified are
3147 different depending on whether or not @option{-g} is also specified.
3149 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
3150 DBX@. DEC is now aware of this problem with the assembler and hopes to
3151 provide a fix shortly.
3153 @c FIXME: still applicable?
3158 @heading @anchor{arm-x-elf}arm-*-elf
3159 ARM-family processors. Subtargets that use the ELF object format
3160 require GNU binutils 2.13 or newer. Such subtargets include:
3161 @code{arm-*-freebsd}, @code{arm-*-netbsdelf}, @code{arm-*-*linux}
3162 and @code{arm-*-rtems}.
3167 @heading @anchor{avr}avr
3169 ATMEL AVR-family micro controllers. These are used in embedded
3170 applications. There are no standard Unix configurations.
3172 @xref{AVR Options,, AVR Options, gcc, Using the GNU Compiler
3176 See ``AVR Options'' in the main manual
3178 for the list of supported MCU types.
3180 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
3182 Further installation notes and other useful information about AVR tools
3183 can also be obtained from:
3187 @uref{http://www.nongnu.org/avr/,,http://www.nongnu.org/avr/}
3189 @uref{http://www.amelek.gda.pl/avr/,,http://www.amelek.gda.pl/avr/}
3192 We @emph{strongly} recommend using binutils 2.13 or newer.
3194 The following error:
3196 Error: register required
3199 indicates that you should upgrade to a newer version of the binutils.
3204 @heading @anchor{bfin}Blackfin
3206 The Blackfin processor, an Analog Devices DSP.
3208 @xref{Blackfin Options,, Blackfin Options, gcc, Using the GNU Compiler
3212 See ``Blackfin Options'' in the main manual
3215 More information, and a version of binutils with support for this processor,
3216 is available at @uref{http://blackfin.uclinux.org}
3221 @heading @anchor{cris}CRIS
3223 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
3224 series. These are used in embedded applications.
3227 @xref{CRIS Options,, CRIS Options, gcc, Using the GNU Compiler
3231 See ``CRIS Options'' in the main manual
3233 for a list of CRIS-specific options.
3235 There are a few different CRIS targets:
3238 Mainly for monolithic embedded systems. Includes a multilib for the
3239 @samp{v10} core used in @samp{ETRAX 100 LX}.
3240 @item cris-axis-linux-gnu
3241 A GNU/Linux port for the CRIS architecture, currently targeting
3242 @samp{ETRAX 100 LX} by default.
3245 For @code{cris-axis-elf} you need binutils 2.11
3246 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
3248 Pre-packaged tools can be obtained from
3249 @uref{ftp://ftp.axis.com/@/pub/@/axis/@/tools/@/cris/@/compiler-kit/}. More
3250 information about this platform is available at
3251 @uref{http://developer.axis.com/}.
3256 @heading @anchor{dos}DOS
3258 Please have a look at the @uref{binaries.html,,binaries page}.
3260 You cannot install GCC by itself on MSDOS; it will not compile under
3261 any MSDOS compiler except itself. You need to get the complete
3262 compilation package DJGPP, which includes binaries as well as sources,
3263 and includes all the necessary compilation tools and libraries.
3268 @heading @anchor{x-x-freebsd}*-*-freebsd*
3270 Support for FreeBSD 1 was discontinued in GCC 3.2. Support for
3271 FreeBSD 2 (and any mutant a.out variants of FreeBSD 3) was
3272 discontinued in GCC 4.0.
3274 In order to better utilize FreeBSD base system functionality and match
3275 the configuration of the system compiler, GCC 4.5 and above as well as
3276 GCC 4.4 past 2010-06-20 leverage SSP support in libc (which is present
3277 on FreeBSD 7 or later) and the use of @code{__cxa_atexit} by default
3278 (on FreeBSD 6 or later). The use of @code{dl_iterate_phdr} inside
3279 @file{libgcc_s.so.1} and boehm-gc (on FreeBSD 7 or later) is enabled
3280 by GCC 4.5 and above.
3282 We support FreeBSD using the ELF file format with DWARF 2 debugging
3283 for all CPU architectures. You may use @option{-gstabs} instead of
3284 @option{-g}, if you really want the old debugging format. There are
3285 no known issues with mixing object files and libraries with different
3286 debugging formats. Otherwise, this release of GCC should now match
3287 more of the configuration used in the stock FreeBSD configuration of
3288 GCC@. In particular, @option{--enable-threads} is now configured by
3289 default. However, as a general user, do not attempt to replace the
3290 system compiler with this release. Known to bootstrap and check with
3291 good results on FreeBSD 7.2-STABLE@. In the past, known to bootstrap
3292 and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4,
3293 4.5, 4.8, 4.9 and 5-CURRENT@.
3295 The version of binutils installed in @file{/usr/bin} probably works
3296 with this release of GCC@. Bootstrapping against the latest GNU
3297 binutils and/or the version found in @file{/usr/ports/devel/binutils} has
3298 been known to enable additional features and improve overall testsuite
3299 results. However, it is currently known that boehm-gc (which itself
3300 is required for java) may not configure properly on FreeBSD prior to
3301 the FreeBSD 7.0 release with GNU binutils after 2.16.1.
3306 @heading @anchor{h8300-hms}h8300-hms
3307 Renesas H8/300 series of processors.
3309 Please have a look at the @uref{binaries.html,,binaries page}.
3311 The calling convention and structure layout has changed in release 2.6.
3312 All code must be recompiled. The calling convention now passes the
3313 first three arguments in function calls in registers. Structures are no
3314 longer a multiple of 2 bytes.
3319 @heading @anchor{hppa-hp-hpux}hppa*-hp-hpux*
3320 Support for HP-UX version 9 and older was discontinued in GCC 3.4.
3322 We require using gas/binutils on all hppa platforms. Version 2.19 or
3323 later is recommended.
3325 It may be helpful to configure GCC with the
3326 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
3327 @option{--with-as=@dots{}} options to ensure that GCC can find GAS@.
3329 The HP assembler should not be used with GCC. It is rarely tested and may
3330 not work. It shouldn't be used with any languages other than C due to its
3333 Specifically, @option{-g} does not work (HP-UX uses a peculiar debugging
3334 format which GCC does not know about). It also inserts timestamps
3335 into each object file it creates, causing the 3-stage comparison test to
3336 fail during a bootstrap. You should be able to continue by saying
3337 @samp{make all-host all-target} after getting the failure from @samp{make}.
3339 Various GCC features are not supported. For example, it does not support weak
3340 symbols or alias definitions. As a result, explicit template instantiations
3341 are required when using C++. This makes it difficult if not impossible to
3342 build many C++ applications.
3344 There are two default scheduling models for instructions. These are
3345 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
3346 architecture specified for the target machine when configuring.
3347 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
3348 the target is a @samp{hppa1*} machine.
3350 The PROCESSOR_8000 model is not well suited to older processors. Thus,
3351 it is important to completely specify the machine architecture when
3352 configuring if you want a model other than PROCESSOR_8000. The macro
3353 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
3354 default scheduling model is desired.
3356 As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
3357 through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
3358 This namespace change might cause problems when bootstrapping with
3359 an earlier version of GCC or the HP compiler as essentially the same
3360 namespace is required for an entire build. This problem can be avoided
3361 in a number of ways. With HP cc, @env{UNIX_STD} can be set to @samp{95}
3362 or @samp{98}. Another way is to add an appropriate set of predefines
3363 to @env{CC}. The description for the @option{munix=} option contains
3364 a list of the predefines used with each standard.
3366 More specific information to @samp{hppa*-hp-hpux*} targets follows.
3371 @heading @anchor{hppa-hp-hpux10}hppa*-hp-hpux10
3373 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
3374 @code{PHCO_19798} from HP@.
3376 The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are
3377 used for one-only code and data. This resolves many of the previous
3378 problems in using C++ on this target. However, the ABI is not compatible
3379 with the one implemented under HP-UX 11 using secondary definitions.
3384 @heading @anchor{hppa-hp-hpux11}hppa*-hp-hpux11
3386 GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
3387 be used to compile GCC 3.0 and up.
3389 The libffi and libjava libraries haven't been ported to 64-bit HP-UX@
3392 Refer to @uref{binaries.html,,binaries} for information about obtaining
3393 precompiled GCC binaries for HP-UX@. Precompiled binaries must be obtained
3394 to build the Ada language as it can't be bootstrapped using C@. Ada is
3395 only available for the 32-bit PA-RISC runtime.
3397 Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The
3398 bundled compiler supports only traditional C; you will need either HP's
3399 unbundled compiler, or a binary distribution of GCC@.
3401 It is possible to build GCC 3.3 starting with the bundled HP compiler,
3402 but the process requires several steps. GCC 3.3 can then be used to
3403 build later versions. The fastjar program contains ISO C code and
3404 can't be built with the HP bundled compiler. This problem can be
3405 avoided by not building the Java language. For example, use the
3406 @option{--enable-languages="c,c++,f77,objc"} option in your configure
3409 There are several possible approaches to building the distribution.
3410 Binutils can be built first using the HP tools. Then, the GCC
3411 distribution can be built. The second approach is to build GCC
3412 first using the HP tools, then build binutils, then rebuild GCC@.
3413 There have been problems with various binary distributions, so it
3414 is best not to start from a binary distribution.
3416 On 64-bit capable systems, there are two distinct targets. Different
3417 installation prefixes must be used if both are to be installed on
3418 the same system. The @samp{hppa[1-2]*-hp-hpux11*} target generates code
3419 for the 32-bit PA-RISC runtime architecture and uses the HP linker.
3420 The @samp{hppa64-hp-hpux11*} target generates 64-bit code for the
3421 PA-RISC 2.0 architecture.
3423 The script config.guess now selects the target type based on the compiler
3424 detected during configuration. You must define @env{PATH} or @env{CC} so
3425 that configure finds an appropriate compiler for the initial bootstrap.
3426 When @env{CC} is used, the definition should contain the options that are
3427 needed whenever @env{CC} is used.
3429 Specifically, options that determine the runtime architecture must be
3430 in @env{CC} to correctly select the target for the build. It is also
3431 convenient to place many other compiler options in @env{CC}. For example,
3432 @env{CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"}
3433 can be used to bootstrap the GCC 3.3 branch with the HP compiler in
3434 64-bit K&R/bundled mode. The @option{+DA2.0W} option will result in
3435 the automatic selection of the @samp{hppa64-hp-hpux11*} target. The
3436 macro definition table of cpp needs to be increased for a successful
3437 build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to
3438 be defined when building with the bundled compiler, or when using the
3439 @option{-Ac} option. These defines aren't necessary with @option{-Ae}.
3441 It is best to explicitly configure the @samp{hppa64-hp-hpux11*} target
3442 with the @option{--with-ld=@dots{}} option. This overrides the standard
3443 search for ld. The two linkers supported on this target require different
3444 commands. The default linker is determined during configuration. As a
3445 result, it's not possible to switch linkers in the middle of a GCC build.
3446 This has been reported to sometimes occur in unified builds of binutils
3449 A recent linker patch must be installed for the correct operation of
3450 GCC 3.3 and later. @code{PHSS_26559} and @code{PHSS_24304} are the
3451 oldest linker patches that are known to work. They are for HP-UX
3452 11.00 and 11.11, respectively. @code{PHSS_24303}, the companion to
3453 @code{PHSS_24304}, might be usable but it hasn't been tested. These
3454 patches have been superseded. Consult the HP patch database to obtain
3455 the currently recommended linker patch for your system.
3457 The patches are necessary for the support of weak symbols on the
3458 32-bit port, and for the running of initializers and finalizers. Weak
3459 symbols are implemented using SOM secondary definition symbols. Prior
3460 to HP-UX 11, there are bugs in the linker support for secondary symbols.
3461 The patches correct a problem of linker core dumps creating shared
3462 libraries containing secondary symbols, as well as various other
3463 linking issues involving secondary symbols.
3465 GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
3466 run initializers and finalizers on the 64-bit port. The 32-bit port
3467 uses the linker @option{+init} and @option{+fini} options for the same
3468 purpose. The patches correct various problems with the +init/+fini
3469 options, including program core dumps. Binutils 2.14 corrects a
3470 problem on the 64-bit port resulting from HP's non-standard use of
3471 the .init and .fini sections for array initializers and finalizers.
3473 Although the HP and GNU linkers are both supported for the
3474 @samp{hppa64-hp-hpux11*} target, it is strongly recommended that the
3475 HP linker be used for link editing on this target.
3477 At this time, the GNU linker does not support the creation of long
3478 branch stubs. As a result, it can't successfully link binaries
3479 containing branch offsets larger than 8 megabytes. In addition,
3480 there are problems linking shared libraries, linking executables
3481 with @option{-static}, and with dwarf2 unwind and exception support.
3482 It also doesn't provide stubs for internal calls to global functions
3483 in shared libraries, so these calls can't be overloaded.
3485 The HP dynamic loader does not support GNU symbol versioning, so symbol
3486 versioning is not supported. It may be necessary to disable symbol
3487 versioning with @option{--disable-symvers} when using GNU ld.
3489 POSIX threads are the default. The optional DCE thread library is not
3490 supported, so @option{--enable-threads=dce} does not work.
3495 @heading @anchor{x-x-linux-gnu}*-*-linux-gnu
3497 Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present
3498 in glibc 2.2.5 and later. More information is available in the
3499 libstdc++-v3 documentation.
3504 @heading @anchor{ix86-x-linux}i?86-*-linux*
3506 As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
3507 See @uref{http://gcc.gnu.org/PR10877,,bug 10877} for more information.
3509 If you receive Signal 11 errors when building on GNU/Linux, then it is
3510 possible you have a hardware problem. Further information on this can be
3511 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
3516 @heading @anchor{ix86-x-solaris289}i?86-*-solaris2.[89]
3517 The Sun assembler in Solaris 8 and 9 has several bugs and limitations.
3518 While GCC works around them, several features are missing, so it is
3519 @c FIXME: which ones?
3520 recommended to use the GNU assembler instead. There is no bundled
3521 version, but the current version, from GNU binutils 2.21, is known to
3524 Solaris@tie{}2/x86 doesn't support the execution of SSE/SSE2 instructions
3525 before Solaris@tie{}9 4/04, even if the CPU supports them. Programs will
3526 receive @code{SIGILL} if they try. The fix is available both in
3527 Solaris@tie{}9 Update@tie{}6 and kernel patch 112234-12 or newer. There is no
3528 corresponding patch for Solaris 8. To avoid this problem,
3529 @option{-march} defaults to @samp{pentiumpro} on Solaris 8 and 9. If
3530 you have the patch installed, you can configure GCC with an appropriate
3531 @option{--with-arch} option, but need GNU @command{as} for SSE2 support.
3536 @heading @anchor{ix86-x-solaris210}i?86-*-solaris2.10
3537 Use this for Solaris 10 or later on x86 and x86-64 systems. This
3538 configuration is supported by GCC 4.0 and later versions only. Unlike
3539 @samp{sparcv9-sun-solaris2*}, there is no corresponding 64-bit
3540 configuration like @samp{amd64-*-solaris2*} or @samp{x86_64-*-solaris2*}.
3541 @c FIXME: will there ever be?
3543 It is recommended that you configure GCC to use the GNU assembler, in
3544 @file{/usr/sfw/bin/gas}. The versions included in Solaris 10, from GNU
3545 binutils 2.15, and Solaris 11, from GNU binutils 2.19, work fine,
3546 although the current version, from GNU binutils
3547 2.21, is known to work, too. Recent versions of the Sun assembler in
3548 @file{/usr/ccs/bin/as} work almost as well, though.
3549 @c FIXME: as patch requirements?
3551 For linking, the Sun linker, is preferred. If you want to use the GNU
3552 linker instead, which is available in @file{/usr/sfw/bin/gld}, note that
3553 due to a packaging bug the version in Solaris 10, from GNU binutils
3554 2.15, cannot be used, while the version in Solaris 11, from GNU binutils
3555 2.19, works, as does the latest version, from GNU binutils 2.21.
3557 To use GNU @command{as}, configure with the options
3558 @option{--with-gnu-as --with-as=@//usr/@/sfw/@/bin/@/gas}. It may be necessary
3559 to configure with @option{--without-gnu-ld --with-ld=@//usr/@/ccs/@/bin/@/ld} to
3560 guarantee use of Sun @command{ld}.
3561 @c FIXME: why --without-gnu-ld --with-ld?
3566 @heading @anchor{ia64-x-linux}ia64-*-linux
3567 IA-64 processor (also known as IPF, or Itanium Processor Family)
3570 If you are using the installed system libunwind library with
3571 @option{--with-system-libunwind}, then you must use libunwind 0.98 or
3574 None of the following versions of GCC has an ABI that is compatible
3575 with any of the other versions in this list, with the exception that
3576 Red Hat 2.96 and Trillian 000171 are compatible with each other:
3577 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
3578 This primarily affects C++ programs and programs that create shared libraries.
3579 GCC 3.1 or later is recommended for compiling linux, the kernel.
3580 As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
3581 more major ABI changes are expected.
3586 @heading @anchor{ia64-x-hpux}ia64-*-hpux*
3587 Building GCC on this target requires the GNU Assembler. The bundled HP
3588 assembler will not work. To prevent GCC from using the wrong assembler,
3589 the option @option{--with-gnu-as} may be necessary.
3591 The GCC libunwind library has not been ported to HPUX@. This means that for
3592 GCC versions 3.2.3 and earlier, @option{--enable-libunwind-exceptions}
3593 is required to build GCC@. For GCC 3.3 and later, this is the default.
3594 For gcc 3.4.3 and later, @option{--enable-libunwind-exceptions} is
3595 removed and the system libunwind library will always be used.
3599 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
3601 @heading @anchor{x-ibm-aix}*-ibm-aix*
3602 Support for AIX version 3 and older was discontinued in GCC 3.4.
3603 Support for AIX version 4.2 and older was discontinued in GCC 4.5.
3605 ``out of memory'' bootstrap failures may indicate a problem with
3606 process resource limits (ulimit). Hard limits are configured in the
3607 @file{/etc/security/limits} system configuration file.
3609 GCC can bootstrap with recent versions of IBM XLC, but bootstrapping
3610 with an earlier release of GCC is recommended. Bootstrapping with XLC
3611 requires a larger data segment, which can be enabled through the
3612 @var{LDR_CNTRL} environment variable, e.g.,
3615 % LDR_CNTRL=MAXDATA=0x50000000
3619 One can start with a pre-compiled version of GCC to build from
3620 sources. One may delete GCC's ``fixed'' header files when starting
3621 with a version of GCC built for an earlier release of AIX.
3623 To speed up the configuration phases of bootstrapping and installing GCC,
3624 one may use GNU Bash instead of AIX @command{/bin/sh}, e.g.,
3627 % CONFIG_SHELL=/opt/freeware/bin/bash
3628 % export CONFIG_SHELL
3631 and then proceed as described in @uref{build.html,,the build
3632 instructions}, where we strongly recommend specifying an absolute path
3633 to invoke @var{srcdir}/configure.
3635 Because GCC on AIX is built as a 32-bit executable by default,
3636 (although it can generate 64-bit programs) the GMP and MPFR libraries
3637 required by gfortran must be 32-bit libraries. Building GMP and MPFR
3638 as static archive libraries works better than shared libraries.
3640 Errors involving @code{alloca} when building GCC generally are due
3641 to an incorrect definition of @code{CC} in the Makefile or mixing files
3642 compiled with the native C compiler and GCC@. During the stage1 phase of
3643 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
3644 (not @command{xlc}). Once @command{configure} has been informed of
3645 @command{xlc}, one needs to use @samp{make distclean} to remove the
3646 configure cache files and ensure that @env{CC} environment variable
3647 does not provide a definition that will confuse @command{configure}.
3648 If this error occurs during stage2 or later, then the problem most likely
3649 is the version of Make (see above).
3651 The native @command{as} and @command{ld} are recommended for bootstrapping
3652 on AIX@. The GNU Assembler, GNU Linker, and GNU Binutils version 2.20
3653 is required to bootstrap on AIX 5@. The native AIX tools do
3654 interoperate with GCC@.
3656 Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
3657 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
3658 fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
3659 referenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1)
3661 @samp{libstdc++} in GCC 3.4 increments the major version number of the
3662 shared object and GCC installation places the @file{libstdc++.a}
3663 shared library in a common location which will overwrite the and GCC
3664 3.3 version of the shared library. Applications either need to be
3665 re-linked against the new shared library or the GCC 3.1 and GCC 3.3
3666 versions of the @samp{libstdc++} shared object needs to be available
3667 to the AIX runtime loader. The GCC 3.1 @samp{libstdc++.so.4}, if
3668 present, and GCC 3.3 @samp{libstdc++.so.5} shared objects can be
3669 installed for runtime dynamic loading using the following steps to set
3670 the @samp{F_LOADONLY} flag in the shared object for @emph{each}
3671 multilib @file{libstdc++.a} installed:
3673 Extract the shared objects from the currently installed
3674 @file{libstdc++.a} archive:
3676 % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
3679 Enable the @samp{F_LOADONLY} flag so that the shared object will be
3680 available for runtime dynamic loading, but not linking:
3682 % strip -e libstdc++.so.4 libstdc++.so.5
3685 Archive the runtime-only shared object in the GCC 3.4
3686 @file{libstdc++.a} archive:
3688 % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
3691 Linking executables and shared libraries may produce warnings of
3692 duplicate symbols. The assembly files generated by GCC for AIX always
3693 have included multiple symbol definitions for certain global variable
3694 and function declarations in the original program. The warnings should
3695 not prevent the linker from producing a correct library or runnable
3698 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
3699 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
3700 to parse archive libraries did not handle the new format correctly.
3701 These routines are used by GCC and result in error messages during
3702 linking such as ``not a COFF file''. The version of the routines shipped
3703 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
3704 option of the archive command may be used to create archives of 32-bit
3705 objects using the original ``small format''. A correct version of the
3706 routines is shipped with AIX 4.3.2 and above.
3708 Some versions of the AIX binder (linker) can fail with a relocation
3709 overflow severe error when the @option{-bbigtoc} option is used to link
3710 GCC-produced object files into an executable that overflows the TOC@. A fix
3711 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
3712 available from IBM Customer Support and from its
3713 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3714 website as PTF U455193.
3716 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
3717 with a segmentation fault when invoked by any version of GCC@. A fix for
3718 APAR IX87327 is available from IBM Customer Support and from its
3719 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3720 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
3722 The initial assembler shipped with AIX 4.3.0 generates incorrect object
3723 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
3724 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
3725 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3726 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
3728 AIX provides National Language Support (NLS)@. Compilers and assemblers
3729 use NLS to support locale-specific representations of various data
3730 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
3731 separating decimal fractions). There have been problems reported where
3732 GCC does not produce the same floating-point formats that the assembler
3733 expects. If one encounters this problem, set the @env{LANG}
3734 environment variable to @samp{C} or @samp{En_US}.
3736 A default can be specified with the @option{-mcpu=@var{cpu_type}}
3737 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
3742 @heading @anchor{iq2000-x-elf}iq2000-*-elf
3743 Vitesse IQ2000 processors. These are used in embedded
3744 applications. There are no standard Unix configurations.
3749 @heading @anchor{lm32-x-elf}lm32-*-elf
3750 Lattice Mico32 processor.
3751 This configuration is intended for embedded systems.
3756 @heading @anchor{lm32-x-uclinux}lm32-*-uclinux
3757 Lattice Mico32 processor.
3758 This configuration is intended for embedded systems running uClinux.
3763 @heading @anchor{m32c-x-elf}m32c-*-elf
3764 Renesas M32C processor.
3765 This configuration is intended for embedded systems.
3770 @heading @anchor{m32r-x-elf}m32r-*-elf
3771 Renesas M32R processor.
3772 This configuration is intended for embedded systems.
3777 @heading @anchor{m68k-x-x}m68k-*-*
3779 @samp{m68k-*-elf*}, @samp{m68k-*-rtems}, @samp{m68k-*-uclinux} and
3781 build libraries for both M680x0 and ColdFire processors. If you only
3782 need the M680x0 libraries, you can omit the ColdFire ones by passing
3783 @option{--with-arch=m68k} to @command{configure}. Alternatively, you
3784 can omit the M680x0 libraries by passing @option{--with-arch=cf} to
3785 @command{configure}. These targets default to 5206 or 5475 code as
3786 appropriate for the target system when
3787 configured with @option{--with-arch=cf} and 68020 code otherwise.
3789 The @samp{m68k-*-netbsd} and
3790 @samp{m68k-*-openbsd} targets also support the @option{--with-arch}
3791 option. They will generate ColdFire CFV4e code when configured with
3792 @option{--with-arch=cf} and 68020 code otherwise.
3794 You can override the default processors listed above by configuring
3795 with @option{--with-cpu=@var{target}}. This @var{target} can either
3796 be a @option{-mcpu} argument or one of the following values:
3797 @samp{m68000}, @samp{m68010}, @samp{m68020}, @samp{m68030},
3798 @samp{m68040}, @samp{m68060}, @samp{m68020-40} and @samp{m68020-60}.
3800 GCC requires at least binutils version 2.17 on these targets.
3805 @heading @anchor{m68k-x-uclinux}m68k-*-uclinux
3806 GCC 4.3 changed the uClinux configuration so that it uses the
3807 @samp{m68k-linux-gnu} ABI rather than the @samp{m68k-elf} ABI.
3808 It also added improved support for C++ and flat shared libraries,
3809 both of which were ABI changes.
3815 @heading @anchor{mep-x-elf}mep-*-elf
3816 Toshiba Media embedded Processor.
3817 This configuration is intended for embedded systems.
3822 @heading @anchor{microblaze-x-elf}microblaze-*-elf
3823 Xilinx MicroBlaze processor.
3824 This configuration is intended for embedded systems.
3829 @heading @anchor{mips-x-x}mips-*-*
3830 If on a MIPS system you get an error message saying ``does not have gp
3831 sections for all it's [sic] sectons [sic]'', don't worry about it. This
3832 happens whenever you use GAS with the MIPS linker, but there is not
3833 really anything wrong, and it is okay to use the output file. You can
3834 stop such warnings by installing the GNU linker.
3836 It would be nice to extend GAS to produce the gp tables, but they are
3837 optional, and there should not be a warning about their absence.
3839 The libstdc++ atomic locking routines for MIPS targets requires MIPS II
3840 and later. A patch went in just after the GCC 3.3 release to
3841 make @samp{mips*-*-*} use the generic implementation instead. You can also
3842 configure for @samp{mipsel-elf} as a workaround. The
3843 @samp{mips*-*-linux*} target continues to use the MIPS II routines. More
3844 work on this is expected in future releases.
3846 @c If you make --with-llsc the default for another target, please also
3847 @c update the description of the --with-llsc option.
3849 The built-in @code{__sync_*} functions are available on MIPS II and
3850 later systems and others that support the @samp{ll}, @samp{sc} and
3851 @samp{sync} instructions. This can be overridden by passing
3852 @option{--with-llsc} or @option{--without-llsc} when configuring GCC.
3853 Since the Linux kernel emulates these instructions if they are
3854 missing, the default for @samp{mips*-*-linux*} targets is
3855 @option{--with-llsc}. The @option{--with-llsc} and
3856 @option{--without-llsc} configure options may be overridden at compile
3857 time by passing the @option{-mllsc} or @option{-mno-llsc} options to
3860 MIPS systems check for division by zero (unless
3861 @option{-mno-check-zero-division} is passed to the compiler) by
3862 generating either a conditional trap or a break instruction. Using
3863 trap results in smaller code, but is only supported on MIPS II and
3864 later. Also, some versions of the Linux kernel have a bug that
3865 prevents trap from generating the proper signal (@code{SIGFPE}). To enable
3866 the use of break, use the @option{--with-divide=breaks}
3867 @command{configure} option when configuring GCC@. The default is to
3868 use traps on systems that support them.
3870 The assembler from GNU binutils 2.17 and earlier has a bug in the way
3871 it sorts relocations for REL targets (o32, o64, EABI). This can cause
3872 bad code to be generated for simple C++ programs. Also the linker
3873 from GNU binutils versions prior to 2.17 has a bug which causes the
3874 runtime linker stubs in very large programs, like @file{libgcj.so}, to
3875 be incorrectly generated. GNU Binutils 2.18 and later (and snapshots
3876 made after Nov. 9, 2006) should be free from both of these problems.
3881 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
3883 Support for IRIX 5 has been removed in GCC 4.6.
3888 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
3890 Support for IRIX 6 releases before 6.5 has been removed in GCC 4.6, as
3892 the O32 ABI. It is @emph{strongly} recommended to upgrade to at least
3893 IRIX 6.5.18. This release introduced full ISO C99 support, though for
3894 the N32 and N64 ABIs only.
3896 To build and use GCC on IRIX 6.5, you need the IRIX Development Foundation
3897 (IDF) and IRIX Development Libraries (IDL). They are included with the
3900 If you are using SGI's MIPSpro @command{cc} as your bootstrap compiler, you must
3901 ensure that the N32 ABI is in use. To test this, compile a simple C
3902 file with @command{cc} and then run @command{file} on the
3903 resulting object file. The output should look like:
3906 test.o: ELF N32 MSB @dots{}
3913 test.o: ELF 32-bit MSB @dots{}
3920 test.o: ELF 64-bit MSB @dots{}
3924 then your version of @command{cc} uses the O32 or N64 ABI by default. You
3925 should set the environment variable @env{CC} to @samp{cc -n32}
3926 before configuring GCC@.
3928 If you want the resulting @command{gcc} to run on old 32-bit systems
3929 with the MIPS R4400 CPU, you need to ensure that only code for the @samp{mips3}
3930 instruction set architecture (ISA) is generated. While GCC 3.x does
3931 this correctly, both GCC 2.95 and SGI's MIPSpro @command{cc} may change
3932 the ISA depending on the machine where GCC is built. Using one of them
3933 as the bootstrap compiler may result in @samp{mips4} code, which won't run at
3934 all on @samp{mips3}-only systems. For the test program above, you should see:
3937 test.o: ELF N32 MSB mips-3 @dots{}
3944 test.o: ELF N32 MSB mips-4 @dots{}
3948 instead, you should set the environment variable @env{CC} to @samp{cc
3949 -n32 -mips3} or @samp{gcc -mips3} respectively before configuring GCC@.
3951 MIPSpro C 7.4 may cause bootstrap failures, due to a bug when inlining
3952 @code{memcmp}. Either add @code{-U__INLINE_INTRINSICS} to the @env{CC}
3953 environment variable as a workaround or upgrade to MIPSpro C 7.4.1m.
3955 GCC on IRIX 6.5 is usually built to support the N32 and N64 ABIs. If
3956 you build GCC on a system that doesn't have the N64 libraries installed
3957 or cannot run 64-bit binaries,
3958 you need to configure with @option{--disable-multilib} so GCC doesn't
3960 Look for @file{/usr/lib64/libc.so.1} to see if you
3961 have the 64-bit libraries installed.
3963 GCC must be configured with GNU @command{as}. The latest version, from GNU
3964 binutils 2.21, is known to work. On the other hand, bootstrap fails
3965 with GNU @command{ld} at least since GNU binutils 2.17.
3967 The @option{--enable-libgcj}
3968 option is disabled by default: IRIX 6 uses a very low default limit
3969 (20480) for the command line length. Although @command{libtool} contains a
3970 workaround for this problem, at least the N64 @samp{libgcj} is known not
3971 to build despite this, running into an internal error of the native
3972 @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
3973 its maximum of 262144 bytes. If you have root access, you can use the
3974 @command{systune} command to do this.
3975 @c FIXME: does this work with current libtool?
3977 @code{wchar_t} support in @samp{libstdc++} is not available for old
3978 IRIX 6.5.x releases, @math{x < 19}. The problem cannot be autodetected
3979 and in order to build GCC for such targets you need to configure with
3980 @option{--disable-wchar_t}.
3985 @heading @anchor{moxie-x-elf}moxie-*-elf
3986 The moxie processor. See @uref{http://moxielogic.org/} for more
3987 information about this processor.
3992 @heading @anchor{powerpc-x-x}powerpc-*-*
3994 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
3995 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
3998 @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.15}
3999 or newer for a working GCC@.
4004 @heading @anchor{powerpc-x-darwin}powerpc-*-darwin*
4005 PowerPC running Darwin (Mac OS X kernel).
4007 Pre-installed versions of Mac OS X may not include any developer tools,
4008 meaning that you will not be able to build GCC from source. Tool
4009 binaries are available at
4010 @uref{http://opensource.apple.com/}.
4012 This version of GCC requires at least cctools-590.36. The
4013 cctools-590.36 package referenced from
4014 @uref{http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html} will not work
4015 on systems older than 10.3.9 (aka darwin7.9.0).
4020 @heading @anchor{powerpc-x-elf}powerpc-*-elf
4021 PowerPC system in big endian mode, running System V.4.
4026 @heading @anchor{powerpc-x-linux-gnu}powerpc*-*-linux-gnu*
4028 PowerPC system in big endian mode running Linux.
4033 @heading @anchor{powerpc-x-netbsd}powerpc-*-netbsd*
4034 PowerPC system in big endian mode running NetBSD@.
4039 @heading @anchor{powerpc-x-eabisim}powerpc-*-eabisim
4040 Embedded PowerPC system in big endian mode for use in running under the
4046 @heading @anchor{powerpc-x-eabi}powerpc-*-eabi
4047 Embedded PowerPC system in big endian mode.
4052 @heading @anchor{powerpcle-x-elf}powerpcle-*-elf
4053 PowerPC system in little endian mode, running System V.4.
4058 @heading @anchor{powerpcle-x-eabisim}powerpcle-*-eabisim
4059 Embedded PowerPC system in little endian mode for use in running under
4065 @heading @anchor{powerpcle-x-eabi}powerpcle-*-eabi
4066 Embedded PowerPC system in little endian mode.
4071 @heading @anchor{rx-x-elf}rx-*-elf
4072 The Renesas RX processor. See
4073 @uref{http://eu.renesas.com/fmwk.jsp?cnt=rx600_series_landing.jsp&fp=/products/mpumcu/rx_family/rx600_series}
4074 for more information about this processor.
4079 @heading @anchor{s390-x-linux}s390-*-linux*
4080 S/390 system running GNU/Linux for S/390@.
4085 @heading @anchor{s390x-x-linux}s390x-*-linux*
4086 zSeries system (64-bit) running GNU/Linux for zSeries@.
4091 @heading @anchor{s390x-ibm-tpf}s390x-ibm-tpf*
4092 zSeries system (64-bit) running TPF@. This platform is
4093 supported as cross-compilation target only.
4098 @c Please use Solaris 2 to refer to all release of Solaris, starting
4099 @c with 2.0 until 2.6, 7, 8, etc. Solaris 1 was a marketing name for
4100 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
4101 @c alone is too unspecific and must be avoided.
4102 @heading @anchor{x-x-solaris2}*-*-solaris2*
4104 Support for Solaris 8 has been obsoleted in GCC 4.7, but can still be
4105 enabled by configuring with @option{--enable-obsolete}. Support will be
4106 removed in GCC 4.8. Support for Solaris 7 has been removed in GCC 4.6.
4108 Sun does not ship a C compiler with Solaris 2, though you can download
4109 the Sun Studio compilers for free. Alternatively,
4110 you can install a pre-built GCC to bootstrap and install GCC. See the
4111 @uref{binaries.html,,binaries page} for details.
4113 The Solaris 2 @command{/bin/sh} will often fail to configure
4114 @samp{libstdc++-v3}, @samp{boehm-gc} or @samp{libjava}. We therefore
4115 recommend using the following initial sequence of commands
4118 % CONFIG_SHELL=/bin/ksh
4119 % export CONFIG_SHELL
4123 and proceed as described in @uref{configure.html,,the configure instructions}.
4124 In addition we strongly recommend specifying an absolute path to invoke
4125 @command{@var{srcdir}/configure}.
4127 Solaris 2 comes with a number of optional OS packages. Some of these
4128 are needed to use GCC fully, namely @code{SUNWarc},
4129 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
4130 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
4131 optional packages when installing Solaris 2, you will need to verify that
4132 the packages that GCC needs are installed.
4134 To check whether an optional package is installed, use
4135 the @command{pkginfo} command. To add an optional package, use the
4136 @command{pkgadd} command. For further details, see the Solaris 2
4139 Trying to use the linker and other tools in
4140 @file{/usr/ucb} to install GCC has been observed to cause trouble.
4141 For example, the linker may hang indefinitely. The fix is to remove
4142 @file{/usr/ucb} from your @env{PATH}.
4144 The build process works more smoothly with the legacy Sun tools so, if you
4145 have @file{/usr/xpg4/bin} in your @env{PATH}, we recommend that you place
4146 @file{/usr/bin} before @file{/usr/xpg4/bin} for the duration of the build.
4148 We recommend the use of the Sun assembler or the GNU assembler, in
4149 conjunction with the Sun linker. The GNU @command{as}
4150 versions included in Solaris 10, from GNU binutils 2.15, and Solaris 11,
4151 from GNU binutils 2.19, are known to work. They can be found in
4152 @file{/usr/sfw/bin/gas}. Current versions of GNU binutils (2.21)
4153 are known to work as well. Note that your mileage may vary
4154 if you use a combination of the GNU tools and the Sun tools: while the
4155 combination GNU @command{as} + Sun @command{ld} should reasonably work,
4156 the reverse combination Sun @command{as} + GNU @command{ld} is known to
4157 cause memory corruption at runtime in some cases for C++ programs.
4159 GNU @command{ld} usually works as well, although the version included in
4160 Solaris 10 cannot be used due to several bugs. Again, the current
4161 version (2.21) is known to work, but generally lacks platform specific
4162 features, so better stay with Sun @command{ld}.
4164 To enable symbol versioning in @samp{libstdc++} with Sun @command{ld},
4165 you need to have any version of GNU @command{c++filt}, which is part of
4166 GNU binutils. @samp{libstdc++} symbol versioning will be disabled if no
4167 appropriate version is found. Sun @command{c++filt} from the Sun Studio
4168 compilers does @emph{not} work.
4170 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
4171 newer: @command{g++} will complain that types are missing. These headers
4172 assume that omitting the type means @code{int}; this assumption worked for
4173 C90 but is wrong for C++, and is now wrong for C99 also.
4175 @command{g++} accepts such (invalid) constructs with the option
4176 @option{-fpermissive}; it will assume that any missing type is @code{int}
4177 (as defined by C90).
4179 There are patches for Solaris 8 (108652-24 or newer for SPARC,
4180 108653-22 for Intel) that fix this bug.
4182 Sun bug 4927647 sometimes causes random spurious testsuite failures
4183 related to missing diagnostic output. This bug doesn't affect GCC
4184 itself, rather it is a kernel bug triggered by the @command{expect}
4185 program which is used only by the GCC testsuite driver. When the bug
4186 causes the @command{expect} program to miss anticipated output, extra
4187 testsuite failures appear.
4189 There are patches for Solaris 8 (117350-12 or newer for SPARC,
4190 117351-12 or newer for Intel) and Solaris 9 (117171-11 or newer for
4191 SPARC, 117172-11 or newer for Intel) that address this problem.
4193 Solaris@tie{}8 provides an alternate implementation of the thread libraries,
4194 @samp{libpthread} and @samp{libthread}. They are required for TLS
4195 support and have been made the default in Solaris@tie{}9, so they are always
4196 used on Solaris@tie{}8.
4198 Thread-local storage (TLS) is supported in Solaris@tie{}8 and 9, but requires
4199 some patches. The @samp{libthread} patches provide the
4200 @code{__tls_get_addr} (SPARC, 64-bit x86) resp.@ @code{___tls_get_addr}
4201 (32-bit x86) functions. On Solaris@tie{}8, you need 108993-26 or newer on
4202 SPARC, 108994-26 or newer on Intel. On Solaris@tie{}9, the necessary support
4203 on SPARC is present since FCS, while 114432-05 or newer is required on
4204 Intel. Additionally, on Solaris@tie{}8, patch 109147-14 or newer on SPARC or
4205 109148-22 or newer on Intel are required for the Sun @command{ld} and
4206 runtime linker (@command{ld.so.1}) support. Again, Solaris@tie{}9/SPARC
4207 works since FCS, while 113986-02 is required on Intel. The linker
4208 patches must be installed even if GNU @command{ld} is used. Sun
4209 @command{as} in Solaris@tie{}8 and 9 doesn't support the necessary
4210 relocations, so GNU @command{as} must be used. The @command{configure}
4211 script checks for those prerequisites and automatically enables TLS
4212 support if they are met. Although those minimal patch versions should
4213 work, it is recommended to use the latest patch versions which include
4214 additional bug fixes.
4219 @heading @anchor{sparc-x-x}sparc*-*-*
4221 This section contains general configuration information for all
4222 SPARC-based platforms. In addition to reading this section, please
4223 read all other sections that match your target.
4225 Newer versions of the GNU Multiple Precision Library (GMP), the MPFR
4226 library and the MPC library are known to be miscompiled by earlier
4227 versions of GCC on these platforms. We therefore recommend the use
4228 of the exact versions of these libraries listed as minimal versions
4229 in @uref{prerequisites.html,,the prerequisites}.
4234 @heading @anchor{sparc-sun-solaris2}sparc-sun-solaris2*
4236 When GCC is configured to use GNU binutils 2.14 or later, the binaries
4237 produced are smaller than the ones produced using Sun's native tools;
4238 this difference is quite significant for binaries containing debugging
4241 Starting with Solaris 7, the operating system is capable of executing
4242 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
4243 this; the @option{-m64} option enables 64-bit code generation.
4244 However, if all you want is code tuned for the UltraSPARC CPU, you
4245 should try the @option{-mtune=ultrasparc} option instead, which produces
4246 code that, unlike full 64-bit code, can still run on non-UltraSPARC
4249 When configuring on a Solaris 7 or later system that is running a kernel
4250 that supports only 32-bit binaries, one must configure with
4251 @option{--disable-multilib}, since we will not be able to build the
4252 64-bit target libraries.
4254 GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of
4255 the GNU compiler (especially GCC 3.0.x versions), which lead to the
4256 miscompilation of the stage1 compiler and the subsequent failure of the
4257 bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary
4258 stage, i.e.@: to bootstrap that compiler with the base compiler and then
4259 use it to bootstrap the final compiler.
4261 GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7)
4262 and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap
4263 failure in form of a miscompilation of the stage1 compiler by the Sun
4264 compiler. This is Sun bug 4974440. This is fixed with patch 112760-07.
4266 GCC 3.4 changed the default debugging format from Stabs to DWARF-2 for
4267 32-bit code on Solaris 7 and later. If you use the Sun assembler, this
4268 change apparently runs afoul of Sun bug 4910101 (which is referenced as
4269 an x86-only problem by Sun, probably because they do not use DWARF-2).
4270 A symptom of the problem is that you cannot compile C++ programs like
4271 @command{groff} 1.19.1 without getting messages similar to the following:
4274 ld: warning: relocation error: R_SPARC_UA32: @dots{}
4275 external symbolic relocation against non-allocatable section
4276 .debug_info cannot be processed at runtime: relocation ignored.
4280 To work around this problem, compile with @option{-gstabs+} instead of
4283 When configuring the GNU Multiple Precision Library (GMP), the MPFR
4284 library or the MPC library on a Solaris 7 or later system, the canonical
4285 target triplet must be specified as the @command{build} parameter on the
4286 configure line. This target triplet can be obtained by invoking @command{./config.guess} in the toplevel source directory of GCC (and
4287 not that of GMP or MPFR or MPC). For example on a Solaris 9 system:
4290 % ./configure --build=sparc-sun-solaris2.9 --prefix=xxx
4296 @heading @anchor{sparc-sun-solaris210}sparc-sun-solaris2.10
4298 There is a bug in older versions of the Sun assembler which breaks
4299 thread-local storage (TLS). A typical error message is
4302 ld: fatal: relocation error: R_SPARC_TLS_LE_HIX22: file /var/tmp//ccamPA1v.o:
4303 symbol <unknown>: bad symbol type SECT: symbol type must be TLS
4307 This bug is fixed in Sun patch 118683-03 or later.
4312 @heading @anchor{sparc-x-linux}sparc-*-linux*
4314 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
4315 or newer on this platform. All earlier binutils and glibc
4316 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
4322 @heading @anchor{sparc64-x-solaris2}sparc64-*-solaris2*
4324 When configuring the GNU Multiple Precision Library (GMP) or the
4325 MPFR library, the canonical target triplet must be specified as
4326 the @command{build} parameter on the configure line. For example
4327 on a Solaris 9 system:
4330 % ./configure --build=sparc64-sun-solaris2.9 --prefix=xxx
4333 The following compiler flags must be specified in the configure
4334 step in order to bootstrap this target with the Sun compiler:
4337 % CC="cc -xarch=v9 -xildoff" @var{srcdir}/configure [@var{options}] [@var{target}]
4341 @option{-xarch=v9} specifies the SPARC-V9 architecture to the Sun toolchain
4342 and @option{-xildoff} turns off the incremental linker.
4347 @heading @anchor{sparcv9-x-solaris2}sparcv9-*-solaris2*
4349 This is a synonym for @samp{sparc64-*-solaris2*}.
4354 @heading @anchor{x-x-vxworks}*-*-vxworks*
4355 Support for VxWorks is in flux. At present GCC supports @emph{only} the
4356 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC@.
4357 We welcome patches for other architectures supported by VxWorks 5.5.
4358 Support for VxWorks AE would also be welcome; we believe this is merely
4359 a matter of writing an appropriate ``configlette'' (see below). We are
4360 not interested in supporting older, a.out or COFF-based, versions of
4363 VxWorks comes with an older version of GCC installed in
4364 @file{@var{$WIND_BASE}/host}; we recommend you do not overwrite it.
4365 Choose an installation @var{prefix} entirely outside @var{$WIND_BASE}.
4366 Before running @command{configure}, create the directories @file{@var{prefix}}
4367 and @file{@var{prefix}/bin}. Link or copy the appropriate assembler,
4368 linker, etc.@: into @file{@var{prefix}/bin}, and set your @var{PATH} to
4369 include that directory while running both @command{configure} and
4372 You must give @command{configure} the
4373 @option{--with-headers=@var{$WIND_BASE}/target/h} switch so that it can
4374 find the VxWorks system headers. Since VxWorks is a cross compilation
4375 target only, you must also specify @option{--target=@var{target}}.
4376 @command{configure} will attempt to create the directory
4377 @file{@var{prefix}/@var{target}/sys-include} and copy files into it;
4378 make sure the user running @command{configure} has sufficient privilege
4381 GCC's exception handling runtime requires a special ``configlette''
4382 module, @file{contrib/gthr_supp_vxw_5x.c}. Follow the instructions in
4383 that file to add the module to your kernel build. (Future versions of
4384 VxWorks will incorporate this module.)
4389 @heading @anchor{x86-64-x-x}x86_64-*-*, amd64-*-*
4391 GCC supports the x86-64 architecture implemented by the AMD64 processor
4392 (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD@.
4393 On GNU/Linux the default is a bi-arch compiler which is able to generate
4394 both 64-bit x86-64 and 32-bit x86 code (via the @option{-m32} switch).
4399 @heading @anchor{xtensa-x-elf}xtensa*-*-elf
4401 This target is intended for embedded Xtensa systems using the
4402 @samp{newlib} C library. It uses ELF but does not support shared
4403 objects. Designed-defined instructions specified via the
4404 Tensilica Instruction Extension (TIE) language are only supported
4405 through inline assembly.
4407 The Xtensa configuration information must be specified prior to
4408 building GCC@. The @file{include/xtensa-config.h} header
4409 file contains the configuration information. If you created your
4410 own Xtensa configuration with the Xtensa Processor Generator, the
4411 downloaded files include a customized copy of this header file,
4412 which you can use to replace the default header file.
4417 @heading @anchor{xtensa-x-linux}xtensa*-*-linux*
4419 This target is for Xtensa systems running GNU/Linux. It supports ELF
4420 shared objects and the GNU C library (glibc). It also generates
4421 position-independent code (PIC) regardless of whether the
4422 @option{-fpic} or @option{-fPIC} options are used. In other
4423 respects, this target is the same as the
4424 @uref{#xtensa*-*-elf,,@samp{xtensa*-*-elf}} target.
4429 @heading @anchor{windows}Microsoft Windows
4431 @subheading Intel 16-bit versions
4432 The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not
4435 However, the 32-bit port has limited support for Microsoft
4436 Windows 3.11 in the Win32s environment, as a target only. See below.
4438 @subheading Intel 32-bit versions
4440 The 32-bit versions of Windows, including Windows 95, Windows NT, Windows
4441 XP, and Windows Vista, are supported by several different target
4442 platforms. These targets differ in which Windows subsystem they target
4443 and which C libraries are used.
4446 @item Cygwin @uref{#x-x-cygwin,,*-*-cygwin}: Cygwin provides a user-space
4447 Linux API emulation layer in the Win32 subsystem.
4448 @item Interix @uref{#x-x-interix,,*-*-interix}: The Interix subsystem
4449 provides native support for POSIX.
4450 @item MinGW @uref{#x-x-mingw32,,*-*-mingw32}: MinGW is a native GCC port for
4451 the Win32 subsystem that provides a subset of POSIX.
4452 @item MKS i386-pc-mks: NuTCracker from MKS. See
4453 @uref{http://www.mkssoftware.com/} for more information.
4456 @subheading Intel 64-bit versions
4458 GCC contains support for x86-64 using the mingw-w64
4459 runtime library, available from @uref{http://mingw-w64.sourceforge.net/}.
4460 This library should be used with the target triple x86_64-pc-mingw32.
4462 Presently Windows for Itanium is not supported.
4464 @subheading Windows CE
4466 Windows CE is supported as a target only on ARM (arm-wince-pe), Hitachi
4467 SuperH (sh-wince-pe), and MIPS (mips-wince-pe).
4469 @subheading Other Windows Platforms
4471 GCC no longer supports Windows NT on the Alpha or PowerPC.
4473 GCC no longer supports the Windows POSIX subsystem. However, it does
4474 support the Interix subsystem. See above.
4476 Old target names including *-*-winnt and *-*-windowsnt are no longer used.
4478 PW32 (i386-pc-pw32) support was never completed, and the project seems to
4479 be inactive. See @uref{http://pw32.sourceforge.net/} for more information.
4481 UWIN support has been removed due to a lack of maintenance.
4486 @heading @anchor{x-x-cygwin}*-*-cygwin
4488 Ports of GCC are included with the
4489 @uref{http://www.cygwin.com/,,Cygwin environment}.
4491 GCC will build under Cygwin without modification; it does not build
4492 with Microsoft's C++ compiler and there are no plans to make it do so.
4494 The Cygwin native compiler can be configured to target any 32-bit x86
4495 cpu architecture desired; the default is i686-pc-cygwin. It should be
4496 used with as up-to-date a version of binutils as possible; use either
4497 the latest official GNU binutils release in the Cygwin distribution,
4498 or version 2.20 or above if building your own.
4503 @heading @anchor{x-x-interix}*-*-interix
4505 The Interix target is used by OpenNT, Interix, Services For UNIX (SFU),
4506 and Subsystem for UNIX-based Applications (SUA). Applications compiled
4507 with this target run in the Interix subsystem, which is separate from
4508 the Win32 subsystem. This target was last known to work in GCC 3.3.
4513 @heading @anchor{x-x-mingw32}*-*-mingw32
4515 GCC will build with and support only MinGW runtime 3.12 and later.
4516 Earlier versions of headers are incompatible with the new default semantics
4517 of @code{extern inline} in @code{-std=c99} and @code{-std=gnu99} modes.
4522 @heading @anchor{older}Older systems
4524 GCC contains support files for many older (1980s and early
4525 1990s) Unix variants. For the most part, support for these systems
4526 has not been deliberately removed, but it has not been maintained for
4527 several years and may suffer from bitrot.
4529 Starting with GCC 3.1, each release has a list of ``obsoleted'' systems.
4530 Support for these systems is still present in that release, but
4531 @command{configure} will fail unless the @option{--enable-obsolete}
4532 option is given. Unless a maintainer steps forward, support for these
4533 systems will be removed from the next release of GCC@.
4535 Support for old systems as hosts for GCC can cause problems if the
4536 workarounds for compiler, library and operating system bugs affect the
4537 cleanliness or maintainability of the rest of GCC@. In some cases, to
4538 bring GCC up on such a system, if still possible with current GCC, may
4539 require first installing an old version of GCC which did work on that
4540 system, and using it to compile a more recent GCC, to avoid bugs in the
4541 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
4542 @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror
4543 sites}. Header bugs may generally be avoided using
4544 @command{fixincludes}, but bugs or deficiencies in libraries and the
4545 operating system may still cause problems.
4547 Support for older systems as targets for cross-compilation is less
4548 problematic than support for them as hosts for GCC; if an enthusiast
4549 wishes to make such a target work again (including resurrecting any of
4550 the targets that never worked with GCC 2, starting from the last
4551 version before they were removed), patches
4552 @uref{../contribute.html,,following the usual requirements} would be
4553 likely to be accepted, since they should not affect the support for more
4556 For some systems, old versions of GNU binutils may also be useful,
4557 and are available from @file{pub/binutils/old-releases} on
4558 @uref{http://sourceware.org/mirrors.html,,sourceware.org mirror sites}.
4560 Some of the information on specific systems above relates to
4561 such older systems, but much of the information
4562 about GCC on such systems (which may no longer be applicable to
4563 current GCC) is to be found in the GCC texinfo manual.
4568 @heading @anchor{elf}all ELF targets (SVR4, Solaris 2, etc.)
4570 C++ support is significantly better on ELF targets if you use the
4571 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
4572 inlines, vtables and template instantiations will be discarded
4581 @uref{./index.html,,Return to the GCC Installation page}
4585 @c ***Old documentation******************************************************
4587 @include install-old.texi
4593 @uref{./index.html,,Return to the GCC Installation page}
4597 @c ***GFDL********************************************************************
4605 @uref{./index.html,,Return to the GCC Installation page}
4609 @c ***************************************************************************
4610 @c Part 6 The End of the Document
4612 @comment node-name, next, previous, up
4613 @node Concept Index, , GNU Free Documentation License, Top
4617 @unnumbered Concept Index