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.
288 @item GNU Multiple Precision Library (GMP) version 4.0 (or later)
290 Necessary to build the Fortran frontend. If you don't have it
291 installed in your library search path, you will have to configure with
292 the @option{--with-gmp} or @option{--with-gmp-dir} configure option.
296 Necessary to build the Fortran frontend. It can be downloaded from
297 @uref{http://www.mpfr.org/}. It is also included in the current GMP
298 release (4.1.3) when configured with @option{--enable-mpfr}.
300 The @option{--with-mpfr} or @option{--with-mpfr-dir} configure option should
301 be used if your MPFR Library is not installed in your library search path.
306 @heading Tools/packages necessary for modifying GCC
308 @item autoconf versions 2.13 and 2.59
309 @itemx GNU m4 version 1.4 (or later)
311 Necessary when modifying @file{configure.ac}, @file{aclocal.m4}, etc.@:
312 to regenerate @file{configure} and @file{config.in} files. Most
313 directories require autoconf 2.59 (exactly), but the toplevel
314 still requires autoconf 2.13 (exactly).
316 @item automake versions 1.8.5 and 1.9.1
318 Necessary when modifying a @file{Makefile.am} file to regenerate its
319 associated @file{Makefile.in}.
321 Much of GCC does not use automake, so directly edit the @file{Makefile.in}
322 file. Specifically this applies to the @file{gcc}, @file{intl},
323 @file{libcpp}, @file{libiberty}, @file{libobjc} directories as well
324 as any of their subdirectories.
326 The Java directory @file{libjava} and the @file{libstdc++-v3} directory
327 require automake 1.9.1. Every other directory should work with either
328 automake 1.8.5 and automake 1.9.1, but most of them have been tested only
329 with automake 1.8.5 so far.
331 @item gettext version 0.12 (or later)
333 Needed to regenerate @file{gcc.pot}.
335 @item gperf version 2.7.2 (or later)
337 Necessary when modifying @command{gperf} input files, e.g.@:
338 @file{gcc/cp/cfns.gperf} to regenerate its associated header file, e.g.@:
339 @file{gcc/cp/cfns.h}.
341 @item expect version ???
342 @itemx tcl version ???
343 @itemx dejagnu version 1.4.4 (or later)
345 Necessary to run the GCC testsuite.
347 @item autogen version 5.5.4 (or later) and
348 @itemx guile version 1.4.1 (or later)
350 Necessary to regenerate @file{fixinc/fixincl.x} from
351 @file{fixinc/inclhack.def} and @file{fixinc/*.tpl}.
353 Necessary to run the @file{fixinc} @command{make check}.
355 Necessary to regenerate the top level @file{Makefile.in} file from
356 @file{Makefile.tpl} and @file{Makefile.def}.
358 @item GNU Bison version 1.28 (or later)
359 Berkeley @command{yacc} (@command{byacc}) is also reported to work other
362 Necessary when modifying @file{*.y} files.
364 Necessary to build GCC during development because the generated output
365 files are not included in the CVS repository. They are included in
368 @item Flex version 2.5.4 (or later)
370 Necessary when modifying @file{*.l} files.
372 Necessary to build GCC during development because the generated output
373 files are not included in the CVS repository. They are included in
376 @item Texinfo version 4.2 (or later)
378 Necessary for running @command{makeinfo} when modifying @file{*.texi}
379 files to test your changes.
381 Necessary to build GCC documentation during development because the
382 generated output files are not included in the CVS repository. They are
383 included in releases.
385 @item @TeX{} (any working version)
387 Necessary for running @command{texi2dvi}, used when running
388 @command{make dvi} to create DVI files.
390 @item cvs version 1.10 (or later)
391 @itemx ssh (any version)
393 Necessary to access the CVS repository. Public releases and weekly
394 snapshots of the development sources are also available via FTP@.
396 @item perl version 5.6.1 (or later)
398 Necessary when regenerating @file{Makefile} dependencies in libiberty.
399 Necessary when regenerating @file{libiberty/functions.texi}.
400 Necessary when generating manpages from Texinfo manuals.
401 Used by various scripts to generate some files included in CVS (mainly
402 Unicode-related and rarely changing) from source tables.
404 @item GNU diffutils version 2.7 (or later)
406 Necessary when creating changes to GCC source code to submit for review.
408 @item patch version 2.5.4 (or later)
410 Necessary when applying patches, created with @command{diff}, to one's
420 @uref{./index.html,,Return to the GCC Installation page}
424 @c ***Downloading the source**************************************************
426 @comment node-name, next, previous, up
427 @node Downloading the source, Configuration, Prerequisites, Installing GCC
431 @chapter Downloading GCC
433 @cindex Downloading GCC
434 @cindex Downloading the Source
436 GCC is distributed via @uref{http://gcc.gnu.org/cvs.html,,CVS} and FTP
437 tarballs compressed with @command{gzip} or
438 @command{bzip2}. It is possible to download a full distribution or specific
441 Please refer to the @uref{http://gcc.gnu.org/releases.html,,releases web page}
442 for information on how to obtain GCC@.
444 The full distribution includes the C, C++, Objective-C, Fortran 77, Fortran
445 (in case of GCC 3.5 and later), Java, and Ada (in case of GCC 3.1 and later)
446 compilers. The full distribution also includes runtime libraries for C++,
447 Objective-C, Fortran 77, Fortran, and Java. In GCC 3.0 and later versions,
448 GNU compiler testsuites are also included in the full distribution.
450 If you choose to download specific components, you must download the core
451 GCC distribution plus any language specific distributions you wish to
452 use. The core distribution includes the C language front end as well as the
453 shared components. Each language has a tarball which includes the language
454 front end as well as the language runtime (when appropriate).
456 Unpack the core distribution as well as any language specific
457 distributions in the same directory.
459 If you also intend to build binutils (either to upgrade an existing
460 installation or for use in place of the corresponding tools of your
461 OS), unpack the binutils distribution either in the same directory or
462 a separate one. In the latter case, add symbolic links to any
463 components of the binutils you intend to build alongside the compiler
464 (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
465 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
472 @uref{./index.html,,Return to the GCC Installation page}
476 @c ***Configuration***********************************************************
478 @comment node-name, next, previous, up
479 @node Configuration, Building, Downloading the source, Installing GCC
483 @chapter Installing GCC: Configuration
485 @cindex Configuration
486 @cindex Installing GCC: Configuration
488 Like most GNU software, GCC must be configured before it can be built.
489 This document describes the recommended configuration procedure
490 for both native and cross targets.
492 We use @var{srcdir} to refer to the toplevel source directory for
493 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
495 If you obtained the sources via CVS, @var{srcdir} must refer to the top
496 @file{gcc} directory, the one where the @file{MAINTAINERS} can be found,
497 and not its @file{gcc} subdirectory, otherwise the build will fail.
499 If either @var{srcdir} or @var{objdir} is located on an automounted NFS
500 file system, the shell's built-in @command{pwd} command will return
501 temporary pathnames. Using these can lead to various sorts of build
502 problems. To avoid this issue, set the @env{PWDCMD} environment
503 variable to an automounter-aware @command{pwd} command, e.g.,
504 @command{pawd} or @samp{amq -w}, during the configuration and build
507 First, we @strong{highly} recommend that GCC be built into a
508 separate directory than the sources which does @strong{not} reside
509 within the source tree. This is how we generally build GCC; building
510 where @var{srcdir} == @var{objdir} should still work, but doesn't
511 get extensive testing; building where @var{objdir} is a subdirectory
512 of @var{srcdir} is unsupported.
514 If you have previously built GCC in the same directory for a
515 different target machine, do @samp{make distclean} to delete all files
516 that might be invalid. One of the files this deletes is @file{Makefile};
517 if @samp{make distclean} complains that @file{Makefile} does not exist
518 or issues a message like ``don't know how to make distclean'' it probably
519 means that the directory is already suitably clean. However, with the
520 recommended method of building in a separate @var{objdir}, you should
521 simply use a different @var{objdir} for each target.
523 Second, when configuring a native system, either @command{cc} or
524 @command{gcc} must be in your path or you must set @env{CC} in
525 your environment before running configure. Otherwise the configuration
528 Note that the bootstrap compiler and the resulting GCC must be link
529 compatible, else the bootstrap will fail with linker errors about
530 incompatible object file formats. Several multilibed targets are
531 affected by this requirement, see
533 @ref{Specific, host/target specific installation notes}.
536 @uref{specific.html,,host/target specific installation notes}.
544 % @var{srcdir}/configure [@var{options}] [@var{target}]
548 @heading Target specification
551 GCC has code to correctly determine the correct value for @var{target}
552 for nearly all native systems. Therefore, we highly recommend you not
553 provide a configure target when configuring a native compiler.
556 @var{target} must be specified as @option{--target=@var{target}}
557 when configuring a cross compiler; examples of valid targets would be
558 m68k-coff, sh-elf, etc.
561 Specifying just @var{target} instead of @option{--target=@var{target}}
562 implies that the host defaults to @var{target}.
566 @heading Options specification
568 Use @var{options} to override several configure time options for
569 GCC@. A list of supported @var{options} follows; @samp{configure
570 --help} may list other options, but those not listed below may not
571 work and should not normally be used.
573 Note that each @option{--enable} option has a corresponding
574 @option{--disable} option and that each @option{--with} option has a
575 corresponding @option{--without} option.
578 @item --prefix=@var{dirname}
579 Specify the toplevel installation
580 directory. This is the recommended way to install the tools into a directory
581 other than the default. The toplevel installation directory defaults to
584 We @strong{highly} recommend against @var{dirname} being the same or a
585 subdirectory of @var{objdir} or vice versa. If specifying a directory
586 beneath a user's home directory tree, some shells will not expand
587 @var{dirname} correctly if it contains the @samp{~} metacharacter; use
590 The following standard @command{autoconf} options are supported. Normally you
591 should not need to use these options.
593 @item --exec-prefix=@var{dirname}
594 Specify the toplevel installation directory for architecture-dependent
595 files. The default is @file{@var{prefix}}.
597 @item --bindir=@var{dirname}
598 Specify the installation directory for the executables called by users
599 (such as @command{gcc} and @command{g++}). The default is
600 @file{@var{exec-prefix}/bin}.
602 @item --libdir=@var{dirname}
603 Specify the installation directory for object code libraries and
604 internal data files of GCC@. The default is @file{@var{exec-prefix}/lib}.
606 @item --libexecdir=@var{dirname}
607 Specify the installation directory for internal executables of GCC@.
608 The default is @file{@var{exec-prefix}/libexec}.
610 @item --with-slibdir=@var{dirname}
611 Specify the installation directory for the shared libgcc library. The
612 default is @file{@var{libdir}}.
614 @item --infodir=@var{dirname}
615 Specify the installation directory for documentation in info format.
616 The default is @file{@var{prefix}/info}.
618 @item --datadir=@var{dirname}
619 Specify the installation directory for some architecture-independent
620 data files referenced by GCC@. The default is @file{@var{prefix}/share}.
622 @item --mandir=@var{dirname}
623 Specify the installation directory for manual pages. The default is
624 @file{@var{prefix}/man}. (Note that the manual pages are only extracts from
625 the full GCC manuals, which are provided in Texinfo format. The manpages
626 are derived by an automatic conversion process from parts of the full
629 @item --with-gxx-include-dir=@var{dirname}
631 the installation directory for G++ header files. The default is
632 @file{@var{prefix}/include/c++/@var{version}}.
636 @item --program-prefix=@var{prefix}
637 GCC supports some transformations of the names of its programs when
638 installing them. This option prepends @var{prefix} to the names of
639 programs to install in @var{bindir} (see above). For example, specifying
640 @option{--program-prefix=foo-} would result in @samp{gcc}
641 being installed as @file{/usr/local/bin/foo-gcc}.
643 @item --program-suffix=@var{suffix}
644 Appends @var{suffix} to the names of programs to install in @var{bindir}
645 (see above). For example, specifying @option{--program-suffix=-3.1}
646 would result in @samp{gcc} being installed as
647 @file{/usr/local/bin/gcc-3.1}.
649 @item --program-transform-name=@var{pattern}
650 Applies the @samp{sed} script @var{pattern} to be applied to the names
651 of programs to install in @var{bindir} (see above). @var{pattern} has to
652 consist of one or more basic @samp{sed} editing commands, separated by
653 semicolons. For example, if you want the @samp{gcc} program name to be
654 transformed to the installed program @file{/usr/local/bin/myowngcc} and
655 the @samp{g++} program name to be transformed to
656 @file{/usr/local/bin/gspecial++} without changing other program names,
657 you could use the pattern
658 @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}
659 to achieve this effect.
661 All three options can be combined and used together, resulting in more
662 complex conversion patterns. As a basic rule, @var{prefix} (and
663 @var{suffix}) are prepended (appended) before further transformations
664 can happen with a special transformation script @var{pattern}.
666 As currently implemented, this option only takes effect for native
667 builds; cross compiler binaries' names are not transformed even when a
668 transformation is explicitly asked for by one of these options.
670 For native builds, some of the installed programs are also installed
671 with the target alias in front of their name, as in
672 @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
673 before the target alias is prepended to the name---so, specifying
674 @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
675 resulting binary would be installed as
676 @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.
678 As a last shortcoming, none of the installed Ada programs are
679 transformed yet, which will be fixed in some time.
681 @item --with-local-prefix=@var{dirname}
683 installation directory for local include files. The default is
684 @file{/usr/local}. Specify this option if you want the compiler to
685 search directory @file{@var{dirname}/include} for locally installed
686 header files @emph{instead} of @file{/usr/local/include}.
688 You should specify @option{--with-local-prefix} @strong{only} if your
689 site has a different convention (not @file{/usr/local}) for where to put
692 The default value for @option{--with-local-prefix} is @file{/usr/local}
693 regardless of the value of @option{--prefix}. Specifying
694 @option{--prefix} has no effect on which directory GCC searches for
695 local header files. This may seem counterintuitive, but actually it is
698 The purpose of @option{--prefix} is to specify where to @emph{install
699 GCC}. The local header files in @file{/usr/local/include}---if you put
700 any in that directory---are not part of GCC@. They are part of other
701 programs---perhaps many others. (GCC installs its own header files in
702 another directory which is based on the @option{--prefix} value.)
704 Both the local-prefix include directory and the GCC-prefix include
705 directory are part of GCC's ``system include'' directories. Although these
706 two directories are not fixed, they need to be searched in the proper
707 order for the correct processing of the include_next directive. The
708 local-prefix include directory is searched before the GCC-prefix
709 include directory. Another characteristic of system include directories
710 is that pedantic warnings are turned off for headers in these directories.
712 Some autoconf macros add @option{-I @var{directory}} options to the
713 compiler command line, to ensure that directories containing installed
714 packages' headers are searched. When @var{directory} is one of GCC's
715 system include directories, GCC will ignore the option so that system
716 directories continue to be processed in the correct order. This
717 may result in a search order different from what was specified but the
718 directory will still be searched.
720 GCC automatically searches for ordinary libraries using
721 @env{GCC_EXEC_PREFIX}. Thus, when the same installation prefix is
722 used for both GCC and packages, GCC will automatically search for
723 both headers and libraries. This provides a configuration that is
724 easy to use. GCC behaves in a manner similar to that when it is
725 installed as a system compiler in @file{/usr}.
727 Sites that need to install multiple versions of GCC may not want to
728 use the above simple configuration. It is possible to use the
729 @option{--program-prefix}, @option{--program-suffix} and
730 @option{--program-transform-name} options to install multiple versions
731 into a single directory, but it may be simpler to use different prefixes
732 and the @option{--with-local-prefix} option to specify the location of the
733 site-specific files for each version. It will then be necessary for
734 users to specify explicitly the location of local site libraries
735 (e.g., with @env{LIBRARY_PATH}).
737 The same value can be used for both @option{--with-local-prefix} and
738 @option{--prefix} provided it is not @file{/usr}. This can be used
739 to avoid the default search of @file{/usr/local/include}.
741 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
742 The directory you use for @option{--with-local-prefix} @strong{must not}
743 contain any of the system's standard header files. If it did contain
744 them, certain programs would be miscompiled (including GNU Emacs, on
745 certain targets), because this would override and nullify the header
746 file corrections made by the @command{fixincludes} script.
748 Indications are that people who use this option use it based on mistaken
749 ideas of what it is for. People use it as if it specified where to
750 install part of GCC@. Perhaps they make this assumption because
751 installing GCC creates the directory.
753 @item --enable-shared[=@var{package}[,@dots{}]]
754 Build shared versions of libraries, if shared libraries are supported on
755 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
756 are enabled by default on all platforms that support shared libraries.
758 If a list of packages is given as an argument, build shared libraries
759 only for the listed packages. For other packages, only static libraries
760 will be built. Package names currently recognized in the GCC tree are
761 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
762 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc},
763 @samp{ada}, @samp{libada}, @samp{libjava} and @samp{libobjc}.
764 Note @samp{libiberty} does not support shared libraries at all.
766 Use @option{--disable-shared} to build only static libraries. Note that
767 @option{--disable-shared} does not accept a list of package names as
768 argument, only @option{--enable-shared} does.
770 @item @anchor{with-gnu-as}--with-gnu-as
771 Specify that the compiler should assume that the
772 assembler it finds is the GNU assembler. However, this does not modify
773 the rules to find an assembler and will result in confusion if the
774 assembler found is not actually the GNU assembler. (Confusion may also
775 result if the compiler finds the GNU assembler but has not been
776 configured with @option{--with-gnu-as}.) If you have more than one
777 assembler installed on your system, you may want to use this option in
778 connection with @option{--with-as=@var{pathname}}.
780 The following systems are the only ones where it makes a difference
781 whether you use the GNU assembler. On any other system,
782 @option{--with-gnu-as} has no effect.
785 @item @samp{hppa1.0-@var{any}-@var{any}}
786 @item @samp{hppa1.1-@var{any}-@var{any}}
787 @item @samp{i386-@var{any}-sysv}
788 @item @samp{m68k-bull-sysv}
789 @item @samp{m68k-hp-hpux}
790 @item @samp{m68000-hp-hpux}
791 @item @samp{m68000-att-sysv}
792 @item @samp{sparc-sun-solaris2.@var{any}}
793 @item @samp{sparc64-@var{any}-solaris2.@var{any}}
796 On the systems listed above (except for the HP-PA, the SPARC, for ISC on
797 the 386, if you use the GNU assembler, you should also use the GNU linker
798 (and specify @option{--with-gnu-ld}).
800 @item @anchor{with-as}--with-as=@var{pathname}
802 compiler should use the assembler pointed to by @var{pathname}, rather
803 than the one found by the standard rules to find an assembler, which
807 Check the @file{@var{libexec}/gcc/@var{target}/@var{version}}
808 directory, where @var{libexec} defaults to
809 @file{@var{exec-prefix}/libexec} and @var{exec-prefix} defaults to
810 @var{prefix} which defaults to @file{/usr/local} unless overridden by
811 the @option{--prefix=@var{pathname}} switch described
812 above. @var{target} is the target system triple, such as
813 @samp{sparc-sun-solaris2.7}, and @var{version} denotes the GCC
814 version, such as 3.0.
816 Check operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
819 Note that these rules do not check for the value of @env{PATH}. You may
820 want to use @option{--with-as} if no assembler is installed in the
821 directories listed above, or if you have multiple assemblers installed
822 and want to choose one that is not found by the above rules.
824 @item @anchor{with-gnu-ld}--with-gnu-ld
825 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
828 @item --with-ld=@var{pathname}
829 Same as @uref{#with-as,,@option{--with-as}}
833 Specify that stabs debugging
834 information should be used instead of whatever format the host normally
835 uses. Normally GCC uses the same debug format as the host system.
837 On MIPS based systems and on Alphas, you must specify whether you want
838 GCC to create the normal ECOFF debugging format, or to use BSD-style
839 stabs passed through the ECOFF symbol table. The normal ECOFF debug
840 format cannot fully handle languages other than C@. BSD stabs format can
841 handle other languages, but it only works with the GNU debugger GDB@.
843 Normally, GCC uses the ECOFF debugging format by default; if you
844 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
846 No matter which default you choose when you configure GCC, the user
847 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
848 the debug format for a particular compilation.
850 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
851 @option{--with-gas} is used. It selects use of stabs debugging
852 information embedded in COFF output. This kind of debugging information
853 supports C++ well; ordinary COFF debugging information does not.
855 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
856 selects use of stabs debugging information embedded in ELF output. The
857 C++ compiler currently (2.6.0) does not support the DWARF debugging
858 information normally used on 386 SVR4 platforms; stabs provide a
859 workable alternative. This requires gas and gdb, as the normal SVR4
860 tools can not generate or interpret stabs.
862 @item --disable-multilib
863 Specify that multiple target
864 libraries to support different target variants, calling
865 conventions, etc should not be built. The default is to build a
866 predefined set of them.
868 Some targets provide finer-grained control over which multilibs are built
869 (e.g., @option{--disable-softfloat}):
875 fpu, 26bit, underscore, interwork, biendian, nofmult.
878 softfloat, m68881, m68000, m68020.
881 single-float, biendian, softfloat.
883 @item powerpc*-*-*, rs6000*-*-*
884 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
889 @item --enable-threads
890 Specify that the target
891 supports threads. This affects the Objective-C compiler and runtime
892 library, and exception handling for other languages like C++ and Java.
893 On some systems, this is the default.
895 In general, the best (and, in many cases, the only known) threading
896 model available will be configured for use. Beware that on some
897 systems, GCC has not been taught what threading models are generally
898 available for the system. In this case, @option{--enable-threads} is an
899 alias for @option{--enable-threads=single}.
901 @item --disable-threads
902 Specify that threading support should be disabled for the system.
903 This is an alias for @option{--enable-threads=single}.
905 @item --enable-threads=@var{lib}
907 @var{lib} is the thread support library. This affects the Objective-C
908 compiler and runtime library, and exception handling for other languages
909 like C++ and Java. The possibilities for @var{lib} are:
917 Ada tasking support. For non-Ada programs, this setting is equivalent
918 to @samp{single}. When used in conjunction with the Ada run time, it
919 causes GCC to use the same thread primitives as Ada uses. This option
920 is necessary when using both Ada and the back end exception handling,
921 which is the default for most Ada targets.
923 Generic MACH thread support, known to work on NeXTSTEP@. (Please note
924 that the file needed to support this configuration, @file{gthr-mach.h}, is
925 missing and thus this setting will cause a known bootstrap failure.)
927 This is an alias for @samp{single}.
929 Generic POSIX thread support.
931 RTEMS thread support.
933 Disable thread support, should work for all platforms.
935 Sun Solaris 2 thread support.
937 VxWorks thread support.
939 Microsoft Win32 API thread support.
941 Novell Kernel Services thread support.
944 @item --with-cpu=@var{cpu}
945 Specify which cpu variant the compiler should generate code for by default.
946 @var{cpu} will be used as the default value of the @option{-mcpu=} switch.
947 This option is only supported on some targets, including ARM, i386, PowerPC,
950 @item --with-schedule=@var{cpu}
951 @itemx --with-arch=@var{cpu}
952 @itemx --with-tune=@var{cpu}
953 @itemx --with-abi=@var{abi}
954 @itemx --with-fpu=@var{type}
955 @itemx --with-float=@var{type}
956 These configure options provide default values for the @option{-mschedule=},
957 @option{-march=}, @option{-mtune=}, @option{-mabi=}, and @option{-mfpu=}
958 options and for @option{-mhard-float} or @option{-msoft-float}. As with
959 @option{--with-cpu}, which switches will be accepted and acceptable values
960 of the arguments depend on the target.
962 @item --with-divide=@var{type}
963 Specify how the compiler should generate code for checking for
964 division by zero. This option is only supported on the MIPS target.
965 The possibilities for @var{type} are:
968 Division by zero checks use conditional traps (this is the default on
969 systems that support conditional traps).
971 Division by zero checks use the break instruction.
974 @item --enable-altivec
975 Specify that the target supports AltiVec vector enhancements. This
976 option will adjust the ABI for AltiVec enhancements, as well as generate
977 AltiVec code when appropriate. This option is only available for
980 @item --enable-__cxa_atexit
981 Define if you want to use __cxa_atexit, rather than atexit, to
982 register C++ destructors for local statics and global objects.
983 This is essential for fully standards-compliant handling of
984 destructors, but requires __cxa_atexit in libc. This option is currently
985 only available on systems with GNU libc. When enabled, this will cause
986 @option{-fuse-cxa-exit} to be passed by default.
988 @item --enable-target-optspace
990 libraries should be optimized for code space instead of code speed.
991 This is the default for the m32r platform.
994 Specify that a user visible @command{cpp} program should not be installed.
996 @item --with-cpp-install-dir=@var{dirname}
997 Specify that the user visible @command{cpp} program should be installed
998 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
1000 @item --enable-initfini-array
1001 Force the use of sections @code{.init_array} and @code{.fini_array}
1002 (instead of @code{.init} and @code{.fini}) for constructors and
1003 destructors. Option @option{--disable-initfini-array} has the
1004 opposite effect. If neither option is specified, the configure script
1005 will try to guess whether the @code{.init_array} and
1006 @code{.fini_array} sections are supported and, if they are, use them.
1008 @item --enable-maintainer-mode
1009 The build rules that
1010 regenerate the GCC master message catalog @file{gcc.pot} are normally
1011 disabled. This is because it can only be rebuilt if the complete source
1012 tree is present. If you have changed the sources and want to rebuild the
1013 catalog, configuring with @option{--enable-maintainer-mode} will enable
1014 this. Note that you need a recent version of the @code{gettext} tools
1017 @item --enable-generated-files-in-srcdir
1018 Neither the .c and .h files that are generated from bison and flex nor the
1019 info manuals and man pages that are built from the .texi files are present
1020 in the CVS development tree. When building GCC from that development tree,
1021 or from a snapshot which are created from CVS, then those generated files
1022 are placed in your build directory, which allows for the source to be in a
1025 If you configure with @option{--enable-generated-files-in-srcdir} then those
1026 generated files will go into the source directory. This is mainly intended
1027 for generating release or prerelease tarballs of the GCC sources, since it
1028 is not a requirement that the users of source releases to have flex, bison, or
1031 @item --enable-version-specific-runtime-libs
1033 that runtime libraries should be installed in the compiler specific
1034 subdirectory (@file{@var{libdir}/gcc}) rather than the usual places. In
1035 addition, @samp{libstdc++}'s include files will be installed into
1036 @file{@var{libdir}} unless you overruled it by using
1037 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
1038 particularly useful if you intend to use several versions of GCC in
1039 parallel. This is currently supported by @samp{libgfortran},
1040 @samp{libjava}, @samp{libmudflap}, @samp{libstdc++}, and @samp{libobjc}.
1043 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
1044 Specify that only a particular subset of compilers and
1045 their runtime libraries should be built. For a list of valid values for
1046 @var{langN} you can issue the following command in the
1047 @file{gcc} directory of your GCC source tree:@*
1049 grep language= */config-lang.in
1051 Currently, you can use any of the following:
1052 @code{ada}, @code{c}, @code{c++}, @code{f77}, @code{f95}, @code{java},
1053 @code{objc}, @code{obj-c++}.
1054 Building the Ada compiler has special requirements, see below.@*
1055 If you do not pass this flag, all languages available in the @file{gcc}
1056 sub-tree will be configured. Re-defining @code{LANGUAGES} when calling
1057 @samp{make bootstrap} @strong{does not} work anymore, as those
1058 language sub-directories might not have been configured!
1060 @item --disable-libada
1061 Specify that the run-time libraries and tools used by GNAT should not
1062 be built. This can be useful for debugging, or for compatibility with
1063 previous Ada build procedures, when it was required to explicitly
1064 do a @samp{make -C gcc gnatlib_and_tools}.
1067 Specify that the compiler should
1068 use DWARF 2 debugging information as the default.
1070 @item --enable-win32-registry
1071 @itemx --enable-win32-registry=@var{key}
1072 @itemx --disable-win32-registry
1073 The @option{--enable-win32-registry} option enables Microsoft Windows-hosted GCC
1074 to look up installations paths in the registry using the following key:
1077 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
1080 @var{key} defaults to GCC version number, and can be overridden by the
1081 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
1082 who use custom installers are encouraged to provide a different key,
1083 perhaps one comprised of vendor name and GCC version number, to
1084 avoid conflict with existing installations. This feature is enabled
1085 by default, and can be disabled by @option{--disable-win32-registry}
1086 option. This option has no effect on the other hosts.
1089 Specify that the machine does not have a floating point unit. This
1090 option only applies to @samp{m68k-sun-sunos@var{n}}. On any other
1091 system, @option{--nfp} has no effect.
1093 @item --enable-werror
1094 @itemx --disable-werror
1095 @itemx --enable-werror=yes
1096 @itemx --enable-werror=no
1097 When you specify this option, it controls whether certain files in the
1098 compiler are built with @option{-Werror} in bootstrap stage2 and later.
1099 If you don't specify it, @option{-Werror} is turned on for the main
1100 development trunk. However it defaults to off for release branches and
1101 final releases. The specific files which get @option{-Werror} are
1102 controlled by the Makefiles.
1104 @item --enable-checking
1105 @itemx --enable-checking=@var{list}
1106 When you specify this option, the compiler is built to perform checking
1107 of tree node types when referencing fields of that node, and some other
1108 internal consistency checks. This does not change the generated code,
1109 but adds error checking within the compiler. This will slow down the
1110 compiler and may only work properly if you are building the compiler
1111 with GCC@. This is on by default when building from CVS or snapshots,
1112 but off for releases. More control over the checks may be had by
1113 specifying @var{list}; the categories of checks available are
1114 @samp{release}, @samp{assert}, @samp{misc}, @samp{tree}, @samp{gc},
1115 @samp{rtl}, @samp{rtlflag}, @samp{fold}, @samp{gcac} and
1116 @samp{valgrind}. The @samp{release} category enables only those checks
1117 suitable for release builds, currently this is just @samp{assert}. The
1118 check @samp{valgrind} requires the external @command{valgrind}
1119 simulator, available from @uref{http://valgrind.kde.org/}. The checks
1120 @samp{rtl}, @samp{gcac} and @samp{valgrind} are very expensive. The
1121 default when @var{list} is not specified is
1122 @samp{assert,misc,tree,gc,rtlflag}. That is also the default for
1123 development builds, when @samp{--enable-checking} is not specified. For
1124 release builds the default, when @samp{--enable-checking} is not given,
1125 is @samp{release}. To disable all checking, @samp{--disable-checking}
1126 must be explicitly requested. Disabling assertions will make the
1127 compiler slightly faster but increase the risk of undetected internal
1128 errors causing wrong code to be generated.
1130 @item --enable-coverage
1131 @itemx --enable-coverage=@var{level}
1132 With this option, the compiler is built to collect self coverage
1133 information, every time it is run. This is for internal development
1134 purposes, and only works when the compiler is being built with gcc. The
1135 @var{level} argument controls whether the compiler is built optimized or
1136 not, values are @samp{opt} and @samp{noopt}. For coverage analysis you
1137 want to disable optimization, for performance analysis you want to
1138 enable optimization. When coverage is enabled, the default level is
1139 without optimization.
1141 @item --enable-gather-detailed-mem-stats
1142 When this option is specified more detailed information on memory
1143 allocation is gathered. This information is printed when using
1144 @option{-fmem-report}.
1147 @itemx --disable-nls
1148 The @option{--enable-nls} option enables Native Language Support (NLS),
1149 which lets GCC output diagnostics in languages other than American
1150 English. Native Language Support is enabled by default if not doing a
1151 canadian cross build. The @option{--disable-nls} option disables NLS@.
1153 @item --with-included-gettext
1154 If NLS is enabled, the @option{--with-included-gettext} option causes the build
1155 procedure to prefer its copy of GNU @command{gettext}.
1157 @item --with-catgets
1158 If NLS is enabled, and if the host lacks @code{gettext} but has the
1159 inferior @code{catgets} interface, the GCC build procedure normally
1160 ignores @code{catgets} and instead uses GCC's copy of the GNU
1161 @code{gettext} library. The @option{--with-catgets} option causes the
1162 build procedure to use the host's @code{catgets} in this situation.
1164 @item --with-libiconv-prefix=@var{dir}
1165 Search for libiconv header files in @file{@var{dir}/include} and
1166 libiconv library files in @file{@var{dir}/lib}.
1168 @item --enable-obsolete
1169 Enable configuration for an obsoleted system. If you attempt to
1170 configure GCC for a system (build, host, or target) which has been
1171 obsoleted, and you do not specify this flag, configure will halt with an
1174 All support for systems which have been obsoleted in one release of GCC
1175 is removed entirely in the next major release, unless someone steps
1176 forward to maintain the port.
1179 @subheading Cross-Compiler-Specific Options
1180 The following options only apply to building cross compilers.
1182 @item --with-sysroot
1183 @itemx --with-sysroot=@var{dir}
1184 Tells GCC to consider @var{dir} as the root of a tree that contains a
1185 (subset of) the root filesystem of the target operating system.
1186 Target system headers, libraries and run-time object files will be
1187 searched in there. The specified directory is not copied into the
1188 install tree, unlike the options @option{--with-headers} and
1189 @option{--with-libs} that this option obsoletes. The default value,
1190 in case @option{--with-sysroot} is not given an argument, is
1191 @option{$@{gcc_tooldir@}/sys-root}. If the specified directory is a
1192 subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to
1193 the GCC binaries if the installation tree is moved.
1195 @item --with-headers
1196 @itemx --with-headers=@var{dir}
1197 Deprecated in favor of @option{--with-sysroot}.
1198 Specifies that target headers are available when building a cross compiler.
1199 The @var{dir} argument specifies a directory which has the target include
1200 files. These include files will be copied into the @file{gcc} install
1201 directory. @emph{This option with the @var{dir} argument is required} when
1202 building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include}
1203 doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does
1204 pre-exist, the @var{dir} argument may be omitted. @command{fixincludes}
1205 will be run on these files to make them compatible with GCC@.
1207 @item --without-headers
1208 Tells GCC not use any target headers from a libc when building a cross
1209 compiler. When crossing to GNU/Linux, you need the headers so GCC
1210 can build the exception handling for libgcc.
1211 See @uref{http://www.objsw.com/CrossGCC/,,CrossGCC} for more information
1215 @itemx --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
1216 Deprecated in favor of @option{--with-sysroot}.
1217 Specifies a list of directories which contain the target runtime
1218 libraries. These libraries will be copied into the @file{gcc} install
1219 directory. If the directory list is omitted, this option has no
1222 Specifies that @samp{newlib} is
1223 being used as the target C library. This causes @code{__eprintf} to be
1224 omitted from @file{libgcc.a} on the assumption that it will be provided by
1228 @subheading Fortran-specific Option
1230 The following options apply to the build of the Fortran front end.
1234 @item --with-gmp=@var{pathname}
1235 @itemx --with-mpfr=@var{pathname}
1236 @itemx --with-gmp-dir=@var{pathname}
1237 @itemx --with-mpfr-dir=@var{pathname}
1238 If you don't have GMP (the GNU Multiple Precision library) and the MPFR
1239 Libraries installed in a standard location and you want to build the Fortran
1240 front-end, you can explicitly specify the directory where they are installed
1241 (@samp{--with-gmp=gmpinstalldir}, @samp{--with-mpfr=mpfrinstalldir}) or where
1242 you built them without installing (@samp{--with-gmp-dir=gmpbuilddir},
1243 @samp{--with-mpfr-dir=gmpbuilddir}).
1247 @subheading Java-Specific Options
1249 The following option applies to the build of the Java front end.
1252 @item --disable-libgcj
1253 Specify that the run-time libraries
1254 used by GCJ should not be built. This is useful in case you intend
1255 to use GCJ with some other run-time, or you're going to install it
1256 separately, or it just happens not to build on your particular
1257 machine. In general, if the Java front end is enabled, the GCJ
1258 libraries will be enabled too, unless they're known to not work on
1259 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
1260 may need to port it; in this case, before modifying the top-level
1261 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
1262 you may use @option{--enable-libgcj} to override the default.
1266 The following options apply to building @samp{libgcj}.
1268 @subsubheading General Options
1271 @item --disable-getenv-properties
1272 Don't set system properties from @env{GCJ_PROPERTIES}.
1274 @item --enable-hash-synchronization
1275 Use a global hash table for monitor locks. Ordinarily,
1276 @samp{libgcj}'s @samp{configure} script automatically makes
1277 the correct choice for this option for your platform. Only use
1278 this if you know you need the library to be configured differently.
1280 @item --enable-interpreter
1281 Enable the Java interpreter. The interpreter is automatically
1282 enabled by default on all platforms that support it. This option
1283 is really only useful if you want to disable the interpreter
1284 (using @option{--disable-interpreter}).
1286 @item --disable-java-net
1287 Disable java.net. This disables the native part of java.net only,
1288 using non-functional stubs for native method implementations.
1290 @item --disable-jvmpi
1291 Disable JVMPI support.
1294 Enable runtime eCos target support.
1296 @item --without-libffi
1297 Don't use @samp{libffi}. This will disable the interpreter and JNI
1298 support as well, as these require @samp{libffi} to work.
1300 @item --enable-libgcj-debug
1301 Enable runtime debugging code.
1303 @item --enable-libgcj-multifile
1304 If specified, causes all @file{.java} source files to be
1305 compiled into @file{.class} files in one invocation of
1306 @samp{gcj}. This can speed up build time, but is more
1307 resource-intensive. If this option is unspecified or
1308 disabled, @samp{gcj} is invoked once for each @file{.java}
1309 file to compile into a @file{.class} file.
1311 @item --with-libiconv-prefix=DIR
1312 Search for libiconv in @file{DIR/include} and @file{DIR/lib}.
1314 @item --enable-sjlj-exceptions
1315 Force use of @code{builtin_setjmp} for exceptions. @samp{configure}
1316 ordinarily picks the correct value based on the platform. Only use
1317 this option if you are sure you need a different setting.
1319 @item --with-system-zlib
1320 Use installed @samp{zlib} rather than that included with GCC@.
1322 @item --with-win32-nlsapi=ansi, unicows or unicode
1323 Indicates how MinGW @samp{libgcj} translates between UNICODE
1324 characters and the Win32 API@.
1327 Use the single-byte @code{char} and the Win32 A functions natively,
1328 translating to and from UNICODE when using these functions. If
1329 unspecified, this is the default.
1332 Use the @code{WCHAR} and Win32 W functions natively. Adds
1333 @code{-lunicows} to @file{libgcj.spec} to link with @samp{libunicows}.
1334 @file{unicows.dll} needs to be deployed on Microsoft Windows 9X machines
1335 running built executables. @file{libunicows.a}, an open-source
1336 import library around Microsoft's @code{unicows.dll}, is obtained from
1337 @uref{http://libunicows.sourceforge.net/}, which also gives details
1338 on getting @file{unicows.dll} from Microsoft.
1341 Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not}
1342 add @code{-lunicows} to @file{libgcj.spec}. The built executables will
1343 only run on Microsoft Windows NT and above.
1347 @subsubheading AWT-Specific Options
1351 Use the X Window System.
1353 @item --enable-java-awt=PEER(S)
1354 Specifies the AWT peer library or libraries to build alongside
1355 @samp{libgcj}. If this option is unspecified or disabled, AWT
1356 will be non-functional. Current valid values are @option{gtk} and
1357 @option{xlib}. Multiple libraries should be separated by a
1358 comma (i.e.@: @option{--enable-java-awt=gtk,xlib}).
1360 @item --enable-gtk-cairo
1361 Build the cairo Graphics2D implementation on GTK@.
1363 @item --enable-java-gc=TYPE
1364 Choose garbage collector. Defaults to @option{boehm} if unspecified.
1366 @item --disable-gtktest
1367 Do not try to compile and run a test GTK+ program.
1369 @item --disable-glibtest
1370 Do not try to compile and run a test GLIB program.
1372 @item --with-libart-prefix=PFX
1373 Prefix where libart is installed (optional).
1375 @item --with-libart-exec-prefix=PFX
1376 Exec prefix where libart is installed (optional).
1378 @item --disable-libarttest
1379 Do not try to compile and run a test libart program.
1388 @uref{./index.html,,Return to the GCC Installation page}
1392 @c ***Building****************************************************************
1394 @comment node-name, next, previous, up
1395 @node Building, Testing, Configuration, Installing GCC
1401 @cindex Installing GCC: Building
1403 Now that GCC is configured, you are ready to build the compiler and
1406 Some commands executed when making the compiler may fail (return a
1407 nonzero status) and be ignored by @command{make}. These failures, which
1408 are often due to files that were not found, are expected, and can safely
1411 It is normal to have compiler warnings when compiling certain files.
1412 Unless you are a GCC developer, you can generally ignore these warnings
1413 unless they cause compilation to fail. Developers should attempt to fix
1414 any warnings encountered, however they can temporarily continue past
1415 warnings-as-errors by specifying the configure flag
1416 @option{--disable-werror}.
1418 On certain old systems, defining certain environment variables such as
1419 @env{CC} can interfere with the functioning of @command{make}.
1421 If you encounter seemingly strange errors when trying to build the
1422 compiler in a directory other than the source directory, it could be
1423 because you have previously configured the compiler in the source
1424 directory. Make sure you have done all the necessary preparations.
1426 If you build GCC on a BSD system using a directory stored in an old System
1427 V file system, problems may occur in running @command{fixincludes} if the
1428 System V file system doesn't support symbolic links. These problems
1429 result in a failure to fix the declaration of @code{size_t} in
1430 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
1431 that type mismatches occur, this could be the cause.
1433 The solution is not to use such a directory for building GCC@.
1435 When building from CVS or snapshots, or if you modify parser sources,
1436 you need the Bison parser generator installed. Any version 1.25 or
1437 later should work; older versions may also work. If you do not modify
1438 parser sources, releases contain the Bison-generated files and you do
1439 not need Bison installed to build them.
1441 When building from CVS or snapshots, or if you modify Texinfo
1442 documentation, you need version 4.2 or later of Texinfo installed if you
1443 want Info documentation to be regenerated. Releases contain Info
1444 documentation pre-built for the unmodified documentation in the release.
1446 @section Building a native compiler
1448 For a native build issue the command @samp{make bootstrap}. This
1449 will build the entire GCC system, which includes the following steps:
1453 Build host tools necessary to build the compiler such as texinfo, bison,
1457 Build target tools for use by the compiler such as binutils (bfd,
1458 binutils, gas, gprof, ld, and opcodes)
1459 if they have been individually linked
1460 or moved into the top level GCC source tree before configuring.
1463 Perform a 3-stage bootstrap of the compiler.
1466 Perform a comparison test of the stage2 and stage3 compilers.
1469 Build runtime libraries using the stage3 compiler from the previous step.
1473 If you are short on disk space you might consider @samp{make
1474 bootstrap-lean} instead. This is identical to @samp{make
1475 bootstrap} except that object files from the stage1 and
1476 stage2 of the 3-stage bootstrap of the compiler are deleted as
1477 soon as they are no longer needed.
1479 If you want to save additional space during the bootstrap and in
1480 the final installation as well, you can build the compiler binaries
1481 without debugging information as in the following example. This will save
1482 roughly 40% of disk space both for the bootstrap and the final installation.
1483 (Libraries will still contain debugging information.)
1486 make CFLAGS='-O' LIBCFLAGS='-g -O2' \
1487 LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap
1490 If you wish to use non-default GCC flags when compiling the stage2 and
1491 stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing
1492 @samp{make bootstrap}. Non-default optimization flags are less well
1493 tested here than the default of @samp{-g -O2}, but should still work.
1494 In a few cases, you may find that you need to specify special flags such
1495 as @option{-msoft-float} here to complete the bootstrap; or, if the
1496 native compiler miscompiles the stage1 compiler, you may need to work
1497 around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the
1498 stage1 compiler that were miscompiled, or by using @samp{make
1499 bootstrap4} to increase the number of stages of bootstrap.
1501 Note that using non-standard @code{CFLAGS} can cause bootstrap to fail in
1502 @file{libiberty}, if these trigger a warning with the new compiler. For
1503 example using @samp{-O2 -g -mcpu=i686} on @code{i686-pc-linux-gnu} will
1504 cause bootstrap failure as @option{-mcpu=} is deprecated in 3.4.0 and above.
1507 If you used the flag @option{--enable-languages=@dots{}} to restrict
1508 the compilers to be built, only those you've actually enabled will be
1509 built. This will of course only build those runtime libraries, for
1510 which the particular compiler has been built. Please note,
1511 that re-defining @env{LANGUAGES} when calling @samp{make bootstrap}
1512 @strong{does not} work anymore!
1514 If the comparison of stage2 and stage3 fails, this normally indicates
1515 that the stage2 compiler has compiled GCC incorrectly, and is therefore
1516 a potentially serious bug which you should investigate and report. (On
1517 a few systems, meaningful comparison of object files is impossible; they
1518 always appear ``different''. If you encounter this problem, you will
1519 need to disable comparison in the @file{Makefile}.)
1521 @section Building a cross compiler
1523 We recommend reading the
1524 @uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ}
1525 for information about building cross compilers.
1527 When building a cross compiler, it is not generally possible to do a
1528 3-stage bootstrap of the compiler. This makes for an interesting problem
1529 as parts of GCC can only be built with GCC@.
1531 To build a cross compiler, we first recommend building and installing a
1532 native compiler. You can then use the native GCC compiler to build the
1533 cross compiler. The installed native compiler needs to be GCC version
1536 Assuming you have already installed a native copy of GCC and configured
1537 your cross compiler, issue the command @command{make}, which performs the
1542 Build host tools necessary to build the compiler such as texinfo, bison,
1546 Build target tools for use by the compiler such as binutils (bfd,
1547 binutils, gas, gprof, ld, and opcodes)
1548 if they have been individually linked or moved into the top level GCC source
1549 tree before configuring.
1552 Build the compiler (single stage only).
1555 Build runtime libraries using the compiler from the previous step.
1558 Note that if an error occurs in any step the make process will exit.
1560 If you are not building GNU binutils in the same source tree as GCC,
1561 you will need a cross-assembler and cross-linker installed before
1562 configuring GCC@. Put them in the directory
1563 @file{@var{prefix}/@var{target}/bin}. Here is a table of the tools
1564 you should put in this directory:
1568 This should be the cross-assembler.
1571 This should be the cross-linker.
1574 This should be the cross-archiver: a program which can manipulate
1575 archive files (linker libraries) in the target machine's format.
1578 This should be a program to construct a symbol table in an archive file.
1581 The installation of GCC will find these programs in that directory,
1582 and copy or link them to the proper place to for the cross-compiler to
1583 find them when run later.
1585 The easiest way to provide these files is to build the Binutils package.
1586 Configure it with the same @option{--host} and @option{--target}
1587 options that you use for configuring GCC, then build and install
1588 them. They install their executables automatically into the proper
1589 directory. Alas, they do not support all the targets that GCC
1592 If you are not building a C library in the same source tree as GCC,
1593 you should also provide the target libraries and headers before
1594 configuring GCC, specifying the directories with
1595 @option{--with-sysroot} or @option{--with-headers} and
1596 @option{--with-libs}. Many targets also require ``start files'' such
1597 as @file{crt0.o} and
1598 @file{crtn.o} which are linked into each executable. There may be several
1599 alternatives for @file{crt0.o}, for use with profiling or other
1600 compilation options. Check your target's definition of
1601 @code{STARTFILE_SPEC} to find out what start files it uses.
1603 @section Building in parallel
1605 You can use @samp{make bootstrap MAKE="make -j 2" -j 2}, or just
1606 @samp{make -j 2 bootstrap} for GNU Make 3.79 and above, instead of
1607 @samp{make bootstrap} to build GCC in parallel.
1608 You can also specify a bigger number, and in most cases using a value
1609 greater than the number of processors in your machine will result in
1610 fewer and shorter I/O latency hits, thus improving overall throughput;
1611 this is especially true for slow drives and network filesystems.
1613 @section Building the Ada compiler
1615 In order to build GNAT, the Ada compiler, you need a working GNAT
1616 compiler (GNAT version 3.14 or later, or GCC version 3.1 or later),
1617 including GNAT tools such as @command{gnatmake} and @command{gnatlink},
1618 since the Ada front end is written in Ada (with some
1619 GNAT-specific extensions), and GNU make.
1621 @command{configure} does not test whether the GNAT installation works
1622 and has a sufficiently recent version; if too old a GNAT version is
1623 installed, the build will fail unless @option{--enable-languages} is
1624 used to disable building the Ada front end.
1626 @section Building with profile feedback
1628 It is possible to use profile feedback to optimize the compiler itself. This
1629 should result in a faster compiler binary. Experiments done on x86 using gcc
1630 3.3 showed approximately 7 percent speedup on compiling C programs. To
1631 bootstrap compiler with profile feedback, use @code{make profiledbootstrap}.
1633 When @samp{make profiledbootstrap} is run, it will first build a @code{stage1}
1634 compiler. This compiler is used to build a @code{stageprofile} compiler
1635 instrumented to collect execution counts of instruction and branch
1636 probabilities. Then runtime libraries are compiled with profile collected.
1637 Finally a @code{stagefeedback} compiler is built using the information collected.
1639 Unlike @samp{make bootstrap} several additional restrictions apply. The
1640 compiler used to build @code{stage1} needs to support a 64-bit integral type.
1641 It is recommended to only use GCC for this. Also parallel make is currently
1642 not supported since collisions in profile collecting may occur.
1649 @uref{./index.html,,Return to the GCC Installation page}
1653 @c ***Testing*****************************************************************
1655 @comment node-name, next, previous, up
1656 @node Testing, Final install, Building, Installing GCC
1660 @chapter Installing GCC: Testing
1663 @cindex Installing GCC: Testing
1666 Before you install GCC, we encourage you to run the testsuites and to
1667 compare your results with results from a similar configuration that have
1668 been submitted to the
1669 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
1670 Some of these archived results are linked from the build status lists
1671 at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who
1672 reports a successful build runs the testsuites and submits the results.
1673 This step is optional and may require you to download additional software,
1674 but it can give you confidence in your new GCC installation or point out
1675 problems before you install and start using your new GCC@.
1677 First, you must have @uref{download.html,,downloaded the testsuites}.
1678 These are part of the full distribution, but if you downloaded the
1679 ``core'' compiler plus any front ends, you must download the testsuites
1682 Second, you must have the testing tools installed. This includes
1683 @uref{http://www.gnu.org/software/dejagnu/,,DejaGnu} 1.4.4 and later,
1684 Tcl, and Expect; the DejaGnu site has links to these.
1686 If the directories where @command{runtest} and @command{expect} were
1687 installed are not in the @env{PATH}, you may need to set the following
1688 environment variables appropriately, as in the following example (which
1689 assumes that DejaGnu has been installed under @file{/usr/local}):
1692 TCL_LIBRARY = /usr/local/share/tcl8.0
1693 DEJAGNULIBS = /usr/local/share/dejagnu
1696 (On systems such as Cygwin, these paths are required to be actual
1697 paths, not mounts or links; presumably this is due to some lack of
1698 portability in the DejaGnu code.)
1701 Finally, you can run the testsuite (which may take a long time):
1703 cd @var{objdir}; make -k check
1706 This will test various components of GCC, such as compiler
1707 front ends and runtime libraries. While running the testsuite, DejaGnu
1708 might emit some harmless messages resembling
1709 @samp{WARNING: Couldn't find the global config file.} or
1710 @samp{WARNING: Couldn't find tool init file} that can be ignored.
1712 @section How can you run the testsuite on selected tests?
1714 In order to run sets of tests selectively, there are targets
1715 @samp{make check-gcc} and @samp{make check-g++}
1716 in the @file{gcc} subdirectory of the object directory. You can also
1717 just run @samp{make check} in a subdirectory of the object directory.
1720 A more selective way to just run all @command{gcc} execute tests in the
1724 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
1727 Likewise, in order to run only the @command{g++} ``old-deja'' tests in
1728 the testsuite with filenames matching @samp{9805*}, you would use
1731 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
1734 The @file{*.exp} files are located in the testsuite directories of the GCC
1735 source, the most important ones being @file{compile.exp},
1736 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
1737 To get a list of the possible @file{*.exp} files, pipe the
1738 output of @samp{make check} into a file and look at the
1739 @samp{Running @dots{} .exp} lines.
1741 @section Passing options and running multiple testsuites
1743 You can pass multiple options to the testsuite using the
1744 @samp{--target_board} option of DejaGNU, either passed as part of
1745 @samp{RUNTESTFLAGS}, or directly to @command{runtest} if you prefer to
1746 work outside the makefiles. For example,
1749 make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fno-strength-reduce"
1752 will run the standard @command{g++} testsuites (``unix'' is the target name
1753 for a standard native testsuite situation), passing
1754 @samp{-O3 -fno-strength-reduce} to the compiler on every test, i.e.,
1755 slashes separate options.
1757 You can run the testsuites multiple times using combinations of options
1758 with a syntax similar to the brace expansion of popular shells:
1761 @dots{}"--target_board=arm-sim/@{-mhard-float,-msoft-float@}@{-O1,-O2,-O3,@}"
1764 (Note the empty option caused by the trailing comma in the final group.)
1765 The following will run each testsuite eight times using the @samp{arm-sim}
1766 target, as if you had specified all possible combinations yourself:
1769 --target_board=arm-sim/-mhard-float/-O1
1770 --target_board=arm-sim/-mhard-float/-O2
1771 --target_board=arm-sim/-mhard-float/-O3
1772 --target_board=arm-sim/-mhard-float
1773 --target_board=arm-sim/-msoft-float/-O1
1774 --target_board=arm-sim/-msoft-float/-O2
1775 --target_board=arm-sim/-msoft-float/-O3
1776 --target_board=arm-sim/-msoft-float
1779 They can be combined as many times as you wish, in arbitrary ways. This
1783 @dots{}"--target_board=unix/-Wextra@{-O3,-fno-strength-reduce@}@{-fomit-frame-pointer,@}"
1786 will generate four combinations, all involving @samp{-Wextra}.
1788 The disadvantage to this method is that the testsuites are run in serial,
1789 which is a waste on multiprocessor systems. For users with GNU Make and
1790 a shell which performs brace expansion, you can run the testsuites in
1791 parallel by having the shell perform the combinations and @command{make}
1792 do the parallel runs. Instead of using @samp{--target_board}, use a
1793 special makefile target:
1796 make -j@var{N} check-@var{testsuite}//@var{test-target}/@var{option1}/@var{option2}/@dots{}
1802 make -j3 check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@}
1805 will run three concurrent ``make-gcc'' testsuites, eventually testing all
1806 ten combinations as described above. Note that this is currently only
1807 supported in the @file{gcc} subdirectory. (To see how this works, try
1808 typing @command{echo} before the example given here.)
1811 @section Additional testing for Java Class Libraries
1813 The Java runtime tests can be executed via @samp{make check}
1814 in the @file{@var{target}/libjava/testsuite} directory in
1817 The @uref{http://sources.redhat.com/mauve/,,Mauve Project} provides
1818 a suite of tests for the Java Class Libraries. This suite can be run
1819 as part of libgcj testing by placing the Mauve tree within the libjava
1820 testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by
1821 specifying the location of that tree when invoking @samp{make}, as in
1822 @samp{make MAUVEDIR=~/mauve check}.
1824 @uref{http://www-124.ibm.com/developerworks/oss/cvs/jikes/~checkout~/jacks/jacks.html,,Jacks}
1825 is a free testsuite that tests Java compiler front ends. This suite
1826 can be run as part of libgcj testing by placing the Jacks tree within
1827 the libjava testsuite at @file{libjava/testsuite/libjava.jacks/jacks}.
1829 @section How to interpret test results
1831 The result of running the testsuite are various @file{*.sum} and @file{*.log}
1832 files in the testsuite subdirectories. The @file{*.log} files contain a
1833 detailed log of the compiler invocations and the corresponding
1834 results, the @file{*.sum} files summarize the results. These summaries
1835 contain status codes for all tests:
1839 PASS: the test passed as expected
1841 XPASS: the test unexpectedly passed
1843 FAIL: the test unexpectedly failed
1845 XFAIL: the test failed as expected
1847 UNSUPPORTED: the test is not supported on this platform
1849 ERROR: the testsuite detected an error
1851 WARNING: the testsuite detected a possible problem
1854 It is normal for some tests to report unexpected failures. At the
1855 current time the testing harness does not allow fine grained control
1856 over whether or not a test is expected to fail. This problem should
1857 be fixed in future releases.
1860 @section Submitting test results
1862 If you want to report the results to the GCC project, use the
1863 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
1866 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
1867 -m gcc-testresults@@gcc.gnu.org |sh
1870 This script uses the @command{Mail} program to send the results, so
1871 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
1872 prepended to the testsuite summary and should contain any special
1873 remarks you have on your results or your build environment. Please
1874 do not edit the testsuite result block or the subject line, as these
1875 messages may be automatically processed.
1882 @uref{./index.html,,Return to the GCC Installation page}
1886 @c ***Final install***********************************************************
1888 @comment node-name, next, previous, up
1889 @node Final install, , Testing, Installing GCC
1891 @ifset finalinstallhtml
1893 @chapter Installing GCC: Final installation
1896 Now that GCC has been built (and optionally tested), you can install it with
1898 cd @var{objdir}; make install
1901 We strongly recommend to install into a target directory where there is
1902 no previous version of GCC present.
1904 That step completes the installation of GCC; user level binaries can
1905 be found in @file{@var{prefix}/bin} where @var{prefix} is the value
1906 you specified with the @option{--prefix} to configure (or
1907 @file{/usr/local} by default). (If you specified @option{--bindir},
1908 that directory will be used instead; otherwise, if you specified
1909 @option{--exec-prefix}, @file{@var{exec-prefix}/bin} will be used.)
1910 Headers for the C++ and Java libraries are installed in
1911 @file{@var{prefix}/include}; libraries in @file{@var{libdir}}
1912 (normally @file{@var{prefix}/lib}); internal parts of the compiler in
1913 @file{@var{libdir}/gcc} and @file{@var{libexecdir}/gcc}; documentation
1914 in info format in @file{@var{infodir}} (normally
1915 @file{@var{prefix}/info}).
1917 When installing cross-compilers, GCC's executables
1918 are not only installed into @file{@var{bindir}}, that
1919 is, @file{@var{exec-prefix}/bin}, but additionally into
1920 @file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory
1921 exists. Typically, such @dfn{tooldirs} hold target-specific
1922 binutils, including assembler and linker.
1924 Installation into a temporary staging area or into a @command{chroot}
1925 jail can be achieved with the command
1928 make DESTDIR=@var{path-to-rootdir} install
1931 @noindent where @var{path-to-rootdir} is the absolute path of
1932 a directory relative to which all installation paths will be
1933 interpreted. Note that the directory specified by @code{DESTDIR}
1934 need not exist yet; it will be created if necessary.
1936 There is a subtle point with tooldirs and @code{DESTDIR}:
1937 If you relocate a cross-compiler installation with
1938 e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory
1939 @file{@var{rootdir}/@var{exec-prefix}/@var{target-alias}/bin} will
1940 be filled with duplicated GCC executables only if it already exists,
1941 it will not be created otherwise. This is regarded as a feature,
1942 not as a bug, because it gives slightly more control to the packagers
1943 using the @code{DESTDIR} feature.
1945 If you built a released version of GCC using @samp{make bootstrap} then please
1946 quickly review the build status page for your release, available from
1947 @uref{http://gcc.gnu.org/buildstat.html}.
1948 If your system is not listed for the version of GCC that you built,
1950 @email{gcc@@gcc.gnu.org} indicating
1951 that you successfully built and installed GCC@.
1952 Include the following information:
1956 Output from running @file{@var{srcdir}/config.guess}. Do not send
1957 that file itself, just the one-line output from running it.
1960 The output of @samp{gcc -v} for your newly installed @command{gcc}.
1961 This tells us which version of GCC you built and the options you passed to
1965 Whether you enabled all languages or a subset of them. If you used a
1966 full distribution then this information is part of the configure
1967 options in the output of @samp{gcc -v}, but if you downloaded the
1968 ``core'' compiler plus additional front ends then it isn't apparent
1969 which ones you built unless you tell us about it.
1972 If the build was for GNU/Linux, also include:
1975 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
1976 this information should be available from @file{/etc/issue}.
1979 The version of the Linux kernel, available from @samp{uname --version}
1983 The version of glibc you used; for RPM-based systems like Red Hat,
1984 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
1985 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
1987 For other systems, you can include similar information if you think it is
1991 Any other information that you think would be useful to people building
1992 GCC on the same configuration. The new entry in the build status list
1993 will include a link to the archived copy of your message.
1996 We'd also like to know if the
1998 @ref{Specific, host/target specific installation notes}
2001 @uref{specific.html,,host/target specific installation notes}
2003 didn't include your host/target information or if that information is
2004 incomplete or out of date. Send a note to
2005 @email{gcc@@gcc.gnu.org} detailing how the information should be changed.
2007 If you find a bug, please report it following the
2008 @uref{../bugs.html,,bug reporting guidelines}.
2010 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
2011 dvi}. You will need to have @command{texi2dvi} (version at least 4.2)
2012 and @TeX{} installed. This creates a number of @file{.dvi} files in
2013 subdirectories of @file{@var{objdir}}; these may be converted for
2014 printing with programs such as @command{dvips}. You can also
2015 @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the
2016 Free Software Foundation}, though such manuals may not be for the most
2017 recent version of GCC@.
2024 @uref{./index.html,,Return to the GCC Installation page}
2028 @c ***Binaries****************************************************************
2030 @comment node-name, next, previous, up
2031 @node Binaries, Specific, Installing GCC, Top
2035 @chapter Installing GCC: Binaries
2038 @cindex Installing GCC: Binaries
2040 We are often asked about pre-compiled versions of GCC@. While we cannot
2041 provide these for all platforms, below you'll find links to binaries for
2042 various platforms where creating them by yourself is not easy due to various
2045 Please note that we did not create these binaries, nor do we
2046 support them. If you have any problems installing them, please
2047 contact their makers.
2054 @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX};
2057 @uref{http://aixpdslib.seas.ucla.edu,,UCLA Software Library for AIX}.
2061 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}.
2064 Renesas H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
2065 Development Tools for the Renesas H8/300[HS] Series}.
2071 @uref{http://hpux.cae.wisc.edu/,,HP-UX Porting Center};
2074 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
2078 Motorola 68HC11/68HC12---@uref{http://www.gnu-m68hc11.org,,GNU
2079 Development Tools for the Motorola 68HC11/68HC12}.
2082 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
2083 OpenServer/Unixware}.
2086 Sinix/Reliant Unix---@uref{ftp://ftp.fujitsu-siemens.com/pub/pd/gnu/gcc/,,Siemens}.
2089 Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware}.
2092 SGI---@uref{http://freeware.sgi.com/,,SGI Freeware}.
2098 The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project;
2100 The @uref{http://www.mingw.org/,,MinGW} project.
2104 @uref{ftp://ftp.thewrittenword.com/packages/by-name/,,The
2105 Written Word} offers binaries for
2108 Digital UNIX 4.0D and 5.1,
2110 HP-UX 10.20, 11.00, and 11.11, and
2111 Solaris/SPARC 2.5.1, 2.6, 2.7, 8, and 9,
2114 @uref{http://www.openpkg.org/,,OpenPKG} offers binaries for quite a
2115 number of platforms.
2118 In addition to those specific offerings, you can get a binary
2119 distribution CD-ROM from the
2120 @uref{http://www.fsf.org/order/order.html,,Free Software Foundation}.
2121 It contains binaries for a number of platforms, and
2122 includes not only GCC, but other stuff as well. The current CD does
2123 not contain the latest version of GCC, but it should allow
2124 bootstrapping the compiler. An updated version of that disk is in the
2132 @uref{./index.html,,Return to the GCC Installation page}
2136 @c ***Specific****************************************************************
2138 @comment node-name, next, previous, up
2139 @node Specific, Old, Binaries, Top
2143 @chapter Host/target specific installation notes for GCC
2146 @cindex Specific installation notes
2147 @cindex Target specific installation
2148 @cindex Host specific installation
2149 @cindex Target specific installation notes
2151 Please read this document carefully @emph{before} installing the
2152 GNU Compiler Collection on your machine.
2157 @uref{#alpha*-*-*,,alpha*-*-*}
2159 @uref{#alpha*-dec-osf*,,alpha*-dec-osf*}
2161 @uref{#alphaev5-cray-unicosmk*,,alphaev5-cray-unicosmk*}
2163 @uref{#arc-*-elf,,arc-*-elf}
2165 @uref{#arm-*-elf,,arm-*-elf}
2166 @uref{#arm-*-coff,,arm-*-coff}
2167 @uref{#arm-*-aout,,arm-*-aout}
2169 @uref{#xscale-*-*,,xscale-*-*}
2177 @uref{#*-*-freebsd*,,*-*-freebsd*}
2179 @uref{#h8300-hms,,h8300-hms}
2181 @uref{#hppa*-hp-hpux*,,hppa*-hp-hpux*}
2183 @uref{#hppa*-hp-hpux10,,hppa*-hp-hpux10}
2185 @uref{#hppa*-hp-hpux11,,hppa*-hp-hpux11}
2187 @uref{#*-*-linux-gnu,,*-*-linux-gnu}
2189 @uref{#ix86-*-linux*aout,,i?86-*-linux*aout}
2191 @uref{#ix86-*-linux*,,i?86-*-linux*}
2193 @uref{#ix86-*-sco3.2v5*,,i?86-*-sco3.2v5*}
2195 @uref{#ix86-*-udk,,i?86-*-udk}
2197 @uref{#ix86-*-esix,,i?86-*-esix}
2199 @uref{#ia64-*-linux,,ia64-*-linux}
2201 @uref{#ia64-*-hpux*,,ia64-*-hpux*}
2203 @uref{#*-ibm-aix*,,*-ibm-aix*}
2205 @uref{#ip2k-*-elf,,ip2k-*-elf}
2207 @uref{#iq2000-*-elf,,iq2000-*-elf}
2209 @uref{#m32r-*-elf,,m32r-*-elf}
2211 @uref{#m6811-elf,,m6811-elf}
2213 @uref{#m6812-elf,,m6812-elf}
2215 @uref{#m68k-hp-hpux,,m68k-hp-hpux}
2217 @uref{#mips-*-*,,mips-*-*}
2219 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
2221 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
2223 @uref{#powerpc*-*-*,,powerpc*-*-*, powerpc-*-sysv4}
2225 @uref{#powerpc-*-darwin*,,powerpc-*-darwin*}
2227 @uref{#powerpc-*-elf,,powerpc-*-elf, powerpc-*-sysv4}
2229 @uref{#powerpc-*-linux-gnu*,,powerpc-*-linux-gnu*}
2231 @uref{#powerpc-*-netbsd*,,powerpc-*-netbsd*}
2233 @uref{#powerpc-*-eabiaix,,powerpc-*-eabiaix}
2235 @uref{#powerpc-*-eabisim,,powerpc-*-eabisim}
2237 @uref{#powerpc-*-eabi,,powerpc-*-eabi}
2239 @uref{#powerpcle-*-elf,,powerpcle-*-elf, powerpcle-*-sysv4}
2241 @uref{#powerpcle-*-eabisim,,powerpcle-*-eabisim}
2243 @uref{#powerpcle-*-eabi,,powerpcle-*-eabi}
2245 @uref{#s390-*-linux*,,s390-*-linux*}
2247 @uref{#s390x-*-linux*,,s390x-*-linux*}
2249 @uref{#s390x-ibm-tpf*,,s390x-ibm-tpf*}
2251 @uref{#*-*-solaris2*,,*-*-solaris2*}
2253 @uref{#sparc-sun-solaris2*,,sparc-sun-solaris2*}
2255 @uref{#sparc-sun-solaris2.7,,sparc-sun-solaris2.7}
2257 @uref{#sparc-*-linux*,,sparc-*-linux*}
2259 @uref{#sparc64-*-solaris2*,,sparc64-*-solaris2*}
2261 @uref{#sparcv9-*-solaris2*,,sparcv9-*-solaris2*}
2263 @uref{#*-*-sysv*,,*-*-sysv*}
2265 @uref{#vax-dec-ultrix,,vax-dec-ultrix}
2267 @uref{#*-*-vxworks*,,*-*-vxworks*}
2269 @uref{#x86_64-*-*,,x86_64-*-*, amd64-*-*}
2271 @uref{#xtensa-*-elf,,xtensa-*-elf}
2273 @uref{#xtensa-*-linux*,,xtensa-*-linux*}
2275 @uref{#windows,,Microsoft Windows}
2279 @uref{#older,,Older systems}
2284 @uref{#elf_targets,,all ELF targets} (SVR4, Solaris 2, etc.)
2290 <!-- -------- host/target specific issues start here ---------------- -->
2293 @heading @anchor{alpha*-*-*}alpha*-*-*
2295 This section contains general configuration information for all
2296 alpha-based platforms using ELF (in particular, ignore this section for
2297 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
2298 section, please read all other sections that match your target.
2300 We require binutils 2.11.2 or newer.
2301 Previous binutils releases had a number of problems with DWARF 2
2302 debugging information, not the least of which is incorrect linking of
2308 @heading @anchor{alpha*-dec-osf*}alpha*-dec-osf*
2309 Systems using processors that implement the DEC Alpha architecture and
2310 are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
2311 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
2313 As of GCC 3.2, versions before @code{alpha*-dec-osf4} are no longer
2314 supported. (These are the versions which identify themselves as DEC
2317 In Digital Unix V4.0, virtual memory exhausted bootstrap failures
2318 may be fixed by configuring with @option{--with-gc=simple},
2319 reconfiguring Kernel Virtual Memory and Swap parameters
2320 per the @command{/usr/sbin/sys_check} Tuning Suggestions,
2321 or applying the patch in
2322 @uref{http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html}.
2324 In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
2325 currently (2001-06-13) work with @command{mips-tfile}. As a workaround,
2326 we need to use the old assembler, invoked via the barely documented
2327 @option{-oldas} option. To bootstrap GCC, you either need to use the
2331 % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
2334 or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
2337 % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
2340 As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld}
2341 are supported on Tru64 UNIX, so you must not configure GCC with
2342 @option{--with-gnu-as} or @option{--with-gnu-ld}.
2344 GCC writes a @samp{.verstamp} directive to the assembler output file
2345 unless it is built as a cross-compiler. It gets the version to use from
2346 the system header file @file{/usr/include/stamp.h}. If you install a
2347 new version of DEC Unix, you should rebuild GCC to pick up the new version
2350 Note that since the Alpha is a 64-bit architecture, cross-compilers from
2351 32-bit machines will not generate code as efficient as that generated
2352 when the compiler is running on a 64-bit machine because many
2353 optimizations that depend on being able to represent a word on the
2354 target in an integral value on the host cannot be performed. Building
2355 cross-compilers on the Alpha for 32-bit machines has only been tested in
2356 a few cases and may not work properly.
2358 @samp{make compare} may fail on old versions of DEC Unix unless you add
2359 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
2360 assembler input file is stored in the object file, and that makes
2361 comparison fail if it differs between the @code{stage1} and
2362 @code{stage2} compilations. The option @option{-save-temps} forces a
2363 fixed name to be used for the assembler input file, instead of a
2364 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
2365 unless the comparisons fail without that option. If you add
2366 @option{-save-temps}, you will have to manually delete the @samp{.i} and
2367 @samp{.s} files after each series of compilations.
2369 GCC now supports both the native (ECOFF) debugging format used by DBX
2370 and GDB and an encapsulated STABS format for use only with GDB@. See the
2371 discussion of the @option{--with-stabs} option of @file{configure} above
2372 for more information on these formats and how to select them.
2374 There is a bug in DEC's assembler that produces incorrect line numbers
2375 for ECOFF format when the @samp{.align} directive is used. To work
2376 around this problem, GCC will not emit such alignment directives
2377 while writing ECOFF format debugging information even if optimization is
2378 being performed. Unfortunately, this has the very undesirable
2379 side-effect that code addresses when @option{-O} is specified are
2380 different depending on whether or not @option{-g} is also specified.
2382 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
2383 DBX@. DEC is now aware of this problem with the assembler and hopes to
2384 provide a fix shortly.
2389 @heading @anchor{alphaev5-cray-unicosmk*}alphaev5-cray-unicosmk*
2390 Cray T3E systems running Unicos/Mk.
2392 This port is incomplete and has many known bugs. We hope to improve the
2393 support for this target soon. Currently, only the C front end is supported,
2394 and it is not possible to build parallel applications. Cray modules are not
2395 supported; in particular, Craylibs are assumed to be in
2396 @file{/opt/ctl/craylibs/craylibs}.
2398 You absolutely @strong{must} use GNU make on this platform. Also, you
2399 need to tell GCC where to find the assembler and the linker. The
2400 simplest way to do so is by providing @option{--with-as} and
2401 @option{--with-ld} to @file{configure}, e.g.@:
2404 configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld \
2405 --enable-languages=c
2408 The comparison test during @samp{make bootstrap} fails on Unicos/Mk
2409 because the assembler inserts timestamps into object files. You should
2410 be able to work around this by doing @samp{make all} after getting this
2416 @heading @anchor{arc-*-elf}arc-*-elf
2417 Argonaut ARC processor.
2418 This configuration is intended for embedded systems.
2423 @heading @anchor{arm-*-elf}arm-*-elf
2424 @heading @anchor{xscale-*-*}xscale-*-*
2425 ARM-family processors. Subtargets that use the ELF object format
2426 require GNU binutils 2.13 or newer. Such subtargets include:
2427 @code{arm-*-freebsd}, @code{arm-*-netbsdelf}, @code{arm-*-*linux},
2428 @code{arm-*-rtems} and @code{arm-*-kaos}.
2433 @heading @anchor{arm-*-coff}arm-*-coff
2434 ARM-family processors. Note that there are two different varieties
2435 of PE format subtarget supported: @code{arm-wince-pe} and
2436 @code{arm-pe} as well as a standard COFF target @code{arm-*-coff}.
2441 @heading @anchor{arm-*-aout}arm-*-aout
2442 ARM-family processors. These targets support the AOUT file format:
2443 @code{arm-*-aout}, @code{arm-*-netbsd}.
2448 @heading @anchor{avr}avr
2450 ATMEL AVR-family micro controllers. These are used in embedded
2451 applications. There are no standard Unix configurations.
2453 @xref{AVR Options,, AVR Options, gcc, Using and Porting the GNU Compiler
2457 See ``AVR Options'' in the main manual
2459 for the list of supported MCU types.
2461 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
2463 Further installation notes and other useful information about AVR tools
2464 can also be obtained from:
2468 @uref{http://www.openavr.org,,http://www.openavr.org}
2470 @uref{http://home.overta.ru/users/denisc/,,http://home.overta.ru/users/denisc/}
2472 @uref{http://www.amelek.gda.pl/avr/,,http://www.amelek.gda.pl/avr/}
2475 We @emph{strongly} recommend using binutils 2.13 or newer.
2477 The following error:
2479 Error: register required
2482 indicates that you should upgrade to a newer version of the binutils.
2487 @heading @anchor{c4x}c4x
2489 Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal
2490 Processors. These are used in embedded applications. There are no
2491 standard Unix configurations.
2493 @xref{TMS320C3x/C4x Options,, TMS320C3x/C4x Options, gcc, Using and
2494 Porting the GNU Compiler Collection (GCC)},
2497 See ``TMS320C3x/C4x Options'' in the main manual
2499 for the list of supported MCU types.
2501 GCC can be configured as a cross compiler for both the C3x and C4x
2502 architectures on the same system. Use @samp{configure --target=c4x
2503 --enable-languages="c,c++"} to configure.
2506 Further installation notes and other useful information about C4x tools
2507 can also be obtained from:
2511 @uref{http://www.elec.canterbury.ac.nz/c4x/,,http://www.elec.canterbury.ac.nz/c4x/}
2517 @heading @anchor{cris}CRIS
2519 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
2520 series. These are used in embedded applications.
2523 @xref{CRIS Options,, CRIS Options, gcc, Using and Porting the GNU Compiler
2527 See ``CRIS Options'' in the main manual
2529 for a list of CRIS-specific options.
2531 There are a few different CRIS targets:
2533 @item cris-axis-aout
2534 Old target. Includes a multilib for the @samp{elinux} a.out-based
2535 target. No multilibs for newer architecture variants.
2537 Mainly for monolithic embedded systems. Includes a multilib for the
2538 @samp{v10} core used in @samp{ETRAX 100 LX}.
2539 @item cris-axis-linux-gnu
2540 A GNU/Linux port for the CRIS architecture, currently targeting
2541 @samp{ETRAX 100 LX} by default.
2544 For @code{cris-axis-aout} and @code{cris-axis-elf} you need binutils 2.11
2545 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
2547 Pre-packaged tools can be obtained from
2548 @uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More
2549 information about this platform is available at
2550 @uref{http://developer.axis.com/}.
2555 @heading @anchor{dos}DOS
2557 Please have a look at the @uref{binaries.html,,binaries page}.
2559 You cannot install GCC by itself on MSDOS; it will not compile under
2560 any MSDOS compiler except itself. You need to get the complete
2561 compilation package DJGPP, which includes binaries as well as sources,
2562 and includes all the necessary compilation tools and libraries.
2567 @heading @anchor{*-*-freebsd*}*-*-freebsd*
2569 The version of binutils installed in @file{/usr/bin} probably works with
2570 this release of GCC@. However, on FreeBSD 4, bootstrapping against the
2571 latest FSF binutils is known to improve overall testsuite results; and,
2572 on FreeBSD/alpha, using binutils 2.14 or later is required to build libjava.
2574 Support for FreeBSD 1 was discontinued in GCC 3.2.
2576 Support for FreeBSD 2 will be discontinued after GCC 3.4. The
2577 following was true for GCC 3.1 but the current status is unknown.
2578 For FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
2579 configuration support and files as shipped with GCC 2.95 are still in
2580 place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
2581 it is unknown which version of binutils was used (it is assumed that it
2582 was the system copy in @file{/usr/bin}) and C++ EH failures were noted.
2584 For FreeBSD using the ELF file format: DWARF 2 debugging is now the
2585 default for all CPU architectures. It had been the default on
2586 FreeBSD/alpha since its inception. You may use @option{-gstabs} instead
2587 of @option{-g}, if you really want the old debugging format. There are
2588 no known issues with mixing object files and libraries with different
2589 debugging formats. Otherwise, this release of GCC should now match more
2590 of the configuration used in the stock FreeBSD configuration of GCC@. In
2591 particular, @option{--enable-threads} is now configured by default.
2592 However, as a general user, do not attempt to replace the system
2593 compiler with this release. Known to bootstrap and check with good
2594 results on FreeBSD 4.9-STABLE and 5-CURRENT@. In the past, known to
2595 bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2,
2596 4.3, 4.4, 4.5, 4.8-STABLE@.
2598 In principle, @option{--enable-threads} is now compatible with
2599 @option{--enable-libgcj} on FreeBSD@. However, it has only been built
2600 and tested on @samp{i386-*-freebsd[45]} and @samp{alpha-*-freebsd[45]}.
2602 library may be incorrectly built (symbols are missing at link time).
2603 There is a rare timing-based startup hang (probably involves an
2604 assumption about the thread library). Multi-threaded boehm-gc (required for
2605 libjava) exposes severe threaded signal-handling bugs on FreeBSD before
2606 4.5-RELEASE@. Other CPU architectures
2607 supported by FreeBSD will require additional configuration tuning in, at
2608 the very least, both boehm-gc and libffi.
2610 Shared @file{libgcc_s.so} is now built and installed by default.
2615 @heading @anchor{h8300-hms}h8300-hms
2616 Renesas H8/300 series of processors.
2618 Please have a look at the @uref{binaries.html,,binaries page}.
2620 The calling convention and structure layout has changed in release 2.6.
2621 All code must be recompiled. The calling convention now passes the
2622 first three arguments in function calls in registers. Structures are no
2623 longer a multiple of 2 bytes.
2628 @heading @anchor{hppa*-hp-hpux*}hppa*-hp-hpux*
2629 Support for HP-UX version 9 and older was discontinued in GCC 3.4.
2631 We @emph{highly} recommend using gas/binutils on all hppa platforms;
2632 you may encounter a variety of problems when using the HP assembler.
2634 Specifically, @option{-g} does not work on HP-UX (since that system
2635 uses a peculiar debugging format which GCC does not know about), unless
2636 you use GAS and GDB@. It may be helpful to configure GCC with the
2637 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
2638 @option{--with-as=@dots{}} options to ensure that GCC can find GAS@.
2640 If you wish to use the pa-risc 2.0 architecture support with a 32-bit
2641 runtime, you must use either the HP assembler, or gas/binutils 2.11
2644 There are two default scheduling models for instructions. These are
2645 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
2646 architecture specified for the target machine when configuring.
2647 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
2648 the target is a @samp{hppa1*} machine.
2650 The PROCESSOR_8000 model is not well suited to older processors. Thus,
2651 it is important to completely specify the machine architecture when
2652 configuring if you want a model other than PROCESSOR_8000. The macro
2653 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
2654 default scheduling model is desired.
2656 As of GCC 3.5, GCC uses the UNIX 95 namespace for HP-UX 10.10
2657 through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
2658 This namespace change might cause problems when bootstrapping with
2659 an earlier version of GCC or the HP compiler as essentially the same
2660 namespace is required for an entire build. This problem can be avoided
2661 in a number of ways. With HP cc, @env{UNIX_STD} can be set to @samp{95}
2662 or @samp{98}. Another way is to add an appropriate set of predefines
2663 to @env{CC}. The description for the @option{munix=} option contains
2664 a list of the predefines used with each standard.
2666 More specific information to @samp{hppa*-hp-hpux*} targets follows.
2671 @heading @anchor{hppa*-hp-hpux10}hppa*-hp-hpux10
2673 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
2674 @code{PHCO_19798} from HP@. HP has two sites which provide patches free of
2680 <a href="http://us.itrc.hp.com/service/home/home.do">US, Canada, Asia-Pacific, and
2684 @uref{http://us.itrc.hp.com/service/home/home.do,,} US, Canada, Asia-Pacific,
2688 @uref{http://europe.itrc.hp.com/service/home/home.do,,} Europe.
2691 The HP assembler on these systems has some problems. Most notably the
2692 assembler inserts timestamps into each object file it creates, causing
2693 the 3-stage comparison test to fail during a @samp{make bootstrap}.
2694 You should be able to continue by saying @samp{make all} after getting
2695 the failure from @samp{make bootstrap}.
2697 GCC 3.5 requires CVS binutils as of April 28, 2004 or later. Earlier
2698 versions require binutils 2.8 or later.
2700 The C++ ABI has changed incompatibly in GCC 3.5. COMDAT subspaces are
2701 used for one-only code and data. This resolves many of the previous
2702 problems in using C++ on this target. However, the ABI is not compatible
2703 with the one implemented under HP-UX 11 using secondary definitions.
2708 @heading @anchor{hppa*-hp-hpux11}hppa*-hp-hpux11
2710 GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
2711 be used to compile GCC 3.0 and up.
2713 Refer to @uref{binaries.html,,binaries} for information about obtaining
2714 precompiled GCC binaries for HP-UX@. Precompiled binaries must be obtained
2715 to build the Ada language as it can't be bootstrapped using C@. Ada is
2716 only available for the 32-bit PA-RISC runtime. The libffi and libjava
2717 haven't been ported to HP-UX and don't build.
2719 It is possible to build GCC 3.3 starting with the bundled HP compiler,
2720 but the process requires several steps. GCC 3.3 can then be used to
2721 build later versions. The fastjar program contains ISO C code and
2722 can't be built with the HP bundled compiler. This problem can be
2723 avoided by not building the Java language. For example, use the
2724 @option{--enable-languages="c,c++,f77,objc"} option in your configure
2727 Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The
2728 bundled compiler supports only traditional C; you will need either HP's
2729 unbundled compiler, or a binary distribution of GCC@.
2731 There are several possible approaches to building the distribution.
2732 Binutils can be built first using the HP tools. Then, the GCC
2733 distribution can be built. The second approach is to build GCC
2734 first using the HP tools, then build binutils, then rebuild GCC@.
2735 There have been problems with various binary distributions, so it
2736 is best not to start from a binary distribution.
2738 On 64-bit capable systems, there are two distinct targets. Different
2739 installation prefixes must be used if both are to be installed on
2740 the same system. The @samp{hppa[1-2]*-hp-hpux11*} target generates code
2741 for the 32-bit PA-RISC runtime architecture and uses the HP linker.
2742 The @samp{hppa64-hp-hpux11*} target generates 64-bit code for the
2743 PA-RISC 2.0 architecture. The HP and GNU linkers are both supported
2746 The script config.guess now selects the target type based on the compiler
2747 detected during configuration. You must define @env{PATH} or @env{CC} so
2748 that configure finds an appropriate compiler for the initial bootstrap.
2749 When @env{CC} is used, the definition should contain the options that are
2750 needed whenever @env{CC} is used.
2752 Specifically, options that determine the runtime architecture must be
2753 in @env{CC} to correctly select the target for the build. It is also
2754 convenient to place many other compiler options in @env{CC}. For example,
2755 @env{CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"}
2756 can be used to bootstrap the GCC 3.3 branch with the HP compiler in
2757 64-bit K&R/bundled mode. The @option{+DA2.0W} option will result in
2758 the automatic selection of the @samp{hppa64-hp-hpux11*} target. The
2759 macro definition table of cpp needs to be increased for a successful
2760 build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to
2761 be defined when building with the bundled compiler, or when using the
2762 @option{-Ac} option. These defines aren't necessary with @option{-Ae}.
2764 It is best to explicitly configure the @samp{hppa64-hp-hpux11*} target
2765 with the @option{--with-ld=@dots{}} option. This overrides the standard
2766 search for ld. The two linkers supported on this target require different
2767 commands. The default linker is determined during configuration. As a
2768 result, it's not possible to switch linkers in the middle of a GCC build.
2769 This has been been reported to sometimes occur in unified builds of
2772 GCC 3.0 through 3.2 require binutils 2.11 or above. GCC 3.3 through
2773 GCC 3.5 require binutils 2.14 or later.
2775 Although the HP assembler can be used for an initial build, it shouldn't
2776 be used with any languages other than C and perhaps Fortran due to its
2777 many limitations. For example, it does not support weak symbols or alias
2778 definitions. As a result, explicit template instantiations are required
2779 when using C++. This makes it difficult if not impossible to build many
2780 C++ applications. You can't generate debugging information when using
2781 the HP assembler. Finally, @samp{make bootstrap} fails in the final
2782 comparison of object modules due to the time stamps that it inserts into
2783 the modules. The bootstrap can be continued from this point with
2786 A recent linker patch must be installed for the correct operation of
2787 GCC 3.3 and later. @code{PHSS_26559} and @code{PHSS_24304} are the
2788 oldest linker patches that are known to work. They are for HP-UX
2789 11.00 and 11.11, respectively. @code{PHSS_24303}, the companion to
2790 @code{PHSS_24304}, might be usable but it hasn't been tested. These
2791 patches have been superseded. Consult the HP patch database to obtain
2792 the currently recommended linker patch for your system.
2794 The patches are necessary for the support of weak symbols on the
2795 32-bit port, and for the running of initializers and finalizers. Weak
2796 symbols are implemented using SOM secondary definition symbols. Prior
2797 to HP-UX 11, there are bugs in the linker support for secondary symbols.
2798 The patches correct a problem of linker core dumps creating shared
2799 libraries containing secondary symbols, as well as various other
2800 linking issues involving secondary symbols.
2802 GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
2803 run initializers and finalizers on the 64-bit port. The 32-bit port
2804 uses the linker @option{+init} and @option{+fini} options for the same
2805 purpose. The patches correct various problems with the +init/+fini
2806 options, including program core dumps. Binutils 2.14 corrects a
2807 problem on the 64-bit port resulting from HP's non-standard use of
2808 the .init and .fini sections for array initializers and finalizers.
2810 There are a number of issues to consider in selecting which linker to
2811 use with the 64-bit port. The GNU 64-bit linker can only create dynamic
2812 binaries. The @option{-static} option causes linking with archive
2813 libraries but doesn't produce a truly static binary. Dynamic binaries
2814 still require final binding by the dynamic loader to resolve a set of
2815 dynamic-loader-defined symbols. The default behavior of the HP linker
2816 is the same as the GNU linker. However, it can generate true 64-bit
2817 static binaries using the @option{+compat} option.
2819 The HP 64-bit linker doesn't support linkonce semantics. As a
2820 result, C++ programs have many more sections than they should.
2822 The GNU 64-bit linker has some issues with shared library support
2823 and exceptions. As a result, we only support libgcc in archive
2824 format. For similar reasons, dwarf2 unwind and exception support
2825 are disabled. The GNU linker also has problems creating binaries
2826 with @option{-static}. It doesn't provide stubs for internal
2827 calls to global functions in shared libraries, so these calls
2828 can't be overloaded.
2830 Thread support is not implemented in GCC 3.0 through 3.2, so the
2831 @option{--enable-threads} configure option does not work. In 3.3
2832 and later, POSIX threads are supported. The optional DCE thread
2833 library is not supported.
2835 This port still is undergoing significant development.
2840 @heading @anchor{*-*-linux-gnu}*-*-linux-gnu
2842 Versions of libstdc++-v3 starting with 3.2.1 require bugfixes present
2843 in glibc 2.2.5 and later. More information is available in the
2844 libstdc++-v3 documentation.
2849 @heading @anchor{ix86-*-linux*aout}i?86-*-linux*aout
2850 Use this configuration to generate @file{a.out} binaries on Linux-based
2851 GNU systems. This configuration is being superseded.
2856 @heading @anchor{ix86-*-linux*}i?86-*-linux*
2858 As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
2859 See @uref{http://gcc.gnu.org/PR10877,,bug 10877} for more information.
2861 If you receive Signal 11 errors when building on GNU/Linux, then it is
2862 possible you have a hardware problem. Further information on this can be
2863 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
2868 @heading @anchor{ix86-*-sco3.2v5*}i?86-*-sco3.2v5*
2869 Use this for the SCO OpenServer Release 5 family of operating systems.
2871 Unlike earlier versions of GCC, the ability to generate COFF with this
2872 target is no longer provided.
2874 Earlier versions of GCC emitted DWARF 1 when generating ELF to allow
2875 the system debugger to be used. That support was too burdensome to
2876 maintain. GCC now emits only DWARF 2 for this target. This means you
2877 may use either the UDK debugger or GDB to debug programs built by this
2880 GCC is now only supported on releases 5.0.4 and later, and requires that
2881 you install Support Level Supplement OSS646B or later, and Support Level
2882 Supplement OSS631C or later. If you are using release 5.0.7 of
2883 OpenServer, you must have at least the first maintenance pack installed
2884 (this includes the relevant portions of OSS646). OSS646, also known as
2885 the ``Execution Environment Update'', provides updated link editors and
2886 assemblers, as well as updated standard C and math libraries. The C
2887 startup modules are also updated to support the System V gABI draft, and
2888 GCC relies on that behavior. OSS631 provides a collection of commonly
2889 used open source libraries, some of which GCC depends on (such as GNU
2890 gettext and zlib). SCO OpenServer Release 5.0.7 has all of this built
2891 in by default, but OSS631C and later also apply to that release. Please
2893 @uref{ftp://ftp.sco.com/pub/openserver5,,ftp://ftp.sco.com/pub/openserver5}
2894 for the latest versions of these (and other potentially useful)
2897 Although there is support for using the native assembler, it is
2898 recommended that you configure GCC to use the GNU assembler. You do
2899 this by using the flags
2900 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You should
2901 use a modern version of GNU binutils. Version 2.13.2.1 was used for all
2902 testing. In general, only the @option{--with-gnu-as} option is tested.
2903 A modern bintuils (as well as a plethora of other development related
2904 GNU utilities) can be found in Support Level Supplement OSS658A, the
2905 ``GNU Development Tools'' package. See the SCO web and ftp sites for details.
2906 That package also contains the currently ``officially supported'' version of
2907 GCC, version 2.95.3. It is useful for bootstrapping this version.
2912 @heading @anchor{ix86-*-udk}i?86-*-udk
2914 This target emulates the SCO Universal Development Kit and requires that
2915 package be installed. (If it is installed, you will have a
2916 @file{/udk/usr/ccs/bin/cc} file present.) It's very much like the
2917 @samp{i?86-*-unixware7*} target
2918 but is meant to be used when hosting on a system where UDK isn't the
2919 default compiler such as OpenServer 5 or Unixware 2. This target will
2920 generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
2921 with the same warnings and caveats as the SCO UDK@.
2923 This target is a little tricky to build because we have to distinguish
2924 it from the native tools (so it gets headers, startups, and libraries
2925 from the right place) while making the tools not think we're actually
2926 building a cross compiler. The easiest way to do this is with a configure
2930 CC=/udk/usr/ccs/bin/cc @var{/your/path/to}/gcc/configure \
2931 --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-
2934 @emph{You should substitute @samp{i686} in the above command with the appropriate
2935 processor for your host.}
2937 After the usual @samp{make bootstrap} and
2938 @samp{make install}, you can then access the UDK-targeted GCC
2939 tools by adding @command{udk-} before the commonly known name. For
2940 example, to invoke the C compiler, you would use @command{udk-gcc}.
2941 They will coexist peacefully with any native-target GCC tools you may
2948 @heading @anchor{ia64-*-linux}ia64-*-linux
2949 IA-64 processor (also known as IPF, or Itanium Processor Family)
2952 If you are using the installed system libunwind library with
2953 @option{--with-system-libunwind}, then you must use libunwind 0.98 or
2956 None of the following versions of GCC has an ABI that is compatible
2957 with any of the other versions in this list, with the exception that
2958 Red Hat 2.96 and Trillian 000171 are compatible with each other:
2959 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
2960 This primarily affects C++ programs and programs that create shared libraries.
2961 GCC 3.1 or later is recommended for compiling linux, the kernel.
2962 As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
2963 more major ABI changes are expected.
2968 @heading @anchor{ia64-*-hpux*}ia64-*-hpux*
2969 Building GCC on this target requires the GNU Assembler. The bundled HP
2970 assembler will not work. To prevent GCC from using the wrong assembler,
2971 the option @option{--with-gnu-as} may be necessary.
2973 The GCC libunwind library has not been ported to HPUX@. This means that for
2974 GCC versions 3.2.3 and earlier, @option{--enable-libunwind-exceptions}
2975 is required to build GCC@. For GCC 3.3 and later, this is the default.
2976 For gcc 3.4.3 and later, @option{--enable-libunwind-exceptions} is
2977 removed and the system libunwind library will always be used.
2981 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
2983 @heading @anchor{*-ibm-aix*}*-ibm-aix*
2984 Support for AIX version 3 and older was discontinued in GCC 3.4.
2986 AIX Make frequently has problems with GCC makefiles. GNU Make 3.79.1 or
2987 newer is recommended to build on this platform.
2989 To speed up the configuration phases of bootstrapping and installing GCC,
2990 one may use GNU Bash instead of AIX @command{/bin/sh}, e.g.,
2993 % CONFIG_SHELL=/opt/freeware/bin/bash
2994 % export CONFIG_SHELL
2997 and then proceed as described in @uref{build.html,,the build instructions},
2998 where we strongly recommend using GNU make and specifying an absolute path
2999 to invoke @var{srcdir}/configure.
3001 Errors involving @code{alloca} when building GCC generally are due
3002 to an incorrect definition of @code{CC} in the Makefile or mixing files
3003 compiled with the native C compiler and GCC@. During the stage1 phase of
3004 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
3005 (not @command{xlc}). Once @command{configure} has been informed of
3006 @command{xlc}, one needs to use @samp{make distclean} to remove the
3007 configure cache files and ensure that @env{CC} environment variable
3008 does not provide a definition that will confuse @command{configure}.
3009 If this error occurs during stage2 or later, then the problem most likely
3010 is the version of Make (see above).
3012 The native @command{as} and @command{ld} are recommended for bootstrapping
3013 on AIX 4 and required for bootstrapping on AIX 5L@. The GNU Assembler
3014 reports that it supports WEAK symbols on AIX 4, which causes GCC to try to
3015 utilize weak symbol functionality although it is not supported. The GNU
3016 Assembler and Linker do not support AIX 5L sufficiently to bootstrap GCC@.
3017 The native AIX tools do interoperate with GCC@.
3019 Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
3020 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
3021 fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
3022 referenced as APAR IY53606 (AIX 5.2) or a APAR IY54774 (AIX 5.1)
3024 @samp{libstdc++} in GCC 3.4 increments the major version number of the
3025 shared object and GCC installation places the @file{libstdc++.a}
3026 shared library in a common location which will overwrite the and GCC
3027 3.3 version of the shared library. Applications either need to be
3028 re-linked against the new shared library or the GCC 3.1 and GCC 3.3
3029 versions of the @samp{libstdc++} shared object needs to be available
3030 to the AIX runtime loader. The GCC 3.1 @samp{libstdc++.so.4}, if
3031 present, and GCC 3.3 @samp{libstdc++.so.5} shared objects can be
3032 installed for runtime dynamic loading using the following steps to set
3033 the @samp{F_LOADONLY} flag in the shared object for @emph{each}
3034 multilib @file{libstdc++.a} installed:
3036 Extract the shared objects from the currently installed
3037 @file{libstdc++.a} archive:
3039 % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
3042 Enable the @samp{F_LOADONLY} flag so that the shared object will be
3043 available for runtime dynamic loading, but not linking:
3045 % strip -e libstdc++.so.4 libstdc++.so.5
3048 Archive the runtime-only shared object in the GCC 3.4
3049 @file{libstdc++.a} archive:
3051 % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
3054 Linking executables and shared libraries may produce warnings of
3055 duplicate symbols. The assembly files generated by GCC for AIX always
3056 have included multiple symbol definitions for certain global variable
3057 and function declarations in the original program. The warnings should
3058 not prevent the linker from producing a correct library or runnable
3061 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
3062 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
3063 to parse archive libraries did not handle the new format correctly.
3064 These routines are used by GCC and result in error messages during
3065 linking such as ``not a COFF file''. The version of the routines shipped
3066 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
3067 option of the archive command may be used to create archives of 32-bit
3068 objects using the original ``small format''. A correct version of the
3069 routines is shipped with AIX 4.3.2 and above.
3071 Some versions of the AIX binder (linker) can fail with a relocation
3072 overflow severe error when the @option{-bbigtoc} option is used to link
3073 GCC-produced object files into an executable that overflows the TOC@. A fix
3074 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
3075 available from IBM Customer Support and from its
3076 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3077 website as PTF U455193.
3079 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
3080 with a segmentation fault when invoked by any version of GCC@. A fix for
3081 APAR IX87327 is available from IBM Customer Support and from its
3082 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3083 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
3085 The initial assembler shipped with AIX 4.3.0 generates incorrect object
3086 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
3087 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
3088 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3089 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
3091 AIX provides National Language Support (NLS)@. Compilers and assemblers
3092 use NLS to support locale-specific representations of various data
3093 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
3094 separating decimal fractions). There have been problems reported where
3095 GCC does not produce the same floating-point formats that the assembler
3096 expects. If one encounters this problem, set the @env{LANG}
3097 environment variable to @samp{C} or @samp{En_US}.
3099 By default, GCC for AIX 4.1 and above produces code that can be used on
3100 both Power or PowerPC processors.
3102 A default can be specified with the @option{-mcpu=@var{cpu_type}}
3103 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
3108 @heading @anchor{ip2k-*-elf}ip2k-*-elf
3109 Ubicom IP2022 micro controller.
3110 This configuration is intended for embedded systems.
3111 There are no standard Unix configurations.
3113 Use @samp{configure --target=ip2k-elf --enable-languages=c} to configure GCC@.
3118 @heading @anchor{iq2000-*-elf}iq2000-*-elf
3119 Vitesse IQ2000 processors. These are used in embedded
3120 applications. There are no standard Unix configurations.
3125 @heading @anchor{m32r-*-elf}m32r-*-elf
3126 Renesas M32R processor.
3127 This configuration is intended for embedded systems.
3132 @heading @anchor{m6811-elf}m6811-elf
3133 Motorola 68HC11 family micro controllers. These are used in embedded
3134 applications. There are no standard Unix configurations.
3139 @heading @anchor{m6812-elf}m6812-elf
3140 Motorola 68HC12 family micro controllers. These are used in embedded
3141 applications. There are no standard Unix configurations.
3146 @heading @anchor{m68k-hp-hpux}m68k-hp-hpux
3147 HP 9000 series 300 or 400 running HP-UX@. HP-UX version 8.0 has a bug in
3148 the assembler that prevents compilation of GCC@. This
3149 bug manifests itself during the first stage of compilation, while
3150 building @file{libgcc2.a}:
3154 cc1: warning: `-g' option not supported on this version of GCC
3155 cc1: warning: `-g1' option not supported on this version of GCC
3156 ./xgcc: Internal compiler error: program as got fatal signal 11
3159 A patched version of the assembler is available as the file
3160 @uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you
3161 have HP software support, the patch can also be obtained directly from
3162 HP, as described in the following note:
3165 This is the patched assembler, to patch SR#1653-010439, where the
3166 assembler aborts on floating point constants.
3168 The bug is not really in the assembler, but in the shared library
3169 version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is
3170 SR#4701-078451. Anyway, the attached assembler uses the archive
3171 library version of ``cvtnum(3c)'' and thus does not exhibit the bug.
3174 This patch is also known as PHCO_4484.
3176 In addition gdb does not understand that native HP-UX format, so
3177 you must use gas if you wish to use gdb.
3179 On HP-UX version 8.05, but not on 8.07 or more recent versions, the
3180 @command{fixproto} shell script triggers a bug in the system shell. If you
3181 encounter this problem, upgrade your operating system or use BASH (the
3182 GNU shell) to run @command{fixproto}. This bug will cause the fixproto
3183 program to report an error of the form:
3186 ./fixproto: sh internal 1K buffer overflow
3189 To fix this, you can also change the first line of the fixproto script
3199 @heading @anchor{mips-*-*}mips-*-*
3200 If on a MIPS system you get an error message saying ``does not have gp
3201 sections for all it's [sic] sectons [sic]'', don't worry about it. This
3202 happens whenever you use GAS with the MIPS linker, but there is not
3203 really anything wrong, and it is okay to use the output file. You can
3204 stop such warnings by installing the GNU linker.
3206 It would be nice to extend GAS to produce the gp tables, but they are
3207 optional, and there should not be a warning about their absence.
3209 The libstdc++ atomic locking routines for MIPS targets requires MIPS II
3210 and later. A patch went in just after the GCC 3.3 release to
3211 make @samp{mips*-*-*} use the generic implementation instead. You can also
3212 configure for @samp{mipsel-elf} as a workaround. The
3213 @samp{mips*-*-linux*} target continues to use the MIPS II routines. More
3214 work on this is expected in future releases.
3216 MIPS systems check for division by zero (unless
3217 @option{-mno-check-zero-division} is passed to the compiler) by
3218 generating either a conditional trap or a break instruction. Using
3219 trap results in smaller code, but is only supported on MIPS II and
3220 later. Also, some versions of the Linux kernel have a bug that
3221 prevents trap from generating the proper signal (@code{SIGFPE}). To enable
3222 the use of break, use the @option{--with-divide=breaks}
3223 @command{configure} option when configuring GCC@. The default is to
3224 use traps on systems that support them.
3226 Cross-compilers for the Mips as target using the Mips assembler
3227 currently do not work, because the auxiliary programs
3228 @file{mips-tdump.c} and @file{mips-tfile.c} can't be compiled on
3229 anything but a Mips. It does work to cross compile for a Mips
3230 if you use the GNU assembler and linker.
3235 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
3237 In order to compile GCC on an SGI running IRIX 5, the @samp{compiler_dev.hdr}
3238 subsystem must be installed from the IDO CD-ROM supplied by SGI@.
3239 It is also available for download from
3240 @uref{ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist}.
3242 If you use the MIPS C compiler to bootstrap, it may be necessary
3243 to increase its table size for switch statements with the
3244 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
3245 optimization option, you also need to use @option{-Olimit 3000}.
3247 To enable debugging under IRIX 5, you must use GNU binutils 2.15 or
3248 later, and use the @option{--with-gnu-ld} @command{configure} option
3249 when configuring GCC@. You need to use GNU @command{ar} and @command{nm},
3250 also distributed with GNU binutils.
3252 Some users have reported that @command{/bin/sh} will hang during bootstrap.
3253 This problem can be avoided by running the commands:
3256 % CONFIG_SHELL=/bin/ksh
3257 % export CONFIG_SHELL
3260 before starting the build.
3265 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
3267 If you are using SGI's MIPSpro @command{cc} as your bootstrap compiler, you must
3268 ensure that the N32 ABI is in use. To test this, compile a simple C
3269 file with @command{cc} and then run @command{file} on the
3270 resulting object file. The output should look like:
3273 test.o: ELF N32 MSB @dots{}
3279 test.o: ELF 32-bit MSB @dots{}
3285 test.o: ELF 64-bit MSB @dots{}
3288 then your version of @command{cc} uses the O32 or N64 ABI by default. You
3289 should set the environment variable @env{CC} to @samp{cc -n32}
3290 before configuring GCC@.
3292 If you want the resulting @command{gcc} to run on old 32-bit systems
3293 with the MIPS R4400 CPU, you need to ensure that only code for the @samp{mips3}
3294 instruction set architecture (ISA) is generated. While GCC 3.x does
3295 this correctly, both GCC 2.95 and SGI's MIPSpro @command{cc} may change
3296 the ISA depending on the machine where GCC is built. Using one of them
3297 as the bootstrap compiler may result in @samp{mips4} code, which won't run at
3298 all on @samp{mips3}-only systems. For the test program above, you should see:
3301 test.o: ELF N32 MSB mips-3 @dots{}
3307 test.o: ELF N32 MSB mips-4 @dots{}
3310 instead, you should set the environment variable @env{CC} to @samp{cc
3311 -n32 -mips3} or @samp{gcc -mips3} respectively before configuring GCC@.
3313 MIPSpro C 7.4 may cause bootstrap failures, due to a bug when inlining
3314 @code{memcmp}. Either add @code{-U__INLINE_INTRINSICS} to the @env{CC}
3315 environment variable as a workaround or upgrade to MIPSpro C 7.4.1m.
3317 GCC on IRIX 6 is usually built to support the N32, O32 and N64 ABIs. If
3318 you build GCC on a system that doesn't have the N64 libraries installed
3319 or cannot run 64-bit binaries,
3320 you need to configure with @option{--disable-multilib} so GCC doesn't
3321 try to use them. This will disable building the O32 libraries, too.
3322 Look for @file{/usr/lib64/libc.so.1} to see if you
3323 have the 64-bit libraries installed.
3325 To enable debugging for the O32 ABI, you must use GNU @command{as} from
3326 GNU binutils 2.15 or later. You may also use GNU @command{ld}, but
3327 this is not required and currently causes some problems with Ada.
3329 The @option{--enable-threads} option doesn't currently work, a patch is
3330 in preparation for a future release. The @option{--enable-libgcj}
3331 option is disabled by default: IRIX 6 uses a very low default limit
3332 (20480) for the command line length. Although @command{libtool} contains a
3333 workaround for this problem, at least the N64 @samp{libgcj} is known not
3334 to build despite this, running into an internal error of the native
3335 @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
3336 its maximum of 262144 bytes. If you have root access, you can use the
3337 @command{systune} command to do this.
3339 See @uref{http://freeware.sgi.com/} for more
3340 information about using GCC on IRIX platforms.
3345 @heading @anchor{powerpc*-*-*}powerpc-*-*
3347 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
3348 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
3353 @heading @anchor{powerpc-*-darwin*}powerpc-*-darwin*
3354 PowerPC running Darwin (Mac OS X kernel).
3356 Pre-installed versions of Mac OS X may not include any developer tools,
3357 meaning that you will not be able to build GCC from source. Tool
3358 binaries are available at
3359 @uref{http://developer.apple.com/tools/compilers.html} (free
3360 registration required).
3362 This version of GCC requires at least cctools-528.
3364 The version of GCC shipped by Apple typically includes a number of
3365 extensions not available in a standard GCC release. These extensions
3366 are generally for backwards compatibility and best avoided.
3371 @heading @anchor{powerpc-*-elf}powerpc-*-elf, powerpc-*-sysv4
3372 PowerPC system in big endian mode, running System V.4.
3377 @heading @anchor{powerpc-*-linux-gnu*}powerpc-*-linux-gnu*
3380 @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.13.90.0.10}
3381 or newer for a working GCC@.
3386 @heading @anchor{powerpc-*-netbsd*}powerpc-*-netbsd*
3387 PowerPC system in big endian mode running NetBSD@. To build the
3388 documentation you will need Texinfo version 4.2 (NetBSD 1.5.1 included
3389 Texinfo version 3.12).
3394 @heading @anchor{powerpc-*-eabisim}powerpc-*-eabisim
3395 Embedded PowerPC system in big endian mode for use in running under the
3401 @heading @anchor{powerpc-*-eabi}powerpc-*-eabi
3402 Embedded PowerPC system in big endian mode.
3407 @heading @anchor{powerpcle-*-elf}powerpcle-*-elf, powerpcle-*-sysv4
3408 PowerPC system in little endian mode, running System V.4.
3413 @heading @anchor{powerpcle-*-eabisim}powerpcle-*-eabisim
3414 Embedded PowerPC system in little endian mode for use in running under
3420 @heading @anchor{powerpcle-*-eabi}powerpcle-*-eabi
3421 Embedded PowerPC system in little endian mode.
3426 @heading @anchor{s390-*-linux*}s390-*-linux*
3427 S/390 system running GNU/Linux for S/390@.
3432 @heading @anchor{s390x-*-linux*}s390x-*-linux*
3433 zSeries system (64-bit) running GNU/Linux for zSeries@.
3438 @heading @anchor{s390x-ibm-tpf*}s390x-ibm-tpf*
3439 zSeries system (64-bit) running TPF@. This platform is
3440 supported as cross-compilation target only.
3445 @c Please use Solaris 2 to refer to all release of Solaris, starting
3446 @c with 2.0 until 2.6, 7, 8, etc. Solaris 1 was a marketing name for
3447 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
3448 @c alone is too unspecific and must be avoided.
3449 @heading @anchor{*-*-solaris2*}*-*-solaris2*
3451 Sun does not ship a C compiler with Solaris 2. To bootstrap and install
3452 GCC you first have to install a pre-built compiler, see the
3453 @uref{binaries.html,,binaries page} for details.
3455 The Solaris 2 @command{/bin/sh} will often fail to configure
3456 @file{libstdc++-v3}, @file{boehm-gc} or @file{libjava}. We therefore
3457 recommend to use the following sequence of commands to bootstrap and
3461 % CONFIG_SHELL=/bin/ksh
3462 % export CONFIG_SHELL
3465 and then proceed as described in @uref{build.html,,the build instructions}.
3466 In addition we strongly recommend specifying an absolute path to invoke
3467 @var{srcdir}/configure.
3469 Solaris 2 comes with a number of optional OS packages. Some of these
3470 are needed to use GCC fully, namely @code{SUNWarc},
3471 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
3472 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
3473 optional packages when installing Solaris 2, you will need to verify that
3474 the packages that GCC needs are installed.
3476 To check whether an optional package is installed, use
3477 the @command{pkginfo} command. To add an optional package, use the
3478 @command{pkgadd} command. For further details, see the Solaris 2
3481 Trying to use the linker and other tools in
3482 @file{/usr/ucb} to install GCC has been observed to cause trouble.
3483 For example, the linker may hang indefinitely. The fix is to remove
3484 @file{/usr/ucb} from your @env{PATH}.
3486 The build process works more smoothly with the legacy Sun tools so, if you
3487 have @file{/usr/xpg4/bin} in your @env{PATH}, we recommend that you place
3488 @file{/usr/bin} before @file{/usr/xpg4/bin} for the duration of the build.
3490 All releases of GNU binutils prior to 2.11.2 have known bugs on this
3491 platform. We recommend the use of GNU binutils 2.11.2 or later, or the
3492 vendor tools (Sun @command{as}, Sun @command{ld}). Note that your mileage
3493 may vary if you use a combination of the GNU tools and the Sun tools: while
3494 the combination GNU @command{as} + Sun @command{ld} should reasonably work,
3495 the reverse combination Sun @command{as} + GNU @command{ld} is known to
3496 cause memory corruption at runtime in some cases for C++ programs.
3498 The stock GNU binutils 2.15 release is broken on this platform because of a
3499 single bug. It has been fixed on the 2.15 branch in the CVS repository.
3500 You can obtain a working version by checking out the binutils-2_15-branch
3501 from the CVS repository or applying the patch
3502 @uref{http://sources.redhat.com/ml/binutils-cvs/2004-09/msg00036.html} to the
3505 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3506 newer: @command{g++} will complain that types are missing. These headers assume
3507 that omitting the type means @code{int}; this assumption worked for C89 but
3508 is wrong for C++, and is now wrong for C99 also.
3510 @command{g++} accepts such (invalid) constructs with the option
3511 @option{-fpermissive}; it
3512 will assume that any missing type is @code{int} (as defined by C89).
3514 There are patches for Solaris 2.6 (105633-56 or newer for SPARC,
3515 106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC,
3516 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
3517 108653-22 for Intel) that fix this bug.
3519 Sun bug 4927647 sometimes causes random spurious testsuite failures
3520 related to missing diagnostic output. This bug doesn't affect GCC
3521 itself, rather it is a kernel bug triggered by the @command{expect}
3522 program which is used only by the GCC testsuite driver. When the bug
3523 causes the @command{expect} program to miss anticipated output, extra
3524 testsuite failures appear.
3526 There are patches for Solaris 8 (117350-12 or newer for SPARC,
3527 117351-12 or newer for Intel) and Solaris 9 (117171-11 or newer for
3528 SPARC, 117172-11 or newer for Intel) that address this problem.
3533 @heading @anchor{sparc-sun-solaris2*}sparc-sun-solaris2*
3535 When GCC is configured to use binutils 2.11.2 or later the binaries
3536 produced are smaller than the ones produced using Sun's native tools;
3537 this difference is quite significant for binaries containing debugging
3540 Sun @command{as} 4.x is broken in that it cannot cope with long symbol names.
3541 A typical error message might look similar to the following:
3544 /usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error:
3545 can't compute value of an expression involving an external symbol.
3548 This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris
3549 2.6 and has been fixed in later (5.x) versions of the assembler,
3550 starting with Solaris 7.
3552 Starting with Solaris 7, the operating system is capable of executing
3553 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
3554 this; the @option{-m64} option enables 64-bit code generation.
3555 However, if all you want is code tuned for the UltraSPARC CPU, you
3556 should try the @option{-mtune=ultrasparc} option instead, which produces
3557 code that, unlike full 64-bit code, can still run on non-UltraSPARC
3560 When configuring on a Solaris 7 or later system that is running a kernel
3561 that supports only 32-bit binaries, one must configure with
3562 @option{--disable-multilib}, since we will not be able to build the
3563 64-bit target libraries.
3565 GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of
3566 the GNU compiler (especially GCC 3.0.x versions), which lead to the
3567 miscompilation of the stage1 compiler and the subsequent failure of the
3568 bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary
3569 stage, i.e.@: to bootstrap that compiler with the base compiler and then
3570 use it to bootstrap the final compiler.
3572 GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7)
3573 and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap
3574 failure in form of a miscompilation of the stage1 compiler by the Sun
3575 compiler. This is Sun bug 4974440. This is fixed with patch 112760-07.
3577 GCC 3.4 changed the default debugging format from STABS to DWARF-2 for
3578 32-bit code on Solaris 7 and later. If you are using the Sun
3579 assembler, this change apparently runs afoul of Sun bug 4910101, for
3580 which (as of 2004-05-23) there is no fix. A symptom of the problem is
3581 that you cannot compile C++ programs like @command{groff} 1.19.1
3582 without getting messages similar to the following:
3585 ld: warning: relocation error: R_SPARC_UA32: @dots{}
3586 external symbolic relocation against non-allocatable section
3587 .debug_info cannot be processed at runtime: relocation ignored.
3590 To work around this problem, compile with @option{-gstabs+} instead of
3596 @heading @anchor{sparc-sun-solaris2.7}sparc-sun-solaris2.7
3598 Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
3599 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
3600 and later, including all EGCS releases. Sun formerly recommended
3601 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
3602 recommend it only for people who use Sun's compilers.
3604 Here are some workarounds to this problem:
3607 Do not install Sun patch 107058-01 until after Sun releases a
3608 complete patch for bug 4210064. This is the simplest course to take,
3609 unless you must also use Sun's C compiler. Unfortunately 107058-01
3610 is preinstalled on some new Solaris 7-based hosts, so you may have to
3614 Copy the original, unpatched Solaris 7
3615 @command{/usr/ccs/bin/as} into
3616 @command{/usr/local/libexec/gcc/sparc-sun-solaris2.7/3.4/as},
3617 adjusting the latter name to fit your local conventions and software
3621 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
3622 both 107058-01 and 106950-03 installed has reported the bug with GCC
3623 and Sun's dynamic linker. This last course of action is riskiest,
3624 for two reasons. First, you must install 106950 on all hosts that
3625 run code generated by GCC; it doesn't suffice to install it only on
3626 the hosts that run GCC itself. Second, Sun says that 106950-03 is
3627 only a partial fix for bug 4210064, but Sun doesn't know whether the
3628 partial fix is adequate for GCC@. Revision -08 or later should fix
3629 the bug. The current (as of 2004-05-23) revision is -24, and is included in
3630 the Solaris 7 Recommended Patch Cluster.
3633 GCC 3.3 triggers a bug in version 5.0 Alpha 03/27/98 of the Sun assembler,
3634 which causes a bootstrap failure when linking the 64-bit shared version of
3635 libgcc. A typical error message is:
3638 ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o:
3639 symbol <unknown>: offset 0xffffffff7ec133e7 is non-aligned.
3642 This bug has been fixed in the final 5.0 version of the assembler.
3647 @heading @anchor{sparc-*-linux*}sparc-*-linux*
3649 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
3650 or newer on this platform. All earlier binutils and glibc
3651 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
3657 @heading @anchor{sparc64-*-solaris2*}sparc64-*-solaris2*
3659 The following compiler flags must be specified in the configure
3660 step in order to bootstrap this target with the Sun compiler:
3663 % CC="cc -xildoff -xarch=v9" @var{srcdir}/configure [@var{options}] [@var{target}]
3666 @option{-xildoff} turns off the incremental linker, and @option{-xarch=v9}
3667 specifies the SPARC-V9 architecture to the Sun linker and assembler.
3672 @heading @anchor{sparcv9-*-solaris2*}sparcv9-*-solaris2*
3674 This is a synonym for sparc64-*-solaris2*.
3679 @heading @anchor{#*-*-sysv*}*-*-sysv*
3680 On System V release 3, you may get this error message
3684 ld fatal: failed to write symbol name @var{something}
3685 in strings table for file @var{whatever}
3688 This probably indicates that the disk is full or your ulimit won't allow
3689 the file to be as large as it needs to be.
3691 This problem can also result because the kernel parameter @code{MAXUMEM}
3692 is too small. If so, you must regenerate the kernel and make the value
3693 much larger. The default value is reported to be 1024; a value of 32768
3694 is said to work. Smaller values may also work.
3696 On System V, if you get an error like this,
3699 /usr/local/lib/bison.simple: In function `yyparse':
3700 /usr/local/lib/bison.simple:625: virtual memory exhausted
3704 that too indicates a problem with disk space, ulimit, or @code{MAXUMEM}.
3706 On a System V release 4 system, make sure @file{/usr/bin} precedes
3707 @file{/usr/ucb} in @code{PATH}. The @command{cc} command in
3708 @file{/usr/ucb} uses libraries which have bugs.
3713 @heading @anchor{vax-dec-ultrix}vax-dec-ultrix
3714 Don't try compiling with VAX C (@command{vcc}). It produces incorrect code
3715 in some cases (for example, when @code{alloca} is used).
3720 @heading @anchor{*-*-vxworks*}*-*-vxworks*
3721 Support for VxWorks is in flux. At present GCC supports @emph{only} the
3722 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC@.
3723 We welcome patches for other architectures supported by VxWorks 5.5.
3724 Support for VxWorks AE would also be welcome; we believe this is merely
3725 a matter of writing an appropriate ``configlette'' (see below). We are
3726 not interested in supporting older, a.out or COFF-based, versions of
3729 VxWorks comes with an older version of GCC installed in
3730 @file{@var{$WIND_BASE}/host}; we recommend you do not overwrite it.
3731 Choose an installation @var{prefix} entirely outside @var{$WIND_BASE}.
3732 Before running @command{configure}, create the directories @file{@var{prefix}}
3733 and @file{@var{prefix}/bin}. Link or copy the appropriate assembler,
3734 linker, etc.@: into @file{@var{prefix}/bin}, and set your @var{PATH} to
3735 include that directory while running both @command{configure} and
3738 You must give @command{configure} the
3739 @option{--with-headers=@var{$WIND_BASE}/target/h} switch so that it can
3740 find the VxWorks system headers. Since VxWorks is a cross compilation
3741 target only, you must also specify @option{--target=@var{target}}.
3742 @command{configure} will attempt to create the directory
3743 @file{@var{prefix}/@var{target}/sys-include} and copy files into it;
3744 make sure the user running @command{configure} has sufficient privilege
3747 GCC's exception handling runtime requires a special ``configlette''
3748 module, @file{contrib/gthr_supp_vxw_5x.c}. Follow the instructions in
3749 that file to add the module to your kernel build. (Future versions of
3750 VxWorks will incorporate this module.)
3755 @heading @anchor{x86_64-*-*}x86_64-*-*, amd64-*-*
3757 GCC supports the x86-64 architecture implemented by the AMD64 processor
3758 (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD@.
3759 On GNU/Linux the default is a bi-arch compiler which is able to generate
3760 both 64-bit x86-64 and 32-bit x86 code (via the @option{-m32} switch).
3765 @heading @anchor{xtensa-*-elf}xtensa-*-elf
3767 This target is intended for embedded Xtensa systems using the
3768 @samp{newlib} C library. It uses ELF but does not support shared
3769 objects. Designed-defined instructions specified via the
3770 Tensilica Instruction Extension (TIE) language are only supported
3771 through inline assembly.
3773 The Xtensa configuration information must be specified prior to
3774 building GCC@. The @file{include/xtensa-config.h} header
3775 file contains the configuration information. If you created your
3776 own Xtensa configuration with the Xtensa Processor Generator, the
3777 downloaded files include a customized copy of this header file,
3778 which you can use to replace the default header file.
3783 @heading @anchor{xtensa-*-linux*}xtensa-*-linux*
3785 This target is for Xtensa systems running GNU/Linux. It supports ELF
3786 shared objects and the GNU C library (glibc). It also generates
3787 position-independent code (PIC) regardless of whether the
3788 @option{-fpic} or @option{-fPIC} options are used. In other
3789 respects, this target is the same as the
3790 @uref{#xtensa-*-elf,,@samp{xtensa-*-elf}} target.
3795 @heading @anchor{windows}Microsoft Windows (32-bit)
3797 A port of GCC 2.95.2 and 3.x is included with the
3798 @uref{http://www.cygwin.com/,,Cygwin environment}.
3800 Current (as of early 2001) snapshots of GCC will build under Cygwin
3801 without modification.
3803 GCC does not currently build with Microsoft's C++ compiler and there
3804 are no plans to make it do so.
3809 @heading @anchor{os2}OS/2
3811 GCC does not currently support OS/2. However, Andrew Zabolotny has been
3812 working on a generic OS/2 port with pgcc. The current code can be found
3813 at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
3815 An older copy of GCC 2.8.1 is included with the EMX tools available at
3816 @uref{ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/,,
3817 ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/}.
3822 @heading @anchor{older}Older systems
3824 GCC contains support files for many older (1980s and early
3825 1990s) Unix variants. For the most part, support for these systems
3826 has not been deliberately removed, but it has not been maintained for
3827 several years and may suffer from bitrot.
3829 Starting with GCC 3.1, each release has a list of ``obsoleted'' systems.
3830 Support for these systems is still present in that release, but
3831 @command{configure} will fail unless the @option{--enable-obsolete}
3832 option is given. Unless a maintainer steps forward, support for these
3833 systems will be removed from the next release of GCC@.
3835 Support for old systems as hosts for GCC can cause problems if the
3836 workarounds for compiler, library and operating system bugs affect the
3837 cleanliness or maintainability of the rest of GCC@. In some cases, to
3838 bring GCC up on such a system, if still possible with current GCC, may
3839 require first installing an old version of GCC which did work on that
3840 system, and using it to compile a more recent GCC, to avoid bugs in the
3841 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
3842 @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror
3843 sites}. Header bugs may generally be avoided using
3844 @command{fixincludes}, but bugs or deficiencies in libraries and the
3845 operating system may still cause problems.
3847 Support for older systems as targets for cross-compilation is less
3848 problematic than support for them as hosts for GCC; if an enthusiast
3849 wishes to make such a target work again (including resurrecting any of
3850 the targets that never worked with GCC 2, starting from the last CVS
3851 version before they were removed), patches
3852 @uref{../contribute.html,,following the usual requirements} would be
3853 likely to be accepted, since they should not affect the support for more
3856 For some systems, old versions of GNU binutils may also be useful,
3857 and are available from @file{pub/binutils/old-releases} on
3858 @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}.
3860 Some of the information on specific systems above relates to
3861 such older systems, but much of the information
3862 about GCC on such systems (which may no longer be applicable to
3863 current GCC) is to be found in the GCC texinfo manual.
3868 @heading @anchor{elf_targets}all ELF targets (SVR4, Solaris 2, etc.)
3870 C++ support is significantly better on ELF targets if you use the
3871 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
3872 inlines, vtables and template instantiations will be discarded
3881 @uref{./index.html,,Return to the GCC Installation page}
3885 @c ***Old documentation******************************************************
3887 @include install-old.texi
3893 @uref{./index.html,,Return to the GCC Installation page}
3897 @c ***GFDL********************************************************************
3905 @uref{./index.html,,Return to the GCC Installation page}
3909 @c ***************************************************************************
3910 @c Part 6 The End of the Document
3912 @comment node-name, next, previous, up
3913 @node Concept Index, , GNU Free Documentation License, Top
3917 @unnumbered Concept Index