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 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 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.
291 @heading Tools/packages necessary for modifying GCC
294 @item autoconf versions 2.13 and 2.59
295 @itemx GNU m4 version 1.4 (or later)
297 Necessary when modifying @file{configure.ac}, @file{aclocal.m4}, etc.@:
298 to regenerate @file{configure} and @file{config.in} files. Most
299 directories require autoconf 2.59 (exactly), but the toplevel, @file{libf2c},
300 @file{libobjc}, @file{zlib}, and @file{libjava} (except for
301 @file{libjava/libltdl}) still require autoconf 2.13 (exactly).
303 @item automake versions 1.4-gcj and 1.7.9
305 Necessary when modifying a @file{Makefile.am} file to regenerate its
306 associated @file{Makefile.in}.
308 Much of GCC does not use automake, so directly edit the @file{Makefile.in}
309 file. Specifically this applies to the @file{gcc}, @file{intl},
310 @file{libf2c}, @file{libiberty}, @file{libobjc} directories as well as any
311 of their subdirectories.
313 The @file{libstdc++-v3}, @file{libjava/libltdl}, @file{fastjar} and
314 @file{libffi} directories require automake 1.7.9. However, the Java
315 directories, which include @file{boehm-gc}, @file{libjava}, and @file{zlib},
316 require a modified version of automake 1.4 downloadable from
317 @uref{ftp://gcc.gnu.org/pub/java/automake-gcj-1.4.tar.gz}.
319 @item gettext version 0.12 (or later)
321 Needed to regenerate @file{gcc.pot}.
323 @item gperf version 2.7.2 (or later)
325 Necessary when modifying @command{gperf} input files, e.g.@:
326 @file{gcc/cp/cfns.gperf} to regenerate its associated header file, e.g.@:
327 @file{gcc/cp/cfns.h}.
329 @item expect version ???
330 @itemx tcl version ???
331 @itemx dejagnu version ???
333 Necessary to run the GCC testsuite.
335 @item autogen version 5.5.4 (or later) and
336 @itemx guile version 1.4.1 (or later)
338 Necessary to regenerate @file{fixinc/fixincl.x} from
339 @file{fixinc/inclhack.def} and @file{fixinc/*.tpl}.
341 Necessary to run the @file{fixinc} @command{make check}.
343 Necessary to regenerate the top level @file{Makefile.in} file from
344 @file{Makefile.tpl} and @file{Makefile.def}.
346 @item GNU Bison version 1.28 (or later)
347 Berkeley @command{yacc} (@command{byacc}) is also reported to work other
350 Necessary when modifying @file{*.y} files.
352 Necessary to build GCC during development because the generated output
353 files are not included in the CVS repository. They are included in
356 @item Flex version 2.5.4 (or later)
358 Necessary when modifying @file{*.l} files.
360 Necessary to build GCC during development because the generated output
361 files are not included in the CVS repository. They are included in
364 @item Texinfo version 4.2 (or later)
366 Necessary for running @command{makeinfo} when modifying @file{*.texi}
367 files to test your changes.
369 Necessary to build GCC documentation during development because the
370 generated output files are not included in the CVS repository. They are
371 included in releases.
373 @item @TeX{} (any working version)
375 Necessary for running @command{texi2dvi}, used when running
376 @command{make dvi} to create DVI files.
378 @item cvs version 1.10 (or later)
379 @itemx ssh (any version)
381 Necessary to access the CVS repository. Public releases and weekly
382 snapshots of the development sources are also available via FTP.
384 @item perl version 5.6.1 (or later)
386 Necessary when regenerating @file{Makefile} dependencies in libiberty.
387 Necessary when regenerating @file{libiberty/functions.texi}.
388 Necessary when generating manpages from Texinfo manuals.
389 Used by various scripts to generate some files included in CVS (mainly
390 Unicode-related and rarely changing) from source tables.
392 @item GNU diffutils version 2.7 (or later)
394 Necessary when creating changes to GCC source code to submit for review.
396 @item patch version 2.5.4 (or later)
398 Necessary when applying patches, created with @command{diff}, to one's
408 @uref{./index.html,,Return to the GCC Installation page}
412 @c ***Downloading the source**************************************************
414 @comment node-name, next, previous, up
415 @node Downloading the source, Configuration, Prerequisites, Installing GCC
419 @chapter Downloading GCC
421 @cindex Downloading GCC
422 @cindex Downloading the Source
424 GCC is distributed via @uref{http://gcc.gnu.org/cvs.html,,CVS} and FTP
425 tarballs compressed with @command{gzip} or
426 @command{bzip2}. It is possible to download a full distribution or specific
429 Please refer to our @uref{http://gcc.gnu.org/releases.html,,releases web page}
430 for information on how to obtain GCC@.
432 The full distribution includes the C, C++, Objective-C, Fortran, Java,
433 and Ada (in case of GCC 3.1 and later) compilers. The full distribution
434 also includes runtime libraries for C++, Objective-C, Fortran, and Java.
435 In GCC 3.0 and later versions, GNU compiler testsuites are also included
436 in the full distribution.
438 If you choose to download specific components, you must download the core
439 GCC distribution plus any language specific distributions you wish to
440 use. The core distribution includes the C language front end as well as the
441 shared components. Each language has a tarball which includes the language
442 front end as well as the language runtime (when appropriate).
444 Unpack the core distribution as well as any language specific
445 distributions in the same directory.
447 If you also intend to build binutils (either to upgrade an existing
448 installation or for use in place of the corresponding tools of your
449 OS), unpack the binutils distribution either in the same directory or
450 a separate one. In the latter case, add symbolic links to any
451 components of the binutils you intend to build alongside the compiler
452 (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
453 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
460 @uref{./index.html,,Return to the GCC Installation page}
464 @c ***Configuration***********************************************************
466 @comment node-name, next, previous, up
467 @node Configuration, Building, Downloading the source, Installing GCC
471 @chapter Installing GCC: Configuration
473 @cindex Configuration
474 @cindex Installing GCC: Configuration
476 Like most GNU software, GCC must be configured before it can be built.
477 This document describes the recommended configuration procedure
478 for both native and cross targets.
480 We use @var{srcdir} to refer to the toplevel source directory for
481 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
483 If you obtained the sources via CVS, @var{srcdir} must refer to the top
484 @file{gcc} directory, the one where the @file{MAINTAINERS} can be found,
485 and not its @file{gcc} subdirectory, otherwise the build will fail.
487 If either @var{srcdir} or @var{objdir} is located on an automounted NFS
488 file system, the shell's built-in @command{pwd} command will return
489 temporary pathnames. Using these can lead to various sorts of build
490 problems. To avoid this issue, set the @env{PWDCMD} environment
491 variable to an automounter-aware @command{pwd} command, e.g.,
492 @command{pawd} or @samp{amq -w}, during the configuration and build
495 First, we @strong{highly} recommend that GCC be built into a
496 separate directory than the sources which does @strong{not} reside
497 within the source tree. This is how we generally build GCC; building
498 where @var{srcdir} == @var{objdir} should still work, but doesn't
499 get extensive testing; building where @var{objdir} is a subdirectory
500 of @var{srcdir} is unsupported.
502 If you have previously built GCC in the same directory for a
503 different target machine, do @samp{make distclean} to delete all files
504 that might be invalid. One of the files this deletes is @file{Makefile};
505 if @samp{make distclean} complains that @file{Makefile} does not exist
506 or issues a message like ``don't know how to make distclean'' it probably
507 means that the directory is already suitably clean. However, with the
508 recommended method of building in a separate @var{objdir}, you should
509 simply use a different @var{objdir} for each target.
511 Second, when configuring a native system, either @command{cc} or
512 @command{gcc} must be in your path or you must set @env{CC} in
513 your environment before running configure. Otherwise the configuration
516 Note that the bootstrap compiler and the resulting GCC must be link
517 compatible, else the bootstrap will fail with linker errors about
518 incompatible object file formats. Several multilibed targets are
519 affected by this requirement, see
521 @ref{Specific, host/target specific installation notes}.
524 @uref{specific.html,,host/target specific installation notes}.
532 % @var{srcdir}/configure [@var{options}] [@var{target}]
536 @heading Target specification
539 GCC has code to correctly determine the correct value for @var{target}
540 for nearly all native systems. Therefore, we highly recommend you not
541 provide a configure target when configuring a native compiler.
544 @var{target} must be specified as @option{--target=@var{target}}
545 when configuring a cross compiler; examples of valid targets would be
546 m68k-coff, sh-elf, etc.
549 Specifying just @var{target} instead of @option{--target=@var{target}}
550 implies that the host defaults to @var{target}.
554 @heading Options specification
556 Use @var{options} to override several configure time options for
557 GCC@. A list of supported @var{options} follows; @samp{configure
558 --help} may list other options, but those not listed below may not
559 work and should not normally be used.
561 Note that each @option{--enable} option has a corresponding
562 @option{--disable} option and that each @option{--with} option has a
563 corresponding @option{--without} option.
566 @item --prefix=@var{dirname}
567 Specify the toplevel installation
568 directory. This is the recommended way to install the tools into a directory
569 other than the default. The toplevel installation directory defaults to
572 We @strong{highly} recommend against @var{dirname} being the same or a
573 subdirectory of @var{objdir} or vice versa. If specifying a directory
574 beneath a user's home directory tree, some shells will not expand
575 @var{dirname} correctly if it contains the @samp{~} metacharacter; use
578 The following standard @command{autoconf} options are supported. Normally you
579 should not need to use these options.
581 @item --exec-prefix=@var{dirname}
582 Specify the toplevel installation directory for architecture-dependent
583 files. The default is @file{@var{prefix}}.
585 @item --bindir=@var{dirname}
586 Specify the installation directory for the executables called by users
587 (such as @command{gcc} and @command{g++}). The default is
588 @file{@var{exec-prefix}/bin}.
590 @item --libdir=@var{dirname}
591 Specify the installation directory for object code libraries and
592 internal data files of GCC@. The default is @file{@var{exec-prefix}/lib}.
594 @item --libexecdir=@var{dirname}
595 Specify the installation directory for internal executables of GCC@.
596 The default is @file{@var{exec-prefix}/libexec}.
598 @item --with-slibdir=@var{dirname}
599 Specify the installation directory for the shared libgcc library. The
600 default is @file{@var{libdir}}.
602 @item --infodir=@var{dirname}
603 Specify the installation directory for documentation in info format.
604 The default is @file{@var{prefix}/info}.
606 @item --datadir=@var{dirname}
607 Specify the installation directory for some architecture-independent
608 data files referenced by GCC@. The default is @file{@var{prefix}/share}.
610 @item --mandir=@var{dirname}
611 Specify the installation directory for manual pages. The default is
612 @file{@var{prefix}/man}. (Note that the manual pages are only extracts from
613 the full GCC manuals, which are provided in Texinfo format. The manpages
614 are derived by an automatic conversion process from parts of the full
617 @item --with-gxx-include-dir=@var{dirname}
619 the installation directory for G++ header files. The default is
620 @file{@var{prefix}/include/c++/@var{version}}.
624 @item --program-prefix=@var{prefix}
625 GCC supports some transformations of the names of its programs when
626 installing them. This option prepends @var{prefix} to the names of
627 programs to install in @var{bindir} (see above). For example, specifying
628 @option{--program-prefix=foo-} would result in @samp{gcc}
629 being installed as @file{/usr/local/bin/foo-gcc}.
631 @item --program-suffix=@var{suffix}
632 Appends @var{suffix} to the names of programs to install in @var{bindir}
633 (see above). For example, specifying @option{--program-suffix=-3.1}
634 would result in @samp{gcc} being installed as
635 @file{/usr/local/bin/gcc-3.1}.
637 @item --program-transform-name=@var{pattern}
638 Applies the @samp{sed} script @var{pattern} to be applied to the names
639 of programs to install in @var{bindir} (see above). @var{pattern} has to
640 consist of one or more basic @samp{sed} editing commands, separated by
641 semicolons. For example, if you want the @samp{gcc} program name to be
642 transformed to the installed program @file{/usr/local/bin/myowngcc} and
643 the @samp{g++} program name to be transformed to
644 @file{/usr/local/bin/gspecial++} without changing other program names,
645 you could use the pattern
646 @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}
647 to achieve this effect.
649 All three options can be combined and used together, resulting in more
650 complex conversion patterns. As a basic rule, @var{prefix} (and
651 @var{suffix}) are prepended (appended) before further transformations
652 can happen with a special transformation script @var{pattern}.
654 As currently implemented, this option only takes effect for native
655 builds; cross compiler binaries' names are not transformed even when a
656 transformation is explicitly asked for by one of these options.
658 For native builds, some of the installed programs are also installed
659 with the target alias in front of their name, as in
660 @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
661 before the target alias is prepended to the name - so, specifying
662 @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
663 resulting binary would be installed as
664 @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.
666 As a last shortcoming, none of the installed Ada programs are
667 transformed yet, which will be fixed in some time.
669 @item --with-local-prefix=@var{dirname}
671 installation directory for local include files. The default is
672 @file{/usr/local}. Specify this option if you want the compiler to
673 search directory @file{@var{dirname}/include} for locally installed
674 header files @emph{instead} of @file{/usr/local/include}.
676 You should specify @option{--with-local-prefix} @strong{only} if your
677 site has a different convention (not @file{/usr/local}) for where to put
680 The default value for @option{--with-local-prefix} is @file{/usr/local}
681 regardless of the value of @option{--prefix}. Specifying
682 @option{--prefix} has no effect on which directory GCC searches for
683 local header files. This may seem counterintuitive, but actually it is
686 The purpose of @option{--prefix} is to specify where to @emph{install
687 GCC}. The local header files in @file{/usr/local/include}---if you put
688 any in that directory---are not part of GCC@. They are part of other
689 programs---perhaps many others. (GCC installs its own header files in
690 another directory which is based on the @option{--prefix} value.)
692 Both the local-prefix include directory and the GCC-prefix include
693 directory are part of GCC's "system include" directories. Although these
694 two directories are not fixed, they need to be searched in the proper
695 order for the correct processing of the include_next directive. The
696 local-prefix include directory is searched before the GCC-prefix
697 include directory. Another characteristic of system include directories
698 is that pedantic warnings are turned off for headers in these directories.
700 Some autoconf macros add @option{-I @var{directory}} options to the
701 compiler command line, to ensure that directories containing installed
702 packages' headers are searched. When @var{directory} is one of GCC's
703 system include directories, GCC will ignore the option so that system
704 directories continue to be processed in the correct order. This
705 may result in a search order different from what was specified but the
706 directory will still be searched.
708 GCC automatically searches for ordinary libraries using
709 @env{GCC_EXEC_PREFIX}. Thus, when the same installation prefix is
710 used for both GCC and packages, GCC will automatically search for
711 both headers and libraries. This provides a configuration that is
712 easy to use. GCC behaves in a manner similar to that when it is
713 installed as a system compiler in @file{/usr}.
715 Sites that need to install multiple versions of GCC may not want to
716 use the above simple configuration. It is possible to use the
717 @option{--program-prefix}, @option{--program-suffix} and
718 @option{--program-transform-name} options to install multiple versions
719 into a single directory, but it may be simpler to use different prefixes
720 and the @option{--with-local-prefix} option to specify the location of the
721 site-specific files for each version. It will then be necessary for
722 users to specify explicitly the location of local site libraries
723 (e.g., with @env{LIBRARY_PATH}).
725 The same value can be used for both @option{--with-local-prefix} and
726 @option{--prefix} provided it is not @file{/usr}. This can be used
727 to avoid the default search of @file{/usr/local/include}.
729 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
730 The directory you use for @option{--with-local-prefix} @strong{must not}
731 contain any of the system's standard header files. If it did contain
732 them, certain programs would be miscompiled (including GNU Emacs, on
733 certain targets), because this would override and nullify the header
734 file corrections made by the @command{fixincludes} script.
736 Indications are that people who use this option use it based on mistaken
737 ideas of what it is for. People use it as if it specified where to
738 install part of GCC@. Perhaps they make this assumption because
739 installing GCC creates the directory.
741 @item --enable-shared[=@var{package}[,@dots{}]]
742 Build shared versions of libraries, if shared libraries are supported on
743 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
744 are enabled by default on all platforms that support shared libraries,
745 except for @samp{libobjc} which is built as a static library only by
748 If a list of packages is given as an argument, build shared libraries
749 only for the listed packages. For other packages, only static libraries
750 will be built. Package names currently recognized in the GCC tree are
751 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
752 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc} and
753 @samp{libjava}. Note that @samp{libobjc} does not recognize itself by
754 any name, so, if you list package names in @option{--enable-shared},
755 you will only get static Objective-C libraries. @samp{libf2c} and
756 @samp{libiberty} do not support shared libraries at all.
758 Use @option{--disable-shared} to build only static libraries. Note that
759 @option{--disable-shared} does not accept a list of package names as
760 argument, only @option{--enable-shared} does.
762 @item @anchor{with-gnu-as}--with-gnu-as
763 Specify that the compiler should assume that the
764 assembler it finds is the GNU assembler. However, this does not modify
765 the rules to find an assembler and will result in confusion if the
766 assembler found is not actually the GNU assembler. (Confusion may also
767 result if the compiler finds the GNU assembler but has not been
768 configured with @option{--with-gnu-as}.) If you have more than one
769 assembler installed on your system, you may want to use this option in
770 connection with @option{--with-as=@var{pathname}}.
772 The following systems are the only ones where it makes a difference
773 whether you use the GNU assembler. On any other system,
774 @option{--with-gnu-as} has no effect.
777 @item @samp{hppa1.0-@var{any}-@var{any}}
778 @item @samp{hppa1.1-@var{any}-@var{any}}
779 @item @samp{i386-@var{any}-sysv}
780 @item @samp{m68k-bull-sysv}
781 @item @samp{m68k-hp-hpux}
782 @item @samp{m68000-hp-hpux}
783 @item @samp{m68000-att-sysv}
784 @item @samp{@var{any}-lynx-lynxos}
785 @item @samp{mips-@var{any}}
786 @item @samp{sparc-sun-solaris2.@var{any}}
787 @item @samp{sparc64-@var{any}-solaris2.@var{any}}
790 On the systems listed above (except for the HP-PA, the SPARC, for ISC on
791 the 386, and for @samp{mips-sgi-irix5.*}), if you use the GNU assembler,
792 you should also use the GNU linker (and specify @option{--with-gnu-ld}).
794 @item @anchor{with-as}--with-as=@var{pathname}
796 compiler should use the assembler pointed to by @var{pathname}, rather
797 than the one found by the standard rules to find an assembler, which
801 Check the @file{@var{libexec}/gcc/@var{target}/@var{version}}
802 directory, where @var{libexec} defaults to
803 @file{@var{exec-prefix}/libexec} and @var{exec-prefix} defaults to
804 @var{prefix} which defaults to @file{/usr/local} unless overridden by
805 the @option{--prefix=@var{pathname}} switch described
806 above. @var{target} is the target system triple, such as
807 @samp{sparc-sun-solaris2.7}, and @var{version} denotes the GCC
808 version, such as 3.0.
810 Check operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
813 Note that these rules do not check for the value of @env{PATH}. You may
814 want to use @option{--with-as} if no assembler is installed in the
815 directories listed above, or if you have multiple assemblers installed
816 and want to choose one that is not found by the above rules.
818 @item @anchor{with-gnu-ld}--with-gnu-ld
819 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
822 @item --with-ld=@var{pathname}
823 Same as @uref{#with-as,,@option{--with-as}}
827 Specify that stabs debugging
828 information should be used instead of whatever format the host normally
829 uses. Normally GCC uses the same debug format as the host system.
831 On MIPS based systems and on Alphas, you must specify whether you want
832 GCC to create the normal ECOFF debugging format, or to use BSD-style
833 stabs passed through the ECOFF symbol table. The normal ECOFF debug
834 format cannot fully handle languages other than C@. BSD stabs format can
835 handle other languages, but it only works with the GNU debugger GDB@.
837 Normally, GCC uses the ECOFF debugging format by default; if you
838 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
840 No matter which default you choose when you configure GCC, the user
841 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
842 the debug format for a particular compilation.
844 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
845 @option{--with-gas} is used. It selects use of stabs debugging
846 information embedded in COFF output. This kind of debugging information
847 supports C++ well; ordinary COFF debugging information does not.
849 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
850 selects use of stabs debugging information embedded in ELF output. The
851 C++ compiler currently (2.6.0) does not support the DWARF debugging
852 information normally used on 386 SVR4 platforms; stabs provide a
853 workable alternative. This requires gas and gdb, as the normal SVR4
854 tools can not generate or interpret stabs.
856 @item --disable-multilib
857 Specify that multiple target
858 libraries to support different target variants, calling
859 conventions, etc should not be built. The default is to build a
860 predefined set of them.
862 Some targets provide finer-grained control over which multilibs are built
863 (e.g., @option{--disable-softfloat}):
869 fpu, 26bit, underscore, interwork, biendian, nofmult.
872 softfloat, m68881, m68000, m68020.
875 single-float, biendian, softfloat.
877 @item powerpc*-*-*, rs6000*-*-*
878 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
883 @item --enable-threads
884 Specify that the target
885 supports threads. This affects the Objective-C compiler and runtime
886 library, and exception handling for other languages like C++ and Java.
887 On some systems, this is the default.
889 In general, the best (and, in many cases, the only known) threading
890 model available will be configured for use. Beware that on some
891 systems, GCC has not been taught what threading models are generally
892 available for the system. In this case, @option{--enable-threads} is an
893 alias for @option{--enable-threads=single}.
895 @item --disable-threads
896 Specify that threading support should be disabled for the system.
897 This is an alias for @option{--enable-threads=single}.
899 @item --enable-threads=@var{lib}
901 @var{lib} is the thread support library. This affects the Objective-C
902 compiler and runtime library, and exception handling for other languages
903 like C++ and Java. The possibilities for @var{lib} are:
911 Ada tasking support. For non-Ada programs, this setting is equivalent
912 to @samp{single}. When used in conjunction with the Ada run time, it
913 causes GCC to use the same thread primitives as Ada uses. This option
914 is necessary when using both Ada and the back end exception handling,
915 which is the default for most Ada targets.
917 Generic MACH thread support, known to work on NeXTSTEP@. (Please note
918 that the file needed to support this configuration, @file{gthr-mach.h}, is
919 missing and thus this setting will cause a known bootstrap failure.)
921 This is an alias for @samp{single}.
923 Generic POSIX thread support.
925 RTEMS thread support.
927 Disable thread support, should work for all platforms.
929 Sun Solaris 2 thread support.
931 VxWorks thread support.
933 Microsoft Win32 API thread support.
936 @item --with-cpu=@var{cpu}
937 Specify which cpu variant the compiler should generate code for by default.
938 @var{cpu} will be used as the default value of the @option{-mcpu=} switch.
939 This option is only supported on some targets, including ARM, i386, PowerPC,
942 @item --with-schedule=@var{cpu}
943 @itemx --with-arch=@var{cpu}
944 @itemx --with-tune=@var{cpu}
945 @itemx --with-abi=@var{abi}
946 @itemx --with-fpu=@var{type}
947 @itemx --with-float=@var{type}
948 These configure options provide default values for the @option{-mschedule=},
949 @option{-march=}, @option{-mtune=}, @option{-mabi=}, and @option{-mfpu=}
950 options and for @option{-mhard-float} or @option{-msoft-float}. As with
951 @option{--with-cpu}, which switches will be accepted and acceptable values
952 of the arguments depend on the target.
954 @item --enable-altivec
955 Specify that the target supports AltiVec vector enhancements. This
956 option will adjust the ABI for AltiVec enhancements, as well as generate
957 AltiVec code when appropriate. This option is only available for
960 @item --enable-__cxa_atexit
961 Define if you want to use __cxa_atexit, rather than atexit, to
962 register C++ destructors for local statics and global objects.
963 This is essential for fully standards-compliant handling of
964 destructors, but requires __cxa_atexit in libc. This option is currently
965 only available on systems with GNU libc. When enabled, this will cause
966 @option{-fuse-cxa-exit} to be passed by default.
968 @item --enable-target-optspace
970 libraries should be optimized for code space instead of code speed.
971 This is the default for the m32r platform.
974 Specify that a user visible @command{cpp} program should not be installed.
976 @item --with-cpp-install-dir=@var{dirname}
977 Specify that the user visible @command{cpp} program should be installed
978 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
980 @item --enable-initfini-array
981 Force the use of sections @code{.init_array} and @code{.fini_array}
982 (instead of @code{.init} and @code{.fini}) for constructors and
983 destructors. Option @option{--disable-initfini-array} has the
984 opposite effect. If neither option is specified, the configure script
985 will try to guess whether the @code{.init_array} and
986 @code{.fini_array} sections are supported and, if they are, use them.
988 @item --enable-maintainer-mode
990 regenerate the GCC master message catalog @file{gcc.pot} are normally
991 disabled. This is because it can only be rebuilt if the complete source
992 tree is present. If you have changed the sources and want to rebuild the
993 catalog, configuring with @option{--enable-maintainer-mode} will enable
994 this. Note that you need a recent version of the @code{gettext} tools
997 @item --enable-generated-files-in-srcdir
998 Neither the .c and .h files that are generated from bison and flex nor the
999 info manuals and man pages that are built from the .texi files are present
1000 in the CVS development tree. When building GCC from that development tree,
1001 or from a snapshot which are created from CVS, then those generated files
1002 are placed in your build directory, which allows for the source to be in a
1005 If you configure with @option{--enable-generated-files-in-srcdir} then those
1006 generated files will go into the source directory. This is mainly intended
1007 for generating release or prerelease tarballs of the GCC sources, since it
1008 is not a requirement that the users of source releases to have flex, bison, or
1011 @item --enable-version-specific-runtime-libs
1013 that runtime libraries should be installed in the compiler specific
1014 subdirectory (@file{@var{libdir}/gcc}) rather than the usual places. In
1015 addition, @samp{libstdc++}'s include files will be installed into
1016 @file{@var{libdir}} unless you overruled it by using
1017 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
1018 particularly useful if you intend to use several versions of GCC in
1019 parallel. This is currently supported by @samp{libf2c} and
1020 @samp{libstdc++}, and is the default for @samp{libobjc} which cannot be
1021 changed in this case.
1023 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
1024 Specify that only a particular subset of compilers and
1025 their runtime libraries should be built. For a list of valid values for
1026 @var{langN} you can issue the following command in the
1027 @file{gcc} directory of your GCC source tree:@*
1029 grep language= */config-lang.in
1031 Currently, you can use any of the following:
1032 @code{ada}, @code{c}, @code{c++}, @code{f77}, @code{java}, @code{objc}.
1033 Building the Ada compiler has special requirements, see below.@*
1034 If you do not pass this flag, all languages available in the @file{gcc}
1035 sub-tree will be configured. Re-defining @code{LANGUAGES} when calling
1036 @samp{make bootstrap} @strong{does not} work anymore, as those
1037 language sub-directories might not have been configured!
1039 @item --disable-libada
1040 Specify that the run-time libraries and tools used by GNAT should not
1041 be built. This can be useful for debugging, or for compatibility with
1042 previous Ada build procedures, when it was required to explicitly
1043 do a @samp{make -C gcc gnatlib_and_tools}.
1046 Specify that the compiler should
1047 use DWARF 2 debugging information as the default.
1049 @item --enable-win32-registry
1050 @itemx --enable-win32-registry=@var{key}
1051 @itemx --disable-win32-registry
1052 The @option{--enable-win32-registry} option enables Microsoft Windows-hosted GCC
1053 to look up installations paths in the registry using the following key:
1056 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
1059 @var{key} defaults to GCC version number, and can be overridden by the
1060 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
1061 who use custom installers are encouraged to provide a different key,
1062 perhaps one comprised of vendor name and GCC version number, to
1063 avoid conflict with existing installations. This feature is enabled
1064 by default, and can be disabled by @option{--disable-win32-registry}
1065 option. This option has no effect on the other hosts.
1068 Specify that the machine does not have a floating point unit. This
1069 option only applies to @samp{m68k-sun-sunos@var{n}}. On any other
1070 system, @option{--nfp} has no effect.
1072 @item --enable-werror
1073 @itemx --disable-werror
1074 @itemx --enable-werror=yes
1075 @itemx --enable-werror=no
1076 When you specify this option, it controls whether certain files in the
1077 compiler are built with @option{-Werror} in bootstrap stage2 and later.
1078 If you don't specify it, @option{-Werror} is turned on for the main
1079 development trunk. However it defaults to off for release branches and
1080 final releases. The specific files which get @option{-Werror} are
1081 controlled by the Makefiles.
1083 @item --enable-checking
1084 @itemx --enable-checking=@var{list}
1085 When you specify this option, the compiler is built to perform checking
1086 of tree node types when referencing fields of that node, and some other
1087 internal consistency checks. This does not change the generated code,
1088 but adds error checking within the compiler. This will slow down the
1089 compiler and may only work properly if you are building the compiler
1090 with GCC@. This is on by default when building from CVS or snapshots,
1091 but off for releases. More control over the checks may be had by
1092 specifying @var{list}; the categories of checks available are
1093 @samp{misc}, @samp{tree}, @samp{gc}, @samp{rtl}, @samp{rtlflag},
1094 @samp{fold}, @samp{gcac} and @samp{valgrind}. The check @samp{valgrind}
1095 requires the external @command{valgrind} simulator, available from
1096 @uref{http://valgrind.kde.org/}. The default when @var{list} is
1097 not specified is @samp{misc,tree,gc,rtlflag}; the checks @samp{rtl},
1098 @samp{gcac} and @samp{valgrind} are very expensive.
1100 @item --enable-coverage
1101 @itemx --enable-coverage=@var{level}
1102 With this option, the compiler is built to collect self coverage
1103 information, every time it is run. This is for internal development
1104 purposes, and only works when the compiler is being built with gcc. The
1105 @var{level} argument controls whether the compiler is built optimized or
1106 not, values are @samp{opt} and @samp{noopt}. For coverage analysis you
1107 want to disable optimization, for performance analysis you want to
1108 enable optimization. When coverage is enabled, the default level is
1109 without optimization.
1111 @item --enable-gather-detailed-mem-stats
1112 When this option is specified more detailed information on memory
1113 allocation is gathered. This information is printed when using
1114 @option{-fmem-report}.
1117 @itemx --disable-nls
1118 The @option{--enable-nls} option enables Native Language Support (NLS),
1119 which lets GCC output diagnostics in languages other than American
1120 English. Native Language Support is enabled by default if not doing a
1121 canadian cross build. The @option{--disable-nls} option disables NLS@.
1123 @item --with-included-gettext
1124 If NLS is enabled, the @option{--with-included-gettext} option causes the build
1125 procedure to prefer its copy of GNU @command{gettext}.
1127 @item --with-catgets
1128 If NLS is enabled, and if the host lacks @code{gettext} but has the
1129 inferior @code{catgets} interface, the GCC build procedure normally
1130 ignores @code{catgets} and instead uses GCC's copy of the GNU
1131 @code{gettext} library. The @option{--with-catgets} option causes the
1132 build procedure to use the host's @code{catgets} in this situation.
1134 @item --with-libiconv-prefix=@var{dir}
1135 Search for libiconv header files in @file{@var{dir}/include} and
1136 libiconv library files in @file{@var{dir}/lib}.
1138 @item --enable-obsolete
1139 Enable configuration for an obsoleted system. If you attempt to
1140 configure GCC for a system (build, host, or target) which has been
1141 obsoleted, and you do not specify this flag, configure will halt with an
1144 All support for systems which have been obsoleted in one release of GCC
1145 is removed entirely in the next major release, unless someone steps
1146 forward to maintain the port.
1149 @subheading Cross-Compiler-Specific Options
1150 The following options only apply to building cross compilers.
1152 @item --with-sysroot
1153 @itemx --with-sysroot=@var{dir}
1154 Tells GCC to consider @var{dir} as the root of a tree that contains a
1155 (subset of) the root filesystem of the target operating system.
1156 Target system headers, libraries and run-time object files will be
1157 searched in there. The specified directory is not copied into the
1158 install tree, unlike the options @option{--with-headers} and
1159 @option{--with-libs} that this option obsoletes. The default value,
1160 in case @option{--with-sysroot} is not given an argument, is
1161 @option{$@{gcc_tooldir@}/sys-root}. If the specified directory is a
1162 subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to
1163 the GCC binaries if the installation tree is moved.
1165 @item --with-headers
1166 @itemx --with-headers=@var{dir}
1167 Deprecated in favor of @option{--with-sysroot}.
1168 Specifies that target headers are available when building a cross compiler.
1169 The @var{dir} argument specifies a directory which has the target include
1170 files. These include files will be copied into the @file{gcc} install
1171 directory. @emph{This option with the @var{dir} argument is required} when
1172 building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include}
1173 doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does
1174 pre-exist, the @var{dir} argument may be omitted. @command{fixincludes}
1175 will be run on these files to make them compatible with GCC.
1177 @item --without-headers
1178 Tells GCC not use any target headers from a libc when building a cross
1179 compiler. When crossing to GNU/Linux, you need the headers so GCC
1180 can build the exception handling for libgcc.
1181 See @uref{http://www.objsw.com/CrossGCC/,,CrossGCC} for more information
1185 @itemx --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
1186 Deprecated in favor of @option{--with-sysroot}.
1187 Specifies a list of directories which contain the target runtime
1188 libraries. These libraries will be copied into the @file{gcc} install
1189 directory. If the directory list is omitted, this option has no
1192 Specifies that @samp{newlib} is
1193 being used as the target C library. This causes @code{__eprintf} to be
1194 omitted from @file{libgcc.a} on the assumption that it will be provided by
1198 @subheading Java-Specific Options
1200 The following option applies to the build of the Java front end.
1203 @item --disable-libgcj
1204 Specify that the run-time libraries
1205 used by GCJ should not be built. This is useful in case you intend
1206 to use GCJ with some other run-time, or you're going to install it
1207 separately, or it just happens not to build on your particular
1208 machine. In general, if the Java front end is enabled, the GCJ
1209 libraries will be enabled too, unless they're known to not work on
1210 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
1211 may need to port it; in this case, before modifying the top-level
1212 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
1213 you may use @option{--enable-libgcj} to override the default.
1217 The following options apply to building @samp{libgcj}.
1219 @subsubheading General Options
1222 @item --disable-getenv-properties
1223 Don't set system properties from @env{GCJ_PROPERTIES}.
1225 @item --enable-hash-synchronization
1226 Use a global hash table for monitor locks. Ordinarily,
1227 @samp{libgcj}'s @samp{configure} script automatically makes
1228 the correct choice for this option for your platform. Only use
1229 this if you know you need the library to be configured differently.
1231 @item --enable-interpreter
1232 Enable the Java interpreter. The interpreter is automatically
1233 enabled by default on all platforms that support it. This option
1234 is really only useful if you want to disable the interpreter
1235 (using @option{--disable-interpreter}).
1237 @item --disable-java-net
1238 Disable java.net. This disables the native part of java.net only,
1239 using non-functional stubs for native method implementations.
1241 @item --disable-jvmpi
1242 Disable JVMPI support.
1245 Enable runtime eCos target support.
1247 @item --without-libffi
1248 Don't use @samp{libffi}. This will disable the interpreter and JNI
1249 support as well, as these require @samp{libffi} to work.
1251 @item --enable-libgcj-debug
1252 Enable runtime debugging code.
1254 @item --enable-libgcj-multifile
1255 If specified, causes all @file{.java} source files to be
1256 compiled into @file{.class} files in one invocation of
1257 @samp{gcj}. This can speed up build time, but is more
1258 resource-intensive. If this option is unspecified or
1259 disabled, @samp{gcj} is invoked once for each @file{.java}
1260 file to compile into a @file{.class} file.
1262 @item --with-libiconv-prefix=DIR
1263 Search for libiconv in @file{DIR/include} and @file{DIR/lib}.
1265 @item --enable-sjlj-exceptions
1266 Force use of @code{builtin_setjmp} for exceptions. @samp{configure}
1267 ordinarily picks the correct value based on the platform. Only use
1268 this option if you are sure you need a different setting.
1270 @item --with-system-zlib
1271 Use installed @samp{zlib} rather than that included with GCC@.
1273 @item --with-win32-nlsapi=ansi, unicows or unicode
1274 Indicates how MinGW @samp{libgcj} translates between UNICODE
1275 characters and the Win32 API.
1278 Use the single-byte @code{char} and the Win32 A functions natively,
1279 translating to and from UNICODE when using these functions. If
1280 unspecified, this is the default.
1283 Use the @code{WCHAR} and Win32 W functions natively. Adds
1284 @code{-lunicows} to @file{libgcj.spec} to link with @samp{libunicows}.
1285 @file{unicows.dll} needs to be deployed on Microsoft Windows 9X machines
1286 running built executables. @file{libunicows.a}, an open-source
1287 import library around Microsoft's @code{unicows.dll}, is obtained from
1288 @uref{http://libunicows.sourceforge.net/}, which also gives details
1289 on getting @file{unicows.dll} from Microsoft.
1292 Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not}
1293 add @code{-lunicows} to @file{libgcj.spec}. The built executables will
1294 only run on Microsoft Windows NT and above.
1298 @subsubheading AWT-Specific Options
1302 Use the X Window System.
1304 @item --enable-java-awt=PEER(S)
1305 Specifies the AWT peer library or libraries to build alongside
1306 @samp{libgcj}. If this option is unspecified or disabled, AWT
1307 will be non-functional. Current valid values are @option{gtk} and
1308 @option{xlib}. Multiple libraries should be separated by a
1309 comma (i.e. @option{--enable-java-awt=gtk,xlib}).
1311 @item --enable-gtk-cairo
1312 Build the cairo Graphics2D implementation on GTK.
1314 @item --enable-java-gc=TYPE
1315 Choose garbage collector. Defaults to @option{boehm} if unspecified.
1317 @item --disable-gtktest
1318 Do not try to compile and run a test GTK+ program.
1320 @item --disable-glibtest
1321 Do not try to compile and run a test GLIB program.
1323 @item --with-libart-prefix=PFX
1324 Prefix where libart is installed (optional).
1326 @item --with-libart-exec-prefix=PFX
1327 Exec prefix where libart is installed (optional).
1329 @item --disable-libarttest
1330 Do not try to compile and run a test libart program.
1339 @uref{./index.html,,Return to the GCC Installation page}
1343 @c ***Building****************************************************************
1345 @comment node-name, next, previous, up
1346 @node Building, Testing, Configuration, Installing GCC
1352 @cindex Installing GCC: Building
1354 Now that GCC is configured, you are ready to build the compiler and
1357 We @strong{highly} recommend that GCC be built using GNU make;
1358 other versions may work, then again they might not.
1359 GNU make is required for compiling GNAT (the Ada compiler) and the Java
1362 (For example, many broken versions of make will fail if you use the
1363 recommended setup where @var{objdir} is different from @var{srcdir}.
1364 Other broken versions may recompile parts of the compiler when
1365 installing the compiler.)
1367 Some commands executed when making the compiler may fail (return a
1368 nonzero status) and be ignored by @command{make}. These failures, which
1369 are often due to files that were not found, are expected, and can safely
1372 It is normal to have compiler warnings when compiling certain files.
1373 Unless you are a GCC developer, you can generally ignore these warnings
1374 unless they cause compilation to fail. Developers should attempt to fix
1375 any warnings encountered, however they can temporarily continue past
1376 warnings-as-errors by specifying the configure flag
1377 @option{--disable-werror}.
1379 On certain old systems, defining certain environment variables such as
1380 @env{CC} can interfere with the functioning of @command{make}.
1382 If you encounter seemingly strange errors when trying to build the
1383 compiler in a directory other than the source directory, it could be
1384 because you have previously configured the compiler in the source
1385 directory. Make sure you have done all the necessary preparations.
1387 If you build GCC on a BSD system using a directory stored in an old System
1388 V file system, problems may occur in running @command{fixincludes} if the
1389 System V file system doesn't support symbolic links. These problems
1390 result in a failure to fix the declaration of @code{size_t} in
1391 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
1392 that type mismatches occur, this could be the cause.
1394 The solution is not to use such a directory for building GCC@.
1396 When building from CVS or snapshots, or if you modify parser sources,
1397 you need the Bison parser generator installed. Any version 1.25 or
1398 later should work; older versions may also work. If you do not modify
1399 parser sources, releases contain the Bison-generated files and you do
1400 not need Bison installed to build them.
1402 When building from CVS or snapshots, or if you modify Texinfo
1403 documentation, you need version 4.2 or later of Texinfo installed if you
1404 want Info documentation to be regenerated. Releases contain Info
1405 documentation pre-built for the unmodified documentation in the release.
1407 @section Building a native compiler
1409 For a native build issue the command @samp{make bootstrap}. This
1410 will build the entire GCC system, which includes the following steps:
1414 Build host tools necessary to build the compiler such as texinfo, bison,
1418 Build target tools for use by the compiler such as binutils (bfd,
1419 binutils, gas, gprof, ld, and opcodes)
1420 if they have been individually linked
1421 or moved into the top level GCC source tree before configuring.
1424 Perform a 3-stage bootstrap of the compiler.
1427 Perform a comparison test of the stage2 and stage3 compilers.
1430 Build runtime libraries using the stage3 compiler from the previous step.
1434 If you are short on disk space you might consider @samp{make
1435 bootstrap-lean} instead. This is identical to @samp{make
1436 bootstrap} except that object files from the stage1 and
1437 stage2 of the 3-stage bootstrap of the compiler are deleted as
1438 soon as they are no longer needed.
1440 If you want to save additional space during the bootstrap and in
1441 the final installation as well, you can build the compiler binaries
1442 without debugging information as in the following example. This will save
1443 roughly 40% of disk space both for the bootstrap and the final installation.
1444 (Libraries will still contain debugging information.)
1447 make CFLAGS='-O' LIBCFLAGS='-g -O2' \
1448 LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap
1451 If you wish to use non-default GCC flags when compiling the stage2 and
1452 stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing
1453 @samp{make bootstrap}. Non-default optimization flags are less well
1454 tested here than the default of @samp{-g -O2}, but should still work.
1455 In a few cases, you may find that you need to specify special flags such
1456 as @option{-msoft-float} here to complete the bootstrap; or, if the
1457 native compiler miscompiles the stage1 compiler, you may need to work
1458 around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the
1459 stage1 compiler that were miscompiled, or by using @samp{make
1460 bootstrap4} to increase the number of stages of bootstrap.
1462 If you used the flag @option{--enable-languages=@dots{}} to restrict
1463 the compilers to be built, only those you've actually enabled will be
1464 built. This will of course only build those runtime libraries, for
1465 which the particular compiler has been built. Please note,
1466 that re-defining @env{LANGUAGES} when calling @samp{make bootstrap}
1467 @strong{does not} work anymore!
1469 If the comparison of stage2 and stage3 fails, this normally indicates
1470 that the stage2 compiler has compiled GCC incorrectly, and is therefore
1471 a potentially serious bug which you should investigate and report. (On
1472 a few systems, meaningful comparison of object files is impossible; they
1473 always appear ``different''. If you encounter this problem, you will
1474 need to disable comparison in the @file{Makefile}.)
1476 @section Building a cross compiler
1478 We recommend reading the
1479 @uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ}
1480 for information about building cross compilers.
1482 When building a cross compiler, it is not generally possible to do a
1483 3-stage bootstrap of the compiler. This makes for an interesting problem
1484 as parts of GCC can only be built with GCC@.
1486 To build a cross compiler, we first recommend building and installing a
1487 native compiler. You can then use the native GCC compiler to build the
1488 cross compiler. The installed native compiler needs to be GCC version
1491 Assuming you have already installed a native copy of GCC and configured
1492 your cross compiler, issue the command @command{make}, which performs the
1497 Build host tools necessary to build the compiler such as texinfo, bison,
1501 Build target tools for use by the compiler such as binutils (bfd,
1502 binutils, gas, gprof, ld, and opcodes)
1503 if they have been individually linked or moved into the top level GCC source
1504 tree before configuring.
1507 Build the compiler (single stage only).
1510 Build runtime libraries using the compiler from the previous step.
1513 Note that if an error occurs in any step the make process will exit.
1515 If you are not building GNU binutils in the same source tree as GCC,
1516 you will need a cross-assembler and cross-linker installed before
1517 configuring GCC@. Put them in the directory
1518 @file{@var{prefix}/@var{target}/bin}. Here is a table of the tools
1519 you should put in this directory:
1523 This should be the cross-assembler.
1526 This should be the cross-linker.
1529 This should be the cross-archiver: a program which can manipulate
1530 archive files (linker libraries) in the target machine's format.
1533 This should be a program to construct a symbol table in an archive file.
1536 The installation of GCC will find these programs in that directory,
1537 and copy or link them to the proper place to for the cross-compiler to
1538 find them when run later.
1540 The easiest way to provide these files is to build the Binutils package.
1541 Configure it with the same @option{--host} and @option{--target}
1542 options that you use for configuring GCC, then build and install
1543 them. They install their executables automatically into the proper
1544 directory. Alas, they do not support all the targets that GCC
1547 If you are not building a C library in the same source tree as GCC,
1548 you should also provide the target libraries and headers before
1549 configuring GCC, specifying the directories with
1550 @option{--with-sysroot} or @option{--with-headers} and
1551 @option{--with-libs}. Many targets also require ``start files'' such
1552 as @file{crt0.o} and
1553 @file{crtn.o} which are linked into each executable. There may be several
1554 alternatives for @file{crt0.o}, for use with profiling or other
1555 compilation options. Check your target's definition of
1556 @code{STARTFILE_SPEC} to find out what start files it uses.
1558 @section Building in parallel
1560 You can use @samp{make bootstrap MAKE="make -j 2" -j 2}, or just
1561 @samp{make -j 2 bootstrap} for GNU Make 3.79 and above, instead of
1562 @samp{make bootstrap} to build GCC in parallel.
1563 You can also specify a bigger number, and in most cases using a value
1564 greater than the number of processors in your machine will result in
1565 fewer and shorter I/O latency hits, thus improving overall throughput;
1566 this is especially true for slow drives and network filesystems.
1568 @section Building the Ada compiler
1570 In order to build GNAT, the Ada compiler, you need a working GNAT
1571 compiler (GNAT version 3.14 or later, or GCC version 3.1 or later),
1572 including GNAT tools such as @command{gnatmake} and @command{gnatlink},
1573 since the Ada front end is written in Ada (with some
1574 GNAT-specific extensions), and GNU make.
1576 @command{configure} does not test whether the GNAT installation works
1577 and has a sufficiently recent version; if too old a GNAT version is
1578 installed, the build will fail unless @option{--enable-languages} is
1579 used to disable building the Ada front end.
1581 @section Building with profile feedback
1583 It is possible to use profile feedback to optimize the compiler itself. This
1584 should result in a faster compiler binary. Experiments done on x86 using gcc
1585 3.3 showed approximately 7 percent speedup on compiling C programs. To
1586 bootstrap compiler with profile feedback, use @code{make profiledbootstrap}.
1588 When @samp{make profiledbootstrap} is run, it will first build a @code{stage1}
1589 compiler. This compiler is used to build a @code{stageprofile} compiler
1590 instrumented to collect execution counts of instruction and branch
1591 probabilities. Then runtime libraries are compiled with profile collected.
1592 Finally a @code{stagefeedback} compiler is built using the information collected.
1594 Unlike @samp{make bootstrap} several additional restrictions apply. The
1595 compiler used to build @code{stage1} needs to support a 64-bit integral type.
1596 It is recommended to only use GCC for this. Also parallel make is currently
1597 not supported since collisions in profile collecting may occur.
1604 @uref{./index.html,,Return to the GCC Installation page}
1608 @c ***Testing*****************************************************************
1610 @comment node-name, next, previous, up
1611 @node Testing, Final install, Building, Installing GCC
1615 @chapter Installing GCC: Testing
1618 @cindex Installing GCC: Testing
1621 Before you install GCC, we encourage you to run the testsuites and to
1622 compare your results with results from a similar configuration that have
1623 been submitted to the
1624 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
1625 Some of these archived results are linked from the build status lists
1626 at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who
1627 reports a successful build runs the testsuites and submits the results.
1628 This step is optional and may require you to download additional software,
1629 but it can give you confidence in your new GCC installation or point out
1630 problems before you install and start using your new GCC.
1632 First, you must have @uref{download.html,,downloaded the testsuites}.
1633 These are part of the full distribution, but if you downloaded the
1634 ``core'' compiler plus any front ends, you must download the testsuites
1637 Second, you must have the testing tools installed. This includes
1638 @uref{http://www.gnu.org/software/dejagnu/,,DejaGnu} 1.4.1 or 1.4.3
1639 and later, Tcl, and Expect; the DejaGnu site has links to these.
1641 If the directories where @command{runtest} and @command{expect} were
1642 installed are not in the @env{PATH}, you may need to set the following
1643 environment variables appropriately, as in the following example (which
1644 assumes that DejaGnu has been installed under @file{/usr/local}):
1647 TCL_LIBRARY = /usr/local/share/tcl8.0
1648 DEJAGNULIBS = /usr/local/share/dejagnu
1651 (On systems such as Cygwin, these paths are required to be actual
1652 paths, not mounts or links; presumably this is due to some lack of
1653 portability in the DejaGnu code.)
1656 Finally, you can run the testsuite (which may take a long time):
1658 cd @var{objdir}; make -k check
1661 This will test various components of GCC, such as compiler
1662 front ends and runtime libraries. While running the testsuite, DejaGnu
1663 might emit some harmless messages resembling
1664 @samp{WARNING: Couldn't find the global config file.} or
1665 @samp{WARNING: Couldn't find tool init file} that can be ignored.
1667 @section How can I run the test suite on selected tests?
1669 In order to run sets of tests selectively, there are targets
1670 @samp{make check-gcc} and @samp{make check-g++}
1671 in the @file{gcc} subdirectory of the object directory. You can also
1672 just run @samp{make check} in a subdirectory of the object directory.
1675 A more selective way to just run all @command{gcc} execute tests in the
1679 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
1682 Likewise, in order to run only the @command{g++} ``old-deja'' tests in
1683 the testsuite with filenames matching @samp{9805*}, you would use
1686 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
1689 The @file{*.exp} files are located in the testsuite directories of the GCC
1690 source, the most important ones being @file{compile.exp},
1691 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
1692 To get a list of the possible @file{*.exp} files, pipe the
1693 output of @samp{make check} into a file and look at the
1694 @samp{Running @dots{} .exp} lines.
1696 @section Passing options and running multiple testsuites
1698 You can pass multiple options to the testsuite using the
1699 @samp{--target_board} option of DejaGNU, either passed as part of
1700 @samp{RUNTESTFLAGS}, or directly to @command{runtest} if you prefer to
1701 work outside the makefiles. For example,
1704 make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fno-strength-reduce"
1707 will run the standard @command{g++} testsuites (``unix'' is the target name
1708 for a standard native testsuite situation), passing
1709 @samp{-O3 -fno-strength-reduce} to the compiler on every test, i.e.,
1710 slashes separate options.
1712 You can run the testsuites multiple times using combinations of options
1713 with a syntax similar to the brace expansion of popular shells:
1716 @dots{}"--target_board=arm-sim@{-mhard-float,-msoft-float@}@{-O1,-O2,-O3,@}"
1719 (Note the empty option caused by the trailing comma in the final group.)
1720 The following will run each testsuite eight times using the @samp{arm-sim}
1721 target, as if you had specified all possible combinations yourself:
1724 --target_board=arm-sim/-mhard-float/-O1
1725 --target_board=arm-sim/-mhard-float/-O2
1726 --target_board=arm-sim/-mhard-float/-O3
1727 --target_board=arm-sim/-mhard-float
1728 --target_board=arm-sim/-msoft-float/-O1
1729 --target_board=arm-sim/-msoft-float/-O2
1730 --target_board=arm-sim/-msoft-float/-O3
1731 --target_board=arm-sim/-msoft-float
1734 They can be combined as many times as you wish, in arbitrary ways. This
1738 @dots{}"--target_board=unix/-Wextra@{-O3,-fno-strength-reduce@}@{-fomit-frame-pointer,@}"
1741 will generate four combinations, all involving @samp{-Wextra}.
1743 The disadvantage to this method is that the testsuites are run in serial,
1744 which is a waste on multiprocessor systems. For users with GNU Make and
1745 a shell which performs brace expansion, you can run the testsuites in
1746 parallel by having the shell perform the combinations and @command{make}
1747 do the parallel runs. Instead of using @samp{--target_board}, use a
1748 special makefile target:
1751 make -j@var{N} check-@var{testsuite}//@var{test-target}/@var{option1}/@var{option2}/@dots{}
1757 make -j3 check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@}
1760 will run three concurrent ``make-gcc'' testsuites, eventually testing all
1761 ten combinations as described above. Note that this is currently only
1762 supported in the @file{gcc} subdirectory. (To see how this works, try
1763 typing @command{echo} before the example given here.)
1766 @section Additional testing for Java Class Libraries
1768 The Java runtime tests can be executed via @samp{make check}
1769 in the @file{@var{target}/libjava/testsuite} directory in
1772 The @uref{http://sources.redhat.com/mauve/,,Mauve Project} provides
1773 a suite of tests for the Java Class Libraries. This suite can be run
1774 as part of libgcj testing by placing the Mauve tree within the libjava
1775 testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by
1776 specifying the location of that tree when invoking @samp{make}, as in
1777 @samp{make MAUVEDIR=~/mauve check}.
1779 @uref{http://www-124.ibm.com/developerworks/oss/cvs/jikes/~checkout~/jacks/jacks.html,,Jacks}
1780 is a free test suite that tests Java compiler front ends. This suite
1781 can be run as part of libgcj testing by placing the Jacks tree within
1782 the libjava testsuite at @file{libjava/testsuite/libjava.jacks/jacks}.
1784 @section How to interpret test results
1786 The result of running the testsuite are various @file{*.sum} and @file{*.log}
1787 files in the testsuite subdirectories. The @file{*.log} files contain a
1788 detailed log of the compiler invocations and the corresponding
1789 results, the @file{*.sum} files summarize the results. These summaries
1790 contain status codes for all tests:
1794 PASS: the test passed as expected
1796 XPASS: the test unexpectedly passed
1798 FAIL: the test unexpectedly failed
1800 XFAIL: the test failed as expected
1802 UNSUPPORTED: the test is not supported on this platform
1804 ERROR: the testsuite detected an error
1806 WARNING: the testsuite detected a possible problem
1809 It is normal for some tests to report unexpected failures. At the
1810 current time our testing harness does not allow fine grained control
1811 over whether or not a test is expected to fail. We expect to fix this
1812 problem in future releases.
1815 @section Submitting test results
1817 If you want to report the results to the GCC project, use the
1818 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
1821 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
1822 -m gcc-testresults@@gcc.gnu.org |sh
1825 This script uses the @command{Mail} program to send the results, so
1826 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
1827 prepended to the testsuite summary and should contain any special
1828 remarks you have on your results or your build environment. Please
1829 do not edit the testsuite result block or the subject line, as these
1830 messages may be automatically processed.
1837 @uref{./index.html,,Return to the GCC Installation page}
1841 @c ***Final install***********************************************************
1843 @comment node-name, next, previous, up
1844 @node Final install, , Testing, Installing GCC
1846 @ifset finalinstallhtml
1848 @chapter Installing GCC: Final installation
1851 Now that GCC has been built (and optionally tested), you can install it with
1853 cd @var{objdir}; make install
1856 We strongly recommend to install into a target directory where there is
1857 no previous version of GCC present.
1859 That step completes the installation of GCC; user level binaries can
1860 be found in @file{@var{prefix}/bin} where @var{prefix} is the value
1861 you specified with the @option{--prefix} to configure (or
1862 @file{/usr/local} by default). (If you specified @option{--bindir},
1863 that directory will be used instead; otherwise, if you specified
1864 @option{--exec-prefix}, @file{@var{exec-prefix}/bin} will be used.)
1865 Headers for the C++ and Java libraries are installed in
1866 @file{@var{prefix}/include}; libraries in @file{@var{libdir}}
1867 (normally @file{@var{prefix}/lib}); internal parts of the compiler in
1868 @file{@var{libdir}/gcc} and @file{@var{libexecdir}/gcc}; documentation
1869 in info format in @file{@var{infodir}} (normally
1870 @file{@var{prefix}/info}).
1872 When installing cross-compilers, GCC's executables
1873 are not only installed into @file{@var{bindir}}, that
1874 is, @file{@var{exec-prefix}/bin}, but additionally into
1875 @file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory
1876 exists. Typically, such @dfn{tooldirs} hold target-specific
1877 binutils, including assembler and linker.
1879 Installation into a temporary staging area or into a @command{chroot}
1880 jail can be achieved with the command
1883 make DESTDIR=@var{path-to-rootdir} install
1886 @noindent where @var{path-to-rootdir} is the absolute path of
1887 a directory relative to which all installation paths will be
1888 interpreted. Note that the directory specified by @code{DESTDIR}
1889 need not exist yet; it will be created if necessary.
1891 There is a subtle point with tooldirs and @code{DESTDIR}:
1892 If you relocate a cross-compiler installation with
1893 e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory
1894 @file{@var{rootdir}/@var{exec-prefix}/@var{target-alias}/bin} will
1895 be filled with duplicated GCC executables only if it already exists,
1896 it will not be created otherwise. This is regarded as a feature,
1897 not as a bug, because it gives slightly more control to the packagers
1898 using the @code{DESTDIR} feature.
1900 If you built a released version of GCC using @samp{make bootstrap} then please
1901 quickly review the build status page for your release, available from
1902 @uref{http://gcc.gnu.org/buildstat.html}.
1903 If your system is not listed for the version of GCC that you built,
1905 @email{gcc@@gcc.gnu.org} indicating
1906 that you successfully built and installed GCC.
1907 Include the following information:
1911 Output from running @file{@var{srcdir}/config.guess}. Do not send us
1912 that file itself, just the one-line output from running it.
1915 The output of @samp{gcc -v} for your newly installed @command{gcc}.
1916 This tells us which version of GCC you built and the options you passed to
1920 Whether you enabled all languages or a subset of them. If you used a
1921 full distribution then this information is part of the configure
1922 options in the output of @samp{gcc -v}, but if you downloaded the
1923 ``core'' compiler plus additional front ends then it isn't apparent
1924 which ones you built unless you tell us about it.
1927 If the build was for GNU/Linux, also include:
1930 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
1931 this information should be available from @file{/etc/issue}.
1934 The version of the Linux kernel, available from @samp{uname --version}
1938 The version of glibc you used; for RPM-based systems like Red Hat,
1939 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
1940 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
1942 For other systems, you can include similar information if you think it is
1946 Any other information that you think would be useful to people building
1947 GCC on the same configuration. The new entry in the build status list
1948 will include a link to the archived copy of your message.
1951 We'd also like to know if the
1953 @ref{Specific, host/target specific installation notes}
1956 @uref{specific.html,,host/target specific installation notes}
1958 didn't include your host/target information or if that information is
1959 incomplete or out of date. Send a note to
1960 @email{gcc@@gcc.gnu.org} telling us how the information should be changed.
1962 If you find a bug, please report it following our
1963 @uref{../bugs.html,,bug reporting guidelines}.
1965 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
1966 dvi}. You will need to have @command{texi2dvi} (version at least 4.2)
1967 and @TeX{} installed. This creates a number of @file{.dvi} files in
1968 subdirectories of @file{@var{objdir}}; these may be converted for
1969 printing with programs such as @command{dvips}. You can also
1970 @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the
1971 Free Software Foundation}, though such manuals may not be for the most
1972 recent version of GCC@.
1979 @uref{./index.html,,Return to the GCC Installation page}
1983 @c ***Binaries****************************************************************
1985 @comment node-name, next, previous, up
1986 @node Binaries, Specific, Installing GCC, Top
1990 @chapter Installing GCC: Binaries
1993 @cindex Installing GCC: Binaries
1995 We are often asked about pre-compiled versions of GCC@. While we cannot
1996 provide these for all platforms, below you'll find links to binaries for
1997 various platforms where creating them by yourself is not easy due to various
2000 Please note that we did not create these binaries, nor do we
2001 support them. If you have any problems installing them, please
2002 contact their makers.
2009 @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX};
2012 @uref{http://aixpdslib.seas.ucla.edu,,UCLA Software Library for AIX}.
2016 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}.
2019 Renesas H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
2020 Development Tools for the Renesas H8/300[HS] Series}.
2026 @uref{http://hpux.cae.wisc.edu/,,HP-UX Porting Center};
2029 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
2033 Motorola 68HC11/68HC12---@uref{http://www.gnu-m68hc11.org,,GNU
2034 Development Tools for the Motorola 68HC11/68HC12}.
2037 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
2038 OpenServer/Unixware}.
2041 Sinix/Reliant Unix---@uref{ftp://ftp.fujitsu-siemens.com/pub/pd/gnu/gcc/,,Siemens}.
2044 Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware}.
2047 SGI---@uref{http://freeware.sgi.com/,,SGI Freeware}.
2053 The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project;
2055 The @uref{http://www.mingw.org/,,MinGW} project.
2059 @uref{ftp://ftp.thewrittenword.com/packages/by-name/,,The
2060 Written Word} offers binaries for
2063 Digital UNIX 4.0D and 5.1,
2065 HP-UX 10.20, 11.00, and 11.11, and
2066 Solaris/SPARC 2.5.1, 2.6, 2.7, 8, and 9,
2069 In addition to those specific offerings, you can get a binary
2070 distribution CD-ROM from the
2071 @uref{http://www.fsf.org/order/order.html,,Free Software Foundation}.
2072 It contains binaries for a number of platforms, and
2073 includes not only GCC, but other stuff as well. The current CD does
2074 not contain the latest version of GCC, but it should allow
2075 bootstrapping the compiler. An updated version of that disk is in the
2083 @uref{./index.html,,Return to the GCC Installation page}
2087 @c ***Specific****************************************************************
2089 @comment node-name, next, previous, up
2090 @node Specific, Old, Binaries, Top
2094 @chapter Host/target specific installation notes for GCC
2097 @cindex Specific installation notes
2098 @cindex Target specific installation
2099 @cindex Host specific installation
2100 @cindex Target specific installation notes
2102 Please read this document carefully @emph{before} installing the
2103 GNU Compiler Collection on your machine.
2108 @uref{#alpha*-*-*,,alpha*-*-*}
2110 @uref{#alpha*-dec-osf*,,alpha*-dec-osf*}
2112 @uref{#alphaev5-cray-unicosmk*,,alphaev5-cray-unicosmk*}
2114 @uref{#arc-*-elf,,arc-*-elf}
2116 @uref{#arm-*-elf,,arm-*-elf}
2117 @uref{#arm-*-coff,,arm-*-coff}
2118 @uref{#arm-*-aout,,arm-*-aout}
2120 @uref{#xscale-*-*,,xscale-*-*}
2128 @uref{#*-*-freebsd*,,*-*-freebsd*}
2130 @uref{#h8300-hms,,h8300-hms}
2132 @uref{#hppa*-hp-hpux*,,hppa*-hp-hpux*}
2134 @uref{#hppa*-hp-hpux10,,hppa*-hp-hpux10}
2136 @uref{#hppa*-hp-hpux11,,hppa*-hp-hpux11}
2138 @uref{#*-*-linux-gnu,,*-*-linux-gnu}
2140 @uref{#ix86-*-linux*aout,,i?86-*-linux*aout}
2142 @uref{#ix86-*-linux*,,i?86-*-linux*}
2144 @uref{#ix86-*-sco3.2v5*,,i?86-*-sco3.2v5*}
2146 @uref{#ix86-*-udk,,i?86-*-udk}
2148 @uref{#ix86-*-esix,,i?86-*-esix}
2150 @uref{#ia64-*-linux,,ia64-*-linux}
2152 @uref{#ia64-*-hpux*,,ia64-*-hpux*}
2154 @uref{#*-ibm-aix*,,*-ibm-aix*}
2156 @uref{#ip2k-*-elf,,ip2k-*-elf}
2158 @uref{#iq2000-*-elf,,iq2000-*-elf}
2160 @uref{#m32r-*-elf,,m32r-*-elf}
2162 @uref{#m6811-elf,,m6811-elf}
2164 @uref{#m6812-elf,,m6812-elf}
2166 @uref{#m68k-hp-hpux,,m68k-hp-hpux}
2168 @uref{#mips-*-*,,mips-*-*}
2170 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
2172 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
2174 @uref{#powerpc*-*-*,,powerpc*-*-*, powerpc-*-sysv4}
2176 @uref{#powerpc-*-darwin*,,powerpc-*-darwin*}
2178 @uref{#powerpc-*-elf,,powerpc-*-elf, powerpc-*-sysv4}
2180 @uref{#powerpc-*-linux-gnu*,,powerpc-*-linux-gnu*}
2182 @uref{#powerpc-*-netbsd*,,powerpc-*-netbsd*}
2184 @uref{#powerpc-*-eabiaix,,powerpc-*-eabiaix}
2186 @uref{#powerpc-*-eabisim,,powerpc-*-eabisim}
2188 @uref{#powerpc-*-eabi,,powerpc-*-eabi}
2190 @uref{#powerpcle-*-elf,,powerpcle-*-elf, powerpcle-*-sysv4}
2192 @uref{#powerpcle-*-eabisim,,powerpcle-*-eabisim}
2194 @uref{#powerpcle-*-eabi,,powerpcle-*-eabi}
2196 @uref{#s390-*-linux*,,s390-*-linux*}
2198 @uref{#s390x-*-linux*,,s390x-*-linux*}
2200 @uref{#s390x-ibm-tpf*,,s390x-ibm-tpf*}
2202 @uref{#*-*-solaris2*,,*-*-solaris2*}
2204 @uref{#sparc-sun-solaris2*,,sparc-sun-solaris2*}
2206 @uref{#sparc-sun-solaris2.7,,sparc-sun-solaris2.7}
2208 @uref{#sparc-*-linux*,,sparc-*-linux*}
2210 @uref{#sparc64-*-solaris2*,,sparc64-*-solaris2*}
2212 @uref{#sparcv9-*-solaris2*,,sparcv9-*-solaris2*}
2214 @uref{#*-*-sysv*,,*-*-sysv*}
2216 @uref{#vax-dec-ultrix,,vax-dec-ultrix}
2218 @uref{#*-*-vxworks*,,*-*-vxworks*}
2220 @uref{#x86_64-*-*,,x86_64-*-*, amd64-*-*}
2222 @uref{#xtensa-*-elf,,xtensa-*-elf}
2224 @uref{#xtensa-*-linux*,,xtensa-*-linux*}
2226 @uref{#windows,,Microsoft Windows}
2230 @uref{#older,,Older systems}
2235 @uref{#elf_targets,,all ELF targets} (SVR4, Solaris 2, etc.)
2241 <!-- -------- host/target specific issues start here ---------------- -->
2244 @heading @anchor{alpha*-*-*}alpha*-*-*
2246 This section contains general configuration information for all
2247 alpha-based platforms using ELF (in particular, ignore this section for
2248 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
2249 section, please read all other sections that match your target.
2251 We require binutils 2.11.2 or newer.
2252 Previous binutils releases had a number of problems with DWARF 2
2253 debugging information, not the least of which is incorrect linking of
2259 @heading @anchor{alpha*-dec-osf*}alpha*-dec-osf*
2260 Systems using processors that implement the DEC Alpha architecture and
2261 are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
2262 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
2264 As of GCC 3.2, versions before @code{alpha*-dec-osf4} are no longer
2265 supported. (These are the versions which identify themselves as DEC
2268 In Digital Unix V4.0, virtual memory exhausted bootstrap failures
2269 may be fixed by configuring with @option{--with-gc=simple},
2270 reconfiguring Kernel Virtual Memory and Swap parameters
2271 per the @command{/usr/sbin/sys_check} Tuning Suggestions,
2272 or applying the patch in
2273 @uref{http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html}.
2275 In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
2276 currently (2001-06-13) work with @command{mips-tfile}. As a workaround,
2277 we need to use the old assembler, invoked via the barely documented
2278 @option{-oldas} option. To bootstrap GCC, you either need to use the
2282 % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
2285 or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
2288 % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
2291 As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld}
2292 are supported on Tru64 UNIX, so you must not configure GCC with
2293 @option{--with-gnu-as} or @option{--with-gnu-ld}.
2295 GCC writes a @samp{.verstamp} directive to the assembler output file
2296 unless it is built as a cross-compiler. It gets the version to use from
2297 the system header file @file{/usr/include/stamp.h}. If you install a
2298 new version of DEC Unix, you should rebuild GCC to pick up the new version
2301 Note that since the Alpha is a 64-bit architecture, cross-compilers from
2302 32-bit machines will not generate code as efficient as that generated
2303 when the compiler is running on a 64-bit machine because many
2304 optimizations that depend on being able to represent a word on the
2305 target in an integral value on the host cannot be performed. Building
2306 cross-compilers on the Alpha for 32-bit machines has only been tested in
2307 a few cases and may not work properly.
2309 @samp{make compare} may fail on old versions of DEC Unix unless you add
2310 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
2311 assembler input file is stored in the object file, and that makes
2312 comparison fail if it differs between the @code{stage1} and
2313 @code{stage2} compilations. The option @option{-save-temps} forces a
2314 fixed name to be used for the assembler input file, instead of a
2315 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
2316 unless the comparisons fail without that option. If you add
2317 @option{-save-temps}, you will have to manually delete the @samp{.i} and
2318 @samp{.s} files after each series of compilations.
2320 GCC now supports both the native (ECOFF) debugging format used by DBX
2321 and GDB and an encapsulated STABS format for use only with GDB@. See the
2322 discussion of the @option{--with-stabs} option of @file{configure} above
2323 for more information on these formats and how to select them.
2325 There is a bug in DEC's assembler that produces incorrect line numbers
2326 for ECOFF format when the @samp{.align} directive is used. To work
2327 around this problem, GCC will not emit such alignment directives
2328 while writing ECOFF format debugging information even if optimization is
2329 being performed. Unfortunately, this has the very undesirable
2330 side-effect that code addresses when @option{-O} is specified are
2331 different depending on whether or not @option{-g} is also specified.
2333 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
2334 DBX@. DEC is now aware of this problem with the assembler and hopes to
2335 provide a fix shortly.
2340 @heading @anchor{alphaev5-cray-unicosmk*}alphaev5-cray-unicosmk*
2341 Cray T3E systems running Unicos/Mk.
2343 This port is incomplete and has many known bugs. We hope to improve the
2344 support for this target soon. Currently, only the C front end is supported,
2345 and it is not possible to build parallel applications. Cray modules are not
2346 supported; in particular, Craylibs are assumed to be in
2347 @file{/opt/ctl/craylibs/craylibs}.
2349 You absolutely @strong{must} use GNU make on this platform. Also, you
2350 need to tell GCC where to find the assembler and the linker. The
2351 simplest way to do so is by providing @option{--with-as} and
2352 @option{--with-ld} to @file{configure}, e.g.@:
2355 configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld \
2356 --enable-languages=c
2359 The comparison test during @samp{make bootstrap} fails on Unicos/Mk
2360 because the assembler inserts timestamps into object files. You should
2361 be able to work around this by doing @samp{make all} after getting this
2367 @heading @anchor{arc-*-elf}arc-*-elf
2368 Argonaut ARC processor.
2369 This configuration is intended for embedded systems.
2374 @heading @anchor{arm-*-elf}arm-*-elf
2375 @heading @anchor{xscale-*-*}xscale-*-*
2376 ARM-family processors. Subtargets that use the ELF object format
2377 require GNU binutils 2.13 or newer. Such subtargets include:
2378 @code{arm-*-freebsd}, @code{arm-*-netbsdelf}, @code{arm-*-*linux},
2379 @code{arm-*-rtems} and @code{arm-*-kaos}.
2384 @heading @anchor{arm-*-coff}arm-*-coff
2385 ARM-family processors. Note that there are two different varieties
2386 of PE format subtarget supported: @code{arm-wince-pe} and
2387 @code{arm-pe} as well as a standard COFF target @code{arm-*-coff}.
2392 @heading @anchor{arm-*-aout}arm-*-aout
2393 ARM-family processors. These targets support the AOUT file format:
2394 @code{arm-*-aout}, @code{arm-*-netbsd}.
2399 @heading @anchor{avr}avr
2401 ATMEL AVR-family micro controllers. These are used in embedded
2402 applications. There are no standard Unix configurations.
2404 @xref{AVR Options,, AVR Options, gcc, Using and Porting the GNU Compiler
2408 See ``AVR Options'' in the main manual
2410 for the list of supported MCU types.
2412 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
2414 Further installation notes and other useful information about AVR tools
2415 can also be obtained from:
2419 @uref{http://www.openavr.org,,http://www.openavr.org}
2421 @uref{http://home.overta.ru/users/denisc/,,http://home.overta.ru/users/denisc/}
2423 @uref{http://www.amelek.gda.pl/avr/,,http://www.amelek.gda.pl/avr/}
2426 We @emph{strongly} recommend using binutils 2.13 or newer.
2428 The following error:
2430 Error: register required
2433 indicates that you should upgrade to a newer version of the binutils.
2438 @heading @anchor{c4x}c4x
2440 Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal
2441 Processors. These are used in embedded applications. There are no
2442 standard Unix configurations.
2444 @xref{TMS320C3x/C4x Options,, TMS320C3x/C4x Options, gcc, Using and
2445 Porting the GNU Compiler Collection (GCC)},
2448 See ``TMS320C3x/C4x Options'' in the main manual
2450 for the list of supported MCU types.
2452 GCC can be configured as a cross compiler for both the C3x and C4x
2453 architectures on the same system. Use @samp{configure --target=c4x
2454 --enable-languages="c,c++"} to configure.
2457 Further installation notes and other useful information about C4x tools
2458 can also be obtained from:
2462 @uref{http://www.elec.canterbury.ac.nz/c4x/,,http://www.elec.canterbury.ac.nz/c4x/}
2468 @heading @anchor{cris}CRIS
2470 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
2471 series. These are used in embedded applications.
2474 @xref{CRIS Options,, CRIS Options, gcc, Using and Porting the GNU Compiler
2478 See ``CRIS Options'' in the main manual
2480 for a list of CRIS-specific options.
2482 There are a few different CRIS targets:
2484 @item cris-axis-aout
2485 Old target. Includes a multilib for the @samp{elinux} a.out-based
2486 target. No multilibs for newer architecture variants.
2488 Mainly for monolithic embedded systems. Includes a multilib for the
2489 @samp{v10} core used in @samp{ETRAX 100 LX}.
2490 @item cris-axis-linux-gnu
2491 A GNU/Linux port for the CRIS architecture, currently targeting
2492 @samp{ETRAX 100 LX} by default.
2495 For @code{cris-axis-aout} and @code{cris-axis-elf} you need binutils 2.11
2496 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
2498 Pre-packaged tools can be obtained from
2499 @uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More
2500 information about this platform is available at
2501 @uref{http://developer.axis.com/}.
2506 @heading @anchor{dos}DOS
2508 Please have a look at our @uref{binaries.html,,binaries page}.
2510 You cannot install GCC by itself on MSDOS; it will not compile under
2511 any MSDOS compiler except itself. You need to get the complete
2512 compilation package DJGPP, which includes binaries as well as sources,
2513 and includes all the necessary compilation tools and libraries.
2518 @heading @anchor{*-*-freebsd*}*-*-freebsd*
2520 The version of binutils installed in @file{/usr/bin} probably works with
2521 this release of GCC. However, on FreeBSD 4, bootstrapping against the
2522 latest FSF binutils is known to improve overall testsuite results; and,
2523 on FreeBSD/alpha, using binutils 2.14 or later is required to build libjava.
2525 Support for FreeBSD 1 was discontinued in GCC 3.2.
2527 Support for FreeBSD 2 will be discontinued after GCC 3.4. The
2528 following was true for GCC 3.1 but the current status is unknown.
2529 For FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
2530 configuration support and files as shipped with GCC 2.95 are still in
2531 place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
2532 it is unknown which version of binutils was used (it is assumed that it
2533 was the system copy in @file{/usr/bin}) and C++ EH failures were noted.
2535 For FreeBSD using the ELF file format: DWARF 2 debugging is now the
2536 default for all CPU architectures. It had been the default on
2537 FreeBSD/alpha since its inception. You may use @option{-gstabs} instead
2538 of @option{-g}, if you really want the old debugging format. There are
2539 no known issues with mixing object files and libraries with different
2540 debugging formats. Otherwise, this release of GCC should now match more
2541 of the configuration used in the stock FreeBSD configuration of GCC. In
2542 particular, @option{--enable-threads} is now configured by default.
2543 However, as a general user, do not attempt to replace the system
2544 compiler with this release. Known to bootstrap and check with good
2545 results on FreeBSD 4.9-STABLE and 5-CURRENT@. In the past, known to
2546 bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2,
2547 4.3, 4.4, 4.5, 4.8-STABLE@.
2549 In principle, @option{--enable-threads} is now compatible with
2550 @option{--enable-libgcj} on FreeBSD@. However, it has only been built
2551 and tested on @samp{i386-*-freebsd[45]} and @samp{alpha-*-freebsd[45]}.
2553 library may be incorrectly built (symbols are missing at link time).
2554 There is a rare timing-based startup hang (probably involves an
2555 assumption about the thread library). Multi-threaded boehm-gc (required for
2556 libjava) exposes severe threaded signal-handling bugs on FreeBSD before
2557 4.5-RELEASE@. Other CPU architectures
2558 supported by FreeBSD will require additional configuration tuning in, at
2559 the very least, both boehm-gc and libffi.
2561 Shared @file{libgcc_s.so} is now built and installed by default.
2566 @heading @anchor{h8300-hms}h8300-hms
2567 Renesas H8/300 series of processors.
2569 Please have a look at our @uref{binaries.html,,binaries page}.
2571 The calling convention and structure layout has changed in release 2.6.
2572 All code must be recompiled. The calling convention now passes the
2573 first three arguments in function calls in registers. Structures are no
2574 longer a multiple of 2 bytes.
2579 @heading @anchor{hppa*-hp-hpux*}hppa*-hp-hpux*
2580 Support for HP-UX version 9 and older was discontinued in GCC 3.4.
2582 We @emph{highly} recommend using gas/binutils 2.8 or newer on all hppa
2583 platforms; you may encounter a variety of problems when using the HP
2586 Specifically, @option{-g} does not work on HP-UX (since that system
2587 uses a peculiar debugging format which GCC does not know about), unless you
2588 use GAS and GDB and configure GCC with the
2589 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
2590 @option{--with-as=@dots{}} options.
2592 If you wish to use the pa-risc 2.0 architecture support with a 32-bit
2593 runtime, you must use either the HP assembler, or gas/binutils 2.11
2596 There are two default scheduling models for instructions. These are
2597 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
2598 architecture specified for the target machine when configuring.
2599 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
2600 the target is a @samp{hppa1*} machine.
2602 The PROCESSOR_8000 model is not well suited to older processors. Thus,
2603 it is important to completely specify the machine architecture when
2604 configuring if you want a model other than PROCESSOR_8000. The macro
2605 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
2606 default scheduling model is desired.
2608 More specific information to @samp{hppa*-hp-hpux*} targets follows.
2613 @heading @anchor{hppa*-hp-hpux10}hppa*-hp-hpux10
2615 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
2616 @code{PHCO_19798} from HP@. HP has two sites which provide patches free of
2622 <a href="http://us.itrc.hp.com/service/home/home.do">US, Canada, Asia-Pacific, and
2626 @uref{http://us.itrc.hp.com/service/home/home.do,,} US, Canada, Asia-Pacific,
2630 @uref{http://europe.itrc.hp.com/service/home/home.do,,} Europe.
2633 The HP assembler on these systems has some problems. Most notably the
2634 assembler inserts timestamps into each object file it creates, causing
2635 the 3-stage comparison test to fail during a @samp{make bootstrap}.
2636 You should be able to continue by saying @samp{make all} after getting
2637 the failure from @samp{make bootstrap}.
2643 @heading @anchor{hppa*-hp-hpux11}hppa*-hp-hpux11
2645 GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
2646 be used to compile GCC 3.0 and up.
2648 Refer to @uref{binaries.html,,binaries} for information about obtaining
2649 precompiled GCC binaries for HP-UX. Precompiled binaries must be obtained
2650 to build the Ada language as it can't be bootstrapped using C. Ada is
2651 only available for the 32-bit PA-RISC runtime. The libffi and libjava
2652 haven't been ported to HP-UX and don't build.
2654 It is possible to build GCC 3.3 starting with the bundled HP compiler,
2655 but the process requires several steps. GCC 3.3 can then be used to
2656 build later versions. The fastjar program contains ISO C code and
2657 can't be built with the HP bundled compiler. This problem can be
2658 avoided by not building the Java language. For example, use the
2659 @option{--enable-languages="c,c++,f77,objc"} option in your configure
2662 Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The
2663 bundled compiler supports only traditional C; you will need either HP's
2664 unbundled compiler, or a binary distribution of GCC@.
2666 There are several possible approaches to building the distribution.
2667 Binutils can be built first using the HP tools. Then, the GCC
2668 distribution can be built. The second approach is to build GCC
2669 first using the HP tools, then build binutils, then rebuild GCC.
2670 There have been problems with various binary distributions, so it
2671 is best not to start from a binary distribution.
2673 On 64-bit capable systems, there are two distinct targets. Different
2674 installation prefixes must be used if both are to be installed on
2675 the same system. The @samp{hppa[1-2]*-hp-hpux11*} target generates code
2676 for the 32-bit PA-RISC runtime architecture and uses the HP linker.
2677 The @samp{hppa64-hp-hpux11*} target generates 64-bit code for the
2678 PA-RISC 2.0 architecture. The HP and GNU linkers are both supported
2681 The script config.guess now selects the target type based on the compiler
2682 detected during configuration. You must define @env{PATH} or @env{CC} so
2683 that configure finds an appropriate compiler for the initial bootstrap.
2684 When @env{CC} is used, the definition should contain the options that are
2685 needed whenever @env{CC} is used.
2687 Specifically, options that determine the runtime architecture must be
2688 in @env{CC} to correctly select the target for the build. It is also
2689 convenient to place many other compiler options in @env{CC}. For example,
2690 @env{CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"}
2691 can be used to bootstrap the GCC 3.3 branch with the HP compiler in
2692 64-bit K&R/bundled mode. The @option{+DA2.0W} option will result in
2693 the automatic selection of the @samp{hppa64-hp-hpux11*} target. The
2694 macro definition table of cpp needs to be increased for a successful
2695 build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to
2696 be defined when building with the bundled compiler, or when using the
2697 @option{-Ac} option. These defines aren't necessary with @option{-Ae}.
2699 It is best to explicitly configure the @samp{hppa64-hp-hpux11*} target
2700 with the @option{--with-ld=@dots{}} option. This overrides the standard
2701 search for ld. The two linkers supported on this target require different
2702 commands. The default linker is determined during configuration. As a
2703 result, it's not possible to switch linkers in the middle of a GCC build.
2704 This has been been reported to sometimes occur in unified builds of
2707 With GCC 3.0 through 3.2, you must use binutils 2.11 or above. As of
2708 GCC 3.3, binutils 2.14 or later is required.
2710 Although the HP assembler can be used for an initial build, it shouldn't
2711 be used with any languages other than C and perhaps Fortran due to its
2712 many limitations. For example, it does not support weak symbols or alias
2713 definitions. As a result, explicit template instantiations are required
2714 when using C++. This makes it difficult if not impossible to build many
2715 C++ applications. You can't generate debugging information when using
2716 the HP assembler. Finally, @samp{make bootstrap} fails in the final
2717 comparison of object modules due to the time stamps that it inserts into
2718 the modules. The bootstrap can be continued from this point with
2721 A recent linker patch must be installed for the correct operation of
2722 GCC 3.3 and later. @code{PHSS_26559} and @code{PHSS_24304} are the
2723 oldest linker patches that are known to work. They are for HP-UX
2724 11.00 and 11.11, respectively. @code{PHSS_24303}, the companion to
2725 @code{PHSS_24304}, might be usable but it hasn't been tested. These
2726 patches have been superseded. Consult the HP patch database to obtain
2727 the currently recommended linker patch for your system.
2729 The patches are necessary for the support of weak symbols on the
2730 32-bit port, and for the running of initializers and finalizers. Weak
2731 symbols are implemented using SOM secondary definition symbols. Prior
2732 to HP-UX 11, there are bugs in the linker support for secondary symbols.
2733 The patches correct a problem of linker core dumps creating shared
2734 libraries containing secondary symbols, as well as various other
2735 linking issues involving secondary symbols.
2737 GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
2738 run initializers and finalizers on the 64-bit port. The 32-bit port
2739 uses the linker @option{+init} and @option{+fini} options for the same
2740 purpose. The patches correct various problems with the +init/+fini
2741 options, including program core dumps. Binutils 2.14 corrects a
2742 problem on the 64-bit port resulting from HP's non-standard use of
2743 the .init and .fini sections for array initializers and finalizers.
2745 There are a number of issues to consider in selecting which linker to
2746 use with the 64-bit port. The GNU 64-bit linker can only create dynamic
2747 binaries. The @option{-static} option causes linking with archive
2748 libraries but doesn't produce a truly static binary. Dynamic binaries
2749 still require final binding by the dynamic loader to resolve a set of
2750 dynamic-loader-defined symbols. The default behavior of the HP linker
2751 is the same as the GNU linker. However, it can generate true 64-bit
2752 static binaries using the @option{+compat} option.
2754 The HP 64-bit linker doesn't support linkonce semantics. As a
2755 result, C++ programs have many more sections than they should.
2757 The GNU 64-bit linker has some issues with shared library support
2758 and exceptions. As a result, we only support libgcc in archive
2759 format. For similar reasons, dwarf2 unwind and exception support
2760 are disabled. The GNU linker also has problems creating binaries
2761 with @option{-static}. It doesn't provide stubs for internal
2762 calls to global functions in shared libraries, so these calls
2763 can't be overloaded.
2765 Thread support is not implemented in GCC 3.0 through 3.2, so the
2766 @option{--enable-threads} configure option does not work. In 3.3
2767 and later, POSIX threads are supported. The optional DCE thread
2768 library is not supported.
2770 This port still is undergoing significant development.
2775 @heading @anchor{*-*-linux-gnu}*-*-linux-gnu
2777 Versions of libstdc++-v3 starting with 3.2.1 require bugfixes present
2778 in glibc 2.2.5 and later. More information is available in the
2779 libstdc++-v3 documentation.
2784 @heading @anchor{ix86-*-linux*aout}i?86-*-linux*aout
2785 Use this configuration to generate @file{a.out} binaries on Linux-based
2786 GNU systems. This configuration is being superseded.
2791 @heading @anchor{ix86-*-linux*}i?86-*-linux*
2793 As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
2794 See @uref{http://gcc.gnu.org/PR10877,,bug 10877} for more information.
2796 If you receive Signal 11 errors when building on GNU/Linux, then it is
2797 possible you have a hardware problem. Further information on this can be
2798 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
2803 @heading @anchor{ix86-*-sco3.2v5*}i?86-*-sco3.2v5*
2804 Use this for the SCO OpenServer Release 5 family of operating systems.
2806 Unlike earlier versions of GCC, the ability to generate COFF with this
2807 target is no longer provided.
2809 Earlier versions of GCC emitted DWARF 1 when generating ELF to allow
2810 the system debugger to be used. That support was too burdensome to
2811 maintain. GCC now emits only DWARF 2 for this target. This means you
2812 may use either the UDK debugger or GDB to debug programs built by this
2815 GCC is now only supported on releases 5.0.4 and later, and requires that
2816 you install Support Level Supplement OSS646B or later, and Support Level
2817 Supplement OSS631C or later. If you are using release 5.0.7 of
2818 OpenServer, you must have at least the first maintenance pack installed
2819 (this includes the relevant portions of OSS646). OSS646, also known as
2820 the "Execution Environment Update", provides updated link editors and
2821 assemblers, as well as updated standard C and math libraries. The C
2822 startup modules are also updated to support the System V gABI draft, and
2823 GCC relies on that behavior. OSS631 provides a collection of commonly
2824 used open source libraries, some of which GCC depends on (such as GNU
2825 gettext and zlib). SCO OpenServer Release 5.0.7 has all of this built
2826 in by default, but OSS631C and later also apply to that release. Please
2828 @uref{ftp://ftp.sco.com/pub/openserver5,,ftp://ftp.sco.com/pub/openserver5}
2829 for the latest versions of these (and other potentially useful)
2832 Although there is support for using the native assembler, it is
2833 recommended that you configure GCC to use the GNU assembler. You do
2834 this by using the flags
2835 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You should
2836 use a modern version of GNU binutils. Version 2.13.2.1 was used for all
2837 testing. In general, only the @option{--with-gnu-as} option is tested.
2838 A modern bintuils (as well as a plethora of other development related
2839 GNU utilities) can be found in Support Level Supplement OSS658A, the
2840 "GNU Development Tools" package. See the SCO web and ftp sites for details.
2841 That package also contains the currently "officially supported" version of
2842 GCC, version 2.95.3. It is useful for bootstrapping this version.
2847 @heading @anchor{ix86-*-udk}i?86-*-udk
2849 This target emulates the SCO Universal Development Kit and requires that
2850 package be installed. (If it is installed, you will have a
2851 @file{/udk/usr/ccs/bin/cc} file present.) It's very much like the
2852 @samp{i?86-*-unixware7*} target
2853 but is meant to be used when hosting on a system where UDK isn't the
2854 default compiler such as OpenServer 5 or Unixware 2. This target will
2855 generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
2856 with the same warnings and caveats as the SCO UDK@.
2858 This target is a little tricky to build because we have to distinguish
2859 it from the native tools (so it gets headers, startups, and libraries
2860 from the right place) while making the tools not think we're actually
2861 building a cross compiler. The easiest way to do this is with a configure
2865 CC=/udk/usr/ccs/bin/cc @var{/your/path/to}/gcc/configure \
2866 --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-
2869 @emph{You should substitute @samp{i686} in the above command with the appropriate
2870 processor for your host.}
2872 After the usual @samp{make bootstrap} and
2873 @samp{make install}, you can then access the UDK-targeted GCC
2874 tools by adding @command{udk-} before the commonly known name. For
2875 example, to invoke the C compiler, you would use @command{udk-gcc}.
2876 They will coexist peacefully with any native-target GCC tools you may
2883 @heading @anchor{ia64-*-linux}ia64-*-linux
2884 IA-64 processor (also known as IPF, or Itanium Processor Family)
2887 If you are using the optional libunwind library, then you must use
2888 libunwind 0.96 or later.
2890 None of the following versions of GCC has an ABI that is compatible
2891 with any of the other versions in this list, with the exception that
2892 Red Hat 2.96 and Trillian 000171 are compatible with each other:
2893 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
2894 This primarily affects C++ programs and programs that create shared libraries.
2895 GCC 3.1 or later is recommended for compiling linux, the kernel.
2896 As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
2897 more major ABI changes are expected.
2902 @heading @anchor{ia64-*-hpux*}ia64-*-hpux*
2903 Building GCC on this target requires the GNU Assembler. The bundled HP
2904 assembler will not work. To prevent GCC from using the wrong assembler,
2905 the option @option{--with-gnu-as} may be necessary.
2907 The GCC libunwind library has not been ported to HPUX. This means that for
2908 GCC versions 3.2.3 and earlier, @option{--enable-libunwind-exceptions}
2909 is required to build GCC. For GCC 3.3 and later, this is the default.
2913 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
2915 @heading @anchor{*-ibm-aix*}*-ibm-aix*
2916 Support for AIX version 3 and older was discontinued in GCC 3.4.
2918 AIX Make frequently has problems with GCC makefiles. GNU Make 3.79.1 or
2919 newer is recommended to build on this platform.
2921 To speed up the configuration phases of bootstrapping and installing GCC,
2922 one may use GNU Bash instead of AIX @command{/bin/sh}, e.g.,
2925 % CONFIG_SHELL=/opt/freeware/bin/bash
2926 % export CONFIG_SHELL
2929 and then proceed as described in @uref{build.html,,the build instructions},
2930 where we strongly recommend using GNU make and specifying an absolute path
2931 to invoke @var{srcdir}/configure.
2933 Errors involving @code{alloca} when building GCC generally are due
2934 to an incorrect definition of @code{CC} in the Makefile or mixing files
2935 compiled with the native C compiler and GCC@. During the stage1 phase of
2936 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
2937 (not @command{xlc}). Once @command{configure} has been informed of
2938 @command{xlc}, one needs to use @samp{make distclean} to remove the
2939 configure cache files and ensure that @env{CC} environment variable
2940 does not provide a definition that will confuse @command{configure}.
2941 If this error occurs during stage2 or later, then the problem most likely
2942 is the version of Make (see above).
2944 The native @command{as} and @command{ld} are recommended for bootstrapping
2945 on AIX 4 and required for bootstrapping on AIX 5L. The GNU Assembler
2946 reports that it supports WEAK symbols on AIX 4, which causes GCC to try to
2947 utilize weak symbol functionality although it is not supported. The GNU
2948 Assembler and Linker do not support AIX 5L sufficiently to bootstrap GCC.
2949 The native AIX tools do interoperate with GCC@.
2951 Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
2952 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
2953 fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
2954 referenced as APAR IY53606 (AIX 5.2) or a APAR IY54774 (AIX 5.1)
2956 @samp{libstdc++} in GCC 3.4 increments the major version number of the
2957 shared object and GCC installation places the @file{libstdc++.a}
2958 shared library in a common location which will overwrite the and GCC
2959 3.3 version of the shared library. Applications either need to be
2960 re-linked against the new shared library or the GCC 3.1 and GCC 3.3
2961 versions of the @samp{libstdc++} shared object needs to be available
2962 to the AIX runtime loader. The GCC 3.1 @samp{libstdc++.so.4}, if
2963 present, and GCC 3.3 @samp{libstdc++.so.5} shared objects can be
2964 installed for runtime dynamic loading using the following steps to set
2965 the @samp{F_LOADONLY} flag in the shared object for @emph{each}
2966 multilib @file{libstdc++.a} installed:
2968 Extract the shared objects from the currently installed
2969 @file{libstdc++.a} archive:
2971 % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
2974 Enable the @samp{F_LOADONLY} flag so that the shared object will be
2975 available for runtime dynamic loading, but not linking:
2977 % strip -e libstdc++.so.4 libstdc++.so.5
2980 Archive the runtime-only shared object in the GCC 3.4
2981 @file{libstdc++.a} archive:
2983 % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
2986 Linking executables and shared libraries may produce warnings of
2987 duplicate symbols. The assembly files generated by GCC for AIX always
2988 have included multiple symbol definitions for certain global variable
2989 and function declarations in the original program. The warnings should
2990 not prevent the linker from producing a correct library or runnable
2993 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
2994 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
2995 to parse archive libraries did not handle the new format correctly.
2996 These routines are used by GCC and result in error messages during
2997 linking such as ``not a COFF file''. The version of the routines shipped
2998 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
2999 option of the archive command may be used to create archives of 32-bit
3000 objects using the original ``small format''. A correct version of the
3001 routines is shipped with AIX 4.3.2 and above.
3003 Some versions of the AIX binder (linker) can fail with a relocation
3004 overflow severe error when the @option{-bbigtoc} option is used to link
3005 GCC-produced object files into an executable that overflows the TOC@. A fix
3006 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
3007 available from IBM Customer Support and from its
3008 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3009 website as PTF U455193.
3011 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
3012 with a segmentation fault when invoked by any version of GCC@. A fix for
3013 APAR IX87327 is available from IBM Customer Support and from its
3014 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3015 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
3017 The initial assembler shipped with AIX 4.3.0 generates incorrect object
3018 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
3019 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
3020 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3021 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
3023 AIX provides National Language Support (NLS)@. Compilers and assemblers
3024 use NLS to support locale-specific representations of various data
3025 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
3026 separating decimal fractions). There have been problems reported where
3027 GCC does not produce the same floating-point formats that the assembler
3028 expects. If one encounters this problem, set the @env{LANG}
3029 environment variable to @samp{C} or @samp{En_US}.
3031 By default, GCC for AIX 4.1 and above produces code that can be used on
3032 both Power or PowerPC processors.
3034 A default can be specified with the @option{-mcpu=@var{cpu_type}}
3035 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
3040 @heading @anchor{ip2k-*-elf}ip2k-*-elf
3041 Ubicom IP2022 micro controller.
3042 This configuration is intended for embedded systems.
3043 There are no standard Unix configurations.
3045 Use @samp{configure --target=ip2k-elf --enable-languages=c} to configure GCC@.
3050 @heading @anchor{iq2000-*-elf}iq2000-*-elf
3051 Vitesse IQ2000 processors. These are used in embedded
3052 applications. There are no standard Unix configurations.
3057 @heading @anchor{m32r-*-elf}m32r-*-elf
3058 Renesas M32R processor.
3059 This configuration is intended for embedded systems.
3064 @heading @anchor{m6811-elf}m6811-elf
3065 Motorola 68HC11 family micro controllers. These are used in embedded
3066 applications. There are no standard Unix configurations.
3071 @heading @anchor{m6812-elf}m6812-elf
3072 Motorola 68HC12 family micro controllers. These are used in embedded
3073 applications. There are no standard Unix configurations.
3078 @heading @anchor{m68k-hp-hpux}m68k-hp-hpux
3079 HP 9000 series 300 or 400 running HP-UX@. HP-UX version 8.0 has a bug in
3080 the assembler that prevents compilation of GCC@. This
3081 bug manifests itself during the first stage of compilation, while
3082 building @file{libgcc2.a}:
3086 cc1: warning: `-g' option not supported on this version of GCC
3087 cc1: warning: `-g1' option not supported on this version of GCC
3088 ./xgcc: Internal compiler error: program as got fatal signal 11
3091 A patched version of the assembler is available as the file
3092 @uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you
3093 have HP software support, the patch can also be obtained directly from
3094 HP, as described in the following note:
3097 This is the patched assembler, to patch SR#1653-010439, where the
3098 assembler aborts on floating point constants.
3100 The bug is not really in the assembler, but in the shared library
3101 version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is
3102 SR#4701-078451. Anyway, the attached assembler uses the archive
3103 library version of ``cvtnum(3c)'' and thus does not exhibit the bug.
3106 This patch is also known as PHCO_4484.
3108 In addition gdb does not understand that native HP-UX format, so
3109 you must use gas if you wish to use gdb.
3111 On HP-UX version 8.05, but not on 8.07 or more recent versions, the
3112 @command{fixproto} shell script triggers a bug in the system shell. If you
3113 encounter this problem, upgrade your operating system or use BASH (the
3114 GNU shell) to run @command{fixproto}. This bug will cause the fixproto
3115 program to report an error of the form:
3118 ./fixproto: sh internal 1K buffer overflow
3121 To fix this, you can also change the first line of the fixproto script
3131 @heading @anchor{mips-*-*}mips-*-*
3132 If on a MIPS system you get an error message saying ``does not have gp
3133 sections for all it's [sic] sectons [sic]'', don't worry about it. This
3134 happens whenever you use GAS with the MIPS linker, but there is not
3135 really anything wrong, and it is okay to use the output file. You can
3136 stop such warnings by installing the GNU linker.
3138 It would be nice to extend GAS to produce the gp tables, but they are
3139 optional, and there should not be a warning about their absence.
3141 The libstdc++ atomic locking routines for MIPS targets requires MIPS II
3142 and later. A patch went in just after the GCC 3.3 release to
3143 make @samp{mips*-*-*} use the generic implementation instead. You can also
3144 configure for @samp{mipsel-elf} as a workaround. The
3145 @samp{mips*-*-linux*} target continues to use the MIPS II routines. More
3146 work on this is expected in future releases.
3148 Cross-compilers for the Mips as target using the Mips assembler
3149 currently do not work, because the auxiliary programs
3150 @file{mips-tdump.c} and @file{mips-tfile.c} can't be compiled on
3151 anything but a Mips. It does work to cross compile for a Mips
3152 if you use the GNU assembler and linker.
3157 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
3159 In order to compile GCC on an SGI running IRIX 5, the @samp{compiler_dev.hdr}
3160 subsystem must be installed from the IDO CD-ROM supplied by SGI@.
3161 It is also available for download from
3162 @uref{ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist}.
3164 If you use the MIPS C compiler to bootstrap, it may be necessary
3165 to increase its table size for switch statements with the
3166 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
3167 optimization option, you also need to use @option{-Olimit 3000}.
3169 To enable debugging under IRIX 5, you must use GNU binutils 2.15 or
3170 later, and use the @option{--with-gnu-as} and @option{--with-gnu-ld}
3171 @command{configure} options when configuring GCC@. You need to use GNU
3172 @command{ar} and @command{nm}, also distributed with GNU binutils.
3177 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
3179 If you are using SGI's MIPSpro @command{cc} as your bootstrap compiler, you must
3180 ensure that the N32 ABI is in use. To test this, compile a simple C
3181 file with @command{cc} and then run @command{file} on the
3182 resulting object file. The output should look like:
3185 test.o: ELF N32 MSB @dots{}
3191 test.o: ELF 32-bit MSB @dots{}
3197 test.o: ELF 64-bit MSB @dots{}
3200 then your version of @command{cc} uses the O32 or N64 ABI by default. You
3201 should set the environment variable @env{CC} to @samp{cc -n32}
3202 before configuring GCC@. SGI's MIPSpro 7.2 assembler may misassemble
3203 parts of the compiler, causing bootstrap failures. MIPSpro 7.3 is
3204 known to work. MIPSpro C 7.4 may cause bootstrap failures, too, due
3205 to a bug when inlining @code{memcmp}. Either add @code{-U__INLINE_INTRINSICS}
3206 to the @env{CC} environment variable as a workaround or upgrade to
3209 If you want the resulting @command{gcc} to run on old 32-bit systems
3210 with the MIPS R4400 CPU, you need to ensure that only code for the @samp{mips3}
3211 instruction set architecture (ISA) is generated. While GCC 3.x does
3212 this correctly, both GCC 2.95 and SGI's MIPSpro @command{cc} may change
3213 the ISA depending on the machine where GCC is built. Using one of them
3214 as the bootstrap compiler may result in @samp{mips4} code, which won't run at
3215 all on @samp{mips3}-only systems. For the test program above, you should see:
3218 test.o: ELF N32 MSB mips-3 @dots{}
3224 test.o: ELF N32 MSB mips-4 @dots{}
3227 instead, you should set the environment variable @env{CC} to @samp{cc
3228 -n32 -mips3} or @samp{gcc -mips3} respectively before configuring GCC@.
3230 GCC on IRIX 6 is usually built to support the N32, O32 and N64 ABIs. If
3231 you build GCC on a system that doesn't have the N64 libraries installed
3232 or cannot run 64-bit binaries,
3233 you need to configure with @option{--disable-multilib} so GCC doesn't
3234 try to use them. This will disable building the O32 libraries, too.
3235 Look for @file{/usr/lib64/libc.so.1} to see if you
3236 have the 64-bit libraries installed.
3238 To enable debugging for the O32 ABI, you must use GNU @command{as} from
3239 GNU binutils 2.15 or later. You may also use GNU @command{ld}, but
3240 this is not required and currently causes some problems with Ada.
3242 The @option{--enable-threads} option doesn't currently work, a patch is
3243 in preparation for a future release. The @option{--enable-libgcj}
3244 option is disabled by default: IRIX 6 uses a very low default limit
3245 (20480) for the command line length. Although @command{libtool} contains a
3246 workaround for this problem, at least the N64 @samp{libgcj} is known not
3247 to build despite this, running into an internal error of the native
3248 @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
3249 its maximum of 262144 bytes. If you have root access, you can use the
3250 @command{systune} command to do this.
3252 See @uref{http://freeware.sgi.com/} for more
3253 information about using GCC on IRIX platforms.
3258 @heading @anchor{powerpc*-*-*}powerpc-*-*
3260 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
3261 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
3266 @heading @anchor{powerpc-*-darwin*}powerpc-*-darwin*
3267 PowerPC running Darwin (Mac OS X kernel).
3269 Pre-installed versions of Mac OS X may not include any developer tools,
3270 meaning that you will not be able to build GCC from source. Tool
3271 binaries are available at
3272 @uref{http://developer.apple.com/tools/compilers.html} (free
3273 registration required).
3275 The default stack limit of 512K is too small, which may cause compiles
3276 to fail with 'Bus error'. Set the stack larger, for instance
3277 by doing @samp{limit stack 800}. It's a good idea to use the GNU
3278 preprocessor instead of Apple's @file{cpp-precomp} during the first stage of
3279 bootstrapping; this is automatic when doing @samp{make bootstrap}, but
3280 to do it from the toplevel objdir you will need to say @samp{make
3281 CC='cc -no-cpp-precomp' bootstrap}.
3283 The version of GCC shipped by Apple typically includes a number of
3284 extensions not available in a standard GCC release. These extensions
3285 are generally specific to Mac programming.
3290 @heading @anchor{powerpc-*-elf}powerpc-*-elf, powerpc-*-sysv4
3291 PowerPC system in big endian mode, running System V.4.
3296 @heading @anchor{powerpc-*-linux-gnu*}powerpc-*-linux-gnu*
3299 @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.13.90.0.10}
3300 or newer for a working GCC@.
3305 @heading @anchor{powerpc-*-netbsd*}powerpc-*-netbsd*
3306 PowerPC system in big endian mode running NetBSD@. To build the
3307 documentation you will need Texinfo version 4.2 (NetBSD 1.5.1 included
3308 Texinfo version 3.12).
3313 @heading @anchor{powerpc-*-eabisim}powerpc-*-eabisim
3314 Embedded PowerPC system in big endian mode for use in running under the
3320 @heading @anchor{powerpc-*-eabi}powerpc-*-eabi
3321 Embedded PowerPC system in big endian mode.
3326 @heading @anchor{powerpcle-*-elf}powerpcle-*-elf, powerpcle-*-sysv4
3327 PowerPC system in little endian mode, running System V.4.
3332 @heading @anchor{powerpcle-*-eabisim}powerpcle-*-eabisim
3333 Embedded PowerPC system in little endian mode for use in running under
3339 @heading @anchor{powerpcle-*-eabi}powerpcle-*-eabi
3340 Embedded PowerPC system in little endian mode.
3345 @heading @anchor{s390-*-linux*}s390-*-linux*
3346 S/390 system running GNU/Linux for S/390@.
3351 @heading @anchor{s390x-*-linux*}s390x-*-linux*
3352 zSeries system (64-bit) running GNU/Linux for zSeries@.
3357 @heading @anchor{s390x-ibm-tpf*}s390x-ibm-tpf*
3358 zSeries system (64-bit) running TPF. This platform is
3359 supported as cross-compilation target only.
3364 @c Please use Solaris 2 to refer to all release of Solaris, starting
3365 @c with 2.0 until 2.6, 7, and 8. Solaris 1 was a marketing name for
3366 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
3367 @c alone is too unspecific and must be avoided.
3368 @heading @anchor{*-*-solaris2*}*-*-solaris2*
3370 Sun does not ship a C compiler with Solaris 2. To bootstrap and install
3371 GCC you first have to install a pre-built compiler, see our
3372 @uref{binaries.html,,binaries page} for details.
3374 The Solaris 2 @command{/bin/sh} will often fail to configure
3375 @file{libstdc++-v3}, @file{boehm-gc} or @file{libjava}. We therefore
3376 recommend to use the following sequence of commands to bootstrap and
3380 % CONFIG_SHELL=/bin/ksh
3381 % export CONFIG_SHELL
3384 and then proceed as described in @uref{build.html,,the build instructions},
3385 where we strongly recommend using GNU make and specifying an absolute path
3386 to invoke @var{srcdir}/configure.
3388 Solaris 2 comes with a number of optional OS packages. Some of these
3389 are needed to use GCC fully, namely @code{SUNWarc},
3390 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
3391 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
3392 optional packages when installing Solaris 2, you will need to verify that
3393 the packages that GCC needs are installed.
3395 To check whether an optional package is installed, use
3396 the @command{pkginfo} command. To add an optional package, use the
3397 @command{pkgadd} command. For further details, see the Solaris 2
3400 Trying to use the linker and other tools in
3401 @file{/usr/ucb} to install GCC has been observed to cause trouble.
3402 For example, the linker may hang indefinitely. The fix is to remove
3403 @file{/usr/ucb} from your @env{PATH}.
3405 The build process works more smoothly with the legacy Sun tools so, if you
3406 have @file{/usr/xpg4/bin} in your @env{PATH}, we recommend that you place
3407 @file{/usr/bin} before @file{/usr/xpg4/bin} for the duration of the build.
3409 All releases of GNU binutils prior to 2.11.2 have known bugs on this
3410 platform. We recommend the use of GNU binutils 2.11.2 or the vendor
3411 tools (Sun @command{as}, Sun @command{ld}).
3413 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3414 newer: @command{g++} will complain that types are missing. These headers assume
3415 that omitting the type means @code{int}; this assumption worked for C89 but
3416 is wrong for C++, and is now wrong for C99 also.
3418 @command{g++} accepts such (invalid) constructs with the option
3419 @option{-fpermissive}; it
3420 will assume that any missing type is @code{int} (as defined by C89).
3422 There are patches for Solaris 2.6 (105633-56 or newer for SPARC,
3423 106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC,
3424 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
3425 108653-22 for Intel) that fix this bug.
3430 @heading @anchor{sparc-sun-solaris2*}sparc-sun-solaris2*
3432 When GCC is configured to use binutils 2.11.2 or later the binaries
3433 produced are smaller than the ones produced using Sun's native tools;
3434 this difference is quite significant for binaries containing debugging
3437 Sun @command{as} 4.x is broken in that it cannot cope with long symbol names.
3438 A typical error message might look similar to the following:
3441 /usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error:
3442 can't compute value of an expression involving an external symbol.
3445 This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris
3446 2.6 and has been fixed in later (5.x) versions of the assembler,
3447 starting with Solaris 7.
3449 Starting with Solaris 7, the operating system is capable of executing
3450 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
3451 this; the @option{-m64} option enables 64-bit code generation.
3452 However, if all you want is code tuned for the UltraSPARC CPU, you
3453 should try the @option{-mtune=ultrasparc} option instead, which produces
3454 code that, unlike full 64-bit code, can still run on non-UltraSPARC
3457 When configuring on a Solaris 7 or later system that is running a kernel
3458 that supports only 32-bit binaries, one must configure with
3459 @option{--disable-multilib}, since we will not be able to build the
3460 64-bit target libraries.
3462 GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of
3463 the GNU compiler (especially GCC 3.0.x versions), which lead to the
3464 miscompilation of the stage1 compiler and the subsequent failure of the
3465 bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary
3466 stage, i.e. to bootstrap that compiler with the base compiler and then
3467 use it to bootstrap the final compiler.
3469 GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7)
3470 and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap
3471 failure in form of a miscompilation of the stage1 compiler by the Sun
3472 compiler. This is Sun bug 4974440. This is fixed with patch 112760-07.
3477 @heading @anchor{sparc-sun-solaris2.7}sparc-sun-solaris2.7
3479 Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
3480 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
3481 and later, including all EGCS releases. Sun formerly recommended
3482 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
3483 recommend it only for people who use Sun's compilers.
3485 Here are some workarounds to this problem:
3488 Do not install Sun patch 107058-01 until after Sun releases a
3489 complete patch for bug 4210064. This is the simplest course to take,
3490 unless you must also use Sun's C compiler. Unfortunately 107058-01
3491 is preinstalled on some new Solaris 7-based hosts, so you may have to
3495 Copy the original, unpatched Solaris 7
3496 @command{/usr/ccs/bin/as} into
3497 @command{/usr/local/libexec/gcc/sparc-sun-solaris2.7/3.4/as},
3498 adjusting the latter name to fit your local conventions and software
3502 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
3503 both 107058-01 and 106950-03 installed has reported the bug with GCC
3504 and Sun's dynamic linker. This last course of action is riskiest,
3505 for two reasons. First, you must install 106950 on all hosts that
3506 run code generated by GCC; it doesn't suffice to install it only on
3507 the hosts that run GCC itself. Second, Sun says that 106950-03 is
3508 only a partial fix for bug 4210064, but Sun doesn't know whether the
3509 partial fix is adequate for GCC@. Revision -08 or later should fix
3510 the bug. The current (as of 2001-09-24) revision is -14, and is included in
3511 the Solaris 7 Recommended Patch Cluster.
3514 GCC 3.3 triggers a bug in version 5.0 Alpha 03/27/98 of the Sun assembler,
3515 which causes a bootstrap failure when linking the 64-bit shared version of
3516 libgcc. A typical error message is:
3519 ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o:
3520 symbol <unknown>: offset 0xffffffff7ec133e7 is non-aligned.
3523 This bug has been fixed in the final 5.0 version of the assembler.
3528 @heading @anchor{sparc-*-linux*}sparc-*-linux*
3530 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
3531 or newer on this platform. All earlier binutils and glibc
3532 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
3538 @heading @anchor{sparc64-*-solaris2*}sparc64-*-solaris2*
3540 The following compiler flags must be specified in the configure
3541 step in order to bootstrap this target with the Sun compiler:
3544 % CC="cc -xildoff -xarch=v9" @var{srcdir}/configure [@var{options}] [@var{target}]
3547 @option{-xildoff} turns off the incremental linker, and @option{-xarch=v9}
3548 specifies the SPARC-V9 architecture to the Sun linker and assembler.
3553 @heading @anchor{sparcv9-*-solaris2*}sparcv9-*-solaris2*
3555 This is a synonym for sparc64-*-solaris2*.
3560 @heading @anchor{#*-*-sysv*}*-*-sysv*
3561 On System V release 3, you may get this error message
3565 ld fatal: failed to write symbol name @var{something}
3566 in strings table for file @var{whatever}
3569 This probably indicates that the disk is full or your ulimit won't allow
3570 the file to be as large as it needs to be.
3572 This problem can also result because the kernel parameter @code{MAXUMEM}
3573 is too small. If so, you must regenerate the kernel and make the value
3574 much larger. The default value is reported to be 1024; a value of 32768
3575 is said to work. Smaller values may also work.
3577 On System V, if you get an error like this,
3580 /usr/local/lib/bison.simple: In function `yyparse':
3581 /usr/local/lib/bison.simple:625: virtual memory exhausted
3585 that too indicates a problem with disk space, ulimit, or @code{MAXUMEM}.
3587 On a System V release 4 system, make sure @file{/usr/bin} precedes
3588 @file{/usr/ucb} in @code{PATH}. The @command{cc} command in
3589 @file{/usr/ucb} uses libraries which have bugs.
3594 @heading @anchor{vax-dec-ultrix}vax-dec-ultrix
3595 Don't try compiling with VAX C (@command{vcc}). It produces incorrect code
3596 in some cases (for example, when @code{alloca} is used).
3601 @heading @anchor{*-*-vxworks*}*-*-vxworks*
3602 Support for VxWorks is in flux. At present GCC supports @emph{only} the
3603 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC.
3604 We welcome patches for other architectures supported by VxWorks 5.5.
3605 Support for VxWorks AE would also be welcome; we believe this is merely
3606 a matter of writing an appropriate ``configlette'' (see below). We are
3607 not interested in supporting older, a.out or COFF-based, versions of
3610 VxWorks comes with an older version of GCC installed in
3611 @file{@var{$WIND_BASE}/host}; we recommend you do not overwrite it.
3612 Choose an installation @var{prefix} entirely outside @var{$WIND_BASE}.
3613 Before running @command{configure}, create the directories @file{@var{prefix}}
3614 and @file{@var{prefix}/bin}. Link or copy the appropriate assembler,
3615 linker, etc. into @file{@var{prefix}/bin}, and set your @var{PATH} to
3616 include that directory while running both @command{configure} and
3619 You must give @command{configure} the
3620 @option{--with-headers=@var{$WIND_BASE}/target/h} switch so that it can
3621 find the VxWorks system headers. Since VxWorks is a cross compilation
3622 target only, you must also specify @option{--target=@var{target}}.
3623 @command{configure} will attempt to create the directory
3624 @file{@var{prefix}/@var{target}/sys-include} and copy files into it;
3625 make sure the user running @command{configure} has sufficient privilege
3628 GCC's exception handling runtime requires a special ``configlette''
3629 module, @file{contrib/gthr_supp_vxw_5x.c}. Follow the instructions in
3630 that file to add the module to your kernel build. (Future versions of
3631 VxWorks will incorporate this module.)
3636 @heading @anchor{x86_64-*-*}x86_64-*-*, amd64-*-*
3638 GCC supports the x86-64 architecture implemented by the AMD64 processor
3639 (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD.
3640 On GNU/Linux the default is a bi-arch compiler which is able to generate
3641 both 64-bit x86-64 and 32-bit x86 code (via the @option{-m32} switch).
3646 @heading @anchor{xtensa-*-elf}xtensa-*-elf
3648 This target is intended for embedded Xtensa systems using the
3649 @samp{newlib} C library. It uses ELF but does not support shared
3650 objects. Designed-defined instructions specified via the
3651 Tensilica Instruction Extension (TIE) language are only supported
3652 through inline assembly.
3654 The Xtensa configuration information must be specified prior to
3655 building GCC@. The @file{include/xtensa-config.h} header
3656 file contains the configuration information. If you created your
3657 own Xtensa configuration with the Xtensa Processor Generator, the
3658 downloaded files include a customized copy of this header file,
3659 which you can use to replace the default header file.
3664 @heading @anchor{xtensa-*-linux*}xtensa-*-linux*
3666 This target is for Xtensa systems running GNU/Linux. It supports ELF
3667 shared objects and the GNU C library (glibc). It also generates
3668 position-independent code (PIC) regardless of whether the
3669 @option{-fpic} or @option{-fPIC} options are used. In other
3670 respects, this target is the same as the
3671 @uref{#xtensa-*-elf,,@samp{xtensa-*-elf}} target.
3676 @heading @anchor{windows}Microsoft Windows (32-bit)
3678 A port of GCC 2.95.2 and 3.x is included with the
3679 @uref{http://www.cygwin.com/,,Cygwin environment}.
3681 Current (as of early 2001) snapshots of GCC will build under Cygwin
3682 without modification.
3684 GCC does not currently build with Microsoft's C++ compiler and there
3685 are no plans to make it do so.
3690 @heading @anchor{os2}OS/2
3692 GCC does not currently support OS/2. However, Andrew Zabolotny has been
3693 working on a generic OS/2 port with pgcc. The current code can be found
3694 at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
3696 An older copy of GCC 2.8.1 is included with the EMX tools available at
3697 @uref{ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/,,
3698 ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/}.
3703 @heading @anchor{older}Older systems
3705 GCC contains support files for many older (1980s and early
3706 1990s) Unix variants. For the most part, support for these systems
3707 has not been deliberately removed, but it has not been maintained for
3708 several years and may suffer from bitrot.
3710 Starting with GCC 3.1, each release has a list of ``obsoleted'' systems.
3711 Support for these systems is still present in that release, but
3712 @command{configure} will fail unless the @option{--enable-obsolete}
3713 option is given. Unless a maintainer steps forward, support for these
3714 systems will be removed from the next release of GCC@.
3716 Support for old systems as hosts for GCC can cause problems if the
3717 workarounds for compiler, library and operating system bugs affect the
3718 cleanliness or maintainability of the rest of GCC@. In some cases, to
3719 bring GCC up on such a system, if still possible with current GCC, may
3720 require first installing an old version of GCC which did work on that
3721 system, and using it to compile a more recent GCC, to avoid bugs in the
3722 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
3723 @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror
3724 sites}. Header bugs may generally be avoided using
3725 @command{fixincludes}, but bugs or deficiencies in libraries and the
3726 operating system may still cause problems.
3728 Support for older systems as targets for cross-compilation is less
3729 problematic than support for them as hosts for GCC; if an enthusiast
3730 wishes to make such a target work again (including resurrecting any of
3731 the targets that never worked with GCC 2, starting from the last CVS
3732 version before they were removed), patches
3733 @uref{../contribute.html,,following the usual requirements} would be
3734 likely to be accepted, since they should not affect the support for more
3737 For some systems, old versions of GNU binutils may also be useful,
3738 and are available from @file{pub/binutils/old-releases} on
3739 @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}.
3741 Some of the information on specific systems above relates to
3742 such older systems, but much of the information
3743 about GCC on such systems (which may no longer be applicable to
3744 current GCC) is to be found in the GCC texinfo manual.
3749 @heading @anchor{elf_targets}all ELF targets (SVR4, Solaris 2, etc.)
3751 C++ support is significantly better on ELF targets if you use the
3752 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
3753 inlines, vtables and template instantiations will be discarded
3762 @uref{./index.html,,Return to the GCC Installation page}
3766 @c ***Old documentation******************************************************
3768 @include install-old.texi
3774 @uref{./index.html,,Return to the GCC Installation page}
3778 @c ***GFDL********************************************************************
3786 @uref{./index.html,,Return to the GCC Installation page}
3790 @c ***************************************************************************
3791 @c Part 6 The End of the Document
3793 @comment node-name, next, previous, up
3794 @node Concept Index, , GNU Free Documentation License, Top
3798 @unnumbered Concept Index