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} configure option. See also
298 @option{--with-gmp-lib} and @option{--with-gmp-include}.
300 @item MPFR Library version 2.2.1 (or later)
302 Necessary to build GCC. It can be downloaded from
303 @uref{http://www.mpfr.org/}. The version of MPFR that is bundled with
304 GMP 4.1.x contains numerous bugs. Although GCC may appear to function
305 with the buggy versions of MPFR, there are a few bugs that will not be
306 fixed when using this version. It is strongly recommended to upgrade
307 to the recommended version of MPFR.
309 The @option{--with-mpfr} configure option should be used if your MPFR
310 Library is not installed in your default library search path. See
311 also @option{--with-mpfr-lib} and @option{--with-mpfr-include}.
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, M68k,
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 and x86-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.
1298 @item --with-gmp=@var{pathname}
1299 @itemx --with-gmp-include=@var{pathname}
1300 @itemx --with-gmp-lib=@var{pathname}
1301 @itemx --with-mpfr=@var{pathname}
1302 @itemx --with-mpfr-include=@var{pathname}
1303 @itemx --with-mpfr-lib=@var{pathname}
1304 If you do not have GMP (the GNU Multiple Precision library) and the
1305 MPFR Libraries installed in a standard location and you want to build
1306 GCC, you can explicitly specify the directory where they are installed
1307 (@samp{--with-gmp=@var{gmpinstalldir}},
1308 @samp{--with-mpfr=@var{mpfrinstalldir}}). The
1309 @option{--with-gmp=@var{gmpinstalldir}} option is shorthand for
1310 @option{--with-gmp-lib=@var{gmpinstalldir}/lib} and
1311 @option{--with-gmp-include=@var{gmpinstalldir}/include}. Likewise the
1312 @option{--with-mpfr=@var{mpfrinstalldir}} option is shorthand for
1313 @option{--with-mpfr-lib=@var{mpfrinstalldir}/lib} and
1314 @option{--with-mpfr-include=@var{mpfrinstalldir}/include}. If these
1315 shorthand assumptions are not correct, you can use the explicit
1316 include and lib options directly.
1320 @subheading Cross-Compiler-Specific Options
1321 The following options only apply to building cross compilers.
1323 @item --with-sysroot
1324 @itemx --with-sysroot=@var{dir}
1325 Tells GCC to consider @var{dir} as the root of a tree that contains a
1326 (subset of) the root filesystem of the target operating system.
1327 Target system headers, libraries and run-time object files will be
1328 searched in there. The specified directory is not copied into the
1329 install tree, unlike the options @option{--with-headers} and
1330 @option{--with-libs} that this option obsoletes. The default value,
1331 in case @option{--with-sysroot} is not given an argument, is
1332 @option{$@{gcc_tooldir@}/sys-root}. If the specified directory is a
1333 subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to
1334 the GCC binaries if the installation tree is moved.
1336 @item --with-build-sysroot
1337 @itemx --with-build-sysroot=@var{dir}
1338 Tells GCC to consider @var{dir} as the system root (see
1339 @option{--with-sysroot}) while building target libraries, instead of
1340 the directory specified with @option{--with-sysroot}. This option is
1341 only useful when you are already using @option{--with-sysroot}. You
1342 can use @option{--with-build-sysroot} when you are configuring with
1343 @option{--prefix} set to a directory that is different from the one in
1344 which you are installing GCC and your target libraries.
1346 This option affects the system root for the compiler used to build
1347 target libraries (which runs on the build system); it does not affect
1348 the compiler which is used to build GCC itself.
1350 @item --with-headers
1351 @itemx --with-headers=@var{dir}
1352 Deprecated in favor of @option{--with-sysroot}.
1353 Specifies that target headers are available when building a cross compiler.
1354 The @var{dir} argument specifies a directory which has the target include
1355 files. These include files will be copied into the @file{gcc} install
1356 directory. @emph{This option with the @var{dir} argument is required} when
1357 building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include}
1358 doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does
1359 pre-exist, the @var{dir} argument may be omitted. @command{fixincludes}
1360 will be run on these files to make them compatible with GCC@.
1362 @item --without-headers
1363 Tells GCC not use any target headers from a libc when building a cross
1364 compiler. When crossing to GNU/Linux, you need the headers so GCC
1365 can build the exception handling for libgcc.
1368 @itemx --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
1369 Deprecated in favor of @option{--with-sysroot}.
1370 Specifies a list of directories which contain the target runtime
1371 libraries. These libraries will be copied into the @file{gcc} install
1372 directory. If the directory list is omitted, this option has no
1376 Specifies that @samp{newlib} is
1377 being used as the target C library. This causes @code{__eprintf} to be
1378 omitted from @file{libgcc.a} on the assumption that it will be provided by
1381 @item --with-build-time-tools=@var{dir}
1382 Specifies where to find the set of target tools (assembler, linker, etc.)
1383 that will be used while building GCC itself. This option can be useful
1384 if the directory layouts are different between the system you are building
1385 GCC on, and the system where you will deploy it.
1387 For example, on a @option{ia64-hp-hpux} system, you may have the GNU
1388 assembler and linker in @file{/usr/bin}, and the native tools in a
1389 different path, and build a toolchain that expects to find the
1390 native tools in @file{/usr/bin}.
1392 When you use this option, you should ensure that @var{dir} includes
1393 @command{ar}, @command{as}, @command{ld}, @command{nm},
1394 @command{ranlib} and @command{strip} if necessary, and possibly
1395 @command{objdump}. Otherwise, GCC may use an inconsistent set of
1399 @subheading Java-Specific Options
1401 The following option applies to the build of the Java front end.
1404 @item --disable-libgcj
1405 Specify that the run-time libraries
1406 used by GCJ should not be built. This is useful in case you intend
1407 to use GCJ with some other run-time, or you're going to install it
1408 separately, or it just happens not to build on your particular
1409 machine. In general, if the Java front end is enabled, the GCJ
1410 libraries will be enabled too, unless they're known to not work on
1411 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
1412 may need to port it; in this case, before modifying the top-level
1413 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
1414 you may use @option{--enable-libgcj} to override the default.
1418 The following options apply to building @samp{libgcj}.
1420 @subsubheading General Options
1423 @item --disable-getenv-properties
1424 Don't set system properties from @env{GCJ_PROPERTIES}.
1426 @item --enable-hash-synchronization
1427 Use a global hash table for monitor locks. Ordinarily,
1428 @samp{libgcj}'s @samp{configure} script automatically makes
1429 the correct choice for this option for your platform. Only use
1430 this if you know you need the library to be configured differently.
1432 @item --enable-interpreter
1433 Enable the Java interpreter. The interpreter is automatically
1434 enabled by default on all platforms that support it. This option
1435 is really only useful if you want to disable the interpreter
1436 (using @option{--disable-interpreter}).
1438 @item --disable-java-net
1439 Disable java.net. This disables the native part of java.net only,
1440 using non-functional stubs for native method implementations.
1442 @item --disable-jvmpi
1443 Disable JVMPI support.
1446 Enable runtime eCos target support.
1448 @item --without-libffi
1449 Don't use @samp{libffi}. This will disable the interpreter and JNI
1450 support as well, as these require @samp{libffi} to work.
1452 @item --enable-libgcj-debug
1453 Enable runtime debugging code.
1455 @item --enable-libgcj-multifile
1456 If specified, causes all @file{.java} source files to be
1457 compiled into @file{.class} files in one invocation of
1458 @samp{gcj}. This can speed up build time, but is more
1459 resource-intensive. If this option is unspecified or
1460 disabled, @samp{gcj} is invoked once for each @file{.java}
1461 file to compile into a @file{.class} file.
1463 @item --with-libiconv-prefix=DIR
1464 Search for libiconv in @file{DIR/include} and @file{DIR/lib}.
1466 @item --enable-sjlj-exceptions
1467 Force use of the @code{setjmp}/@code{longjmp}-based scheme for exceptions.
1468 @samp{configure} ordinarily picks the correct value based on the platform.
1469 Only use this option if you are sure you need a different setting.
1471 @item --with-system-zlib
1472 Use installed @samp{zlib} rather than that included with GCC@.
1474 @item --with-win32-nlsapi=ansi, unicows or unicode
1475 Indicates how MinGW @samp{libgcj} translates between UNICODE
1476 characters and the Win32 API@.
1479 Use the single-byte @code{char} and the Win32 A functions natively,
1480 translating to and from UNICODE when using these functions. If
1481 unspecified, this is the default.
1484 Use the @code{WCHAR} and Win32 W functions natively. Adds
1485 @code{-lunicows} to @file{libgcj.spec} to link with @samp{libunicows}.
1486 @file{unicows.dll} needs to be deployed on Microsoft Windows 9X machines
1487 running built executables. @file{libunicows.a}, an open-source
1488 import library around Microsoft's @code{unicows.dll}, is obtained from
1489 @uref{http://libunicows.sourceforge.net/}, which also gives details
1490 on getting @file{unicows.dll} from Microsoft.
1493 Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not}
1494 add @code{-lunicows} to @file{libgcj.spec}. The built executables will
1495 only run on Microsoft Windows NT and above.
1499 @subsubheading AWT-Specific Options
1503 Use the X Window System.
1505 @item --enable-java-awt=PEER(S)
1506 Specifies the AWT peer library or libraries to build alongside
1507 @samp{libgcj}. If this option is unspecified or disabled, AWT
1508 will be non-functional. Current valid values are @option{gtk} and
1509 @option{xlib}. Multiple libraries should be separated by a
1510 comma (i.e.@: @option{--enable-java-awt=gtk,xlib}).
1512 @item --enable-gtk-cairo
1513 Build the cairo Graphics2D implementation on GTK@.
1515 @item --enable-java-gc=TYPE
1516 Choose garbage collector. Defaults to @option{boehm} if unspecified.
1518 @item --disable-gtktest
1519 Do not try to compile and run a test GTK+ program.
1521 @item --disable-glibtest
1522 Do not try to compile and run a test GLIB program.
1524 @item --with-libart-prefix=PFX
1525 Prefix where libart is installed (optional).
1527 @item --with-libart-exec-prefix=PFX
1528 Exec prefix where libart is installed (optional).
1530 @item --disable-libarttest
1531 Do not try to compile and run a test libart program.
1540 @uref{./index.html,,Return to the GCC Installation page}
1544 @c ***Building****************************************************************
1546 @comment node-name, next, previous, up
1547 @node Building, Testing, Configuration, Installing GCC
1553 @cindex Installing GCC: Building
1555 Now that GCC is configured, you are ready to build the compiler and
1558 Some commands executed when making the compiler may fail (return a
1559 nonzero status) and be ignored by @command{make}. These failures, which
1560 are often due to files that were not found, are expected, and can safely
1563 It is normal to have compiler warnings when compiling certain files.
1564 Unless you are a GCC developer, you can generally ignore these warnings
1565 unless they cause compilation to fail. Developers should attempt to fix
1566 any warnings encountered, however they can temporarily continue past
1567 warnings-as-errors by specifying the configure flag
1568 @option{--disable-werror}.
1570 On certain old systems, defining certain environment variables such as
1571 @env{CC} can interfere with the functioning of @command{make}.
1573 If you encounter seemingly strange errors when trying to build the
1574 compiler in a directory other than the source directory, it could be
1575 because you have previously configured the compiler in the source
1576 directory. Make sure you have done all the necessary preparations.
1578 If you build GCC on a BSD system using a directory stored in an old System
1579 V file system, problems may occur in running @command{fixincludes} if the
1580 System V file system doesn't support symbolic links. These problems
1581 result in a failure to fix the declaration of @code{size_t} in
1582 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
1583 that type mismatches occur, this could be the cause.
1585 The solution is not to use such a directory for building GCC@.
1587 When building from SVN or snapshots, or if you modify parser sources,
1588 you need the Bison parser generator installed. If you do not modify
1589 parser sources, releases contain the Bison-generated files and you do
1590 not need Bison installed to build them.
1592 When building from SVN or snapshots, or if you modify Texinfo
1593 documentation, you need version 4.4 or later of Texinfo installed if you
1594 want Info documentation to be regenerated. Releases contain Info
1595 documentation pre-built for the unmodified documentation in the release.
1597 @section Building a native compiler
1599 For a native build, the default configuration is to perform
1600 a 3-stage bootstrap of the compiler when @samp{make} is invoked.
1601 This will build the entire GCC system and ensure that it compiles
1602 itself correctly. It can be disabled with the @option{--disable-bootstrap}
1603 parameter to @samp{configure}, but bootstrapping is suggested because
1604 the compiler will be tested more completely and could also have
1607 The bootstrapping process will complete the following steps:
1611 Build tools necessary to build the compiler.
1614 Perform a 3-stage bootstrap of the compiler. This includes building
1615 three times the target tools for use by the compiler such as binutils
1616 (bfd, binutils, gas, gprof, ld, and opcodes) if they have been
1617 individually linked or moved into the top level GCC source tree before
1621 Perform a comparison test of the stage2 and stage3 compilers.
1624 Build runtime libraries using the stage3 compiler from the previous step.
1628 If you are short on disk space you might consider @samp{make
1629 bootstrap-lean} instead. The sequence of compilation is the
1630 same described above, but object files from the stage1 and
1631 stage2 of the 3-stage bootstrap of the compiler are deleted as
1632 soon as they are no longer needed.
1634 If you want to save additional space during the bootstrap and in
1635 the final installation as well, you can build the compiler binaries
1636 without debugging information as in the following example. This will save
1637 roughly 40% of disk space both for the bootstrap and the final installation.
1638 (Libraries will still contain debugging information.)
1641 make CFLAGS='-O' LIBCFLAGS='-g -O2' \
1642 LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap
1645 If you wish to use non-default GCC flags when compiling the stage2 and
1646 stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing
1647 @samp{make}. Non-default optimization flags are less well
1648 tested here than the default of @samp{-g -O2}, but should still work.
1649 In a few cases, you may find that you need to specify special flags such
1650 as @option{-msoft-float} here to complete the bootstrap; or, if the
1651 native compiler miscompiles the stage1 compiler, you may need to work
1652 around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the
1653 stage1 compiler that were miscompiled, or by using @samp{make
1654 bootstrap4} to increase the number of stages of bootstrap.
1656 Note that using non-standard @code{CFLAGS} can cause bootstrap to fail
1657 if these trigger a warning with the new compiler. For example using
1658 @samp{-O2 -g -mcpu=i686} on @code{i686-pc-linux-gnu} will cause bootstrap
1659 failure as @option{-mcpu=} is deprecated in 3.4.0 and above.
1662 If you used the flag @option{--enable-languages=@dots{}} to restrict
1663 the compilers to be built, only those you've actually enabled will be
1664 built. This will of course only build those runtime libraries, for
1665 which the particular compiler has been built. Please note,
1666 that re-defining @env{LANGUAGES} when calling @samp{make}
1667 @strong{does not} work anymore!
1669 If the comparison of stage2 and stage3 fails, this normally indicates
1670 that the stage2 compiler has compiled GCC incorrectly, and is therefore
1671 a potentially serious bug which you should investigate and report. (On
1672 a few systems, meaningful comparison of object files is impossible; they
1673 always appear ``different''. If you encounter this problem, you will
1674 need to disable comparison in the @file{Makefile}.)
1676 If you do not want to bootstrap your compiler, you can configure with
1677 @option{--disable-bootstrap}. In particular cases, you may want to
1678 bootstrap your compiler even if the target system is not the same as
1679 the one you are building on: for example, you could build a
1680 @code{powerpc-unknown-linux-gnu} toolchain on a
1681 @code{powerpc64-unknown-linux-gnu} host. In this case, pass
1682 @option{--enable-bootstrap} to the configure script.
1685 @section Building a cross compiler
1687 When building a cross compiler, it is not generally possible to do a
1688 3-stage bootstrap of the compiler. This makes for an interesting problem
1689 as parts of GCC can only be built with GCC@.
1691 To build a cross compiler, we first recommend building and installing a
1692 native compiler. You can then use the native GCC compiler to build the
1693 cross compiler. The installed native compiler needs to be GCC version
1696 Assuming you have already installed a native copy of GCC and configured
1697 your cross compiler, issue the command @command{make}, which performs the
1702 Build host tools necessary to build the compiler.
1705 Build target tools for use by the compiler such as binutils (bfd,
1706 binutils, gas, gprof, ld, and opcodes)
1707 if they have been individually linked or moved into the top level GCC source
1708 tree before configuring.
1711 Build the compiler (single stage only).
1714 Build runtime libraries using the compiler from the previous step.
1717 Note that if an error occurs in any step the make process will exit.
1719 If you are not building GNU binutils in the same source tree as GCC,
1720 you will need a cross-assembler and cross-linker installed before
1721 configuring GCC@. Put them in the directory
1722 @file{@var{prefix}/@var{target}/bin}. Here is a table of the tools
1723 you should put in this directory:
1727 This should be the cross-assembler.
1730 This should be the cross-linker.
1733 This should be the cross-archiver: a program which can manipulate
1734 archive files (linker libraries) in the target machine's format.
1737 This should be a program to construct a symbol table in an archive file.
1740 The installation of GCC will find these programs in that directory,
1741 and copy or link them to the proper place to for the cross-compiler to
1742 find them when run later.
1744 The easiest way to provide these files is to build the Binutils package.
1745 Configure it with the same @option{--host} and @option{--target}
1746 options that you use for configuring GCC, then build and install
1747 them. They install their executables automatically into the proper
1748 directory. Alas, they do not support all the targets that GCC
1751 If you are not building a C library in the same source tree as GCC,
1752 you should also provide the target libraries and headers before
1753 configuring GCC, specifying the directories with
1754 @option{--with-sysroot} or @option{--with-headers} and
1755 @option{--with-libs}. Many targets also require ``start files'' such
1756 as @file{crt0.o} and
1757 @file{crtn.o} which are linked into each executable. There may be several
1758 alternatives for @file{crt0.o}, for use with profiling or other
1759 compilation options. Check your target's definition of
1760 @code{STARTFILE_SPEC} to find out what start files it uses.
1762 @section Building in parallel
1764 GNU Make 3.79 and above, which is necessary to build GCC, support
1765 building in parallel. To activate this, you can use @samp{make -j 2}
1766 instead of @samp{make}. You can also specify a bigger number, and
1767 in most cases using a value greater than the number of processors in
1768 your machine will result in fewer and shorter I/O latency hits, thus
1769 improving overall throughput; this is especially true for slow drives
1770 and network filesystems.
1772 @section Building the Ada compiler
1774 In order to build GNAT, the Ada compiler, you need a working GNAT
1775 compiler (GNAT version 3.14 or later, or GCC version 3.1 or later).
1776 This includes GNAT tools such as @command{gnatmake} and
1777 @command{gnatlink}, since the Ada front end is written in Ada and
1778 uses some GNAT-specific extensions.
1780 In order to build a cross compiler, it is suggested to install
1781 the new compiler as native first, and then use it to build the cross
1784 @command{configure} does not test whether the GNAT installation works
1785 and has a sufficiently recent version; if too old a GNAT version is
1786 installed, the build will fail unless @option{--enable-languages} is
1787 used to disable building the Ada front end.
1789 @section Building with profile feedback
1791 It is possible to use profile feedback to optimize the compiler itself. This
1792 should result in a faster compiler binary. Experiments done on x86 using gcc
1793 3.3 showed approximately 7 percent speedup on compiling C programs. To
1794 bootstrap the compiler with profile feedback, use @code{make profiledbootstrap}.
1796 When @samp{make profiledbootstrap} is run, it will first build a @code{stage1}
1797 compiler. This compiler is used to build a @code{stageprofile} compiler
1798 instrumented to collect execution counts of instruction and branch
1799 probabilities. Then runtime libraries are compiled with profile collected.
1800 Finally a @code{stagefeedback} compiler is built using the information collected.
1802 Unlike standard bootstrap, several additional restrictions apply. The
1803 compiler used to build @code{stage1} needs to support a 64-bit integral type.
1804 It is recommended to only use GCC for this. Also parallel make is currently
1805 not supported since collisions in profile collecting may occur.
1812 @uref{./index.html,,Return to the GCC Installation page}
1816 @c ***Testing*****************************************************************
1818 @comment node-name, next, previous, up
1819 @node Testing, Final install, Building, Installing GCC
1823 @chapter Installing GCC: Testing
1826 @cindex Installing GCC: Testing
1829 Before you install GCC, we encourage you to run the testsuites and to
1830 compare your results with results from a similar configuration that have
1831 been submitted to the
1832 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
1833 Some of these archived results are linked from the build status lists
1834 at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who
1835 reports a successful build runs the testsuites and submits the results.
1836 This step is optional and may require you to download additional software,
1837 but it can give you confidence in your new GCC installation or point out
1838 problems before you install and start using your new GCC@.
1840 First, you must have @uref{download.html,,downloaded the testsuites}.
1841 These are part of the full distribution, but if you downloaded the
1842 ``core'' compiler plus any front ends, you must download the testsuites
1845 Second, you must have the testing tools installed. This includes
1846 @uref{http://www.gnu.org/software/dejagnu/,,DejaGnu}, Tcl, and Expect;
1847 the DejaGnu site has links to these.
1849 If the directories where @command{runtest} and @command{expect} were
1850 installed are not in the @env{PATH}, you may need to set the following
1851 environment variables appropriately, as in the following example (which
1852 assumes that DejaGnu has been installed under @file{/usr/local}):
1855 TCL_LIBRARY = /usr/local/share/tcl8.0
1856 DEJAGNULIBS = /usr/local/share/dejagnu
1859 (On systems such as Cygwin, these paths are required to be actual
1860 paths, not mounts or links; presumably this is due to some lack of
1861 portability in the DejaGnu code.)
1864 Finally, you can run the testsuite (which may take a long time):
1866 cd @var{objdir}; make -k check
1869 This will test various components of GCC, such as compiler
1870 front ends and runtime libraries. While running the testsuite, DejaGnu
1871 might emit some harmless messages resembling
1872 @samp{WARNING: Couldn't find the global config file.} or
1873 @samp{WARNING: Couldn't find tool init file} that can be ignored.
1875 @section How can you run the testsuite on selected tests?
1877 In order to run sets of tests selectively, there are targets
1878 @samp{make check-gcc} and @samp{make check-g++}
1879 in the @file{gcc} subdirectory of the object directory. You can also
1880 just run @samp{make check} in a subdirectory of the object directory.
1883 A more selective way to just run all @command{gcc} execute tests in the
1887 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
1890 Likewise, in order to run only the @command{g++} ``old-deja'' tests in
1891 the testsuite with filenames matching @samp{9805*}, you would use
1894 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
1897 The @file{*.exp} files are located in the testsuite directories of the GCC
1898 source, the most important ones being @file{compile.exp},
1899 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
1900 To get a list of the possible @file{*.exp} files, pipe the
1901 output of @samp{make check} into a file and look at the
1902 @samp{Running @dots{} .exp} lines.
1904 @section Passing options and running multiple testsuites
1906 You can pass multiple options to the testsuite using the
1907 @samp{--target_board} option of DejaGNU, either passed as part of
1908 @samp{RUNTESTFLAGS}, or directly to @command{runtest} if you prefer to
1909 work outside the makefiles. For example,
1912 make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants"
1915 will run the standard @command{g++} testsuites (``unix'' is the target name
1916 for a standard native testsuite situation), passing
1917 @samp{-O3 -fmerge-constants} to the compiler on every test, i.e.,
1918 slashes separate options.
1920 You can run the testsuites multiple times using combinations of options
1921 with a syntax similar to the brace expansion of popular shells:
1924 @dots{}"--target_board=arm-sim/@{-mhard-float,-msoft-float@}@{-O1,-O2,-O3,@}"
1927 (Note the empty option caused by the trailing comma in the final group.)
1928 The following will run each testsuite eight times using the @samp{arm-sim}
1929 target, as if you had specified all possible combinations yourself:
1932 --target_board=arm-sim/-mhard-float/-O1
1933 --target_board=arm-sim/-mhard-float/-O2
1934 --target_board=arm-sim/-mhard-float/-O3
1935 --target_board=arm-sim/-mhard-float
1936 --target_board=arm-sim/-msoft-float/-O1
1937 --target_board=arm-sim/-msoft-float/-O2
1938 --target_board=arm-sim/-msoft-float/-O3
1939 --target_board=arm-sim/-msoft-float
1942 They can be combined as many times as you wish, in arbitrary ways. This
1946 @dots{}"--target_board=unix/-Wextra@{-O3,-fno-strength-reduce@}@{-fomit-frame-pointer,@}"
1949 will generate four combinations, all involving @samp{-Wextra}.
1951 The disadvantage to this method is that the testsuites are run in serial,
1952 which is a waste on multiprocessor systems. For users with GNU Make and
1953 a shell which performs brace expansion, you can run the testsuites in
1954 parallel by having the shell perform the combinations and @command{make}
1955 do the parallel runs. Instead of using @samp{--target_board}, use a
1956 special makefile target:
1959 make -j@var{N} check-@var{testsuite}//@var{test-target}/@var{option1}/@var{option2}/@dots{}
1965 make -j3 check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@}
1968 will run three concurrent ``make-gcc'' testsuites, eventually testing all
1969 ten combinations as described above. Note that this is currently only
1970 supported in the @file{gcc} subdirectory. (To see how this works, try
1971 typing @command{echo} before the example given here.)
1974 @section Additional testing for Java Class Libraries
1976 The Java runtime tests can be executed via @samp{make check}
1977 in the @file{@var{target}/libjava/testsuite} directory in
1980 The @uref{http://sources.redhat.com/mauve/,,Mauve Project} provides
1981 a suite of tests for the Java Class Libraries. This suite can be run
1982 as part of libgcj testing by placing the Mauve tree within the libjava
1983 testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by
1984 specifying the location of that tree when invoking @samp{make}, as in
1985 @samp{make MAUVEDIR=~/mauve check}.
1987 @uref{http://sources.redhat.com/mauve/jacks.html,,Jacks}
1988 is a free testsuite that tests Java compiler front ends. This suite
1989 can be run as part of libgcj testing by placing the Jacks tree within
1990 the libjava testsuite at @file{libjava/testsuite/libjava.jacks/jacks}.
1992 @section How to interpret test results
1994 The result of running the testsuite are various @file{*.sum} and @file{*.log}
1995 files in the testsuite subdirectories. The @file{*.log} files contain a
1996 detailed log of the compiler invocations and the corresponding
1997 results, the @file{*.sum} files summarize the results. These summaries
1998 contain status codes for all tests:
2002 PASS: the test passed as expected
2004 XPASS: the test unexpectedly passed
2006 FAIL: the test unexpectedly failed
2008 XFAIL: the test failed as expected
2010 UNSUPPORTED: the test is not supported on this platform
2012 ERROR: the testsuite detected an error
2014 WARNING: the testsuite detected a possible problem
2017 It is normal for some tests to report unexpected failures. At the
2018 current time the testing harness does not allow fine grained control
2019 over whether or not a test is expected to fail. This problem should
2020 be fixed in future releases.
2023 @section Submitting test results
2025 If you want to report the results to the GCC project, use the
2026 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
2029 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
2030 -m gcc-testresults@@gcc.gnu.org |sh
2033 This script uses the @command{Mail} program to send the results, so
2034 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
2035 prepended to the testsuite summary and should contain any special
2036 remarks you have on your results or your build environment. Please
2037 do not edit the testsuite result block or the subject line, as these
2038 messages may be automatically processed.
2045 @uref{./index.html,,Return to the GCC Installation page}
2049 @c ***Final install***********************************************************
2051 @comment node-name, next, previous, up
2052 @node Final install, , Testing, Installing GCC
2054 @ifset finalinstallhtml
2056 @chapter Installing GCC: Final installation
2059 Now that GCC has been built (and optionally tested), you can install it with
2061 cd @var{objdir}; make install
2064 We strongly recommend to install into a target directory where there is
2065 no previous version of GCC present. Also, the GNAT runtime should not
2066 be stripped, as this would break certain features of the debugger that
2067 depend on this debugging information (catching Ada exceptions for
2070 That step completes the installation of GCC; user level binaries can
2071 be found in @file{@var{prefix}/bin} where @var{prefix} is the value
2072 you specified with the @option{--prefix} to configure (or
2073 @file{/usr/local} by default). (If you specified @option{--bindir},
2074 that directory will be used instead; otherwise, if you specified
2075 @option{--exec-prefix}, @file{@var{exec-prefix}/bin} will be used.)
2076 Headers for the C++ and Java libraries are installed in
2077 @file{@var{prefix}/include}; libraries in @file{@var{libdir}}
2078 (normally @file{@var{prefix}/lib}); internal parts of the compiler in
2079 @file{@var{libdir}/gcc} and @file{@var{libexecdir}/gcc}; documentation
2080 in info format in @file{@var{infodir}} (normally
2081 @file{@var{prefix}/info}).
2083 When installing cross-compilers, GCC's executables
2084 are not only installed into @file{@var{bindir}}, that
2085 is, @file{@var{exec-prefix}/bin}, but additionally into
2086 @file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory
2087 exists. Typically, such @dfn{tooldirs} hold target-specific
2088 binutils, including assembler and linker.
2090 Installation into a temporary staging area or into a @command{chroot}
2091 jail can be achieved with the command
2094 make DESTDIR=@var{path-to-rootdir} install
2097 @noindent where @var{path-to-rootdir} is the absolute path of
2098 a directory relative to which all installation paths will be
2099 interpreted. Note that the directory specified by @code{DESTDIR}
2100 need not exist yet; it will be created if necessary.
2102 There is a subtle point with tooldirs and @code{DESTDIR}:
2103 If you relocate a cross-compiler installation with
2104 e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory
2105 @file{@var{rootdir}/@var{exec-prefix}/@var{target-alias}/bin} will
2106 be filled with duplicated GCC executables only if it already exists,
2107 it will not be created otherwise. This is regarded as a feature,
2108 not as a bug, because it gives slightly more control to the packagers
2109 using the @code{DESTDIR} feature.
2111 If you are bootstrapping a released version of GCC then please
2112 quickly review the build status page for your release, available from
2113 @uref{http://gcc.gnu.org/buildstat.html}.
2114 If your system is not listed for the version of GCC that you built,
2116 @email{gcc@@gcc.gnu.org} indicating
2117 that you successfully built and installed GCC@.
2118 Include the following information:
2122 Output from running @file{@var{srcdir}/config.guess}. Do not send
2123 that file itself, just the one-line output from running it.
2126 The output of @samp{gcc -v} for your newly installed @command{gcc}.
2127 This tells us which version of GCC you built and the options you passed to
2131 Whether you enabled all languages or a subset of them. If you used a
2132 full distribution then this information is part of the configure
2133 options in the output of @samp{gcc -v}, but if you downloaded the
2134 ``core'' compiler plus additional front ends then it isn't apparent
2135 which ones you built unless you tell us about it.
2138 If the build was for GNU/Linux, also include:
2141 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
2142 this information should be available from @file{/etc/issue}.
2145 The version of the Linux kernel, available from @samp{uname --version}
2149 The version of glibc you used; for RPM-based systems like Red Hat,
2150 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
2151 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
2153 For other systems, you can include similar information if you think it is
2157 Any other information that you think would be useful to people building
2158 GCC on the same configuration. The new entry in the build status list
2159 will include a link to the archived copy of your message.
2162 We'd also like to know if the
2164 @ref{Specific, host/target specific installation notes}
2167 @uref{specific.html,,host/target specific installation notes}
2169 didn't include your host/target information or if that information is
2170 incomplete or out of date. Send a note to
2171 @email{gcc@@gcc.gnu.org} detailing how the information should be changed.
2173 If you find a bug, please report it following the
2174 @uref{../bugs.html,,bug reporting guidelines}.
2176 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
2177 dvi}. You will need to have @command{texi2dvi} (version at least 4.4)
2178 and @TeX{} installed. This creates a number of @file{.dvi} files in
2179 subdirectories of @file{@var{objdir}}; these may be converted for
2180 printing with programs such as @command{dvips}. Alternately, by using
2181 @samp{make pdf} in place of @samp{make dvi}, you can create documentation
2182 in the form of @file{.pdf} files; this requires @command{texi2pdf}, which
2183 is included with Texinfo version 4.8 and later. You can also
2184 @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the
2185 Free Software Foundation}, though such manuals may not be for the most
2186 recent version of GCC@.
2188 If you would like to generate online HTML documentation, do @samp{cd
2189 @var{objdir}; make html} and HTML will be generated for the gcc manuals in
2190 @file{@var{objdir}/gcc/HTML}.
2197 @uref{./index.html,,Return to the GCC Installation page}
2201 @c ***Binaries****************************************************************
2203 @comment node-name, next, previous, up
2204 @node Binaries, Specific, Installing GCC, Top
2208 @chapter Installing GCC: Binaries
2211 @cindex Installing GCC: Binaries
2213 We are often asked about pre-compiled versions of GCC@. While we cannot
2214 provide these for all platforms, below you'll find links to binaries for
2215 various platforms where creating them by yourself is not easy due to various
2218 Please note that we did not create these binaries, nor do we
2219 support them. If you have any problems installing them, please
2220 contact their makers.
2227 @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX};
2230 @uref{http://aixpdslib.seas.ucla.edu,,UCLA Software Library for AIX}.
2234 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}.
2237 Renesas H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
2238 Development Tools for the Renesas H8/300[HS] Series}.
2244 @uref{http://hpux.cs.utah.edu/,,HP-UX Porting Center};
2247 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
2251 Motorola 68HC11/68HC12---@uref{http://www.gnu-m68hc11.org,,GNU
2252 Development Tools for the Motorola 68HC11/68HC12}.
2255 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
2256 OpenServer/Unixware}.
2259 Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware}.
2262 SGI---@uref{http://freeware.sgi.com/,,SGI Freeware}.
2268 The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project;
2270 The @uref{http://www.mingw.org/,,MinGW} project.
2274 @uref{ftp://ftp.thewrittenword.com/packages/by-name/,,The
2275 Written Word} offers binaries for
2278 Digital UNIX 4.0D and 5.1,
2280 HP-UX 10.20, 11.00, and 11.11, and
2281 Solaris/SPARC 2.5.1, 2.6, 7, 8, and 9.
2284 @uref{http://www.openpkg.org/,,OpenPKG} offers binaries for quite a
2285 number of platforms.
2288 The @uref{http://gcc.gnu.org/wiki/GFortranBinaries,,GFortran Wiki} has
2289 links to GNU Fortran binaries for several platforms.
2292 In addition to those specific offerings, you can get a binary
2293 distribution CD-ROM from the
2294 @uref{http://www.gnu.org/order/order.html,,Free Software Foundation}.
2295 It contains binaries for a number of platforms, and
2296 includes not only GCC, but other stuff as well. The current CD does
2297 not contain the latest version of GCC, but it should allow
2298 bootstrapping the compiler. An updated version of that disk is in the
2306 @uref{./index.html,,Return to the GCC Installation page}
2310 @c ***Specific****************************************************************
2312 @comment node-name, next, previous, up
2313 @node Specific, Old, Binaries, Top
2317 @chapter Host/target specific installation notes for GCC
2320 @cindex Specific installation notes
2321 @cindex Target specific installation
2322 @cindex Host specific installation
2323 @cindex Target specific installation notes
2325 Please read this document carefully @emph{before} installing the
2326 GNU Compiler Collection on your machine.
2328 Note that this list of install notes is @emph{not} a list of supported
2329 hosts or targets. Not all supported hosts and targets are listed
2330 here, only the ones that require host-specific or target-specific
2336 @uref{#alpha-x-x,,alpha*-*-*}
2338 @uref{#alpha-dec-osf,,alpha*-dec-osf*}
2340 @uref{#alphaev5-cray-unicosmk,,alphaev5-cray-unicosmk*}
2342 @uref{#arc-x-elf,,arc-*-elf}
2344 @uref{#arm-x-elf,,arm-*-elf}
2345 @uref{#arm-x-coff,,arm-*-coff}
2346 @uref{#arm-x-aout,,arm-*-aout}
2348 @uref{#xscale-x-x,,xscale-*-*}
2352 @uref{#bfin,,Blackfin}
2358 @uref{#x-x-freebsd,,*-*-freebsd*}
2360 @uref{#h8300-hms,,h8300-hms}
2362 @uref{#hppa-hp-hpux,,hppa*-hp-hpux*}
2364 @uref{#hppa-hp-hpux10,,hppa*-hp-hpux10}
2366 @uref{#hppa-hp-hpux11,,hppa*-hp-hpux11}
2368 @uref{#x-x-linux-gnu,,*-*-linux-gnu}
2370 @uref{#ix86-x-linuxaout,,i?86-*-linux*aout}
2372 @uref{#ix86-x-linux,,i?86-*-linux*}
2374 @uref{#ix86-x-sco32v5,,i?86-*-sco3.2v5*}
2376 @uref{#ix86-x-solaris210,,i?86-*-solaris2.10}
2378 @uref{#ix86-x-udk,,i?86-*-udk}
2380 @uref{#ia64-x-linux,,ia64-*-linux}
2382 @uref{#ia64-x-hpux,,ia64-*-hpux*}
2384 @uref{#x-ibm-aix,,*-ibm-aix*}
2386 @uref{#iq2000-x-elf,,iq2000-*-elf}
2388 @uref{#m32c-x-elf,,m32c-*-elf}
2390 @uref{#m32r-x-elf,,m32r-*-elf}
2392 @uref{#m6811-elf,,m6811-elf}
2394 @uref{#m6812-elf,,m6812-elf}
2396 @uref{#m68k-hp-hpux,,m68k-hp-hpux}
2398 @uref{#mips-x-x,,mips-*-*}
2400 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
2402 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
2404 @uref{#powerpc-x-x,,powerpc*-*-*, powerpc-*-sysv4}
2406 @uref{#powerpc-x-darwin,,powerpc-*-darwin*}
2408 @uref{#powerpc-x-elf,,powerpc-*-elf, powerpc-*-sysv4}
2410 @uref{#powerpc-x-linux-gnu,,powerpc*-*-linux-gnu*}
2412 @uref{#powerpc-x-netbsd,,powerpc-*-netbsd*}
2414 @uref{#powerpc-x-eabisim,,powerpc-*-eabisim}
2416 @uref{#powerpc-x-eabi,,powerpc-*-eabi}
2418 @uref{#powerpcle-x-elf,,powerpcle-*-elf, powerpcle-*-sysv4}
2420 @uref{#powerpcle-x-eabisim,,powerpcle-*-eabisim}
2422 @uref{#powerpcle-x-eabi,,powerpcle-*-eabi}
2424 @uref{#s390-x-linux,,s390-*-linux*}
2426 @uref{#s390x-x-linux,,s390x-*-linux*}
2428 @uref{#s390x-ibm-tpf,,s390x-ibm-tpf*}
2430 @uref{#x-x-solaris2,,*-*-solaris2*}
2432 @uref{#sparc-sun-solaris2,,sparc-sun-solaris2*}
2434 @uref{#sparc-sun-solaris27,,sparc-sun-solaris2.7}
2436 @uref{#sparc-x-linux,,sparc-*-linux*}
2438 @uref{#sparc64-x-solaris2,,sparc64-*-solaris2*}
2440 @uref{#sparcv9-x-solaris2,,sparcv9-*-solaris2*}
2442 @uref{#x-x-sysv,,*-*-sysv*}
2444 @uref{#vax-dec-ultrix,,vax-dec-ultrix}
2446 @uref{#x-x-vxworks,,*-*-vxworks*}
2448 @uref{#x86-64-x-x,,x86_64-*-*, amd64-*-*}
2450 @uref{#xtensa-x-elf,,xtensa-*-elf}
2452 @uref{#xtensa-x-linux,,xtensa-*-linux*}
2454 @uref{#windows,,Microsoft Windows}
2458 @uref{#older,,Older systems}
2463 @uref{#elf,,all ELF targets} (SVR4, Solaris 2, etc.)
2469 <!-- -------- host/target specific issues start here ---------------- -->
2472 @heading @anchor{alpha-x-x}alpha*-*-*
2474 This section contains general configuration information for all
2475 alpha-based platforms using ELF (in particular, ignore this section for
2476 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
2477 section, please read all other sections that match your target.
2479 We require binutils 2.11.2 or newer.
2480 Previous binutils releases had a number of problems with DWARF 2
2481 debugging information, not the least of which is incorrect linking of
2487 @heading @anchor{alpha-dec-osf}alpha*-dec-osf*
2488 Systems using processors that implement the DEC Alpha architecture and
2489 are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
2490 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
2492 As of GCC 3.2, versions before @code{alpha*-dec-osf4} are no longer
2493 supported. (These are the versions which identify themselves as DEC
2496 In Digital Unix V4.0, virtual memory exhausted bootstrap failures
2497 may be fixed by configuring with @option{--with-gc=simple},
2498 reconfiguring Kernel Virtual Memory and Swap parameters
2499 per the @command{/usr/sbin/sys_check} Tuning Suggestions,
2500 or applying the patch in
2501 @uref{http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html}.
2503 In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
2504 currently (2001-06-13) work with @command{mips-tfile}. As a workaround,
2505 we need to use the old assembler, invoked via the barely documented
2506 @option{-oldas} option. To bootstrap GCC, you either need to use the
2510 % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
2513 or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
2516 % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
2519 As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld}
2520 are supported on Tru64 UNIX, so you must not configure GCC with
2521 @option{--with-gnu-as} or @option{--with-gnu-ld}.
2523 GCC writes a @samp{.verstamp} directive to the assembler output file
2524 unless it is built as a cross-compiler. It gets the version to use from
2525 the system header file @file{/usr/include/stamp.h}. If you install a
2526 new version of DEC Unix, you should rebuild GCC to pick up the new version
2529 Note that since the Alpha is a 64-bit architecture, cross-compilers from
2530 32-bit machines will not generate code as efficient as that generated
2531 when the compiler is running on a 64-bit machine because many
2532 optimizations that depend on being able to represent a word on the
2533 target in an integral value on the host cannot be performed. Building
2534 cross-compilers on the Alpha for 32-bit machines has only been tested in
2535 a few cases and may not work properly.
2537 @samp{make compare} may fail on old versions of DEC Unix unless you add
2538 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
2539 assembler input file is stored in the object file, and that makes
2540 comparison fail if it differs between the @code{stage1} and
2541 @code{stage2} compilations. The option @option{-save-temps} forces a
2542 fixed name to be used for the assembler input file, instead of a
2543 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
2544 unless the comparisons fail without that option. If you add
2545 @option{-save-temps}, you will have to manually delete the @samp{.i} and
2546 @samp{.s} files after each series of compilations.
2548 GCC now supports both the native (ECOFF) debugging format used by DBX
2549 and GDB and an encapsulated STABS format for use only with GDB@. See the
2550 discussion of the @option{--with-stabs} option of @file{configure} above
2551 for more information on these formats and how to select them.
2553 There is a bug in DEC's assembler that produces incorrect line numbers
2554 for ECOFF format when the @samp{.align} directive is used. To work
2555 around this problem, GCC will not emit such alignment directives
2556 while writing ECOFF format debugging information even if optimization is
2557 being performed. Unfortunately, this has the very undesirable
2558 side-effect that code addresses when @option{-O} is specified are
2559 different depending on whether or not @option{-g} is also specified.
2561 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
2562 DBX@. DEC is now aware of this problem with the assembler and hopes to
2563 provide a fix shortly.
2568 @heading @anchor{alphaev5-cray-unicosmk}alphaev5-cray-unicosmk*
2569 Cray T3E systems running Unicos/Mk.
2571 This port is incomplete and has many known bugs. We hope to improve the
2572 support for this target soon. Currently, only the C front end is supported,
2573 and it is not possible to build parallel applications. Cray modules are not
2574 supported; in particular, Craylibs are assumed to be in
2575 @file{/opt/ctl/craylibs/craylibs}.
2577 On this platform, you need to tell GCC where to find the assembler and
2578 the linker. The simplest way to do so is by providing @option{--with-as}
2579 and @option{--with-ld} to @file{configure}, e.g.@:
2582 configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld \
2583 --enable-languages=c
2586 The comparison test at the end of the bootstrapping process fails on Unicos/Mk
2587 because the assembler inserts timestamps into object files. You should
2588 be able to work around this by doing @samp{make all} after getting this
2594 @heading @anchor{arc-x-elf}arc-*-elf
2595 Argonaut ARC processor.
2596 This configuration is intended for embedded systems.
2601 @heading @anchor{arm-x-elf}arm-*-elf
2602 @heading @anchor{xscale-x-x}xscale-*-*
2603 ARM-family processors. Subtargets that use the ELF object format
2604 require GNU binutils 2.13 or newer. Such subtargets include:
2605 @code{arm-*-freebsd}, @code{arm-*-netbsdelf}, @code{arm-*-*linux},
2606 @code{arm-*-rtems} and @code{arm-*-kaos}.
2611 @heading @anchor{arm-x-coff}arm-*-coff
2612 ARM-family processors. Note that there are two different varieties
2613 of PE format subtarget supported: @code{arm-wince-pe} and
2614 @code{arm-pe} as well as a standard COFF target @code{arm-*-coff}.
2619 @heading @anchor{arm-x-aout}arm-*-aout
2620 ARM-family processors. These targets support the AOUT file format:
2621 @code{arm-*-aout}, @code{arm-*-netbsd}.
2626 @heading @anchor{avr}avr
2628 ATMEL AVR-family micro controllers. These are used in embedded
2629 applications. There are no standard Unix configurations.
2631 @xref{AVR Options,, AVR Options, gcc, Using the GNU Compiler
2635 See ``AVR Options'' in the main manual
2637 for the list of supported MCU types.
2639 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
2641 Further installation notes and other useful information about AVR tools
2642 can also be obtained from:
2646 @uref{http://www.nongnu.org/avr/,,http://www.nongnu.org/avr/}
2648 @uref{http://home.overta.ru/users/denisc/,,http://home.overta.ru/users/denisc/}
2650 @uref{http://www.amelek.gda.pl/avr/,,http://www.amelek.gda.pl/avr/}
2653 We @emph{strongly} recommend using binutils 2.13 or newer.
2655 The following error:
2657 Error: register required
2660 indicates that you should upgrade to a newer version of the binutils.
2665 @heading @anchor{bfin}Blackfin
2667 The Blackfin processor, an Analog Devices DSP.
2669 @xref{Blackfin Options,, Blackfin Options, gcc, Using the GNU Compiler
2673 See ``Blackfin Options'' in the main manual
2676 More information, and a version of binutils with support for this processor,
2677 is available at @uref{http://blackfin.uclinux.org}
2682 @heading @anchor{c4x}c4x
2684 Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal
2685 Processors. These are used in embedded applications. There are no
2686 standard Unix configurations.
2688 @xref{TMS320C3x/C4x Options,, TMS320C3x/C4x Options, gcc, Using the
2689 GNU Compiler Collection (GCC)},
2692 See ``TMS320C3x/C4x Options'' in the main manual
2694 for the list of supported MCU types.
2696 GCC can be configured as a cross compiler for both the C3x and C4x
2697 architectures on the same system. Use @samp{configure --target=c4x
2698 --enable-languages="c,c++"} to configure.
2701 Further installation notes and other useful information about C4x tools
2702 can also be obtained from:
2706 @uref{http://www.elec.canterbury.ac.nz/c4x/,,http://www.elec.canterbury.ac.nz/c4x/}
2712 @heading @anchor{cris}CRIS
2714 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
2715 series. These are used in embedded applications.
2718 @xref{CRIS Options,, CRIS Options, gcc, Using the GNU Compiler
2722 See ``CRIS Options'' in the main manual
2724 for a list of CRIS-specific options.
2726 There are a few different CRIS targets:
2728 @item cris-axis-aout
2729 Old target. Includes a multilib for the @samp{elinux} a.out-based
2730 target. No multilibs for newer architecture variants.
2732 Mainly for monolithic embedded systems. Includes a multilib for the
2733 @samp{v10} core used in @samp{ETRAX 100 LX}.
2734 @item cris-axis-linux-gnu
2735 A GNU/Linux port for the CRIS architecture, currently targeting
2736 @samp{ETRAX 100 LX} by default.
2739 For @code{cris-axis-aout} and @code{cris-axis-elf} you need binutils 2.11
2740 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
2742 Pre-packaged tools can be obtained from
2743 @uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More
2744 information about this platform is available at
2745 @uref{http://developer.axis.com/}.
2750 @heading @anchor{crx}CRX
2752 The CRX CompactRISC architecture is a low-power 32-bit architecture with
2753 fast context switching and architectural extensibility features.
2756 @xref{CRX Options,, CRX Options, gcc, Using and Porting the GNU Compiler
2761 See ``CRX Options'' in the main manual for a list of CRX-specific options.
2764 Use @samp{configure --target=crx-elf --enable-languages=c,c++} to configure
2765 GCC@ for building a CRX cross-compiler. The option @samp{--target=crx-elf}
2766 is also used to build the @samp{newlib} C library for CRX.
2768 It is also possible to build libstdc++-v3 for the CRX architecture. This
2769 needs to be done in a separate step with the following configure settings:
2770 @samp{gcc/libstdc++-v3/configure --host=crx-elf --with-newlib
2771 --enable-sjlj-exceptions --enable-cxx-flags='-fexceptions -frtti'}
2776 @heading @anchor{dos}DOS
2778 Please have a look at the @uref{binaries.html,,binaries page}.
2780 You cannot install GCC by itself on MSDOS; it will not compile under
2781 any MSDOS compiler except itself. You need to get the complete
2782 compilation package DJGPP, which includes binaries as well as sources,
2783 and includes all the necessary compilation tools and libraries.
2788 @heading @anchor{x-x-freebsd}*-*-freebsd*
2790 The version of binutils installed in @file{/usr/bin} probably works with
2791 this release of GCC@. However, on FreeBSD 4, bootstrapping against the
2792 latest FSF binutils is known to improve overall testsuite results; and,
2793 on FreeBSD/alpha, using binutils 2.14 or later is required to build libjava.
2795 Support for FreeBSD 1 was discontinued in GCC 3.2.
2797 Support for FreeBSD 2 will be discontinued after GCC 3.4. The
2798 following was true for GCC 3.1 but the current status is unknown.
2799 For FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
2800 configuration support and files as shipped with GCC 2.95 are still in
2801 place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
2802 it is unknown which version of binutils was used (it is assumed that it
2803 was the system copy in @file{/usr/bin}) and C++ EH failures were noted.
2805 For FreeBSD using the ELF file format: DWARF 2 debugging is now the
2806 default for all CPU architectures. It had been the default on
2807 FreeBSD/alpha since its inception. You may use @option{-gstabs} instead
2808 of @option{-g}, if you really want the old debugging format. There are
2809 no known issues with mixing object files and libraries with different
2810 debugging formats. Otherwise, this release of GCC should now match more
2811 of the configuration used in the stock FreeBSD configuration of GCC@. In
2812 particular, @option{--enable-threads} is now configured by default.
2813 However, as a general user, do not attempt to replace the system
2814 compiler with this release. Known to bootstrap and check with good
2815 results on FreeBSD 4.9-STABLE and 5-CURRENT@. In the past, known to
2816 bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2,
2817 4.3, 4.4, 4.5, 4.8-STABLE@.
2819 In principle, @option{--enable-threads} is now compatible with
2820 @option{--enable-libgcj} on FreeBSD@. However, it has only been built
2821 and tested on @samp{i386-*-freebsd[45]} and @samp{alpha-*-freebsd[45]}.
2823 library may be incorrectly built (symbols are missing at link time).
2824 There is a rare timing-based startup hang (probably involves an
2825 assumption about the thread library). Multi-threaded boehm-gc (required for
2826 libjava) exposes severe threaded signal-handling bugs on FreeBSD before
2827 4.5-RELEASE@. Other CPU architectures
2828 supported by FreeBSD will require additional configuration tuning in, at
2829 the very least, both boehm-gc and libffi.
2831 Shared @file{libgcc_s.so} is now built and installed by default.
2836 @heading @anchor{h8300-hms}h8300-hms
2837 Renesas H8/300 series of processors.
2839 Please have a look at the @uref{binaries.html,,binaries page}.
2841 The calling convention and structure layout has changed in release 2.6.
2842 All code must be recompiled. The calling convention now passes the
2843 first three arguments in function calls in registers. Structures are no
2844 longer a multiple of 2 bytes.
2849 @heading @anchor{hppa-hp-hpux}hppa*-hp-hpux*
2850 Support for HP-UX version 9 and older was discontinued in GCC 3.4.
2852 We require using gas/binutils on all hppa platforms;
2853 you may encounter a variety of problems if you try to use the HP assembler.
2855 Specifically, @option{-g} does not work on HP-UX (since that system
2856 uses a peculiar debugging format which GCC does not know about), unless
2857 you use GAS and GDB@. It may be helpful to configure GCC with the
2858 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
2859 @option{--with-as=@dots{}} options to ensure that GCC can find GAS@.
2861 If you wish to use the pa-risc 2.0 architecture support with a 32-bit
2862 runtime, you must use gas/binutils 2.11 or newer.
2864 There are two default scheduling models for instructions. These are
2865 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
2866 architecture specified for the target machine when configuring.
2867 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
2868 the target is a @samp{hppa1*} machine.
2870 The PROCESSOR_8000 model is not well suited to older processors. Thus,
2871 it is important to completely specify the machine architecture when
2872 configuring if you want a model other than PROCESSOR_8000. The macro
2873 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
2874 default scheduling model is desired.
2876 As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
2877 through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
2878 This namespace change might cause problems when bootstrapping with
2879 an earlier version of GCC or the HP compiler as essentially the same
2880 namespace is required for an entire build. This problem can be avoided
2881 in a number of ways. With HP cc, @env{UNIX_STD} can be set to @samp{95}
2882 or @samp{98}. Another way is to add an appropriate set of predefines
2883 to @env{CC}. The description for the @option{munix=} option contains
2884 a list of the predefines used with each standard.
2886 As of GCC 4.1, @env{DWARF2} exception handling is available on HP-UX.
2887 It is now the default. This exposed a bug in the handling of data
2888 relocations in the GAS assembler. The handling of 64-bit data relocations
2889 was seriously broken, affecting debugging and exception support on all
2890 @samp{hppa64-*-*} targets. Under some circumstances, 32-bit data relocations
2891 could also be handled incorrectly. This problem is fixed in GAS version
2894 GCC versions prior to 4.1 incorrectly passed and returned complex
2895 values. They are now passed in the same manner as aggregates.
2897 More specific information to @samp{hppa*-hp-hpux*} targets follows.
2902 @heading @anchor{hppa-hp-hpux10}hppa*-hp-hpux10
2904 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
2905 @code{PHCO_19798} from HP@. HP has two sites which provide patches free of
2911 <a href="http://us.itrc.hp.com/service/home/home.do">US, Canada, Asia-Pacific, and
2915 @uref{http://us.itrc.hp.com/service/home/home.do,,} US, Canada, Asia-Pacific,
2919 @uref{http://europe.itrc.hp.com/service/home/home.do,,} Europe.
2922 The HP assembler on these systems has some problems. Most notably the
2923 assembler inserts timestamps into each object file it creates, causing
2924 the 3-stage comparison test to fail during a bootstrap.
2925 You should be able to continue by saying @samp{make all-host all-target}
2926 after getting the failure from @samp{make}.
2928 GCC 4.0 requires CVS binutils as of April 28, 2004 or later. Earlier
2929 versions require binutils 2.8 or later.
2931 The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are
2932 used for one-only code and data. This resolves many of the previous
2933 problems in using C++ on this target. However, the ABI is not compatible
2934 with the one implemented under HP-UX 11 using secondary definitions.
2939 @heading @anchor{hppa-hp-hpux11}hppa*-hp-hpux11
2941 GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
2942 be used to compile GCC 3.0 and up.
2944 Refer to @uref{binaries.html,,binaries} for information about obtaining
2945 precompiled GCC binaries for HP-UX@. Precompiled binaries must be obtained
2946 to build the Ada language as it can't be bootstrapped using C@. Ada is
2947 only available for the 32-bit PA-RISC runtime. The libffi and libjava
2948 haven't been ported to HP-UX and don't build.
2950 Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The
2951 bundled compiler supports only traditional C; you will need either HP's
2952 unbundled compiler, or a binary distribution of GCC@.
2954 It is possible to build GCC 3.3 starting with the bundled HP compiler,
2955 but the process requires several steps. GCC 3.3 can then be used to
2956 build later versions. The fastjar program contains ISO C code and
2957 can't be built with the HP bundled compiler. This problem can be
2958 avoided by not building the Java language. For example, use the
2959 @option{--enable-languages="c,c++,f77,objc"} option in your configure
2962 There are several possible approaches to building the distribution.
2963 Binutils can be built first using the HP tools. Then, the GCC
2964 distribution can be built. The second approach is to build GCC
2965 first using the HP tools, then build binutils, then rebuild GCC@.
2966 There have been problems with various binary distributions, so it
2967 is best not to start from a binary distribution.
2969 On 64-bit capable systems, there are two distinct targets. Different
2970 installation prefixes must be used if both are to be installed on
2971 the same system. The @samp{hppa[1-2]*-hp-hpux11*} target generates code
2972 for the 32-bit PA-RISC runtime architecture and uses the HP linker.
2973 The @samp{hppa64-hp-hpux11*} target generates 64-bit code for the
2974 PA-RISC 2.0 architecture. The HP and GNU linkers are both supported
2977 The script config.guess now selects the target type based on the compiler
2978 detected during configuration. You must define @env{PATH} or @env{CC} so
2979 that configure finds an appropriate compiler for the initial bootstrap.
2980 When @env{CC} is used, the definition should contain the options that are
2981 needed whenever @env{CC} is used.
2983 Specifically, options that determine the runtime architecture must be
2984 in @env{CC} to correctly select the target for the build. It is also
2985 convenient to place many other compiler options in @env{CC}. For example,
2986 @env{CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"}
2987 can be used to bootstrap the GCC 3.3 branch with the HP compiler in
2988 64-bit K&R/bundled mode. The @option{+DA2.0W} option will result in
2989 the automatic selection of the @samp{hppa64-hp-hpux11*} target. The
2990 macro definition table of cpp needs to be increased for a successful
2991 build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to
2992 be defined when building with the bundled compiler, or when using the
2993 @option{-Ac} option. These defines aren't necessary with @option{-Ae}.
2995 It is best to explicitly configure the @samp{hppa64-hp-hpux11*} target
2996 with the @option{--with-ld=@dots{}} option. This overrides the standard
2997 search for ld. The two linkers supported on this target require different
2998 commands. The default linker is determined during configuration. As a
2999 result, it's not possible to switch linkers in the middle of a GCC build.
3000 This has been been reported to sometimes occur in unified builds of
3003 GCC 3.0 through 3.2 require binutils 2.11 or above. GCC 3.3 through
3004 GCC 4.0 require binutils 2.14 or later.
3006 Although the HP assembler can be used for an initial build, it shouldn't
3007 be used with any languages other than C and perhaps Fortran due to its
3008 many limitations. For example, it does not support weak symbols or alias
3009 definitions. As a result, explicit template instantiations are required
3010 when using C++. This makes it difficult if not impossible to build many
3011 C++ applications. You can't generate debugging information when using
3012 the HP assembler. Finally, bootstrapping fails in the final
3013 comparison of object modules due to the time stamps that it inserts into
3014 the modules. The bootstrap can be continued from this point with
3015 @samp{make all-host all-target}.
3017 A recent linker patch must be installed for the correct operation of
3018 GCC 3.3 and later. @code{PHSS_26559} and @code{PHSS_24304} are the
3019 oldest linker patches that are known to work. They are for HP-UX
3020 11.00 and 11.11, respectively. @code{PHSS_24303}, the companion to
3021 @code{PHSS_24304}, might be usable but it hasn't been tested. These
3022 patches have been superseded. Consult the HP patch database to obtain
3023 the currently recommended linker patch for your system.
3025 The patches are necessary for the support of weak symbols on the
3026 32-bit port, and for the running of initializers and finalizers. Weak
3027 symbols are implemented using SOM secondary definition symbols. Prior
3028 to HP-UX 11, there are bugs in the linker support for secondary symbols.
3029 The patches correct a problem of linker core dumps creating shared
3030 libraries containing secondary symbols, as well as various other
3031 linking issues involving secondary symbols.
3033 GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
3034 run initializers and finalizers on the 64-bit port. The 32-bit port
3035 uses the linker @option{+init} and @option{+fini} options for the same
3036 purpose. The patches correct various problems with the +init/+fini
3037 options, including program core dumps. Binutils 2.14 corrects a
3038 problem on the 64-bit port resulting from HP's non-standard use of
3039 the .init and .fini sections for array initializers and finalizers.
3041 There are a number of issues to consider in selecting which linker to
3042 use with the 64-bit port. The GNU 64-bit linker can only create dynamic
3043 binaries. The @option{-static} option causes linking with archive
3044 libraries but doesn't produce a truly static binary. Dynamic binaries
3045 still require final binding by the dynamic loader to resolve a set of
3046 dynamic-loader-defined symbols. The default behavior of the HP linker
3047 is the same as the GNU linker. However, it can generate true 64-bit
3048 static binaries using the @option{+compat} option.
3050 The HP 64-bit linker doesn't support linkonce semantics. As a
3051 result, C++ programs have many more sections than they should.
3053 The GNU 64-bit linker has some issues with shared library support
3054 and exceptions. As a result, we only support libgcc in archive
3055 format. For similar reasons, dwarf2 unwind and exception support
3056 are disabled. The GNU linker also has problems creating binaries
3057 with @option{-static}. It doesn't provide stubs for internal
3058 calls to global functions in shared libraries, so these calls
3059 can't be overloaded.
3061 Thread support is not implemented in GCC 3.0 through 3.2, so the
3062 @option{--enable-threads} configure option does not work. In 3.3
3063 and later, POSIX threads are supported. The optional DCE thread
3064 library is not supported.
3066 This port still is undergoing significant development.
3071 @heading @anchor{x-x-linux-gnu}*-*-linux-gnu
3073 Versions of libstdc++-v3 starting with 3.2.1 require bugfixes present
3074 in glibc 2.2.5 and later. More information is available in the
3075 libstdc++-v3 documentation.
3080 @heading @anchor{ix86-x-linuxaout}i?86-*-linux*aout
3081 Use this configuration to generate @file{a.out} binaries on Linux-based
3082 GNU systems. This configuration is being superseded.
3087 @heading @anchor{ix86-x-linux}i?86-*-linux*
3089 As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
3090 See @uref{http://gcc.gnu.org/PR10877,,bug 10877} for more information.
3092 If you receive Signal 11 errors when building on GNU/Linux, then it is
3093 possible you have a hardware problem. Further information on this can be
3094 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
3099 @heading @anchor{ix86-x-sco32v5}i?86-*-sco3.2v5*
3100 Use this for the SCO OpenServer Release 5 family of operating systems.
3102 Unlike earlier versions of GCC, the ability to generate COFF with this
3103 target is no longer provided.
3105 Earlier versions of GCC emitted DWARF 1 when generating ELF to allow
3106 the system debugger to be used. That support was too burdensome to
3107 maintain. GCC now emits only DWARF 2 for this target. This means you
3108 may use either the UDK debugger or GDB to debug programs built by this
3111 GCC is now only supported on releases 5.0.4 and later, and requires that
3112 you install Support Level Supplement OSS646B or later, and Support Level
3113 Supplement OSS631C or later. If you are using release 5.0.7 of
3114 OpenServer, you must have at least the first maintenance pack installed
3115 (this includes the relevant portions of OSS646). OSS646, also known as
3116 the ``Execution Environment Update'', provides updated link editors and
3117 assemblers, as well as updated standard C and math libraries. The C
3118 startup modules are also updated to support the System V gABI draft, and
3119 GCC relies on that behavior. OSS631 provides a collection of commonly
3120 used open source libraries, some of which GCC depends on (such as GNU
3121 gettext and zlib). SCO OpenServer Release 5.0.7 has all of this built
3122 in by default, but OSS631C and later also apply to that release. Please
3124 @uref{ftp://ftp.sco.com/pub/openserver5,,ftp://ftp.sco.com/pub/openserver5}
3125 for the latest versions of these (and other potentially useful)
3128 Although there is support for using the native assembler, it is
3129 recommended that you configure GCC to use the GNU assembler. You do
3130 this by using the flags
3131 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You should
3132 use a modern version of GNU binutils. Version 2.13.2.1 was used for all
3133 testing. In general, only the @option{--with-gnu-as} option is tested.
3134 A modern bintuils (as well as a plethora of other development related
3135 GNU utilities) can be found in Support Level Supplement OSS658A, the
3136 ``GNU Development Tools'' package. See the SCO web and ftp sites for details.
3137 That package also contains the currently ``officially supported'' version of
3138 GCC, version 2.95.3. It is useful for bootstrapping this version.
3143 @heading @anchor{ix86-x-solaris210}i?86-*-solaris2.10
3144 Use this for Solaris 10 or later on x86 and x86-64 systems. This
3145 configuration is supported by GCC 4.0 and later versions only.
3147 It is recommended that you configure GCC to use the GNU assembler in
3148 @file{/usr/sfw/bin/gas} but the Sun linker, using the options
3149 @option{--with-gnu-as --with-as=/usr/sfw/bin/gas --without-gnu-ld
3150 --with-ld=/usr/ccs/bin/ld}.
3155 @heading @anchor{ix86-x-udk}i?86-*-udk
3157 This target emulates the SCO Universal Development Kit and requires that
3158 package be installed. (If it is installed, you will have a
3159 @file{/udk/usr/ccs/bin/cc} file present.) It's very much like the
3160 @samp{i?86-*-unixware7*} target
3161 but is meant to be used when hosting on a system where UDK isn't the
3162 default compiler such as OpenServer 5 or Unixware 2. This target will
3163 generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
3164 with the same warnings and caveats as the SCO UDK@.
3166 This target is a little tricky to build because we have to distinguish
3167 it from the native tools (so it gets headers, startups, and libraries
3168 from the right place) while making the tools not think we're actually
3169 building a cross compiler. The easiest way to do this is with a configure
3173 CC=/udk/usr/ccs/bin/cc @var{/your/path/to}/gcc/configure \
3174 --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-
3177 @emph{You should substitute @samp{i686} in the above command with the appropriate
3178 processor for your host.}
3180 After the usual @samp{make} and
3181 @samp{make install}, you can then access the UDK-targeted GCC
3182 tools by adding @command{udk-} before the commonly known name. For
3183 example, to invoke the C compiler, you would use @command{udk-gcc}.
3184 They will coexist peacefully with any native-target GCC tools you may
3191 @heading @anchor{ia64-x-linux}ia64-*-linux
3192 IA-64 processor (also known as IPF, or Itanium Processor Family)
3195 If you are using the installed system libunwind library with
3196 @option{--with-system-libunwind}, then you must use libunwind 0.98 or
3199 None of the following versions of GCC has an ABI that is compatible
3200 with any of the other versions in this list, with the exception that
3201 Red Hat 2.96 and Trillian 000171 are compatible with each other:
3202 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
3203 This primarily affects C++ programs and programs that create shared libraries.
3204 GCC 3.1 or later is recommended for compiling linux, the kernel.
3205 As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
3206 more major ABI changes are expected.
3211 @heading @anchor{ia64-x-hpux}ia64-*-hpux*
3212 Building GCC on this target requires the GNU Assembler. The bundled HP
3213 assembler will not work. To prevent GCC from using the wrong assembler,
3214 the option @option{--with-gnu-as} may be necessary.
3216 The GCC libunwind library has not been ported to HPUX@. This means that for
3217 GCC versions 3.2.3 and earlier, @option{--enable-libunwind-exceptions}
3218 is required to build GCC@. For GCC 3.3 and later, this is the default.
3219 For gcc 3.4.3 and later, @option{--enable-libunwind-exceptions} is
3220 removed and the system libunwind library will always be used.
3224 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
3226 @heading @anchor{x-ibm-aix}*-ibm-aix*
3227 Support for AIX version 3 and older was discontinued in GCC 3.4.
3229 ``out of memory'' bootstrap failures may indicate a problem with
3230 process resource limits (ulimit). Hard limits are configured in the
3231 @file{/etc/security/limits} system configuration file.
3233 To speed up the configuration phases of bootstrapping and installing GCC,
3234 one may use GNU Bash instead of AIX @command{/bin/sh}, e.g.,
3237 % CONFIG_SHELL=/opt/freeware/bin/bash
3238 % export CONFIG_SHELL
3241 and then proceed as described in @uref{build.html,,the build
3242 instructions}, where we strongly recommend specifying an absolute path
3243 to invoke @var{srcdir}/configure.
3245 Because GCC on AIX is built as a 32-bit executable by default,
3246 (although it can generate 64-bit programs) the GMP and MPFR libraries
3247 required by gfortran must be 32-bit libraries. Building GMP and MPFR
3248 as static archive libraries works better than shared libraries.
3250 Errors involving @code{alloca} when building GCC generally are due
3251 to an incorrect definition of @code{CC} in the Makefile or mixing files
3252 compiled with the native C compiler and GCC@. During the stage1 phase of
3253 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
3254 (not @command{xlc}). Once @command{configure} has been informed of
3255 @command{xlc}, one needs to use @samp{make distclean} to remove the
3256 configure cache files and ensure that @env{CC} environment variable
3257 does not provide a definition that will confuse @command{configure}.
3258 If this error occurs during stage2 or later, then the problem most likely
3259 is the version of Make (see above).
3261 The native @command{as} and @command{ld} are recommended for bootstrapping
3262 on AIX 4 and required for bootstrapping on AIX 5L@. The GNU Assembler
3263 reports that it supports WEAK symbols on AIX 4, which causes GCC to try to
3264 utilize weak symbol functionality although it is not supported. The GNU
3265 Assembler and Linker do not support AIX 5L sufficiently to bootstrap GCC@.
3266 The native AIX tools do interoperate with GCC@.
3268 Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
3269 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
3270 fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
3271 referenced as APAR IY53606 (AIX 5.2) or a APAR IY54774 (AIX 5.1)
3273 @samp{libstdc++} in GCC 3.4 increments the major version number of the
3274 shared object and GCC installation places the @file{libstdc++.a}
3275 shared library in a common location which will overwrite the and GCC
3276 3.3 version of the shared library. Applications either need to be
3277 re-linked against the new shared library or the GCC 3.1 and GCC 3.3
3278 versions of the @samp{libstdc++} shared object needs to be available
3279 to the AIX runtime loader. The GCC 3.1 @samp{libstdc++.so.4}, if
3280 present, and GCC 3.3 @samp{libstdc++.so.5} shared objects can be
3281 installed for runtime dynamic loading using the following steps to set
3282 the @samp{F_LOADONLY} flag in the shared object for @emph{each}
3283 multilib @file{libstdc++.a} installed:
3285 Extract the shared objects from the currently installed
3286 @file{libstdc++.a} archive:
3288 % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
3291 Enable the @samp{F_LOADONLY} flag so that the shared object will be
3292 available for runtime dynamic loading, but not linking:
3294 % strip -e libstdc++.so.4 libstdc++.so.5
3297 Archive the runtime-only shared object in the GCC 3.4
3298 @file{libstdc++.a} archive:
3300 % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
3303 Linking executables and shared libraries may produce warnings of
3304 duplicate symbols. The assembly files generated by GCC for AIX always
3305 have included multiple symbol definitions for certain global variable
3306 and function declarations in the original program. The warnings should
3307 not prevent the linker from producing a correct library or runnable
3310 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
3311 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
3312 to parse archive libraries did not handle the new format correctly.
3313 These routines are used by GCC and result in error messages during
3314 linking such as ``not a COFF file''. The version of the routines shipped
3315 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
3316 option of the archive command may be used to create archives of 32-bit
3317 objects using the original ``small format''. A correct version of the
3318 routines is shipped with AIX 4.3.2 and above.
3320 Some versions of the AIX binder (linker) can fail with a relocation
3321 overflow severe error when the @option{-bbigtoc} option is used to link
3322 GCC-produced object files into an executable that overflows the TOC@. A fix
3323 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
3324 available from IBM Customer Support and from its
3325 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3326 website as PTF U455193.
3328 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
3329 with a segmentation fault when invoked by any version of GCC@. A fix for
3330 APAR IX87327 is available from IBM Customer Support and from its
3331 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3332 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
3334 The initial assembler shipped with AIX 4.3.0 generates incorrect object
3335 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
3336 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
3337 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3338 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
3340 AIX provides National Language Support (NLS)@. Compilers and assemblers
3341 use NLS to support locale-specific representations of various data
3342 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
3343 separating decimal fractions). There have been problems reported where
3344 GCC does not produce the same floating-point formats that the assembler
3345 expects. If one encounters this problem, set the @env{LANG}
3346 environment variable to @samp{C} or @samp{En_US}.
3348 By default, GCC for AIX 4.1 and above produces code that can be used on
3349 both Power or PowerPC processors.
3351 A default can be specified with the @option{-mcpu=@var{cpu_type}}
3352 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
3357 @heading @anchor{iq2000-x-elf}iq2000-*-elf
3358 Vitesse IQ2000 processors. These are used in embedded
3359 applications. There are no standard Unix configurations.
3364 @heading @anchor{m32c-x-elf}m32c-*-elf
3365 Renesas M32C processor.
3366 This configuration is intended for embedded systems.
3371 @heading @anchor{m32r-x-elf}m32r-*-elf
3372 Renesas M32R processor.
3373 This configuration is intended for embedded systems.
3378 @heading @anchor{m6811-elf}m6811-elf
3379 Motorola 68HC11 family micro controllers. These are used in embedded
3380 applications. There are no standard Unix configurations.
3385 @heading @anchor{m6812-elf}m6812-elf
3386 Motorola 68HC12 family micro controllers. These are used in embedded
3387 applications. There are no standard Unix configurations.
3392 @heading @anchor{m68k-*-*}m68k-*-*
3393 You can specify a default target using @option{--with-cpu=@var{target}}.
3394 The recognized values for @var{target} are: @samp{m68000}, @samp{m68010},
3395 @samp{m68020}, @samp{m68030}, @samp{m68040}, @samp{m68060}, @samp{m68020-40}
3396 and @samp{m68020-60}.
3398 @heading @anchor{m68k-hp-hpux}m68k-hp-hpux
3399 HP 9000 series 300 or 400 running HP-UX@. HP-UX version 8.0 has a bug in
3400 the assembler that prevents compilation of GCC@. This
3401 bug manifests itself during the first stage of compilation, while
3402 building @file{libgcc2.a}:
3406 cc1: warning: `-g' option not supported on this version of GCC
3407 cc1: warning: `-g1' option not supported on this version of GCC
3408 ./xgcc: Internal compiler error: program as got fatal signal 11
3411 A patched version of the assembler is available as the file
3412 @uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you
3413 have HP software support, the patch can also be obtained directly from
3414 HP, as described in the following note:
3417 This is the patched assembler, to patch SR#1653-010439, where the
3418 assembler aborts on floating point constants.
3420 The bug is not really in the assembler, but in the shared library
3421 version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is
3422 SR#4701-078451. Anyway, the attached assembler uses the archive
3423 library version of ``cvtnum(3c)'' and thus does not exhibit the bug.
3426 This patch is also known as PHCO_4484.
3428 In addition gdb does not understand that native HP-UX format, so
3429 you must use gas if you wish to use gdb.
3431 On HP-UX version 8.05, but not on 8.07 or more recent versions, the
3432 @command{fixproto} shell script triggers a bug in the system shell. If you
3433 encounter this problem, upgrade your operating system or use BASH (the
3434 GNU shell) to run @command{fixproto}. This bug will cause the fixproto
3435 program to report an error of the form:
3438 ./fixproto: sh internal 1K buffer overflow
3441 To fix this, you can also change the first line of the fixproto script
3451 @heading @anchor{mips-x-x}mips-*-*
3452 If on a MIPS system you get an error message saying ``does not have gp
3453 sections for all it's [sic] sectons [sic]'', don't worry about it. This
3454 happens whenever you use GAS with the MIPS linker, but there is not
3455 really anything wrong, and it is okay to use the output file. You can
3456 stop such warnings by installing the GNU linker.
3458 It would be nice to extend GAS to produce the gp tables, but they are
3459 optional, and there should not be a warning about their absence.
3461 The libstdc++ atomic locking routines for MIPS targets requires MIPS II
3462 and later. A patch went in just after the GCC 3.3 release to
3463 make @samp{mips*-*-*} use the generic implementation instead. You can also
3464 configure for @samp{mipsel-elf} as a workaround. The
3465 @samp{mips*-*-linux*} target continues to use the MIPS II routines. More
3466 work on this is expected in future releases.
3468 MIPS systems check for division by zero (unless
3469 @option{-mno-check-zero-division} is passed to the compiler) by
3470 generating either a conditional trap or a break instruction. Using
3471 trap results in smaller code, but is only supported on MIPS II and
3472 later. Also, some versions of the Linux kernel have a bug that
3473 prevents trap from generating the proper signal (@code{SIGFPE}). To enable
3474 the use of break, use the @option{--with-divide=breaks}
3475 @command{configure} option when configuring GCC@. The default is to
3476 use traps on systems that support them.
3478 Cross-compilers for the MIPS as target using the MIPS assembler
3479 currently do not work, because the auxiliary programs
3480 @file{mips-tdump.c} and @file{mips-tfile.c} can't be compiled on
3481 anything but a MIPS. It does work to cross compile for a MIPS
3482 if you use the GNU assembler and linker.
3484 The linker from GNU binutils versions prior to 2.17 has a bug which
3485 causes the runtime linker stubs in @file{libgcj.so} to be incorrectly
3486 generated. If you want to use libgcj, either use binutils 2.17 or
3487 later to build it or export @samp{LD_BIND_NOW=1} in your runtime environment.
3492 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
3494 In order to compile GCC on an SGI running IRIX 5, the @samp{compiler_dev.hdr}
3495 subsystem must be installed from the IDO CD-ROM supplied by SGI@.
3496 It is also available for download from
3497 @uref{ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist}.
3499 If you use the MIPS C compiler to bootstrap, it may be necessary
3500 to increase its table size for switch statements with the
3501 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
3502 optimization option, you also need to use @option{-Olimit 3000}.
3504 To enable debugging under IRIX 5, you must use GNU binutils 2.15 or
3505 later, and use the @option{--with-gnu-ld} @command{configure} option
3506 when configuring GCC@. You need to use GNU @command{ar} and @command{nm},
3507 also distributed with GNU binutils.
3509 Some users have reported that @command{/bin/sh} will hang during bootstrap.
3510 This problem can be avoided by running the commands:
3513 % CONFIG_SHELL=/bin/ksh
3514 % export CONFIG_SHELL
3517 before starting the build.
3522 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
3524 If you are using SGI's MIPSpro @command{cc} as your bootstrap compiler, you must
3525 ensure that the N32 ABI is in use. To test this, compile a simple C
3526 file with @command{cc} and then run @command{file} on the
3527 resulting object file. The output should look like:
3530 test.o: ELF N32 MSB @dots{}
3536 test.o: ELF 32-bit MSB @dots{}
3542 test.o: ELF 64-bit MSB @dots{}
3545 then your version of @command{cc} uses the O32 or N64 ABI by default. You
3546 should set the environment variable @env{CC} to @samp{cc -n32}
3547 before configuring GCC@.
3549 If you want the resulting @command{gcc} to run on old 32-bit systems
3550 with the MIPS R4400 CPU, you need to ensure that only code for the @samp{mips3}
3551 instruction set architecture (ISA) is generated. While GCC 3.x does
3552 this correctly, both GCC 2.95 and SGI's MIPSpro @command{cc} may change
3553 the ISA depending on the machine where GCC is built. Using one of them
3554 as the bootstrap compiler may result in @samp{mips4} code, which won't run at
3555 all on @samp{mips3}-only systems. For the test program above, you should see:
3558 test.o: ELF N32 MSB mips-3 @dots{}
3564 test.o: ELF N32 MSB mips-4 @dots{}
3567 instead, you should set the environment variable @env{CC} to @samp{cc
3568 -n32 -mips3} or @samp{gcc -mips3} respectively before configuring GCC@.
3570 MIPSpro C 7.4 may cause bootstrap failures, due to a bug when inlining
3571 @code{memcmp}. Either add @code{-U__INLINE_INTRINSICS} to the @env{CC}
3572 environment variable as a workaround or upgrade to MIPSpro C 7.4.1m.
3574 GCC on IRIX 6 is usually built to support the N32, O32 and N64 ABIs. If
3575 you build GCC on a system that doesn't have the N64 libraries installed
3576 or cannot run 64-bit binaries,
3577 you need to configure with @option{--disable-multilib} so GCC doesn't
3578 try to use them. This will disable building the O32 libraries, too.
3579 Look for @file{/usr/lib64/libc.so.1} to see if you
3580 have the 64-bit libraries installed.
3582 To enable debugging for the O32 ABI, you must use GNU @command{as} from
3583 GNU binutils 2.15 or later. You may also use GNU @command{ld}, but
3584 this is not required and currently causes some problems with Ada.
3586 The @option{--enable-threads} option doesn't currently work, a patch is
3587 in preparation for a future release. The @option{--enable-libgcj}
3588 option is disabled by default: IRIX 6 uses a very low default limit
3589 (20480) for the command line length. Although @command{libtool} contains a
3590 workaround for this problem, at least the N64 @samp{libgcj} is known not
3591 to build despite this, running into an internal error of the native
3592 @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
3593 its maximum of 262144 bytes. If you have root access, you can use the
3594 @command{systune} command to do this.
3596 @code{wchar_t} support in @samp{libstdc++} is not available for old
3597 IRIX 6.5.x releases, @math{x < 19}. The problem cannot be autodetected
3598 and in order to build GCC for such targets you need to configure with
3599 @option{--disable-wchar_t}.
3601 See @uref{http://freeware.sgi.com/} for more
3602 information about using GCC on IRIX platforms.
3607 @heading @anchor{powerpc-x-x}powerpc-*-*
3609 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
3610 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
3615 @heading @anchor{powerpc-x-darwin}powerpc-*-darwin*
3616 PowerPC running Darwin (Mac OS X kernel).
3618 Pre-installed versions of Mac OS X may not include any developer tools,
3619 meaning that you will not be able to build GCC from source. Tool
3620 binaries are available at
3621 @uref{http://developer.apple.com/darwin/projects/compiler/} (free
3622 registration required).
3624 This version of GCC requires at least cctools-590.36. The
3625 cctools-590.36 package referenced from
3626 @uref{http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html} will not work
3627 on systems older than 10.3.9 (aka darwin7.9.0).
3632 @heading @anchor{powerpc-x-elf}powerpc-*-elf, powerpc-*-sysv4
3633 PowerPC system in big endian mode, running System V.4.
3638 @heading @anchor{powerpc-x-linux-gnu}powerpc*-*-linux-gnu*
3641 @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.15}
3642 or newer for a working GCC@.
3647 @heading @anchor{powerpc-x-netbsd}powerpc-*-netbsd*
3648 PowerPC system in big endian mode running NetBSD@. To build the
3649 documentation you will need Texinfo version 4.4 (NetBSD 1.5.1 included
3650 Texinfo version 3.12).
3655 @heading @anchor{powerpc-x-eabisim}powerpc-*-eabisim
3656 Embedded PowerPC system in big endian mode for use in running under the
3662 @heading @anchor{powerpc-x-eabi}powerpc-*-eabi
3663 Embedded PowerPC system in big endian mode.
3668 @heading @anchor{powerpcle-x-elf}powerpcle-*-elf, powerpcle-*-sysv4
3669 PowerPC system in little endian mode, running System V.4.
3674 @heading @anchor{powerpcle-x-eabisim}powerpcle-*-eabisim
3675 Embedded PowerPC system in little endian mode for use in running under
3681 @heading @anchor{powerpcle-x-eabi}powerpcle-*-eabi
3682 Embedded PowerPC system in little endian mode.
3687 @heading @anchor{s390-x-linux}s390-*-linux*
3688 S/390 system running GNU/Linux for S/390@.
3693 @heading @anchor{s390x-x-linux}s390x-*-linux*
3694 zSeries system (64-bit) running GNU/Linux for zSeries@.
3699 @heading @anchor{s390x-ibm-tpf}s390x-ibm-tpf*
3700 zSeries system (64-bit) running TPF@. This platform is
3701 supported as cross-compilation target only.
3706 @c Please use Solaris 2 to refer to all release of Solaris, starting
3707 @c with 2.0 until 2.6, 7, 8, etc. Solaris 1 was a marketing name for
3708 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
3709 @c alone is too unspecific and must be avoided.
3710 @heading @anchor{x-x-solaris2}*-*-solaris2*
3712 Sun does not ship a C compiler with Solaris 2. To bootstrap and install
3713 GCC you first have to install a pre-built compiler, see the
3714 @uref{binaries.html,,binaries page} for details.
3716 The Solaris 2 @command{/bin/sh} will often fail to configure
3717 @file{libstdc++-v3}, @file{boehm-gc} or @file{libjava}. We therefore
3718 recommend using the following initial sequence of commands
3721 % CONFIG_SHELL=/bin/ksh
3722 % export CONFIG_SHELL
3725 and proceed as described in @uref{configure.html,,the configure instructions}.
3726 In addition we strongly recommend specifying an absolute path to invoke
3727 @var{srcdir}/configure.
3729 Solaris 2 comes with a number of optional OS packages. Some of these
3730 are needed to use GCC fully, namely @code{SUNWarc},
3731 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
3732 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
3733 optional packages when installing Solaris 2, you will need to verify that
3734 the packages that GCC needs are installed.
3736 To check whether an optional package is installed, use
3737 the @command{pkginfo} command. To add an optional package, use the
3738 @command{pkgadd} command. For further details, see the Solaris 2
3741 Trying to use the linker and other tools in
3742 @file{/usr/ucb} to install GCC has been observed to cause trouble.
3743 For example, the linker may hang indefinitely. The fix is to remove
3744 @file{/usr/ucb} from your @env{PATH}.
3746 The build process works more smoothly with the legacy Sun tools so, if you
3747 have @file{/usr/xpg4/bin} in your @env{PATH}, we recommend that you place
3748 @file{/usr/bin} before @file{/usr/xpg4/bin} for the duration of the build.
3750 All releases of GNU binutils prior to 2.11.2 have known bugs on this
3751 platform. We recommend the use of GNU binutils 2.11.2 or later, or the
3752 vendor tools (Sun @command{as}, Sun @command{ld}). Note that your mileage
3753 may vary if you use a combination of the GNU tools and the Sun tools: while
3754 the combination GNU @command{as} + Sun @command{ld} should reasonably work,
3755 the reverse combination Sun @command{as} + GNU @command{ld} is known to
3756 cause memory corruption at runtime in some cases for C++ programs.
3758 The stock GNU binutils 2.15 release is broken on this platform because of a
3759 single bug. It has been fixed on the 2.15 branch in the CVS repository.
3760 You can obtain a working version by checking out the binutils-2_15-branch
3761 from the CVS repository or applying the patch
3762 @uref{http://sources.redhat.com/ml/binutils-cvs/2004-09/msg00036.html} to the
3765 We recommend using GNU binutils 2.16 or later in conjunction with GCC 4.x,
3766 or the vendor tools (Sun @command{as}, Sun @command{ld}). However, for
3767 Solaris 10 and above, an additional patch is required in order for the GNU
3768 linker to be able to cope with a new flavor of shared libraries. You
3769 can obtain a working version by checking out the binutils-2_16-branch from
3770 the CVS repository or applying the patch
3771 @uref{http://sourceware.org/ml/binutils-cvs/2005-07/msg00122.html} to the
3774 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3775 newer: @command{g++} will complain that types are missing. These headers assume
3776 that omitting the type means @code{int}; this assumption worked for C89 but
3777 is wrong for C++, and is now wrong for C99 also.
3779 @command{g++} accepts such (invalid) constructs with the option
3780 @option{-fpermissive}; it
3781 will assume that any missing type is @code{int} (as defined by C89).
3783 There are patches for Solaris 2.6 (105633-56 or newer for SPARC,
3784 106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC,
3785 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
3786 108653-22 for Intel) that fix this bug.
3788 Sun bug 4927647 sometimes causes random spurious testsuite failures
3789 related to missing diagnostic output. This bug doesn't affect GCC
3790 itself, rather it is a kernel bug triggered by the @command{expect}
3791 program which is used only by the GCC testsuite driver. When the bug
3792 causes the @command{expect} program to miss anticipated output, extra
3793 testsuite failures appear.
3795 There are patches for Solaris 8 (117350-12 or newer for SPARC,
3796 117351-12 or newer for Intel) and Solaris 9 (117171-11 or newer for
3797 SPARC, 117172-11 or newer for Intel) that address this problem.
3802 @heading @anchor{sparc-sun-solaris2}sparc-sun-solaris2*
3804 When GCC is configured to use binutils 2.11.2 or later the binaries
3805 produced are smaller than the ones produced using Sun's native tools;
3806 this difference is quite significant for binaries containing debugging
3809 Sun @command{as} 4.x is broken in that it cannot cope with long symbol names.
3810 A typical error message might look similar to the following:
3813 /usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error:
3814 can't compute value of an expression involving an external symbol.
3817 This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris
3818 2.6 and has been fixed in later (5.x) versions of the assembler,
3819 starting with Solaris 7.
3821 Starting with Solaris 7, the operating system is capable of executing
3822 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
3823 this; the @option{-m64} option enables 64-bit code generation.
3824 However, if all you want is code tuned for the UltraSPARC CPU, you
3825 should try the @option{-mtune=ultrasparc} option instead, which produces
3826 code that, unlike full 64-bit code, can still run on non-UltraSPARC
3829 When configuring on a Solaris 7 or later system that is running a kernel
3830 that supports only 32-bit binaries, one must configure with
3831 @option{--disable-multilib}, since we will not be able to build the
3832 64-bit target libraries.
3834 GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of
3835 the GNU compiler (especially GCC 3.0.x versions), which lead to the
3836 miscompilation of the stage1 compiler and the subsequent failure of the
3837 bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary
3838 stage, i.e.@: to bootstrap that compiler with the base compiler and then
3839 use it to bootstrap the final compiler.
3841 GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7)
3842 and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap
3843 failure in form of a miscompilation of the stage1 compiler by the Sun
3844 compiler. This is Sun bug 4974440. This is fixed with patch 112760-07.
3846 GCC 3.4 changed the default debugging format from STABS to DWARF-2 for
3847 32-bit code on Solaris 7 and later. If you use the Sun assembler, this
3848 change apparently runs afoul of Sun bug 4910101 (which is referenced as
3849 a x86-only problem by Sun, probably because they do not use DWARF-2).
3850 A symptom of the problem is that you cannot compile C++ programs like
3851 @command{groff} 1.19.1 without getting messages similar to the following:
3854 ld: warning: relocation error: R_SPARC_UA32: @dots{}
3855 external symbolic relocation against non-allocatable section
3856 .debug_info cannot be processed at runtime: relocation ignored.
3859 To work around this problem, compile with @option{-gstabs+} instead of
3862 When configuring the GNU Multiple Precision Library (GMP) or the MPFR
3863 library on a Solaris 7 or later system, the canonical target triplet
3864 must be specified as the @command{build} parameter on the configure
3865 line. This triplet can be obtained by invoking ./config.guess in
3866 the toplevel source directory of GCC (and not that of GMP or MPFR).
3867 For example on a Solaris 7 system:
3870 % ./configure --build=sparc-sun-solaris2.7 --prefix=xxx
3876 @heading @anchor{sparc-sun-solaris27}sparc-sun-solaris2.7
3878 Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
3879 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
3880 and later, including all EGCS releases. Sun formerly recommended
3881 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
3882 recommend it only for people who use Sun's compilers.
3884 Here are some workarounds to this problem:
3887 Do not install Sun patch 107058-01 until after Sun releases a
3888 complete patch for bug 4210064. This is the simplest course to take,
3889 unless you must also use Sun's C compiler. Unfortunately 107058-01
3890 is preinstalled on some new Solaris 7-based hosts, so you may have to
3894 Copy the original, unpatched Solaris 7
3895 @command{/usr/ccs/bin/as} into
3896 @command{/usr/local/libexec/gcc/sparc-sun-solaris2.7/3.4/as},
3897 adjusting the latter name to fit your local conventions and software
3901 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
3902 both 107058-01 and 106950-03 installed has reported the bug with GCC
3903 and Sun's dynamic linker. This last course of action is riskiest,
3904 for two reasons. First, you must install 106950 on all hosts that
3905 run code generated by GCC; it doesn't suffice to install it only on
3906 the hosts that run GCC itself. Second, Sun says that 106950-03 is
3907 only a partial fix for bug 4210064, but Sun doesn't know whether the
3908 partial fix is adequate for GCC@. Revision -08 or later should fix
3909 the bug. The current (as of 2004-05-23) revision is -24, and is included in
3910 the Solaris 7 Recommended Patch Cluster.
3913 GCC 3.3 triggers a bug in version 5.0 Alpha 03/27/98 of the Sun assembler,
3914 which causes a bootstrap failure when linking the 64-bit shared version of
3915 libgcc. A typical error message is:
3918 ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o:
3919 symbol <unknown>: offset 0xffffffff7ec133e7 is non-aligned.
3922 This bug has been fixed in the final 5.0 version of the assembler.
3924 A similar problem was reported for version Sun WorkShop 6 99/08/18 of the
3925 Sun assembler, which causes a bootstrap failure with GCC 4.0.0:
3928 ld: fatal: relocation error: R_SPARC_DISP32:
3929 file .libs/libstdc++.lax/libsupc++convenience.a/vterminate.o:
3930 symbol <unknown>: offset 0xfccd33ad is non-aligned
3933 This bug has been fixed in more recent revisions of the assembler.
3938 @heading @anchor{sparc-x-linux}sparc-*-linux*
3940 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
3941 or newer on this platform. All earlier binutils and glibc
3942 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
3948 @heading @anchor{sparc64-x-solaris2}sparc64-*-solaris2*
3950 When configuring the GNU Multiple Precision Library (GMP) or the
3951 MPFR library, the canonical target triplet must be specified as
3952 the @command{build} parameter on the configure line. For example
3953 on a Solaris 7 system:
3956 % ./configure --build=sparc64-sun-solaris2.7 --prefix=xxx
3959 The following compiler flags must be specified in the configure
3960 step in order to bootstrap this target with the Sun compiler:
3963 % CC="cc -xarch=v9 -xildoff" @var{srcdir}/configure [@var{options}] [@var{target}]
3966 @option{-xarch=v9} specifies the SPARC-V9 architecture to the Sun toolchain
3967 and @option{-xildoff} turns off the incremental linker.
3972 @heading @anchor{sparcv9-x-solaris2}sparcv9-*-solaris2*
3974 This is a synonym for sparc64-*-solaris2*.
3979 @heading @anchor{x-x-sysv}*-*-sysv*
3980 On System V release 3, you may get this error message
3984 ld fatal: failed to write symbol name @var{something}
3985 in strings table for file @var{whatever}
3988 This probably indicates that the disk is full or your ulimit won't allow
3989 the file to be as large as it needs to be.
3991 This problem can also result because the kernel parameter @code{MAXUMEM}
3992 is too small. If so, you must regenerate the kernel and make the value
3993 much larger. The default value is reported to be 1024; a value of 32768
3994 is said to work. Smaller values may also work.
3996 On System V, if you get an error like this,
3999 /usr/local/lib/bison.simple: In function `yyparse':
4000 /usr/local/lib/bison.simple:625: virtual memory exhausted
4004 that too indicates a problem with disk space, ulimit, or @code{MAXUMEM}.
4006 On a System V release 4 system, make sure @file{/usr/bin} precedes
4007 @file{/usr/ucb} in @code{PATH}. The @command{cc} command in
4008 @file{/usr/ucb} uses libraries which have bugs.
4013 @heading @anchor{vax-dec-ultrix}vax-dec-ultrix
4014 Don't try compiling with VAX C (@command{vcc}). It produces incorrect code
4015 in some cases (for example, when @code{alloca} is used).
4020 @heading @anchor{x-x-vxworks}*-*-vxworks*
4021 Support for VxWorks is in flux. At present GCC supports @emph{only} the
4022 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC@.
4023 We welcome patches for other architectures supported by VxWorks 5.5.
4024 Support for VxWorks AE would also be welcome; we believe this is merely
4025 a matter of writing an appropriate ``configlette'' (see below). We are
4026 not interested in supporting older, a.out or COFF-based, versions of
4029 VxWorks comes with an older version of GCC installed in
4030 @file{@var{$WIND_BASE}/host}; we recommend you do not overwrite it.
4031 Choose an installation @var{prefix} entirely outside @var{$WIND_BASE}.
4032 Before running @command{configure}, create the directories @file{@var{prefix}}
4033 and @file{@var{prefix}/bin}. Link or copy the appropriate assembler,
4034 linker, etc.@: into @file{@var{prefix}/bin}, and set your @var{PATH} to
4035 include that directory while running both @command{configure} and
4038 You must give @command{configure} the
4039 @option{--with-headers=@var{$WIND_BASE}/target/h} switch so that it can
4040 find the VxWorks system headers. Since VxWorks is a cross compilation
4041 target only, you must also specify @option{--target=@var{target}}.
4042 @command{configure} will attempt to create the directory
4043 @file{@var{prefix}/@var{target}/sys-include} and copy files into it;
4044 make sure the user running @command{configure} has sufficient privilege
4047 GCC's exception handling runtime requires a special ``configlette''
4048 module, @file{contrib/gthr_supp_vxw_5x.c}. Follow the instructions in
4049 that file to add the module to your kernel build. (Future versions of
4050 VxWorks will incorporate this module.)
4055 @heading @anchor{x86-64-x-x}x86_64-*-*, amd64-*-*
4057 GCC supports the x86-64 architecture implemented by the AMD64 processor
4058 (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD@.
4059 On GNU/Linux the default is a bi-arch compiler which is able to generate
4060 both 64-bit x86-64 and 32-bit x86 code (via the @option{-m32} switch).
4065 @heading @anchor{xtensa-x-elf}xtensa-*-elf
4067 This target is intended for embedded Xtensa systems using the
4068 @samp{newlib} C library. It uses ELF but does not support shared
4069 objects. Designed-defined instructions specified via the
4070 Tensilica Instruction Extension (TIE) language are only supported
4071 through inline assembly.
4073 The Xtensa configuration information must be specified prior to
4074 building GCC@. The @file{include/xtensa-config.h} header
4075 file contains the configuration information. If you created your
4076 own Xtensa configuration with the Xtensa Processor Generator, the
4077 downloaded files include a customized copy of this header file,
4078 which you can use to replace the default header file.
4083 @heading @anchor{xtensa-x-linux}xtensa-*-linux*
4085 This target is for Xtensa systems running GNU/Linux. It supports ELF
4086 shared objects and the GNU C library (glibc). It also generates
4087 position-independent code (PIC) regardless of whether the
4088 @option{-fpic} or @option{-fPIC} options are used. In other
4089 respects, this target is the same as the
4090 @uref{#xtensa-*-elf,,@samp{xtensa-*-elf}} target.
4095 @heading @anchor{windows}Microsoft Windows (32-bit)
4097 Ports of GCC are included with the
4098 @uref{http://www.cygwin.com/,,Cygwin environment}.
4100 GCC will build under Cygwin without modification; it does not build
4101 with Microsoft's C++ compiler and there are no plans to make it do so.
4106 @heading @anchor{os2}OS/2
4108 GCC does not currently support OS/2. However, Andrew Zabolotny has been
4109 working on a generic OS/2 port with pgcc. The current code can be found
4110 at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
4115 @heading @anchor{older}Older systems
4117 GCC contains support files for many older (1980s and early
4118 1990s) Unix variants. For the most part, support for these systems
4119 has not been deliberately removed, but it has not been maintained for
4120 several years and may suffer from bitrot.
4122 Starting with GCC 3.1, each release has a list of ``obsoleted'' systems.
4123 Support for these systems is still present in that release, but
4124 @command{configure} will fail unless the @option{--enable-obsolete}
4125 option is given. Unless a maintainer steps forward, support for these
4126 systems will be removed from the next release of GCC@.
4128 Support for old systems as hosts for GCC can cause problems if the
4129 workarounds for compiler, library and operating system bugs affect the
4130 cleanliness or maintainability of the rest of GCC@. In some cases, to
4131 bring GCC up on such a system, if still possible with current GCC, may
4132 require first installing an old version of GCC which did work on that
4133 system, and using it to compile a more recent GCC, to avoid bugs in the
4134 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
4135 @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror
4136 sites}. Header bugs may generally be avoided using
4137 @command{fixincludes}, but bugs or deficiencies in libraries and the
4138 operating system may still cause problems.
4140 Support for older systems as targets for cross-compilation is less
4141 problematic than support for them as hosts for GCC; if an enthusiast
4142 wishes to make such a target work again (including resurrecting any of
4143 the targets that never worked with GCC 2, starting from the last
4144 version before they were removed), patches
4145 @uref{../contribute.html,,following the usual requirements} would be
4146 likely to be accepted, since they should not affect the support for more
4149 For some systems, old versions of GNU binutils may also be useful,
4150 and are available from @file{pub/binutils/old-releases} on
4151 @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}.
4153 Some of the information on specific systems above relates to
4154 such older systems, but much of the information
4155 about GCC on such systems (which may no longer be applicable to
4156 current GCC) is to be found in the GCC texinfo manual.
4161 @heading @anchor{elf}all ELF targets (SVR4, Solaris 2, etc.)
4163 C++ support is significantly better on ELF targets if you use the
4164 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
4165 inlines, vtables and template instantiations will be discarded
4174 @uref{./index.html,,Return to the GCC Installation page}
4178 @c ***Old documentation******************************************************
4180 @include install-old.texi
4186 @uref{./index.html,,Return to the GCC Installation page}
4190 @c ***GFDL********************************************************************
4198 @uref{./index.html,,Return to the GCC Installation page}
4202 @c ***************************************************************************
4203 @c Part 6 The End of the Document
4205 @comment node-name, next, previous, up
4206 @node Concept Index, , GNU Free Documentation License, Top
4210 @unnumbered Concept Index