1 \input texinfo.tex @c -*-texinfo-*-
4 @setfilename gccinstall.info
5 @settitle Installing GCC
10 @c Specify title for specific html page
12 @settitle Installing GCC
15 @settitle Host/Target specific installation notes for GCC
17 @ifset prerequisiteshtml
18 @settitle Prerequisites for GCC
21 @settitle Downloading GCC
24 @settitle Installing GCC: Configuration
27 @settitle Installing GCC: Building
30 @settitle Installing GCC: Testing
32 @ifset finalinstallhtml
33 @settitle Installing GCC: Final installation
36 @settitle Installing GCC: Binaries
39 @settitle Installing GCC: Old documentation
42 @settitle Installing GCC: GNU Free Documentation License
45 @c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
46 @c 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc.
47 @c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com
49 @c IMPORTANT: whenever you modify this file, run `install.texi2html' to
50 @c test the generation of HTML documents for the gcc.gnu.org web pages.
52 @c Do not use @footnote{} in this file as it breaks install.texi2html!
54 @c Include everything if we're not making html
58 @set prerequisiteshtml
69 @c Part 2 Summary Description and Copyright
71 Copyright @copyright{} 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
72 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc.
74 Permission is granted to copy, distribute and/or modify this document
75 under the terms of the GNU Free Documentation License, Version 1.2 or
76 any later version published by the Free Software Foundation; with no
77 Invariant Sections, the Front-Cover texts being (a) (see below), and
78 with the Back-Cover Texts being (b) (see below). A copy of the
79 license is included in the section entitled ``@uref{./gfdl.html,,GNU
80 Free Documentation License}''.
82 (a) The FSF's Front-Cover Text is:
86 (b) The FSF's Back-Cover Text is:
88 You have freedom to copy and modify this GNU Manual, like GNU
89 software. Copies published by the Free Software Foundation raise
90 funds for GNU development.
95 @dircategory Software development
97 * gccinstall: (gccinstall). Installing the GNU Compiler Collection.
100 @c Part 3 Titlepage and Copyright
103 @comment The title is printed in a large font.
104 @center @titlefont{Installing GCC}
106 @c The following two commands start the copyright page.
108 @vskip 0pt plus 1filll
112 @c Part 4 Top node and Master Menu
115 @comment node-name, next, Previous, up
118 * Installing GCC:: This document describes the generic installation
119 procedure for GCC as well as detailing some target
120 specific installation instructions.
122 * Specific:: Host/target specific installation notes for GCC.
123 * Binaries:: Where to get pre-compiled binaries.
125 * Old:: Old installation documentation.
127 * GNU Free Documentation License:: How you can copy and share this manual.
128 * Concept Index:: This index has two entries.
132 @c Part 5 The Body of the Document
133 @c ***Installing GCC**********************************************************
135 @comment node-name, next, previous, up
136 @node Installing GCC, Binaries, , Top
140 @chapter Installing GCC
143 The latest version of this document is always available at
144 @uref{http://gcc.gnu.org/install/,,http://gcc.gnu.org/install/}.
146 This document describes the generic installation procedure for GCC as well
147 as detailing some target specific installation instructions.
149 GCC includes several components that previously were separate distributions
150 with their own installation instructions. This document supersedes all
151 package specific installation instructions.
153 @emph{Before} starting the build/install procedure please check the
155 @ref{Specific, host/target specific installation notes}.
158 @uref{specific.html,,host/target specific installation notes}.
160 We recommend you browse the entire generic installation instructions before
163 Lists of successful builds for released versions of GCC are
164 available at @uref{http://gcc.gnu.org/buildstat.html}.
165 These lists are updated as new information becomes available.
167 The installation procedure itself is broken into five steps.
172 * Downloading the source::
175 * Testing:: (optional)
182 @uref{prerequisites.html,,Prerequisites}
184 @uref{download.html,,Downloading the source}
186 @uref{configure.html,,Configuration}
188 @uref{build.html,,Building}
190 @uref{test.html,,Testing} (optional)
192 @uref{finalinstall.html,,Final install}
196 Please note that GCC does not support @samp{make uninstall} and probably
197 won't do so in the near future as this would open a can of worms. Instead,
198 we suggest that you install GCC into a directory of its own and simply
199 remove that directory when you do not need that specific version of GCC
200 any longer, and, if shared libraries are installed there as well, no
201 more binaries exist that use them.
204 There are also some @uref{old.html,,old installation instructions},
205 which are mostly obsolete but still contain some information which has
206 not yet been merged into the main part of this manual.
214 @uref{./index.html,,Return to the GCC Installation page}
220 @c ***Prerequisites**************************************************
222 @comment node-name, next, previous, up
223 @node Prerequisites, Downloading the source, , Installing GCC
225 @ifset prerequisiteshtml
227 @chapter Prerequisites
229 @cindex Prerequisites
231 GCC requires that various tools and packages be available for use in the
232 build procedure. Modifying GCC sources requires additional tools
235 @heading Tools/packages necessary for building GCC
237 @item ISO C90 compiler
238 Necessary to bootstrap GCC, although versions of GCC prior
239 to 3.4 also allow bootstrapping with a traditional (K&R) C compiler.
241 To build all languages in a cross-compiler or other configuration where
242 3-stage bootstrap is not performed, you need to start with an existing
243 GCC binary (version 2.95 or later) because source code for language
244 frontends other than C might use GCC extensions.
248 In order to build the Ada compiler (GNAT) you must already have GNAT
249 installed because portions of the Ada frontend are written in Ada (with
250 GNAT extensions.) Refer to the Ada installation instructions for more
251 specific information.
253 @item A ``working'' POSIX compatible shell, or GNU bash
255 Necessary when running @command{configure} because some
256 @command{/bin/sh} shells have bugs and may crash when configuring the
257 target libraries. In other cases, @command{/bin/sh} or @command{ksh}
258 have disastrous corner-case performance problems. This
259 can cause target @command{configure} runs to literally take days to
260 complete in some cases.
262 So on some platforms @command{/bin/ksh} is sufficient, on others it
263 isn't. See the host/target specific instructions for your platform, or
264 use @command{bash} to be sure. Then set @env{CONFIG_SHELL} in your
265 environment to your ``good'' shell prior to running
266 @command{configure}/@command{make}.
268 @command{zsh} is not a fully compliant POSIX shell and will not
269 work when configuring GCC@.
273 Necessary in some circumstances, optional in others. See the
274 host/target specific instructions for your platform for the exact
277 @item gzip version 1.2.4 (or later) or
278 @itemx bzip2 version 1.0.2 (or later)
280 Necessary to uncompress GCC @command{tar} files when source code is
281 obtained via FTP mirror sites.
283 @item GNU make version 3.79.1 (or later)
285 You must have GNU make installed to build GCC@.
287 @item GNU tar version 1.14 (or later)
289 Necessary (only on some platforms) to untar the source code. Many
290 systems' @command{tar} programs will also work, only try GNU
291 @command{tar} if you have problems.
293 @item GNU Multiple Precision Library (GMP) version 4.1 (or later)
295 Necessary to build GCC. If you do not have it installed in your
296 library search path, you will have to configure with the
297 @option{--with-gmp} or @option{--with-gmp-dir} configure option.
299 @item MPFR Library version 2.2 (or later)
301 Necessary to build GCC. It can be downloaded from
302 @uref{http://www.mpfr.org/}. If you're using version 2.2.0, You
303 should also apply revision 16 (or later) of the cumulative patch from
304 @uref{http://www.mpfr.org/mpfr-current/}. The version of MPFR that is
305 bundled with GMP 4.1.x contains numerous bugs. Although GNU Fortran
306 will appear to function with the buggy versions of MPFR, there are a
307 few GNU Fortran bugs that will not be fixed when using this version.
308 It is strongly recommended to upgrade to at least MPFR version 2.2.
310 The @option{--with-mpfr} or @option{--with-mpfr-dir} configure option should
311 be used if your MPFR Library is not installed in your library search path.
313 @item @command{jar}, or InfoZIP (@command{zip} and @command{unzip})
315 Necessary to build libgcj, the GCJ runtime.
320 @heading Tools/packages necessary for modifying GCC
322 @item autoconf versions 2.13 and 2.59
323 @itemx GNU m4 version 1.4 (or later)
325 Necessary when modifying @file{configure.ac}, @file{aclocal.m4}, etc.@:
326 to regenerate @file{configure} and @file{config.in} files. Most
327 directories require autoconf 2.59 (exactly), but the toplevel
328 still requires autoconf 2.13 (exactly).
330 @item automake version 1.9.6
332 Necessary when modifying a @file{Makefile.am} file to regenerate its
333 associated @file{Makefile.in}.
335 Much of GCC does not use automake, so directly edit the @file{Makefile.in}
336 file. Specifically this applies to the @file{gcc}, @file{intl},
337 @file{libcpp}, @file{libiberty}, @file{libobjc} directories as well
338 as any of their subdirectories.
340 For directories that use automake, GCC requires the latest release in
341 the 1.9.x series, which is currently 1.9.6. When regenerating a directory
342 to a newer version, please update all the directories using an older 1.9.x
343 to the latest released version.
345 @item gettext version 0.14.5 (or later)
347 Needed to regenerate @file{gcc.pot}.
349 @item gperf version 2.7.2 (or later)
351 Necessary when modifying @command{gperf} input files, e.g.@:
352 @file{gcc/cp/cfns.gperf} to regenerate its associated header file, e.g.@:
353 @file{gcc/cp/cfns.h}.
359 Necessary to run the GCC testsuite; see the section on testing for details.
361 @item autogen version 5.5.4 (or later) and
362 @itemx guile version 1.4.1 (or later)
364 Necessary to regenerate @file{fixinc/fixincl.x} from
365 @file{fixinc/inclhack.def} and @file{fixinc/*.tpl}.
367 Necessary to run @samp{make check} for @file{fixinc}.
369 Necessary to regenerate the top level @file{Makefile.in} file from
370 @file{Makefile.tpl} and @file{Makefile.def}.
372 @item GNU Bison version 1.28 (or later)
373 Berkeley @command{yacc} (@command{byacc}) is also reported to work other
376 Necessary when modifying @file{*.y} files.
378 Necessary to build GCC during development because the generated output
379 files are not included in the SVN repository. They are included in
382 @item Flex version 2.5.4 (or later)
384 Necessary when modifying @file{*.l} files.
386 Necessary to build GCC during development because the generated output
387 files are not included in the SVN repository. They are included in
390 @item Texinfo version 4.4 (or later)
392 Necessary for running @command{makeinfo} when modifying @file{*.texi}
393 files to test your changes.
395 Necessary for running @command{make dvi} or @command{make pdf} to
396 create printable documentation in DVI or PDF format. Texinfo version
397 4.8 or later is required for @command{make pdf}.
399 Necessary to build GCC documentation during development because the
400 generated output files are not included in the SVN repository. They are
401 included in releases.
403 @item @TeX{} (any working version)
405 Necessary for running @command{texi2dvi} and @command{texi2pdf}, which
406 are used when running @command{make dvi} or @command{make pdf} to create
407 DVI or PDF files, respectively.
409 @item SVN (any version)
410 @itemx SSH (any version)
412 Necessary to access the SVN repository. Public releases and weekly
413 snapshots of the development sources are also available via FTP@.
415 @item Perl version 5.6.1 (or later)
417 Necessary when regenerating @file{Makefile} dependencies in libiberty.
418 Necessary when regenerating @file{libiberty/functions.texi}.
419 Necessary when generating manpages from Texinfo manuals.
420 Necessary when targetting Darwin, building libstdc++,
421 and not using @option{--disable-symvers}.
422 Used by various scripts to generate some files included in SVN (mainly
423 Unicode-related and rarely changing) from source tables.
425 @item GNU diffutils version 2.7 (or later)
427 Useful when submitting patches for the GCC source code.
429 @item patch version 2.5.4 (or later)
431 Necessary when applying patches, created with @command{diff}, to one's
441 @uref{./index.html,,Return to the GCC Installation page}
445 @c ***Downloading the source**************************************************
447 @comment node-name, next, previous, up
448 @node Downloading the source, Configuration, Prerequisites, Installing GCC
452 @chapter Downloading GCC
454 @cindex Downloading GCC
455 @cindex Downloading the Source
457 GCC is distributed via @uref{http://gcc.gnu.org/svn.html,,SVN} and FTP
458 tarballs compressed with @command{gzip} or
459 @command{bzip2}. It is possible to download a full distribution or specific
462 Please refer to the @uref{http://gcc.gnu.org/releases.html,,releases web page}
463 for information on how to obtain GCC@.
465 The full distribution includes the C, C++, Objective-C, Fortran, Java,
466 and Ada (in the case of GCC 3.1 and later) compilers. The full
467 distribution also includes runtime libraries for C++, Objective-C,
468 Fortran, and Java. In GCC 3.0 and later versions, the GNU compiler
469 testsuites are also included in the full distribution.
471 If you choose to download specific components, you must download the core
472 GCC distribution plus any language specific distributions you wish to
473 use. The core distribution includes the C language front end as well as the
474 shared components. Each language has a tarball which includes the language
475 front end as well as the language runtime (when appropriate).
477 Unpack the core distribution as well as any language specific
478 distributions in the same directory.
480 If you also intend to build binutils (either to upgrade an existing
481 installation or for use in place of the corresponding tools of your
482 OS), unpack the binutils distribution either in the same directory or
483 a separate one. In the latter case, add symbolic links to any
484 components of the binutils you intend to build alongside the compiler
485 (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
486 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
493 @uref{./index.html,,Return to the GCC Installation page}
497 @c ***Configuration***********************************************************
499 @comment node-name, next, previous, up
500 @node Configuration, Building, Downloading the source, Installing GCC
504 @chapter Installing GCC: Configuration
506 @cindex Configuration
507 @cindex Installing GCC: Configuration
509 Like most GNU software, GCC must be configured before it can be built.
510 This document describes the recommended configuration procedure
511 for both native and cross targets.
513 We use @var{srcdir} to refer to the toplevel source directory for
514 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
516 If you obtained the sources via SVN, @var{srcdir} must refer to the top
517 @file{gcc} directory, the one where the @file{MAINTAINERS} can be found,
518 and not its @file{gcc} subdirectory, otherwise the build will fail.
520 If either @var{srcdir} or @var{objdir} is located on an automounted NFS
521 file system, the shell's built-in @command{pwd} command will return
522 temporary pathnames. Using these can lead to various sorts of build
523 problems. To avoid this issue, set the @env{PWDCMD} environment
524 variable to an automounter-aware @command{pwd} command, e.g.,
525 @command{pawd} or @samp{amq -w}, during the configuration and build
528 First, we @strong{highly} recommend that GCC be built into a
529 separate directory than the sources which does @strong{not} reside
530 within the source tree. This is how we generally build GCC; building
531 where @var{srcdir} == @var{objdir} should still work, but doesn't
532 get extensive testing; building where @var{objdir} is a subdirectory
533 of @var{srcdir} is unsupported.
535 If you have previously built GCC in the same directory for a
536 different target machine, do @samp{make distclean} to delete all files
537 that might be invalid. One of the files this deletes is @file{Makefile};
538 if @samp{make distclean} complains that @file{Makefile} does not exist
539 or issues a message like ``don't know how to make distclean'' it probably
540 means that the directory is already suitably clean. However, with the
541 recommended method of building in a separate @var{objdir}, you should
542 simply use a different @var{objdir} for each target.
544 Second, when configuring a native system, either @command{cc} or
545 @command{gcc} must be in your path or you must set @env{CC} in
546 your environment before running configure. Otherwise the configuration
550 Note that the bootstrap compiler and the resulting GCC must be link
551 compatible, else the bootstrap will fail with linker errors about
552 incompatible object file formats. Several multilibed targets are
553 affected by this requirement, see
555 @ref{Specific, host/target specific installation notes}.
558 @uref{specific.html,,host/target specific installation notes}.
567 % @var{srcdir}/configure [@var{options}] [@var{target}]
571 @heading Target specification
574 GCC has code to correctly determine the correct value for @var{target}
575 for nearly all native systems. Therefore, we highly recommend you not
576 provide a configure target when configuring a native compiler.
579 @var{target} must be specified as @option{--target=@var{target}}
580 when configuring a cross compiler; examples of valid targets would be
581 m68k-coff, sh-elf, etc.
584 Specifying just @var{target} instead of @option{--target=@var{target}}
585 implies that the host defaults to @var{target}.
589 @heading Options specification
591 Use @var{options} to override several configure time options for
592 GCC@. A list of supported @var{options} follows; @samp{configure
593 --help} may list other options, but those not listed below may not
594 work and should not normally be used.
596 Note that each @option{--enable} option has a corresponding
597 @option{--disable} option and that each @option{--with} option has a
598 corresponding @option{--without} option.
601 @item --prefix=@var{dirname}
602 Specify the toplevel installation
603 directory. This is the recommended way to install the tools into a directory
604 other than the default. The toplevel installation directory defaults to
607 We @strong{highly} recommend against @var{dirname} being the same or a
608 subdirectory of @var{objdir} or vice versa. If specifying a directory
609 beneath a user's home directory tree, some shells will not expand
610 @var{dirname} correctly if it contains the @samp{~} metacharacter; use
613 The following standard @command{autoconf} options are supported. Normally you
614 should not need to use these options.
616 @item --exec-prefix=@var{dirname}
617 Specify the toplevel installation directory for architecture-dependent
618 files. The default is @file{@var{prefix}}.
620 @item --bindir=@var{dirname}
621 Specify the installation directory for the executables called by users
622 (such as @command{gcc} and @command{g++}). The default is
623 @file{@var{exec-prefix}/bin}.
625 @item --libdir=@var{dirname}
626 Specify the installation directory for object code libraries and
627 internal data files of GCC@. The default is @file{@var{exec-prefix}/lib}.
629 @item --libexecdir=@var{dirname}
630 Specify the installation directory for internal executables of GCC@.
631 The default is @file{@var{exec-prefix}/libexec}.
633 @item --with-slibdir=@var{dirname}
634 Specify the installation directory for the shared libgcc library. The
635 default is @file{@var{libdir}}.
637 @item --infodir=@var{dirname}
638 Specify the installation directory for documentation in info format.
639 The default is @file{@var{prefix}/info}.
641 @item --datadir=@var{dirname}
642 Specify the installation directory for some architecture-independent
643 data files referenced by GCC@. The default is @file{@var{prefix}/share}.
645 @item --mandir=@var{dirname}
646 Specify the installation directory for manual pages. The default is
647 @file{@var{prefix}/man}. (Note that the manual pages are only extracts from
648 the full GCC manuals, which are provided in Texinfo format. The manpages
649 are derived by an automatic conversion process from parts of the full
652 @item --with-gxx-include-dir=@var{dirname}
654 the installation directory for G++ header files. The default is
655 @file{@var{prefix}/include/c++/@var{version}}.
659 @item --program-prefix=@var{prefix}
660 GCC supports some transformations of the names of its programs when
661 installing them. This option prepends @var{prefix} to the names of
662 programs to install in @var{bindir} (see above). For example, specifying
663 @option{--program-prefix=foo-} would result in @samp{gcc}
664 being installed as @file{/usr/local/bin/foo-gcc}.
666 @item --program-suffix=@var{suffix}
667 Appends @var{suffix} to the names of programs to install in @var{bindir}
668 (see above). For example, specifying @option{--program-suffix=-3.1}
669 would result in @samp{gcc} being installed as
670 @file{/usr/local/bin/gcc-3.1}.
672 @item --program-transform-name=@var{pattern}
673 Applies the @samp{sed} script @var{pattern} to be applied to the names
674 of programs to install in @var{bindir} (see above). @var{pattern} has to
675 consist of one or more basic @samp{sed} editing commands, separated by
676 semicolons. For example, if you want the @samp{gcc} program name to be
677 transformed to the installed program @file{/usr/local/bin/myowngcc} and
678 the @samp{g++} program name to be transformed to
679 @file{/usr/local/bin/gspecial++} without changing other program names,
680 you could use the pattern
681 @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}
682 to achieve this effect.
684 All three options can be combined and used together, resulting in more
685 complex conversion patterns. As a basic rule, @var{prefix} (and
686 @var{suffix}) are prepended (appended) before further transformations
687 can happen with a special transformation script @var{pattern}.
689 As currently implemented, this option only takes effect for native
690 builds; cross compiler binaries' names are not transformed even when a
691 transformation is explicitly asked for by one of these options.
693 For native builds, some of the installed programs are also installed
694 with the target alias in front of their name, as in
695 @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
696 before the target alias is prepended to the name---so, specifying
697 @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
698 resulting binary would be installed as
699 @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.
701 As a last shortcoming, none of the installed Ada programs are
702 transformed yet, which will be fixed in some time.
704 @item --with-local-prefix=@var{dirname}
706 installation directory for local include files. The default is
707 @file{/usr/local}. Specify this option if you want the compiler to
708 search directory @file{@var{dirname}/include} for locally installed
709 header files @emph{instead} of @file{/usr/local/include}.
711 You should specify @option{--with-local-prefix} @strong{only} if your
712 site has a different convention (not @file{/usr/local}) for where to put
715 The default value for @option{--with-local-prefix} is @file{/usr/local}
716 regardless of the value of @option{--prefix}. Specifying
717 @option{--prefix} has no effect on which directory GCC searches for
718 local header files. This may seem counterintuitive, but actually it is
721 The purpose of @option{--prefix} is to specify where to @emph{install
722 GCC}. The local header files in @file{/usr/local/include}---if you put
723 any in that directory---are not part of GCC@. They are part of other
724 programs---perhaps many others. (GCC installs its own header files in
725 another directory which is based on the @option{--prefix} value.)
727 Both the local-prefix include directory and the GCC-prefix include
728 directory are part of GCC's ``system include'' directories. Although these
729 two directories are not fixed, they need to be searched in the proper
730 order for the correct processing of the include_next directive. The
731 local-prefix include directory is searched before the GCC-prefix
732 include directory. Another characteristic of system include directories
733 is that pedantic warnings are turned off for headers in these directories.
735 Some autoconf macros add @option{-I @var{directory}} options to the
736 compiler command line, to ensure that directories containing installed
737 packages' headers are searched. When @var{directory} is one of GCC's
738 system include directories, GCC will ignore the option so that system
739 directories continue to be processed in the correct order. This
740 may result in a search order different from what was specified but the
741 directory will still be searched.
743 GCC automatically searches for ordinary libraries using
744 @env{GCC_EXEC_PREFIX}. Thus, when the same installation prefix is
745 used for both GCC and packages, GCC will automatically search for
746 both headers and libraries. This provides a configuration that is
747 easy to use. GCC behaves in a manner similar to that when it is
748 installed as a system compiler in @file{/usr}.
750 Sites that need to install multiple versions of GCC may not want to
751 use the above simple configuration. It is possible to use the
752 @option{--program-prefix}, @option{--program-suffix} and
753 @option{--program-transform-name} options to install multiple versions
754 into a single directory, but it may be simpler to use different prefixes
755 and the @option{--with-local-prefix} option to specify the location of the
756 site-specific files for each version. It will then be necessary for
757 users to specify explicitly the location of local site libraries
758 (e.g., with @env{LIBRARY_PATH}).
760 The same value can be used for both @option{--with-local-prefix} and
761 @option{--prefix} provided it is not @file{/usr}. This can be used
762 to avoid the default search of @file{/usr/local/include}.
764 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
765 The directory you use for @option{--with-local-prefix} @strong{must not}
766 contain any of the system's standard header files. If it did contain
767 them, certain programs would be miscompiled (including GNU Emacs, on
768 certain targets), because this would override and nullify the header
769 file corrections made by the @command{fixincludes} script.
771 Indications are that people who use this option use it based on mistaken
772 ideas of what it is for. People use it as if it specified where to
773 install part of GCC@. Perhaps they make this assumption because
774 installing GCC creates the directory.
776 @item --enable-shared[=@var{package}[,@dots{}]]
777 Build shared versions of libraries, if shared libraries are supported on
778 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
779 are enabled by default on all platforms that support shared libraries.
781 If a list of packages is given as an argument, build shared libraries
782 only for the listed packages. For other packages, only static libraries
783 will be built. Package names currently recognized in the GCC tree are
784 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
785 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc},
786 @samp{ada}, @samp{libada}, @samp{libjava} and @samp{libobjc}.
787 Note @samp{libiberty} does not support shared libraries at all.
789 Use @option{--disable-shared} to build only static libraries. Note that
790 @option{--disable-shared} does not accept a list of package names as
791 argument, only @option{--enable-shared} does.
793 @item @anchor{with-gnu-as}--with-gnu-as
794 Specify that the compiler should assume that the
795 assembler it finds is the GNU assembler. However, this does not modify
796 the rules to find an assembler and will result in confusion if the
797 assembler found is not actually the GNU assembler. (Confusion may also
798 result if the compiler finds the GNU assembler but has not been
799 configured with @option{--with-gnu-as}.) If you have more than one
800 assembler installed on your system, you may want to use this option in
801 connection with @option{--with-as=@var{pathname}} or
802 @option{--with-build-time-tools=@var{pathname}}.
804 The following systems are the only ones where it makes a difference
805 whether you use the GNU assembler. On any other system,
806 @option{--with-gnu-as} has no effect.
809 @item @samp{hppa1.0-@var{any}-@var{any}}
810 @item @samp{hppa1.1-@var{any}-@var{any}}
811 @item @samp{i386-@var{any}-sysv}
812 @item @samp{m68k-bull-sysv}
813 @item @samp{m68k-hp-hpux}
814 @item @samp{m68000-hp-hpux}
815 @item @samp{m68000-att-sysv}
816 @item @samp{sparc-sun-solaris2.@var{any}}
817 @item @samp{sparc64-@var{any}-solaris2.@var{any}}
820 On the systems listed above (except for the HP-PA, the SPARC, for ISC on
821 the 386, if you use the GNU assembler, you should also use the GNU linker
822 (and specify @option{--with-gnu-ld}).
824 @item @anchor{with-as}--with-as=@var{pathname}
825 Specify that the compiler should use the assembler pointed to by
826 @var{pathname}, rather than the one found by the standard rules to find
827 an assembler, which are:
830 Unless GCC is being built with a cross compiler, check the
831 @file{@var{libexec}/gcc/@var{target}/@var{version}} directory.
832 @var{libexec} defaults to @file{@var{exec-prefix}/libexec};
833 @var{exec-prefix} defaults to @var{prefix}, which
834 defaults to @file{/usr/local} unless overridden by the
835 @option{--prefix=@var{pathname}} switch described above. @var{target}
836 is the target system triple, such as @samp{sparc-sun-solaris2.7}, and
837 @var{version} denotes the GCC version, such as 3.0.
840 If the target system is the same that you are building on, check
841 operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
845 Check in the @env{PATH} for a tool whose name is prefixed by the
846 target system triple.
849 Check in the @env{PATH} for a tool whose name is not prefixed by the
850 target system triple, if the host and target system triple are
851 the same (in other words, we use a host tool if it can be used for
855 You may want to use @option{--with-as} if no assembler
856 is installed in the directories listed above, or if you have multiple
857 assemblers installed and want to choose one that is not found by the
860 @item @anchor{with-gnu-ld}--with-gnu-ld
861 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
864 @item --with-ld=@var{pathname}
865 Same as @uref{#with-as,,@option{--with-as}}
869 Specify that stabs debugging
870 information should be used instead of whatever format the host normally
871 uses. Normally GCC uses the same debug format as the host system.
873 On MIPS based systems and on Alphas, you must specify whether you want
874 GCC to create the normal ECOFF debugging format, or to use BSD-style
875 stabs passed through the ECOFF symbol table. The normal ECOFF debug
876 format cannot fully handle languages other than C@. BSD stabs format can
877 handle other languages, but it only works with the GNU debugger GDB@.
879 Normally, GCC uses the ECOFF debugging format by default; if you
880 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
882 No matter which default you choose when you configure GCC, the user
883 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
884 the debug format for a particular compilation.
886 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
887 @option{--with-gas} is used. It selects use of stabs debugging
888 information embedded in COFF output. This kind of debugging information
889 supports C++ well; ordinary COFF debugging information does not.
891 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
892 selects use of stabs debugging information embedded in ELF output. The
893 C++ compiler currently (2.6.0) does not support the DWARF debugging
894 information normally used on 386 SVR4 platforms; stabs provide a
895 workable alternative. This requires gas and gdb, as the normal SVR4
896 tools can not generate or interpret stabs.
898 @item --disable-multilib
899 Specify that multiple target
900 libraries to support different target variants, calling
901 conventions, etc should not be built. The default is to build a
902 predefined set of them.
904 Some targets provide finer-grained control over which multilibs are built
905 (e.g., @option{--disable-softfloat}):
911 fpu, 26bit, underscore, interwork, biendian, nofmult.
914 softfloat, m68881, m68000, m68020.
917 single-float, biendian, softfloat.
919 @item powerpc*-*-*, rs6000*-*-*
920 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
925 @item --enable-threads
926 Specify that the target
927 supports threads. This affects the Objective-C compiler and runtime
928 library, and exception handling for other languages like C++ and Java.
929 On some systems, this is the default.
931 In general, the best (and, in many cases, the only known) threading
932 model available will be configured for use. Beware that on some
933 systems, GCC has not been taught what threading models are generally
934 available for the system. In this case, @option{--enable-threads} is an
935 alias for @option{--enable-threads=single}.
937 @item --disable-threads
938 Specify that threading support should be disabled for the system.
939 This is an alias for @option{--enable-threads=single}.
941 @item --enable-threads=@var{lib}
943 @var{lib} is the thread support library. This affects the Objective-C
944 compiler and runtime library, and exception handling for other languages
945 like C++ and Java. The possibilities for @var{lib} are:
953 Ada tasking support. For non-Ada programs, this setting is equivalent
954 to @samp{single}. When used in conjunction with the Ada run time, it
955 causes GCC to use the same thread primitives as Ada uses. This option
956 is necessary when using both Ada and the back end exception handling,
957 which is the default for most Ada targets.
959 Generic MACH thread support, known to work on NeXTSTEP@. (Please note
960 that the file needed to support this configuration, @file{gthr-mach.h}, is
961 missing and thus this setting will cause a known bootstrap failure.)
963 This is an alias for @samp{single}.
965 Generic POSIX/Unix98 thread support.
967 Generic POSIX/Unix95 thread support.
969 RTEMS thread support.
971 Disable thread support, should work for all platforms.
973 Sun Solaris 2 thread support.
975 VxWorks thread support.
977 Microsoft Win32 API thread support.
979 Novell Kernel Services thread support.
983 Specify that the target supports TLS (Thread Local Storage). Usually
984 configure can correctly determine if TLS is supported. In cases where
985 it guesses incorrectly, TLS can be explicitly enabled or disabled with
986 @option{--enable-tls} or @option{--disable-tls}. This can happen if
987 the assembler supports TLS but the C library does not, or if the
988 assumptions made by the configure test are incorrect.
991 Specify that the target does not support TLS.
992 This is an alias for @option{--enable-tls=no}.
994 @item --with-cpu=@var{cpu}
995 Specify which cpu variant the compiler should generate code for by default.
996 @var{cpu} will be used as the default value of the @option{-mcpu=} switch.
997 This option is only supported on some targets, including ARM, i386, PowerPC,
1000 @item --with-schedule=@var{cpu}
1001 @itemx --with-arch=@var{cpu}
1002 @itemx --with-tune=@var{cpu}
1003 @itemx --with-abi=@var{abi}
1004 @itemx --with-fpu=@var{type}
1005 @itemx --with-float=@var{type}
1006 These configure options provide default values for the @option{-mschedule=},
1007 @option{-march=}, @option{-mtune=}, @option{-mabi=}, and @option{-mfpu=}
1008 options and for @option{-mhard-float} or @option{-msoft-float}. As with
1009 @option{--with-cpu}, which switches will be accepted and acceptable values
1010 of the arguments depend on the target.
1012 @item --with-mode=@var{mode}
1013 Specify if the compiler should default to @option{-marm} or @option{-mthumb}.
1014 This option is only supported on ARM targets.
1016 @item --with-divide=@var{type}
1017 Specify how the compiler should generate code for checking for
1018 division by zero. This option is only supported on the MIPS target.
1019 The possibilities for @var{type} are:
1022 Division by zero checks use conditional traps (this is the default on
1023 systems that support conditional traps).
1025 Division by zero checks use the break instruction.
1028 @item --enable-__cxa_atexit
1029 Define if you want to use __cxa_atexit, rather than atexit, to
1030 register C++ destructors for local statics and global objects.
1031 This is essential for fully standards-compliant handling of
1032 destructors, but requires __cxa_atexit in libc. This option is currently
1033 only available on systems with GNU libc. When enabled, this will cause
1034 @option{-fuse-cxa-exit} to be passed by default.
1036 @item --enable-target-optspace
1038 libraries should be optimized for code space instead of code speed.
1039 This is the default for the m32r platform.
1042 Specify that a user visible @command{cpp} program should not be installed.
1044 @item --with-cpp-install-dir=@var{dirname}
1045 Specify that the user visible @command{cpp} program should be installed
1046 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
1048 @item --enable-initfini-array
1049 Force the use of sections @code{.init_array} and @code{.fini_array}
1050 (instead of @code{.init} and @code{.fini}) for constructors and
1051 destructors. Option @option{--disable-initfini-array} has the
1052 opposite effect. If neither option is specified, the configure script
1053 will try to guess whether the @code{.init_array} and
1054 @code{.fini_array} sections are supported and, if they are, use them.
1056 @item --enable-maintainer-mode
1057 The build rules that
1058 regenerate the GCC master message catalog @file{gcc.pot} are normally
1059 disabled. This is because it can only be rebuilt if the complete source
1060 tree is present. If you have changed the sources and want to rebuild the
1061 catalog, configuring with @option{--enable-maintainer-mode} will enable
1062 this. Note that you need a recent version of the @code{gettext} tools
1065 @item --disable-bootstrap
1066 For a native build, the default configuration is to perform
1067 a 3-stage bootstrap of the compiler when @samp{make} is invoked,
1068 testing that GCC can compile itself correctly. If you want to disable
1069 this process, you can configure with @option{--disable-bootstrap}.
1071 @item --enable-bootstrap
1072 In special cases, you may want to perform a 3-stage build
1073 even if the target and host triplets are different.
1074 This could happen when the host can run code compiled for
1075 the target (e.g.@: host is i686-linux, target is i486-linux).
1076 Starting from GCC 4.2, to do this you have to configure explicitly
1077 with @option{--enable-bootstrap}.
1079 @item --enable-generated-files-in-srcdir
1080 Neither the .c and .h files that are generated from Bison and flex nor the
1081 info manuals and man pages that are built from the .texi files are present
1082 in the SVN development tree. When building GCC from that development tree,
1083 or from one of our snapshots, those generated files are placed in your
1084 build directory, which allows for the source to be in a readonly
1087 If you configure with @option{--enable-generated-files-in-srcdir} then those
1088 generated files will go into the source directory. This is mainly intended
1089 for generating release or prerelease tarballs of the GCC sources, since it
1090 is not a requirement that the users of source releases to have flex, Bison,
1093 @item --enable-version-specific-runtime-libs
1095 that runtime libraries should be installed in the compiler specific
1096 subdirectory (@file{@var{libdir}/gcc}) rather than the usual places. In
1097 addition, @samp{libstdc++}'s include files will be installed into
1098 @file{@var{libdir}} unless you overruled it by using
1099 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
1100 particularly useful if you intend to use several versions of GCC in
1101 parallel. This is currently supported by @samp{libgfortran},
1102 @samp{libjava}, @samp{libmudflap}, @samp{libstdc++}, and @samp{libobjc}.
1104 @item --with-java-home=@var{dirname}
1105 This @samp{libjava} option overrides the default value of the
1106 @samp{java.home} system property. It is also used to set
1107 @samp{sun.boot.class.path} to @file{@var{dirname}/lib/rt.jar}. By
1108 default @samp{java.home} is set to @file{@var{prefix}} and
1109 @samp{sun.boot.class.path} to
1110 @file{@var{datadir}/java/libgcj-@var{version}.jar}.
1112 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
1113 Specify that only a particular subset of compilers and
1114 their runtime libraries should be built. For a list of valid values for
1115 @var{langN} you can issue the following command in the
1116 @file{gcc} directory of your GCC source tree:@*
1118 grep language= */config-lang.in
1120 Currently, you can use any of the following:
1121 @code{all}, @code{ada}, @code{c}, @code{c++}, @code{fortran}, @code{java},
1122 @code{objc}, @code{obj-c++}, @code{treelang}.
1123 Building the Ada compiler has special requirements, see below.
1124 If you do not pass this flag, or specify the option @code{all}, then all
1125 default languages available in the @file{gcc} sub-tree will be configured.
1126 Ada, Objective-C++, and treelang are not default languages; the rest are.
1127 Re-defining @code{LANGUAGES} when calling @samp{make} @strong{does not}
1128 work anymore, as those language sub-directories might not have been
1131 @item --disable-libada
1132 Specify that the run-time libraries and tools used by GNAT should not
1133 be built. This can be useful for debugging, or for compatibility with
1134 previous Ada build procedures, when it was required to explicitly
1135 do a @samp{make -C gcc gnatlib_and_tools}.
1137 @item --disable-libssp
1138 Specify that the run-time libraries for stack smashing protection
1139 should not be built.
1141 @item --disable-libgomp
1142 Specify that the run-time libraries used by GOMP should not be built.
1145 Specify that the compiler should
1146 use DWARF 2 debugging information as the default.
1148 @item --enable-targets=all
1149 @itemx --enable-targets=@var{target_list}
1150 Some GCC targets, e.g.@: powerpc64-linux, build bi-arch compilers.
1151 These are compilers that are able to generate either 64-bit or 32-bit
1152 code. Typically, the corresponding 32-bit target, e.g.@:
1153 powerpc-linux for powerpc64-linux, only generates 32-bit code. This
1154 option enables the 32-bit target to be a bi-arch compiler, which is
1155 useful when you want a bi-arch compiler that defaults to 32-bit, and
1156 you are building a bi-arch or multi-arch binutils in a combined tree.
1157 Currently, this option only affects powerpc-linux.
1159 @item --enable-secureplt
1160 This option enables @option{-msecure-plt} by default for powerpc-linux.
1162 @xref{RS/6000 and PowerPC Options,, RS/6000 and PowerPC Options, gcc,
1163 Using the GNU Compiler Collection (GCC)},
1166 See ``RS/6000 and PowerPC Options'' in the main manual
1169 @item --enable-win32-registry
1170 @itemx --enable-win32-registry=@var{key}
1171 @itemx --disable-win32-registry
1172 The @option{--enable-win32-registry} option enables Microsoft Windows-hosted GCC
1173 to look up installations paths in the registry using the following key:
1176 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
1179 @var{key} defaults to GCC version number, and can be overridden by the
1180 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
1181 who use custom installers are encouraged to provide a different key,
1182 perhaps one comprised of vendor name and GCC version number, to
1183 avoid conflict with existing installations. This feature is enabled
1184 by default, and can be disabled by @option{--disable-win32-registry}
1185 option. This option has no effect on the other hosts.
1188 Specify that the machine does not have a floating point unit. This
1189 option only applies to @samp{m68k-sun-sunos@var{n}}. On any other
1190 system, @option{--nfp} has no effect.
1192 @item --enable-werror
1193 @itemx --disable-werror
1194 @itemx --enable-werror=yes
1195 @itemx --enable-werror=no
1196 When you specify this option, it controls whether certain files in the
1197 compiler are built with @option{-Werror} in bootstrap stage2 and later.
1198 If you don't specify it, @option{-Werror} is turned on for the main
1199 development trunk. However it defaults to off for release branches and
1200 final releases. The specific files which get @option{-Werror} are
1201 controlled by the Makefiles.
1203 @item --enable-checking
1204 @itemx --enable-checking=@var{list}
1205 When you specify this option, the compiler is built to perform internal
1206 consistency checks of the requested complexity. This does not change the
1207 generated code, but adds error checking within the compiler. This will
1208 slow down the compiler and may only work properly if you are building
1209 the compiler with GCC@. This is @samp{yes} by default when building
1210 from SVN or snapshots, but @samp{release} for releases. More control
1211 over the checks may be had by specifying @var{list}. The categories of
1212 checks available are @samp{yes} (most common checks
1213 @samp{assert,misc,tree,gc,rtlflag,runtime}), @samp{no} (no checks at
1214 all), @samp{all} (all but @samp{valgrind}), @samp{release} (cheapest
1215 checks @samp{assert,runtime}) or @samp{none} (same as @samp{no}).
1216 Individual checks can be enabled with these flags @samp{assert},
1217 @samp{fold}, @samp{gc}, @samp{gcac} @samp{misc}, @samp{rtl},
1218 @samp{rtlflag}, @samp{runtime}, @samp{tree}, and @samp{valgrind}.
1220 The @samp{valgrind} check requires the external @command{valgrind}
1221 simulator, available from @uref{http://valgrind.org/}. The
1222 @samp{rtl}, @samp{gcac} and @samp{valgrind} checks are very expensive.
1223 To disable all checking, @samp{--disable-checking} or
1224 @samp{--enable-checking=none} must be explicitly requested. Disabling
1225 assertions will make the compiler and runtime slightly faster but
1226 increase the risk of undetected internal errors causing wrong code to be
1229 @item --enable-coverage
1230 @itemx --enable-coverage=@var{level}
1231 With this option, the compiler is built to collect self coverage
1232 information, every time it is run. This is for internal development
1233 purposes, and only works when the compiler is being built with gcc. The
1234 @var{level} argument controls whether the compiler is built optimized or
1235 not, values are @samp{opt} and @samp{noopt}. For coverage analysis you
1236 want to disable optimization, for performance analysis you want to
1237 enable optimization. When coverage is enabled, the default level is
1238 without optimization.
1240 @item --enable-gather-detailed-mem-stats
1241 When this option is specified more detailed information on memory
1242 allocation is gathered. This information is printed when using
1243 @option{-fmem-report}.
1246 @itemx --with-gc=@var{choice}
1247 With this option you can specify the garbage collector implementation
1248 used during the compilation process. @var{choice} can be one of
1249 @samp{page} and @samp{zone}, where @samp{page} is the default.
1252 @itemx --disable-nls
1253 The @option{--enable-nls} option enables Native Language Support (NLS),
1254 which lets GCC output diagnostics in languages other than American
1255 English. Native Language Support is enabled by default if not doing a
1256 canadian cross build. The @option{--disable-nls} option disables NLS@.
1258 @item --with-included-gettext
1259 If NLS is enabled, the @option{--with-included-gettext} option causes the build
1260 procedure to prefer its copy of GNU @command{gettext}.
1262 @item --with-catgets
1263 If NLS is enabled, and if the host lacks @code{gettext} but has the
1264 inferior @code{catgets} interface, the GCC build procedure normally
1265 ignores @code{catgets} and instead uses GCC's copy of the GNU
1266 @code{gettext} library. The @option{--with-catgets} option causes the
1267 build procedure to use the host's @code{catgets} in this situation.
1269 @item --with-libiconv-prefix=@var{dir}
1270 Search for libiconv header files in @file{@var{dir}/include} and
1271 libiconv library files in @file{@var{dir}/lib}.
1273 @item --enable-obsolete
1274 Enable configuration for an obsoleted system. If you attempt to
1275 configure GCC for a system (build, host, or target) which has been
1276 obsoleted, and you do not specify this flag, configure will halt with an
1279 All support for systems which have been obsoleted in one release of GCC
1280 is removed entirely in the next major release, unless someone steps
1281 forward to maintain the port.
1283 @item --enable-decimal-float
1284 @itemx --disable-decimal-float
1285 Enable (or disable) support for the C decimal floating point
1286 extension. This is enabled by default only on PowerPC GNU/Linux
1287 systems. Other systems may also support it, but require the user to
1288 specifically enable it.
1290 @item --with-long-double-128
1291 Specify if @code{long double} type should be 128-bit by default on selected
1292 GNU/Linux architectures. If using @code{--without-long-double-128},
1293 @code{long double} will be by default 64-bit, the same as @code{double} type.
1294 When neither of these configure options are used, the default will be
1295 128-bit @code{long double} when built against GNU C Library 2.4 and later,
1296 64-bit @code{long double} otherwise.
1300 @subheading Cross-Compiler-Specific Options
1301 The following options only apply to building cross compilers.
1303 @item --with-sysroot
1304 @itemx --with-sysroot=@var{dir}
1305 Tells GCC to consider @var{dir} as the root of a tree that contains a
1306 (subset of) the root filesystem of the target operating system.
1307 Target system headers, libraries and run-time object files will be
1308 searched in there. The specified directory is not copied into the
1309 install tree, unlike the options @option{--with-headers} and
1310 @option{--with-libs} that this option obsoletes. The default value,
1311 in case @option{--with-sysroot} is not given an argument, is
1312 @option{$@{gcc_tooldir@}/sys-root}. If the specified directory is a
1313 subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to
1314 the GCC binaries if the installation tree is moved.
1316 @item --with-build-sysroot
1317 @itemx --with-build-sysroot=@var{dir}
1318 Tells GCC to consider @var{dir} as the system root (see
1319 @option{--with-sysroot}) while building target libraries, instead of
1320 the directory specified with @option{--with-sysroot}. This option is
1321 only useful when you are already using @option{--with-sysroot}. You
1322 can use @option{--with-build-sysroot} when you are configuring with
1323 @option{--prefix} set to a directory that is different from the one in
1324 which you are installing GCC and your target libraries.
1326 This option affects the system root for the compiler used to build
1327 target libraries (which runs on the build system); it does not affect
1328 the compiler which is used to build GCC itself.
1330 @item --with-headers
1331 @itemx --with-headers=@var{dir}
1332 Deprecated in favor of @option{--with-sysroot}.
1333 Specifies that target headers are available when building a cross compiler.
1334 The @var{dir} argument specifies a directory which has the target include
1335 files. These include files will be copied into the @file{gcc} install
1336 directory. @emph{This option with the @var{dir} argument is required} when
1337 building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include}
1338 doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does
1339 pre-exist, the @var{dir} argument may be omitted. @command{fixincludes}
1340 will be run on these files to make them compatible with GCC@.
1342 @item --without-headers
1343 Tells GCC not use any target headers from a libc when building a cross
1344 compiler. When crossing to GNU/Linux, you need the headers so GCC
1345 can build the exception handling for libgcc.
1348 @itemx --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
1349 Deprecated in favor of @option{--with-sysroot}.
1350 Specifies a list of directories which contain the target runtime
1351 libraries. These libraries will be copied into the @file{gcc} install
1352 directory. If the directory list is omitted, this option has no
1356 Specifies that @samp{newlib} is
1357 being used as the target C library. This causes @code{__eprintf} to be
1358 omitted from @file{libgcc.a} on the assumption that it will be provided by
1361 @item --with-build-time-tools=@var{dir}
1362 Specifies where to find the set of target tools (assembler, linker, etc.)
1363 that will be used while building GCC itself. This option can be useful
1364 if the directory layouts are different between the system you are building
1365 GCC on, and the system where you will deploy it.
1367 For example, on a @option{ia64-hp-hpux} system, you may have the GNU
1368 assembler and linker in @file{/usr/bin}, and the native tools in a
1369 different path, and build a toolchain that expects to find the
1370 native tools in @file{/usr/bin}.
1372 When you use this option, you should ensure that @var{dir} includes
1373 @command{ar}, @command{as}, @command{ld}, @command{nm},
1374 @command{ranlib} and @command{strip} if necessary, and possibly
1375 @command{objdump}. Otherwise, GCC may use an inconsistent set of
1379 @subheading Fortran-Specific Options
1381 The following options apply to the build of the Fortran front end.
1385 @item --with-gmp=@var{pathname}
1386 @itemx --with-mpfr=@var{pathname}
1387 @itemx --with-gmp-dir=@var{pathname}
1388 @itemx --with-mpfr-dir=@var{pathname}
1389 If you don't have GMP (the GNU Multiple Precision library) and the MPFR
1390 Libraries installed in a standard location and you want to build the Fortran
1391 front-end, you can explicitly specify the directory where they are installed
1392 (@samp{--with-gmp=gmpinstalldir}, @samp{--with-mpfr=mpfrinstalldir}) or where
1393 you built them without installing (@samp{--with-gmp-dir=gmpbuilddir},
1394 @samp{--with-mpfr-dir=gmpbuilddir}).
1398 @subheading Java-Specific Options
1400 The following option applies to the build of the Java front end.
1403 @item --disable-libgcj
1404 Specify that the run-time libraries
1405 used by GCJ should not be built. This is useful in case you intend
1406 to use GCJ with some other run-time, or you're going to install it
1407 separately, or it just happens not to build on your particular
1408 machine. In general, if the Java front end is enabled, the GCJ
1409 libraries will be enabled too, unless they're known to not work on
1410 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
1411 may need to port it; in this case, before modifying the top-level
1412 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
1413 you may use @option{--enable-libgcj} to override the default.
1417 The following options apply to building @samp{libgcj}.
1419 @subsubheading General Options
1422 @item --disable-getenv-properties
1423 Don't set system properties from @env{GCJ_PROPERTIES}.
1425 @item --enable-hash-synchronization
1426 Use a global hash table for monitor locks. Ordinarily,
1427 @samp{libgcj}'s @samp{configure} script automatically makes
1428 the correct choice for this option for your platform. Only use
1429 this if you know you need the library to be configured differently.
1431 @item --enable-interpreter
1432 Enable the Java interpreter. The interpreter is automatically
1433 enabled by default on all platforms that support it. This option
1434 is really only useful if you want to disable the interpreter
1435 (using @option{--disable-interpreter}).
1437 @item --disable-java-net
1438 Disable java.net. This disables the native part of java.net only,
1439 using non-functional stubs for native method implementations.
1441 @item --disable-jvmpi
1442 Disable JVMPI support.
1445 Enable runtime eCos target support.
1447 @item --without-libffi
1448 Don't use @samp{libffi}. This will disable the interpreter and JNI
1449 support as well, as these require @samp{libffi} to work.
1451 @item --enable-libgcj-debug
1452 Enable runtime debugging code.
1454 @item --enable-libgcj-multifile
1455 If specified, causes all @file{.java} source files to be
1456 compiled into @file{.class} files in one invocation of
1457 @samp{gcj}. This can speed up build time, but is more
1458 resource-intensive. If this option is unspecified or
1459 disabled, @samp{gcj} is invoked once for each @file{.java}
1460 file to compile into a @file{.class} file.
1462 @item --with-libiconv-prefix=DIR
1463 Search for libiconv in @file{DIR/include} and @file{DIR/lib}.
1465 @item --enable-sjlj-exceptions
1466 Force use of the @code{setjmp}/@code{longjmp}-based scheme for exceptions.
1467 @samp{configure} ordinarily picks the correct value based on the platform.
1468 Only use this option if you are sure you need a different setting.
1470 @item --with-system-zlib
1471 Use installed @samp{zlib} rather than that included with GCC@.
1473 @item --with-win32-nlsapi=ansi, unicows or unicode
1474 Indicates how MinGW @samp{libgcj} translates between UNICODE
1475 characters and the Win32 API@.
1478 Use the single-byte @code{char} and the Win32 A functions natively,
1479 translating to and from UNICODE when using these functions. If
1480 unspecified, this is the default.
1483 Use the @code{WCHAR} and Win32 W functions natively. Adds
1484 @code{-lunicows} to @file{libgcj.spec} to link with @samp{libunicows}.
1485 @file{unicows.dll} needs to be deployed on Microsoft Windows 9X machines
1486 running built executables. @file{libunicows.a}, an open-source
1487 import library around Microsoft's @code{unicows.dll}, is obtained from
1488 @uref{http://libunicows.sourceforge.net/}, which also gives details
1489 on getting @file{unicows.dll} from Microsoft.
1492 Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not}
1493 add @code{-lunicows} to @file{libgcj.spec}. The built executables will
1494 only run on Microsoft Windows NT and above.
1498 @subsubheading AWT-Specific Options
1502 Use the X Window System.
1504 @item --enable-java-awt=PEER(S)
1505 Specifies the AWT peer library or libraries to build alongside
1506 @samp{libgcj}. If this option is unspecified or disabled, AWT
1507 will be non-functional. Current valid values are @option{gtk} and
1508 @option{xlib}. Multiple libraries should be separated by a
1509 comma (i.e.@: @option{--enable-java-awt=gtk,xlib}).
1511 @item --enable-gtk-cairo
1512 Build the cairo Graphics2D implementation on GTK@.
1514 @item --enable-java-gc=TYPE
1515 Choose garbage collector. Defaults to @option{boehm} if unspecified.
1517 @item --disable-gtktest
1518 Do not try to compile and run a test GTK+ program.
1520 @item --disable-glibtest
1521 Do not try to compile and run a test GLIB program.
1523 @item --with-libart-prefix=PFX
1524 Prefix where libart is installed (optional).
1526 @item --with-libart-exec-prefix=PFX
1527 Exec prefix where libart is installed (optional).
1529 @item --disable-libarttest
1530 Do not try to compile and run a test libart program.
1539 @uref{./index.html,,Return to the GCC Installation page}
1543 @c ***Building****************************************************************
1545 @comment node-name, next, previous, up
1546 @node Building, Testing, Configuration, Installing GCC
1552 @cindex Installing GCC: Building
1554 Now that GCC is configured, you are ready to build the compiler and
1557 Some commands executed when making the compiler may fail (return a
1558 nonzero status) and be ignored by @command{make}. These failures, which
1559 are often due to files that were not found, are expected, and can safely
1562 It is normal to have compiler warnings when compiling certain files.
1563 Unless you are a GCC developer, you can generally ignore these warnings
1564 unless they cause compilation to fail. Developers should attempt to fix
1565 any warnings encountered, however they can temporarily continue past
1566 warnings-as-errors by specifying the configure flag
1567 @option{--disable-werror}.
1569 On certain old systems, defining certain environment variables such as
1570 @env{CC} can interfere with the functioning of @command{make}.
1572 If you encounter seemingly strange errors when trying to build the
1573 compiler in a directory other than the source directory, it could be
1574 because you have previously configured the compiler in the source
1575 directory. Make sure you have done all the necessary preparations.
1577 If you build GCC on a BSD system using a directory stored in an old System
1578 V file system, problems may occur in running @command{fixincludes} if the
1579 System V file system doesn't support symbolic links. These problems
1580 result in a failure to fix the declaration of @code{size_t} in
1581 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
1582 that type mismatches occur, this could be the cause.
1584 The solution is not to use such a directory for building GCC@.
1586 When building from SVN or snapshots, or if you modify parser sources,
1587 you need the Bison parser generator installed. If you do not modify
1588 parser sources, releases contain the Bison-generated files and you do
1589 not need Bison installed to build them.
1591 When building from SVN or snapshots, or if you modify Texinfo
1592 documentation, you need version 4.4 or later of Texinfo installed if you
1593 want Info documentation to be regenerated. Releases contain Info
1594 documentation pre-built for the unmodified documentation in the release.
1596 @section Building a native compiler
1598 For a native build, the default configuration is to perform
1599 a 3-stage bootstrap of the compiler when @samp{make} is invoked.
1600 This will build the entire GCC system and ensure that it compiles
1601 itself correctly. It can be disabled with the @option{--disable-bootstrap}
1602 parameter to @samp{configure}, but bootstrapping is suggested because
1603 the compiler will be tested more completely and could also have
1606 The bootstrapping process will complete the following steps:
1610 Build tools necessary to build the compiler.
1613 Perform a 3-stage bootstrap of the compiler. This includes building
1614 three times the target tools for use by the compiler such as binutils
1615 (bfd, binutils, gas, gprof, ld, and opcodes) if they have been
1616 individually linked or moved into the top level GCC source tree before
1620 Perform a comparison test of the stage2 and stage3 compilers.
1623 Build runtime libraries using the stage3 compiler from the previous step.
1627 If you are short on disk space you might consider @samp{make
1628 bootstrap-lean} instead. The sequence of compilation is the
1629 same described above, but object files from the stage1 and
1630 stage2 of the 3-stage bootstrap of the compiler are deleted as
1631 soon as they are no longer needed.
1633 If you want to save additional space during the bootstrap and in
1634 the final installation as well, you can build the compiler binaries
1635 without debugging information as in the following example. This will save
1636 roughly 40% of disk space both for the bootstrap and the final installation.
1637 (Libraries will still contain debugging information.)
1640 make CFLAGS='-O' LIBCFLAGS='-g -O2' \
1641 LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap
1644 If you wish to use non-default GCC flags when compiling the stage2 and
1645 stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing
1646 @samp{make}. Non-default optimization flags are less well
1647 tested here than the default of @samp{-g -O2}, but should still work.
1648 In a few cases, you may find that you need to specify special flags such
1649 as @option{-msoft-float} here to complete the bootstrap; or, if the
1650 native compiler miscompiles the stage1 compiler, you may need to work
1651 around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the
1652 stage1 compiler that were miscompiled, or by using @samp{make
1653 bootstrap4} to increase the number of stages of bootstrap.
1655 Note that using non-standard @code{CFLAGS} can cause bootstrap to fail
1656 if these trigger a warning with the new compiler. For example using
1657 @samp{-O2 -g -mcpu=i686} on @code{i686-pc-linux-gnu} will cause bootstrap
1658 failure as @option{-mcpu=} is deprecated in 3.4.0 and above.
1661 If you used the flag @option{--enable-languages=@dots{}} to restrict
1662 the compilers to be built, only those you've actually enabled will be
1663 built. This will of course only build those runtime libraries, for
1664 which the particular compiler has been built. Please note,
1665 that re-defining @env{LANGUAGES} when calling @samp{make}
1666 @strong{does not} work anymore!
1668 If the comparison of stage2 and stage3 fails, this normally indicates
1669 that the stage2 compiler has compiled GCC incorrectly, and is therefore
1670 a potentially serious bug which you should investigate and report. (On
1671 a few systems, meaningful comparison of object files is impossible; they
1672 always appear ``different''. If you encounter this problem, you will
1673 need to disable comparison in the @file{Makefile}.)
1675 If you do not want to bootstrap your compiler, you can configure with
1676 @option{--disable-bootstrap}. In particular cases, you may want to
1677 bootstrap your compiler even if the target system is not the same as
1678 the one you are building on: for example, you could build a
1679 @code{powerpc-unknown-linux-gnu} toolchain on a
1680 @code{powerpc64-unknown-linux-gnu} host. In this case, pass
1681 @option{--enable-bootstrap} to the configure script.
1684 @section Building a cross compiler
1686 When building a cross compiler, it is not generally possible to do a
1687 3-stage bootstrap of the compiler. This makes for an interesting problem
1688 as parts of GCC can only be built with GCC@.
1690 To build a cross compiler, we first recommend building and installing a
1691 native compiler. You can then use the native GCC compiler to build the
1692 cross compiler. The installed native compiler needs to be GCC version
1695 Assuming you have already installed a native copy of GCC and configured
1696 your cross compiler, issue the command @command{make}, which performs the
1701 Build host tools necessary to build the compiler.
1704 Build target tools for use by the compiler such as binutils (bfd,
1705 binutils, gas, gprof, ld, and opcodes)
1706 if they have been individually linked or moved into the top level GCC source
1707 tree before configuring.
1710 Build the compiler (single stage only).
1713 Build runtime libraries using the compiler from the previous step.
1716 Note that if an error occurs in any step the make process will exit.
1718 If you are not building GNU binutils in the same source tree as GCC,
1719 you will need a cross-assembler and cross-linker installed before
1720 configuring GCC@. Put them in the directory
1721 @file{@var{prefix}/@var{target}/bin}. Here is a table of the tools
1722 you should put in this directory:
1726 This should be the cross-assembler.
1729 This should be the cross-linker.
1732 This should be the cross-archiver: a program which can manipulate
1733 archive files (linker libraries) in the target machine's format.
1736 This should be a program to construct a symbol table in an archive file.
1739 The installation of GCC will find these programs in that directory,
1740 and copy or link them to the proper place to for the cross-compiler to
1741 find them when run later.
1743 The easiest way to provide these files is to build the Binutils package.
1744 Configure it with the same @option{--host} and @option{--target}
1745 options that you use for configuring GCC, then build and install
1746 them. They install their executables automatically into the proper
1747 directory. Alas, they do not support all the targets that GCC
1750 If you are not building a C library in the same source tree as GCC,
1751 you should also provide the target libraries and headers before
1752 configuring GCC, specifying the directories with
1753 @option{--with-sysroot} or @option{--with-headers} and
1754 @option{--with-libs}. Many targets also require ``start files'' such
1755 as @file{crt0.o} and
1756 @file{crtn.o} which are linked into each executable. There may be several
1757 alternatives for @file{crt0.o}, for use with profiling or other
1758 compilation options. Check your target's definition of
1759 @code{STARTFILE_SPEC} to find out what start files it uses.
1761 @section Building in parallel
1763 GNU Make 3.79 and above, which is necessary to build GCC, support
1764 building in parallel. To activate this, you can use @samp{make -j 2}
1765 instead of @samp{make}. You can also specify a bigger number, and
1766 in most cases using a value greater than the number of processors in
1767 your machine will result in fewer and shorter I/O latency hits, thus
1768 improving overall throughput; this is especially true for slow drives
1769 and network filesystems.
1771 @section Building the Ada compiler
1773 In order to build GNAT, the Ada compiler, you need a working GNAT
1774 compiler (GNAT version 3.14 or later, or GCC version 3.1 or later).
1775 This includes GNAT tools such as @command{gnatmake} and
1776 @command{gnatlink}, since the Ada front end is written in Ada and
1777 uses some GNAT-specific extensions.
1779 In order to build a cross compiler, it is suggested to install
1780 the new compiler as native first, and then use it to build the cross
1783 @command{configure} does not test whether the GNAT installation works
1784 and has a sufficiently recent version; if too old a GNAT version is
1785 installed, the build will fail unless @option{--enable-languages} is
1786 used to disable building the Ada front end.
1788 @section Building with profile feedback
1790 It is possible to use profile feedback to optimize the compiler itself. This
1791 should result in a faster compiler binary. Experiments done on x86 using gcc
1792 3.3 showed approximately 7 percent speedup on compiling C programs. To
1793 bootstrap the compiler with profile feedback, use @code{make profiledbootstrap}.
1795 When @samp{make profiledbootstrap} is run, it will first build a @code{stage1}
1796 compiler. This compiler is used to build a @code{stageprofile} compiler
1797 instrumented to collect execution counts of instruction and branch
1798 probabilities. Then runtime libraries are compiled with profile collected.
1799 Finally a @code{stagefeedback} compiler is built using the information collected.
1801 Unlike standard bootstrap, several additional restrictions apply. The
1802 compiler used to build @code{stage1} needs to support a 64-bit integral type.
1803 It is recommended to only use GCC for this. Also parallel make is currently
1804 not supported since collisions in profile collecting may occur.
1811 @uref{./index.html,,Return to the GCC Installation page}
1815 @c ***Testing*****************************************************************
1817 @comment node-name, next, previous, up
1818 @node Testing, Final install, Building, Installing GCC
1822 @chapter Installing GCC: Testing
1825 @cindex Installing GCC: Testing
1828 Before you install GCC, we encourage you to run the testsuites and to
1829 compare your results with results from a similar configuration that have
1830 been submitted to the
1831 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
1832 Some of these archived results are linked from the build status lists
1833 at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who
1834 reports a successful build runs the testsuites and submits the results.
1835 This step is optional and may require you to download additional software,
1836 but it can give you confidence in your new GCC installation or point out
1837 problems before you install and start using your new GCC@.
1839 First, you must have @uref{download.html,,downloaded the testsuites}.
1840 These are part of the full distribution, but if you downloaded the
1841 ``core'' compiler plus any front ends, you must download the testsuites
1844 Second, you must have the testing tools installed. This includes
1845 @uref{http://www.gnu.org/software/dejagnu/,,DejaGnu}, Tcl, and Expect;
1846 the DejaGnu site has links to these.
1848 If the directories where @command{runtest} and @command{expect} were
1849 installed are not in the @env{PATH}, you may need to set the following
1850 environment variables appropriately, as in the following example (which
1851 assumes that DejaGnu has been installed under @file{/usr/local}):
1854 TCL_LIBRARY = /usr/local/share/tcl8.0
1855 DEJAGNULIBS = /usr/local/share/dejagnu
1858 (On systems such as Cygwin, these paths are required to be actual
1859 paths, not mounts or links; presumably this is due to some lack of
1860 portability in the DejaGnu code.)
1863 Finally, you can run the testsuite (which may take a long time):
1865 cd @var{objdir}; make -k check
1868 This will test various components of GCC, such as compiler
1869 front ends and runtime libraries. While running the testsuite, DejaGnu
1870 might emit some harmless messages resembling
1871 @samp{WARNING: Couldn't find the global config file.} or
1872 @samp{WARNING: Couldn't find tool init file} that can be ignored.
1874 @section How can you run the testsuite on selected tests?
1876 In order to run sets of tests selectively, there are targets
1877 @samp{make check-gcc} and @samp{make check-g++}
1878 in the @file{gcc} subdirectory of the object directory. You can also
1879 just run @samp{make check} in a subdirectory of the object directory.
1882 A more selective way to just run all @command{gcc} execute tests in the
1886 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
1889 Likewise, in order to run only the @command{g++} ``old-deja'' tests in
1890 the testsuite with filenames matching @samp{9805*}, you would use
1893 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
1896 The @file{*.exp} files are located in the testsuite directories of the GCC
1897 source, the most important ones being @file{compile.exp},
1898 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
1899 To get a list of the possible @file{*.exp} files, pipe the
1900 output of @samp{make check} into a file and look at the
1901 @samp{Running @dots{} .exp} lines.
1903 @section Passing options and running multiple testsuites
1905 You can pass multiple options to the testsuite using the
1906 @samp{--target_board} option of DejaGNU, either passed as part of
1907 @samp{RUNTESTFLAGS}, or directly to @command{runtest} if you prefer to
1908 work outside the makefiles. For example,
1911 make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fno-strength-reduce"
1914 will run the standard @command{g++} testsuites (``unix'' is the target name
1915 for a standard native testsuite situation), passing
1916 @samp{-O3 -fno-strength-reduce} to the compiler on every test, i.e.,
1917 slashes separate options.
1919 You can run the testsuites multiple times using combinations of options
1920 with a syntax similar to the brace expansion of popular shells:
1923 @dots{}"--target_board=arm-sim/@{-mhard-float,-msoft-float@}@{-O1,-O2,-O3,@}"
1926 (Note the empty option caused by the trailing comma in the final group.)
1927 The following will run each testsuite eight times using the @samp{arm-sim}
1928 target, as if you had specified all possible combinations yourself:
1931 --target_board=arm-sim/-mhard-float/-O1
1932 --target_board=arm-sim/-mhard-float/-O2
1933 --target_board=arm-sim/-mhard-float/-O3
1934 --target_board=arm-sim/-mhard-float
1935 --target_board=arm-sim/-msoft-float/-O1
1936 --target_board=arm-sim/-msoft-float/-O2
1937 --target_board=arm-sim/-msoft-float/-O3
1938 --target_board=arm-sim/-msoft-float
1941 They can be combined as many times as you wish, in arbitrary ways. This
1945 @dots{}"--target_board=unix/-Wextra@{-O3,-fno-strength-reduce@}@{-fomit-frame-pointer,@}"
1948 will generate four combinations, all involving @samp{-Wextra}.
1950 The disadvantage to this method is that the testsuites are run in serial,
1951 which is a waste on multiprocessor systems. For users with GNU Make and
1952 a shell which performs brace expansion, you can run the testsuites in
1953 parallel by having the shell perform the combinations and @command{make}
1954 do the parallel runs. Instead of using @samp{--target_board}, use a
1955 special makefile target:
1958 make -j@var{N} check-@var{testsuite}//@var{test-target}/@var{option1}/@var{option2}/@dots{}
1964 make -j3 check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@}
1967 will run three concurrent ``make-gcc'' testsuites, eventually testing all
1968 ten combinations as described above. Note that this is currently only
1969 supported in the @file{gcc} subdirectory. (To see how this works, try
1970 typing @command{echo} before the example given here.)
1973 @section Additional testing for Java Class Libraries
1975 The Java runtime tests can be executed via @samp{make check}
1976 in the @file{@var{target}/libjava/testsuite} directory in
1979 The @uref{http://sources.redhat.com/mauve/,,Mauve Project} provides
1980 a suite of tests for the Java Class Libraries. This suite can be run
1981 as part of libgcj testing by placing the Mauve tree within the libjava
1982 testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by
1983 specifying the location of that tree when invoking @samp{make}, as in
1984 @samp{make MAUVEDIR=~/mauve check}.
1986 @uref{http://sources.redhat.com/mauve/jacks.html,,Jacks}
1987 is a free testsuite that tests Java compiler front ends. This suite
1988 can be run as part of libgcj testing by placing the Jacks tree within
1989 the libjava testsuite at @file{libjava/testsuite/libjava.jacks/jacks}.
1991 @section How to interpret test results
1993 The result of running the testsuite are various @file{*.sum} and @file{*.log}
1994 files in the testsuite subdirectories. The @file{*.log} files contain a
1995 detailed log of the compiler invocations and the corresponding
1996 results, the @file{*.sum} files summarize the results. These summaries
1997 contain status codes for all tests:
2001 PASS: the test passed as expected
2003 XPASS: the test unexpectedly passed
2005 FAIL: the test unexpectedly failed
2007 XFAIL: the test failed as expected
2009 UNSUPPORTED: the test is not supported on this platform
2011 ERROR: the testsuite detected an error
2013 WARNING: the testsuite detected a possible problem
2016 It is normal for some tests to report unexpected failures. At the
2017 current time the testing harness does not allow fine grained control
2018 over whether or not a test is expected to fail. This problem should
2019 be fixed in future releases.
2022 @section Submitting test results
2024 If you want to report the results to the GCC project, use the
2025 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
2028 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
2029 -m gcc-testresults@@gcc.gnu.org |sh
2032 This script uses the @command{Mail} program to send the results, so
2033 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
2034 prepended to the testsuite summary and should contain any special
2035 remarks you have on your results or your build environment. Please
2036 do not edit the testsuite result block or the subject line, as these
2037 messages may be automatically processed.
2044 @uref{./index.html,,Return to the GCC Installation page}
2048 @c ***Final install***********************************************************
2050 @comment node-name, next, previous, up
2051 @node Final install, , Testing, Installing GCC
2053 @ifset finalinstallhtml
2055 @chapter Installing GCC: Final installation
2058 Now that GCC has been built (and optionally tested), you can install it with
2060 cd @var{objdir}; make install
2063 We strongly recommend to install into a target directory where there is
2064 no previous version of GCC present.
2066 That step completes the installation of GCC; user level binaries can
2067 be found in @file{@var{prefix}/bin} where @var{prefix} is the value
2068 you specified with the @option{--prefix} to configure (or
2069 @file{/usr/local} by default). (If you specified @option{--bindir},
2070 that directory will be used instead; otherwise, if you specified
2071 @option{--exec-prefix}, @file{@var{exec-prefix}/bin} will be used.)
2072 Headers for the C++ and Java libraries are installed in
2073 @file{@var{prefix}/include}; libraries in @file{@var{libdir}}
2074 (normally @file{@var{prefix}/lib}); internal parts of the compiler in
2075 @file{@var{libdir}/gcc} and @file{@var{libexecdir}/gcc}; documentation
2076 in info format in @file{@var{infodir}} (normally
2077 @file{@var{prefix}/info}).
2079 When installing cross-compilers, GCC's executables
2080 are not only installed into @file{@var{bindir}}, that
2081 is, @file{@var{exec-prefix}/bin}, but additionally into
2082 @file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory
2083 exists. Typically, such @dfn{tooldirs} hold target-specific
2084 binutils, including assembler and linker.
2086 Installation into a temporary staging area or into a @command{chroot}
2087 jail can be achieved with the command
2090 make DESTDIR=@var{path-to-rootdir} install
2093 @noindent where @var{path-to-rootdir} is the absolute path of
2094 a directory relative to which all installation paths will be
2095 interpreted. Note that the directory specified by @code{DESTDIR}
2096 need not exist yet; it will be created if necessary.
2098 There is a subtle point with tooldirs and @code{DESTDIR}:
2099 If you relocate a cross-compiler installation with
2100 e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory
2101 @file{@var{rootdir}/@var{exec-prefix}/@var{target-alias}/bin} will
2102 be filled with duplicated GCC executables only if it already exists,
2103 it will not be created otherwise. This is regarded as a feature,
2104 not as a bug, because it gives slightly more control to the packagers
2105 using the @code{DESTDIR} feature.
2107 If you are bootstrapping a released version of GCC then please
2108 quickly review the build status page for your release, available from
2109 @uref{http://gcc.gnu.org/buildstat.html}.
2110 If your system is not listed for the version of GCC that you built,
2112 @email{gcc@@gcc.gnu.org} indicating
2113 that you successfully built and installed GCC@.
2114 Include the following information:
2118 Output from running @file{@var{srcdir}/config.guess}. Do not send
2119 that file itself, just the one-line output from running it.
2122 The output of @samp{gcc -v} for your newly installed @command{gcc}.
2123 This tells us which version of GCC you built and the options you passed to
2127 Whether you enabled all languages or a subset of them. If you used a
2128 full distribution then this information is part of the configure
2129 options in the output of @samp{gcc -v}, but if you downloaded the
2130 ``core'' compiler plus additional front ends then it isn't apparent
2131 which ones you built unless you tell us about it.
2134 If the build was for GNU/Linux, also include:
2137 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
2138 this information should be available from @file{/etc/issue}.
2141 The version of the Linux kernel, available from @samp{uname --version}
2145 The version of glibc you used; for RPM-based systems like Red Hat,
2146 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
2147 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
2149 For other systems, you can include similar information if you think it is
2153 Any other information that you think would be useful to people building
2154 GCC on the same configuration. The new entry in the build status list
2155 will include a link to the archived copy of your message.
2158 We'd also like to know if the
2160 @ref{Specific, host/target specific installation notes}
2163 @uref{specific.html,,host/target specific installation notes}
2165 didn't include your host/target information or if that information is
2166 incomplete or out of date. Send a note to
2167 @email{gcc@@gcc.gnu.org} detailing how the information should be changed.
2169 If you find a bug, please report it following the
2170 @uref{../bugs.html,,bug reporting guidelines}.
2172 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
2173 dvi}. You will need to have @command{texi2dvi} (version at least 4.4)
2174 and @TeX{} installed. This creates a number of @file{.dvi} files in
2175 subdirectories of @file{@var{objdir}}; these may be converted for
2176 printing with programs such as @command{dvips}. Alternately, by using
2177 @samp{make pdf} in place of @samp{make dvi}, you can create documentation
2178 in the form of @file{.pdf} files; this requires @command{texi2pdf}, which
2179 is included with Texinfo version 4.8 and later. You can also
2180 @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the
2181 Free Software Foundation}, though such manuals may not be for the most
2182 recent version of GCC@.
2184 If you would like to generate online HTML documentation, do @samp{cd
2185 @var{objdir}; make html} and HTML will be generated for the gcc manuals in
2186 @file{@var{objdir}/gcc/HTML}.
2193 @uref{./index.html,,Return to the GCC Installation page}
2197 @c ***Binaries****************************************************************
2199 @comment node-name, next, previous, up
2200 @node Binaries, Specific, Installing GCC, Top
2204 @chapter Installing GCC: Binaries
2207 @cindex Installing GCC: Binaries
2209 We are often asked about pre-compiled versions of GCC@. While we cannot
2210 provide these for all platforms, below you'll find links to binaries for
2211 various platforms where creating them by yourself is not easy due to various
2214 Please note that we did not create these binaries, nor do we
2215 support them. If you have any problems installing them, please
2216 contact their makers.
2223 @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX};
2226 @uref{http://aixpdslib.seas.ucla.edu,,UCLA Software Library for AIX}.
2230 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}.
2233 Renesas H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
2234 Development Tools for the Renesas H8/300[HS] Series}.
2240 @uref{http://hpux.cs.utah.edu/,,HP-UX Porting Center};
2243 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
2247 Motorola 68HC11/68HC12---@uref{http://www.gnu-m68hc11.org,,GNU
2248 Development Tools for the Motorola 68HC11/68HC12}.
2251 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
2252 OpenServer/Unixware}.
2255 Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware}.
2258 SGI---@uref{http://freeware.sgi.com/,,SGI Freeware}.
2264 The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project;
2266 The @uref{http://www.mingw.org/,,MinGW} project.
2270 @uref{ftp://ftp.thewrittenword.com/packages/by-name/,,The
2271 Written Word} offers binaries for
2274 Digital UNIX 4.0D and 5.1,
2276 HP-UX 10.20, 11.00, and 11.11, and
2277 Solaris/SPARC 2.5.1, 2.6, 7, 8, and 9.
2280 @uref{http://www.openpkg.org/,,OpenPKG} offers binaries for quite a
2281 number of platforms.
2284 The @uref{http://gcc.gnu.org/wiki/GFortranBinaries,,GFortran Wiki} has
2285 links to GNU Fortran binaries for several platforms.
2288 In addition to those specific offerings, you can get a binary
2289 distribution CD-ROM from the
2290 @uref{http://www.gnu.org/order/order.html,,Free Software Foundation}.
2291 It contains binaries for a number of platforms, and
2292 includes not only GCC, but other stuff as well. The current CD does
2293 not contain the latest version of GCC, but it should allow
2294 bootstrapping the compiler. An updated version of that disk is in the
2302 @uref{./index.html,,Return to the GCC Installation page}
2306 @c ***Specific****************************************************************
2308 @comment node-name, next, previous, up
2309 @node Specific, Old, Binaries, Top
2313 @chapter Host/target specific installation notes for GCC
2316 @cindex Specific installation notes
2317 @cindex Target specific installation
2318 @cindex Host specific installation
2319 @cindex Target specific installation notes
2321 Please read this document carefully @emph{before} installing the
2322 GNU Compiler Collection on your machine.
2324 Note that this list of install notes is @emph{not} a list of supported
2325 hosts or targets. Not all supported hosts and targets are listed
2326 here, only the ones that require host-specific or target-specific
2332 @uref{#alpha-x-x,,alpha*-*-*}
2334 @uref{#alpha-dec-osf,,alpha*-dec-osf*}
2336 @uref{#alphaev5-cray-unicosmk,,alphaev5-cray-unicosmk*}
2338 @uref{#arc-x-elf,,arc-*-elf}
2340 @uref{#arm-x-elf,,arm-*-elf}
2341 @uref{#arm-x-coff,,arm-*-coff}
2342 @uref{#arm-x-aout,,arm-*-aout}
2344 @uref{#xscale-x-x,,xscale-*-*}
2348 @uref{#bfin,,Blackfin}
2354 @uref{#x-x-freebsd,,*-*-freebsd*}
2356 @uref{#h8300-hms,,h8300-hms}
2358 @uref{#hppa-hp-hpux,,hppa*-hp-hpux*}
2360 @uref{#hppa-hp-hpux10,,hppa*-hp-hpux10}
2362 @uref{#hppa-hp-hpux11,,hppa*-hp-hpux11}
2364 @uref{#x-x-linux-gnu,,*-*-linux-gnu}
2366 @uref{#ix86-x-linuxaout,,i?86-*-linux*aout}
2368 @uref{#ix86-x-linux,,i?86-*-linux*}
2370 @uref{#ix86-x-sco32v5,,i?86-*-sco3.2v5*}
2372 @uref{#ix86-x-solaris210,,i?86-*-solaris2.10}
2374 @uref{#ix86-x-udk,,i?86-*-udk}
2376 @uref{#ia64-x-linux,,ia64-*-linux}
2378 @uref{#ia64-x-hpux,,ia64-*-hpux*}
2380 @uref{#x-ibm-aix,,*-ibm-aix*}
2382 @uref{#iq2000-x-elf,,iq2000-*-elf}
2384 @uref{#m32c-x-elf,,m32c-*-elf}
2386 @uref{#m32r-x-elf,,m32r-*-elf}
2388 @uref{#m6811-elf,,m6811-elf}
2390 @uref{#m6812-elf,,m6812-elf}
2392 @uref{#m68k-hp-hpux,,m68k-hp-hpux}
2394 @uref{#mips-x-x,,mips-*-*}
2396 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
2398 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
2400 @uref{#powerpc-x-x,,powerpc*-*-*, powerpc-*-sysv4}
2402 @uref{#powerpc-x-darwin,,powerpc-*-darwin*}
2404 @uref{#powerpc-x-elf,,powerpc-*-elf, powerpc-*-sysv4}
2406 @uref{#powerpc-x-linux-gnu,,powerpc*-*-linux-gnu*}
2408 @uref{#powerpc-x-netbsd,,powerpc-*-netbsd*}
2410 @uref{#powerpc-x-eabisim,,powerpc-*-eabisim}
2412 @uref{#powerpc-x-eabi,,powerpc-*-eabi}
2414 @uref{#powerpcle-x-elf,,powerpcle-*-elf, powerpcle-*-sysv4}
2416 @uref{#powerpcle-x-eabisim,,powerpcle-*-eabisim}
2418 @uref{#powerpcle-x-eabi,,powerpcle-*-eabi}
2420 @uref{#s390-x-linux,,s390-*-linux*}
2422 @uref{#s390x-x-linux,,s390x-*-linux*}
2424 @uref{#s390x-ibm-tpf,,s390x-ibm-tpf*}
2426 @uref{#x-x-solaris2,,*-*-solaris2*}
2428 @uref{#sparc-sun-solaris2,,sparc-sun-solaris2*}
2430 @uref{#sparc-sun-solaris27,,sparc-sun-solaris2.7}
2432 @uref{#sparc-x-linux,,sparc-*-linux*}
2434 @uref{#sparc64-x-solaris2,,sparc64-*-solaris2*}
2436 @uref{#sparcv9-x-solaris2,,sparcv9-*-solaris2*}
2438 @uref{#x-x-sysv,,*-*-sysv*}
2440 @uref{#vax-dec-ultrix,,vax-dec-ultrix}
2442 @uref{#x-x-vxworks,,*-*-vxworks*}
2444 @uref{#x86-64-x-x,,x86_64-*-*, amd64-*-*}
2446 @uref{#xtensa-x-elf,,xtensa-*-elf}
2448 @uref{#xtensa-x-linux,,xtensa-*-linux*}
2450 @uref{#windows,,Microsoft Windows}
2454 @uref{#older,,Older systems}
2459 @uref{#elf,,all ELF targets} (SVR4, Solaris 2, etc.)
2465 <!-- -------- host/target specific issues start here ---------------- -->
2468 @heading @anchor{alpha-x-x}alpha*-*-*
2470 This section contains general configuration information for all
2471 alpha-based platforms using ELF (in particular, ignore this section for
2472 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
2473 section, please read all other sections that match your target.
2475 We require binutils 2.11.2 or newer.
2476 Previous binutils releases had a number of problems with DWARF 2
2477 debugging information, not the least of which is incorrect linking of
2483 @heading @anchor{alpha-dec-osf}alpha*-dec-osf*
2484 Systems using processors that implement the DEC Alpha architecture and
2485 are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
2486 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
2488 As of GCC 3.2, versions before @code{alpha*-dec-osf4} are no longer
2489 supported. (These are the versions which identify themselves as DEC
2492 In Digital Unix V4.0, virtual memory exhausted bootstrap failures
2493 may be fixed by configuring with @option{--with-gc=simple},
2494 reconfiguring Kernel Virtual Memory and Swap parameters
2495 per the @command{/usr/sbin/sys_check} Tuning Suggestions,
2496 or applying the patch in
2497 @uref{http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html}.
2499 In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
2500 currently (2001-06-13) work with @command{mips-tfile}. As a workaround,
2501 we need to use the old assembler, invoked via the barely documented
2502 @option{-oldas} option. To bootstrap GCC, you either need to use the
2506 % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
2509 or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
2512 % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
2515 As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld}
2516 are supported on Tru64 UNIX, so you must not configure GCC with
2517 @option{--with-gnu-as} or @option{--with-gnu-ld}.
2519 GCC writes a @samp{.verstamp} directive to the assembler output file
2520 unless it is built as a cross-compiler. It gets the version to use from
2521 the system header file @file{/usr/include/stamp.h}. If you install a
2522 new version of DEC Unix, you should rebuild GCC to pick up the new version
2525 Note that since the Alpha is a 64-bit architecture, cross-compilers from
2526 32-bit machines will not generate code as efficient as that generated
2527 when the compiler is running on a 64-bit machine because many
2528 optimizations that depend on being able to represent a word on the
2529 target in an integral value on the host cannot be performed. Building
2530 cross-compilers on the Alpha for 32-bit machines has only been tested in
2531 a few cases and may not work properly.
2533 @samp{make compare} may fail on old versions of DEC Unix unless you add
2534 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
2535 assembler input file is stored in the object file, and that makes
2536 comparison fail if it differs between the @code{stage1} and
2537 @code{stage2} compilations. The option @option{-save-temps} forces a
2538 fixed name to be used for the assembler input file, instead of a
2539 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
2540 unless the comparisons fail without that option. If you add
2541 @option{-save-temps}, you will have to manually delete the @samp{.i} and
2542 @samp{.s} files after each series of compilations.
2544 GCC now supports both the native (ECOFF) debugging format used by DBX
2545 and GDB and an encapsulated STABS format for use only with GDB@. See the
2546 discussion of the @option{--with-stabs} option of @file{configure} above
2547 for more information on these formats and how to select them.
2549 There is a bug in DEC's assembler that produces incorrect line numbers
2550 for ECOFF format when the @samp{.align} directive is used. To work
2551 around this problem, GCC will not emit such alignment directives
2552 while writing ECOFF format debugging information even if optimization is
2553 being performed. Unfortunately, this has the very undesirable
2554 side-effect that code addresses when @option{-O} is specified are
2555 different depending on whether or not @option{-g} is also specified.
2557 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
2558 DBX@. DEC is now aware of this problem with the assembler and hopes to
2559 provide a fix shortly.
2564 @heading @anchor{alphaev5-cray-unicosmk}alphaev5-cray-unicosmk*
2565 Cray T3E systems running Unicos/Mk.
2567 This port is incomplete and has many known bugs. We hope to improve the
2568 support for this target soon. Currently, only the C front end is supported,
2569 and it is not possible to build parallel applications. Cray modules are not
2570 supported; in particular, Craylibs are assumed to be in
2571 @file{/opt/ctl/craylibs/craylibs}.
2573 On this platform, you need to tell GCC where to find the assembler and
2574 the linker. The simplest way to do so is by providing @option{--with-as}
2575 and @option{--with-ld} to @file{configure}, e.g.@:
2578 configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld \
2579 --enable-languages=c
2582 The comparison test at the end of the bootstrapping process fails on Unicos/Mk
2583 because the assembler inserts timestamps into object files. You should
2584 be able to work around this by doing @samp{make all} after getting this
2590 @heading @anchor{arc-x-elf}arc-*-elf
2591 Argonaut ARC processor.
2592 This configuration is intended for embedded systems.
2597 @heading @anchor{arm-x-elf}arm-*-elf
2598 @heading @anchor{xscale-x-x}xscale-*-*
2599 ARM-family processors. Subtargets that use the ELF object format
2600 require GNU binutils 2.13 or newer. Such subtargets include:
2601 @code{arm-*-freebsd}, @code{arm-*-netbsdelf}, @code{arm-*-*linux},
2602 @code{arm-*-rtems} and @code{arm-*-kaos}.
2607 @heading @anchor{arm-x-coff}arm-*-coff
2608 ARM-family processors. Note that there are two different varieties
2609 of PE format subtarget supported: @code{arm-wince-pe} and
2610 @code{arm-pe} as well as a standard COFF target @code{arm-*-coff}.
2615 @heading @anchor{arm-x-aout}arm-*-aout
2616 ARM-family processors. These targets support the AOUT file format:
2617 @code{arm-*-aout}, @code{arm-*-netbsd}.
2622 @heading @anchor{avr}avr
2624 ATMEL AVR-family micro controllers. These are used in embedded
2625 applications. There are no standard Unix configurations.
2627 @xref{AVR Options,, AVR Options, gcc, Using the GNU Compiler
2631 See ``AVR Options'' in the main manual
2633 for the list of supported MCU types.
2635 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
2637 Further installation notes and other useful information about AVR tools
2638 can also be obtained from:
2642 @uref{http://www.nongnu.org/avr/,,http://www.nongnu.org/avr/}
2644 @uref{http://home.overta.ru/users/denisc/,,http://home.overta.ru/users/denisc/}
2646 @uref{http://www.amelek.gda.pl/avr/,,http://www.amelek.gda.pl/avr/}
2649 We @emph{strongly} recommend using binutils 2.13 or newer.
2651 The following error:
2653 Error: register required
2656 indicates that you should upgrade to a newer version of the binutils.
2661 @heading @anchor{bfin}Blackfin
2663 The Blackfin processor, an Analog Devices DSP.
2665 @xref{Blackfin Options,, Blackfin Options, gcc, Using the GNU Compiler
2669 See ``Blackfin Options'' in the main manual
2672 More information, and a version of binutils with support for this processor,
2673 is available at @uref{http://blackfin.uclinux.org}
2678 @heading @anchor{c4x}c4x
2680 Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal
2681 Processors. These are used in embedded applications. There are no
2682 standard Unix configurations.
2684 @xref{TMS320C3x/C4x Options,, TMS320C3x/C4x Options, gcc, Using the
2685 GNU Compiler Collection (GCC)},
2688 See ``TMS320C3x/C4x Options'' in the main manual
2690 for the list of supported MCU types.
2692 GCC can be configured as a cross compiler for both the C3x and C4x
2693 architectures on the same system. Use @samp{configure --target=c4x
2694 --enable-languages="c,c++"} to configure.
2697 Further installation notes and other useful information about C4x tools
2698 can also be obtained from:
2702 @uref{http://www.elec.canterbury.ac.nz/c4x/,,http://www.elec.canterbury.ac.nz/c4x/}
2708 @heading @anchor{cris}CRIS
2710 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
2711 series. These are used in embedded applications.
2714 @xref{CRIS Options,, CRIS Options, gcc, Using the GNU Compiler
2718 See ``CRIS Options'' in the main manual
2720 for a list of CRIS-specific options.
2722 There are a few different CRIS targets:
2724 @item cris-axis-aout
2725 Old target. Includes a multilib for the @samp{elinux} a.out-based
2726 target. No multilibs for newer architecture variants.
2728 Mainly for monolithic embedded systems. Includes a multilib for the
2729 @samp{v10} core used in @samp{ETRAX 100 LX}.
2730 @item cris-axis-linux-gnu
2731 A GNU/Linux port for the CRIS architecture, currently targeting
2732 @samp{ETRAX 100 LX} by default.
2735 For @code{cris-axis-aout} and @code{cris-axis-elf} you need binutils 2.11
2736 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
2738 Pre-packaged tools can be obtained from
2739 @uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More
2740 information about this platform is available at
2741 @uref{http://developer.axis.com/}.
2746 @heading @anchor{crx}CRX
2748 The CRX CompactRISC architecture is a low-power 32-bit architecture with
2749 fast context switching and architectural extensibility features.
2752 @xref{CRX Options,, CRX Options, gcc, Using and Porting the GNU Compiler
2757 See ``CRX Options'' in the main manual for a list of CRX-specific options.
2760 Use @samp{configure --target=crx-elf --enable-languages=c,c++} to configure
2761 GCC@ for building a CRX cross-compiler. The option @samp{--target=crx-elf}
2762 is also used to build the @samp{newlib} C library for CRX.
2764 It is also possible to build libstdc++-v3 for the CRX architecture. This
2765 needs to be done in a separate step with the following configure settings:
2766 @samp{gcc/libstdc++-v3/configure --host=crx-elf --with-newlib
2767 --enable-sjlj-exceptions --enable-cxx-flags='-fexceptions -frtti'}
2772 @heading @anchor{dos}DOS
2774 Please have a look at the @uref{binaries.html,,binaries page}.
2776 You cannot install GCC by itself on MSDOS; it will not compile under
2777 any MSDOS compiler except itself. You need to get the complete
2778 compilation package DJGPP, which includes binaries as well as sources,
2779 and includes all the necessary compilation tools and libraries.
2784 @heading @anchor{x-x-freebsd}*-*-freebsd*
2786 The version of binutils installed in @file{/usr/bin} probably works with
2787 this release of GCC@. However, on FreeBSD 4, bootstrapping against the
2788 latest FSF binutils is known to improve overall testsuite results; and,
2789 on FreeBSD/alpha, using binutils 2.14 or later is required to build libjava.
2791 Support for FreeBSD 1 was discontinued in GCC 3.2.
2793 Support for FreeBSD 2 will be discontinued after GCC 3.4. The
2794 following was true for GCC 3.1 but the current status is unknown.
2795 For FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
2796 configuration support and files as shipped with GCC 2.95 are still in
2797 place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
2798 it is unknown which version of binutils was used (it is assumed that it
2799 was the system copy in @file{/usr/bin}) and C++ EH failures were noted.
2801 For FreeBSD using the ELF file format: DWARF 2 debugging is now the
2802 default for all CPU architectures. It had been the default on
2803 FreeBSD/alpha since its inception. You may use @option{-gstabs} instead
2804 of @option{-g}, if you really want the old debugging format. There are
2805 no known issues with mixing object files and libraries with different
2806 debugging formats. Otherwise, this release of GCC should now match more
2807 of the configuration used in the stock FreeBSD configuration of GCC@. In
2808 particular, @option{--enable-threads} is now configured by default.
2809 However, as a general user, do not attempt to replace the system
2810 compiler with this release. Known to bootstrap and check with good
2811 results on FreeBSD 4.9-STABLE and 5-CURRENT@. In the past, known to
2812 bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2,
2813 4.3, 4.4, 4.5, 4.8-STABLE@.
2815 In principle, @option{--enable-threads} is now compatible with
2816 @option{--enable-libgcj} on FreeBSD@. However, it has only been built
2817 and tested on @samp{i386-*-freebsd[45]} and @samp{alpha-*-freebsd[45]}.
2819 library may be incorrectly built (symbols are missing at link time).
2820 There is a rare timing-based startup hang (probably involves an
2821 assumption about the thread library). Multi-threaded boehm-gc (required for
2822 libjava) exposes severe threaded signal-handling bugs on FreeBSD before
2823 4.5-RELEASE@. Other CPU architectures
2824 supported by FreeBSD will require additional configuration tuning in, at
2825 the very least, both boehm-gc and libffi.
2827 Shared @file{libgcc_s.so} is now built and installed by default.
2832 @heading @anchor{h8300-hms}h8300-hms
2833 Renesas H8/300 series of processors.
2835 Please have a look at the @uref{binaries.html,,binaries page}.
2837 The calling convention and structure layout has changed in release 2.6.
2838 All code must be recompiled. The calling convention now passes the
2839 first three arguments in function calls in registers. Structures are no
2840 longer a multiple of 2 bytes.
2845 @heading @anchor{hppa-hp-hpux}hppa*-hp-hpux*
2846 Support for HP-UX version 9 and older was discontinued in GCC 3.4.
2848 We require using gas/binutils on all hppa platforms;
2849 you may encounter a variety of problems if you try to use the HP assembler.
2851 Specifically, @option{-g} does not work on HP-UX (since that system
2852 uses a peculiar debugging format which GCC does not know about), unless
2853 you use GAS and GDB@. It may be helpful to configure GCC with the
2854 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
2855 @option{--with-as=@dots{}} options to ensure that GCC can find GAS@.
2857 If you wish to use the pa-risc 2.0 architecture support with a 32-bit
2858 runtime, you must use gas/binutils 2.11 or newer.
2860 There are two default scheduling models for instructions. These are
2861 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
2862 architecture specified for the target machine when configuring.
2863 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
2864 the target is a @samp{hppa1*} machine.
2866 The PROCESSOR_8000 model is not well suited to older processors. Thus,
2867 it is important to completely specify the machine architecture when
2868 configuring if you want a model other than PROCESSOR_8000. The macro
2869 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
2870 default scheduling model is desired.
2872 As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
2873 through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
2874 This namespace change might cause problems when bootstrapping with
2875 an earlier version of GCC or the HP compiler as essentially the same
2876 namespace is required for an entire build. This problem can be avoided
2877 in a number of ways. With HP cc, @env{UNIX_STD} can be set to @samp{95}
2878 or @samp{98}. Another way is to add an appropriate set of predefines
2879 to @env{CC}. The description for the @option{munix=} option contains
2880 a list of the predefines used with each standard.
2882 As of GCC 4.1, @env{DWARF2} exception handling is available on HP-UX.
2883 It is now the default. This exposed a bug in the handling of data
2884 relocations in the GAS assembler. The handling of 64-bit data relocations
2885 was seriously broken, affecting debugging and exception support on all
2886 @samp{hppa64-*-*} targets. Under some circumstances, 32-bit data relocations
2887 could also be handled incorrectly. This problem is fixed in GAS version
2890 GCC versions prior to 4.1 incorrectly passed and returned complex
2891 values. They are now passed in the same manner as aggregates.
2893 More specific information to @samp{hppa*-hp-hpux*} targets follows.
2898 @heading @anchor{hppa-hp-hpux10}hppa*-hp-hpux10
2900 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
2901 @code{PHCO_19798} from HP@. HP has two sites which provide patches free of
2907 <a href="http://us.itrc.hp.com/service/home/home.do">US, Canada, Asia-Pacific, and
2911 @uref{http://us.itrc.hp.com/service/home/home.do,,} US, Canada, Asia-Pacific,
2915 @uref{http://europe.itrc.hp.com/service/home/home.do,,} Europe.
2918 The HP assembler on these systems has some problems. Most notably the
2919 assembler inserts timestamps into each object file it creates, causing
2920 the 3-stage comparison test to fail during a bootstrap.
2921 You should be able to continue by saying @samp{make all-host all-target}
2922 after getting the failure from @samp{make}.
2924 GCC 4.0 requires CVS binutils as of April 28, 2004 or later. Earlier
2925 versions require binutils 2.8 or later.
2927 The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are
2928 used for one-only code and data. This resolves many of the previous
2929 problems in using C++ on this target. However, the ABI is not compatible
2930 with the one implemented under HP-UX 11 using secondary definitions.
2935 @heading @anchor{hppa-hp-hpux11}hppa*-hp-hpux11
2937 GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
2938 be used to compile GCC 3.0 and up.
2940 Refer to @uref{binaries.html,,binaries} for information about obtaining
2941 precompiled GCC binaries for HP-UX@. Precompiled binaries must be obtained
2942 to build the Ada language as it can't be bootstrapped using C@. Ada is
2943 only available for the 32-bit PA-RISC runtime. The libffi and libjava
2944 haven't been ported to HP-UX and don't build.
2946 Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The
2947 bundled compiler supports only traditional C; you will need either HP's
2948 unbundled compiler, or a binary distribution of GCC@.
2950 It is possible to build GCC 3.3 starting with the bundled HP compiler,
2951 but the process requires several steps. GCC 3.3 can then be used to
2952 build later versions. The fastjar program contains ISO C code and
2953 can't be built with the HP bundled compiler. This problem can be
2954 avoided by not building the Java language. For example, use the
2955 @option{--enable-languages="c,c++,f77,objc"} option in your configure
2958 There are several possible approaches to building the distribution.
2959 Binutils can be built first using the HP tools. Then, the GCC
2960 distribution can be built. The second approach is to build GCC
2961 first using the HP tools, then build binutils, then rebuild GCC@.
2962 There have been problems with various binary distributions, so it
2963 is best not to start from a binary distribution.
2965 On 64-bit capable systems, there are two distinct targets. Different
2966 installation prefixes must be used if both are to be installed on
2967 the same system. The @samp{hppa[1-2]*-hp-hpux11*} target generates code
2968 for the 32-bit PA-RISC runtime architecture and uses the HP linker.
2969 The @samp{hppa64-hp-hpux11*} target generates 64-bit code for the
2970 PA-RISC 2.0 architecture. The HP and GNU linkers are both supported
2973 The script config.guess now selects the target type based on the compiler
2974 detected during configuration. You must define @env{PATH} or @env{CC} so
2975 that configure finds an appropriate compiler for the initial bootstrap.
2976 When @env{CC} is used, the definition should contain the options that are
2977 needed whenever @env{CC} is used.
2979 Specifically, options that determine the runtime architecture must be
2980 in @env{CC} to correctly select the target for the build. It is also
2981 convenient to place many other compiler options in @env{CC}. For example,
2982 @env{CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"}
2983 can be used to bootstrap the GCC 3.3 branch with the HP compiler in
2984 64-bit K&R/bundled mode. The @option{+DA2.0W} option will result in
2985 the automatic selection of the @samp{hppa64-hp-hpux11*} target. The
2986 macro definition table of cpp needs to be increased for a successful
2987 build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to
2988 be defined when building with the bundled compiler, or when using the
2989 @option{-Ac} option. These defines aren't necessary with @option{-Ae}.
2991 It is best to explicitly configure the @samp{hppa64-hp-hpux11*} target
2992 with the @option{--with-ld=@dots{}} option. This overrides the standard
2993 search for ld. The two linkers supported on this target require different
2994 commands. The default linker is determined during configuration. As a
2995 result, it's not possible to switch linkers in the middle of a GCC build.
2996 This has been been reported to sometimes occur in unified builds of
2999 GCC 3.0 through 3.2 require binutils 2.11 or above. GCC 3.3 through
3000 GCC 4.0 require binutils 2.14 or later.
3002 Although the HP assembler can be used for an initial build, it shouldn't
3003 be used with any languages other than C and perhaps Fortran due to its
3004 many limitations. For example, it does not support weak symbols or alias
3005 definitions. As a result, explicit template instantiations are required
3006 when using C++. This makes it difficult if not impossible to build many
3007 C++ applications. You can't generate debugging information when using
3008 the HP assembler. Finally, bootstrapping fails in the final
3009 comparison of object modules due to the time stamps that it inserts into
3010 the modules. The bootstrap can be continued from this point with
3011 @samp{make all-host all-target}.
3013 A recent linker patch must be installed for the correct operation of
3014 GCC 3.3 and later. @code{PHSS_26559} and @code{PHSS_24304} are the
3015 oldest linker patches that are known to work. They are for HP-UX
3016 11.00 and 11.11, respectively. @code{PHSS_24303}, the companion to
3017 @code{PHSS_24304}, might be usable but it hasn't been tested. These
3018 patches have been superseded. Consult the HP patch database to obtain
3019 the currently recommended linker patch for your system.
3021 The patches are necessary for the support of weak symbols on the
3022 32-bit port, and for the running of initializers and finalizers. Weak
3023 symbols are implemented using SOM secondary definition symbols. Prior
3024 to HP-UX 11, there are bugs in the linker support for secondary symbols.
3025 The patches correct a problem of linker core dumps creating shared
3026 libraries containing secondary symbols, as well as various other
3027 linking issues involving secondary symbols.
3029 GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
3030 run initializers and finalizers on the 64-bit port. The 32-bit port
3031 uses the linker @option{+init} and @option{+fini} options for the same
3032 purpose. The patches correct various problems with the +init/+fini
3033 options, including program core dumps. Binutils 2.14 corrects a
3034 problem on the 64-bit port resulting from HP's non-standard use of
3035 the .init and .fini sections for array initializers and finalizers.
3037 There are a number of issues to consider in selecting which linker to
3038 use with the 64-bit port. The GNU 64-bit linker can only create dynamic
3039 binaries. The @option{-static} option causes linking with archive
3040 libraries but doesn't produce a truly static binary. Dynamic binaries
3041 still require final binding by the dynamic loader to resolve a set of
3042 dynamic-loader-defined symbols. The default behavior of the HP linker
3043 is the same as the GNU linker. However, it can generate true 64-bit
3044 static binaries using the @option{+compat} option.
3046 The HP 64-bit linker doesn't support linkonce semantics. As a
3047 result, C++ programs have many more sections than they should.
3049 The GNU 64-bit linker has some issues with shared library support
3050 and exceptions. As a result, we only support libgcc in archive
3051 format. For similar reasons, dwarf2 unwind and exception support
3052 are disabled. The GNU linker also has problems creating binaries
3053 with @option{-static}. It doesn't provide stubs for internal
3054 calls to global functions in shared libraries, so these calls
3055 can't be overloaded.
3057 Thread support is not implemented in GCC 3.0 through 3.2, so the
3058 @option{--enable-threads} configure option does not work. In 3.3
3059 and later, POSIX threads are supported. The optional DCE thread
3060 library is not supported.
3062 This port still is undergoing significant development.
3067 @heading @anchor{x-x-linux-gnu}*-*-linux-gnu
3069 Versions of libstdc++-v3 starting with 3.2.1 require bugfixes present
3070 in glibc 2.2.5 and later. More information is available in the
3071 libstdc++-v3 documentation.
3076 @heading @anchor{ix86-x-linuxaout}i?86-*-linux*aout
3077 Use this configuration to generate @file{a.out} binaries on Linux-based
3078 GNU systems. This configuration is being superseded.
3083 @heading @anchor{ix86-x-linux}i?86-*-linux*
3085 As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
3086 See @uref{http://gcc.gnu.org/PR10877,,bug 10877} for more information.
3088 If you receive Signal 11 errors when building on GNU/Linux, then it is
3089 possible you have a hardware problem. Further information on this can be
3090 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
3095 @heading @anchor{ix86-x-sco32v5}i?86-*-sco3.2v5*
3096 Use this for the SCO OpenServer Release 5 family of operating systems.
3098 Unlike earlier versions of GCC, the ability to generate COFF with this
3099 target is no longer provided.
3101 Earlier versions of GCC emitted DWARF 1 when generating ELF to allow
3102 the system debugger to be used. That support was too burdensome to
3103 maintain. GCC now emits only DWARF 2 for this target. This means you
3104 may use either the UDK debugger or GDB to debug programs built by this
3107 GCC is now only supported on releases 5.0.4 and later, and requires that
3108 you install Support Level Supplement OSS646B or later, and Support Level
3109 Supplement OSS631C or later. If you are using release 5.0.7 of
3110 OpenServer, you must have at least the first maintenance pack installed
3111 (this includes the relevant portions of OSS646). OSS646, also known as
3112 the ``Execution Environment Update'', provides updated link editors and
3113 assemblers, as well as updated standard C and math libraries. The C
3114 startup modules are also updated to support the System V gABI draft, and
3115 GCC relies on that behavior. OSS631 provides a collection of commonly
3116 used open source libraries, some of which GCC depends on (such as GNU
3117 gettext and zlib). SCO OpenServer Release 5.0.7 has all of this built
3118 in by default, but OSS631C and later also apply to that release. Please
3120 @uref{ftp://ftp.sco.com/pub/openserver5,,ftp://ftp.sco.com/pub/openserver5}
3121 for the latest versions of these (and other potentially useful)
3124 Although there is support for using the native assembler, it is
3125 recommended that you configure GCC to use the GNU assembler. You do
3126 this by using the flags
3127 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You should
3128 use a modern version of GNU binutils. Version 2.13.2.1 was used for all
3129 testing. In general, only the @option{--with-gnu-as} option is tested.
3130 A modern bintuils (as well as a plethora of other development related
3131 GNU utilities) can be found in Support Level Supplement OSS658A, the
3132 ``GNU Development Tools'' package. See the SCO web and ftp sites for details.
3133 That package also contains the currently ``officially supported'' version of
3134 GCC, version 2.95.3. It is useful for bootstrapping this version.
3139 @heading @anchor{ix86-x-solaris210}i?86-*-solaris2.10
3140 Use this for Solaris 10 or later on x86 and x86-64 systems. This
3141 configuration is supported by GCC 4.0 and later versions only.
3143 It is recommended that you configure GCC to use the GNU assembler in
3144 @file{/usr/sfw/bin/gas} but the Sun linker, using the options
3145 @option{--with-gnu-as --with-as=/usr/sfw/bin/gas --without-gnu-ld
3146 --with-ld=/usr/ccs/bin/ld}.
3151 @heading @anchor{ix86-x-udk}i?86-*-udk
3153 This target emulates the SCO Universal Development Kit and requires that
3154 package be installed. (If it is installed, you will have a
3155 @file{/udk/usr/ccs/bin/cc} file present.) It's very much like the
3156 @samp{i?86-*-unixware7*} target
3157 but is meant to be used when hosting on a system where UDK isn't the
3158 default compiler such as OpenServer 5 or Unixware 2. This target will
3159 generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
3160 with the same warnings and caveats as the SCO UDK@.
3162 This target is a little tricky to build because we have to distinguish
3163 it from the native tools (so it gets headers, startups, and libraries
3164 from the right place) while making the tools not think we're actually
3165 building a cross compiler. The easiest way to do this is with a configure
3169 CC=/udk/usr/ccs/bin/cc @var{/your/path/to}/gcc/configure \
3170 --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-
3173 @emph{You should substitute @samp{i686} in the above command with the appropriate
3174 processor for your host.}
3176 After the usual @samp{make} and
3177 @samp{make install}, you can then access the UDK-targeted GCC
3178 tools by adding @command{udk-} before the commonly known name. For
3179 example, to invoke the C compiler, you would use @command{udk-gcc}.
3180 They will coexist peacefully with any native-target GCC tools you may
3187 @heading @anchor{ia64-x-linux}ia64-*-linux
3188 IA-64 processor (also known as IPF, or Itanium Processor Family)
3191 If you are using the installed system libunwind library with
3192 @option{--with-system-libunwind}, then you must use libunwind 0.98 or
3195 None of the following versions of GCC has an ABI that is compatible
3196 with any of the other versions in this list, with the exception that
3197 Red Hat 2.96 and Trillian 000171 are compatible with each other:
3198 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
3199 This primarily affects C++ programs and programs that create shared libraries.
3200 GCC 3.1 or later is recommended for compiling linux, the kernel.
3201 As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
3202 more major ABI changes are expected.
3207 @heading @anchor{ia64-x-hpux}ia64-*-hpux*
3208 Building GCC on this target requires the GNU Assembler. The bundled HP
3209 assembler will not work. To prevent GCC from using the wrong assembler,
3210 the option @option{--with-gnu-as} may be necessary.
3212 The GCC libunwind library has not been ported to HPUX@. This means that for
3213 GCC versions 3.2.3 and earlier, @option{--enable-libunwind-exceptions}
3214 is required to build GCC@. For GCC 3.3 and later, this is the default.
3215 For gcc 3.4.3 and later, @option{--enable-libunwind-exceptions} is
3216 removed and the system libunwind library will always be used.
3220 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
3222 @heading @anchor{x-ibm-aix}*-ibm-aix*
3223 Support for AIX version 3 and older was discontinued in GCC 3.4.
3225 ``out of memory'' bootstrap failures may indicate a problem with
3226 process resource limits (ulimit). Hard limits are configured in the
3227 @file{/etc/security/limits} system configuration file.
3229 To speed up the configuration phases of bootstrapping and installing GCC,
3230 one may use GNU Bash instead of AIX @command{/bin/sh}, e.g.,
3233 % CONFIG_SHELL=/opt/freeware/bin/bash
3234 % export CONFIG_SHELL
3237 and then proceed as described in @uref{build.html,,the build
3238 instructions}, where we strongly recommend specifying an absolute path
3239 to invoke @var{srcdir}/configure.
3241 Because GCC on AIX is built as a 32-bit executable by default,
3242 (although it can generate 64-bit programs) the GMP and MPFR libraries
3243 required by gfortran must be 32-bit libraries. Building GMP and MPFR
3244 as static archive libraries works better than shared libraries.
3246 Errors involving @code{alloca} when building GCC generally are due
3247 to an incorrect definition of @code{CC} in the Makefile or mixing files
3248 compiled with the native C compiler and GCC@. During the stage1 phase of
3249 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
3250 (not @command{xlc}). Once @command{configure} has been informed of
3251 @command{xlc}, one needs to use @samp{make distclean} to remove the
3252 configure cache files and ensure that @env{CC} environment variable
3253 does not provide a definition that will confuse @command{configure}.
3254 If this error occurs during stage2 or later, then the problem most likely
3255 is the version of Make (see above).
3257 The native @command{as} and @command{ld} are recommended for bootstrapping
3258 on AIX 4 and required for bootstrapping on AIX 5L@. The GNU Assembler
3259 reports that it supports WEAK symbols on AIX 4, which causes GCC to try to
3260 utilize weak symbol functionality although it is not supported. The GNU
3261 Assembler and Linker do not support AIX 5L sufficiently to bootstrap GCC@.
3262 The native AIX tools do interoperate with GCC@.
3264 Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
3265 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
3266 fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
3267 referenced as APAR IY53606 (AIX 5.2) or a APAR IY54774 (AIX 5.1)
3269 @samp{libstdc++} in GCC 3.4 increments the major version number of the
3270 shared object and GCC installation places the @file{libstdc++.a}
3271 shared library in a common location which will overwrite the and GCC
3272 3.3 version of the shared library. Applications either need to be
3273 re-linked against the new shared library or the GCC 3.1 and GCC 3.3
3274 versions of the @samp{libstdc++} shared object needs to be available
3275 to the AIX runtime loader. The GCC 3.1 @samp{libstdc++.so.4}, if
3276 present, and GCC 3.3 @samp{libstdc++.so.5} shared objects can be
3277 installed for runtime dynamic loading using the following steps to set
3278 the @samp{F_LOADONLY} flag in the shared object for @emph{each}
3279 multilib @file{libstdc++.a} installed:
3281 Extract the shared objects from the currently installed
3282 @file{libstdc++.a} archive:
3284 % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
3287 Enable the @samp{F_LOADONLY} flag so that the shared object will be
3288 available for runtime dynamic loading, but not linking:
3290 % strip -e libstdc++.so.4 libstdc++.so.5
3293 Archive the runtime-only shared object in the GCC 3.4
3294 @file{libstdc++.a} archive:
3296 % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
3299 Linking executables and shared libraries may produce warnings of
3300 duplicate symbols. The assembly files generated by GCC for AIX always
3301 have included multiple symbol definitions for certain global variable
3302 and function declarations in the original program. The warnings should
3303 not prevent the linker from producing a correct library or runnable
3306 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
3307 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
3308 to parse archive libraries did not handle the new format correctly.
3309 These routines are used by GCC and result in error messages during
3310 linking such as ``not a COFF file''. The version of the routines shipped
3311 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
3312 option of the archive command may be used to create archives of 32-bit
3313 objects using the original ``small format''. A correct version of the
3314 routines is shipped with AIX 4.3.2 and above.
3316 Some versions of the AIX binder (linker) can fail with a relocation
3317 overflow severe error when the @option{-bbigtoc} option is used to link
3318 GCC-produced object files into an executable that overflows the TOC@. A fix
3319 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
3320 available from IBM Customer Support and from its
3321 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3322 website as PTF U455193.
3324 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
3325 with a segmentation fault when invoked by any version of GCC@. A fix for
3326 APAR IX87327 is available from IBM Customer Support and from its
3327 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3328 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
3330 The initial assembler shipped with AIX 4.3.0 generates incorrect object
3331 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
3332 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
3333 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3334 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
3336 AIX provides National Language Support (NLS)@. Compilers and assemblers
3337 use NLS to support locale-specific representations of various data
3338 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
3339 separating decimal fractions). There have been problems reported where
3340 GCC does not produce the same floating-point formats that the assembler
3341 expects. If one encounters this problem, set the @env{LANG}
3342 environment variable to @samp{C} or @samp{En_US}.
3344 By default, GCC for AIX 4.1 and above produces code that can be used on
3345 both Power or PowerPC processors.
3347 A default can be specified with the @option{-mcpu=@var{cpu_type}}
3348 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
3353 @heading @anchor{iq2000-x-elf}iq2000-*-elf
3354 Vitesse IQ2000 processors. These are used in embedded
3355 applications. There are no standard Unix configurations.
3360 @heading @anchor{m32c-x-elf}m32c-*-elf
3361 Renesas M32C processor.
3362 This configuration is intended for embedded systems.
3367 @heading @anchor{m32r-x-elf}m32r-*-elf
3368 Renesas M32R processor.
3369 This configuration is intended for embedded systems.
3374 @heading @anchor{m6811-elf}m6811-elf
3375 Motorola 68HC11 family micro controllers. These are used in embedded
3376 applications. There are no standard Unix configurations.
3381 @heading @anchor{m6812-elf}m6812-elf
3382 Motorola 68HC12 family micro controllers. These are used in embedded
3383 applications. There are no standard Unix configurations.
3388 @heading @anchor{m68k-hp-hpux}m68k-hp-hpux
3389 HP 9000 series 300 or 400 running HP-UX@. HP-UX version 8.0 has a bug in
3390 the assembler that prevents compilation of GCC@. This
3391 bug manifests itself during the first stage of compilation, while
3392 building @file{libgcc2.a}:
3396 cc1: warning: `-g' option not supported on this version of GCC
3397 cc1: warning: `-g1' option not supported on this version of GCC
3398 ./xgcc: Internal compiler error: program as got fatal signal 11
3401 A patched version of the assembler is available as the file
3402 @uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you
3403 have HP software support, the patch can also be obtained directly from
3404 HP, as described in the following note:
3407 This is the patched assembler, to patch SR#1653-010439, where the
3408 assembler aborts on floating point constants.
3410 The bug is not really in the assembler, but in the shared library
3411 version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is
3412 SR#4701-078451. Anyway, the attached assembler uses the archive
3413 library version of ``cvtnum(3c)'' and thus does not exhibit the bug.
3416 This patch is also known as PHCO_4484.
3418 In addition gdb does not understand that native HP-UX format, so
3419 you must use gas if you wish to use gdb.
3421 On HP-UX version 8.05, but not on 8.07 or more recent versions, the
3422 @command{fixproto} shell script triggers a bug in the system shell. If you
3423 encounter this problem, upgrade your operating system or use BASH (the
3424 GNU shell) to run @command{fixproto}. This bug will cause the fixproto
3425 program to report an error of the form:
3428 ./fixproto: sh internal 1K buffer overflow
3431 To fix this, you can also change the first line of the fixproto script
3441 @heading @anchor{mips-x-x}mips-*-*
3442 If on a MIPS system you get an error message saying ``does not have gp
3443 sections for all it's [sic] sectons [sic]'', don't worry about it. This
3444 happens whenever you use GAS with the MIPS linker, but there is not
3445 really anything wrong, and it is okay to use the output file. You can
3446 stop such warnings by installing the GNU linker.
3448 It would be nice to extend GAS to produce the gp tables, but they are
3449 optional, and there should not be a warning about their absence.
3451 The libstdc++ atomic locking routines for MIPS targets requires MIPS II
3452 and later. A patch went in just after the GCC 3.3 release to
3453 make @samp{mips*-*-*} use the generic implementation instead. You can also
3454 configure for @samp{mipsel-elf} as a workaround. The
3455 @samp{mips*-*-linux*} target continues to use the MIPS II routines. More
3456 work on this is expected in future releases.
3458 MIPS systems check for division by zero (unless
3459 @option{-mno-check-zero-division} is passed to the compiler) by
3460 generating either a conditional trap or a break instruction. Using
3461 trap results in smaller code, but is only supported on MIPS II and
3462 later. Also, some versions of the Linux kernel have a bug that
3463 prevents trap from generating the proper signal (@code{SIGFPE}). To enable
3464 the use of break, use the @option{--with-divide=breaks}
3465 @command{configure} option when configuring GCC@. The default is to
3466 use traps on systems that support them.
3468 Cross-compilers for the MIPS as target using the MIPS assembler
3469 currently do not work, because the auxiliary programs
3470 @file{mips-tdump.c} and @file{mips-tfile.c} can't be compiled on
3471 anything but a MIPS. It does work to cross compile for a MIPS
3472 if you use the GNU assembler and linker.
3474 The linker from GNU binutils versions prior to 2.17 has a bug which
3475 causes the runtime linker stubs in @file{libgcj.so} to be incorrectly
3476 generated. If you want to use libgcj, either use binutils 2.17 or
3477 later to build it or export @samp{LD_BIND_NOW=1} in your runtime environment.
3482 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
3484 In order to compile GCC on an SGI running IRIX 5, the @samp{compiler_dev.hdr}
3485 subsystem must be installed from the IDO CD-ROM supplied by SGI@.
3486 It is also available for download from
3487 @uref{ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist}.
3489 If you use the MIPS C compiler to bootstrap, it may be necessary
3490 to increase its table size for switch statements with the
3491 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
3492 optimization option, you also need to use @option{-Olimit 3000}.
3494 To enable debugging under IRIX 5, you must use GNU binutils 2.15 or
3495 later, and use the @option{--with-gnu-ld} @command{configure} option
3496 when configuring GCC@. You need to use GNU @command{ar} and @command{nm},
3497 also distributed with GNU binutils.
3499 Some users have reported that @command{/bin/sh} will hang during bootstrap.
3500 This problem can be avoided by running the commands:
3503 % CONFIG_SHELL=/bin/ksh
3504 % export CONFIG_SHELL
3507 before starting the build.
3512 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
3514 If you are using SGI's MIPSpro @command{cc} as your bootstrap compiler, you must
3515 ensure that the N32 ABI is in use. To test this, compile a simple C
3516 file with @command{cc} and then run @command{file} on the
3517 resulting object file. The output should look like:
3520 test.o: ELF N32 MSB @dots{}
3526 test.o: ELF 32-bit MSB @dots{}
3532 test.o: ELF 64-bit MSB @dots{}
3535 then your version of @command{cc} uses the O32 or N64 ABI by default. You
3536 should set the environment variable @env{CC} to @samp{cc -n32}
3537 before configuring GCC@.
3539 If you want the resulting @command{gcc} to run on old 32-bit systems
3540 with the MIPS R4400 CPU, you need to ensure that only code for the @samp{mips3}
3541 instruction set architecture (ISA) is generated. While GCC 3.x does
3542 this correctly, both GCC 2.95 and SGI's MIPSpro @command{cc} may change
3543 the ISA depending on the machine where GCC is built. Using one of them
3544 as the bootstrap compiler may result in @samp{mips4} code, which won't run at
3545 all on @samp{mips3}-only systems. For the test program above, you should see:
3548 test.o: ELF N32 MSB mips-3 @dots{}
3554 test.o: ELF N32 MSB mips-4 @dots{}
3557 instead, you should set the environment variable @env{CC} to @samp{cc
3558 -n32 -mips3} or @samp{gcc -mips3} respectively before configuring GCC@.
3560 MIPSpro C 7.4 may cause bootstrap failures, due to a bug when inlining
3561 @code{memcmp}. Either add @code{-U__INLINE_INTRINSICS} to the @env{CC}
3562 environment variable as a workaround or upgrade to MIPSpro C 7.4.1m.
3564 GCC on IRIX 6 is usually built to support the N32, O32 and N64 ABIs. If
3565 you build GCC on a system that doesn't have the N64 libraries installed
3566 or cannot run 64-bit binaries,
3567 you need to configure with @option{--disable-multilib} so GCC doesn't
3568 try to use them. This will disable building the O32 libraries, too.
3569 Look for @file{/usr/lib64/libc.so.1} to see if you
3570 have the 64-bit libraries installed.
3572 To enable debugging for the O32 ABI, you must use GNU @command{as} from
3573 GNU binutils 2.15 or later. You may also use GNU @command{ld}, but
3574 this is not required and currently causes some problems with Ada.
3576 The @option{--enable-threads} option doesn't currently work, a patch is
3577 in preparation for a future release. The @option{--enable-libgcj}
3578 option is disabled by default: IRIX 6 uses a very low default limit
3579 (20480) for the command line length. Although @command{libtool} contains a
3580 workaround for this problem, at least the N64 @samp{libgcj} is known not
3581 to build despite this, running into an internal error of the native
3582 @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
3583 its maximum of 262144 bytes. If you have root access, you can use the
3584 @command{systune} command to do this.
3586 @code{wchar_t} support in @samp{libstdc++} is not available for old
3587 IRIX 6.5.x releases, @math{x < 19}. The problem cannot be autodetected
3588 and in order to build GCC for such targets you need to configure with
3589 @option{--disable-wchar_t}.
3591 See @uref{http://freeware.sgi.com/} for more
3592 information about using GCC on IRIX platforms.
3597 @heading @anchor{powerpc-x-x}powerpc-*-*
3599 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
3600 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
3605 @heading @anchor{powerpc-x-darwin}powerpc-*-darwin*
3606 PowerPC running Darwin (Mac OS X kernel).
3608 Pre-installed versions of Mac OS X may not include any developer tools,
3609 meaning that you will not be able to build GCC from source. Tool
3610 binaries are available at
3611 @uref{http://developer.apple.com/darwin/projects/compiler/} (free
3612 registration required).
3614 This version of GCC requires at least cctools-590.7.
3616 The version of GCC shipped by Apple typically includes a number of
3617 extensions not available in a standard GCC release. These extensions
3618 are generally for backwards compatibility and best avoided.
3623 @heading @anchor{powerpc-x-elf}powerpc-*-elf, powerpc-*-sysv4
3624 PowerPC system in big endian mode, running System V.4.
3629 @heading @anchor{powerpc-x-linux-gnu}powerpc*-*-linux-gnu*
3632 @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.15}
3633 or newer for a working GCC@.
3638 @heading @anchor{powerpc-x-netbsd}powerpc-*-netbsd*
3639 PowerPC system in big endian mode running NetBSD@. To build the
3640 documentation you will need Texinfo version 4.4 (NetBSD 1.5.1 included
3641 Texinfo version 3.12).
3646 @heading @anchor{powerpc-x-eabisim}powerpc-*-eabisim
3647 Embedded PowerPC system in big endian mode for use in running under the
3653 @heading @anchor{powerpc-x-eabi}powerpc-*-eabi
3654 Embedded PowerPC system in big endian mode.
3659 @heading @anchor{powerpcle-x-elf}powerpcle-*-elf, powerpcle-*-sysv4
3660 PowerPC system in little endian mode, running System V.4.
3665 @heading @anchor{powerpcle-x-eabisim}powerpcle-*-eabisim
3666 Embedded PowerPC system in little endian mode for use in running under
3672 @heading @anchor{powerpcle-x-eabi}powerpcle-*-eabi
3673 Embedded PowerPC system in little endian mode.
3678 @heading @anchor{s390-x-linux}s390-*-linux*
3679 S/390 system running GNU/Linux for S/390@.
3684 @heading @anchor{s390x-x-linux}s390x-*-linux*
3685 zSeries system (64-bit) running GNU/Linux for zSeries@.
3690 @heading @anchor{s390x-ibm-tpf}s390x-ibm-tpf*
3691 zSeries system (64-bit) running TPF@. This platform is
3692 supported as cross-compilation target only.
3697 @c Please use Solaris 2 to refer to all release of Solaris, starting
3698 @c with 2.0 until 2.6, 7, 8, etc. Solaris 1 was a marketing name for
3699 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
3700 @c alone is too unspecific and must be avoided.
3701 @heading @anchor{x-x-solaris2}*-*-solaris2*
3703 Sun does not ship a C compiler with Solaris 2. To bootstrap and install
3704 GCC you first have to install a pre-built compiler, see the
3705 @uref{binaries.html,,binaries page} for details.
3707 The Solaris 2 @command{/bin/sh} will often fail to configure
3708 @file{libstdc++-v3}, @file{boehm-gc} or @file{libjava}. We therefore
3709 recommend using the following initial sequence of commands
3712 % CONFIG_SHELL=/bin/ksh
3713 % export CONFIG_SHELL
3716 and proceed as described in @uref{configure.html,,the configure instructions}.
3717 In addition we strongly recommend specifying an absolute path to invoke
3718 @var{srcdir}/configure.
3720 Solaris 2 comes with a number of optional OS packages. Some of these
3721 are needed to use GCC fully, namely @code{SUNWarc},
3722 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
3723 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
3724 optional packages when installing Solaris 2, you will need to verify that
3725 the packages that GCC needs are installed.
3727 To check whether an optional package is installed, use
3728 the @command{pkginfo} command. To add an optional package, use the
3729 @command{pkgadd} command. For further details, see the Solaris 2
3732 Trying to use the linker and other tools in
3733 @file{/usr/ucb} to install GCC has been observed to cause trouble.
3734 For example, the linker may hang indefinitely. The fix is to remove
3735 @file{/usr/ucb} from your @env{PATH}.
3737 The build process works more smoothly with the legacy Sun tools so, if you
3738 have @file{/usr/xpg4/bin} in your @env{PATH}, we recommend that you place
3739 @file{/usr/bin} before @file{/usr/xpg4/bin} for the duration of the build.
3741 All releases of GNU binutils prior to 2.11.2 have known bugs on this
3742 platform. We recommend the use of GNU binutils 2.11.2 or later, or the
3743 vendor tools (Sun @command{as}, Sun @command{ld}). Note that your mileage
3744 may vary if you use a combination of the GNU tools and the Sun tools: while
3745 the combination GNU @command{as} + Sun @command{ld} should reasonably work,
3746 the reverse combination Sun @command{as} + GNU @command{ld} is known to
3747 cause memory corruption at runtime in some cases for C++ programs.
3749 The stock GNU binutils 2.15 release is broken on this platform because of a
3750 single bug. It has been fixed on the 2.15 branch in the CVS repository.
3751 You can obtain a working version by checking out the binutils-2_15-branch
3752 from the CVS repository or applying the patch
3753 @uref{http://sources.redhat.com/ml/binutils-cvs/2004-09/msg00036.html} to the
3756 We recommend using GNU binutils 2.16 or later in conjunction with GCC 4.x,
3757 or the vendor tools (Sun @command{as}, Sun @command{ld}). However, for
3758 Solaris 10 and above, an additional patch is required in order for the GNU
3759 linker to be able to cope with a new flavor of shared libraries. You
3760 can obtain a working version by checking out the binutils-2_16-branch from
3761 the CVS repository or applying the patch
3762 @uref{http://sourceware.org/ml/binutils-cvs/2005-07/msg00122.html} to the
3765 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3766 newer: @command{g++} will complain that types are missing. These headers assume
3767 that omitting the type means @code{int}; this assumption worked for C89 but
3768 is wrong for C++, and is now wrong for C99 also.
3770 @command{g++} accepts such (invalid) constructs with the option
3771 @option{-fpermissive}; it
3772 will assume that any missing type is @code{int} (as defined by C89).
3774 There are patches for Solaris 2.6 (105633-56 or newer for SPARC,
3775 106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC,
3776 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
3777 108653-22 for Intel) that fix this bug.
3779 Sun bug 4927647 sometimes causes random spurious testsuite failures
3780 related to missing diagnostic output. This bug doesn't affect GCC
3781 itself, rather it is a kernel bug triggered by the @command{expect}
3782 program which is used only by the GCC testsuite driver. When the bug
3783 causes the @command{expect} program to miss anticipated output, extra
3784 testsuite failures appear.
3786 There are patches for Solaris 8 (117350-12 or newer for SPARC,
3787 117351-12 or newer for Intel) and Solaris 9 (117171-11 or newer for
3788 SPARC, 117172-11 or newer for Intel) that address this problem.
3793 @heading @anchor{sparc-sun-solaris2}sparc-sun-solaris2*
3795 When GCC is configured to use binutils 2.11.2 or later the binaries
3796 produced are smaller than the ones produced using Sun's native tools;
3797 this difference is quite significant for binaries containing debugging
3800 Sun @command{as} 4.x is broken in that it cannot cope with long symbol names.
3801 A typical error message might look similar to the following:
3804 /usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error:
3805 can't compute value of an expression involving an external symbol.
3808 This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris
3809 2.6 and has been fixed in later (5.x) versions of the assembler,
3810 starting with Solaris 7.
3812 Starting with Solaris 7, the operating system is capable of executing
3813 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
3814 this; the @option{-m64} option enables 64-bit code generation.
3815 However, if all you want is code tuned for the UltraSPARC CPU, you
3816 should try the @option{-mtune=ultrasparc} option instead, which produces
3817 code that, unlike full 64-bit code, can still run on non-UltraSPARC
3820 When configuring on a Solaris 7 or later system that is running a kernel
3821 that supports only 32-bit binaries, one must configure with
3822 @option{--disable-multilib}, since we will not be able to build the
3823 64-bit target libraries.
3825 GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of
3826 the GNU compiler (especially GCC 3.0.x versions), which lead to the
3827 miscompilation of the stage1 compiler and the subsequent failure of the
3828 bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary
3829 stage, i.e.@: to bootstrap that compiler with the base compiler and then
3830 use it to bootstrap the final compiler.
3832 GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7)
3833 and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap
3834 failure in form of a miscompilation of the stage1 compiler by the Sun
3835 compiler. This is Sun bug 4974440. This is fixed with patch 112760-07.
3837 GCC 3.4 changed the default debugging format from STABS to DWARF-2 for
3838 32-bit code on Solaris 7 and later. If you use the Sun assembler, this
3839 change apparently runs afoul of Sun bug 4910101 (which is referenced as
3840 a x86-only problem by Sun, probably because they do not use DWARF-2).
3841 A symptom of the problem is that you cannot compile C++ programs like
3842 @command{groff} 1.19.1 without getting messages similar to the following:
3845 ld: warning: relocation error: R_SPARC_UA32: @dots{}
3846 external symbolic relocation against non-allocatable section
3847 .debug_info cannot be processed at runtime: relocation ignored.
3850 To work around this problem, compile with @option{-gstabs+} instead of
3853 When configuring the GNU Multiple Precision Library (GMP) version 4.1.x
3854 on a Solaris 7 or later system, the canonical target triplet must be
3855 specified as the @command{build} parameter on the configure line:
3858 ./configure --build=sparc-sun-solaris2.7 --prefix=xxx --enable-mpfr
3864 @heading @anchor{sparc-sun-solaris27}sparc-sun-solaris2.7
3866 Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
3867 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
3868 and later, including all EGCS releases. Sun formerly recommended
3869 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
3870 recommend it only for people who use Sun's compilers.
3872 Here are some workarounds to this problem:
3875 Do not install Sun patch 107058-01 until after Sun releases a
3876 complete patch for bug 4210064. This is the simplest course to take,
3877 unless you must also use Sun's C compiler. Unfortunately 107058-01
3878 is preinstalled on some new Solaris 7-based hosts, so you may have to
3882 Copy the original, unpatched Solaris 7
3883 @command{/usr/ccs/bin/as} into
3884 @command{/usr/local/libexec/gcc/sparc-sun-solaris2.7/3.4/as},
3885 adjusting the latter name to fit your local conventions and software
3889 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
3890 both 107058-01 and 106950-03 installed has reported the bug with GCC
3891 and Sun's dynamic linker. This last course of action is riskiest,
3892 for two reasons. First, you must install 106950 on all hosts that
3893 run code generated by GCC; it doesn't suffice to install it only on
3894 the hosts that run GCC itself. Second, Sun says that 106950-03 is
3895 only a partial fix for bug 4210064, but Sun doesn't know whether the
3896 partial fix is adequate for GCC@. Revision -08 or later should fix
3897 the bug. The current (as of 2004-05-23) revision is -24, and is included in
3898 the Solaris 7 Recommended Patch Cluster.
3901 GCC 3.3 triggers a bug in version 5.0 Alpha 03/27/98 of the Sun assembler,
3902 which causes a bootstrap failure when linking the 64-bit shared version of
3903 libgcc. A typical error message is:
3906 ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o:
3907 symbol <unknown>: offset 0xffffffff7ec133e7 is non-aligned.
3910 This bug has been fixed in the final 5.0 version of the assembler.
3912 A similar problem was reported for version Sun WorkShop 6 99/08/18 of the
3913 Sun assembler, which causes a bootstrap failure with GCC 4.0.0:
3916 ld: fatal: relocation error: R_SPARC_DISP32:
3917 file .libs/libstdc++.lax/libsupc++convenience.a/vterminate.o:
3918 symbol <unknown>: offset 0xfccd33ad is non-aligned
3921 This bug has been fixed in more recent revisions of the assembler.
3926 @heading @anchor{sparc-x-linux}sparc-*-linux*
3928 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
3929 or newer on this platform. All earlier binutils and glibc
3930 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
3936 @heading @anchor{sparc64-x-solaris2}sparc64-*-solaris2*
3938 The following compiler flags must be specified in the configure
3939 step in order to bootstrap this target with the Sun compiler:
3942 % CC="cc -xildoff -xarch=v9" @var{srcdir}/configure [@var{options}] [@var{target}]
3945 @option{-xildoff} turns off the incremental linker, and @option{-xarch=v9}
3946 specifies the SPARC-V9 architecture to the Sun linker and assembler.
3951 @heading @anchor{sparcv9-x-solaris2}sparcv9-*-solaris2*
3953 This is a synonym for sparc64-*-solaris2*.
3958 @heading @anchor{x-x-sysv}*-*-sysv*
3959 On System V release 3, you may get this error message
3963 ld fatal: failed to write symbol name @var{something}
3964 in strings table for file @var{whatever}
3967 This probably indicates that the disk is full or your ulimit won't allow
3968 the file to be as large as it needs to be.
3970 This problem can also result because the kernel parameter @code{MAXUMEM}
3971 is too small. If so, you must regenerate the kernel and make the value
3972 much larger. The default value is reported to be 1024; a value of 32768
3973 is said to work. Smaller values may also work.
3975 On System V, if you get an error like this,
3978 /usr/local/lib/bison.simple: In function `yyparse':
3979 /usr/local/lib/bison.simple:625: virtual memory exhausted
3983 that too indicates a problem with disk space, ulimit, or @code{MAXUMEM}.
3985 On a System V release 4 system, make sure @file{/usr/bin} precedes
3986 @file{/usr/ucb} in @code{PATH}. The @command{cc} command in
3987 @file{/usr/ucb} uses libraries which have bugs.
3992 @heading @anchor{vax-dec-ultrix}vax-dec-ultrix
3993 Don't try compiling with VAX C (@command{vcc}). It produces incorrect code
3994 in some cases (for example, when @code{alloca} is used).
3999 @heading @anchor{x-x-vxworks}*-*-vxworks*
4000 Support for VxWorks is in flux. At present GCC supports @emph{only} the
4001 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC@.
4002 We welcome patches for other architectures supported by VxWorks 5.5.
4003 Support for VxWorks AE would also be welcome; we believe this is merely
4004 a matter of writing an appropriate ``configlette'' (see below). We are
4005 not interested in supporting older, a.out or COFF-based, versions of
4008 VxWorks comes with an older version of GCC installed in
4009 @file{@var{$WIND_BASE}/host}; we recommend you do not overwrite it.
4010 Choose an installation @var{prefix} entirely outside @var{$WIND_BASE}.
4011 Before running @command{configure}, create the directories @file{@var{prefix}}
4012 and @file{@var{prefix}/bin}. Link or copy the appropriate assembler,
4013 linker, etc.@: into @file{@var{prefix}/bin}, and set your @var{PATH} to
4014 include that directory while running both @command{configure} and
4017 You must give @command{configure} the
4018 @option{--with-headers=@var{$WIND_BASE}/target/h} switch so that it can
4019 find the VxWorks system headers. Since VxWorks is a cross compilation
4020 target only, you must also specify @option{--target=@var{target}}.
4021 @command{configure} will attempt to create the directory
4022 @file{@var{prefix}/@var{target}/sys-include} and copy files into it;
4023 make sure the user running @command{configure} has sufficient privilege
4026 GCC's exception handling runtime requires a special ``configlette''
4027 module, @file{contrib/gthr_supp_vxw_5x.c}. Follow the instructions in
4028 that file to add the module to your kernel build. (Future versions of
4029 VxWorks will incorporate this module.)
4034 @heading @anchor{x86-64-x-x}x86_64-*-*, amd64-*-*
4036 GCC supports the x86-64 architecture implemented by the AMD64 processor
4037 (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD@.
4038 On GNU/Linux the default is a bi-arch compiler which is able to generate
4039 both 64-bit x86-64 and 32-bit x86 code (via the @option{-m32} switch).
4044 @heading @anchor{xtensa-x-elf}xtensa-*-elf
4046 This target is intended for embedded Xtensa systems using the
4047 @samp{newlib} C library. It uses ELF but does not support shared
4048 objects. Designed-defined instructions specified via the
4049 Tensilica Instruction Extension (TIE) language are only supported
4050 through inline assembly.
4052 The Xtensa configuration information must be specified prior to
4053 building GCC@. The @file{include/xtensa-config.h} header
4054 file contains the configuration information. If you created your
4055 own Xtensa configuration with the Xtensa Processor Generator, the
4056 downloaded files include a customized copy of this header file,
4057 which you can use to replace the default header file.
4062 @heading @anchor{xtensa-x-linux}xtensa-*-linux*
4064 This target is for Xtensa systems running GNU/Linux. It supports ELF
4065 shared objects and the GNU C library (glibc). It also generates
4066 position-independent code (PIC) regardless of whether the
4067 @option{-fpic} or @option{-fPIC} options are used. In other
4068 respects, this target is the same as the
4069 @uref{#xtensa-*-elf,,@samp{xtensa-*-elf}} target.
4074 @heading @anchor{windows}Microsoft Windows (32-bit)
4076 Ports of GCC are included with the
4077 @uref{http://www.cygwin.com/,,Cygwin environment}.
4079 GCC will build under Cygwin without modification; it does not build
4080 with Microsoft's C++ compiler and there are no plans to make it do so.
4085 @heading @anchor{os2}OS/2
4087 GCC does not currently support OS/2. However, Andrew Zabolotny has been
4088 working on a generic OS/2 port with pgcc. The current code can be found
4089 at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
4094 @heading @anchor{older}Older systems
4096 GCC contains support files for many older (1980s and early
4097 1990s) Unix variants. For the most part, support for these systems
4098 has not been deliberately removed, but it has not been maintained for
4099 several years and may suffer from bitrot.
4101 Starting with GCC 3.1, each release has a list of ``obsoleted'' systems.
4102 Support for these systems is still present in that release, but
4103 @command{configure} will fail unless the @option{--enable-obsolete}
4104 option is given. Unless a maintainer steps forward, support for these
4105 systems will be removed from the next release of GCC@.
4107 Support for old systems as hosts for GCC can cause problems if the
4108 workarounds for compiler, library and operating system bugs affect the
4109 cleanliness or maintainability of the rest of GCC@. In some cases, to
4110 bring GCC up on such a system, if still possible with current GCC, may
4111 require first installing an old version of GCC which did work on that
4112 system, and using it to compile a more recent GCC, to avoid bugs in the
4113 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
4114 @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror
4115 sites}. Header bugs may generally be avoided using
4116 @command{fixincludes}, but bugs or deficiencies in libraries and the
4117 operating system may still cause problems.
4119 Support for older systems as targets for cross-compilation is less
4120 problematic than support for them as hosts for GCC; if an enthusiast
4121 wishes to make such a target work again (including resurrecting any of
4122 the targets that never worked with GCC 2, starting from the last
4123 version before they were removed), patches
4124 @uref{../contribute.html,,following the usual requirements} would be
4125 likely to be accepted, since they should not affect the support for more
4128 For some systems, old versions of GNU binutils may also be useful,
4129 and are available from @file{pub/binutils/old-releases} on
4130 @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}.
4132 Some of the information on specific systems above relates to
4133 such older systems, but much of the information
4134 about GCC on such systems (which may no longer be applicable to
4135 current GCC) is to be found in the GCC texinfo manual.
4140 @heading @anchor{elf}all ELF targets (SVR4, Solaris 2, etc.)
4142 C++ support is significantly better on ELF targets if you use the
4143 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
4144 inlines, vtables and template instantiations will be discarded
4153 @uref{./index.html,,Return to the GCC Installation page}
4157 @c ***Old documentation******************************************************
4159 @include install-old.texi
4165 @uref{./index.html,,Return to the GCC Installation page}
4169 @c ***GFDL********************************************************************
4177 @uref{./index.html,,Return to the GCC Installation page}
4181 @c ***************************************************************************
4182 @c Part 6 The End of the Document
4184 @comment node-name, next, previous, up
4185 @node Concept Index, , GNU Free Documentation License, Top
4189 @unnumbered Concept Index