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 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 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.
91 @c Part 3 Titlepage and Copyright
94 @comment The title is printed in a large font.
95 @center @titlefont{Installing GCC}
97 @c The following two commands start the copyright page.
99 @vskip 0pt plus 1filll
103 @c Part 4 Top node and Master Menu
106 @comment node-name, next, Previous, up
109 * Installing GCC:: This document describes the generic installation
110 procedure for GCC as well as detailing some target
111 specific installation instructions.
113 * Specific:: Host/target specific installation notes for GCC.
114 * Binaries:: Where to get pre-compiled binaries.
116 * Old:: Old installation documentation.
118 * GNU Free Documentation License:: How you can copy and share this manual.
119 * Concept Index:: This index has two entries.
123 @c Part 5 The Body of the Document
124 @c ***Installing GCC**********************************************************
126 @comment node-name, next, previous, up
127 @node Installing GCC, Binaries, , Top
131 @chapter Installing GCC
134 The latest version of this document is always available at
135 @uref{http://gcc.gnu.org/install/,,http://gcc.gnu.org/install/}.
137 This document describes the generic installation procedure for GCC as well
138 as detailing some target specific installation instructions.
140 GCC includes several components that previously were separate distributions
141 with their own installation instructions. This document supersedes all
142 package specific installation instructions.
144 @emph{Before} starting the build/install procedure please check the
146 @ref{Specific, host/target specific installation notes}.
149 @uref{specific.html,,host/target specific installation notes}.
151 We recommend you browse the entire generic installation instructions before
154 Lists of successful builds for released versions of GCC are
155 available at @uref{http://gcc.gnu.org/buildstat.html}.
156 These lists are updated as new information becomes available.
158 The installation procedure itself is broken into five steps.
163 * Downloading the source::
166 * Testing:: (optional)
173 @uref{prerequisites.html,,Prerequisites}
175 @uref{download.html,,Downloading the source}
177 @uref{configure.html,,Configuration}
179 @uref{build.html,,Building}
181 @uref{test.html,,Testing} (optional)
183 @uref{finalinstall.html,,Final install}
187 Please note that GCC does not support @samp{make uninstall} and probably
188 won't do so in the near future as this would open a can of worms. Instead,
189 we suggest that you install GCC into a directory of its own and simply
190 remove that directory when you do not need that specific version of GCC
191 any longer, and, if shared libraries are installed there as well, no
192 more binaries exist that use them.
195 There are also some @uref{old.html,,old installation instructions},
196 which are mostly obsolete but still contain some information which has
197 not yet been merged into the main part of this manual.
205 @uref{./index.html,,Return to the GCC Installation page}
211 @c ***Prerequisites**************************************************
213 @comment node-name, next, previous, up
214 @node Prerequisites, Downloading the source, , Installing GCC
216 @ifset prerequisiteshtml
218 @chapter Prerequisites
220 @cindex Prerequisites
222 GCC requires that various tools and packages be available for use in the
223 build procedure. Modifying GCC sources requires additional tools
226 @heading Tools/packages necessary for building GCC
228 @item ISO C90 compiler
229 Necessary to bootstrap the GCC package, although versions of GCC prior
230 to 3.4 also allow bootstrapping with a traditional (K&R) C compiler.
232 To make all languages in a cross-compiler or other configuration where
233 3-stage bootstrap is not performed, you need to start with an existing
234 GCC binary (version 2.95 or later) because source code for language
235 frontends other than C might use GCC extensions.
239 In order to build the Ada compiler (GNAT) you must already have GNAT
240 installed because portions of the Ada frontend are written in Ada (with
241 GNAT extensions.) Refer to the Ada installation instructions for more
242 specific information.
244 @item A ``working'' POSIX compatible shell, or GNU bash
246 Necessary when running @command{configure} because some
247 @command{/bin/sh} shells have bugs and may crash when configuring the
248 target libraries. In other cases, @command{/bin/sh} or even some
249 @command{ksh} have disastrous corner-case performance problems. This
250 can cause target @command{configure} runs to literally take days to
251 complete in some cases.
253 So on some platforms @command{/bin/ksh} is sufficient, on others it
254 isn't. See the host/target specific instructions for your platform, or
255 use @command{bash} to be sure. Then set @env{CONFIG_SHELL} in your
256 environment to your ``good'' shell prior to running
257 @command{configure}/@command{make}.
259 @command{zsh} is not a fully compliant POSIX shell and will not
260 work when configuring GCC.
264 Necessary in some circumstances, optional in others. See the
265 host/target specific instructions for your platform for the exact
268 @item gzip version 1.2.4 (or later) or
269 @itemx bzip2 version 1.0.2 (or later)
271 Necessary to uncompress GCC @command{tar} files when source code is
272 obtained via FTP mirror sites.
274 @item GNU make version 3.79.1 (or later)
276 You must have GNU make installed to build GCC.
278 @item GNU tar version 1.12 (or later)
280 Necessary (only on some platforms) to untar the source code. Many
281 systems' @command{tar} programs will also work, only try GNU
282 @command{tar} if you have problems.
287 @heading Tools/packages necessary for modifying GCC
290 @item autoconf version 2.13 (NO earlier or later versions) and
291 @itemx GNU m4 version 1.4 (or later)
293 Necessary when modifying @file{configure.in}, @file{aclocal.m4}, etc.@:
294 to regenerate @file{configure} and @file{config.in} files
296 @item automake version ???
298 Necessary when modifying a @file{Makefile.am} file to regenerate its
299 associated @file{Makefile.in}
301 @item gperf version 2.7.2 (or later)
303 Necessary when modifying @command{gperf} input files, e.g.@:
304 @file{gcc/cp/cfns.gperf} to regenerate its associated header file, e.g.@:
305 @file{gcc/cp/cfns.h}.
307 @item expect version ???
308 @itemx tcl version ???
309 @itemx dejagnu version ???
311 Necessary to run the GCC testsuite.
313 @item autogen version 5.5.4 (or later) and
314 @itemx guile version 1.4.1 (or later)
316 Necessary to regenerate @file{fixinc/fixincl.x} from
317 @file{fixinc/inclhack.def} and @file{fixinc/*.tpl}.
319 Necessary to run the @file{fixinc} @command{make check}.
321 Necessary to regenerate the top level @file{Makefile.am} files from
322 @file{Makefile.tpl} and @file{Makefile.def}.
324 @item GNU Bison version 1.28 (or later)
325 Berkeley @command{yacc} (@command{byacc}) is also reported to work other
328 Necessary when modifying @file{*.y} files.
330 Necessary to build GCC during development because the generated output
331 files are not included in the CVS repository. They are included in
334 @item Flex version 2.5.4 (or later)
336 Necessary when modifying @file{*.l} files.
338 Necessary to build GCC during development because the generated output
339 files are not included in the CVS repository. They are included in
342 @item Texinfo version 4.2 (or later)
344 Necessary for running @command{makeinfo} when modifying @file{*.texi}
345 files to test your changes.
347 Necessary to build GCC documentation during development because the
348 generated output files are not included in the CVS repository. They are
349 included in releases.
351 @item @TeX{} (any working version)
353 Necessary for running @command{texi2dvi}, used when running
354 @command{make dvi} to create DVI files.
356 @item cvs version 1.10 (or later)
357 @itemx ssh (any version)
359 Necessary to access the CVS repository. Public releases and weekly
360 snapshots of the development sources are also available via FTP.
362 @item perl version 5.6.1 (or later)
364 Necessary when regenerating @file{Makefile} dependencies in libiberty.
365 Necessary when regenerating something with intl??? (pod2man???)
368 @item GNU diffutils version 2.7 (or later)
370 Necessary when creating changes to GCC source code to submit for review.
372 @item patch version 2.5.4 (or later)
374 Necessary when applying patches, created with @command{diff}, to one's
384 @uref{./index.html,,Return to the GCC Installation page}
388 @c ***Downloading the source**************************************************
390 @comment node-name, next, previous, up
391 @node Downloading the source, Configuration, Prerequisites, Installing GCC
395 @chapter Downloading GCC
397 @cindex Downloading GCC
398 @cindex Downloading the Source
400 GCC is distributed via @uref{http://gcc.gnu.org/cvs.html,,CVS} and FTP
401 tarballs compressed with @command{gzip} or
402 @command{bzip2}. It is possible to download a full distribution or specific
405 Please refer to our @uref{http://gcc.gnu.org/releases.html,,releases web page}
406 for information on how to obtain GCC@.
408 The full distribution includes the C, C++, Objective-C, Fortran, Java,
409 and Ada (in case of GCC 3.1 and later) compilers. The full distribution
410 also includes runtime libraries for C++, Objective-C, Fortran, and Java.
411 In GCC 3.0 and later versions, GNU compiler testsuites are also included
412 in the full distribution.
414 If you choose to download specific components, you must download the core
415 GCC distribution plus any language specific distributions you wish to
416 use. The core distribution includes the C language front end as well as the
417 shared components. Each language has a tarball which includes the language
418 front end as well as the language runtime (when appropriate).
420 Unpack the core distribution as well as any language specific
421 distributions in the same directory.
423 If you also intend to build binutils (either to upgrade an existing
424 installation or for use in place of the corresponding tools of your
425 OS), unpack the binutils distribution either in the same directory or
426 a separate one. In the latter case, add symbolic links to any
427 components of the binutils you intend to build alongside the compiler
428 (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
429 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
436 @uref{./index.html,,Return to the GCC Installation page}
440 @c ***Configuration***********************************************************
442 @comment node-name, next, previous, up
443 @node Configuration, Building, Downloading the source, Installing GCC
447 @chapter Installing GCC: Configuration
449 @cindex Configuration
450 @cindex Installing GCC: Configuration
452 Like most GNU software, GCC must be configured before it can be built.
453 This document describes the recommended configuration procedure
454 for both native and cross targets.
456 We use @var{srcdir} to refer to the toplevel source directory for
457 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
459 If you obtained the sources via CVS, @var{srcdir} must refer to the top
460 @file{gcc} directory, the one where the @file{MAINTAINERS} can be found,
461 and not its @file{gcc} subdirectory, otherwise the build will fail.
463 If either @var{srcdir} or @var{objdir} is located on an automounted NFS
464 file system, the shell's built-in @command{pwd} command will return
465 temporary pathnames. Using these can lead to various sorts of build
466 problems. To avoid this issue, set the @env{PWDCMD} environment
467 variable to an automounter-aware @command{pwd} command, e.g.,
468 @command{pawd} or @samp{amq -w}, during the configuration and build
471 First, we @strong{highly} recommend that GCC be built into a
472 separate directory than the sources which does @strong{not} reside
473 within the source tree. This is how we generally build GCC; building
474 where @var{srcdir} == @var{objdir} should still work, but doesn't
475 get extensive testing; building where @var{objdir} is a subdirectory
476 of @var{srcdir} is unsupported.
478 If you have previously built GCC in the same directory for a
479 different target machine, do @samp{make distclean} to delete all files
480 that might be invalid. One of the files this deletes is @file{Makefile};
481 if @samp{make distclean} complains that @file{Makefile} does not exist
482 or issues a message like ``don't know how to make distclean'' it probably
483 means that the directory is already suitably clean. However, with the
484 recommended method of building in a separate @var{objdir}, you should
485 simply use a different @var{objdir} for each target.
487 Second, when configuring a native system, either @command{cc} or
488 @command{gcc} must be in your path or you must set @env{CC} in
489 your environment before running configure. Otherwise the configuration
492 Note that the bootstrap compiler and the resulting GCC must be link
493 compatible, else the bootstrap will fail with linker errors about
494 incompatible object file formats. Several multilibed targets are
495 affected by this requirement, see
497 @ref{Specific, host/target specific installation notes}.
500 @uref{specific.html,,host/target specific installation notes}.
508 % @var{srcdir}/configure [@var{options}] [@var{target}]
512 @heading Target specification
515 GCC has code to correctly determine the correct value for @var{target}
516 for nearly all native systems. Therefore, we highly recommend you not
517 provide a configure target when configuring a native compiler.
520 @var{target} must be specified as @option{--target=@var{target}}
521 when configuring a cross compiler; examples of valid targets would be
522 i960-rtems, m68k-coff, sh-elf, etc.
525 Specifying just @var{target} instead of @option{--target=@var{target}}
526 implies that the host defaults to @var{target}.
530 @heading Options specification
532 Use @var{options} to override several configure time options for
533 GCC@. A list of supported @var{options} follows; @samp{configure
534 --help} may list other options, but those not listed below may not
535 work and should not normally be used.
538 @item --prefix=@var{dirname}
539 Specify the toplevel installation
540 directory. This is the recommended way to install the tools into a directory
541 other than the default. The toplevel installation directory defaults to
544 We @strong{highly} recommend against @var{dirname} being the same or a
545 subdirectory of @var{objdir} or vice versa. If specifying a directory
546 beneath a user's home directory tree, some shells will not expand
547 @var{dirname} correctly if it contains the @samp{~} metacharacter; use
550 The following standard @command{autoconf} options are supported. Normally you
551 should not need to use these options.
553 @item --exec-prefix=@var{dirname}
554 Specify the toplevel installation directory for architecture-dependent
555 files. The default is @file{@var{prefix}}.
557 @item --bindir=@var{dirname}
558 Specify the installation directory for the executables called by users
559 (such as @command{gcc} and @command{g++}). The default is
560 @file{@var{exec-prefix}/bin}.
562 @item --libdir=@var{dirname}
563 Specify the installation directory for object code libraries and
564 internal data files of GCC@. The default is @file{@var{exec-prefix}/lib}.
566 @item --libexecdir=@var{dirname}
567 Specify the installation directory for internal executables of GCC@.
568 The default is @file{@var{exec-prefix}/libexec}.
570 @item --with-slibdir=@var{dirname}
571 Specify the installation directory for the shared libgcc library. The
572 default is @file{@var{libdir}}.
574 @item --infodir=@var{dirname}
575 Specify the installation directory for documentation in info format.
576 The default is @file{@var{prefix}/info}.
578 @item --datadir=@var{dirname}
579 Specify the installation directory for some architecture-independent
580 data files referenced by GCC@. The default is @file{@var{prefix}/share}.
582 @item --mandir=@var{dirname}
583 Specify the installation directory for manual pages. The default is
584 @file{@var{prefix}/man}. (Note that the manual pages are only extracts from
585 the full GCC manuals, which are provided in Texinfo format. The manpages
586 are derived by an automatic conversion process from parts of the full
589 @item --with-gxx-include-dir=@var{dirname}
591 the installation directory for G++ header files. The default is
592 @file{@var{prefix}/include/g++-v3}.
596 @item --program-prefix=@var{prefix}
597 GCC supports some transformations of the names of its programs when
598 installing them. This option prepends @var{prefix} to the names of
599 programs to install in @var{bindir} (see above). For example, specifying
600 @option{--program-prefix=foo-} would result in @samp{gcc}
601 being installed as @file{/usr/local/bin/foo-gcc}.
603 @item --program-suffix=@var{suffix}
604 Appends @var{suffix} to the names of programs to install in @var{bindir}
605 (see above). For example, specifying @option{--program-suffix=-3.1}
606 would result in @samp{gcc} being installed as
607 @file{/usr/local/bin/gcc-3.1}.
609 @item --program-transform-name=@var{pattern}
610 Applies the @samp{sed} script @var{pattern} to be applied to the names
611 of programs to install in @var{bindir} (see above). @var{pattern} has to
612 consist of one or more basic @samp{sed} editing commands, separated by
613 semicolons. For example, if you want the @samp{gcc} program name to be
614 transformed to the installed program @file{/usr/local/bin/myowngcc} and
615 the @samp{g++} program name to be transformed to
616 @file{/usr/local/bin/gspecial++} without changing other program names,
617 you could use the pattern
618 @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}
619 to achieve this effect.
621 All three options can be combined and used together, resulting in more
622 complex conversion patterns. As a basic rule, @var{prefix} (and
623 @var{suffix}) are prepended (appended) before further transformations
624 can happen with a special transformation script @var{pattern}.
626 As currently implemented, this option only takes effect for native
627 builds; cross compiler binaries' names are not transformed even when a
628 transformation is explicitly asked for by one of these options.
630 For native builds, some of the installed programs are also installed
631 with the target alias in front of their name, as in
632 @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
633 before the target alias is prepended to the name - so, specifying
634 @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
635 resulting binary would be installed as
636 @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.
638 As a last shortcoming, none of the installed Ada programs are
639 transformed yet, which will be fixed in some time.
641 @item --with-local-prefix=@var{dirname}
643 installation directory for local include files. The default is
644 @file{/usr/local}. Specify this option if you want the compiler to
645 search directory @file{@var{dirname}/include} for locally installed
646 header files @emph{instead} of @file{/usr/local/include}.
648 You should specify @option{--with-local-prefix} @strong{only} if your
649 site has a different convention (not @file{/usr/local}) for where to put
652 The default value for @option{--with-local-prefix} is @file{/usr/local}
653 regardless of the value of @option{--prefix}. Specifying
654 @option{--prefix} has no effect on which directory GCC searches for
655 local header files. This may seem counterintuitive, but actually it is
658 The purpose of @option{--prefix} is to specify where to @emph{install
659 GCC}. The local header files in @file{/usr/local/include}---if you put
660 any in that directory---are not part of GCC@. They are part of other
661 programs---perhaps many others. (GCC installs its own header files in
662 another directory which is based on the @option{--prefix} value.)
664 Both the local-prefix include directory and the GCC-prefix include
665 directory are part of GCC's "system include" directories. Although these
666 two directories are not fixed, they need to be searched in the proper
667 order for the correct processing of the include_next directive. The
668 local-prefix include directory is searched before the GCC-prefix
669 include directory. Another characteristic of system include directories
670 is that pedantic warnings are turned off for headers in these directories.
672 Some autoconf macros add @option{-I @var{directory}} options to the
673 compiler command line, to ensure that directories containing installed
674 packages' headers are searched. When @var{directory} is one of GCC's
675 system include directories, GCC will ignore the option so that system
676 directories continue to be processed in the correct order. This
677 may result in a search order different from what was specified but the
678 directory will still be searched.
680 GCC automatically searches for ordinary libraries using
681 @env{GCC_EXEC_PREFIX}. Thus, when the same installation prefix is
682 used for both GCC and packages, GCC will automatically search for
683 both headers and libraries. This provides a configuration that is
684 easy to use. GCC behaves in a manner similar to that when it is
685 installed as a system compiler in @file{/usr}.
687 Sites that need to install multiple versions of GCC may not want to
688 use the above simple configuration. It is possible to use the
689 @option{--program-prefix}, @option{--program-suffix} and
690 @option{--program-transform-name} options to install multiple versions
691 into a single directory, but it may be simpler to use different prefixes
692 and the @option{--with-local-prefix} option to specify the location of the
693 site-specific files for each version. It will then be necessary for
694 users to specify explicitly the location of local site libraries
695 (e.g., with @env{LIBRARY_PATH}).
697 The same value can be used for both @option{--with-local-prefix} and
698 @option{--prefix} provided it is not @file{/usr}. This can be used
699 to avoid the default search of @file{/usr/local/include}.
701 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
702 The directory you use for @option{--with-local-prefix} @strong{must not}
703 contain any of the system's standard header files. If it did contain
704 them, certain programs would be miscompiled (including GNU Emacs, on
705 certain targets), because this would override and nullify the header
706 file corrections made by the @command{fixincludes} script.
708 Indications are that people who use this option use it based on mistaken
709 ideas of what it is for. People use it as if it specified where to
710 install part of GCC@. Perhaps they make this assumption because
711 installing GCC creates the directory.
713 @item --enable-shared[=@var{package}[,@dots{}]]
714 Build shared versions of libraries, if shared libraries are supported on
715 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
716 are enabled by default on all platforms that support shared libraries,
717 except for @samp{libobjc} which is built as a static library only by
720 If a list of packages is given as an argument, build shared libraries
721 only for the listed packages. For other packages, only static libraries
722 will be built. Package names currently recognized in the GCC tree are
723 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
724 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc} and
725 @samp{libjava}. Note that @samp{libobjc} does not recognize itself by
726 any name, so, if you list package names in @option{--enable-shared},
727 you will only get static Objective-C libraries. @samp{libf2c} and
728 @samp{libiberty} do not support shared libraries at all.
730 Use @option{--disable-shared} to build only static libraries. Note that
731 @option{--disable-shared} does not accept a list of package names as
732 argument, only @option{--enable-shared} does.
734 @item @anchor{with-gnu-as}--with-gnu-as
735 Specify that the compiler should assume that the
736 assembler it finds is the GNU assembler. However, this does not modify
737 the rules to find an assembler and will result in confusion if the
738 assembler found is not actually the GNU assembler. (Confusion may also
739 result if the compiler finds the GNU assembler but has not been
740 configured with @option{--with-gnu-as}.) If you have more than one
741 assembler installed on your system, you may want to use this option in
742 connection with @option{--with-as=@var{pathname}}.
744 The following systems are the only ones where it makes a difference
745 whether you use the GNU assembler. On any other system,
746 @option{--with-gnu-as} has no effect.
749 @item @samp{hppa1.0-@var{any}-@var{any}}
750 @item @samp{hppa1.1-@var{any}-@var{any}}
751 @item @samp{i386-@var{any}-sysv}
752 @item @samp{m68k-bull-sysv}
753 @item @samp{m68k-hp-hpux}
754 @item @samp{m68000-hp-hpux}
755 @item @samp{m68000-att-sysv}
756 @item @samp{@var{any}-lynx-lynxos}
757 @item @samp{mips-@var{any}}
758 @item @samp{sparc-sun-solaris2.@var{any}}
759 @item @samp{sparc64-@var{any}-solaris2.@var{any}}
762 On the systems listed above (except for the HP-PA, the SPARC, for ISC on
763 the 386, and for @samp{mips-sgi-irix5.*}), if you use the GNU assembler,
764 you should also use the GNU linker (and specify @option{--with-gnu-ld}).
766 @item @anchor{with-as}--with-as=@var{pathname}
768 compiler should use the assembler pointed to by @var{pathname}, rather
769 than the one found by the standard rules to find an assembler, which
773 Check the @file{@var{libexec}/gcc/@var{target}/@var{version}}
774 directory, where @var{libexec} defaults to
775 @file{@var{exec-prefix}/libexec} and @var{exec-prefix} defaults to
776 @var{prefix} which defaults to @file{/usr/local} unless overridden by
777 the @option{--prefix=@var{pathname}} switch described
778 above. @var{target} is the target system triple, such as
779 @samp{sparc-sun-solaris2.7}, and @var{version} denotes the GCC
780 version, such as 3.0.
782 Check operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
785 Note that these rules do not check for the value of @env{PATH}. You may
786 want to use @option{--with-as} if no assembler is installed in the
787 directories listed above, or if you have multiple assemblers installed
788 and want to choose one that is not found by the above rules.
790 @item @anchor{with-gnu-ld}--with-gnu-ld
791 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
794 @item --with-ld=@var{pathname}
795 Same as @uref{#with-as,,@option{--with-as}}
799 Specify that stabs debugging
800 information should be used instead of whatever format the host normally
801 uses. Normally GCC uses the same debug format as the host system.
803 On MIPS based systems and on Alphas, you must specify whether you want
804 GCC to create the normal ECOFF debugging format, or to use BSD-style
805 stabs passed through the ECOFF symbol table. The normal ECOFF debug
806 format cannot fully handle languages other than C@. BSD stabs format can
807 handle other languages, but it only works with the GNU debugger GDB@.
809 Normally, GCC uses the ECOFF debugging format by default; if you
810 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
812 No matter which default you choose when you configure GCC, the user
813 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
814 the debug format for a particular compilation.
816 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
817 @option{--with-gas} is used. It selects use of stabs debugging
818 information embedded in COFF output. This kind of debugging information
819 supports C++ well; ordinary COFF debugging information does not.
821 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
822 selects use of stabs debugging information embedded in ELF output. The
823 C++ compiler currently (2.6.0) does not support the DWARF debugging
824 information normally used on 386 SVR4 platforms; stabs provide a
825 workable alternative. This requires gas and gdb, as the normal SVR4
826 tools can not generate or interpret stabs.
828 @item --disable-multilib
829 Specify that multiple target
830 libraries to support different target variants, calling
831 conventions, etc should not be built. The default is to build a
832 predefined set of them.
834 Some targets provide finer-grained control over which multilibs are built
835 (e.g., @option{--disable-softfloat}):
841 fpu, 26bit, underscore, interwork, biendian, nofmult.
844 softfloat, m68881, m68000, m68020.
847 single-float, biendian, softfloat.
849 @item powerpc*-*-*, rs6000*-*-*
850 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
855 @item --enable-threads
856 Specify that the target
857 supports threads. This affects the Objective-C compiler and runtime
858 library, and exception handling for other languages like C++ and Java.
859 On some systems, this is the default.
861 In general, the best (and, in many cases, the only known) threading
862 model available will be configured for use. Beware that on some
863 systems, gcc has not been taught what threading models are generally
864 available for the system. In this case, @option{--enable-threads} is an
865 alias for @option{--enable-threads=single}.
867 @item --disable-threads
868 Specify that threading support should be disabled for the system.
869 This is an alias for @option{--enable-threads=single}.
871 @item --enable-threads=@var{lib}
873 @var{lib} is the thread support library. This affects the Objective-C
874 compiler and runtime library, and exception handling for other languages
875 like C++ and Java. The possibilities for @var{lib} are:
883 Ada tasking support. For non-Ada programs, this setting is equivalent
884 to @samp{single}. When used in conjunction with the Ada run time, it
885 causes GCC to use the same thread primitives as Ada uses. This option
886 is necessary when using both Ada and the back end exception handling,
887 which is the default for most Ada targets.
889 Generic MACH thread support, known to work on NeXTSTEP@. (Please note
890 that the file needed to support this configuration, @file{gthr-mach.h}, is
891 missing and thus this setting will cause a known bootstrap failure.)
893 This is an alias for @samp{single}.
895 Generic POSIX thread support.
897 RTEMS thread support.
899 Disable thread support, should work for all platforms.
901 Sun Solaris 2 thread support.
903 VxWorks thread support.
905 Microsoft Win32 API thread support.
908 @item --with-cpu=@var{cpu}
909 Specify which cpu variant the compiler should generate code for by default.
910 @var{cpu} will be used as the default value of the @option{-mcpu=} switch.
911 This option is only supported on some targets, including ARM, i386, PowerPC,
914 @item --with-schedule=@var{cpu}
915 @itemx --with-arch=@var{cpu}
916 @itemx --with-tune=@var{cpu}
917 @itemx --with-abi=@var{abi}
918 @itemx --with-float=@var{type}
919 These configure options provide default values for the @option{-mschedule=},
920 @option{-march=}, @option{-mtune=}, and @option{-mabi=} options and for
921 @option{-mhard-float} or @option{-msoft-float}. As with @option{--with-cpu},
922 which switches will be accepted and acceptable values of the arguments depend
925 @item --enable-altivec
926 Specify that the target supports AltiVec vector enhancements. This
927 option will adjust the ABI for AltiVec enhancements, as well as generate
928 AltiVec code when appropriate. This option is only available for
931 @item --enable-target-optspace
933 libraries should be optimized for code space instead of code speed.
934 This is the default for the m32r platform.
937 Specify that a user visible @command{cpp} program should not be installed.
939 @item --with-cpp-install-dir=@var{dirname}
940 Specify that the user visible @command{cpp} program should be installed
941 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
943 @item --enable-initfini-array
944 Force the use of sections @code{.init_array} and @code{.fini_array}
945 (instead of @code{.init} and @code{.fini}) for constructors and
946 destructors. Option @option{--disable-initfini-array} has the
947 opposite effect. If neither option is specified, the configure script
948 will try to guess whether the @code{.init_array} and
949 @code{.fini_array} sections are supported and, if they are, use them.
951 @item --enable-maintainer-mode
953 regenerate the GCC master message catalog @file{gcc.pot} are normally
954 disabled. This is because it can only be rebuilt if the complete source
955 tree is present. If you have changed the sources and want to rebuild the
956 catalog, configuring with @option{--enable-maintainer-mode} will enable
957 this. Note that you need a recent version of the @code{gettext} tools
960 @item --enable-generated-files-in-srcdir
961 Neither the .c and .h files that are generated from bison and flex nor the
962 info manuals and man pages that are built from the .texi files are present
963 in the CVS development tree. When building GCC from that development tree,
964 or from a snapshot which are created from CVS, then those generated files
965 are placed in your build directory, which allows for the source to be in a
968 If you configure with @option{--enable-generated-files-in-srcdir} then those
969 generated files will go into the source directory. This is mainly intended
970 for generating release or prerelease tarballs of the GCC sources, since it
971 is not a requirement that the users of source releases to have flex, bison, or
974 @item --enable-version-specific-runtime-libs
976 that runtime libraries should be installed in the compiler specific
977 subdirectory (@file{@var{libdir}/gcc}) rather than the usual places. In
978 addition, @samp{libstdc++}'s include files will be installed into
979 @file{@var{libdir}} unless you overruled it by using
980 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
981 particularly useful if you intend to use several versions of GCC in
982 parallel. This is currently supported by @samp{libf2c} and
983 @samp{libstdc++}, and is the default for @samp{libobjc} which cannot be
984 changed in this case.
986 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
987 Specify that only a particular subset of compilers and
988 their runtime libraries should be built. For a list of valid values for
989 @var{langN} you can issue the following command in the
990 @file{gcc} directory of your GCC source tree:@*
992 grep language= */config-lang.in
994 Currently, you can use any of the following:
995 @code{ada}, @code{c}, @code{c++}, @code{f77}, @code{java}, @code{objc}.
996 Building the Ada compiler has special requirements, see below.@*
997 If you do not pass this flag, all languages available in the @file{gcc}
998 sub-tree will be configured. Re-defining @code{LANGUAGES} when calling
999 @samp{make bootstrap} @strong{does not} work anymore, as those
1000 language sub-directories might not have been configured!
1002 @item --disable-libgcj
1003 Specify that the run-time libraries
1004 used by GCJ should not be built. This is useful in case you intend
1005 to use GCJ with some other run-time, or you're going to install it
1006 separately, or it just happens not to build on your particular
1007 machine. In general, if the Java front end is enabled, the GCJ
1008 libraries will be enabled too, unless they're known to not work on
1009 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
1010 may need to port it; in this case, before modifying the top-level
1011 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
1012 you may use @option{--enable-libgcj} to override the default.
1015 Specify that the compiler should
1016 use DWARF 2 debugging information as the default.
1018 @item --enable-win32-registry
1019 @itemx --enable-win32-registry=@var{key}
1020 @itemx --disable-win32-registry
1021 The @option{--enable-win32-registry} option enables Windows-hosted GCC
1022 to look up installations paths in the registry using the following key:
1025 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
1028 @var{key} defaults to GCC version number, and can be overridden by the
1029 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
1030 who use custom installers are encouraged to provide a different key,
1031 perhaps one comprised of vendor name and GCC version number, to
1032 avoid conflict with existing installations. This feature is enabled
1033 by default, and can be disabled by @option{--disable-win32-registry}
1034 option. This option has no effect on the other hosts.
1037 Specify that the machine does not have a floating point unit. This
1038 option only applies to @samp{m68k-sun-sunos@var{n}}. On any other
1039 system, @option{--nfp} has no effect.
1041 @item --enable-werror
1042 @itemx --disable-werror
1043 @itemx --enable-werror=yes
1044 @itemx --enable-werror=no
1045 When you specify this option, it controls whether certain files in the
1046 compiler are built with @option{-Werror} in bootstrap stage2 and later.
1047 If you don't specify it, @option{-Werror} is turned on for the main
1048 development trunk. However it defaults to off for release branches and
1049 final releases. The specific files which get @option{-Werror} are
1050 controlled by the Makefiles.
1052 @item --enable-checking
1053 @itemx --enable-checking=@var{list}
1054 When you specify this option, the compiler is built to perform checking
1055 of tree node types when referencing fields of that node, and some other
1056 internal consistency checks. This does not change the generated code,
1057 but adds error checking within the compiler. This will slow down the
1058 compiler and may only work properly if you are building the compiler
1059 with GCC@. This is on by default when building from CVS or snapshots,
1060 but off for releases. More control over the checks may be had by
1061 specifying @var{list}; the categories of checks available are
1062 @samp{misc}, @samp{tree}, @samp{gc}, @samp{rtl}, @samp{rtlflag},
1063 @samp{fold}, @samp{gcac} and @samp{valgrind}. The check @samp{valgrind}
1064 requires the external @command{valgrind} simulator, available from
1065 @uref{http://developer.kde.org/~sewardj/}. The default when @var{list} is
1066 not specified is @samp{misc,tree,gc,rtlflag}; the checks @samp{rtl},
1067 @samp{gcac} and @samp{valgrind} are very expensive.
1069 @item --enable-coverage
1070 @item --enable-coverage=@var{level}
1071 With this option, the compiler is built to collect self coverage
1072 information, every time it is run. This is for internal development
1073 purposes, and only works when the compiler is being built with gcc. The
1074 @var{level} argument controls whether the compiler is built optimized or
1075 not, values are @samp{opt} and @samp{noopt}. For coverage analysis you
1076 want to disable optimization, for performance analysis you want to
1077 enable optimization. When coverage is enabled, the default level is
1078 without optimization.
1081 @itemx --disable-nls
1082 The @option{--enable-nls} option enables Native Language Support (NLS),
1083 which lets GCC output diagnostics in languages other than American
1084 English. Native Language Support is enabled by default if not doing a
1085 canadian cross build. The @option{--disable-nls} option disables NLS@.
1087 @item --with-included-gettext
1088 If NLS is enabled, the @option{--with-included-gettext} option causes the build
1089 procedure to prefer its copy of GNU @command{gettext}.
1091 @item --with-catgets
1092 If NLS is enabled, and if the host lacks @code{gettext} but has the
1093 inferior @code{catgets} interface, the GCC build procedure normally
1094 ignores @code{catgets} and instead uses GCC's copy of the GNU
1095 @code{gettext} library. The @option{--with-catgets} option causes the
1096 build procedure to use the host's @code{catgets} in this situation.
1098 @item --with-libiconv-prefix=@var{dir}
1099 Search for libiconv header files in @file{@var{dir}/include} and
1100 libiconv library files in @file{@var{dir}/lib}.
1102 @item --with-system-zlib
1103 Use installed zlib rather than that included with GCC@. This option
1104 only applies if the Java front end is being built.
1106 @item --enable-obsolete
1107 Enable configuration for an obsoleted system. If you attempt to
1108 configure GCC for a system (build, host, or target) which has been
1109 obsoleted, and you do not specify this flag, configure will halt with an
1112 All support for systems which have been obsoleted in one release of GCC
1113 is removed entirely in the next major release, unless someone steps
1114 forward to maintain the port.
1117 Some options which only apply to building cross compilers:
1119 @item --with-sysroot
1120 @itemx --with-sysroot=@var{dir}
1121 Tells GCC to consider @var{dir} as the root of a tree that contains a
1122 (subset of) the root filesystem of the target operating system.
1123 Target system headers, libraries and run-time object files will be
1124 searched in there. The specified directory is not copied into the
1125 install tree, unlike the options @option{--with-headers} and
1126 @option{--with-libs} that this option obsoletes. The default value,
1127 in case @option{--with-sysroot} is not given an argument, is
1128 @option{$@{gcc_tooldir@}/sys-root}. If the specified directory is a
1129 subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to
1130 the GCC binaries if the installation tree is moved.
1132 @item --with-headers
1133 @itemx --with-headers=@var{dir}
1134 Deprecated in favor of @option{--with-sysroot}.
1135 Specifies that target headers are available when building a cross compiler.
1136 The @var{dir} argument specifies a directory which has the target include
1137 files. These include files will be copied into the @file{gcc} install
1138 directory. @emph{This option with the @var{dir} argument is required} when
1139 building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include}
1140 doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does
1141 pre-exist, the @var{dir} argument may be omitted. @command{fixincludes}
1142 will be run on these files to make them compatible with GCC.
1144 @item --without-headers
1145 Tells GCC not use any target headers from a libc when building a cross
1146 compiler. When crossing to GNU/Linux, you need the headers so gcc
1147 can build the exception handling for libgcc.
1148 See @uref{http://www.objsw.com/CrossGCC/,,CrossGCC} for more information
1152 @itemx --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
1153 Deprecated in favor of @option{--with-sysroot}.
1154 Specifies a list of directories which contain the target runtime
1155 libraries. These libraries will be copied into the @file{gcc} install
1156 directory. If the directory list is omitted, this option has no
1159 Specifies that @samp{newlib} is
1160 being used as the target C library. This causes @code{__eprintf} to be
1161 omitted from @file{libgcc.a} on the assumption that it will be provided by
1165 Note that each @option{--enable} option has a corresponding
1166 @option{--disable} option and that each @option{--with} option has a
1167 corresponding @option{--without} option.
1174 @uref{./index.html,,Return to the GCC Installation page}
1178 @c ***Building****************************************************************
1180 @comment node-name, next, previous, up
1181 @node Building, Testing, Configuration, Installing GCC
1187 @cindex Installing GCC: Building
1189 Now that GCC is configured, you are ready to build the compiler and
1192 We @strong{highly} recommend that GCC be built using GNU make;
1193 other versions may work, then again they might not.
1194 GNU make is required for compiling GNAT (the Ada compiler) and the Java
1197 (For example, many broken versions of make will fail if you use the
1198 recommended setup where @var{objdir} is different from @var{srcdir}.
1199 Other broken versions may recompile parts of the compiler when
1200 installing the compiler.)
1202 Some commands executed when making the compiler may fail (return a
1203 nonzero status) and be ignored by @command{make}. These failures, which
1204 are often due to files that were not found, are expected, and can safely
1207 It is normal to have compiler warnings when compiling certain files.
1208 Unless you are a GCC developer, you can generally ignore these warnings
1209 unless they cause compilation to fail. Developers should attempt to fix
1210 any warnings encountered, however they can temporarily continue past
1211 warnings-as-errors by specifying the configure flag
1212 @option{--disable-werror}.
1214 On certain old systems, defining certain environment variables such as
1215 @env{CC} can interfere with the functioning of @command{make}.
1217 If you encounter seemingly strange errors when trying to build the
1218 compiler in a directory other than the source directory, it could be
1219 because you have previously configured the compiler in the source
1220 directory. Make sure you have done all the necessary preparations.
1222 If you build GCC on a BSD system using a directory stored in an old System
1223 V file system, problems may occur in running @command{fixincludes} if the
1224 System V file system doesn't support symbolic links. These problems
1225 result in a failure to fix the declaration of @code{size_t} in
1226 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
1227 that type mismatches occur, this could be the cause.
1229 The solution is not to use such a directory for building GCC@.
1231 When building from CVS or snapshots, or if you modify parser sources,
1232 you need the Bison parser generator installed. Any version 1.25 or
1233 later should work; older versions may also work. If you do not modify
1234 parser sources, releases contain the Bison-generated files and you do
1235 not need Bison installed to build them.
1237 When building from CVS or snapshots, or if you modify Texinfo
1238 documentation, you need version 4.2 or later of Texinfo installed if you
1239 want Info documentation to be regenerated. Releases contain Info
1240 documentation pre-built for the unmodified documentation in the release.
1242 @section Building a native compiler
1244 For a native build issue the command @samp{make bootstrap}. This
1245 will build the entire GCC system, which includes the following steps:
1249 Build host tools necessary to build the compiler such as texinfo, bison,
1253 Build target tools for use by the compiler such as binutils (bfd,
1254 binutils, gas, gprof, ld, and opcodes)
1255 if they have been individually linked
1256 or moved into the top level GCC source tree before configuring.
1259 Perform a 3-stage bootstrap of the compiler.
1262 Perform a comparison test of the stage2 and stage3 compilers.
1265 Build runtime libraries using the stage3 compiler from the previous step.
1269 If you are short on disk space you might consider @samp{make
1270 bootstrap-lean} instead. This is identical to @samp{make
1271 bootstrap} except that object files from the stage1 and
1272 stage2 of the 3-stage bootstrap of the compiler are deleted as
1273 soon as they are no longer needed.
1275 If you want to save additional space during the bootstrap and in
1276 the final installation as well, you can build the compiler binaries
1277 without debugging information as in the following example. This will save
1278 roughly 40% of disk space both for the bootstrap and the final installation.
1279 (Libraries will still contain debugging information.)
1282 make CFLAGS='-O' LIBCFLAGS='-g -O2' \
1283 LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap
1286 If you wish to use non-default GCC flags when compiling the stage2 and
1287 stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing
1288 @samp{make bootstrap}. Non-default optimization flags are less well
1289 tested here than the default of @samp{-g -O2}, but should still work.
1290 In a few cases, you may find that you need to specify special flags such
1291 as @option{-msoft-float} here to complete the bootstrap; or, if the
1292 native compiler miscompiles the stage1 compiler, you may need to work
1293 around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the
1294 stage1 compiler that were miscompiled, or by using @samp{make
1295 bootstrap4} to increase the number of stages of bootstrap.
1297 If you used the flag @option{--enable-languages=@dots{}} to restrict
1298 the compilers to be built, only those you've actually enabled will be
1299 built. This will of course only build those runtime libraries, for
1300 which the particular compiler has been built. Please note,
1301 that re-defining @env{LANGUAGES} when calling @samp{make bootstrap}
1302 @strong{does not} work anymore!
1304 If the comparison of stage2 and stage3 fails, this normally indicates
1305 that the stage2 compiler has compiled GCC incorrectly, and is therefore
1306 a potentially serious bug which you should investigate and report. (On
1307 a few systems, meaningful comparison of object files is impossible; they
1308 always appear ``different''. If you encounter this problem, you will
1309 need to disable comparison in the @file{Makefile}.)
1311 @section Building a cross compiler
1313 We recommend reading the
1314 @uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ}
1315 for information about building cross compilers.
1317 When building a cross compiler, it is not generally possible to do a
1318 3-stage bootstrap of the compiler. This makes for an interesting problem
1319 as parts of GCC can only be built with GCC@.
1321 To build a cross compiler, we first recommend building and installing a
1322 native compiler. You can then use the native GCC compiler to build the
1323 cross compiler. The installed native compiler needs to be GCC version
1326 Assuming you have already installed a native copy of GCC and configured
1327 your cross compiler, issue the command @command{make}, which performs the
1332 Build host tools necessary to build the compiler such as texinfo, bison,
1336 Build target tools for use by the compiler such as binutils (bfd,
1337 binutils, gas, gprof, ld, and opcodes)
1338 if they have been individually linked or moved into the top level GCC source
1339 tree before configuring.
1342 Build the compiler (single stage only).
1345 Build runtime libraries using the compiler from the previous step.
1348 Note that if an error occurs in any step the make process will exit.
1350 If you are not building GNU binutils in the same source tree as GCC,
1351 you will need a cross-assembler and cross-linker installed before
1352 configuring GCC@. Put them in the directory
1353 @file{@var{prefix}/@var{target}/bin}. Here is a table of the tools
1354 you should put in this directory:
1358 This should be the cross-assembler.
1361 This should be the cross-linker.
1364 This should be the cross-archiver: a program which can manipulate
1365 archive files (linker libraries) in the target machine's format.
1368 This should be a program to construct a symbol table in an archive file.
1371 The installation of GCC will find these programs in that directory,
1372 and copy or link them to the proper place to for the cross-compiler to
1373 find them when run later.
1375 The easiest way to provide these files is to build the Binutils package.
1376 Configure it with the same @option{--host} and @option{--target}
1377 options that you use for configuring GCC, then build and install
1378 them. They install their executables automatically into the proper
1379 directory. Alas, they do not support all the targets that GCC
1382 If you are not building a C library in the same source tree as GCC,
1383 you should also provide the target libraries and headers before
1384 configuring GCC, specifying the directories with
1385 @option{--with-sysroot} or @option{--with-headers} and
1386 @option{--with-libs}. Many targets also require ``start files'' such
1387 as @file{crt0.o} and
1388 @file{crtn.o} which are linked into each executable. There may be several
1389 alternatives for @file{crt0.o}, for use with profiling or other
1390 compilation options. Check your target's definition of
1391 @code{STARTFILE_SPEC} to find out what start files it uses.
1393 @section Building in parallel
1395 You can use @samp{make bootstrap MAKE="make -j 2" -j 2}, or just
1396 @samp{make -j 2 bootstrap} for GNU Make 3.79 and above, instead of
1397 @samp{make bootstrap} to build GCC in parallel.
1398 You can also specify a bigger number, and in most cases using a value
1399 greater than the number of processors in your machine will result in
1400 fewer and shorter I/O latency hits, thus improving overall throughput;
1401 this is especially true for slow drives and network filesystems.
1403 @section Building the Ada compiler
1405 In order to build GNAT, the Ada compiler, you need a working GNAT
1406 compiler (GNAT version 3.14 or later, or GCC version 3.1 or later),
1407 since the Ada front end is written in Ada (with some
1408 GNAT-specific extensions), and GNU make.
1410 However, you do not need a full installation of GNAT, just the GNAT
1411 binary @file{gnat1}, a copy of @file{gnatbind}, and a compiler driver
1412 which can deal with Ada input (by invoking the @file{gnat1} binary).
1413 You can specify this compiler driver by setting the @env{ADAC}
1414 environment variable at the configure step. @command{configure} can
1415 detect the driver automatically if it has got a common name such as
1416 @command{gcc} or @command{gnatgcc}. Of course, you still need a working
1417 C compiler (the compiler driver can be different or not).
1418 @command{configure} does not test whether the GNAT installation works
1419 and has a sufficiently recent version; if too old a GNAT version is
1420 installed, the build will fail unless @option{--enable-languages} is
1421 used to disable building the Ada front end.
1423 Additional build tools (such as @command{gnatmake}) or a working GNAT
1424 run-time library installation are usually @emph{not} required. However,
1425 if you want to bootstrap the compiler using a minimal version of GNAT,
1426 you have to issue the following commands before invoking @samp{make
1427 bootstrap} (this assumes that you start with an unmodified and consistent
1428 source distribution):
1431 cd @var{srcdir}/gcc/ada
1432 touch treeprs.ads [es]info.h nmake.ad[bs]
1435 At the moment, the GNAT library and several tools for GNAT are not built
1436 by @samp{make bootstrap}. For a native build, you have to invoke
1437 @samp{make gnatlib_and_tools} in the @file{@var{objdir}/gcc}
1438 subdirectory before proceeding with the next steps.
1439 For a cross build, you need to invoke
1440 @samp{make gnatlib cross-gnattools ada.all.cross}. For a canadian
1441 cross you only need to invoke @samp{make cross-gnattools}; the GNAT
1442 library would be the same as the one built for the cross compiler.
1444 For example, you can build a native Ada compiler by issuing the
1445 following commands (assuming @command{make} is GNU make):
1449 @var{srcdir}/configure --enable-languages=c,ada
1450 cd @var{srcdir}/gcc/ada
1451 touch treeprs.ads [es]info.h nmake.ad[bs]
1455 make gnatlib_and_tools
1459 Currently, when compiling the Ada front end, you cannot use the parallel
1460 build feature described in the previous section.
1462 @section Building with profile feedback
1464 It is possible to use profile feedback to optimize the compiler itself. This
1465 should result in a faster compiler binary. Experiments done on x86 using gcc
1466 3.3 showed approximately 7 percent speedup on compiling C programs. To
1467 bootstrap compiler with profile feedback, use @code{make profiledbootstrap}.
1469 When @samp{make profiledbootstrap} is run, it will first build a @code{stage1}
1470 compiler. This compiler is used to build a @code{stageprofile} compiler
1471 instrumented to collect execution counts of instruction and branch
1472 probabilities. Then runtime libraries are compiled with profile collected.
1473 Finally a @code{stagefeedback} compiler is built using the information collected.
1475 Unlike @samp{make bootstrap} several additional restrictions apply. The
1476 compiler used to build @code{stage1} needs to support a 64-bit integral type.
1477 It is recommended to only use GCC for this. Also parallel make is currently
1478 not supported since collisions in profile collecting may occur.
1485 @uref{./index.html,,Return to the GCC Installation page}
1489 @c ***Testing*****************************************************************
1491 @comment node-name, next, previous, up
1492 @node Testing, Final install, Building, Installing GCC
1496 @chapter Installing GCC: Testing
1499 @cindex Installing GCC: Testing
1502 Before you install GCC, we encourage you to run the testsuites and to
1503 compare your results with results from a similar configuration that have
1504 been submitted to the
1505 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
1506 Some of these archived results are linked from the build status lists
1507 at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who
1508 reports a successful build runs the testsuites and submits the results.
1509 This step is optional and may require you to download additional software,
1510 but it can give you confidence in your new GCC installation or point out
1511 problems before you install and start using your new GCC.
1513 First, you must have @uref{download.html,,downloaded the testsuites}.
1514 These are part of the full distribution, but if you downloaded the
1515 ``core'' compiler plus any front ends, you must download the testsuites
1518 Second, you must have the testing tools installed. This includes
1519 @uref{http://www.gnu.org/software/dejagnu/,,DejaGnu} 1.4.1 or 1.4.3
1520 and later, Tcl, and Expect; the DejaGnu site has links to these.
1522 If the directories where @command{runtest} and @command{expect} were
1523 installed are not in the @env{PATH}, you may need to set the following
1524 environment variables appropriately, as in the following example (which
1525 assumes that DejaGnu has been installed under @file{/usr/local}):
1528 TCL_LIBRARY = /usr/local/share/tcl8.0
1529 DEJAGNULIBS = /usr/local/share/dejagnu
1532 (On systems such as Cygwin, these paths are required to be actual
1533 paths, not mounts or links; presumably this is due to some lack of
1534 portability in the DejaGnu code.)
1537 Finally, you can run the testsuite (which may take a long time):
1539 cd @var{objdir}; make -k check
1542 This will test various components of GCC, such as compiler
1543 front ends and runtime libraries. While running the testsuite, DejaGnu
1544 might emit some harmless messages resembling
1545 @samp{WARNING: Couldn't find the global config file.} or
1546 @samp{WARNING: Couldn't find tool init file} that can be ignored.
1548 @section How can I run the test suite on selected tests?
1550 In order to run sets of tests selectively, there are targets
1551 @samp{make check-gcc} and @samp{make check-g++}
1552 in the @file{gcc} subdirectory of the object directory. You can also
1553 just run @samp{make check} in a subdirectory of the object directory.
1556 A more selective way to just run all @command{gcc} execute tests in the
1560 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
1563 Likewise, in order to run only the @command{g++} ``old-deja'' tests in
1564 the testsuite with filenames matching @samp{9805*}, you would use
1567 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
1570 The @file{*.exp} files are located in the testsuite directories of the GCC
1571 source, the most important ones being @file{compile.exp},
1572 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
1573 To get a list of the possible @file{*.exp} files, pipe the
1574 output of @samp{make check} into a file and look at the
1575 @samp{Running @dots{} .exp} lines.
1577 @section Passing options and running multiple testsuites
1579 You can pass multiple options to the testsuite using the
1580 @samp{--target_board} option of DejaGNU, either passed as part of
1581 @samp{RUNTESTFLAGS}, or directly to @command{runtest} if you prefer to
1582 work outside the makefiles. For example,
1585 make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fno-strength-reduce"
1588 will run the standard @command{g++} testsuites (``unix'' is the target name
1589 for a standard native testsuite situation), passing
1590 @samp{-O3 -fno-strength-reduce} to the compiler on every test, i.e.,
1591 slashes separate options.
1593 You can run the testsuites multiple times using combinations of options
1594 with a syntax similar to the brace expansion of popular shells:
1597 @dots{}"--target_board=arm-sim@{-mhard-float,-msoft-float@}@{-O1,-O2,-O3,@}"
1600 (Note the empty option caused by the trailing comma in the final group.)
1601 The following will run each testsuite eight times using the @samp{arm-sim}
1602 target, as if you had specified all possible combinations yourself:
1605 --target_board=arm-sim/-mhard-float/-O1
1606 --target_board=arm-sim/-mhard-float/-O2
1607 --target_board=arm-sim/-mhard-float/-O3
1608 --target_board=arm-sim/-mhard-float
1609 --target_board=arm-sim/-msoft-float/-O1
1610 --target_board=arm-sim/-msoft-float/-O2
1611 --target_board=arm-sim/-msoft-float/-O3
1612 --target_board=arm-sim/-msoft-float
1615 They can be combined as many times as you wish, in arbitrary ways. This
1619 @dots{}"--target_board=unix/-Wextra@{-O3,-fno-strength-reduce@}@{-fomit-frame-pointer,@}"
1622 will generate four combinations, all involving @samp{-Wextra}.
1624 The disadvantage to this method is that the testsuites are run in serial,
1625 which is a waste on multiprocessor systems. For users with GNU Make and
1626 a shell which performs brace expansion, you can run the testsuites in
1627 parallel by having the shell perform the combinations and @command{make}
1628 do the parallel runs. Instead of using @samp{--target_board}, use a
1629 special makefile target:
1632 make -j@var{N} check-@var{testsuite}//@var{test-target}/@var{option1}/@var{option2}/@dots{}
1638 make -j3 check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@}
1641 will run three concurrent ``make-gcc'' testsuites, eventually testing all
1642 ten combinations as described above. Note that this is currently only
1643 supported in the @file{gcc} subdirectory. (To see how this works, try
1644 typing @command{echo} before the example given here.)
1647 @section Additional testing for Java Class Libraries
1649 The Java runtime tests can be executed via @samp{make check}
1650 in the @file{@var{target}/libjava/testsuite} directory in
1653 The @uref{http://sources.redhat.com/mauve/,,Mauve Project} provides
1654 a suite of tests for the Java Class Libraries. This suite can be run
1655 as part of libgcj testing by placing the Mauve tree within the libjava
1656 testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by
1657 specifying the location of that tree when invoking @samp{make}, as in
1658 @samp{make MAUVEDIR=~/mauve check}.
1660 @uref{http://www-124.ibm.com/developerworks/oss/cvs/jikes/~checkout~/jacks/jacks.html,,Jacks}
1661 is a free test suite that tests Java compiler front ends. This suite
1662 can be run as part of libgcj testing by placing the Jacks tree within
1663 the libjava testsuite at @file{libjava/testsuite/libjava.jacks/jacks}.
1665 @section How to interpret test results
1667 The result of running the testsuite are various @file{*.sum} and @file{*.log}
1668 files in the testsuite subdirectories. The @file{*.log} files contain a
1669 detailed log of the compiler invocations and the corresponding
1670 results, the @file{*.sum} files summarize the results. These summaries
1671 contain status codes for all tests:
1675 PASS: the test passed as expected
1677 XPASS: the test unexpectedly passed
1679 FAIL: the test unexpectedly failed
1681 XFAIL: the test failed as expected
1683 UNSUPPORTED: the test is not supported on this platform
1685 ERROR: the testsuite detected an error
1687 WARNING: the testsuite detected a possible problem
1690 It is normal for some tests to report unexpected failures. At the
1691 current time our testing harness does not allow fine grained control
1692 over whether or not a test is expected to fail. We expect to fix this
1693 problem in future releases.
1696 @section Submitting test results
1698 If you want to report the results to the GCC project, use the
1699 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
1702 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
1703 -m gcc-testresults@@gcc.gnu.org |sh
1706 This script uses the @command{Mail} program to send the results, so
1707 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
1708 prepended to the testsuite summary and should contain any special
1709 remarks you have on your results or your build environment. Please
1710 do not edit the testsuite result block or the subject line, as these
1711 messages may be automatically processed.
1718 @uref{./index.html,,Return to the GCC Installation page}
1722 @c ***Final install***********************************************************
1724 @comment node-name, next, previous, up
1725 @node Final install, , Testing, Installing GCC
1727 @ifset finalinstallhtml
1729 @chapter Installing GCC: Final installation
1732 Now that GCC has been built (and optionally tested), you can install it with
1734 cd @var{objdir}; make install
1737 We strongly recommend to install into a target directory where there is
1738 no previous version of GCC present.
1740 That step completes the installation of GCC; user level binaries can
1741 be found in @file{@var{prefix}/bin} where @var{prefix} is the value
1742 you specified with the @option{--prefix} to configure (or
1743 @file{/usr/local} by default). (If you specified @option{--bindir},
1744 that directory will be used instead; otherwise, if you specified
1745 @option{--exec-prefix}, @file{@var{exec-prefix}/bin} will be used.)
1746 Headers for the C++ and Java libraries are installed in
1747 @file{@var{prefix}/include}; libraries in @file{@var{libdir}}
1748 (normally @file{@var{prefix}/lib}); internal parts of the compiler in
1749 @file{@var{libdir}/gcc} and @file{@var{libexecdir}/gcc}; documentation
1750 in info format in @file{@var{infodir}} (normally
1751 @file{@var{prefix}/info}).
1753 When installing cross-compilers, GCC's executables
1754 are not only installed into @file{@var{bindir}}, that
1755 is, @file{@var{exec-prefix}/bin}, but additionally into
1756 @file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory
1757 exists. Typically, such @dfn{tooldirs} hold target-specific
1758 binutils, including assembler and linker.
1760 Installation into a temporary staging area or into a @command{chroot}
1761 jail can be achieved with the command
1764 make DESTDIR=@var{path-to-rootdir} install
1767 @noindent where @var{path-to-rootdir} is the absolute path of
1768 a directory relative to which all installation paths will be
1769 interpreted. Note that the directory specified by @code{DESTDIR}
1770 need not exist yet; it will be created if necessary.
1772 There is a subtle point with tooldirs and @code{DESTDIR}:
1773 If you relocate a cross-compiler installation with
1774 e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory
1775 @file{@var{rootdir}/@var{exec-prefix}/@var{target-alias}/bin} will
1776 be filled with duplicated GCC executables only if it already exists,
1777 it will not be created otherwise. This is regarded as a feature,
1778 not as a bug, because it gives slightly more control to the packagers
1779 using the @code{DESTDIR} feature.
1781 If you built a released version of GCC using @samp{make bootstrap} then please
1782 quickly review the build status page for your release, available from
1783 @uref{http://gcc.gnu.org/buildstat.html}.
1784 If your system is not listed for the version of GCC that you built,
1786 @email{gcc@@gcc.gnu.org} indicating
1787 that you successfully built and installed GCC.
1788 Include the following information:
1792 Output from running @file{@var{srcdir}/config.guess}. Do not send us
1793 that file itself, just the one-line output from running it.
1796 The output of @samp{gcc -v} for your newly installed gcc.
1797 This tells us which version of GCC you built and the options you passed to
1801 Whether you enabled all languages or a subset of them. If you used a
1802 full distribution then this information is part of the configure
1803 options in the output of @samp{gcc -v}, but if you downloaded the
1804 ``core'' compiler plus additional front ends then it isn't apparent
1805 which ones you built unless you tell us about it.
1808 If the build was for GNU/Linux, also include:
1811 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
1812 this information should be available from @file{/etc/issue}.
1815 The version of the Linux kernel, available from @samp{uname --version}
1819 The version of glibc you used; for RPM-based systems like Red Hat,
1820 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
1821 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
1823 For other systems, you can include similar information if you think it is
1827 Any other information that you think would be useful to people building
1828 GCC on the same configuration. The new entry in the build status list
1829 will include a link to the archived copy of your message.
1832 We'd also like to know if the
1834 @ref{Specific, host/target specific installation notes}
1837 @uref{specific.html,,host/target specific installation notes}
1839 didn't include your host/target information or if that information is
1840 incomplete or out of date. Send a note to
1841 @email{gcc@@gcc.gnu.org} telling us how the information should be changed.
1843 If you find a bug, please report it following our
1844 @uref{../bugs.html,,bug reporting guidelines}.
1846 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
1847 dvi}. You will need to have @command{texi2dvi} (version at least 4.2)
1848 and @TeX{} installed. This creates a number of @file{.dvi} files in
1849 subdirectories of @file{@var{objdir}}; these may be converted for
1850 printing with programs such as @command{dvips}. You can also
1851 @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the
1852 Free Software Foundation}, though such manuals may not be for the most
1853 recent version of GCC@.
1860 @uref{./index.html,,Return to the GCC Installation page}
1864 @c ***Binaries****************************************************************
1866 @comment node-name, next, previous, up
1867 @node Binaries, Specific, Installing GCC, Top
1871 @chapter Installing GCC: Binaries
1874 @cindex Installing GCC: Binaries
1876 We are often asked about pre-compiled versions of GCC@. While we cannot
1877 provide these for all platforms, below you'll find links to binaries for
1878 various platforms where creating them by yourself is not easy due to various
1881 Please note that we did not create these binaries, nor do we
1882 support them. If you have any problems installing them, please
1883 contact their makers.
1890 @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX};
1893 @uref{http://aixpdslib.seas.ucla.edu,,UCLA Software Library for AIX}.
1897 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}.
1900 Renesas H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
1901 Development Tools for the Renesas H8/300[HS] Series}.
1907 @uref{http://hpux.cae.wisc.edu/,,HP-UX Porting Center};
1910 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
1914 Motorola 68HC11/68HC12---@uref{http://www.gnu-m68hc11.org,,GNU
1915 Development Tools for the Motorola 68HC11/68HC12}.
1918 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
1919 OpenServer/Unixware}.
1922 Sinix/Reliant Unix---@uref{ftp://ftp.fujitsu-siemens.com/pub/pd/gnu/gcc/,,Siemens}.
1925 Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware}.
1928 SGI---@uref{http://freeware.sgi.com/,,SGI Freeware}.
1934 The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project;
1936 The @uref{http://www.mingw.org/,,MinGW} project.
1940 @uref{ftp://ftp.thewrittenword.com/packages/by-name/,,The
1941 Written Word} offers binaries for
1944 Digital UNIX 4.0D and 5.1,
1946 HP-UX 10.20, 11.00, and 11.11, and
1947 Solaris/SPARC 2.5.1, 2.6, 2.7, 8, and 9,
1950 In addition to those specific offerings, you can get a binary
1951 distribution CD-ROM from the
1952 @uref{http://www.fsf.org/order/order.html,,Free Software Foundation}.
1953 It contains binaries for a number of platforms, and
1954 includes not only GCC, but other stuff as well. The current CD does
1955 not contain the latest version of GCC, but it should allow
1956 bootstrapping the compiler. An updated version of that disk is in the
1964 @uref{./index.html,,Return to the GCC Installation page}
1968 @c ***Specific****************************************************************
1970 @comment node-name, next, previous, up
1971 @node Specific, Old, Binaries, Top
1975 @chapter Host/target specific installation notes for GCC
1978 @cindex Specific installation notes
1979 @cindex Target specific installation
1980 @cindex Host specific installation
1981 @cindex Target specific installation notes
1983 Please read this document carefully @emph{before} installing the
1984 GNU Compiler Collection on your machine.
1989 @uref{#alpha*-*-*,,alpha*-*-*}
1991 @uref{#alpha*-dec-osf*,,alpha*-dec-osf*}
1993 @uref{#alphaev5-cray-unicosmk*,,alphaev5-cray-unicosmk*}
1995 @uref{#arc-*-elf,,arc-*-elf}
1997 @uref{#arm-*-elf,,arm-*-elf}
1998 @uref{#arm-*-coff,,arm-*-coff}
1999 @uref{#arm-*-aout,,arm-*-aout}
2001 @uref{#xscale-*-*,,xscale-*-*}
2009 @uref{#dsp16xx,,dsp16xx}
2011 @uref{#*-*-freebsd*,,*-*-freebsd*}
2013 @uref{#h8300-hms,,h8300-hms}
2015 @uref{#hppa*-hp-hpux*,,hppa*-hp-hpux*}
2017 @uref{#hppa*-hp-hpux10,,hppa*-hp-hpux10}
2019 @uref{#hppa*-hp-hpux11,,hppa*-hp-hpux11}
2021 @uref{#i370-*-*,,i370-*-*}
2023 @uref{#*-*-linux-gnu,,*-*-linux-gnu}
2025 @uref{#ix86-*-linux*aout,,i?86-*-linux*aout}
2027 @uref{#ix86-*-linux*,,i?86-*-linux*}
2029 @uref{#ix86-*-sco3.2v5*,,i?86-*-sco3.2v5*}
2031 @uref{#ix86-*-udk,,i?86-*-udk}
2033 @uref{#ix86-*-esix,,i?86-*-esix}
2035 @uref{#ia64-*-linux,,ia64-*-linux}
2037 @uref{#ia64-*-hpux*,,ia64-*-hpux*}
2039 @uref{#*-ibm-aix*,,*-ibm-aix*}
2041 @uref{#ip2k-*-elf,,ip2k-*-elf}
2043 @uref{#iq2000-*-elf,,iq2000-*-elf}
2045 @uref{#m32r-*-elf,,m32r-*-elf}
2047 @uref{#m6811-elf,,m6811-elf}
2049 @uref{#m6812-elf,,m6812-elf}
2051 @uref{#m68k-hp-hpux,,m68k-hp-hpux}
2053 @uref{#mips-*-*,,mips-*-*}
2055 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
2057 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
2059 @uref{#powerpc*-*-*,,powerpc*-*-*, powerpc-*-sysv4}
2061 @uref{#powerpc-*-darwin*,,powerpc-*-darwin*}
2063 @uref{#powerpc-*-elf,,powerpc-*-elf, powerpc-*-sysv4}
2065 @uref{#powerpc-*-linux-gnu*,,powerpc-*-linux-gnu*}
2067 @uref{#powerpc-*-netbsd*,,powerpc-*-netbsd*}
2069 @uref{#powerpc-*-eabiaix,,powerpc-*-eabiaix}
2071 @uref{#powerpc-*-eabisim,,powerpc-*-eabisim}
2073 @uref{#powerpc-*-eabi,,powerpc-*-eabi}
2075 @uref{#powerpcle-*-elf,,powerpcle-*-elf, powerpcle-*-sysv4}
2077 @uref{#powerpcle-*-eabisim,,powerpcle-*-eabisim}
2079 @uref{#powerpcle-*-eabi,,powerpcle-*-eabi}
2081 @uref{#s390-*-linux*,,s390-*-linux*}
2083 @uref{#s390x-*-linux*,,s390x-*-linux*}
2085 @uref{#s390x-ibm-tpf*,,s390x-ibm-tpf*}
2087 @uref{#*-*-solaris2*,,*-*-solaris2*}
2089 @uref{#sparc-sun-solaris2*,,sparc-sun-solaris2*}
2091 @uref{#sparc-sun-solaris2.7,,sparc-sun-solaris2.7}
2093 @uref{#sparc-*-linux*,,sparc-*-linux*}
2095 @uref{#sparc64-*-solaris2*,,sparc64-*-solaris2*}
2097 @uref{#sparcv9-*-solaris2*,,sparcv9-*-solaris2*}
2099 @uref{#*-*-sysv*,,*-*-sysv*}
2101 @uref{#vax-dec-ultrix,,vax-dec-ultrix}
2103 @uref{#*-*-vxworks*,,*-*-vxworks*}
2105 @uref{#xtensa-*-elf,,xtensa-*-elf}
2107 @uref{#xtensa-*-linux*,,xtensa-*-linux*}
2109 @uref{#windows,,Microsoft Windows}
2113 @uref{#older,,Older systems}
2118 @uref{#elf_targets,,all ELF targets} (SVR4, Solaris 2, etc.)
2124 <!-- -------- host/target specific issues start here ---------------- -->
2127 @heading @anchor{alpha*-*-*}alpha*-*-*
2129 This section contains general configuration information for all
2130 alpha-based platforms using ELF (in particular, ignore this section for
2131 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
2132 section, please read all other sections that match your target.
2134 We require binutils 2.11.2 or newer.
2135 Previous binutils releases had a number of problems with DWARF 2
2136 debugging information, not the least of which is incorrect linking of
2142 @heading @anchor{alpha*-dec-osf*}alpha*-dec-osf*
2143 Systems using processors that implement the DEC Alpha architecture and
2144 are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
2145 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
2147 As of GCC 3.2, versions before @code{alpha*-dec-osf4} are no longer
2148 supported. (These are the versions which identify themselves as DEC
2151 In Digital Unix V4.0, virtual memory exhausted bootstrap failures
2152 may be fixed by configuring with @option{--with-gc=simple},
2153 reconfiguring Kernel Virtual Memory and Swap parameters
2154 per the @command{/usr/sbin/sys_check} Tuning Suggestions,
2155 or applying the patch in
2156 @uref{http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html}.
2158 In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
2159 currently (2001-06-13) work with @command{mips-tfile}. As a workaround,
2160 we need to use the old assembler, invoked via the barely documented
2161 @option{-oldas} option. To bootstrap GCC, you either need to use the
2165 % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
2168 or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
2171 % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
2174 As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld}
2175 are supported on Tru64 UNIX, so you must not configure GCC with
2176 @option{--with-gnu-as} or @option{--with-gnu-ld}.
2178 GCC writes a @samp{.verstamp} directive to the assembler output file
2179 unless it is built as a cross-compiler. It gets the version to use from
2180 the system header file @file{/usr/include/stamp.h}. If you install a
2181 new version of DEC Unix, you should rebuild GCC to pick up the new version
2184 Note that since the Alpha is a 64-bit architecture, cross-compilers from
2185 32-bit machines will not generate code as efficient as that generated
2186 when the compiler is running on a 64-bit machine because many
2187 optimizations that depend on being able to represent a word on the
2188 target in an integral value on the host cannot be performed. Building
2189 cross-compilers on the Alpha for 32-bit machines has only been tested in
2190 a few cases and may not work properly.
2192 @samp{make compare} may fail on old versions of DEC Unix unless you add
2193 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
2194 assembler input file is stored in the object file, and that makes
2195 comparison fail if it differs between the @code{stage1} and
2196 @code{stage2} compilations. The option @option{-save-temps} forces a
2197 fixed name to be used for the assembler input file, instead of a
2198 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
2199 unless the comparisons fail without that option. If you add
2200 @option{-save-temps}, you will have to manually delete the @samp{.i} and
2201 @samp{.s} files after each series of compilations.
2203 GCC now supports both the native (ECOFF) debugging format used by DBX
2204 and GDB and an encapsulated STABS format for use only with GDB@. See the
2205 discussion of the @option{--with-stabs} option of @file{configure} above
2206 for more information on these formats and how to select them.
2208 There is a bug in DEC's assembler that produces incorrect line numbers
2209 for ECOFF format when the @samp{.align} directive is used. To work
2210 around this problem, GCC will not emit such alignment directives
2211 while writing ECOFF format debugging information even if optimization is
2212 being performed. Unfortunately, this has the very undesirable
2213 side-effect that code addresses when @option{-O} is specified are
2214 different depending on whether or not @option{-g} is also specified.
2216 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
2217 DBX@. DEC is now aware of this problem with the assembler and hopes to
2218 provide a fix shortly.
2223 @heading @anchor{alphaev5-cray-unicosmk*}alphaev5-cray-unicosmk*
2224 Cray T3E systems running Unicos/Mk.
2226 This port is incomplete and has many known bugs. We hope to improve the
2227 support for this target soon. Currently, only the C front end is supported,
2228 and it is not possible to build parallel applications. Cray modules are not
2229 supported; in particular, Craylibs are assumed to be in
2230 @file{/opt/ctl/craylibs/craylibs}.
2232 You absolutely @strong{must} use GNU make on this platform. Also, you
2233 need to tell GCC where to find the assembler and the linker. The
2234 simplest way to do so is by providing @option{--with-as} and
2235 @option{--with-ld} to @file{configure}, e.g.@:
2238 configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld \
2239 --enable-languages=c
2242 The comparison test during @samp{make bootstrap} fails on Unicos/Mk
2243 because the assembler inserts timestamps into object files. You should
2244 be able to work around this by doing @samp{make all} after getting this
2250 @heading @anchor{arc-*-elf}arc-*-elf
2251 Argonaut ARC processor.
2252 This configuration is intended for embedded systems.
2257 @heading @anchor{arm-*-elf}arm-*-elf
2258 @heading @anchor{xscale-*-*}xscale-*-*
2259 ARM-family processors. Subtargets that use the ELF object format
2260 require GNU binutils 2.13 or newer. Such subtargets include:
2261 @code{arm-*-freebsd}, @code{arm-*-netbsdelf}, @code{arm-*-*linux},
2262 @code{arm-*-rtems} and @code{arm-*-kaos}.
2267 @heading @anchor{arm-*-coff}arm-*-coff
2268 ARM-family processors. Note that there are two different varieties
2269 of PE format subtarget supported: @code{arm-wince-pe} and
2270 @code{arm-pe} as well as a standard COFF target @code{arm-*-coff}.
2275 @heading @anchor{arm-*-aout}arm-*-aout
2276 ARM-family processors. These targets support the AOUT file format:
2277 @code{arm-*-aout}, @code{arm-*-netbsd}.
2282 @heading @anchor{avr}avr
2284 ATMEL AVR-family micro controllers. These are used in embedded
2285 applications. There are no standard Unix configurations.
2287 @xref{AVR Options,, AVR Options, gcc, Using and Porting the GNU Compiler
2291 See ``AVR Options'' in the main manual
2293 for the list of supported MCU types.
2295 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
2297 Further installation notes and other useful information about AVR tools
2298 can also be obtained from:
2302 @uref{http://www.openavr.org,,http://www.openavr.org}
2304 @uref{http://home.overta.ru/users/denisc/,,http://home.overta.ru/users/denisc/}
2306 @uref{http://www.amelek.gda.pl/avr/,,http://www.amelek.gda.pl/avr/}
2309 We @emph{strongly} recommend using binutils 2.13 or newer.
2311 The following error:
2313 Error: register required
2316 indicates that you should upgrade to a newer version of the binutils.
2321 @heading @anchor{c4x}c4x
2323 Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal
2324 Processors. These are used in embedded applications. There are no
2325 standard Unix configurations.
2327 @xref{TMS320C3x/C4x Options,, TMS320C3x/C4x Options, gcc, Using and
2328 Porting the GNU Compiler Collection (GCC)},
2331 See ``TMS320C3x/C4x Options'' in the main manual
2333 for the list of supported MCU types.
2335 GCC can be configured as a cross compiler for both the C3x and C4x
2336 architectures on the same system. Use @samp{configure --target=c4x
2337 --enable-languages="c,c++"} to configure.
2340 Further installation notes and other useful information about C4x tools
2341 can also be obtained from:
2345 @uref{http://www.elec.canterbury.ac.nz/c4x/,,http://www.elec.canterbury.ac.nz/c4x/}
2351 @heading @anchor{cris}CRIS
2353 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
2354 series. These are used in embedded applications.
2357 @xref{CRIS Options,, CRIS Options, gcc, Using and Porting the GNU Compiler
2361 See ``CRIS Options'' in the main manual
2363 for a list of CRIS-specific options.
2365 There are a few different CRIS targets:
2367 @item cris-axis-aout
2368 Old target. Includes a multilib for the @samp{elinux} a.out-based
2369 target. No multilibs for newer architecture variants.
2371 Mainly for monolithic embedded systems. Includes a multilib for the
2372 @samp{v10} core used in @samp{ETRAX 100 LX}.
2373 @item cris-axis-linux-gnu
2374 A GNU/Linux port for the CRIS architecture, currently targeting
2375 @samp{ETRAX 100 LX} by default.
2378 For @code{cris-axis-aout} and @code{cris-axis-elf} you need binutils 2.11
2379 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
2381 Pre-packaged tools can be obtained from
2382 @uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More
2383 information about this platform is available at
2384 @uref{http://developer.axis.com/}.
2389 @heading @anchor{dos}DOS
2391 Please have a look at our @uref{binaries.html,,binaries page}.
2393 You cannot install GCC by itself on MSDOS; it will not compile under
2394 any MSDOS compiler except itself. You need to get the complete
2395 compilation package DJGPP, which includes binaries as well as sources,
2396 and includes all the necessary compilation tools and libraries.
2401 @heading @anchor{dsp16xx}dsp16xx
2402 A port to the AT&T DSP1610 family of processors.
2407 @heading @anchor{*-*-freebsd*}*-*-freebsd*
2409 The version of binutils installed in @file{/usr/bin} is known to work unless
2410 otherwise specified in any per-architecture notes. However, binutils
2411 2.12.1 or greater is known to improve overall testsuite results.
2413 Support for FreeBSD 1 was discontinued in GCC 3.2.
2415 For FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
2416 configuration support and files as shipped with GCC 2.95 are still in
2417 place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
2418 it is unknown which version of binutils was used (it is assumed that it
2419 was the system copy in @file{/usr/bin}) and C++ EH failures were noted.
2421 For FreeBSD using the ELF file format: DWARF 2 debugging is now the
2422 default for all CPU architectures. It had been the default on
2423 FreeBSD/alpha since its inception. You may use @option{-gstabs} instead
2424 of @option{-g}, if you really want the old debugging format. There are
2425 no known issues with mixing object files and libraries with different
2426 debugging formats. Otherwise, this release of GCC should now match more
2427 of the configuration used in the stock FreeBSD configuration of GCC. In
2428 particular, @option{--enable-threads} is now configured by default.
2429 However, as a general user, do not attempt to replace the system
2430 compiler with this release. Known to bootstrap and check with good
2431 results on FreeBSD 4.8-STABLE and 5-CURRENT@. In the past, known to
2432 bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2,
2433 4.3, 4.4, 4.5-STABLE@.
2435 In principle, @option{--enable-threads} is now compatible with
2436 @option{--enable-libgcj} on FreeBSD@. However, it has only been built
2437 and tested on @samp{i386-*-freebsd[45]} and @samp{alpha-*-freebsd[45]}.
2439 library may be incorrectly built (symbols are missing at link time).
2440 There is a rare timing-based startup hang (probably involves an
2441 assumption about the thread library). Multi-threaded boehm-gc (required for
2442 libjava) exposes severe threaded signal-handling bugs on FreeBSD before
2443 4.5-RELEASE@. Other CPU architectures
2444 supported by FreeBSD will require additional configuration tuning in, at
2445 the very least, both boehm-gc and libffi.
2447 Shared @file{libgcc_s.so} is now built and installed by default.
2452 @heading @anchor{h8300-hms}h8300-hms
2453 Renesas H8/300 series of processors.
2455 Please have a look at our @uref{binaries.html,,binaries page}.
2457 The calling convention and structure layout has changed in release 2.6.
2458 All code must be recompiled. The calling convention now passes the
2459 first three arguments in function calls in registers. Structures are no
2460 longer a multiple of 2 bytes.
2465 @heading @anchor{hppa*-hp-hpux*}hppa*-hp-hpux*
2466 Support for HP-UX version 9 and older was discontinued in GCC 3.4.
2468 We @emph{highly} recommend using gas/binutils 2.8 or newer on all hppa
2469 platforms; you may encounter a variety of problems when using the HP
2472 Specifically, @option{-g} does not work on HP-UX (since that system
2473 uses a peculiar debugging format which GCC does not know about), unless you
2474 use GAS and GDB and configure GCC with the
2475 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
2476 @option{--with-as=@dots{}} options.
2478 If you wish to use the pa-risc 2.0 architecture support with a 32-bit
2479 runtime, you must use either the HP assembler, gas/binutils 2.11 or newer,
2481 @uref{ftp://sources.redhat.com/pub/binutils/snapshots,,snapshot of gas}.
2483 There are two default scheduling models for instructions. These are
2484 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
2485 architecture specified for the target machine when configuring.
2486 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
2487 the target is a @samp{hppa1*} machine.
2489 The PROCESSOR_8000 model is not well suited to older processors. Thus,
2490 it is important to completely specify the machine architecture when
2491 configuring if you want a model other than PROCESSOR_8000. The macro
2492 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
2493 default scheduling model is desired.
2495 More specific information to @samp{hppa*-hp-hpux*} targets follows.
2500 @heading @anchor{hppa*-hp-hpux10}hppa*-hp-hpux10
2502 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
2503 @code{PHCO_19798} from HP@. HP has two sites which provide patches free of
2509 <a href="http://us.itrc.hp.com/service/home/home.do">US, Canada, Asia-Pacific, and
2513 @uref{http://us.itrc.hp.com/service/home/home.do,,} US, Canada, Asia-Pacific,
2517 @uref{http://europe.itrc.hp.com/service/home/home.do,,} Europe.
2520 The HP assembler on these systems has some problems. Most notably the
2521 assembler inserts timestamps into each object file it creates, causing
2522 the 3-stage comparison test to fail during a @samp{make bootstrap}.
2523 You should be able to continue by saying @samp{make all} after getting
2524 the failure from @samp{make bootstrap}.
2530 @heading @anchor{hppa*-hp-hpux11}hppa*-hp-hpux11
2532 GCC 3.0 and up support HP-UX 11. On 64-bit capable systems, there
2533 are two distinct ports. The @samp{hppa2.0w-hp-hpux11*} port generates
2534 code for the 32-bit pa-risc runtime architecture. It uses the HP
2535 linker. The @samp{hppa64-hp-hpux11*} port generates 64-bit code for the
2536 pa-risc 2.0 architecture. The script config.guess now selects the port
2537 type based on the type compiler detected during configuration. You must
2538 set your @env{PATH} or define @env{CC} so that configure finds an appropriate
2539 compiler for the initial bootstrap. Different prefixes must be used if
2540 both ports are to be installed on the same system.
2542 It is best to explicitly configure the @samp{hppa64-hp-hpux11*} target
2543 with the @option{--with-ld=@dots{}} option. We support both the HP
2544 and GNU linkers for this target. The two linkers require different
2545 link commands. Thus, it's not possible to switch linkers during a
2546 GCC build. This has been been reported to occur in a unified build
2547 of binutils and GCC.
2549 GCC 2.95.x is not supported under HP-UX 11 and cannot be used to
2550 compile GCC 3.0 and up. Refer to @uref{binaries.html,,binaries} for
2551 information about obtaining precompiled GCC binaries for HP-UX.
2553 You must use GNU binutils 2.11 or above with the 32-bit port. Thread
2554 support is not currently implemented, so @option{--enable-threads} does
2558 @item @uref{http://gcc.gnu.org/ml/gcc-prs/2002-01/msg00551.html}
2559 @item @uref{http://gcc.gnu.org/ml/gcc-bugs/2002-01/msg00663.html}
2562 GCC 3.3 and later support weak symbols on the 32-bit port using SOM
2563 secondary definition symbols. This feature is not enabled for earlier
2564 versions of HP-UX since there have been bugs in the linker support for
2565 secondary symbols. The HP linker patches @code{PHSS_26559} and
2566 @code{PHSS_24304} for HP-UX 11.00 and 11.11, respectively, correct the
2567 problem of linker core dumps creating C++ libraries. Earlier patches
2568 may work but they have not been tested.
2570 GCC 3.3 nows uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capability
2571 to run initializers and finalizers on the 64-bit port. The feature
2572 requires CVS binutils as of January 2, 2003, or a subsequent release
2573 to correct a problem arising from HP's non-standard use of the .init
2574 and .fini sections. The 32-bit port uses the linker @option{+init}
2575 and @option{+fini} options. As with the support for secondary symbols,
2576 there have been bugs in the order in which these options are executed
2577 by the HP linker. So, again a recent linker patch is recommended.
2579 The HP assembler has many limitations and is not recommended for either
2580 the 32 or 64-bit ports. For example, it does not support weak symbols
2581 or alias definitions. As a result, explicit template instantiations
2582 are required when using C++. This will make it difficult if not
2583 impossible to build many C++ applications. You also can't generate
2584 debugging information when using the HP assembler with GCC.
2586 There are a number of issues to consider in selecting which linker to
2587 use with the 64-bit port. The GNU 64-bit linker can only create dynamic
2588 binaries. The @option{-static} option causes linking with archive
2589 libraries but doesn't produce a truly static binary. Dynamic binaries
2590 still require final binding by the dynamic loader to resolve a set of
2591 dynamic-loader-defined symbols. The default behavior of the HP linker
2592 is the same as the GNU linker. However, it can generate true 64-bit
2593 static binaries using the @option{+compat} option.
2595 The HP 64-bit linker doesn't support linkonce semantics. As a
2596 result, C++ programs have many more sections than they should.
2598 The GNU 64-bit linker has some issues with shared library support
2599 and exceptions. As a result, we only support libgcc in archive
2600 format. For similar reasons, dwarf2 unwind and exception support
2601 are disabled. The GNU linker also has problems creating binaries
2602 with @option{-static}. It doesn't provide stubs for internal
2603 calls to global functions in shared libraries, so these calls
2604 can't be overloaded.
2606 There are several possible approaches to building the distribution.
2607 Binutils can be built first using the HP tools. Then, the GCC
2608 distribution can be built. The second approach is to build GCC
2609 first using the HP tools, then build binutils, then rebuild GCC.
2610 There have been problems with various binary distributions, so
2611 it is best not to start from a binary distribution.
2613 Starting with GCC 3.4 an ISO C compiler is required to bootstrap.
2614 The bundled compiler supports only traditional C; you will need
2615 either HP's unbundled compiler, or a binary distribution of GCC@.
2617 This port still is undergoing significant development.
2622 @heading @anchor{i370-*-*}i370-*-*
2623 This port is very preliminary and has many known bugs. We hope to
2624 have a higher-quality port for this machine soon.
2629 @heading @anchor{*-*-linux-gnu}*-*-linux-gnu
2631 Versions of libstdc++-v3 starting with 3.2.1 require bugfixes present
2632 in glibc 2.2.5 and later. More information is available in the
2633 libstdc++-v3 documentation.
2635 If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install
2636 out-of-the-box. You'll get compile errors while building @samp{libstdc++}.
2637 The patch @uref{glibc-2.2.patch,,glibc-2.2.patch}, that is to be
2638 applied in the GCC source tree, fixes the compatibility problems.
2640 Currently Glibc 2.2.3 (and older releases) and GCC 3.0 are out of sync
2641 since the latest exception handling changes for GCC@. Compiling glibc
2642 with GCC 3.0 will give a binary incompatible glibc and therefore cause
2643 lots of problems and might make your system completely unusable. This
2644 will definitely need fixes in glibc but might also need fixes in GCC@. We
2645 strongly advise to wait for glibc 2.2.4 and to read the release notes of
2646 glibc 2.2.4 whether patches for GCC 3.0 are needed. You can use glibc
2647 2.2.3 with GCC 3.0, just do not try to recompile it.
2652 @heading @anchor{ix86-*-linux*aout}i?86-*-linux*aout
2653 Use this configuration to generate @file{a.out} binaries on Linux-based
2654 GNU systems. This configuration is being superseded.
2659 @heading @anchor{ix86-*-linux*}i?86-*-linux*
2661 As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
2662 See @uref{http://gcc.gnu.org/PR10877,,bug 10877} for more information.
2664 If you receive Signal 11 errors when building on GNU/Linux, then it is
2665 possible you have a hardware problem. Further information on this can be
2666 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
2671 @heading @anchor{ix86-*-sco3.2v5*}i?86-*-sco3.2v5*
2672 Use this for the SCO OpenServer Release 5 family of operating systems.
2674 Unlike earlier versions of GCC, the ability to generate COFF with this
2675 target is no longer provided.
2677 Earlier versions of GCC emitted DWARF 1 when generating ELF to allow
2678 the system debugger to be used. That support was too burdensome to
2679 maintain. GCC now emits only DWARF 2 for this target. This means you
2680 may use either the UDK debugger or GDB to debug programs built by this
2683 GCC is now only supported on releases 5.0.4 and later, and requires that
2684 you install Support Level Supplement OSS646B or later, and Support Level
2685 Supplement OSS631C or later. If you are using release 5.0.7 of
2686 OpenServer, you must have at least the first maintenance pack installed
2687 (this includes the relevant portions of OSS646). OSS646, also known as
2688 the "Execution Environment Update", provides updated link editors and
2689 assemblers, as well as updated standard C and math libraries. The C
2690 startup modules are also updated to support the System V gABI draft, and
2691 GCC relies on that behavior. OSS631 provides a collection of commonly
2692 used open source libraries, some of which GCC depends on (such as GNU
2693 gettext and zlib). SCO OpenServer Release 5.0.7 has all of this built
2694 in by default, but OSS631C and later also apply to that release. Please
2696 @uref{ftp://ftp.sco.com/pub/openserver5,,ftp://ftp.sco.com/pub/openserver5}
2697 for the latest versions of these (and other potentially useful)
2700 Although there is support for using the native assembler, it is
2701 recommended that you configure GCC to use the GNU assembler. You do
2702 this by using the flags
2703 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You should
2704 use a modern version of GNU binutils. Version 2.13.2.1 was used for all
2705 testing. In general, only the @option{--with-gnu-as} option is tested.
2706 A modern bintuils (as well as a plethora of other development related
2707 GNU utilities) can be found in Support Level Supplement OSS658A, the
2708 "GNU Development Tools" package. See the SCO web and ftp sites for details.
2709 That package also contains the currently "officially supported" version of
2710 GCC, version 2.95.3. It is useful for bootstrapping this version.
2715 @heading @anchor{ix86-*-udk}i?86-*-udk
2717 This target emulates the SCO Universal Development Kit and requires that
2718 package be installed. (If it is installed, you will have a
2719 @file{/udk/usr/ccs/bin/cc} file present.) It's very much like the
2720 @samp{i?86-*-unixware7*} target
2721 but is meant to be used when hosting on a system where UDK isn't the
2722 default compiler such as OpenServer 5 or Unixware 2. This target will
2723 generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
2724 with the same warnings and caveats as the SCO UDK@.
2726 This target is a little tricky to build because we have to distinguish
2727 it from the native tools (so it gets headers, startups, and libraries
2728 from the right place) while making the tools not think we're actually
2729 building a cross compiler. The easiest way to do this is with a configure
2733 CC=/udk/usr/ccs/bin/cc @var{/your/path/to}/gcc/configure \
2734 --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-
2737 @emph{You should substitute @samp{i686} in the above command with the appropriate
2738 processor for your host.}
2740 After the usual @samp{make bootstrap} and
2741 @samp{make install}, you can then access the UDK-targeted GCC
2742 tools by adding @command{udk-} before the commonly known name. For
2743 example, to invoke the C compiler, you would use @command{udk-gcc}.
2744 They will coexist peacefully with any native-target GCC tools you may
2751 @heading @anchor{ia64-*-linux}ia64-*-linux
2752 IA-64 processor (also known as IPF, or Itanium Processor Family)
2755 None of the following versions of GCC has an ABI that is compatible
2756 with any of the other versions in this list, with the exception that
2757 Red Hat 2.96 and Trillian 000171 are compatible with each other:
2758 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
2759 This primarily affects C++ programs and programs that create shared libraries.
2760 GCC 3.1 or later is recommended for compiling linux, the kernel.
2761 As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
2762 more major ABI changes are expected.
2767 @heading @anchor{ia64-*-hpux*}ia64-*-hpux*
2768 Building GCC on this target requires the GNU Assembler. The bundled HP
2769 assembler will not work. To prevent GCC from using the wrong assembler,
2770 the option @option{--with-gnu-as} may be necessary.
2772 The GCC libunwind library has not been ported to HPUX. This means that for
2773 GCC versions 3.2.3 and earlier, @option{--enable-libunwind-exceptions}
2774 is required to build GCC. For GCC 3.3 and later, this is the default.
2778 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
2780 @heading @anchor{*-ibm-aix*}*-ibm-aix*
2781 Support for AIX version 3 and older was discontinued in GCC 3.4.
2783 AIX Make frequently has problems with GCC makefiles. GNU Make 3.79.1 or
2784 newer is recommended to build on this platform.
2786 Errors involving @code{alloca} when building GCC generally are due
2787 to an incorrect definition of @code{CC} in the Makefile or mixing files
2788 compiled with the native C compiler and GCC@. During the stage1 phase of
2789 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
2790 (not @command{xlc}). Once @command{configure} has been informed of
2791 @command{xlc}, one needs to use @samp{make distclean} to remove the
2792 configure cache files and ensure that @env{CC} environment variable
2793 does not provide a definition that will confuse @command{configure}.
2794 If this error occurs during stage2 or later, then the problem most likely
2795 is the version of Make (see above).
2797 The native @command{as} and @command{ld} are recommended for bootstrapping
2798 on AIX 4 and required for bootstrapping on AIX 5L. The GNU Assembler
2799 reports that it supports WEAK symbols on AIX 4, which causes GCC to try to
2800 utilize weak symbol functionality although it is not supported. The GNU
2801 Assembler and Linker do not support AIX 5L sufficiently to bootstrap GCC.
2802 The native AIX tools do interoperate with GCC@.
2804 Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
2805 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1).
2807 @samp{libstdc++} in GCC 3.2 increments the major version number of the
2808 shared object and GCC installation places the @file{libstdc++.a}
2809 shared library in a common location which will overwrite the GCC 3.1
2810 version of the shared library. Applications either need to be
2811 re-linked against the new shared library or the GCC 3.1 version of the
2812 @samp{libstdc++} shared object needs to be available to the AIX
2813 runtime loader. The GCC 3.1 @samp{libstdc++.so.4} shared object can
2814 be installed for runtime dynamic loading using the following steps to
2815 set the @samp{F_LOADONLY} flag in the shared object for @emph{each}
2816 multilib @file{libstdc++.a} installed:
2818 Extract the shared object from each the GCC 3.1 @file{libstdc++.a}
2821 % ar -x libstdc++.a libstdc++.so.4
2824 Enable the @samp{F_LOADONLY} flag so that the shared object will be
2825 available for runtime dynamic loading, but not linking:
2827 % strip -e libstdc++.so.4
2830 Archive the runtime-only shared object in the GCC 3.2
2831 @file{libstdc++.a} archive:
2833 % ar -q libstdc++.a libstdc++.so.4
2836 Linking executables and shared libraries may produce warnings of
2837 duplicate symbols. The assembly files generated by GCC for AIX always
2838 have included multiple symbol definitions for certain global variable
2839 and function declarations in the original program. The warnings should
2840 not prevent the linker from producing a correct library or runnable
2843 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
2844 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
2845 to parse archive libraries did not handle the new format correctly.
2846 These routines are used by GCC and result in error messages during
2847 linking such as ``not a COFF file''. The version of the routines shipped
2848 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
2849 option of the archive command may be used to create archives of 32-bit
2850 objects using the original ``small format''. A correct version of the
2851 routines is shipped with AIX 4.3.2 and above.
2853 Some versions of the AIX binder (linker) can fail with a relocation
2854 overflow severe error when the @option{-bbigtoc} option is used to link
2855 GCC-produced object files into an executable that overflows the TOC@. A fix
2856 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
2857 available from IBM Customer Support and from its
2858 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2859 website as PTF U455193.
2861 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
2862 with a segmentation fault when invoked by any version of GCC@. A fix for
2863 APAR IX87327 is available from IBM Customer Support and from its
2864 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2865 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
2867 The initial assembler shipped with AIX 4.3.0 generates incorrect object
2868 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
2869 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
2870 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2871 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
2873 AIX provides National Language Support (NLS)@. Compilers and assemblers
2874 use NLS to support locale-specific representations of various data
2875 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
2876 separating decimal fractions). There have been problems reported where
2877 GCC does not produce the same floating-point formats that the assembler
2878 expects. If one encounters this problem, set the @env{LANG}
2879 environment variable to @samp{C} or @samp{En_US}.
2881 By default, GCC for AIX 4.1 and above produces code that can be used on
2882 both Power or PowerPC processors.
2884 A default can be specified with the @option{-mcpu=@var{cpu_type}}
2885 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
2890 @heading @anchor{ip2k-*-elf}ip2k-*-elf
2891 Ubicom IP2022 micro controller.
2892 This configuration is intended for embedded systems.
2893 There are no standard Unix configurations.
2895 Use @samp{configure --target=ip2k-elf --enable-languages=c} to configure GCC@.
2900 @heading @anchor{iq2000-*-elf}iq2000-*-elf
2901 Vitesse IQ2000 processors. These are used in embedded
2902 applications. There are no standard Unix configurations.
2907 @heading @anchor{m32r-*-elf}m32r-*-elf
2908 Renesas M32R processor.
2909 This configuration is intended for embedded systems.
2914 @heading @anchor{m6811-elf}m6811-elf
2915 Motorola 68HC11 family micro controllers. These are used in embedded
2916 applications. There are no standard Unix configurations.
2921 @heading @anchor{m6812-elf}m6812-elf
2922 Motorola 68HC12 family micro controllers. These are used in embedded
2923 applications. There are no standard Unix configurations.
2928 @heading @anchor{m68k-hp-hpux}m68k-hp-hpux
2929 HP 9000 series 300 or 400 running HP-UX@. HP-UX version 8.0 has a bug in
2930 the assembler that prevents compilation of GCC@. This
2931 bug manifests itself during the first stage of compilation, while
2932 building @file{libgcc2.a}:
2936 cc1: warning: `-g' option not supported on this version of GCC
2937 cc1: warning: `-g1' option not supported on this version of GCC
2938 ./xgcc: Internal compiler error: program as got fatal signal 11
2941 A patched version of the assembler is available as the file
2942 @uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you
2943 have HP software support, the patch can also be obtained directly from
2944 HP, as described in the following note:
2947 This is the patched assembler, to patch SR#1653-010439, where the
2948 assembler aborts on floating point constants.
2950 The bug is not really in the assembler, but in the shared library
2951 version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is
2952 SR#4701-078451. Anyway, the attached assembler uses the archive
2953 library version of ``cvtnum(3c)'' and thus does not exhibit the bug.
2956 This patch is also known as PHCO_4484.
2958 In addition gdb does not understand that native HP-UX format, so
2959 you must use gas if you wish to use gdb.
2961 On HP-UX version 8.05, but not on 8.07 or more recent versions, the
2962 @command{fixproto} shell script triggers a bug in the system shell. If you
2963 encounter this problem, upgrade your operating system or use BASH (the
2964 GNU shell) to run @command{fixproto}. This bug will cause the fixproto
2965 program to report an error of the form:
2968 ./fixproto: sh internal 1K buffer overflow
2971 To fix this, you can also change the first line of the fixproto script
2981 @heading @anchor{mips-*-*}mips-*-*
2982 If on a MIPS system you get an error message saying ``does not have gp
2983 sections for all it's [sic] sectons [sic]'', don't worry about it. This
2984 happens whenever you use GAS with the MIPS linker, but there is not
2985 really anything wrong, and it is okay to use the output file. You can
2986 stop such warnings by installing the GNU linker.
2988 It would be nice to extend GAS to produce the gp tables, but they are
2989 optional, and there should not be a warning about their absence.
2991 The libstdc++ atomic locking routines for MIPS targets requires MIPS II
2992 and later. A patch went in just after the GCC 3.3 release to
2993 make @samp{mips*-*-*} use the generic implementation instead. You can also
2994 configure for @samp{mipsel-elf} as a workaround. The
2995 @samp{mips*-*-linux*} target continues to use the MIPS II routines. More
2996 work on this is expected in future releases.
2998 Cross-compilers for the Mips as target using the Mips assembler
2999 currently do not work, because the auxiliary programs
3000 @file{mips-tdump.c} and @file{mips-tfile.c} can't be compiled on
3001 anything but a Mips. It does work to cross compile for a Mips
3002 if you use the GNU assembler and linker.
3007 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
3009 This configuration has considerable problems, which will be fixed in a
3012 In order to compile GCC on an SGI running IRIX 5, the ``compiler_dev.hdr''
3013 subsystem must be installed from the IDO CD-ROM supplied by Silicon
3014 Graphics. It is also available for download from
3015 @uref{http://www.sgi.com/developers/devtools/apis/ido.html,,http://www.sgi.com/developers/devtools/apis/ido.html}.
3017 @samp{make compare} may fail on version 5 of IRIX unless you add
3018 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
3019 assembler input file is stored in the object file, and that makes
3020 comparison fail if it differs between the @code{stage1} and
3021 @code{stage2} compilations. The option @option{-save-temps} forces a
3022 fixed name to be used for the assembler input file, instead of a
3023 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
3024 unless the comparisons fail without that option. If you do you
3025 @option{-save-temps}, you will have to manually delete the @samp{.i} and
3026 @samp{.s} files after each series of compilations.
3028 If you use the MIPS C compiler to bootstrap, it may be necessary
3029 to increase its table size for switch statements with the
3030 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
3031 optimization option, you also need to use @option{-Olimit 3000}.
3033 To enable debugging under IRIX 5, you must use GNU @command{as} 2.11.2
3035 and use the @option{--with-gnu-as} configure option when configuring GCC.
3036 GNU @command{as} is distributed as part of the binutils package.
3037 When using release 2.11.2, you need to apply a patch
3038 @uref{http://sources.redhat.com/ml/binutils/2001-07/msg00352.html,,http://sources.redhat.com/ml/binutils/2001-07/msg00352.html}
3039 which will be included in the next release of binutils.
3041 When building GCC, the build process loops rebuilding @command{cc1} over
3042 and over again. This happens on @samp{mips-sgi-irix5.2}, and possibly
3043 other platforms. It has been reported that this is a known bug in the
3044 @command{make} shipped with IRIX 5.2. We recommend you use GNU
3045 @command{make} instead of the vendor supplied @command{make} program;
3046 however, you may have success with @command{smake} on IRIX 5.2 if you do
3047 not have GNU @command{make} available.
3052 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
3054 If you are using IRIX @command{cc} as your bootstrap compiler, you must
3055 ensure that the N32 ABI is in use. To test this, compile a simple C
3056 file with @command{cc} and then run @command{file} on the
3057 resulting object file. The output should look like:
3060 test.o: ELF N32 MSB @dots{}
3066 test.o: ELF 32-bit MSB @dots{}
3072 test.o: ELF 64-bit MSB @dots{}
3075 then your version of @command{cc} uses the O32 or N64 ABI by default. You
3076 should set the environment variable @env{CC} to @samp{cc -n32}
3077 before configuring GCC@.
3079 If you want the resulting @command{gcc} to run on old 32-bit systems
3080 with the MIPS R4400 CPU, you need to ensure that only code for the mips3
3081 instruction set architecture (ISA) is generated. While GCC 3.x does
3082 this correctly, both GCC 2.95 and SGI's MIPSpro @command{cc} may change
3083 the ISA depending on the machine where GCC is built. Using one of them
3084 as the bootstrap compiler may result in mips4 code, which won't run at
3085 all on mips3-only systems. For the test program above, you should see:
3088 test.o: ELF N32 MSB mips-3 @dots{}
3094 test.o: ELF N32 MSB mips-4 @dots{}
3097 instead, you should set the environment variable @env{CC} to @samp{cc
3098 -n32 -mips3} or @samp{gcc -mips3} respectively before configuring GCC@.
3100 GCC on IRIX 6 is usually built to support both the N32 and N64 ABIs. If
3101 you build GCC on a system that doesn't have the N64 libraries installed,
3102 you need to configure with @option{--disable-multilib} so GCC doesn't
3103 try to use them. Look for @file{/usr/lib64/libc.so.1} to see if you
3104 have the 64-bit libraries installed.
3106 You must @emph{not} use GNU @command{as} (which isn't built anyway as of
3107 binutils 2.11.2) on IRIX 6 platforms; doing so will only cause problems.
3109 GCC does not currently support generating O32 ABI binaries in the
3110 @samp{mips-sgi-irix6} configurations. It is possible to create a GCC
3111 with O32 ABI only support by configuring it for the @samp{mips-sgi-irix5}
3112 target and using a patched GNU @command{as} 2.11.2 as documented in the
3113 @uref{#mips-sgi-irix5,,@samp{mips-sgi-irix5}} section above. Using the
3114 native assembler requires patches to GCC which will be included in a
3115 future release. It is
3116 expected that O32 ABI support will be available again in a future release.
3118 The @option{--enable-threads} option doesn't currently work, a patch is
3119 in preparation for a future release. The @option{--enable-libgcj}
3120 option is disabled by default: IRIX 6 uses a very low default limit
3121 (20480) for the command line length. Although libtool contains a
3122 workaround for this problem, at least the N64 @samp{libgcj} is known not
3123 to build despite this, running into an internal error of the native
3124 @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
3125 its maximum of 262144 bytes. If you have root access, you can use the
3126 @command{systune} command to do this.
3128 GCC does not correctly pass/return structures which are
3129 smaller than 16 bytes and which are not 8 bytes. The problem is very
3130 involved and difficult to fix. It affects a number of other targets also,
3131 but IRIX 6 is affected the most, because it is a 64-bit target, and 4 byte
3132 structures are common. The exact problem is that structures are being padded
3133 at the wrong end, e.g.@: a 4 byte structure is loaded into the lower 4 bytes
3134 of the register when it should be loaded into the upper 4 bytes of the
3137 GCC is consistent with itself, but not consistent with the SGI C compiler
3138 (and the SGI supplied runtime libraries), so the only failures that can
3139 happen are when there are library functions that take/return such
3140 structures. There are very few such library functions. Currently this
3141 is known to affect @code{inet_ntoa}, @code{inet_lnaof},
3142 @code{inet_netof}, @code{inet_makeaddr}, and @code{semctl}. Until the
3143 bug is fixed, GCC contains workarounds for the known affected functions.
3145 See @uref{http://freeware.sgi.com/,,http://freeware.sgi.com/} for more
3146 information about using GCC on IRIX platforms.
3151 @heading @anchor{powerpc*-*-*}powerpc-*-*
3153 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
3154 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
3159 @heading @anchor{powerpc-*-darwin*}powerpc-*-darwin*
3160 PowerPC running Darwin (Mac OS X kernel).
3162 Pre-installed versions of Mac OS X may not include any developer tools,
3163 meaning that you will not be able to build GCC from source. Tool
3164 binaries are available at
3165 @uref{http://developer.apple.com/tools/compilers.html} (free
3166 registration required).
3168 The default stack limit of 512K is too small, which may cause compiles
3169 to fail with 'Bus error'. Set the stack larger, for instance
3170 by doing @samp{limit stack 800}. It's a good idea to use the GNU
3171 preprocessor instead of Apple's @file{cpp-precomp} during the first stage of
3172 bootstrapping; this is automatic when doing @samp{make bootstrap}, but
3173 to do it from the toplevel objdir you will need to say @samp{make
3174 CC='cc -no-cpp-precomp' bootstrap}.
3176 The version of GCC shipped by Apple typically includes a number of
3177 extensions not available in a standard GCC release. These extensions
3178 are generally specific to Mac programming.
3183 @heading @anchor{powerpc-*-elf}powerpc-*-elf, powerpc-*-sysv4
3184 PowerPC system in big endian mode, running System V.4.
3189 @heading @anchor{powerpc-*-linux-gnu*}powerpc-*-linux-gnu*
3192 @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.13.90.0.10}
3193 or newer for a working GCC@.
3198 @heading @anchor{powerpc-*-netbsd*}powerpc-*-netbsd*
3199 PowerPC system in big endian mode running NetBSD@. To build the
3200 documentation you will need Texinfo version 4.2 (NetBSD 1.5.1 included
3201 Texinfo version 3.12).
3206 @heading @anchor{powerpc-*-eabisim}powerpc-*-eabisim
3207 Embedded PowerPC system in big endian mode for use in running under the
3213 @heading @anchor{powerpc-*-eabi}powerpc-*-eabi
3214 Embedded PowerPC system in big endian mode.
3219 @heading @anchor{powerpcle-*-elf}powerpcle-*-elf, powerpcle-*-sysv4
3220 PowerPC system in little endian mode, running System V.4.
3225 @heading @anchor{powerpcle-*-eabisim}powerpcle-*-eabisim
3226 Embedded PowerPC system in little endian mode for use in running under
3232 @heading @anchor{powerpcle-*-eabi}powerpcle-*-eabi
3233 Embedded PowerPC system in little endian mode.
3238 @heading @anchor{s390-*-linux*}s390-*-linux*
3239 S/390 system running Linux for S/390@.
3244 @heading @anchor{s390x-*-linux*}s390x-*-linux*
3245 zSeries system (64-bit) running Linux for zSeries@.
3250 @heading @anchor{s390x-ibm-tpf*}s390x-ibm-tpf*
3251 zSeries system (64-bit) running TPF. This platform is
3252 supported as cross-compilation target only.
3257 @c Please use Solaris 2 to refer to all release of Solaris, starting
3258 @c with 2.0 until 2.6, 7, and 8. Solaris 1 was a marketing name for
3259 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
3260 @c alone is too unspecific and must be avoided.
3261 @heading @anchor{*-*-solaris2*}*-*-solaris2*
3263 Sun does not ship a C compiler with Solaris 2. To bootstrap and install
3264 GCC you first have to install a pre-built compiler, see our
3265 @uref{binaries.html,,binaries page} for details.
3267 The Solaris 2 @command{/bin/sh} will often fail to configure
3268 @file{libstdc++-v3}, @file{boehm-gc} or @file{libjava}. We therefore
3269 recommend to use the following sequence of commands to bootstrap and
3273 % CONFIG_SHELL=/bin/ksh
3274 % export CONFIG_SHELL
3277 and then proceed as described in @uref{build.html,,the build instructions},
3278 where we strongly recommend using GNU make and specifying an absolute path
3279 to invoke @var{srcdir}/configure.
3281 Solaris 2 comes with a number of optional OS packages. Some of these
3282 are needed to use GCC fully, namely @code{SUNWarc},
3283 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
3284 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
3285 optional packages when installing Solaris 2, you will need to verify that
3286 the packages that GCC needs are installed.
3288 To check whether an optional package is installed, use
3289 the @command{pkginfo} command. To add an optional package, use the
3290 @command{pkgadd} command. For further details, see the Solaris 2
3293 Trying to use the linker and other tools in
3294 @file{/usr/ucb} to install GCC has been observed to cause trouble.
3295 For example, the linker may hang indefinitely. The fix is to remove
3296 @file{/usr/ucb} from your @env{PATH}.
3298 The build process works more smoothly with the legacy Sun tools so, if you
3299 have @file{/usr/xpg4/bin} in your @env{PATH}, we recommend that you place
3300 @file{/usr/bin} before @file{/usr/xpg4/bin} for the duration of the build.
3302 All releases of GNU binutils prior to 2.11.2 have known bugs on this
3303 platform. We recommend the use of GNU binutils 2.11.2 or the vendor
3304 tools (Sun @command{as}, Sun @command{ld}).
3306 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3307 newer: @command{g++} will complain that types are missing. These headers assume
3308 that omitting the type means @code{int}; this assumption worked for C89 but
3309 is wrong for C++, and is now wrong for C99 also.
3311 @command{g++} accepts such (invalid) constructs with the option
3312 @option{-fpermissive}; it
3313 will assume that any missing type is @code{int} (as defined by C89).
3315 There are patches for Solaris 2.6 (105633-56 or newer for SPARC,
3316 106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC,
3317 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
3318 108653-22 for Intel) that fix this bug.
3323 @heading @anchor{sparc-sun-solaris2*}sparc-sun-solaris2*
3325 When GCC is configured to use binutils 2.11.2 or later the binaries
3326 produced are smaller than the ones produced using Sun's native tools;
3327 this difference is quite significant for binaries containing debugging
3330 Sun @command{as} 4.x is broken in that it cannot cope with long symbol names.
3331 A typical error message might look similar to the following:
3334 /usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error:
3335 can't compute value of an expression involving an external symbol.
3338 This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris
3339 2.6 and has been fixed in later (5.x) versions of the assembler,
3340 starting with Solaris 7.
3342 Starting with Solaris 7, the operating system is capable of executing
3343 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
3344 this; the @option{-m64} option enables 64-bit code generation.
3345 However, if all you want is code tuned for the UltraSPARC CPU, you
3346 should try the @option{-mtune=ultrasparc} option instead, which produces
3347 code that, unlike full 64-bit code, can still run on non-UltraSPARC
3350 When configuring on a Solaris 7 or later system that is running a kernel
3351 that supports only 32-bit binaries, one must configure with
3352 @option{--disable-multilib}, since we will not be able to build the
3353 64-bit target libraries.
3358 @heading @anchor{sparc-sun-solaris2.7}sparc-sun-solaris2.7
3360 Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
3361 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
3362 and later, including all EGCS releases. Sun formerly recommended
3363 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
3364 recommend it only for people who use Sun's compilers.
3366 Here are some workarounds to this problem:
3369 Do not install Sun patch 107058-01 until after Sun releases a
3370 complete patch for bug 4210064. This is the simplest course to take,
3371 unless you must also use Sun's C compiler. Unfortunately 107058-01
3372 is preinstalled on some new Solaris 7-based hosts, so you may have to
3376 Copy the original, unpatched Solaris 7
3377 @command{/usr/ccs/bin/as} into
3378 @command{/usr/local/libexec/gcc/sparc-sun-solaris2.7/3.4/as},
3379 adjusting the latter name to fit your local conventions and software
3383 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
3384 both 107058-01 and 106950-03 installed has reported the bug with GCC
3385 and Sun's dynamic linker. This last course of action is riskiest,
3386 for two reasons. First, you must install 106950 on all hosts that
3387 run code generated by GCC; it doesn't suffice to install it only on
3388 the hosts that run GCC itself. Second, Sun says that 106950-03 is
3389 only a partial fix for bug 4210064, but Sun doesn't know whether the
3390 partial fix is adequate for GCC@. Revision -08 or later should fix
3391 the bug. The current (as of 2001-09-24) revision is -14, and is included in
3392 the Solaris 7 Recommended Patch Cluster.
3395 GCC 3.3 triggers a bug in version 5.0 Alpha 03/27/98 of the Sun assembler,
3396 which causes a bootstrap failure when linking the 64-bit shared version of
3397 libgcc. A typical error message is:
3400 ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o:
3401 symbol <unknown>: offset 0xffffffff7ec133e7 is non-aligned.
3404 This bug has been fixed in the final 5.0 version of the assembler.
3409 @heading @anchor{sparc-*-linux*}sparc-*-linux*
3411 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
3412 or newer on this platform. All earlier binutils and glibc
3413 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
3419 @heading @anchor{sparc64-*-solaris2*}sparc64-*-solaris2*
3421 The following compiler flags must be specified in the configure
3422 step in order to bootstrap this target with the Sun compiler:
3425 % CC="cc -xildoff -xarch=v9" @var{srcdir}/configure [@var{options}] [@var{target}]
3428 @option{-xildoff} turns off the incremental linker, and @option{-xarch=v9}
3429 specifies the SPARC-V9 architecture to the Sun linker and assembler.
3434 @heading @anchor{sparcv9-*-solaris2*}sparcv9-*-solaris2*
3436 This is a synonym for sparc64-*-solaris2*.
3441 @heading @anchor{#*-*-sysv*}*-*-sysv*
3442 On System V release 3, you may get this error message
3446 ld fatal: failed to write symbol name @var{something}
3447 in strings table for file @var{whatever}
3450 This probably indicates that the disk is full or your ulimit won't allow
3451 the file to be as large as it needs to be.
3453 This problem can also result because the kernel parameter @code{MAXUMEM}
3454 is too small. If so, you must regenerate the kernel and make the value
3455 much larger. The default value is reported to be 1024; a value of 32768
3456 is said to work. Smaller values may also work.
3458 On System V, if you get an error like this,
3461 /usr/local/lib/bison.simple: In function `yyparse':
3462 /usr/local/lib/bison.simple:625: virtual memory exhausted
3466 that too indicates a problem with disk space, ulimit, or @code{MAXUMEM}.
3468 On a System V release 4 system, make sure @file{/usr/bin} precedes
3469 @file{/usr/ucb} in @code{PATH}. The @command{cc} command in
3470 @file{/usr/ucb} uses libraries which have bugs.
3475 @heading @anchor{vax-dec-ultrix}vax-dec-ultrix
3476 Don't try compiling with VAX C (@command{vcc}). It produces incorrect code
3477 in some cases (for example, when @code{alloca} is used).
3482 @heading @anchor{*-*-vxworks*}*-*-vxworks*
3483 Support for VxWorks is in flux. At present GCC supports @emph{only} the
3484 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC.
3485 We welcome patches for other architectures supported by VxWorks 5.5.
3486 Support for VxWorks AE would also be welcome; we believe this is merely
3487 a matter of writing an appropriate ``configlette'' (see below). We are
3488 not interested in supporting older, a.out or COFF-based, versions of
3491 VxWorks comes with an older version of GCC installed in
3492 @file{@var{$WIND_BASE}/host}; we recommend you do not overwrite it.
3493 Choose an installation @var{prefix} entirely outside @var{$WIND_BASE}.
3494 Before running @command{configure}, create the directories @file{@var{prefix}}
3495 and @file{@var{prefix}/bin}. Link or copy the appropriate assembler,
3496 linker, etc. into @file{@var{prefix}/bin}, and set your @var{PATH} to
3497 include that directory while running both @command{configure} and
3500 You must give @command{configure} the
3501 @option{--with-headers=@var{$WIND_BASE}/target/h} switch so that it can
3502 find the VxWorks system headers. Since VxWorks is a cross compilation
3503 target only, you must also specify @option{--target=@var{target}}.
3504 @command{configure} will attempt to create the directory
3505 @file{@var{prefix}/@var{target}/sys-include} and copy files into it;
3506 make sure the user running @command{configure} has sufficient privilege
3509 GCC's exception handling runtime requires a special ``configlette''
3510 module, @file{contrib/gthr_supp_vxw_5x.c}. Follow the instructions in
3511 that file to add the module to your kernel build. (Future versions of
3512 VxWorks will incorporate this module.)
3517 @heading @anchor{xtensa-*-elf}xtensa-*-elf
3519 This target is intended for embedded Xtensa systems using the
3520 @samp{newlib} C library. It uses ELF but does not support shared
3521 objects. Designed-defined instructions specified via the
3522 Tensilica Instruction Extension (TIE) language are only supported
3523 through inline assembly.
3525 The Xtensa configuration information must be specified prior to
3526 building GCC@. The @file{include/xtensa-config.h} header
3527 file contains the configuration information. If you created your
3528 own Xtensa configuration with the Xtensa Processor Generator, the
3529 downloaded files include a customized copy of this header file,
3530 which you can use to replace the default header file.
3535 @heading @anchor{xtensa-*-linux*}xtensa-*-linux*
3537 This target is for Xtensa systems running GNU/Linux. It supports ELF
3538 shared objects and the GNU C library (glibc). It also generates
3539 position-independent code (PIC) regardless of whether the
3540 @option{-fpic} or @option{-fPIC} options are used. In other
3541 respects, this target is the same as the
3542 @uref{#xtensa-*-elf,,@samp{xtensa-*-elf}} target.
3547 @heading @anchor{windows}Microsoft Windows (32-bit)
3549 A port of GCC 2.95.2 and 3.x is included with the
3550 @uref{http://www.cygwin.com/,,Cygwin environment}.
3552 Current (as of early 2001) snapshots of GCC will build under Cygwin
3553 without modification.
3555 GCC does not currently build with Microsoft's C++ compiler and there
3556 are no plans to make it do so.
3561 @heading @anchor{os2}OS/2
3563 GCC does not currently support OS/2. However, Andrew Zabolotny has been
3564 working on a generic OS/2 port with pgcc. The current code can be found
3565 at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
3567 An older copy of GCC 2.8.1 is included with the EMX tools available at
3568 @uref{ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/,,
3569 ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/}.
3574 @heading @anchor{older}Older systems
3576 GCC contains support files for many older (1980s and early
3577 1990s) Unix variants. For the most part, support for these systems
3578 has not been deliberately removed, but it has not been maintained for
3579 several years and may suffer from bitrot.
3581 Starting with GCC 3.1, each release has a list of ``obsoleted'' systems.
3582 Support for these systems is still present in that release, but
3583 @command{configure} will fail unless the @option{--enable-obsolete}
3584 option is given. Unless a maintainer steps forward, support for these
3585 systems will be removed from the next release of GCC@.
3587 Support for old systems as hosts for GCC can cause problems if the
3588 workarounds for compiler, library and operating system bugs affect the
3589 cleanliness or maintainability of the rest of GCC@. In some cases, to
3590 bring GCC up on such a system, if still possible with current GCC, may
3591 require first installing an old version of GCC which did work on that
3592 system, and using it to compile a more recent GCC, to avoid bugs in the
3593 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
3594 @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror
3595 sites}. Header bugs may generally be avoided using
3596 @command{fixincludes}, but bugs or deficiencies in libraries and the
3597 operating system may still cause problems.
3599 Support for older systems as targets for cross-compilation is less
3600 problematic than support for them as hosts for GCC; if an enthusiast
3601 wishes to make such a target work again (including resurrecting any of
3602 the targets that never worked with GCC 2, starting from the last CVS
3603 version before they were removed), patches
3604 @uref{../contribute.html,,following the usual requirements} would be
3605 likely to be accepted, since they should not affect the support for more
3608 For some systems, old versions of GNU binutils may also be useful,
3609 and are available from @file{pub/binutils/old-releases} on
3610 @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}.
3612 Some of the information on specific systems above relates to
3613 such older systems, but much of the information
3614 about GCC on such systems (which may no longer be applicable to
3615 current GCC) is to be found in the GCC texinfo manual.
3620 @heading @anchor{elf_targets}all ELF targets (SVR4, Solaris 2, etc.)
3622 C++ support is significantly better on ELF targets if you use the
3623 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
3624 inlines, vtables and template instantiations will be discarded
3633 @uref{./index.html,,Return to the GCC Installation page}
3637 @c ***Old documentation******************************************************
3639 @include install-old.texi
3645 @uref{./index.html,,Return to the GCC Installation page}
3649 @c ***GFDL********************************************************************
3657 @uref{./index.html,,Return to the GCC Installation page}
3661 @c ***************************************************************************
3662 @c Part 6 The End of the Document
3664 @comment node-name, next, previous, up
3665 @node Concept Index, , GNU Free Documentation License, Top
3669 @unnumbered Concept Index