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 Free Software Foundation, Inc.
47 @c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com
49 @c Include everything if we're not making html
53 @set prerequisiteshtml
64 @c Part 2 Summary Description and Copyright
66 Copyright @copyright{} 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
67 1999, 2000, 2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc.
69 Permission is granted to copy, distribute and/or modify this document
70 under the terms of the GNU Free Documentation License, Version 1.2 or
71 any later version published by the Free Software Foundation; with no
72 Invariant Sections, the Front-Cover texts being (a) (see below), and
73 with the Back-Cover Texts being (b) (see below). A copy of the
74 license is included in the section entitled ``@uref{./gfdl.html,,GNU
75 Free Documentation License}''.
77 (a) The FSF's Front-Cover Text is:
81 (b) The FSF's Back-Cover Text is:
83 You have freedom to copy and modify this GNU Manual, like GNU
84 software. Copies published by the Free Software Foundation raise
85 funds for GNU development.
90 @dircategory Programming
92 * gccinstall: (gccinstall). Installing the GNU Compiler Collection.
95 @c Part 3 Titlepage and Copyright
98 @comment The title is printed in a large font.
99 @center @titlefont{Installing GCC}
101 @c The following two commands start the copyright page.
103 @vskip 0pt plus 1filll
107 @c Part 4 Top node and Master Menu
110 @comment node-name, next, Previous, up
113 * Installing GCC:: This document describes the generic installation
114 procedure for GCC as well as detailing some target
115 specific installation instructions.
117 * Specific:: Host/target specific installation notes for GCC.
118 * Binaries:: Where to get pre-compiled binaries.
120 * Old:: Old installation documentation.
122 * GNU Free Documentation License:: How you can copy and share this manual.
123 * Concept Index:: This index has two entries.
127 @c Part 5 The Body of the Document
128 @c ***Installing GCC**********************************************************
130 @comment node-name, next, previous, up
131 @node Installing GCC, Binaries, , Top
135 @chapter Installing GCC
138 The latest version of this document is always available at
139 @uref{http://gcc.gnu.org/install/,,http://gcc.gnu.org/install/}.
141 This document describes the generic installation procedure for GCC as well
142 as detailing some target specific installation instructions.
144 GCC includes several components that previously were separate distributions
145 with their own installation instructions. This document supersedes all
146 package specific installation instructions.
148 @emph{Before} starting the build/install procedure please check the
150 @ref{Specific, host/target specific installation notes}.
153 @uref{specific.html,,host/target specific installation notes}.
155 We recommend you browse the entire generic installation instructions before
158 Lists of successful builds for released versions of GCC are
159 available at @uref{http://gcc.gnu.org/buildstat.html}.
160 These lists are updated as new information becomes available.
162 The installation procedure itself is broken into five steps.
167 * Downloading the source::
170 * Testing:: (optional)
177 @uref{prerequisites.html,,Prerequisites}
179 @uref{download.html,,Downloading the source}
181 @uref{configure.html,,Configuration}
183 @uref{build.html,,Building}
185 @uref{test.html,,Testing} (optional)
187 @uref{finalinstall.html,,Final install}
191 Please note that GCC does not support @samp{make uninstall} and probably
192 won't do so in the near future as this would open a can of worms. Instead,
193 we suggest that you install GCC into a directory of its own and simply
194 remove that directory when you do not need that specific version of GCC
195 any longer, and, if shared libraries are installed there as well, no
196 more binaries exist that use them.
199 There are also some @uref{old.html,,old installation instructions},
200 which are mostly obsolete but still contain some information which has
201 not yet been merged into the main part of this manual.
209 @uref{./index.html,,Return to the GCC Installation page}
215 @c ***Prerequisites**************************************************
217 @comment node-name, next, previous, up
218 @node Prerequisites, Downloading the source, , Installing GCC
220 @ifset prerequisiteshtml
222 @chapter Prerequisites
224 @cindex Prerequisites
226 GCC requires that various tools and packages be available for use in the
227 build procedure. Modifying GCC sources requires additional tools
230 @heading Tools/packages necessary for building GCC
232 @item ISO C90 compiler
233 Necessary to bootstrap the GCC package, although versions of GCC prior
234 to 3.4 also allow bootstrapping with a traditional (K&R) C compiler.
236 To make all languages in a cross-compiler or other configuration where
237 3-stage bootstrap is not performed, you need to start with an existing
238 GCC binary (version 2.95 or later) because source code for language
239 frontends other than C might use GCC extensions.
243 In order to build the Ada compiler (GNAT) you must already have GNAT
244 installed because portions of the Ada frontend are written in Ada (with
245 GNAT extensions.) Refer to the Ada installation instructions for more
246 specific information.
248 @item A ``working'' POSIX compatible shell, or GNU bash
250 Necessary when running @command{configure} because some
251 @command{/bin/sh} shells have bugs and may crash when configuring the
252 target libraries. In other cases, @command{/bin/sh} or even some
253 @command{ksh} have disastrous corner-case performance problems. This
254 can cause target @command{configure} runs to literally take days to
255 complete in some cases.
257 So on some platforms @command{/bin/ksh} is sufficient, on others it
258 isn't. See the host/target specific instructions for your platform, or
259 use @command{bash} to be sure. Then set @env{CONFIG_SHELL} in your
260 environment to your ``good'' shell prior to running
261 @command{configure}/@command{make}.
263 @command{zsh} is not a fully compliant POSIX shell and will not
264 work when configuring GCC@.
268 Necessary in some circumstances, optional in others. See the
269 host/target specific instructions for your platform for the exact
272 @item gzip version 1.2.4 (or later) or
273 @itemx bzip2 version 1.0.2 (or later)
275 Necessary to uncompress GCC @command{tar} files when source code is
276 obtained via FTP mirror sites.
278 @item GNU make version 3.79.1 (or later)
280 You must have GNU make installed to build GCC@.
282 @item GNU tar version 1.12 (or later)
284 Necessary (only on some platforms) to untar the source code. Many
285 systems' @command{tar} programs will also work, only try GNU
286 @command{tar} if you have problems.
288 @item GNU Multiple Precision Library (GMP) version 4.0 (or later)
290 Necessary to build the Fortran frontend. If you don't have it
291 installed in your library search path, you will have to configure with
292 the @option{--with-gmp} or @option{--with-gmp-dir} configure option.
296 Necessary to build the Fortran frontend. It can be downloaded from
297 @uref{http://www.mpfr.org/}. It is also included in the current GMP
298 release (4.1.3) when configured with @option{--enable-mpfr}.
300 The @option{--with-mpfr} or @option{--with-mpfr-dir} configure option should
301 be used if your MPFR Library is not installed in your library search path.
306 @heading Tools/packages necessary for modifying GCC
308 @item autoconf versions 2.13 and 2.59
309 @itemx GNU m4 version 1.4 (or later)
311 Necessary when modifying @file{configure.ac}, @file{aclocal.m4}, etc.@:
312 to regenerate @file{configure} and @file{config.in} files. Most
313 directories require autoconf 2.59 (exactly), but the toplevel
314 still requires autoconf 2.13 (exactly).
316 @item automake versions 1.9.3
318 Necessary when modifying a @file{Makefile.am} file to regenerate its
319 associated @file{Makefile.in}.
321 Much of GCC does not use automake, so directly edit the @file{Makefile.in}
322 file. Specifically this applies to the @file{gcc}, @file{intl},
323 @file{libcpp}, @file{libiberty}, @file{libobjc} directories as well
324 as any of their subdirectories.
326 For directories that use automake, GCC requires the latest release in
327 the 1.9.x series, which is currently 1.9.3. When regenerating a directory
328 to a newer version, please update all the directories using an older 1.9.x
329 to the latest released version.
331 @item gettext version 0.14.5 (or later)
333 Needed to regenerate @file{gcc.pot}.
335 @item gperf version 2.7.2 (or later)
337 Necessary when modifying @command{gperf} input files, e.g.@:
338 @file{gcc/cp/cfns.gperf} to regenerate its associated header file, e.g.@:
339 @file{gcc/cp/cfns.h}.
341 @item expect version ???
342 @itemx tcl version ???
343 @itemx dejagnu version 1.4.4 (or later)
345 Necessary to run the GCC testsuite.
347 @item autogen version 5.5.4 (or later) and
348 @itemx guile version 1.4.1 (or later)
350 Necessary to regenerate @file{fixinc/fixincl.x} from
351 @file{fixinc/inclhack.def} and @file{fixinc/*.tpl}.
353 Necessary to run the @file{fixinc} @command{make check}.
355 Necessary to regenerate the top level @file{Makefile.in} file from
356 @file{Makefile.tpl} and @file{Makefile.def}.
358 @item GNU Bison version 1.28 (or later)
359 Berkeley @command{yacc} (@command{byacc}) is also reported to work other
362 Necessary when modifying @file{*.y} files.
364 Necessary to build GCC during development because the generated output
365 files are not included in the CVS repository. They are included in
368 @item Flex version 2.5.4 (or later)
370 Necessary when modifying @file{*.l} files.
372 Necessary to build GCC during development because the generated output
373 files are not included in the CVS repository. They are included in
376 @item Texinfo version 4.4 (or later)
378 Necessary for running @command{makeinfo} when modifying @file{*.texi}
379 files to test your changes.
381 Necessary to build GCC documentation during development because the
382 generated output files are not included in the CVS repository. They are
383 included in releases.
385 @item @TeX{} (any working version)
387 Necessary for running @command{texi2dvi}, used when running
388 @command{make dvi} to create DVI files.
390 @item cvs version 1.10 (or later)
391 @itemx ssh (any version)
393 Necessary to access the CVS repository. Public releases and weekly
394 snapshots of the development sources are also available via FTP@.
396 @item perl version 5.6.1 (or later)
398 Necessary when regenerating @file{Makefile} dependencies in libiberty.
399 Necessary when regenerating @file{libiberty/functions.texi}.
400 Necessary when generating manpages from Texinfo manuals.
401 Necessary when targetting Darwin, building libstdc++,
402 and not using @option{--disable-symvers}.
403 Used by various scripts to generate some files included in CVS (mainly
404 Unicode-related and rarely changing) from source tables.
406 @item GNU diffutils version 2.7 (or later)
408 Necessary when creating changes to GCC source code to submit for review.
410 @item patch version 2.5.4 (or later)
412 Necessary when applying patches, created with @command{diff}, to one's
422 @uref{./index.html,,Return to the GCC Installation page}
426 @c ***Downloading the source**************************************************
428 @comment node-name, next, previous, up
429 @node Downloading the source, Configuration, Prerequisites, Installing GCC
433 @chapter Downloading GCC
435 @cindex Downloading GCC
436 @cindex Downloading the Source
438 GCC is distributed via @uref{http://gcc.gnu.org/cvs.html,,CVS} and FTP
439 tarballs compressed with @command{gzip} or
440 @command{bzip2}. It is possible to download a full distribution or specific
443 Please refer to the @uref{http://gcc.gnu.org/releases.html,,releases web page}
444 for information on how to obtain GCC@.
446 The full distribution includes the C, C++, Objective-C, Fortran 77, Fortran
447 (in case of GCC 4.0 and later), Java, and Ada (in case of GCC 3.1 and later)
448 compilers. The full distribution also includes runtime libraries for C++,
449 Objective-C, Fortran 77, Fortran, and Java. In GCC 3.0 and later versions,
450 GNU compiler testsuites are also included in the full distribution.
452 If you choose to download specific components, you must download the core
453 GCC distribution plus any language specific distributions you wish to
454 use. The core distribution includes the C language front end as well as the
455 shared components. Each language has a tarball which includes the language
456 front end as well as the language runtime (when appropriate).
458 Unpack the core distribution as well as any language specific
459 distributions in the same directory.
461 If you also intend to build binutils (either to upgrade an existing
462 installation or for use in place of the corresponding tools of your
463 OS), unpack the binutils distribution either in the same directory or
464 a separate one. In the latter case, add symbolic links to any
465 components of the binutils you intend to build alongside the compiler
466 (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
467 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
474 @uref{./index.html,,Return to the GCC Installation page}
478 @c ***Configuration***********************************************************
480 @comment node-name, next, previous, up
481 @node Configuration, Building, Downloading the source, Installing GCC
485 @chapter Installing GCC: Configuration
487 @cindex Configuration
488 @cindex Installing GCC: Configuration
490 Like most GNU software, GCC must be configured before it can be built.
491 This document describes the recommended configuration procedure
492 for both native and cross targets.
494 We use @var{srcdir} to refer to the toplevel source directory for
495 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
497 If you obtained the sources via CVS, @var{srcdir} must refer to the top
498 @file{gcc} directory, the one where the @file{MAINTAINERS} can be found,
499 and not its @file{gcc} subdirectory, otherwise the build will fail.
501 If either @var{srcdir} or @var{objdir} is located on an automounted NFS
502 file system, the shell's built-in @command{pwd} command will return
503 temporary pathnames. Using these can lead to various sorts of build
504 problems. To avoid this issue, set the @env{PWDCMD} environment
505 variable to an automounter-aware @command{pwd} command, e.g.,
506 @command{pawd} or @samp{amq -w}, during the configuration and build
509 First, we @strong{highly} recommend that GCC be built into a
510 separate directory than the sources which does @strong{not} reside
511 within the source tree. This is how we generally build GCC; building
512 where @var{srcdir} == @var{objdir} should still work, but doesn't
513 get extensive testing; building where @var{objdir} is a subdirectory
514 of @var{srcdir} is unsupported.
516 If you have previously built GCC in the same directory for a
517 different target machine, do @samp{make distclean} to delete all files
518 that might be invalid. One of the files this deletes is @file{Makefile};
519 if @samp{make distclean} complains that @file{Makefile} does not exist
520 or issues a message like ``don't know how to make distclean'' it probably
521 means that the directory is already suitably clean. However, with the
522 recommended method of building in a separate @var{objdir}, you should
523 simply use a different @var{objdir} for each target.
525 Second, when configuring a native system, either @command{cc} or
526 @command{gcc} must be in your path or you must set @env{CC} in
527 your environment before running configure. Otherwise the configuration
531 Note that the bootstrap compiler and the resulting GCC must be link
532 compatible, else the bootstrap will fail with linker errors about
533 incompatible object file formats. Several multilibed targets are
534 affected by this requirement, see
536 @ref{Specific, host/target specific installation notes}.
539 @uref{specific.html,,host/target specific installation notes}.
548 % @var{srcdir}/configure [@var{options}] [@var{target}]
552 @heading Target specification
555 GCC has code to correctly determine the correct value for @var{target}
556 for nearly all native systems. Therefore, we highly recommend you not
557 provide a configure target when configuring a native compiler.
560 @var{target} must be specified as @option{--target=@var{target}}
561 when configuring a cross compiler; examples of valid targets would be
562 m68k-coff, sh-elf, etc.
565 Specifying just @var{target} instead of @option{--target=@var{target}}
566 implies that the host defaults to @var{target}.
570 @heading Options specification
572 Use @var{options} to override several configure time options for
573 GCC@. A list of supported @var{options} follows; @samp{configure
574 --help} may list other options, but those not listed below may not
575 work and should not normally be used.
577 Note that each @option{--enable} option has a corresponding
578 @option{--disable} option and that each @option{--with} option has a
579 corresponding @option{--without} option.
582 @item --prefix=@var{dirname}
583 Specify the toplevel installation
584 directory. This is the recommended way to install the tools into a directory
585 other than the default. The toplevel installation directory defaults to
588 We @strong{highly} recommend against @var{dirname} being the same or a
589 subdirectory of @var{objdir} or vice versa. If specifying a directory
590 beneath a user's home directory tree, some shells will not expand
591 @var{dirname} correctly if it contains the @samp{~} metacharacter; use
594 The following standard @command{autoconf} options are supported. Normally you
595 should not need to use these options.
597 @item --exec-prefix=@var{dirname}
598 Specify the toplevel installation directory for architecture-dependent
599 files. The default is @file{@var{prefix}}.
601 @item --bindir=@var{dirname}
602 Specify the installation directory for the executables called by users
603 (such as @command{gcc} and @command{g++}). The default is
604 @file{@var{exec-prefix}/bin}.
606 @item --libdir=@var{dirname}
607 Specify the installation directory for object code libraries and
608 internal data files of GCC@. The default is @file{@var{exec-prefix}/lib}.
610 @item --libexecdir=@var{dirname}
611 Specify the installation directory for internal executables of GCC@.
612 The default is @file{@var{exec-prefix}/libexec}.
614 @item --with-slibdir=@var{dirname}
615 Specify the installation directory for the shared libgcc library. The
616 default is @file{@var{libdir}}.
618 @item --infodir=@var{dirname}
619 Specify the installation directory for documentation in info format.
620 The default is @file{@var{prefix}/info}.
622 @item --datadir=@var{dirname}
623 Specify the installation directory for some architecture-independent
624 data files referenced by GCC@. The default is @file{@var{prefix}/share}.
626 @item --mandir=@var{dirname}
627 Specify the installation directory for manual pages. The default is
628 @file{@var{prefix}/man}. (Note that the manual pages are only extracts from
629 the full GCC manuals, which are provided in Texinfo format. The manpages
630 are derived by an automatic conversion process from parts of the full
633 @item --with-gxx-include-dir=@var{dirname}
635 the installation directory for G++ header files. The default is
636 @file{@var{prefix}/include/c++/@var{version}}.
640 @item --program-prefix=@var{prefix}
641 GCC supports some transformations of the names of its programs when
642 installing them. This option prepends @var{prefix} to the names of
643 programs to install in @var{bindir} (see above). For example, specifying
644 @option{--program-prefix=foo-} would result in @samp{gcc}
645 being installed as @file{/usr/local/bin/foo-gcc}.
647 @item --program-suffix=@var{suffix}
648 Appends @var{suffix} to the names of programs to install in @var{bindir}
649 (see above). For example, specifying @option{--program-suffix=-3.1}
650 would result in @samp{gcc} being installed as
651 @file{/usr/local/bin/gcc-3.1}.
653 @item --program-transform-name=@var{pattern}
654 Applies the @samp{sed} script @var{pattern} to be applied to the names
655 of programs to install in @var{bindir} (see above). @var{pattern} has to
656 consist of one or more basic @samp{sed} editing commands, separated by
657 semicolons. For example, if you want the @samp{gcc} program name to be
658 transformed to the installed program @file{/usr/local/bin/myowngcc} and
659 the @samp{g++} program name to be transformed to
660 @file{/usr/local/bin/gspecial++} without changing other program names,
661 you could use the pattern
662 @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}
663 to achieve this effect.
665 All three options can be combined and used together, resulting in more
666 complex conversion patterns. As a basic rule, @var{prefix} (and
667 @var{suffix}) are prepended (appended) before further transformations
668 can happen with a special transformation script @var{pattern}.
670 As currently implemented, this option only takes effect for native
671 builds; cross compiler binaries' names are not transformed even when a
672 transformation is explicitly asked for by one of these options.
674 For native builds, some of the installed programs are also installed
675 with the target alias in front of their name, as in
676 @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
677 before the target alias is prepended to the name---so, specifying
678 @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
679 resulting binary would be installed as
680 @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.
682 As a last shortcoming, none of the installed Ada programs are
683 transformed yet, which will be fixed in some time.
685 @item --with-local-prefix=@var{dirname}
687 installation directory for local include files. The default is
688 @file{/usr/local}. Specify this option if you want the compiler to
689 search directory @file{@var{dirname}/include} for locally installed
690 header files @emph{instead} of @file{/usr/local/include}.
692 You should specify @option{--with-local-prefix} @strong{only} if your
693 site has a different convention (not @file{/usr/local}) for where to put
696 The default value for @option{--with-local-prefix} is @file{/usr/local}
697 regardless of the value of @option{--prefix}. Specifying
698 @option{--prefix} has no effect on which directory GCC searches for
699 local header files. This may seem counterintuitive, but actually it is
702 The purpose of @option{--prefix} is to specify where to @emph{install
703 GCC}. The local header files in @file{/usr/local/include}---if you put
704 any in that directory---are not part of GCC@. They are part of other
705 programs---perhaps many others. (GCC installs its own header files in
706 another directory which is based on the @option{--prefix} value.)
708 Both the local-prefix include directory and the GCC-prefix include
709 directory are part of GCC's ``system include'' directories. Although these
710 two directories are not fixed, they need to be searched in the proper
711 order for the correct processing of the include_next directive. The
712 local-prefix include directory is searched before the GCC-prefix
713 include directory. Another characteristic of system include directories
714 is that pedantic warnings are turned off for headers in these directories.
716 Some autoconf macros add @option{-I @var{directory}} options to the
717 compiler command line, to ensure that directories containing installed
718 packages' headers are searched. When @var{directory} is one of GCC's
719 system include directories, GCC will ignore the option so that system
720 directories continue to be processed in the correct order. This
721 may result in a search order different from what was specified but the
722 directory will still be searched.
724 GCC automatically searches for ordinary libraries using
725 @env{GCC_EXEC_PREFIX}. Thus, when the same installation prefix is
726 used for both GCC and packages, GCC will automatically search for
727 both headers and libraries. This provides a configuration that is
728 easy to use. GCC behaves in a manner similar to that when it is
729 installed as a system compiler in @file{/usr}.
731 Sites that need to install multiple versions of GCC may not want to
732 use the above simple configuration. It is possible to use the
733 @option{--program-prefix}, @option{--program-suffix} and
734 @option{--program-transform-name} options to install multiple versions
735 into a single directory, but it may be simpler to use different prefixes
736 and the @option{--with-local-prefix} option to specify the location of the
737 site-specific files for each version. It will then be necessary for
738 users to specify explicitly the location of local site libraries
739 (e.g., with @env{LIBRARY_PATH}).
741 The same value can be used for both @option{--with-local-prefix} and
742 @option{--prefix} provided it is not @file{/usr}. This can be used
743 to avoid the default search of @file{/usr/local/include}.
745 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
746 The directory you use for @option{--with-local-prefix} @strong{must not}
747 contain any of the system's standard header files. If it did contain
748 them, certain programs would be miscompiled (including GNU Emacs, on
749 certain targets), because this would override and nullify the header
750 file corrections made by the @command{fixincludes} script.
752 Indications are that people who use this option use it based on mistaken
753 ideas of what it is for. People use it as if it specified where to
754 install part of GCC@. Perhaps they make this assumption because
755 installing GCC creates the directory.
757 @item --enable-shared[=@var{package}[,@dots{}]]
758 Build shared versions of libraries, if shared libraries are supported on
759 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
760 are enabled by default on all platforms that support shared libraries.
762 If a list of packages is given as an argument, build shared libraries
763 only for the listed packages. For other packages, only static libraries
764 will be built. Package names currently recognized in the GCC tree are
765 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
766 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc},
767 @samp{ada}, @samp{libada}, @samp{libjava} and @samp{libobjc}.
768 Note @samp{libiberty} does not support shared libraries at all.
770 Use @option{--disable-shared} to build only static libraries. Note that
771 @option{--disable-shared} does not accept a list of package names as
772 argument, only @option{--enable-shared} does.
774 @item @anchor{with-gnu-as}--with-gnu-as
775 Specify that the compiler should assume that the
776 assembler it finds is the GNU assembler. However, this does not modify
777 the rules to find an assembler and will result in confusion if the
778 assembler found is not actually the GNU assembler. (Confusion may also
779 result if the compiler finds the GNU assembler but has not been
780 configured with @option{--with-gnu-as}.) If you have more than one
781 assembler installed on your system, you may want to use this option in
782 connection with @option{--with-as=@var{pathname}} or
783 @option{--with-build-time-tools=@var{pathname}}.
785 The following systems are the only ones where it makes a difference
786 whether you use the GNU assembler. On any other system,
787 @option{--with-gnu-as} has no effect.
790 @item @samp{hppa1.0-@var{any}-@var{any}}
791 @item @samp{hppa1.1-@var{any}-@var{any}}
792 @item @samp{i386-@var{any}-sysv}
793 @item @samp{m68k-bull-sysv}
794 @item @samp{m68k-hp-hpux}
795 @item @samp{m68000-hp-hpux}
796 @item @samp{m68000-att-sysv}
797 @item @samp{sparc-sun-solaris2.@var{any}}
798 @item @samp{sparc64-@var{any}-solaris2.@var{any}}
801 On the systems listed above (except for the HP-PA, the SPARC, for ISC on
802 the 386, if you use the GNU assembler, you should also use the GNU linker
803 (and specify @option{--with-gnu-ld}).
805 @item @anchor{with-as}--with-as=@var{pathname}
806 Specify that the compiler should use the assembler pointed to by
807 @var{pathname}, rather than the one found by the standard rules to find
808 an assembler, which are:
811 Unless GCC is being built with a cross compiler, check the
812 @file{@var{libexec}/gcc/@var{target}/@var{version}} directory.
813 @var{libexec} defaults to @file{@var{exec-prefix}/libexec};
814 @var{exec-prefix} defaults to @var{prefix}, which
815 defaults to @file{/usr/local} unless overridden by the
816 @option{--prefix=@var{pathname}} switch described above. @var{target}
817 is the target system triple, such as @samp{sparc-sun-solaris2.7}, and
818 @var{version} denotes the GCC version, such as 3.0.
821 If the target system is the same that you are building on, check
822 operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
826 Check in the @env{PATH} for a tool whose name is prefixed by the
827 target system triple.
830 Check in the @env{PATH} for a tool whose name is not prefixed by the
831 target system triple, if the host and target system triple are
832 the same (in other words, we use a host tool if it can be used for
836 You may want to use @option{--with-as} if no assembler
837 is installed in the directories listed above, or if you have multiple
838 assemblers installed and want to choose one that is not found by the
841 @item @anchor{with-gnu-ld}--with-gnu-ld
842 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
845 @item --with-ld=@var{pathname}
846 Same as @uref{#with-as,,@option{--with-as}}
850 Specify that stabs debugging
851 information should be used instead of whatever format the host normally
852 uses. Normally GCC uses the same debug format as the host system.
854 On MIPS based systems and on Alphas, you must specify whether you want
855 GCC to create the normal ECOFF debugging format, or to use BSD-style
856 stabs passed through the ECOFF symbol table. The normal ECOFF debug
857 format cannot fully handle languages other than C@. BSD stabs format can
858 handle other languages, but it only works with the GNU debugger GDB@.
860 Normally, GCC uses the ECOFF debugging format by default; if you
861 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
863 No matter which default you choose when you configure GCC, the user
864 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
865 the debug format for a particular compilation.
867 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
868 @option{--with-gas} is used. It selects use of stabs debugging
869 information embedded in COFF output. This kind of debugging information
870 supports C++ well; ordinary COFF debugging information does not.
872 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
873 selects use of stabs debugging information embedded in ELF output. The
874 C++ compiler currently (2.6.0) does not support the DWARF debugging
875 information normally used on 386 SVR4 platforms; stabs provide a
876 workable alternative. This requires gas and gdb, as the normal SVR4
877 tools can not generate or interpret stabs.
879 @item --disable-multilib
880 Specify that multiple target
881 libraries to support different target variants, calling
882 conventions, etc should not be built. The default is to build a
883 predefined set of them.
885 Some targets provide finer-grained control over which multilibs are built
886 (e.g., @option{--disable-softfloat}):
892 fpu, 26bit, underscore, interwork, biendian, nofmult.
895 softfloat, m68881, m68000, m68020.
898 single-float, biendian, softfloat.
900 @item powerpc*-*-*, rs6000*-*-*
901 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
906 @item --enable-threads
907 Specify that the target
908 supports threads. This affects the Objective-C compiler and runtime
909 library, and exception handling for other languages like C++ and Java.
910 On some systems, this is the default.
912 In general, the best (and, in many cases, the only known) threading
913 model available will be configured for use. Beware that on some
914 systems, GCC has not been taught what threading models are generally
915 available for the system. In this case, @option{--enable-threads} is an
916 alias for @option{--enable-threads=single}.
918 @item --disable-threads
919 Specify that threading support should be disabled for the system.
920 This is an alias for @option{--enable-threads=single}.
922 @item --enable-threads=@var{lib}
924 @var{lib} is the thread support library. This affects the Objective-C
925 compiler and runtime library, and exception handling for other languages
926 like C++ and Java. The possibilities for @var{lib} are:
934 Ada tasking support. For non-Ada programs, this setting is equivalent
935 to @samp{single}. When used in conjunction with the Ada run time, it
936 causes GCC to use the same thread primitives as Ada uses. This option
937 is necessary when using both Ada and the back end exception handling,
938 which is the default for most Ada targets.
940 Generic MACH thread support, known to work on NeXTSTEP@. (Please note
941 that the file needed to support this configuration, @file{gthr-mach.h}, is
942 missing and thus this setting will cause a known bootstrap failure.)
944 This is an alias for @samp{single}.
946 Generic POSIX/Unix98 thread support.
948 Generic POSIX/Unix95 thread support.
950 RTEMS thread support.
952 Disable thread support, should work for all platforms.
954 Sun Solaris 2 thread support.
956 VxWorks thread support.
958 Microsoft Win32 API thread support.
960 Novell Kernel Services thread support.
964 Specify that the target supports TLS (Thread Local Storage). Usually
965 configure can correctly determine if TLS is supported. In cases where
966 it guesses incorrectly, TLS can be explicitly enabled or disabled with
967 @option{--enable-tls} or @option{--disable-tls}. This can happen if
968 the assembler supports TLS but the C library does not, or if the
969 assumptions made by the configure test are incorrect.
972 Specify that the target does not support TLS.
973 This is an alias for @option{--enable-tls=no}.
975 @item --with-cpu=@var{cpu}
976 Specify which cpu variant the compiler should generate code for by default.
977 @var{cpu} will be used as the default value of the @option{-mcpu=} switch.
978 This option is only supported on some targets, including ARM, i386, PowerPC,
981 @item --with-schedule=@var{cpu}
982 @itemx --with-arch=@var{cpu}
983 @itemx --with-tune=@var{cpu}
984 @itemx --with-abi=@var{abi}
985 @itemx --with-fpu=@var{type}
986 @itemx --with-float=@var{type}
987 These configure options provide default values for the @option{-mschedule=},
988 @option{-march=}, @option{-mtune=}, @option{-mabi=}, and @option{-mfpu=}
989 options and for @option{-mhard-float} or @option{-msoft-float}. As with
990 @option{--with-cpu}, which switches will be accepted and acceptable values
991 of the arguments depend on the target.
993 @item --with-divide=@var{type}
994 Specify how the compiler should generate code for checking for
995 division by zero. This option is only supported on the MIPS target.
996 The possibilities for @var{type} are:
999 Division by zero checks use conditional traps (this is the default on
1000 systems that support conditional traps).
1002 Division by zero checks use the break instruction.
1005 @item --enable-__cxa_atexit
1006 Define if you want to use __cxa_atexit, rather than atexit, to
1007 register C++ destructors for local statics and global objects.
1008 This is essential for fully standards-compliant handling of
1009 destructors, but requires __cxa_atexit in libc. This option is currently
1010 only available on systems with GNU libc. When enabled, this will cause
1011 @option{-fuse-cxa-exit} to be passed by default.
1013 @item --enable-target-optspace
1015 libraries should be optimized for code space instead of code speed.
1016 This is the default for the m32r platform.
1019 Specify that a user visible @command{cpp} program should not be installed.
1021 @item --with-cpp-install-dir=@var{dirname}
1022 Specify that the user visible @command{cpp} program should be installed
1023 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
1025 @item --enable-initfini-array
1026 Force the use of sections @code{.init_array} and @code{.fini_array}
1027 (instead of @code{.init} and @code{.fini}) for constructors and
1028 destructors. Option @option{--disable-initfini-array} has the
1029 opposite effect. If neither option is specified, the configure script
1030 will try to guess whether the @code{.init_array} and
1031 @code{.fini_array} sections are supported and, if they are, use them.
1033 @item --enable-maintainer-mode
1034 The build rules that
1035 regenerate the GCC master message catalog @file{gcc.pot} are normally
1036 disabled. This is because it can only be rebuilt if the complete source
1037 tree is present. If you have changed the sources and want to rebuild the
1038 catalog, configuring with @option{--enable-maintainer-mode} will enable
1039 this. Note that you need a recent version of the @code{gettext} tools
1042 @item --enable-generated-files-in-srcdir
1043 Neither the .c and .h files that are generated from bison and flex nor the
1044 info manuals and man pages that are built from the .texi files are present
1045 in the CVS development tree. When building GCC from that development tree,
1046 or from a snapshot which are created from CVS, then those generated files
1047 are placed in your build directory, which allows for the source to be in a
1050 If you configure with @option{--enable-generated-files-in-srcdir} then those
1051 generated files will go into the source directory. This is mainly intended
1052 for generating release or prerelease tarballs of the GCC sources, since it
1053 is not a requirement that the users of source releases to have flex, bison, or
1056 @item --enable-version-specific-runtime-libs
1058 that runtime libraries should be installed in the compiler specific
1059 subdirectory (@file{@var{libdir}/gcc}) rather than the usual places. In
1060 addition, @samp{libstdc++}'s include files will be installed into
1061 @file{@var{libdir}} unless you overruled it by using
1062 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
1063 particularly useful if you intend to use several versions of GCC in
1064 parallel. This is currently supported by @samp{libgfortran},
1065 @samp{libjava}, @samp{libmudflap}, @samp{libstdc++}, and @samp{libobjc}.
1067 @item --with-java-home=@var{dirname}
1068 This @samp{libjava} option overrides the default value of the
1069 @samp{java.home} system property. It is also used to set
1070 @samp{sun.boot.class.path} to @file{@var{dirname}/lib/rt.jar}. By
1071 default @samp{java.home} is set to @file{@var{prefix}} and
1072 @samp{sun.boot.class.path} to
1073 @file{@var{datadir}/java/libgcj-@var{version}.jar}.
1075 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
1076 Specify that only a particular subset of compilers and
1077 their runtime libraries should be built. For a list of valid values for
1078 @var{langN} you can issue the following command in the
1079 @file{gcc} directory of your GCC source tree:@*
1081 grep language= */config-lang.in
1083 Currently, you can use any of the following:
1084 @code{all}, @code{ada}, @code{c}, @code{c++}, @code{fortran}, @code{java},
1085 @code{objc}, @code{obj-c++}, @code{treelang}.
1086 Building the Ada compiler has special requirements, see below.
1087 If you do not pass this flag, or specify the option @code{all}, then all
1088 default languages available in the @file{gcc} sub-tree will be configured.
1089 Ada, Objective-C++, and treelang are not default languages; the rest are.
1090 Re-defining @code{LANGUAGES} when calling @samp{make} @strong{does not}
1091 work anymore, as those language sub-directories might not have been
1094 @item --disable-libada
1095 Specify that the run-time libraries and tools used by GNAT should not
1096 be built. This can be useful for debugging, or for compatibility with
1097 previous Ada build procedures, when it was required to explicitly
1098 do a @samp{make -C gcc gnatlib_and_tools}.
1100 @item --disable-libssp
1101 Specify that the run-time libraries for stack smashing protection
1102 should not be built.
1104 @item --disable-libgcc-math
1105 Specify that the run-time libraries for arch and gcc specific math
1106 functions should not be built.
1108 @item --disable-libgomp
1109 Specify that the run-time libraries used by GOMP should not be built.
1112 Specify that the compiler should
1113 use DWARF 2 debugging information as the default.
1115 @item --enable-targets=all
1116 @itemx --enable-targets=@var{target_list}
1117 Some GCC targets, e.g.@: powerpc64-linux, build bi-arch compilers.
1118 These are compilers that are able to generate either 64-bit or 32-bit
1119 code. Typically, the corresponding 32-bit target, e.g.@:
1120 powerpc-linux for powerpc64-linux, only generates 32-bit code. This
1121 option enables the 32-bit target to be a bi-arch compiler, which is
1122 useful when you want a bi-arch compiler that defaults to 32-bit, and
1123 you are building a bi-arch or multi-arch binutils in a combined tree.
1124 Currently, this option only affects powerpc-linux.
1126 @item --enable-secureplt
1127 This option enables @option{-msecure-plt} by default for powerpc-linux.
1129 @xref{RS/6000 and PowerPC Options,, RS/6000 and PowerPC Options, gcc,
1130 Using the GNU Compiler Collection (GCC)},
1133 See ``RS/6000 and PowerPC Options'' in the main manual
1136 @item --enable-win32-registry
1137 @itemx --enable-win32-registry=@var{key}
1138 @itemx --disable-win32-registry
1139 The @option{--enable-win32-registry} option enables Microsoft Windows-hosted GCC
1140 to look up installations paths in the registry using the following key:
1143 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
1146 @var{key} defaults to GCC version number, and can be overridden by the
1147 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
1148 who use custom installers are encouraged to provide a different key,
1149 perhaps one comprised of vendor name and GCC version number, to
1150 avoid conflict with existing installations. This feature is enabled
1151 by default, and can be disabled by @option{--disable-win32-registry}
1152 option. This option has no effect on the other hosts.
1155 Specify that the machine does not have a floating point unit. This
1156 option only applies to @samp{m68k-sun-sunos@var{n}}. On any other
1157 system, @option{--nfp} has no effect.
1159 @item --enable-werror
1160 @itemx --disable-werror
1161 @itemx --enable-werror=yes
1162 @itemx --enable-werror=no
1163 When you specify this option, it controls whether certain files in the
1164 compiler are built with @option{-Werror} in bootstrap stage2 and later.
1165 If you don't specify it, @option{-Werror} is turned on for the main
1166 development trunk. However it defaults to off for release branches and
1167 final releases. The specific files which get @option{-Werror} are
1168 controlled by the Makefiles.
1170 @item --enable-checking
1171 @itemx --enable-checking=@var{list}
1172 When you specify this option, the compiler is built to perform internal
1173 consistency checks of the requested complexity. This does not change the
1174 generated code, but adds error checking within the compiler. This will
1175 slow down the compiler and may only work properly if you are building
1176 the compiler with GCC@. This is @samp{yes} by default when building
1177 from CVS or snapshots, but @samp{release} for releases. More control
1178 over the checks may be had by specifying @var{list}. The categories of
1179 checks available are @samp{yes} (most common checks
1180 @samp{assert,misc,tree,gc,rtlflag,runtime}), @samp{no} (no checks at
1181 all), @samp{all} (all but @samp{valgrind}), @samp{release} (cheapest
1182 checks @samp{assert,runtime}) or @samp{none} (same as @samp{no}).
1183 Individual checks can be enabled with these flags @samp{assert},
1184 @samp{fold}, @samp{gc}, @samp{gcac} @samp{misc}, @samp{rtl},
1185 @samp{rtlflag}, @samp{runtime}, @samp{tree}, and @samp{valgrind}.
1187 The @samp{valgrind} check requires the external @command{valgrind}
1188 simulator, available from @uref{http://valgrind.org/}. The
1189 @samp{rtl}, @samp{gcac} and @samp{valgrind} checks are very expensive.
1190 To disable all checking, @samp{--disable-checking} or
1191 @samp{--enable-checking=none} must be explicitly requested. Disabling
1192 assertions will make the compiler and runtime slightly faster but
1193 increase the risk of undetected internal errors causing wrong code to be
1196 @item --enable-coverage
1197 @itemx --enable-coverage=@var{level}
1198 With this option, the compiler is built to collect self coverage
1199 information, every time it is run. This is for internal development
1200 purposes, and only works when the compiler is being built with gcc. The
1201 @var{level} argument controls whether the compiler is built optimized or
1202 not, values are @samp{opt} and @samp{noopt}. For coverage analysis you
1203 want to disable optimization, for performance analysis you want to
1204 enable optimization. When coverage is enabled, the default level is
1205 without optimization.
1207 @item --enable-gather-detailed-mem-stats
1208 When this option is specified more detailed information on memory
1209 allocation is gathered. This information is printed when using
1210 @option{-fmem-report}.
1213 @itemx --with-gc=@var{choice}
1214 With this option you can specify the garbage collector implementation
1215 used during the compilation process. @var{choice} can be one of
1216 @samp{page} and @samp{zone}, where @samp{page} is the default.
1219 @itemx --disable-nls
1220 The @option{--enable-nls} option enables Native Language Support (NLS),
1221 which lets GCC output diagnostics in languages other than American
1222 English. Native Language Support is enabled by default if not doing a
1223 canadian cross build. The @option{--disable-nls} option disables NLS@.
1225 @item --with-included-gettext
1226 If NLS is enabled, the @option{--with-included-gettext} option causes the build
1227 procedure to prefer its copy of GNU @command{gettext}.
1229 @item --with-catgets
1230 If NLS is enabled, and if the host lacks @code{gettext} but has the
1231 inferior @code{catgets} interface, the GCC build procedure normally
1232 ignores @code{catgets} and instead uses GCC's copy of the GNU
1233 @code{gettext} library. The @option{--with-catgets} option causes the
1234 build procedure to use the host's @code{catgets} in this situation.
1236 @item --with-libiconv-prefix=@var{dir}
1237 Search for libiconv header files in @file{@var{dir}/include} and
1238 libiconv library files in @file{@var{dir}/lib}.
1240 @item --enable-obsolete
1241 Enable configuration for an obsoleted system. If you attempt to
1242 configure GCC for a system (build, host, or target) which has been
1243 obsoleted, and you do not specify this flag, configure will halt with an
1246 All support for systems which have been obsoleted in one release of GCC
1247 is removed entirely in the next major release, unless someone steps
1248 forward to maintain the port.
1250 @item --enable-decimal-float
1251 @itemx --disable-decimal-float
1252 Enable (or disable) support for the C decimal floating point
1253 extension. This is enabled by default only on PowerPC GNU/Linux
1254 systems. Other systems may also support it, but require the user to
1255 specifically enable it.
1259 @subheading Cross-Compiler-Specific Options
1260 The following options only apply to building cross compilers.
1262 @item --with-sysroot
1263 @itemx --with-sysroot=@var{dir}
1264 Tells GCC to consider @var{dir} as the root of a tree that contains a
1265 (subset of) the root filesystem of the target operating system.
1266 Target system headers, libraries and run-time object files will be
1267 searched in there. The specified directory is not copied into the
1268 install tree, unlike the options @option{--with-headers} and
1269 @option{--with-libs} that this option obsoletes. The default value,
1270 in case @option{--with-sysroot} is not given an argument, is
1271 @option{$@{gcc_tooldir@}/sys-root}. If the specified directory is a
1272 subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to
1273 the GCC binaries if the installation tree is moved.
1275 @item --with-build-sysroot
1276 @itemx --with-build-sysroot=@var{dir}
1277 Tells GCC to consider @var{dir} as the system root (see
1278 @option{--with-sysroot}) while building target libraries, instead of
1279 the directory specified with @option{--with-sysroot}. This option is
1280 only useful when you are already using @option{--with-sysroot}. You
1281 can use @option{--with-build-sysroot} when you are configuring with
1282 @option{--prefix} set to a directory that is different from the one in
1283 which you are installing GCC and your target libraries.
1285 This option affects the system root for the compiler used to build
1286 target libraries (which runs on the build system); it does not affect
1287 the compiler which is used to build GCC itself.
1289 @item --with-headers
1290 @itemx --with-headers=@var{dir}
1291 Deprecated in favor of @option{--with-sysroot}.
1292 Specifies that target headers are available when building a cross compiler.
1293 The @var{dir} argument specifies a directory which has the target include
1294 files. These include files will be copied into the @file{gcc} install
1295 directory. @emph{This option with the @var{dir} argument is required} when
1296 building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include}
1297 doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does
1298 pre-exist, the @var{dir} argument may be omitted. @command{fixincludes}
1299 will be run on these files to make them compatible with GCC@.
1301 @item --without-headers
1302 Tells GCC not use any target headers from a libc when building a cross
1303 compiler. When crossing to GNU/Linux, you need the headers so GCC
1304 can build the exception handling for libgcc.
1305 See @uref{http://www.objsw.com/CrossGCC/,,CrossGCC} for more information
1309 @itemx --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
1310 Deprecated in favor of @option{--with-sysroot}.
1311 Specifies a list of directories which contain the target runtime
1312 libraries. These libraries will be copied into the @file{gcc} install
1313 directory. If the directory list is omitted, this option has no
1317 Specifies that @samp{newlib} is
1318 being used as the target C library. This causes @code{__eprintf} to be
1319 omitted from @file{libgcc.a} on the assumption that it will be provided by
1322 @item --with-build-time-tools=@var{dir}
1323 Specifies where to find the set of target tools (assembler, linker, etc.)
1324 that will be used while building GCC itself. This option can be useful
1325 if the directory layouts are different between the system you are building
1326 GCC on, and the system where you will deploy it.
1328 For example, on a @option{ia64-hp-hpux} system, you may have the GNU
1329 assembler and linker in @file{/usr/bin}, and the native tools in a
1330 different path, and build a toolchain that expects to find the
1331 native tools in @file{/usr/bin}.
1333 When you use this option, you should ensure that @var{dir} includes
1334 @command{ar}, @command{as}, @command{ld}, @command{nm},
1335 @command{ranlib} and @command{strip} if necessary, and possibly
1336 @command{objdump}. Otherwise, GCC may use an inconsistent set of
1340 @subheading Fortran-Specific Options
1342 The following options apply to the build of the Fortran front end.
1346 @item --with-gmp=@var{pathname}
1347 @itemx --with-mpfr=@var{pathname}
1348 @itemx --with-gmp-dir=@var{pathname}
1349 @itemx --with-mpfr-dir=@var{pathname}
1350 If you don't have GMP (the GNU Multiple Precision library) and the MPFR
1351 Libraries installed in a standard location and you want to build the Fortran
1352 front-end, you can explicitly specify the directory where they are installed
1353 (@samp{--with-gmp=gmpinstalldir}, @samp{--with-mpfr=mpfrinstalldir}) or where
1354 you built them without installing (@samp{--with-gmp-dir=gmpbuilddir},
1355 @samp{--with-mpfr-dir=gmpbuilddir}).
1359 @subheading Java-Specific Options
1361 The following option applies to the build of the Java front end.
1364 @item --disable-libgcj
1365 Specify that the run-time libraries
1366 used by GCJ should not be built. This is useful in case you intend
1367 to use GCJ with some other run-time, or you're going to install it
1368 separately, or it just happens not to build on your particular
1369 machine. In general, if the Java front end is enabled, the GCJ
1370 libraries will be enabled too, unless they're known to not work on
1371 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
1372 may need to port it; in this case, before modifying the top-level
1373 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
1374 you may use @option{--enable-libgcj} to override the default.
1378 The following options apply to building @samp{libgcj}.
1380 @subsubheading General Options
1383 @item --disable-getenv-properties
1384 Don't set system properties from @env{GCJ_PROPERTIES}.
1386 @item --enable-hash-synchronization
1387 Use a global hash table for monitor locks. Ordinarily,
1388 @samp{libgcj}'s @samp{configure} script automatically makes
1389 the correct choice for this option for your platform. Only use
1390 this if you know you need the library to be configured differently.
1392 @item --enable-interpreter
1393 Enable the Java interpreter. The interpreter is automatically
1394 enabled by default on all platforms that support it. This option
1395 is really only useful if you want to disable the interpreter
1396 (using @option{--disable-interpreter}).
1398 @item --disable-java-net
1399 Disable java.net. This disables the native part of java.net only,
1400 using non-functional stubs for native method implementations.
1402 @item --disable-jvmpi
1403 Disable JVMPI support.
1406 Enable runtime eCos target support.
1408 @item --without-libffi
1409 Don't use @samp{libffi}. This will disable the interpreter and JNI
1410 support as well, as these require @samp{libffi} to work.
1412 @item --enable-libgcj-debug
1413 Enable runtime debugging code.
1415 @item --enable-libgcj-multifile
1416 If specified, causes all @file{.java} source files to be
1417 compiled into @file{.class} files in one invocation of
1418 @samp{gcj}. This can speed up build time, but is more
1419 resource-intensive. If this option is unspecified or
1420 disabled, @samp{gcj} is invoked once for each @file{.java}
1421 file to compile into a @file{.class} file.
1423 @item --with-libiconv-prefix=DIR
1424 Search for libiconv in @file{DIR/include} and @file{DIR/lib}.
1426 @item --enable-sjlj-exceptions
1427 Force use of @code{builtin_setjmp} for exceptions. @samp{configure}
1428 ordinarily picks the correct value based on the platform. Only use
1429 this option if you are sure you need a different setting.
1431 @item --with-system-zlib
1432 Use installed @samp{zlib} rather than that included with GCC@.
1434 @item --with-win32-nlsapi=ansi, unicows or unicode
1435 Indicates how MinGW @samp{libgcj} translates between UNICODE
1436 characters and the Win32 API@.
1439 Use the single-byte @code{char} and the Win32 A functions natively,
1440 translating to and from UNICODE when using these functions. If
1441 unspecified, this is the default.
1444 Use the @code{WCHAR} and Win32 W functions natively. Adds
1445 @code{-lunicows} to @file{libgcj.spec} to link with @samp{libunicows}.
1446 @file{unicows.dll} needs to be deployed on Microsoft Windows 9X machines
1447 running built executables. @file{libunicows.a}, an open-source
1448 import library around Microsoft's @code{unicows.dll}, is obtained from
1449 @uref{http://libunicows.sourceforge.net/}, which also gives details
1450 on getting @file{unicows.dll} from Microsoft.
1453 Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not}
1454 add @code{-lunicows} to @file{libgcj.spec}. The built executables will
1455 only run on Microsoft Windows NT and above.
1459 @subsubheading AWT-Specific Options
1463 Use the X Window System.
1465 @item --enable-java-awt=PEER(S)
1466 Specifies the AWT peer library or libraries to build alongside
1467 @samp{libgcj}. If this option is unspecified or disabled, AWT
1468 will be non-functional. Current valid values are @option{gtk} and
1469 @option{xlib}. Multiple libraries should be separated by a
1470 comma (i.e.@: @option{--enable-java-awt=gtk,xlib}).
1472 @item --enable-gtk-cairo
1473 Build the cairo Graphics2D implementation on GTK@.
1475 @item --enable-java-gc=TYPE
1476 Choose garbage collector. Defaults to @option{boehm} if unspecified.
1478 @item --disable-gtktest
1479 Do not try to compile and run a test GTK+ program.
1481 @item --disable-glibtest
1482 Do not try to compile and run a test GLIB program.
1484 @item --with-libart-prefix=PFX
1485 Prefix where libart is installed (optional).
1487 @item --with-libart-exec-prefix=PFX
1488 Exec prefix where libart is installed (optional).
1490 @item --disable-libarttest
1491 Do not try to compile and run a test libart program.
1500 @uref{./index.html,,Return to the GCC Installation page}
1504 @c ***Building****************************************************************
1506 @comment node-name, next, previous, up
1507 @node Building, Testing, Configuration, Installing GCC
1513 @cindex Installing GCC: Building
1515 Now that GCC is configured, you are ready to build the compiler and
1518 Some commands executed when making the compiler may fail (return a
1519 nonzero status) and be ignored by @command{make}. These failures, which
1520 are often due to files that were not found, are expected, and can safely
1523 It is normal to have compiler warnings when compiling certain files.
1524 Unless you are a GCC developer, you can generally ignore these warnings
1525 unless they cause compilation to fail. Developers should attempt to fix
1526 any warnings encountered, however they can temporarily continue past
1527 warnings-as-errors by specifying the configure flag
1528 @option{--disable-werror}.
1530 On certain old systems, defining certain environment variables such as
1531 @env{CC} can interfere with the functioning of @command{make}.
1533 If you encounter seemingly strange errors when trying to build the
1534 compiler in a directory other than the source directory, it could be
1535 because you have previously configured the compiler in the source
1536 directory. Make sure you have done all the necessary preparations.
1538 If you build GCC on a BSD system using a directory stored in an old System
1539 V file system, problems may occur in running @command{fixincludes} if the
1540 System V file system doesn't support symbolic links. These problems
1541 result in a failure to fix the declaration of @code{size_t} in
1542 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
1543 that type mismatches occur, this could be the cause.
1545 The solution is not to use such a directory for building GCC@.
1547 When building from CVS or snapshots, or if you modify parser sources,
1548 you need the Bison parser generator installed. Any version 1.25 or
1549 later should work; older versions may also work. If you do not modify
1550 parser sources, releases contain the Bison-generated files and you do
1551 not need Bison installed to build them.
1553 When building from CVS or snapshots, or if you modify Texinfo
1554 documentation, you need version 4.4 or later of Texinfo installed if you
1555 want Info documentation to be regenerated. Releases contain Info
1556 documentation pre-built for the unmodified documentation in the release.
1558 @section Building a native compiler
1560 For a native build, the command @samp{make} will trigger a 3-stage
1561 bootstrap of the compiler. This will build the entire GCC system
1562 and ensure that it compiles itself correctly, by doing the
1567 Build tools necessary to build the compiler such as texinfo, bison,
1571 Perform a 3-stage bootstrap of the compiler. This includes building
1572 three times the target tools for use by the compiler such as binutils
1573 (bfd, binutils, gas, gprof, ld, and opcodes) if they have been
1574 individually linked or moved into the top level GCC source tree before
1578 Perform a comparison test of the stage2 and stage3 compilers.
1581 Build runtime libraries using the stage3 compiler from the previous step.
1585 If you are short on disk space you might consider @samp{make
1586 bootstrap-lean} instead. The sequence of compilation is the
1587 same described above, but object files from the stage1 and
1588 stage2 of the 3-stage bootstrap of the compiler are deleted as
1589 soon as they are no longer needed.
1591 If you want to save additional space during the bootstrap and in
1592 the final installation as well, you can build the compiler binaries
1593 without debugging information as in the following example. This will save
1594 roughly 40% of disk space both for the bootstrap and the final installation.
1595 (Libraries will still contain debugging information.)
1598 make CFLAGS='-O' LIBCFLAGS='-g -O2' \
1599 LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap
1602 If you wish to use non-default GCC flags when compiling the stage2 and
1603 stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing
1604 @samp{make}. Non-default optimization flags are less well
1605 tested here than the default of @samp{-g -O2}, but should still work.
1606 In a few cases, you may find that you need to specify special flags such
1607 as @option{-msoft-float} here to complete the bootstrap; or, if the
1608 native compiler miscompiles the stage1 compiler, you may need to work
1609 around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the
1610 stage1 compiler that were miscompiled, or by using @samp{make
1611 bootstrap4} to increase the number of stages of bootstrap.
1613 Note that using non-standard @code{CFLAGS} can cause bootstrap to fail
1614 if these trigger a warning with the new compiler. For example using
1615 @samp{-O2 -g -mcpu=i686} on @code{i686-pc-linux-gnu} will cause bootstrap
1616 failure as @option{-mcpu=} is deprecated in 3.4.0 and above.
1619 If you used the flag @option{--enable-languages=@dots{}} to restrict
1620 the compilers to be built, only those you've actually enabled will be
1621 built. This will of course only build those runtime libraries, for
1622 which the particular compiler has been built. Please note,
1623 that re-defining @env{LANGUAGES} when calling @samp{make}
1624 @strong{does not} work anymore!
1626 If the comparison of stage2 and stage3 fails, this normally indicates
1627 that the stage2 compiler has compiled GCC incorrectly, and is therefore
1628 a potentially serious bug which you should investigate and report. (On
1629 a few systems, meaningful comparison of object files is impossible; they
1630 always appear ``different''. If you encounter this problem, you will
1631 need to disable comparison in the @file{Makefile}.)
1633 If you do not want to bootstrap your compiler, you can configure with
1634 @option{--disable-bootstrap}. In particular cases, you may want to
1635 bootstrap your compiler even if the target system is not the same as
1636 the one you are building on: for example, you could build a
1637 @code{powerpc-unknown-linux-gnu} toolchain on a
1638 @code{powerpc64-unknown-linux-gnu} host. In this case, pass
1639 @option{--enable-bootstrap} to the configure script.
1642 @section Building a cross compiler
1644 We recommend reading the
1645 @uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ}
1646 for information about building cross compilers.
1648 When building a cross compiler, it is not generally possible to do a
1649 3-stage bootstrap of the compiler. This makes for an interesting problem
1650 as parts of GCC can only be built with GCC@.
1652 To build a cross compiler, we first recommend building and installing a
1653 native compiler. You can then use the native GCC compiler to build the
1654 cross compiler. The installed native compiler needs to be GCC version
1657 Assuming you have already installed a native copy of GCC and configured
1658 your cross compiler, issue the command @command{make}, which performs the
1663 Build host tools necessary to build the compiler such as texinfo, bison,
1667 Build target tools for use by the compiler such as binutils (bfd,
1668 binutils, gas, gprof, ld, and opcodes)
1669 if they have been individually linked or moved into the top level GCC source
1670 tree before configuring.
1673 Build the compiler (single stage only).
1676 Build runtime libraries using the compiler from the previous step.
1679 Note that if an error occurs in any step the make process will exit.
1681 If you are not building GNU binutils in the same source tree as GCC,
1682 you will need a cross-assembler and cross-linker installed before
1683 configuring GCC@. Put them in the directory
1684 @file{@var{prefix}/@var{target}/bin}. Here is a table of the tools
1685 you should put in this directory:
1689 This should be the cross-assembler.
1692 This should be the cross-linker.
1695 This should be the cross-archiver: a program which can manipulate
1696 archive files (linker libraries) in the target machine's format.
1699 This should be a program to construct a symbol table in an archive file.
1702 The installation of GCC will find these programs in that directory,
1703 and copy or link them to the proper place to for the cross-compiler to
1704 find them when run later.
1706 The easiest way to provide these files is to build the Binutils package.
1707 Configure it with the same @option{--host} and @option{--target}
1708 options that you use for configuring GCC, then build and install
1709 them. They install their executables automatically into the proper
1710 directory. Alas, they do not support all the targets that GCC
1713 If you are not building a C library in the same source tree as GCC,
1714 you should also provide the target libraries and headers before
1715 configuring GCC, specifying the directories with
1716 @option{--with-sysroot} or @option{--with-headers} and
1717 @option{--with-libs}. Many targets also require ``start files'' such
1718 as @file{crt0.o} and
1719 @file{crtn.o} which are linked into each executable. There may be several
1720 alternatives for @file{crt0.o}, for use with profiling or other
1721 compilation options. Check your target's definition of
1722 @code{STARTFILE_SPEC} to find out what start files it uses.
1724 @section Building in parallel
1726 You can use @samp{make -j 2}@footnote{Only supported by GNU Make 3.79
1727 and above, which is anyway necessary to build GCC.}, instead of @samp{make},
1728 to build GCC in parallel. You can also specify a bigger number, and
1729 in most cases using a value greater than the number of processors in
1730 your machine will result in fewer and shorter I/O latency hits, thus
1731 improving overall throughput; this is especially true for slow drives
1732 and network filesystems.
1734 @section Building the Ada compiler
1736 In order to build GNAT, the Ada compiler, you need a working GNAT
1737 compiler (GNAT version 3.14 or later, or GCC version 3.1 or later).
1738 This includes GNAT tools such as @command{gnatmake} and
1739 @command{gnatlink}, since the Ada front end is written in Ada and
1740 uses some GNAT-specific extensions.
1742 In order to build a cross compiler, it is suggested to install
1743 the new compiler as native first, and then use it to build the cross
1746 @command{configure} does not test whether the GNAT installation works
1747 and has a sufficiently recent version; if too old a GNAT version is
1748 installed, the build will fail unless @option{--enable-languages} is
1749 used to disable building the Ada front end.
1751 @section Building with profile feedback
1753 It is possible to use profile feedback to optimize the compiler itself. This
1754 should result in a faster compiler binary. Experiments done on x86 using gcc
1755 3.3 showed approximately 7 percent speedup on compiling C programs. To
1756 bootstrap the compiler with profile feedback, use @code{make profiledbootstrap}.
1758 When @samp{make profiledbootstrap} is run, it will first build a @code{stage1}
1759 compiler. This compiler is used to build a @code{stageprofile} compiler
1760 instrumented to collect execution counts of instruction and branch
1761 probabilities. Then runtime libraries are compiled with profile collected.
1762 Finally a @code{stagefeedback} compiler is built using the information collected.
1764 Unlike standard bootstrap, several additional restrictions apply. The
1765 compiler used to build @code{stage1} needs to support a 64-bit integral type.
1766 It is recommended to only use GCC for this. Also parallel make is currently
1767 not supported since collisions in profile collecting may occur.
1774 @uref{./index.html,,Return to the GCC Installation page}
1778 @c ***Testing*****************************************************************
1780 @comment node-name, next, previous, up
1781 @node Testing, Final install, Building, Installing GCC
1785 @chapter Installing GCC: Testing
1788 @cindex Installing GCC: Testing
1791 Before you install GCC, we encourage you to run the testsuites and to
1792 compare your results with results from a similar configuration that have
1793 been submitted to the
1794 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
1795 Some of these archived results are linked from the build status lists
1796 at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who
1797 reports a successful build runs the testsuites and submits the results.
1798 This step is optional and may require you to download additional software,
1799 but it can give you confidence in your new GCC installation or point out
1800 problems before you install and start using your new GCC@.
1802 First, you must have @uref{download.html,,downloaded the testsuites}.
1803 These are part of the full distribution, but if you downloaded the
1804 ``core'' compiler plus any front ends, you must download the testsuites
1807 Second, you must have the testing tools installed. This includes
1808 @uref{http://www.gnu.org/software/dejagnu/,,DejaGnu} 1.4.4 and later,
1809 Tcl, and Expect; the DejaGnu site has links to these.
1811 If the directories where @command{runtest} and @command{expect} were
1812 installed are not in the @env{PATH}, you may need to set the following
1813 environment variables appropriately, as in the following example (which
1814 assumes that DejaGnu has been installed under @file{/usr/local}):
1817 TCL_LIBRARY = /usr/local/share/tcl8.0
1818 DEJAGNULIBS = /usr/local/share/dejagnu
1821 (On systems such as Cygwin, these paths are required to be actual
1822 paths, not mounts or links; presumably this is due to some lack of
1823 portability in the DejaGnu code.)
1826 Finally, you can run the testsuite (which may take a long time):
1828 cd @var{objdir}; make -k check
1831 This will test various components of GCC, such as compiler
1832 front ends and runtime libraries. While running the testsuite, DejaGnu
1833 might emit some harmless messages resembling
1834 @samp{WARNING: Couldn't find the global config file.} or
1835 @samp{WARNING: Couldn't find tool init file} that can be ignored.
1837 @section How can you run the testsuite on selected tests?
1839 In order to run sets of tests selectively, there are targets
1840 @samp{make check-gcc} and @samp{make check-g++}
1841 in the @file{gcc} subdirectory of the object directory. You can also
1842 just run @samp{make check} in a subdirectory of the object directory.
1845 A more selective way to just run all @command{gcc} execute tests in the
1849 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
1852 Likewise, in order to run only the @command{g++} ``old-deja'' tests in
1853 the testsuite with filenames matching @samp{9805*}, you would use
1856 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
1859 The @file{*.exp} files are located in the testsuite directories of the GCC
1860 source, the most important ones being @file{compile.exp},
1861 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
1862 To get a list of the possible @file{*.exp} files, pipe the
1863 output of @samp{make check} into a file and look at the
1864 @samp{Running @dots{} .exp} lines.
1866 @section Passing options and running multiple testsuites
1868 You can pass multiple options to the testsuite using the
1869 @samp{--target_board} option of DejaGNU, either passed as part of
1870 @samp{RUNTESTFLAGS}, or directly to @command{runtest} if you prefer to
1871 work outside the makefiles. For example,
1874 make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fno-strength-reduce"
1877 will run the standard @command{g++} testsuites (``unix'' is the target name
1878 for a standard native testsuite situation), passing
1879 @samp{-O3 -fno-strength-reduce} to the compiler on every test, i.e.,
1880 slashes separate options.
1882 You can run the testsuites multiple times using combinations of options
1883 with a syntax similar to the brace expansion of popular shells:
1886 @dots{}"--target_board=arm-sim/@{-mhard-float,-msoft-float@}@{-O1,-O2,-O3,@}"
1889 (Note the empty option caused by the trailing comma in the final group.)
1890 The following will run each testsuite eight times using the @samp{arm-sim}
1891 target, as if you had specified all possible combinations yourself:
1894 --target_board=arm-sim/-mhard-float/-O1
1895 --target_board=arm-sim/-mhard-float/-O2
1896 --target_board=arm-sim/-mhard-float/-O3
1897 --target_board=arm-sim/-mhard-float
1898 --target_board=arm-sim/-msoft-float/-O1
1899 --target_board=arm-sim/-msoft-float/-O2
1900 --target_board=arm-sim/-msoft-float/-O3
1901 --target_board=arm-sim/-msoft-float
1904 They can be combined as many times as you wish, in arbitrary ways. This
1908 @dots{}"--target_board=unix/-Wextra@{-O3,-fno-strength-reduce@}@{-fomit-frame-pointer,@}"
1911 will generate four combinations, all involving @samp{-Wextra}.
1913 The disadvantage to this method is that the testsuites are run in serial,
1914 which is a waste on multiprocessor systems. For users with GNU Make and
1915 a shell which performs brace expansion, you can run the testsuites in
1916 parallel by having the shell perform the combinations and @command{make}
1917 do the parallel runs. Instead of using @samp{--target_board}, use a
1918 special makefile target:
1921 make -j@var{N} check-@var{testsuite}//@var{test-target}/@var{option1}/@var{option2}/@dots{}
1927 make -j3 check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@}
1930 will run three concurrent ``make-gcc'' testsuites, eventually testing all
1931 ten combinations as described above. Note that this is currently only
1932 supported in the @file{gcc} subdirectory. (To see how this works, try
1933 typing @command{echo} before the example given here.)
1936 @section Additional testing for Java Class Libraries
1938 The Java runtime tests can be executed via @samp{make check}
1939 in the @file{@var{target}/libjava/testsuite} directory in
1942 The @uref{http://sources.redhat.com/mauve/,,Mauve Project} provides
1943 a suite of tests for the Java Class Libraries. This suite can be run
1944 as part of libgcj testing by placing the Mauve tree within the libjava
1945 testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by
1946 specifying the location of that tree when invoking @samp{make}, as in
1947 @samp{make MAUVEDIR=~/mauve check}.
1949 @uref{http://sources.redhat.com/mauve/jacks.html,,Jacks}
1950 is a free testsuite that tests Java compiler front ends. This suite
1951 can be run as part of libgcj testing by placing the Jacks tree within
1952 the libjava testsuite at @file{libjava/testsuite/libjava.jacks/jacks}.
1954 @section How to interpret test results
1956 The result of running the testsuite are various @file{*.sum} and @file{*.log}
1957 files in the testsuite subdirectories. The @file{*.log} files contain a
1958 detailed log of the compiler invocations and the corresponding
1959 results, the @file{*.sum} files summarize the results. These summaries
1960 contain status codes for all tests:
1964 PASS: the test passed as expected
1966 XPASS: the test unexpectedly passed
1968 FAIL: the test unexpectedly failed
1970 XFAIL: the test failed as expected
1972 UNSUPPORTED: the test is not supported on this platform
1974 ERROR: the testsuite detected an error
1976 WARNING: the testsuite detected a possible problem
1979 It is normal for some tests to report unexpected failures. At the
1980 current time the testing harness does not allow fine grained control
1981 over whether or not a test is expected to fail. This problem should
1982 be fixed in future releases.
1985 @section Submitting test results
1987 If you want to report the results to the GCC project, use the
1988 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
1991 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
1992 -m gcc-testresults@@gcc.gnu.org |sh
1995 This script uses the @command{Mail} program to send the results, so
1996 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
1997 prepended to the testsuite summary and should contain any special
1998 remarks you have on your results or your build environment. Please
1999 do not edit the testsuite result block or the subject line, as these
2000 messages may be automatically processed.
2007 @uref{./index.html,,Return to the GCC Installation page}
2011 @c ***Final install***********************************************************
2013 @comment node-name, next, previous, up
2014 @node Final install, , Testing, Installing GCC
2016 @ifset finalinstallhtml
2018 @chapter Installing GCC: Final installation
2021 Now that GCC has been built (and optionally tested), you can install it with
2023 cd @var{objdir}; make install
2026 We strongly recommend to install into a target directory where there is
2027 no previous version of GCC present.
2029 That step completes the installation of GCC; user level binaries can
2030 be found in @file{@var{prefix}/bin} where @var{prefix} is the value
2031 you specified with the @option{--prefix} to configure (or
2032 @file{/usr/local} by default). (If you specified @option{--bindir},
2033 that directory will be used instead; otherwise, if you specified
2034 @option{--exec-prefix}, @file{@var{exec-prefix}/bin} will be used.)
2035 Headers for the C++ and Java libraries are installed in
2036 @file{@var{prefix}/include}; libraries in @file{@var{libdir}}
2037 (normally @file{@var{prefix}/lib}); internal parts of the compiler in
2038 @file{@var{libdir}/gcc} and @file{@var{libexecdir}/gcc}; documentation
2039 in info format in @file{@var{infodir}} (normally
2040 @file{@var{prefix}/info}).
2042 When installing cross-compilers, GCC's executables
2043 are not only installed into @file{@var{bindir}}, that
2044 is, @file{@var{exec-prefix}/bin}, but additionally into
2045 @file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory
2046 exists. Typically, such @dfn{tooldirs} hold target-specific
2047 binutils, including assembler and linker.
2049 Installation into a temporary staging area or into a @command{chroot}
2050 jail can be achieved with the command
2053 make DESTDIR=@var{path-to-rootdir} install
2056 @noindent where @var{path-to-rootdir} is the absolute path of
2057 a directory relative to which all installation paths will be
2058 interpreted. Note that the directory specified by @code{DESTDIR}
2059 need not exist yet; it will be created if necessary.
2061 There is a subtle point with tooldirs and @code{DESTDIR}:
2062 If you relocate a cross-compiler installation with
2063 e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory
2064 @file{@var{rootdir}/@var{exec-prefix}/@var{target-alias}/bin} will
2065 be filled with duplicated GCC executables only if it already exists,
2066 it will not be created otherwise. This is regarded as a feature,
2067 not as a bug, because it gives slightly more control to the packagers
2068 using the @code{DESTDIR} feature.
2070 If you are bootstrapping a released version of GCC then please
2071 quickly review the build status page for your release, available from
2072 @uref{http://gcc.gnu.org/buildstat.html}.
2073 If your system is not listed for the version of GCC that you built,
2075 @email{gcc@@gcc.gnu.org} indicating
2076 that you successfully built and installed GCC@.
2077 Include the following information:
2081 Output from running @file{@var{srcdir}/config.guess}. Do not send
2082 that file itself, just the one-line output from running it.
2085 The output of @samp{gcc -v} for your newly installed @command{gcc}.
2086 This tells us which version of GCC you built and the options you passed to
2090 Whether you enabled all languages or a subset of them. If you used a
2091 full distribution then this information is part of the configure
2092 options in the output of @samp{gcc -v}, but if you downloaded the
2093 ``core'' compiler plus additional front ends then it isn't apparent
2094 which ones you built unless you tell us about it.
2097 If the build was for GNU/Linux, also include:
2100 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
2101 this information should be available from @file{/etc/issue}.
2104 The version of the Linux kernel, available from @samp{uname --version}
2108 The version of glibc you used; for RPM-based systems like Red Hat,
2109 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
2110 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
2112 For other systems, you can include similar information if you think it is
2116 Any other information that you think would be useful to people building
2117 GCC on the same configuration. The new entry in the build status list
2118 will include a link to the archived copy of your message.
2121 We'd also like to know if the
2123 @ref{Specific, host/target specific installation notes}
2126 @uref{specific.html,,host/target specific installation notes}
2128 didn't include your host/target information or if that information is
2129 incomplete or out of date. Send a note to
2130 @email{gcc@@gcc.gnu.org} detailing how the information should be changed.
2132 If you find a bug, please report it following the
2133 @uref{../bugs.html,,bug reporting guidelines}.
2135 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
2136 dvi}. You will need to have @command{texi2dvi} (version at least 4.4)
2137 and @TeX{} installed. This creates a number of @file{.dvi} files in
2138 subdirectories of @file{@var{objdir}}; these may be converted for
2139 printing with programs such as @command{dvips}. You can also
2140 @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the
2141 Free Software Foundation}, though such manuals may not be for the most
2142 recent version of GCC@.
2144 If you would like to generate online HTML documentation, do @samp{cd
2145 @var{objdir}; make html} and HTML will be generated for the gcc manuals in
2146 @file{@var{objdir}/gcc/HTML}.
2153 @uref{./index.html,,Return to the GCC Installation page}
2157 @c ***Binaries****************************************************************
2159 @comment node-name, next, previous, up
2160 @node Binaries, Specific, Installing GCC, Top
2164 @chapter Installing GCC: Binaries
2167 @cindex Installing GCC: Binaries
2169 We are often asked about pre-compiled versions of GCC@. While we cannot
2170 provide these for all platforms, below you'll find links to binaries for
2171 various platforms where creating them by yourself is not easy due to various
2174 Please note that we did not create these binaries, nor do we
2175 support them. If you have any problems installing them, please
2176 contact their makers.
2183 @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX};
2186 @uref{http://aixpdslib.seas.ucla.edu,,UCLA Software Library for AIX}.
2190 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}.
2193 Renesas H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
2194 Development Tools for the Renesas H8/300[HS] Series}.
2200 @uref{http://hpux.cs.utah.edu/,,HP-UX Porting Center};
2203 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
2207 Motorola 68HC11/68HC12---@uref{http://www.gnu-m68hc11.org,,GNU
2208 Development Tools for the Motorola 68HC11/68HC12}.
2211 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
2212 OpenServer/Unixware}.
2215 Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware}.
2218 SGI---@uref{http://freeware.sgi.com/,,SGI Freeware}.
2224 The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project;
2226 The @uref{http://www.mingw.org/,,MinGW} project.
2230 @uref{ftp://ftp.thewrittenword.com/packages/by-name/,,The
2231 Written Word} offers binaries for
2234 Digital UNIX 4.0D and 5.1,
2236 HP-UX 10.20, 11.00, and 11.11, and
2237 Solaris/SPARC 2.5.1, 2.6, 7, 8, and 9.
2240 @uref{http://www.openpkg.org/,,OpenPKG} offers binaries for quite a
2241 number of platforms.
2244 The @uref{http://gcc.gnu.org/wiki/GFortranBinaries,,GFortran Wiki} has
2245 links to gfortran binaries for several platforms.
2248 In addition to those specific offerings, you can get a binary
2249 distribution CD-ROM from the
2250 @uref{http://www.gnu.org/order/order.html,,Free Software Foundation}.
2251 It contains binaries for a number of platforms, and
2252 includes not only GCC, but other stuff as well. The current CD does
2253 not contain the latest version of GCC, but it should allow
2254 bootstrapping the compiler. An updated version of that disk is in the
2262 @uref{./index.html,,Return to the GCC Installation page}
2266 @c ***Specific****************************************************************
2268 @comment node-name, next, previous, up
2269 @node Specific, Old, Binaries, Top
2273 @chapter Host/target specific installation notes for GCC
2276 @cindex Specific installation notes
2277 @cindex Target specific installation
2278 @cindex Host specific installation
2279 @cindex Target specific installation notes
2281 Please read this document carefully @emph{before} installing the
2282 GNU Compiler Collection on your machine.
2287 @uref{#alpha-x-x,,alpha*-*-*}
2289 @uref{#alpha-dec-osf,,alpha*-dec-osf*}
2291 @uref{#alphaev5-cray-unicosmk,,alphaev5-cray-unicosmk*}
2293 @uref{#arc-x-elf,,arc-*-elf}
2295 @uref{#arm-x-elf,,arm-*-elf}
2296 @uref{#arm-x-coff,,arm-*-coff}
2297 @uref{#arm-x-aout,,arm-*-aout}
2299 @uref{#xscale-x-x,,xscale-*-*}
2303 @uref{#bfin,,Blackfin}
2309 @uref{#x-x-freebsd,,*-*-freebsd*}
2311 @uref{#h8300-hms,,h8300-hms}
2313 @uref{#hppa-hp-hpux,,hppa*-hp-hpux*}
2315 @uref{#hppa-hp-hpux10,,hppa*-hp-hpux10}
2317 @uref{#hppa-hp-hpux11,,hppa*-hp-hpux11}
2319 @uref{#x-x-linux-gnu,,*-*-linux-gnu}
2321 @uref{#ix86-x-linuxaout,,i?86-*-linux*aout}
2323 @uref{#ix86-x-linux,,i?86-*-linux*}
2325 @uref{#ix86-x-sco32v5,,i?86-*-sco3.2v5*}
2327 @uref{#ix86-x-solaris210,,i?86-*-solaris2.10}
2329 @uref{#ix86-x-udk,,i?86-*-udk}
2331 @uref{#ia64-x-linux,,ia64-*-linux}
2333 @uref{#ia64-x-hpux,,ia64-*-hpux*}
2335 @uref{#x-ibm-aix,,*-ibm-aix*}
2337 @uref{#iq2000-x-elf,,iq2000-*-elf}
2339 @uref{#m32c-x-elf,,m32c-*-elf}
2341 @uref{#m32r-x-elf,,m32r-*-elf}
2343 @uref{#m6811-elf,,m6811-elf}
2345 @uref{#m6812-elf,,m6812-elf}
2347 @uref{#m68k-hp-hpux,,m68k-hp-hpux}
2349 @uref{#mips-x-x,,mips-*-*}
2351 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
2353 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
2355 @uref{#powerpc-x-x,,powerpc*-*-*, powerpc-*-sysv4}
2357 @uref{#powerpc-x-darwin,,powerpc-*-darwin*}
2359 @uref{#powerpc-x-elf,,powerpc-*-elf, powerpc-*-sysv4}
2361 @uref{#powerpc-x-linux-gnu,,powerpc*-*-linux-gnu*}
2363 @uref{#powerpc-x-netbsd,,powerpc-*-netbsd*}
2365 @uref{#powerpc-x-eabisim,,powerpc-*-eabisim}
2367 @uref{#powerpc-x-eabi,,powerpc-*-eabi}
2369 @uref{#powerpcle-x-elf,,powerpcle-*-elf, powerpcle-*-sysv4}
2371 @uref{#powerpcle-x-eabisim,,powerpcle-*-eabisim}
2373 @uref{#powerpcle-x-eabi,,powerpcle-*-eabi}
2375 @uref{#s390-x-linux,,s390-*-linux*}
2377 @uref{#s390x-x-linux,,s390x-*-linux*}
2379 @uref{#s390x-ibm-tpf,,s390x-ibm-tpf*}
2381 @uref{#x-x-solaris2,,*-*-solaris2*}
2383 @uref{#sparc-sun-solaris2,,sparc-sun-solaris2*}
2385 @uref{#sparc-sun-solaris27,,sparc-sun-solaris2.7}
2387 @uref{#sparc-x-linux,,sparc-*-linux*}
2389 @uref{#sparc64-x-solaris2,,sparc64-*-solaris2*}
2391 @uref{#sparcv9-x-solaris2,,sparcv9-*-solaris2*}
2393 @uref{#x-x-sysv,,*-*-sysv*}
2395 @uref{#vax-dec-ultrix,,vax-dec-ultrix}
2397 @uref{#x-x-vxworks,,*-*-vxworks*}
2399 @uref{#x86-64-x-x,,x86_64-*-*, amd64-*-*}
2401 @uref{#xtensa-x-elf,,xtensa-*-elf}
2403 @uref{#xtensa-x-linux,,xtensa-*-linux*}
2405 @uref{#windows,,Microsoft Windows}
2409 @uref{#older,,Older systems}
2414 @uref{#elf,,all ELF targets} (SVR4, Solaris 2, etc.)
2420 <!-- -------- host/target specific issues start here ---------------- -->
2423 @heading @anchor{alpha-x-x}alpha*-*-*
2425 This section contains general configuration information for all
2426 alpha-based platforms using ELF (in particular, ignore this section for
2427 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
2428 section, please read all other sections that match your target.
2430 We require binutils 2.11.2 or newer.
2431 Previous binutils releases had a number of problems with DWARF 2
2432 debugging information, not the least of which is incorrect linking of
2438 @heading @anchor{alpha-dec-osf}alpha*-dec-osf*
2439 Systems using processors that implement the DEC Alpha architecture and
2440 are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
2441 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
2443 As of GCC 3.2, versions before @code{alpha*-dec-osf4} are no longer
2444 supported. (These are the versions which identify themselves as DEC
2447 In Digital Unix V4.0, virtual memory exhausted bootstrap failures
2448 may be fixed by configuring with @option{--with-gc=simple},
2449 reconfiguring Kernel Virtual Memory and Swap parameters
2450 per the @command{/usr/sbin/sys_check} Tuning Suggestions,
2451 or applying the patch in
2452 @uref{http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html}.
2454 In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
2455 currently (2001-06-13) work with @command{mips-tfile}. As a workaround,
2456 we need to use the old assembler, invoked via the barely documented
2457 @option{-oldas} option. To bootstrap GCC, you either need to use the
2461 % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
2464 or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
2467 % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
2470 As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld}
2471 are supported on Tru64 UNIX, so you must not configure GCC with
2472 @option{--with-gnu-as} or @option{--with-gnu-ld}.
2474 GCC writes a @samp{.verstamp} directive to the assembler output file
2475 unless it is built as a cross-compiler. It gets the version to use from
2476 the system header file @file{/usr/include/stamp.h}. If you install a
2477 new version of DEC Unix, you should rebuild GCC to pick up the new version
2480 Note that since the Alpha is a 64-bit architecture, cross-compilers from
2481 32-bit machines will not generate code as efficient as that generated
2482 when the compiler is running on a 64-bit machine because many
2483 optimizations that depend on being able to represent a word on the
2484 target in an integral value on the host cannot be performed. Building
2485 cross-compilers on the Alpha for 32-bit machines has only been tested in
2486 a few cases and may not work properly.
2488 @samp{make compare} may fail on old versions of DEC Unix unless you add
2489 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
2490 assembler input file is stored in the object file, and that makes
2491 comparison fail if it differs between the @code{stage1} and
2492 @code{stage2} compilations. The option @option{-save-temps} forces a
2493 fixed name to be used for the assembler input file, instead of a
2494 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
2495 unless the comparisons fail without that option. If you add
2496 @option{-save-temps}, you will have to manually delete the @samp{.i} and
2497 @samp{.s} files after each series of compilations.
2499 GCC now supports both the native (ECOFF) debugging format used by DBX
2500 and GDB and an encapsulated STABS format for use only with GDB@. See the
2501 discussion of the @option{--with-stabs} option of @file{configure} above
2502 for more information on these formats and how to select them.
2504 There is a bug in DEC's assembler that produces incorrect line numbers
2505 for ECOFF format when the @samp{.align} directive is used. To work
2506 around this problem, GCC will not emit such alignment directives
2507 while writing ECOFF format debugging information even if optimization is
2508 being performed. Unfortunately, this has the very undesirable
2509 side-effect that code addresses when @option{-O} is specified are
2510 different depending on whether or not @option{-g} is also specified.
2512 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
2513 DBX@. DEC is now aware of this problem with the assembler and hopes to
2514 provide a fix shortly.
2519 @heading @anchor{alphaev5-cray-unicosmk}alphaev5-cray-unicosmk*
2520 Cray T3E systems running Unicos/Mk.
2522 This port is incomplete and has many known bugs. We hope to improve the
2523 support for this target soon. Currently, only the C front end is supported,
2524 and it is not possible to build parallel applications. Cray modules are not
2525 supported; in particular, Craylibs are assumed to be in
2526 @file{/opt/ctl/craylibs/craylibs}.
2528 On this platform, you need to tell GCC where to find the assembler and
2529 the linker. The simplest way to do so is by providing @option{--with-as}
2530 and @option{--with-ld} to @file{configure}, e.g.@:
2533 configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld \
2534 --enable-languages=c
2537 The comparison test at the end of the bootstrapping process fails on Unicos/Mk
2538 because the assembler inserts timestamps into object files. You should
2539 be able to work around this by doing @samp{make all} after getting this
2545 @heading @anchor{arc-x-elf}arc-*-elf
2546 Argonaut ARC processor.
2547 This configuration is intended for embedded systems.
2552 @heading @anchor{arm-x-elf}arm-*-elf
2553 @heading @anchor{xscale-x-x}xscale-*-*
2554 ARM-family processors. Subtargets that use the ELF object format
2555 require GNU binutils 2.13 or newer. Such subtargets include:
2556 @code{arm-*-freebsd}, @code{arm-*-netbsdelf}, @code{arm-*-*linux},
2557 @code{arm-*-rtems} and @code{arm-*-kaos}.
2562 @heading @anchor{arm-x-coff}arm-*-coff
2563 ARM-family processors. Note that there are two different varieties
2564 of PE format subtarget supported: @code{arm-wince-pe} and
2565 @code{arm-pe} as well as a standard COFF target @code{arm-*-coff}.
2570 @heading @anchor{arm-x-aout}arm-*-aout
2571 ARM-family processors. These targets support the AOUT file format:
2572 @code{arm-*-aout}, @code{arm-*-netbsd}.
2577 @heading @anchor{avr}avr
2579 ATMEL AVR-family micro controllers. These are used in embedded
2580 applications. There are no standard Unix configurations.
2582 @xref{AVR Options,, AVR Options, gcc, Using the GNU Compiler
2586 See ``AVR Options'' in the main manual
2588 for the list of supported MCU types.
2590 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
2592 Further installation notes and other useful information about AVR tools
2593 can also be obtained from:
2597 @uref{http://www.nongnu.org/avr/,,http://www.nongnu.org/avr/}
2599 @uref{http://home.overta.ru/users/denisc/,,http://home.overta.ru/users/denisc/}
2601 @uref{http://www.amelek.gda.pl/avr/,,http://www.amelek.gda.pl/avr/}
2604 We @emph{strongly} recommend using binutils 2.13 or newer.
2606 The following error:
2608 Error: register required
2611 indicates that you should upgrade to a newer version of the binutils.
2616 @heading @anchor{bfin}Blackfin
2618 The Blackfin processor, an Analog Devices DSP.
2620 @xref{Blackfin Options,, Blackfin Options, gcc, Using the GNU Compiler
2624 See ``Blackfin Options'' in the main manual
2627 More information, and a version of binutils with support for this processor,
2628 is available at @uref{http://blackfin.uclinux.org}
2633 @heading @anchor{c4x}c4x
2635 Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal
2636 Processors. These are used in embedded applications. There are no
2637 standard Unix configurations.
2639 @xref{TMS320C3x/C4x Options,, TMS320C3x/C4x Options, gcc, Using the
2640 GNU Compiler Collection (GCC)},
2643 See ``TMS320C3x/C4x Options'' in the main manual
2645 for the list of supported MCU types.
2647 GCC can be configured as a cross compiler for both the C3x and C4x
2648 architectures on the same system. Use @samp{configure --target=c4x
2649 --enable-languages="c,c++"} to configure.
2652 Further installation notes and other useful information about C4x tools
2653 can also be obtained from:
2657 @uref{http://www.elec.canterbury.ac.nz/c4x/,,http://www.elec.canterbury.ac.nz/c4x/}
2663 @heading @anchor{cris}CRIS
2665 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
2666 series. These are used in embedded applications.
2669 @xref{CRIS Options,, CRIS Options, gcc, Using the GNU Compiler
2673 See ``CRIS Options'' in the main manual
2675 for a list of CRIS-specific options.
2677 There are a few different CRIS targets:
2679 @item cris-axis-aout
2680 Old target. Includes a multilib for the @samp{elinux} a.out-based
2681 target. No multilibs for newer architecture variants.
2683 Mainly for monolithic embedded systems. Includes a multilib for the
2684 @samp{v10} core used in @samp{ETRAX 100 LX}.
2685 @item cris-axis-linux-gnu
2686 A GNU/Linux port for the CRIS architecture, currently targeting
2687 @samp{ETRAX 100 LX} by default.
2690 For @code{cris-axis-aout} and @code{cris-axis-elf} you need binutils 2.11
2691 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
2693 Pre-packaged tools can be obtained from
2694 @uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More
2695 information about this platform is available at
2696 @uref{http://developer.axis.com/}.
2701 @heading @anchor{crx}CRX
2703 The CRX CompactRISC architecture is a low-power 32-bit architecture with
2704 fast context switching and architectural extensibility features.
2707 @xref{CRX Options,, CRX Options, gcc, Using and Porting the GNU Compiler
2712 See ``CRX Options'' in the main manual for a list of CRX-specific options.
2715 Use @samp{configure --target=crx-elf --enable-languages=c,c++} to configure
2716 GCC@ for building a CRX cross-compiler. The option @samp{--target=crx-elf}
2717 is also used to build the @samp{newlib} C library for CRX.
2719 It is also possible to build libstdc++-v3 for the CRX architecture. This
2720 needs to be done in a separate step with the following configure settings:
2721 @samp{gcc/libstdc++-v3/configure --host=crx-elf --with-newlib
2722 --enable-sjlj-exceptions --enable-cxx-flags='-fexceptions -frtti'}
2727 @heading @anchor{dos}DOS
2729 Please have a look at the @uref{binaries.html,,binaries page}.
2731 You cannot install GCC by itself on MSDOS; it will not compile under
2732 any MSDOS compiler except itself. You need to get the complete
2733 compilation package DJGPP, which includes binaries as well as sources,
2734 and includes all the necessary compilation tools and libraries.
2739 @heading @anchor{x-x-freebsd}*-*-freebsd*
2741 The version of binutils installed in @file{/usr/bin} probably works with
2742 this release of GCC@. However, on FreeBSD 4, bootstrapping against the
2743 latest FSF binutils is known to improve overall testsuite results; and,
2744 on FreeBSD/alpha, using binutils 2.14 or later is required to build libjava.
2746 Support for FreeBSD 1 was discontinued in GCC 3.2.
2748 Support for FreeBSD 2 will be discontinued after GCC 3.4. The
2749 following was true for GCC 3.1 but the current status is unknown.
2750 For FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
2751 configuration support and files as shipped with GCC 2.95 are still in
2752 place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
2753 it is unknown which version of binutils was used (it is assumed that it
2754 was the system copy in @file{/usr/bin}) and C++ EH failures were noted.
2756 For FreeBSD using the ELF file format: DWARF 2 debugging is now the
2757 default for all CPU architectures. It had been the default on
2758 FreeBSD/alpha since its inception. You may use @option{-gstabs} instead
2759 of @option{-g}, if you really want the old debugging format. There are
2760 no known issues with mixing object files and libraries with different
2761 debugging formats. Otherwise, this release of GCC should now match more
2762 of the configuration used in the stock FreeBSD configuration of GCC@. In
2763 particular, @option{--enable-threads} is now configured by default.
2764 However, as a general user, do not attempt to replace the system
2765 compiler with this release. Known to bootstrap and check with good
2766 results on FreeBSD 4.9-STABLE and 5-CURRENT@. In the past, known to
2767 bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2,
2768 4.3, 4.4, 4.5, 4.8-STABLE@.
2770 In principle, @option{--enable-threads} is now compatible with
2771 @option{--enable-libgcj} on FreeBSD@. However, it has only been built
2772 and tested on @samp{i386-*-freebsd[45]} and @samp{alpha-*-freebsd[45]}.
2774 library may be incorrectly built (symbols are missing at link time).
2775 There is a rare timing-based startup hang (probably involves an
2776 assumption about the thread library). Multi-threaded boehm-gc (required for
2777 libjava) exposes severe threaded signal-handling bugs on FreeBSD before
2778 4.5-RELEASE@. Other CPU architectures
2779 supported by FreeBSD will require additional configuration tuning in, at
2780 the very least, both boehm-gc and libffi.
2782 Shared @file{libgcc_s.so} is now built and installed by default.
2787 @heading @anchor{h8300-hms}h8300-hms
2788 Renesas H8/300 series of processors.
2790 Please have a look at the @uref{binaries.html,,binaries page}.
2792 The calling convention and structure layout has changed in release 2.6.
2793 All code must be recompiled. The calling convention now passes the
2794 first three arguments in function calls in registers. Structures are no
2795 longer a multiple of 2 bytes.
2800 @heading @anchor{hppa-hp-hpux}hppa*-hp-hpux*
2801 Support for HP-UX version 9 and older was discontinued in GCC 3.4.
2803 We require using gas/binutils on all hppa platforms;
2804 you may encounter a variety of problems if you try to use the HP assembler.
2806 Specifically, @option{-g} does not work on HP-UX (since that system
2807 uses a peculiar debugging format which GCC does not know about), unless
2808 you use GAS and GDB@. It may be helpful to configure GCC with the
2809 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
2810 @option{--with-as=@dots{}} options to ensure that GCC can find GAS@.
2812 If you wish to use the pa-risc 2.0 architecture support with a 32-bit
2813 runtime, you must use gas/binutils 2.11 or newer.
2815 There are two default scheduling models for instructions. These are
2816 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
2817 architecture specified for the target machine when configuring.
2818 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
2819 the target is a @samp{hppa1*} machine.
2821 The PROCESSOR_8000 model is not well suited to older processors. Thus,
2822 it is important to completely specify the machine architecture when
2823 configuring if you want a model other than PROCESSOR_8000. The macro
2824 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
2825 default scheduling model is desired.
2827 As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
2828 through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
2829 This namespace change might cause problems when bootstrapping with
2830 an earlier version of GCC or the HP compiler as essentially the same
2831 namespace is required for an entire build. This problem can be avoided
2832 in a number of ways. With HP cc, @env{UNIX_STD} can be set to @samp{95}
2833 or @samp{98}. Another way is to add an appropriate set of predefines
2834 to @env{CC}. The description for the @option{munix=} option contains
2835 a list of the predefines used with each standard.
2837 As of GCC 4.1, @env{DWARF2} exception handling is available on HP-UX.
2838 It is now the default. This exposed a bug in the handling of data
2839 relocations in the GAS assembler. The handling of 64-bit data relocations
2840 was seriously broken, affecting debugging and exception support on all
2841 @samp{hppa64-*-*} targets. Under some circumstances, 32-bit data relocations
2842 could also be handled incorrectly. This problem is fixed in GAS version
2845 GCC versions prior to 4.1 incorrectly passed and returned complex
2846 values. They are now passed in the same manner as aggregates.
2848 More specific information to @samp{hppa*-hp-hpux*} targets follows.
2853 @heading @anchor{hppa-hp-hpux10}hppa*-hp-hpux10
2855 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
2856 @code{PHCO_19798} from HP@. HP has two sites which provide patches free of
2862 <a href="http://us.itrc.hp.com/service/home/home.do">US, Canada, Asia-Pacific, and
2866 @uref{http://us.itrc.hp.com/service/home/home.do,,} US, Canada, Asia-Pacific,
2870 @uref{http://europe.itrc.hp.com/service/home/home.do,,} Europe.
2873 The HP assembler on these systems has some problems. Most notably the
2874 assembler inserts timestamps into each object file it creates, causing
2875 the 3-stage comparison test to fail during a bootstrap.
2876 You should be able to continue by saying @samp{make all-host all-target}
2877 after getting the failure from @samp{make}.
2879 GCC 4.0 requires CVS binutils as of April 28, 2004 or later. Earlier
2880 versions require binutils 2.8 or later.
2882 The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are
2883 used for one-only code and data. This resolves many of the previous
2884 problems in using C++ on this target. However, the ABI is not compatible
2885 with the one implemented under HP-UX 11 using secondary definitions.
2890 @heading @anchor{hppa-hp-hpux11}hppa*-hp-hpux11
2892 GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
2893 be used to compile GCC 3.0 and up.
2895 Refer to @uref{binaries.html,,binaries} for information about obtaining
2896 precompiled GCC binaries for HP-UX@. Precompiled binaries must be obtained
2897 to build the Ada language as it can't be bootstrapped using C@. Ada is
2898 only available for the 32-bit PA-RISC runtime. The libffi and libjava
2899 haven't been ported to HP-UX and don't build.
2901 It is possible to build GCC 3.3 starting with the bundled HP compiler,
2902 but the process requires several steps. GCC 3.3 can then be used to
2903 build later versions. The fastjar program contains ISO C code and
2904 can't be built with the HP bundled compiler. This problem can be
2905 avoided by not building the Java language. For example, use the
2906 @option{--enable-languages="c,c++,f77,objc"} option in your configure
2909 Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The
2910 bundled compiler supports only traditional C; you will need either HP's
2911 unbundled compiler, or a binary distribution of GCC@.
2913 There are several possible approaches to building the distribution.
2914 Binutils can be built first using the HP tools. Then, the GCC
2915 distribution can be built. The second approach is to build GCC
2916 first using the HP tools, then build binutils, then rebuild GCC@.
2917 There have been problems with various binary distributions, so it
2918 is best not to start from a binary distribution.
2920 On 64-bit capable systems, there are two distinct targets. Different
2921 installation prefixes must be used if both are to be installed on
2922 the same system. The @samp{hppa[1-2]*-hp-hpux11*} target generates code
2923 for the 32-bit PA-RISC runtime architecture and uses the HP linker.
2924 The @samp{hppa64-hp-hpux11*} target generates 64-bit code for the
2925 PA-RISC 2.0 architecture. The HP and GNU linkers are both supported
2928 The script config.guess now selects the target type based on the compiler
2929 detected during configuration. You must define @env{PATH} or @env{CC} so
2930 that configure finds an appropriate compiler for the initial bootstrap.
2931 When @env{CC} is used, the definition should contain the options that are
2932 needed whenever @env{CC} is used.
2934 Specifically, options that determine the runtime architecture must be
2935 in @env{CC} to correctly select the target for the build. It is also
2936 convenient to place many other compiler options in @env{CC}. For example,
2937 @env{CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"}
2938 can be used to bootstrap the GCC 3.3 branch with the HP compiler in
2939 64-bit K&R/bundled mode. The @option{+DA2.0W} option will result in
2940 the automatic selection of the @samp{hppa64-hp-hpux11*} target. The
2941 macro definition table of cpp needs to be increased for a successful
2942 build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to
2943 be defined when building with the bundled compiler, or when using the
2944 @option{-Ac} option. These defines aren't necessary with @option{-Ae}.
2946 It is best to explicitly configure the @samp{hppa64-hp-hpux11*} target
2947 with the @option{--with-ld=@dots{}} option. This overrides the standard
2948 search for ld. The two linkers supported on this target require different
2949 commands. The default linker is determined during configuration. As a
2950 result, it's not possible to switch linkers in the middle of a GCC build.
2951 This has been been reported to sometimes occur in unified builds of
2954 GCC 3.0 through 3.2 require binutils 2.11 or above. GCC 3.3 through
2955 GCC 4.0 require binutils 2.14 or later.
2957 Although the HP assembler can be used for an initial build, it shouldn't
2958 be used with any languages other than C and perhaps Fortran due to its
2959 many limitations. For example, it does not support weak symbols or alias
2960 definitions. As a result, explicit template instantiations are required
2961 when using C++. This makes it difficult if not impossible to build many
2962 C++ applications. You can't generate debugging information when using
2963 the HP assembler. Finally, bootstrapping fails in the final
2964 comparison of object modules due to the time stamps that it inserts into
2965 the modules. The bootstrap can be continued from this point with
2966 @samp{make all-host all-target}.
2968 A recent linker patch must be installed for the correct operation of
2969 GCC 3.3 and later. @code{PHSS_26559} and @code{PHSS_24304} are the
2970 oldest linker patches that are known to work. They are for HP-UX
2971 11.00 and 11.11, respectively. @code{PHSS_24303}, the companion to
2972 @code{PHSS_24304}, might be usable but it hasn't been tested. These
2973 patches have been superseded. Consult the HP patch database to obtain
2974 the currently recommended linker patch for your system.
2976 The patches are necessary for the support of weak symbols on the
2977 32-bit port, and for the running of initializers and finalizers. Weak
2978 symbols are implemented using SOM secondary definition symbols. Prior
2979 to HP-UX 11, there are bugs in the linker support for secondary symbols.
2980 The patches correct a problem of linker core dumps creating shared
2981 libraries containing secondary symbols, as well as various other
2982 linking issues involving secondary symbols.
2984 GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
2985 run initializers and finalizers on the 64-bit port. The 32-bit port
2986 uses the linker @option{+init} and @option{+fini} options for the same
2987 purpose. The patches correct various problems with the +init/+fini
2988 options, including program core dumps. Binutils 2.14 corrects a
2989 problem on the 64-bit port resulting from HP's non-standard use of
2990 the .init and .fini sections for array initializers and finalizers.
2992 There are a number of issues to consider in selecting which linker to
2993 use with the 64-bit port. The GNU 64-bit linker can only create dynamic
2994 binaries. The @option{-static} option causes linking with archive
2995 libraries but doesn't produce a truly static binary. Dynamic binaries
2996 still require final binding by the dynamic loader to resolve a set of
2997 dynamic-loader-defined symbols. The default behavior of the HP linker
2998 is the same as the GNU linker. However, it can generate true 64-bit
2999 static binaries using the @option{+compat} option.
3001 The HP 64-bit linker doesn't support linkonce semantics. As a
3002 result, C++ programs have many more sections than they should.
3004 The GNU 64-bit linker has some issues with shared library support
3005 and exceptions. As a result, we only support libgcc in archive
3006 format. For similar reasons, dwarf2 unwind and exception support
3007 are disabled. The GNU linker also has problems creating binaries
3008 with @option{-static}. It doesn't provide stubs for internal
3009 calls to global functions in shared libraries, so these calls
3010 can't be overloaded.
3012 Thread support is not implemented in GCC 3.0 through 3.2, so the
3013 @option{--enable-threads} configure option does not work. In 3.3
3014 and later, POSIX threads are supported. The optional DCE thread
3015 library is not supported.
3017 This port still is undergoing significant development.
3022 @heading @anchor{x-x-linux-gnu}*-*-linux-gnu
3024 Versions of libstdc++-v3 starting with 3.2.1 require bugfixes present
3025 in glibc 2.2.5 and later. More information is available in the
3026 libstdc++-v3 documentation.
3031 @heading @anchor{ix86-x-linuxaout}i?86-*-linux*aout
3032 Use this configuration to generate @file{a.out} binaries on Linux-based
3033 GNU systems. This configuration is being superseded.
3038 @heading @anchor{ix86-x-linux}i?86-*-linux*
3040 As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
3041 See @uref{http://gcc.gnu.org/PR10877,,bug 10877} for more information.
3043 If you receive Signal 11 errors when building on GNU/Linux, then it is
3044 possible you have a hardware problem. Further information on this can be
3045 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
3050 @heading @anchor{ix86-x-sco32v5}i?86-*-sco3.2v5*
3051 Use this for the SCO OpenServer Release 5 family of operating systems.
3053 Unlike earlier versions of GCC, the ability to generate COFF with this
3054 target is no longer provided.
3056 Earlier versions of GCC emitted DWARF 1 when generating ELF to allow
3057 the system debugger to be used. That support was too burdensome to
3058 maintain. GCC now emits only DWARF 2 for this target. This means you
3059 may use either the UDK debugger or GDB to debug programs built by this
3062 GCC is now only supported on releases 5.0.4 and later, and requires that
3063 you install Support Level Supplement OSS646B or later, and Support Level
3064 Supplement OSS631C or later. If you are using release 5.0.7 of
3065 OpenServer, you must have at least the first maintenance pack installed
3066 (this includes the relevant portions of OSS646). OSS646, also known as
3067 the ``Execution Environment Update'', provides updated link editors and
3068 assemblers, as well as updated standard C and math libraries. The C
3069 startup modules are also updated to support the System V gABI draft, and
3070 GCC relies on that behavior. OSS631 provides a collection of commonly
3071 used open source libraries, some of which GCC depends on (such as GNU
3072 gettext and zlib). SCO OpenServer Release 5.0.7 has all of this built
3073 in by default, but OSS631C and later also apply to that release. Please
3075 @uref{ftp://ftp.sco.com/pub/openserver5,,ftp://ftp.sco.com/pub/openserver5}
3076 for the latest versions of these (and other potentially useful)
3079 Although there is support for using the native assembler, it is
3080 recommended that you configure GCC to use the GNU assembler. You do
3081 this by using the flags
3082 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You should
3083 use a modern version of GNU binutils. Version 2.13.2.1 was used for all
3084 testing. In general, only the @option{--with-gnu-as} option is tested.
3085 A modern bintuils (as well as a plethora of other development related
3086 GNU utilities) can be found in Support Level Supplement OSS658A, the
3087 ``GNU Development Tools'' package. See the SCO web and ftp sites for details.
3088 That package also contains the currently ``officially supported'' version of
3089 GCC, version 2.95.3. It is useful for bootstrapping this version.
3094 @heading @anchor{ix86-x-solaris210}i?86-*-solaris2.10
3095 Use this for Solaris 10 or later on x86 and x86-64 systems. This
3096 configuration is supported by GCC 4.0 and later versions only.
3098 It is recommended that you configure GCC to use the GNU assembler in
3099 @file{/usr/sfw/bin/gas} but the Sun linker, using the options
3100 @option{--with-gnu-as --with-as=/usr/sfw/bin/gas --without-gnu-ld
3101 --with-ld=/usr/ccs/bin/ld}.
3106 @heading @anchor{ix86-x-udk}i?86-*-udk
3108 This target emulates the SCO Universal Development Kit and requires that
3109 package be installed. (If it is installed, you will have a
3110 @file{/udk/usr/ccs/bin/cc} file present.) It's very much like the
3111 @samp{i?86-*-unixware7*} target
3112 but is meant to be used when hosting on a system where UDK isn't the
3113 default compiler such as OpenServer 5 or Unixware 2. This target will
3114 generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
3115 with the same warnings and caveats as the SCO UDK@.
3117 This target is a little tricky to build because we have to distinguish
3118 it from the native tools (so it gets headers, startups, and libraries
3119 from the right place) while making the tools not think we're actually
3120 building a cross compiler. The easiest way to do this is with a configure
3124 CC=/udk/usr/ccs/bin/cc @var{/your/path/to}/gcc/configure \
3125 --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-
3128 @emph{You should substitute @samp{i686} in the above command with the appropriate
3129 processor for your host.}
3131 After the usual @samp{make} and
3132 @samp{make install}, you can then access the UDK-targeted GCC
3133 tools by adding @command{udk-} before the commonly known name. For
3134 example, to invoke the C compiler, you would use @command{udk-gcc}.
3135 They will coexist peacefully with any native-target GCC tools you may
3142 @heading @anchor{ia64-x-linux}ia64-*-linux
3143 IA-64 processor (also known as IPF, or Itanium Processor Family)
3146 If you are using the installed system libunwind library with
3147 @option{--with-system-libunwind}, then you must use libunwind 0.98 or
3150 None of the following versions of GCC has an ABI that is compatible
3151 with any of the other versions in this list, with the exception that
3152 Red Hat 2.96 and Trillian 000171 are compatible with each other:
3153 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
3154 This primarily affects C++ programs and programs that create shared libraries.
3155 GCC 3.1 or later is recommended for compiling linux, the kernel.
3156 As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
3157 more major ABI changes are expected.
3162 @heading @anchor{ia64-x-hpux}ia64-*-hpux*
3163 Building GCC on this target requires the GNU Assembler. The bundled HP
3164 assembler will not work. To prevent GCC from using the wrong assembler,
3165 the option @option{--with-gnu-as} may be necessary.
3167 The GCC libunwind library has not been ported to HPUX@. This means that for
3168 GCC versions 3.2.3 and earlier, @option{--enable-libunwind-exceptions}
3169 is required to build GCC@. For GCC 3.3 and later, this is the default.
3170 For gcc 3.4.3 and later, @option{--enable-libunwind-exceptions} is
3171 removed and the system libunwind library will always be used.
3175 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
3177 @heading @anchor{x-ibm-aix}*-ibm-aix*
3178 Support for AIX version 3 and older was discontinued in GCC 3.4.
3180 ``out of memory'' bootstrap failures may indicate a problem with
3181 process resource limits (ulimit). Hard limits are configured in the
3182 @file{/etc/security/limits} system configuration file.
3184 To speed up the configuration phases of bootstrapping and installing GCC,
3185 one may use GNU Bash instead of AIX @command{/bin/sh}, e.g.,
3188 % CONFIG_SHELL=/opt/freeware/bin/bash
3189 % export CONFIG_SHELL
3192 and then proceed as described in @uref{build.html,,the build
3193 instructions}, where we strongly recommend specifying an absolute path
3194 to invoke @var{srcdir}/configure.
3196 Errors involving @code{alloca} when building GCC generally are due
3197 to an incorrect definition of @code{CC} in the Makefile or mixing files
3198 compiled with the native C compiler and GCC@. During the stage1 phase of
3199 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
3200 (not @command{xlc}). Once @command{configure} has been informed of
3201 @command{xlc}, one needs to use @samp{make distclean} to remove the
3202 configure cache files and ensure that @env{CC} environment variable
3203 does not provide a definition that will confuse @command{configure}.
3204 If this error occurs during stage2 or later, then the problem most likely
3205 is the version of Make (see above).
3207 The native @command{as} and @command{ld} are recommended for bootstrapping
3208 on AIX 4 and required for bootstrapping on AIX 5L@. The GNU Assembler
3209 reports that it supports WEAK symbols on AIX 4, which causes GCC to try to
3210 utilize weak symbol functionality although it is not supported. The GNU
3211 Assembler and Linker do not support AIX 5L sufficiently to bootstrap GCC@.
3212 The native AIX tools do interoperate with GCC@.
3214 Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
3215 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
3216 fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
3217 referenced as APAR IY53606 (AIX 5.2) or a APAR IY54774 (AIX 5.1)
3219 @samp{libstdc++} in GCC 3.4 increments the major version number of the
3220 shared object and GCC installation places the @file{libstdc++.a}
3221 shared library in a common location which will overwrite the and GCC
3222 3.3 version of the shared library. Applications either need to be
3223 re-linked against the new shared library or the GCC 3.1 and GCC 3.3
3224 versions of the @samp{libstdc++} shared object needs to be available
3225 to the AIX runtime loader. The GCC 3.1 @samp{libstdc++.so.4}, if
3226 present, and GCC 3.3 @samp{libstdc++.so.5} shared objects can be
3227 installed for runtime dynamic loading using the following steps to set
3228 the @samp{F_LOADONLY} flag in the shared object for @emph{each}
3229 multilib @file{libstdc++.a} installed:
3231 Extract the shared objects from the currently installed
3232 @file{libstdc++.a} archive:
3234 % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
3237 Enable the @samp{F_LOADONLY} flag so that the shared object will be
3238 available for runtime dynamic loading, but not linking:
3240 % strip -e libstdc++.so.4 libstdc++.so.5
3243 Archive the runtime-only shared object in the GCC 3.4
3244 @file{libstdc++.a} archive:
3246 % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
3249 Linking executables and shared libraries may produce warnings of
3250 duplicate symbols. The assembly files generated by GCC for AIX always
3251 have included multiple symbol definitions for certain global variable
3252 and function declarations in the original program. The warnings should
3253 not prevent the linker from producing a correct library or runnable
3256 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
3257 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
3258 to parse archive libraries did not handle the new format correctly.
3259 These routines are used by GCC and result in error messages during
3260 linking such as ``not a COFF file''. The version of the routines shipped
3261 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
3262 option of the archive command may be used to create archives of 32-bit
3263 objects using the original ``small format''. A correct version of the
3264 routines is shipped with AIX 4.3.2 and above.
3266 Some versions of the AIX binder (linker) can fail with a relocation
3267 overflow severe error when the @option{-bbigtoc} option is used to link
3268 GCC-produced object files into an executable that overflows the TOC@. A fix
3269 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
3270 available from IBM Customer Support and from its
3271 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3272 website as PTF U455193.
3274 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
3275 with a segmentation fault when invoked by any version of GCC@. A fix for
3276 APAR IX87327 is available from IBM Customer Support and from its
3277 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3278 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
3280 The initial assembler shipped with AIX 4.3.0 generates incorrect object
3281 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
3282 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
3283 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3284 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
3286 AIX provides National Language Support (NLS)@. Compilers and assemblers
3287 use NLS to support locale-specific representations of various data
3288 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
3289 separating decimal fractions). There have been problems reported where
3290 GCC does not produce the same floating-point formats that the assembler
3291 expects. If one encounters this problem, set the @env{LANG}
3292 environment variable to @samp{C} or @samp{En_US}.
3294 By default, GCC for AIX 4.1 and above produces code that can be used on
3295 both Power or PowerPC processors.
3297 A default can be specified with the @option{-mcpu=@var{cpu_type}}
3298 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
3303 @heading @anchor{iq2000-x-elf}iq2000-*-elf
3304 Vitesse IQ2000 processors. These are used in embedded
3305 applications. There are no standard Unix configurations.
3310 @heading @anchor{m32c-x-elf}m32c-*-elf
3311 Renesas M32C processor.
3312 This configuration is intended for embedded systems.
3317 @heading @anchor{m32r-x-elf}m32r-*-elf
3318 Renesas M32R processor.
3319 This configuration is intended for embedded systems.
3324 @heading @anchor{m6811-elf}m6811-elf
3325 Motorola 68HC11 family micro controllers. These are used in embedded
3326 applications. There are no standard Unix configurations.
3331 @heading @anchor{m6812-elf}m6812-elf
3332 Motorola 68HC12 family micro controllers. These are used in embedded
3333 applications. There are no standard Unix configurations.
3338 @heading @anchor{m68k-hp-hpux}m68k-hp-hpux
3339 HP 9000 series 300 or 400 running HP-UX@. HP-UX version 8.0 has a bug in
3340 the assembler that prevents compilation of GCC@. This
3341 bug manifests itself during the first stage of compilation, while
3342 building @file{libgcc2.a}:
3346 cc1: warning: `-g' option not supported on this version of GCC
3347 cc1: warning: `-g1' option not supported on this version of GCC
3348 ./xgcc: Internal compiler error: program as got fatal signal 11
3351 A patched version of the assembler is available as the file
3352 @uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you
3353 have HP software support, the patch can also be obtained directly from
3354 HP, as described in the following note:
3357 This is the patched assembler, to patch SR#1653-010439, where the
3358 assembler aborts on floating point constants.
3360 The bug is not really in the assembler, but in the shared library
3361 version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is
3362 SR#4701-078451. Anyway, the attached assembler uses the archive
3363 library version of ``cvtnum(3c)'' and thus does not exhibit the bug.
3366 This patch is also known as PHCO_4484.
3368 In addition gdb does not understand that native HP-UX format, so
3369 you must use gas if you wish to use gdb.
3371 On HP-UX version 8.05, but not on 8.07 or more recent versions, the
3372 @command{fixproto} shell script triggers a bug in the system shell. If you
3373 encounter this problem, upgrade your operating system or use BASH (the
3374 GNU shell) to run @command{fixproto}. This bug will cause the fixproto
3375 program to report an error of the form:
3378 ./fixproto: sh internal 1K buffer overflow
3381 To fix this, you can also change the first line of the fixproto script
3391 @heading @anchor{mips-x-x}mips-*-*
3392 If on a MIPS system you get an error message saying ``does not have gp
3393 sections for all it's [sic] sectons [sic]'', don't worry about it. This
3394 happens whenever you use GAS with the MIPS linker, but there is not
3395 really anything wrong, and it is okay to use the output file. You can
3396 stop such warnings by installing the GNU linker.
3398 It would be nice to extend GAS to produce the gp tables, but they are
3399 optional, and there should not be a warning about their absence.
3401 The libstdc++ atomic locking routines for MIPS targets requires MIPS II
3402 and later. A patch went in just after the GCC 3.3 release to
3403 make @samp{mips*-*-*} use the generic implementation instead. You can also
3404 configure for @samp{mipsel-elf} as a workaround. The
3405 @samp{mips*-*-linux*} target continues to use the MIPS II routines. More
3406 work on this is expected in future releases.
3408 MIPS systems check for division by zero (unless
3409 @option{-mno-check-zero-division} is passed to the compiler) by
3410 generating either a conditional trap or a break instruction. Using
3411 trap results in smaller code, but is only supported on MIPS II and
3412 later. Also, some versions of the Linux kernel have a bug that
3413 prevents trap from generating the proper signal (@code{SIGFPE}). To enable
3414 the use of break, use the @option{--with-divide=breaks}
3415 @command{configure} option when configuring GCC@. The default is to
3416 use traps on systems that support them.
3418 Cross-compilers for the MIPS as target using the MIPS assembler
3419 currently do not work, because the auxiliary programs
3420 @file{mips-tdump.c} and @file{mips-tfile.c} can't be compiled on
3421 anything but a MIPS. It does work to cross compile for a MIPS
3422 if you use the GNU assembler and linker.
3427 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
3429 In order to compile GCC on an SGI running IRIX 5, the @samp{compiler_dev.hdr}
3430 subsystem must be installed from the IDO CD-ROM supplied by SGI@.
3431 It is also available for download from
3432 @uref{ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist}.
3434 If you use the MIPS C compiler to bootstrap, it may be necessary
3435 to increase its table size for switch statements with the
3436 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
3437 optimization option, you also need to use @option{-Olimit 3000}.
3439 To enable debugging under IRIX 5, you must use GNU binutils 2.15 or
3440 later, and use the @option{--with-gnu-ld} @command{configure} option
3441 when configuring GCC@. You need to use GNU @command{ar} and @command{nm},
3442 also distributed with GNU binutils.
3444 Some users have reported that @command{/bin/sh} will hang during bootstrap.
3445 This problem can be avoided by running the commands:
3448 % CONFIG_SHELL=/bin/ksh
3449 % export CONFIG_SHELL
3452 before starting the build.
3457 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
3459 If you are using SGI's MIPSpro @command{cc} as your bootstrap compiler, you must
3460 ensure that the N32 ABI is in use. To test this, compile a simple C
3461 file with @command{cc} and then run @command{file} on the
3462 resulting object file. The output should look like:
3465 test.o: ELF N32 MSB @dots{}
3471 test.o: ELF 32-bit MSB @dots{}
3477 test.o: ELF 64-bit MSB @dots{}
3480 then your version of @command{cc} uses the O32 or N64 ABI by default. You
3481 should set the environment variable @env{CC} to @samp{cc -n32}
3482 before configuring GCC@.
3484 If you want the resulting @command{gcc} to run on old 32-bit systems
3485 with the MIPS R4400 CPU, you need to ensure that only code for the @samp{mips3}
3486 instruction set architecture (ISA) is generated. While GCC 3.x does
3487 this correctly, both GCC 2.95 and SGI's MIPSpro @command{cc} may change
3488 the ISA depending on the machine where GCC is built. Using one of them
3489 as the bootstrap compiler may result in @samp{mips4} code, which won't run at
3490 all on @samp{mips3}-only systems. For the test program above, you should see:
3493 test.o: ELF N32 MSB mips-3 @dots{}
3499 test.o: ELF N32 MSB mips-4 @dots{}
3502 instead, you should set the environment variable @env{CC} to @samp{cc
3503 -n32 -mips3} or @samp{gcc -mips3} respectively before configuring GCC@.
3505 MIPSpro C 7.4 may cause bootstrap failures, due to a bug when inlining
3506 @code{memcmp}. Either add @code{-U__INLINE_INTRINSICS} to the @env{CC}
3507 environment variable as a workaround or upgrade to MIPSpro C 7.4.1m.
3509 GCC on IRIX 6 is usually built to support the N32, O32 and N64 ABIs. If
3510 you build GCC on a system that doesn't have the N64 libraries installed
3511 or cannot run 64-bit binaries,
3512 you need to configure with @option{--disable-multilib} so GCC doesn't
3513 try to use them. This will disable building the O32 libraries, too.
3514 Look for @file{/usr/lib64/libc.so.1} to see if you
3515 have the 64-bit libraries installed.
3517 To enable debugging for the O32 ABI, you must use GNU @command{as} from
3518 GNU binutils 2.15 or later. You may also use GNU @command{ld}, but
3519 this is not required and currently causes some problems with Ada.
3521 The @option{--enable-threads} option doesn't currently work, a patch is
3522 in preparation for a future release. The @option{--enable-libgcj}
3523 option is disabled by default: IRIX 6 uses a very low default limit
3524 (20480) for the command line length. Although @command{libtool} contains a
3525 workaround for this problem, at least the N64 @samp{libgcj} is known not
3526 to build despite this, running into an internal error of the native
3527 @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
3528 its maximum of 262144 bytes. If you have root access, you can use the
3529 @command{systune} command to do this.
3531 See @uref{http://freeware.sgi.com/} for more
3532 information about using GCC on IRIX platforms.
3537 @heading @anchor{powerpc-x-x}powerpc-*-*
3539 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
3540 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
3545 @heading @anchor{powerpc-x-darwin}powerpc-*-darwin*
3546 PowerPC running Darwin (Mac OS X kernel).
3548 Pre-installed versions of Mac OS X may not include any developer tools,
3549 meaning that you will not be able to build GCC from source. Tool
3550 binaries are available at
3551 @uref{http://developer.apple.com/darwin/projects/compiler/} (free
3552 registration required).
3554 This version of GCC requires at least cctools-590.7.
3556 The version of GCC shipped by Apple typically includes a number of
3557 extensions not available in a standard GCC release. These extensions
3558 are generally for backwards compatibility and best avoided.
3563 @heading @anchor{powerpc-x-elf}powerpc-*-elf, powerpc-*-sysv4
3564 PowerPC system in big endian mode, running System V.4.
3569 @heading @anchor{powerpc-x-linux-gnu}powerpc*-*-linux-gnu*
3572 @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.15}
3573 or newer for a working GCC@.
3578 @heading @anchor{powerpc-x-netbsd}powerpc-*-netbsd*
3579 PowerPC system in big endian mode running NetBSD@. To build the
3580 documentation you will need Texinfo version 4.4 (NetBSD 1.5.1 included
3581 Texinfo version 3.12).
3586 @heading @anchor{powerpc-x-eabisim}powerpc-*-eabisim
3587 Embedded PowerPC system in big endian mode for use in running under the
3593 @heading @anchor{powerpc-x-eabi}powerpc-*-eabi
3594 Embedded PowerPC system in big endian mode.
3599 @heading @anchor{powerpcle-x-elf}powerpcle-*-elf, powerpcle-*-sysv4
3600 PowerPC system in little endian mode, running System V.4.
3605 @heading @anchor{powerpcle-x-eabisim}powerpcle-*-eabisim
3606 Embedded PowerPC system in little endian mode for use in running under
3612 @heading @anchor{powerpcle-x-eabi}powerpcle-*-eabi
3613 Embedded PowerPC system in little endian mode.
3618 @heading @anchor{s390-x-linux}s390-*-linux*
3619 S/390 system running GNU/Linux for S/390@.
3624 @heading @anchor{s390x-x-linux}s390x-*-linux*
3625 zSeries system (64-bit) running GNU/Linux for zSeries@.
3630 @heading @anchor{s390x-ibm-tpf}s390x-ibm-tpf*
3631 zSeries system (64-bit) running TPF@. This platform is
3632 supported as cross-compilation target only.
3637 @c Please use Solaris 2 to refer to all release of Solaris, starting
3638 @c with 2.0 until 2.6, 7, 8, etc. Solaris 1 was a marketing name for
3639 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
3640 @c alone is too unspecific and must be avoided.
3641 @heading @anchor{x-x-solaris2}*-*-solaris2*
3643 Sun does not ship a C compiler with Solaris 2. To bootstrap and install
3644 GCC you first have to install a pre-built compiler, see the
3645 @uref{binaries.html,,binaries page} for details.
3647 The Solaris 2 @command{/bin/sh} will often fail to configure
3648 @file{libstdc++-v3}, @file{boehm-gc} or @file{libjava}. We therefore
3649 recommend to use the following sequence of commands to bootstrap and
3653 % CONFIG_SHELL=/bin/ksh
3654 % export CONFIG_SHELL
3657 and then proceed as described in @uref{build.html,,the build instructions}.
3658 In addition we strongly recommend specifying an absolute path to invoke
3659 @var{srcdir}/configure.
3661 Solaris 2 comes with a number of optional OS packages. Some of these
3662 are needed to use GCC fully, namely @code{SUNWarc},
3663 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
3664 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
3665 optional packages when installing Solaris 2, you will need to verify that
3666 the packages that GCC needs are installed.
3668 To check whether an optional package is installed, use
3669 the @command{pkginfo} command. To add an optional package, use the
3670 @command{pkgadd} command. For further details, see the Solaris 2
3673 Trying to use the linker and other tools in
3674 @file{/usr/ucb} to install GCC has been observed to cause trouble.
3675 For example, the linker may hang indefinitely. The fix is to remove
3676 @file{/usr/ucb} from your @env{PATH}.
3678 The build process works more smoothly with the legacy Sun tools so, if you
3679 have @file{/usr/xpg4/bin} in your @env{PATH}, we recommend that you place
3680 @file{/usr/bin} before @file{/usr/xpg4/bin} for the duration of the build.
3682 All releases of GNU binutils prior to 2.11.2 have known bugs on this
3683 platform. We recommend the use of GNU binutils 2.11.2 or later, or the
3684 vendor tools (Sun @command{as}, Sun @command{ld}). Note that your mileage
3685 may vary if you use a combination of the GNU tools and the Sun tools: while
3686 the combination GNU @command{as} + Sun @command{ld} should reasonably work,
3687 the reverse combination Sun @command{as} + GNU @command{ld} is known to
3688 cause memory corruption at runtime in some cases for C++ programs.
3690 The stock GNU binutils 2.15 release is broken on this platform because of a
3691 single bug. It has been fixed on the 2.15 branch in the CVS repository.
3692 You can obtain a working version by checking out the binutils-2_15-branch
3693 from the CVS repository or applying the patch
3694 @uref{http://sources.redhat.com/ml/binutils-cvs/2004-09/msg00036.html} to the
3697 We recommend using GNU binutils 2.16 or later in conjunction with GCC 4.x,
3698 or the vendor tools (Sun @command{as}, Sun @command{ld}). However, for
3699 Solaris 10 and above, an additional patch is required in order for the GNU
3700 linker to be able to cope with a new flavor of shared libraries. You
3701 can obtain a working version by checking out the binutils-2_16-branch from
3702 the CVS repository or applying the patch
3703 @uref{http://sourceware.org/ml/binutils-cvs/2005-07/msg00122.html} to the
3706 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3707 newer: @command{g++} will complain that types are missing. These headers assume
3708 that omitting the type means @code{int}; this assumption worked for C89 but
3709 is wrong for C++, and is now wrong for C99 also.
3711 @command{g++} accepts such (invalid) constructs with the option
3712 @option{-fpermissive}; it
3713 will assume that any missing type is @code{int} (as defined by C89).
3715 There are patches for Solaris 2.6 (105633-56 or newer for SPARC,
3716 106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC,
3717 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
3718 108653-22 for Intel) that fix this bug.
3720 Sun bug 4927647 sometimes causes random spurious testsuite failures
3721 related to missing diagnostic output. This bug doesn't affect GCC
3722 itself, rather it is a kernel bug triggered by the @command{expect}
3723 program which is used only by the GCC testsuite driver. When the bug
3724 causes the @command{expect} program to miss anticipated output, extra
3725 testsuite failures appear.
3727 There are patches for Solaris 8 (117350-12 or newer for SPARC,
3728 117351-12 or newer for Intel) and Solaris 9 (117171-11 or newer for
3729 SPARC, 117172-11 or newer for Intel) that address this problem.
3734 @heading @anchor{sparc-sun-solaris2}sparc-sun-solaris2*
3736 When GCC is configured to use binutils 2.11.2 or later the binaries
3737 produced are smaller than the ones produced using Sun's native tools;
3738 this difference is quite significant for binaries containing debugging
3741 Sun @command{as} 4.x is broken in that it cannot cope with long symbol names.
3742 A typical error message might look similar to the following:
3745 /usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error:
3746 can't compute value of an expression involving an external symbol.
3749 This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris
3750 2.6 and has been fixed in later (5.x) versions of the assembler,
3751 starting with Solaris 7.
3753 Starting with Solaris 7, the operating system is capable of executing
3754 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
3755 this; the @option{-m64} option enables 64-bit code generation.
3756 However, if all you want is code tuned for the UltraSPARC CPU, you
3757 should try the @option{-mtune=ultrasparc} option instead, which produces
3758 code that, unlike full 64-bit code, can still run on non-UltraSPARC
3761 When configuring on a Solaris 7 or later system that is running a kernel
3762 that supports only 32-bit binaries, one must configure with
3763 @option{--disable-multilib}, since we will not be able to build the
3764 64-bit target libraries.
3766 GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of
3767 the GNU compiler (especially GCC 3.0.x versions), which lead to the
3768 miscompilation of the stage1 compiler and the subsequent failure of the
3769 bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary
3770 stage, i.e.@: to bootstrap that compiler with the base compiler and then
3771 use it to bootstrap the final compiler.
3773 GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7)
3774 and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap
3775 failure in form of a miscompilation of the stage1 compiler by the Sun
3776 compiler. This is Sun bug 4974440. This is fixed with patch 112760-07.
3778 GCC 3.4 changed the default debugging format from STABS to DWARF-2 for
3779 32-bit code on Solaris 7 and later. If you use the Sun assembler, this
3780 change apparently runs afoul of Sun bug 4910101 (which is referenced as
3781 a x86-only problem by Sun, probably because they do not use DWARF-2).
3782 A symptom of the problem is that you cannot compile C++ programs like
3783 @command{groff} 1.19.1 without getting messages similar to the following:
3786 ld: warning: relocation error: R_SPARC_UA32: @dots{}
3787 external symbolic relocation against non-allocatable section
3788 .debug_info cannot be processed at runtime: relocation ignored.
3791 To work around this problem, compile with @option{-gstabs+} instead of
3794 When configuring the GNU Multiple Precision Library (GMP) on a Solaris 7
3795 or later system, the canonical target triplet must be specified as the
3796 @command{build} parameter on the configure line:
3799 ./configure --build=sparc-sun-solaris2.7 --prefix=xxx --enable-mpfr
3805 @heading @anchor{sparc-sun-solaris27}sparc-sun-solaris2.7
3807 Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
3808 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
3809 and later, including all EGCS releases. Sun formerly recommended
3810 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
3811 recommend it only for people who use Sun's compilers.
3813 Here are some workarounds to this problem:
3816 Do not install Sun patch 107058-01 until after Sun releases a
3817 complete patch for bug 4210064. This is the simplest course to take,
3818 unless you must also use Sun's C compiler. Unfortunately 107058-01
3819 is preinstalled on some new Solaris 7-based hosts, so you may have to
3823 Copy the original, unpatched Solaris 7
3824 @command{/usr/ccs/bin/as} into
3825 @command{/usr/local/libexec/gcc/sparc-sun-solaris2.7/3.4/as},
3826 adjusting the latter name to fit your local conventions and software
3830 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
3831 both 107058-01 and 106950-03 installed has reported the bug with GCC
3832 and Sun's dynamic linker. This last course of action is riskiest,
3833 for two reasons. First, you must install 106950 on all hosts that
3834 run code generated by GCC; it doesn't suffice to install it only on
3835 the hosts that run GCC itself. Second, Sun says that 106950-03 is
3836 only a partial fix for bug 4210064, but Sun doesn't know whether the
3837 partial fix is adequate for GCC@. Revision -08 or later should fix
3838 the bug. The current (as of 2004-05-23) revision is -24, and is included in
3839 the Solaris 7 Recommended Patch Cluster.
3842 GCC 3.3 triggers a bug in version 5.0 Alpha 03/27/98 of the Sun assembler,
3843 which causes a bootstrap failure when linking the 64-bit shared version of
3844 libgcc. A typical error message is:
3847 ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o:
3848 symbol <unknown>: offset 0xffffffff7ec133e7 is non-aligned.
3851 This bug has been fixed in the final 5.0 version of the assembler.
3853 A similar problem was reported for version Sun WorkShop 6 99/08/18 of the
3854 Sun assembler, which causes a bootstrap failure with GCC 4.0.0:
3857 ld: fatal: relocation error: R_SPARC_DISP32:
3858 file .libs/libstdc++.lax/libsupc++convenience.a/vterminate.o:
3859 symbol <unknown>: offset 0xfccd33ad is non-aligned
3862 This bug has been fixed in more recent revisions of the assembler.
3867 @heading @anchor{sparc-x-linux}sparc-*-linux*
3869 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
3870 or newer on this platform. All earlier binutils and glibc
3871 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
3877 @heading @anchor{sparc64-x-solaris2}sparc64-*-solaris2*
3879 The following compiler flags must be specified in the configure
3880 step in order to bootstrap this target with the Sun compiler:
3883 % CC="cc -xildoff -xarch=v9" @var{srcdir}/configure [@var{options}] [@var{target}]
3886 @option{-xildoff} turns off the incremental linker, and @option{-xarch=v9}
3887 specifies the SPARC-V9 architecture to the Sun linker and assembler.
3892 @heading @anchor{sparcv9-x-solaris2}sparcv9-*-solaris2*
3894 This is a synonym for sparc64-*-solaris2*.
3899 @heading @anchor{x-x-sysv}*-*-sysv*
3900 On System V release 3, you may get this error message
3904 ld fatal: failed to write symbol name @var{something}
3905 in strings table for file @var{whatever}
3908 This probably indicates that the disk is full or your ulimit won't allow
3909 the file to be as large as it needs to be.
3911 This problem can also result because the kernel parameter @code{MAXUMEM}
3912 is too small. If so, you must regenerate the kernel and make the value
3913 much larger. The default value is reported to be 1024; a value of 32768
3914 is said to work. Smaller values may also work.
3916 On System V, if you get an error like this,
3919 /usr/local/lib/bison.simple: In function `yyparse':
3920 /usr/local/lib/bison.simple:625: virtual memory exhausted
3924 that too indicates a problem with disk space, ulimit, or @code{MAXUMEM}.
3926 On a System V release 4 system, make sure @file{/usr/bin} precedes
3927 @file{/usr/ucb} in @code{PATH}. The @command{cc} command in
3928 @file{/usr/ucb} uses libraries which have bugs.
3933 @heading @anchor{vax-dec-ultrix}vax-dec-ultrix
3934 Don't try compiling with VAX C (@command{vcc}). It produces incorrect code
3935 in some cases (for example, when @code{alloca} is used).
3940 @heading @anchor{x-x-vxworks}*-*-vxworks*
3941 Support for VxWorks is in flux. At present GCC supports @emph{only} the
3942 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC@.
3943 We welcome patches for other architectures supported by VxWorks 5.5.
3944 Support for VxWorks AE would also be welcome; we believe this is merely
3945 a matter of writing an appropriate ``configlette'' (see below). We are
3946 not interested in supporting older, a.out or COFF-based, versions of
3949 VxWorks comes with an older version of GCC installed in
3950 @file{@var{$WIND_BASE}/host}; we recommend you do not overwrite it.
3951 Choose an installation @var{prefix} entirely outside @var{$WIND_BASE}.
3952 Before running @command{configure}, create the directories @file{@var{prefix}}
3953 and @file{@var{prefix}/bin}. Link or copy the appropriate assembler,
3954 linker, etc.@: into @file{@var{prefix}/bin}, and set your @var{PATH} to
3955 include that directory while running both @command{configure} and
3958 You must give @command{configure} the
3959 @option{--with-headers=@var{$WIND_BASE}/target/h} switch so that it can
3960 find the VxWorks system headers. Since VxWorks is a cross compilation
3961 target only, you must also specify @option{--target=@var{target}}.
3962 @command{configure} will attempt to create the directory
3963 @file{@var{prefix}/@var{target}/sys-include} and copy files into it;
3964 make sure the user running @command{configure} has sufficient privilege
3967 GCC's exception handling runtime requires a special ``configlette''
3968 module, @file{contrib/gthr_supp_vxw_5x.c}. Follow the instructions in
3969 that file to add the module to your kernel build. (Future versions of
3970 VxWorks will incorporate this module.)
3975 @heading @anchor{x86-64-x-x}x86_64-*-*, amd64-*-*
3977 GCC supports the x86-64 architecture implemented by the AMD64 processor
3978 (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD@.
3979 On GNU/Linux the default is a bi-arch compiler which is able to generate
3980 both 64-bit x86-64 and 32-bit x86 code (via the @option{-m32} switch).
3985 @heading @anchor{xtensa-x-elf}xtensa-*-elf
3987 This target is intended for embedded Xtensa systems using the
3988 @samp{newlib} C library. It uses ELF but does not support shared
3989 objects. Designed-defined instructions specified via the
3990 Tensilica Instruction Extension (TIE) language are only supported
3991 through inline assembly.
3993 The Xtensa configuration information must be specified prior to
3994 building GCC@. The @file{include/xtensa-config.h} header
3995 file contains the configuration information. If you created your
3996 own Xtensa configuration with the Xtensa Processor Generator, the
3997 downloaded files include a customized copy of this header file,
3998 which you can use to replace the default header file.
4003 @heading @anchor{xtensa-x-linux}xtensa-*-linux*
4005 This target is for Xtensa systems running GNU/Linux. It supports ELF
4006 shared objects and the GNU C library (glibc). It also generates
4007 position-independent code (PIC) regardless of whether the
4008 @option{-fpic} or @option{-fPIC} options are used. In other
4009 respects, this target is the same as the
4010 @uref{#xtensa-*-elf,,@samp{xtensa-*-elf}} target.
4015 @heading @anchor{windows}Microsoft Windows (32-bit)
4017 Ports of GCC are included with the
4018 @uref{http://www.cygwin.com/,,Cygwin environment}.
4020 GCC will build under Cygwin without modification; it does not build
4021 with Microsoft's C++ compiler and there are no plans to make it do so.
4026 @heading @anchor{os2}OS/2
4028 GCC does not currently support OS/2. However, Andrew Zabolotny has been
4029 working on a generic OS/2 port with pgcc. The current code can be found
4030 at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
4035 @heading @anchor{older}Older systems
4037 GCC contains support files for many older (1980s and early
4038 1990s) Unix variants. For the most part, support for these systems
4039 has not been deliberately removed, but it has not been maintained for
4040 several years and may suffer from bitrot.
4042 Starting with GCC 3.1, each release has a list of ``obsoleted'' systems.
4043 Support for these systems is still present in that release, but
4044 @command{configure} will fail unless the @option{--enable-obsolete}
4045 option is given. Unless a maintainer steps forward, support for these
4046 systems will be removed from the next release of GCC@.
4048 Support for old systems as hosts for GCC can cause problems if the
4049 workarounds for compiler, library and operating system bugs affect the
4050 cleanliness or maintainability of the rest of GCC@. In some cases, to
4051 bring GCC up on such a system, if still possible with current GCC, may
4052 require first installing an old version of GCC which did work on that
4053 system, and using it to compile a more recent GCC, to avoid bugs in the
4054 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
4055 @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror
4056 sites}. Header bugs may generally be avoided using
4057 @command{fixincludes}, but bugs or deficiencies in libraries and the
4058 operating system may still cause problems.
4060 Support for older systems as targets for cross-compilation is less
4061 problematic than support for them as hosts for GCC; if an enthusiast
4062 wishes to make such a target work again (including resurrecting any of
4063 the targets that never worked with GCC 2, starting from the last CVS
4064 version before they were removed), patches
4065 @uref{../contribute.html,,following the usual requirements} would be
4066 likely to be accepted, since they should not affect the support for more
4069 For some systems, old versions of GNU binutils may also be useful,
4070 and are available from @file{pub/binutils/old-releases} on
4071 @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}.
4073 Some of the information on specific systems above relates to
4074 such older systems, but much of the information
4075 about GCC on such systems (which may no longer be applicable to
4076 current GCC) is to be found in the GCC texinfo manual.
4081 @heading @anchor{elf}all ELF targets (SVR4, Solaris 2, etc.)
4083 C++ support is significantly better on ELF targets if you use the
4084 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
4085 inlines, vtables and template instantiations will be discarded
4094 @uref{./index.html,,Return to the GCC Installation page}
4098 @c ***Old documentation******************************************************
4100 @include install-old.texi
4106 @uref{./index.html,,Return to the GCC Installation page}
4110 @c ***GFDL********************************************************************
4118 @uref{./index.html,,Return to the GCC Installation page}
4122 @c ***************************************************************************
4123 @c Part 6 The End of the Document
4125 @comment node-name, next, previous, up
4126 @node Concept Index, , GNU Free Documentation License, Top
4130 @unnumbered Concept Index