1 \input texinfo.tex @c -*-texinfo-*-
4 @setfilename gccinstall.info
5 @settitle Installing GCC
10 @c Specify title for specific html page
12 @settitle Installing GCC
15 @settitle Host/Target specific installation notes for GCC
17 @ifset prerequisiteshtml
18 @settitle Prerequisites for GCC
21 @settitle Downloading GCC
24 @settitle Installing GCC: Configuration
27 @settitle Installing GCC: Building
30 @settitle Installing GCC: Testing
32 @ifset finalinstallhtml
33 @settitle Installing GCC: Final installation
36 @settitle Installing GCC: Binaries
39 @settitle Installing GCC: Old documentation
42 @settitle Installing GCC: GNU Free Documentation License
45 @c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
46 @c 1999, 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc.
47 @c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com
49 @c Include everything if we're not making html
53 @set prerequisiteshtml
64 @c Part 2 Summary Description and Copyright
66 Copyright @copyright{} 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
67 1999, 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc.
69 Permission is granted to copy, distribute and/or modify this document
70 under the terms of the GNU Free Documentation License, Version 1.2 or
71 any later version published by the Free Software Foundation; with no
72 Invariant Sections, the Front-Cover texts being (a) (see below), and
73 with the Back-Cover Texts being (b) (see below). A copy of the
74 license is included in the section entitled ``@uref{./gfdl.html,,GNU
75 Free Documentation License}''.
77 (a) The FSF's Front-Cover Text is:
81 (b) The FSF's Back-Cover Text is:
83 You have freedom to copy and modify this GNU Manual, like GNU
84 software. Copies published by the Free Software Foundation raise
85 funds for GNU development.
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 versions 2.13 and 2.57
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. Most
295 directories require autoconf 2.13 (exactly), but @file{libiberty},
296 @file{fastjar}, @file{libstdc++-v3}, @file{libjava/libltdl}, and @file{gcc}
297 require autoconf 2.57 (exactly).
299 @item automake versions 1.4-gcj and 1.7.9
301 Necessary when modifying a @file{Makefile.am} file to regenerate its
302 associated @file{Makefile.in}.
304 Much of GCC does not use automake, so directly edit the @file{Makefile.in}
305 file. Specifically this applies to the @file{gcc}, @file{intl},
306 @file{libf2c}, @file{libiberty}, @file{libobjc} directories as well as any
307 of their subdirectories.
309 The @file{libstdc++-v3}, @file{libjava/libltdl}, and @file{fastjar}
310 directories require automake 1.7.9. However, the Java directories, which
311 include @file{boehm-gc}, @file{libffi}, @file{libjava}, and @file{zlib},
312 require a modified version of automake 1.4 downloadable from
313 @uref{ftp://gcc.gnu.org/pub/java/automake-gcj-1.4.tar.gz}.
315 @item gettext version 0.12 (or later)
317 Needed to regenerate @file{gcc.pot}.
319 @item gperf version 2.7.2 (or later)
321 Necessary when modifying @command{gperf} input files, e.g.@:
322 @file{gcc/cp/cfns.gperf} to regenerate its associated header file, e.g.@:
323 @file{gcc/cp/cfns.h}.
325 @item expect version ???
326 @itemx tcl version ???
327 @itemx dejagnu version ???
329 Necessary to run the GCC testsuite.
331 @item autogen version 5.5.4 (or later) and
332 @itemx guile version 1.4.1 (or later)
334 Necessary to regenerate @file{fixinc/fixincl.x} from
335 @file{fixinc/inclhack.def} and @file{fixinc/*.tpl}.
337 Necessary to run the @file{fixinc} @command{make check}.
339 Necessary to regenerate the top level @file{Makefile.in} file from
340 @file{Makefile.tpl} and @file{Makefile.def}.
342 @item GNU Bison version 1.28 (or later)
343 Berkeley @command{yacc} (@command{byacc}) is also reported to work other
346 Necessary when modifying @file{*.y} files.
348 Necessary to build GCC during development because the generated output
349 files are not included in the CVS repository. They are included in
352 @item Flex version 2.5.4 (or later)
354 Necessary when modifying @file{*.l} files.
356 Necessary to build GCC during development because the generated output
357 files are not included in the CVS repository. They are included in
360 @item Texinfo version 4.2 (or later)
362 Necessary for running @command{makeinfo} when modifying @file{*.texi}
363 files to test your changes.
365 Necessary to build GCC documentation during development because the
366 generated output files are not included in the CVS repository. They are
367 included in releases.
369 @item @TeX{} (any working version)
371 Necessary for running @command{texi2dvi}, used when running
372 @command{make dvi} to create DVI files.
374 @item cvs version 1.10 (or later)
375 @itemx ssh (any version)
377 Necessary to access the CVS repository. Public releases and weekly
378 snapshots of the development sources are also available via FTP.
380 @item perl version 5.6.1 (or later)
382 Necessary when regenerating @file{Makefile} dependencies in libiberty.
383 Necessary when regenerating @file{libiberty/functions.texi}.
384 Necessary when generating manpages from Texinfo manuals.
385 Used by various scripts to generate some files included in CVS (mainly
386 Unicode-related and rarely changing) from source tables.
388 @item GNU diffutils version 2.7 (or later)
390 Necessary when creating changes to GCC source code to submit for review.
392 @item patch version 2.5.4 (or later)
394 Necessary when applying patches, created with @command{diff}, to one's
404 @uref{./index.html,,Return to the GCC Installation page}
408 @c ***Downloading the source**************************************************
410 @comment node-name, next, previous, up
411 @node Downloading the source, Configuration, Prerequisites, Installing GCC
415 @chapter Downloading GCC
417 @cindex Downloading GCC
418 @cindex Downloading the Source
420 GCC is distributed via @uref{http://gcc.gnu.org/cvs.html,,CVS} and FTP
421 tarballs compressed with @command{gzip} or
422 @command{bzip2}. It is possible to download a full distribution or specific
425 Please refer to our @uref{http://gcc.gnu.org/releases.html,,releases web page}
426 for information on how to obtain GCC@.
428 The full distribution includes the C, C++, Objective-C, Fortran, Java,
429 and Ada (in case of GCC 3.1 and later) compilers. The full distribution
430 also includes runtime libraries for C++, Objective-C, Fortran, and Java.
431 In GCC 3.0 and later versions, GNU compiler testsuites are also included
432 in the full distribution.
434 If you choose to download specific components, you must download the core
435 GCC distribution plus any language specific distributions you wish to
436 use. The core distribution includes the C language front end as well as the
437 shared components. Each language has a tarball which includes the language
438 front end as well as the language runtime (when appropriate).
440 Unpack the core distribution as well as any language specific
441 distributions in the same directory.
443 If you also intend to build binutils (either to upgrade an existing
444 installation or for use in place of the corresponding tools of your
445 OS), unpack the binutils distribution either in the same directory or
446 a separate one. In the latter case, add symbolic links to any
447 components of the binutils you intend to build alongside the compiler
448 (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
449 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
456 @uref{./index.html,,Return to the GCC Installation page}
460 @c ***Configuration***********************************************************
462 @comment node-name, next, previous, up
463 @node Configuration, Building, Downloading the source, Installing GCC
467 @chapter Installing GCC: Configuration
469 @cindex Configuration
470 @cindex Installing GCC: Configuration
472 Like most GNU software, GCC must be configured before it can be built.
473 This document describes the recommended configuration procedure
474 for both native and cross targets.
476 We use @var{srcdir} to refer to the toplevel source directory for
477 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
479 If you obtained the sources via CVS, @var{srcdir} must refer to the top
480 @file{gcc} directory, the one where the @file{MAINTAINERS} can be found,
481 and not its @file{gcc} subdirectory, otherwise the build will fail.
483 If either @var{srcdir} or @var{objdir} is located on an automounted NFS
484 file system, the shell's built-in @command{pwd} command will return
485 temporary pathnames. Using these can lead to various sorts of build
486 problems. To avoid this issue, set the @env{PWDCMD} environment
487 variable to an automounter-aware @command{pwd} command, e.g.,
488 @command{pawd} or @samp{amq -w}, during the configuration and build
491 First, we @strong{highly} recommend that GCC be built into a
492 separate directory than the sources which does @strong{not} reside
493 within the source tree. This is how we generally build GCC; building
494 where @var{srcdir} == @var{objdir} should still work, but doesn't
495 get extensive testing; building where @var{objdir} is a subdirectory
496 of @var{srcdir} is unsupported.
498 If you have previously built GCC in the same directory for a
499 different target machine, do @samp{make distclean} to delete all files
500 that might be invalid. One of the files this deletes is @file{Makefile};
501 if @samp{make distclean} complains that @file{Makefile} does not exist
502 or issues a message like ``don't know how to make distclean'' it probably
503 means that the directory is already suitably clean. However, with the
504 recommended method of building in a separate @var{objdir}, you should
505 simply use a different @var{objdir} for each target.
507 Second, when configuring a native system, either @command{cc} or
508 @command{gcc} must be in your path or you must set @env{CC} in
509 your environment before running configure. Otherwise the configuration
512 Note that the bootstrap compiler and the resulting GCC must be link
513 compatible, else the bootstrap will fail with linker errors about
514 incompatible object file formats. Several multilibed targets are
515 affected by this requirement, see
517 @ref{Specific, host/target specific installation notes}.
520 @uref{specific.html,,host/target specific installation notes}.
528 % @var{srcdir}/configure [@var{options}] [@var{target}]
532 @heading Target specification
535 GCC has code to correctly determine the correct value for @var{target}
536 for nearly all native systems. Therefore, we highly recommend you not
537 provide a configure target when configuring a native compiler.
540 @var{target} must be specified as @option{--target=@var{target}}
541 when configuring a cross compiler; examples of valid targets would be
542 m68k-coff, sh-elf, etc.
545 Specifying just @var{target} instead of @option{--target=@var{target}}
546 implies that the host defaults to @var{target}.
550 @heading Options specification
552 Use @var{options} to override several configure time options for
553 GCC@. A list of supported @var{options} follows; @samp{configure
554 --help} may list other options, but those not listed below may not
555 work and should not normally be used.
558 @item --prefix=@var{dirname}
559 Specify the toplevel installation
560 directory. This is the recommended way to install the tools into a directory
561 other than the default. The toplevel installation directory defaults to
564 We @strong{highly} recommend against @var{dirname} being the same or a
565 subdirectory of @var{objdir} or vice versa. If specifying a directory
566 beneath a user's home directory tree, some shells will not expand
567 @var{dirname} correctly if it contains the @samp{~} metacharacter; use
570 The following standard @command{autoconf} options are supported. Normally you
571 should not need to use these options.
573 @item --exec-prefix=@var{dirname}
574 Specify the toplevel installation directory for architecture-dependent
575 files. The default is @file{@var{prefix}}.
577 @item --bindir=@var{dirname}
578 Specify the installation directory for the executables called by users
579 (such as @command{gcc} and @command{g++}). The default is
580 @file{@var{exec-prefix}/bin}.
582 @item --libdir=@var{dirname}
583 Specify the installation directory for object code libraries and
584 internal data files of GCC@. The default is @file{@var{exec-prefix}/lib}.
586 @item --libexecdir=@var{dirname}
587 Specify the installation directory for internal executables of GCC@.
588 The default is @file{@var{exec-prefix}/libexec}.
590 @item --with-slibdir=@var{dirname}
591 Specify the installation directory for the shared libgcc library. The
592 default is @file{@var{libdir}}.
594 @item --infodir=@var{dirname}
595 Specify the installation directory for documentation in info format.
596 The default is @file{@var{prefix}/info}.
598 @item --datadir=@var{dirname}
599 Specify the installation directory for some architecture-independent
600 data files referenced by GCC@. The default is @file{@var{prefix}/share}.
602 @item --mandir=@var{dirname}
603 Specify the installation directory for manual pages. The default is
604 @file{@var{prefix}/man}. (Note that the manual pages are only extracts from
605 the full GCC manuals, which are provided in Texinfo format. The manpages
606 are derived by an automatic conversion process from parts of the full
609 @item --with-gxx-include-dir=@var{dirname}
611 the installation directory for G++ header files. The default is
612 @file{@var{prefix}/include/c++/@var{version}}.
616 @item --program-prefix=@var{prefix}
617 GCC supports some transformations of the names of its programs when
618 installing them. This option prepends @var{prefix} to the names of
619 programs to install in @var{bindir} (see above). For example, specifying
620 @option{--program-prefix=foo-} would result in @samp{gcc}
621 being installed as @file{/usr/local/bin/foo-gcc}.
623 @item --program-suffix=@var{suffix}
624 Appends @var{suffix} to the names of programs to install in @var{bindir}
625 (see above). For example, specifying @option{--program-suffix=-3.1}
626 would result in @samp{gcc} being installed as
627 @file{/usr/local/bin/gcc-3.1}.
629 @item --program-transform-name=@var{pattern}
630 Applies the @samp{sed} script @var{pattern} to be applied to the names
631 of programs to install in @var{bindir} (see above). @var{pattern} has to
632 consist of one or more basic @samp{sed} editing commands, separated by
633 semicolons. For example, if you want the @samp{gcc} program name to be
634 transformed to the installed program @file{/usr/local/bin/myowngcc} and
635 the @samp{g++} program name to be transformed to
636 @file{/usr/local/bin/gspecial++} without changing other program names,
637 you could use the pattern
638 @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}
639 to achieve this effect.
641 All three options can be combined and used together, resulting in more
642 complex conversion patterns. As a basic rule, @var{prefix} (and
643 @var{suffix}) are prepended (appended) before further transformations
644 can happen with a special transformation script @var{pattern}.
646 As currently implemented, this option only takes effect for native
647 builds; cross compiler binaries' names are not transformed even when a
648 transformation is explicitly asked for by one of these options.
650 For native builds, some of the installed programs are also installed
651 with the target alias in front of their name, as in
652 @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
653 before the target alias is prepended to the name - so, specifying
654 @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
655 resulting binary would be installed as
656 @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.
658 As a last shortcoming, none of the installed Ada programs are
659 transformed yet, which will be fixed in some time.
661 @item --with-local-prefix=@var{dirname}
663 installation directory for local include files. The default is
664 @file{/usr/local}. Specify this option if you want the compiler to
665 search directory @file{@var{dirname}/include} for locally installed
666 header files @emph{instead} of @file{/usr/local/include}.
668 You should specify @option{--with-local-prefix} @strong{only} if your
669 site has a different convention (not @file{/usr/local}) for where to put
672 The default value for @option{--with-local-prefix} is @file{/usr/local}
673 regardless of the value of @option{--prefix}. Specifying
674 @option{--prefix} has no effect on which directory GCC searches for
675 local header files. This may seem counterintuitive, but actually it is
678 The purpose of @option{--prefix} is to specify where to @emph{install
679 GCC}. The local header files in @file{/usr/local/include}---if you put
680 any in that directory---are not part of GCC@. They are part of other
681 programs---perhaps many others. (GCC installs its own header files in
682 another directory which is based on the @option{--prefix} value.)
684 Both the local-prefix include directory and the GCC-prefix include
685 directory are part of GCC's "system include" directories. Although these
686 two directories are not fixed, they need to be searched in the proper
687 order for the correct processing of the include_next directive. The
688 local-prefix include directory is searched before the GCC-prefix
689 include directory. Another characteristic of system include directories
690 is that pedantic warnings are turned off for headers in these directories.
692 Some autoconf macros add @option{-I @var{directory}} options to the
693 compiler command line, to ensure that directories containing installed
694 packages' headers are searched. When @var{directory} is one of GCC's
695 system include directories, GCC will ignore the option so that system
696 directories continue to be processed in the correct order. This
697 may result in a search order different from what was specified but the
698 directory will still be searched.
700 GCC automatically searches for ordinary libraries using
701 @env{GCC_EXEC_PREFIX}. Thus, when the same installation prefix is
702 used for both GCC and packages, GCC will automatically search for
703 both headers and libraries. This provides a configuration that is
704 easy to use. GCC behaves in a manner similar to that when it is
705 installed as a system compiler in @file{/usr}.
707 Sites that need to install multiple versions of GCC may not want to
708 use the above simple configuration. It is possible to use the
709 @option{--program-prefix}, @option{--program-suffix} and
710 @option{--program-transform-name} options to install multiple versions
711 into a single directory, but it may be simpler to use different prefixes
712 and the @option{--with-local-prefix} option to specify the location of the
713 site-specific files for each version. It will then be necessary for
714 users to specify explicitly the location of local site libraries
715 (e.g., with @env{LIBRARY_PATH}).
717 The same value can be used for both @option{--with-local-prefix} and
718 @option{--prefix} provided it is not @file{/usr}. This can be used
719 to avoid the default search of @file{/usr/local/include}.
721 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
722 The directory you use for @option{--with-local-prefix} @strong{must not}
723 contain any of the system's standard header files. If it did contain
724 them, certain programs would be miscompiled (including GNU Emacs, on
725 certain targets), because this would override and nullify the header
726 file corrections made by the @command{fixincludes} script.
728 Indications are that people who use this option use it based on mistaken
729 ideas of what it is for. People use it as if it specified where to
730 install part of GCC@. Perhaps they make this assumption because
731 installing GCC creates the directory.
733 @item --enable-shared[=@var{package}[,@dots{}]]
734 Build shared versions of libraries, if shared libraries are supported on
735 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
736 are enabled by default on all platforms that support shared libraries,
737 except for @samp{libobjc} which is built as a static library only by
740 If a list of packages is given as an argument, build shared libraries
741 only for the listed packages. For other packages, only static libraries
742 will be built. Package names currently recognized in the GCC tree are
743 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
744 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc} and
745 @samp{libjava}. Note that @samp{libobjc} does not recognize itself by
746 any name, so, if you list package names in @option{--enable-shared},
747 you will only get static Objective-C libraries. @samp{libf2c} and
748 @samp{libiberty} do not support shared libraries at all.
750 Use @option{--disable-shared} to build only static libraries. Note that
751 @option{--disable-shared} does not accept a list of package names as
752 argument, only @option{--enable-shared} does.
754 @item @anchor{with-gnu-as}--with-gnu-as
755 Specify that the compiler should assume that the
756 assembler it finds is the GNU assembler. However, this does not modify
757 the rules to find an assembler and will result in confusion if the
758 assembler found is not actually the GNU assembler. (Confusion may also
759 result if the compiler finds the GNU assembler but has not been
760 configured with @option{--with-gnu-as}.) If you have more than one
761 assembler installed on your system, you may want to use this option in
762 connection with @option{--with-as=@var{pathname}}.
764 The following systems are the only ones where it makes a difference
765 whether you use the GNU assembler. On any other system,
766 @option{--with-gnu-as} has no effect.
769 @item @samp{hppa1.0-@var{any}-@var{any}}
770 @item @samp{hppa1.1-@var{any}-@var{any}}
771 @item @samp{i386-@var{any}-sysv}
772 @item @samp{m68k-bull-sysv}
773 @item @samp{m68k-hp-hpux}
774 @item @samp{m68000-hp-hpux}
775 @item @samp{m68000-att-sysv}
776 @item @samp{@var{any}-lynx-lynxos}
777 @item @samp{mips-@var{any}}
778 @item @samp{sparc-sun-solaris2.@var{any}}
779 @item @samp{sparc64-@var{any}-solaris2.@var{any}}
782 On the systems listed above (except for the HP-PA, the SPARC, for ISC on
783 the 386, and for @samp{mips-sgi-irix5.*}), if you use the GNU assembler,
784 you should also use the GNU linker (and specify @option{--with-gnu-ld}).
786 @item @anchor{with-as}--with-as=@var{pathname}
788 compiler should use the assembler pointed to by @var{pathname}, rather
789 than the one found by the standard rules to find an assembler, which
793 Check the @file{@var{libexec}/gcc/@var{target}/@var{version}}
794 directory, where @var{libexec} defaults to
795 @file{@var{exec-prefix}/libexec} and @var{exec-prefix} defaults to
796 @var{prefix} which defaults to @file{/usr/local} unless overridden by
797 the @option{--prefix=@var{pathname}} switch described
798 above. @var{target} is the target system triple, such as
799 @samp{sparc-sun-solaris2.7}, and @var{version} denotes the GCC
800 version, such as 3.0.
802 Check operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
805 Note that these rules do not check for the value of @env{PATH}. You may
806 want to use @option{--with-as} if no assembler is installed in the
807 directories listed above, or if you have multiple assemblers installed
808 and want to choose one that is not found by the above rules.
810 @item @anchor{with-gnu-ld}--with-gnu-ld
811 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
814 @item --with-ld=@var{pathname}
815 Same as @uref{#with-as,,@option{--with-as}}
819 Specify that stabs debugging
820 information should be used instead of whatever format the host normally
821 uses. Normally GCC uses the same debug format as the host system.
823 On MIPS based systems and on Alphas, you must specify whether you want
824 GCC to create the normal ECOFF debugging format, or to use BSD-style
825 stabs passed through the ECOFF symbol table. The normal ECOFF debug
826 format cannot fully handle languages other than C@. BSD stabs format can
827 handle other languages, but it only works with the GNU debugger GDB@.
829 Normally, GCC uses the ECOFF debugging format by default; if you
830 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
832 No matter which default you choose when you configure GCC, the user
833 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
834 the debug format for a particular compilation.
836 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
837 @option{--with-gas} is used. It selects use of stabs debugging
838 information embedded in COFF output. This kind of debugging information
839 supports C++ well; ordinary COFF debugging information does not.
841 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
842 selects use of stabs debugging information embedded in ELF output. The
843 C++ compiler currently (2.6.0) does not support the DWARF debugging
844 information normally used on 386 SVR4 platforms; stabs provide a
845 workable alternative. This requires gas and gdb, as the normal SVR4
846 tools can not generate or interpret stabs.
848 @item --disable-multilib
849 Specify that multiple target
850 libraries to support different target variants, calling
851 conventions, etc should not be built. The default is to build a
852 predefined set of them.
854 Some targets provide finer-grained control over which multilibs are built
855 (e.g., @option{--disable-softfloat}):
861 fpu, 26bit, underscore, interwork, biendian, nofmult.
864 softfloat, m68881, m68000, m68020.
867 single-float, biendian, softfloat.
869 @item powerpc*-*-*, rs6000*-*-*
870 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
875 @item --enable-threads
876 Specify that the target
877 supports threads. This affects the Objective-C compiler and runtime
878 library, and exception handling for other languages like C++ and Java.
879 On some systems, this is the default.
881 In general, the best (and, in many cases, the only known) threading
882 model available will be configured for use. Beware that on some
883 systems, gcc has not been taught what threading models are generally
884 available for the system. In this case, @option{--enable-threads} is an
885 alias for @option{--enable-threads=single}.
887 @item --disable-threads
888 Specify that threading support should be disabled for the system.
889 This is an alias for @option{--enable-threads=single}.
891 @item --enable-threads=@var{lib}
893 @var{lib} is the thread support library. This affects the Objective-C
894 compiler and runtime library, and exception handling for other languages
895 like C++ and Java. The possibilities for @var{lib} are:
903 Ada tasking support. For non-Ada programs, this setting is equivalent
904 to @samp{single}. When used in conjunction with the Ada run time, it
905 causes GCC to use the same thread primitives as Ada uses. This option
906 is necessary when using both Ada and the back end exception handling,
907 which is the default for most Ada targets.
909 Generic MACH thread support, known to work on NeXTSTEP@. (Please note
910 that the file needed to support this configuration, @file{gthr-mach.h}, is
911 missing and thus this setting will cause a known bootstrap failure.)
913 This is an alias for @samp{single}.
915 Generic POSIX thread support.
917 RTEMS thread support.
919 Disable thread support, should work for all platforms.
921 Sun Solaris 2 thread support.
923 VxWorks thread support.
925 Microsoft Win32 API thread support.
928 @item --with-cpu=@var{cpu}
929 Specify which cpu variant the compiler should generate code for by default.
930 @var{cpu} will be used as the default value of the @option{-mcpu=} switch.
931 This option is only supported on some targets, including ARM, i386, PowerPC,
934 @item --with-schedule=@var{cpu}
935 @itemx --with-arch=@var{cpu}
936 @itemx --with-tune=@var{cpu}
937 @itemx --with-abi=@var{abi}
938 @itemx --with-fpu=@var{type}
939 @itemx --with-float=@var{type}
940 These configure options provide default values for the @option{-mschedule=},
941 @option{-march=}, @option{-mtune=}, @option{-mabi=}, and @option{-mfpu=}
942 options and for @option{-mhard-float} or @option{-msoft-float}. As with
943 @option{--with-cpu}, which switches will be accepted and acceptable values
944 of the arguments depend on the target.
946 @item --enable-altivec
947 Specify that the target supports AltiVec vector enhancements. This
948 option will adjust the ABI for AltiVec enhancements, as well as generate
949 AltiVec code when appropriate. This option is only available for
952 @item --enable-__cxa_atexit
953 Define if you want to use __cxa_atexit, rather than atexit, to
954 register C++ destructors for local statics and global objects.
955 This is essential for fully standards-compliant handling of
956 destructors, but requires __cxa_atexit in libc. This option is currently
957 only available on systems with GNU libc. When enabled, this will cause
958 @option{-fuse-cxa-exit} to be passed by default.
960 @item --enable-target-optspace
962 libraries should be optimized for code space instead of code speed.
963 This is the default for the m32r platform.
966 Specify that a user visible @command{cpp} program should not be installed.
968 @item --with-cpp-install-dir=@var{dirname}
969 Specify that the user visible @command{cpp} program should be installed
970 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
972 @item --enable-initfini-array
973 Force the use of sections @code{.init_array} and @code{.fini_array}
974 (instead of @code{.init} and @code{.fini}) for constructors and
975 destructors. Option @option{--disable-initfini-array} has the
976 opposite effect. If neither option is specified, the configure script
977 will try to guess whether the @code{.init_array} and
978 @code{.fini_array} sections are supported and, if they are, use them.
980 @item --enable-maintainer-mode
982 regenerate the GCC master message catalog @file{gcc.pot} are normally
983 disabled. This is because it can only be rebuilt if the complete source
984 tree is present. If you have changed the sources and want to rebuild the
985 catalog, configuring with @option{--enable-maintainer-mode} will enable
986 this. Note that you need a recent version of the @code{gettext} tools
989 @item --enable-generated-files-in-srcdir
990 Neither the .c and .h files that are generated from bison and flex nor the
991 info manuals and man pages that are built from the .texi files are present
992 in the CVS development tree. When building GCC from that development tree,
993 or from a snapshot which are created from CVS, then those generated files
994 are placed in your build directory, which allows for the source to be in a
997 If you configure with @option{--enable-generated-files-in-srcdir} then those
998 generated files will go into the source directory. This is mainly intended
999 for generating release or prerelease tarballs of the GCC sources, since it
1000 is not a requirement that the users of source releases to have flex, bison, or
1003 @item --enable-version-specific-runtime-libs
1005 that runtime libraries should be installed in the compiler specific
1006 subdirectory (@file{@var{libdir}/gcc}) rather than the usual places. In
1007 addition, @samp{libstdc++}'s include files will be installed into
1008 @file{@var{libdir}} unless you overruled it by using
1009 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
1010 particularly useful if you intend to use several versions of GCC in
1011 parallel. This is currently supported by @samp{libf2c} and
1012 @samp{libstdc++}, and is the default for @samp{libobjc} which cannot be
1013 changed in this case.
1015 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
1016 Specify that only a particular subset of compilers and
1017 their runtime libraries should be built. For a list of valid values for
1018 @var{langN} you can issue the following command in the
1019 @file{gcc} directory of your GCC source tree:@*
1021 grep language= */config-lang.in
1023 Currently, you can use any of the following:
1024 @code{ada}, @code{c}, @code{c++}, @code{f77}, @code{java}, @code{objc}.
1025 Building the Ada compiler has special requirements, see below.@*
1026 If you do not pass this flag, all languages available in the @file{gcc}
1027 sub-tree will be configured. Re-defining @code{LANGUAGES} when calling
1028 @samp{make bootstrap} @strong{does not} work anymore, as those
1029 language sub-directories might not have been configured!
1031 @item --disable-libada
1032 Specify that the run-time libraries and tools used by GNAT should not
1033 be built. This can be useful for debugging, or for compatibility with
1034 previous Ada build procedures, when it was required to explicitly
1035 do a @samp{make -C gcc gnatlib_and_tools}.
1037 @item --disable-libgcj
1038 Specify that the run-time libraries
1039 used by GCJ should not be built. This is useful in case you intend
1040 to use GCJ with some other run-time, or you're going to install it
1041 separately, or it just happens not to build on your particular
1042 machine. In general, if the Java front end is enabled, the GCJ
1043 libraries will be enabled too, unless they're known to not work on
1044 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
1045 may need to port it; in this case, before modifying the top-level
1046 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
1047 you may use @option{--enable-libgcj} to override the default.
1050 Specify that the compiler should
1051 use DWARF 2 debugging information as the default.
1053 @item --enable-win32-registry
1054 @itemx --enable-win32-registry=@var{key}
1055 @itemx --disable-win32-registry
1056 The @option{--enable-win32-registry} option enables Microsoft Windows-hosted GCC
1057 to look up installations paths in the registry using the following key:
1060 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
1063 @var{key} defaults to GCC version number, and can be overridden by the
1064 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
1065 who use custom installers are encouraged to provide a different key,
1066 perhaps one comprised of vendor name and GCC version number, to
1067 avoid conflict with existing installations. This feature is enabled
1068 by default, and can be disabled by @option{--disable-win32-registry}
1069 option. This option has no effect on the other hosts.
1072 Specify that the machine does not have a floating point unit. This
1073 option only applies to @samp{m68k-sun-sunos@var{n}}. On any other
1074 system, @option{--nfp} has no effect.
1076 @item --enable-werror
1077 @itemx --disable-werror
1078 @itemx --enable-werror=yes
1079 @itemx --enable-werror=no
1080 When you specify this option, it controls whether certain files in the
1081 compiler are built with @option{-Werror} in bootstrap stage2 and later.
1082 If you don't specify it, @option{-Werror} is turned on for the main
1083 development trunk. However it defaults to off for release branches and
1084 final releases. The specific files which get @option{-Werror} are
1085 controlled by the Makefiles.
1087 @item --enable-checking
1088 @itemx --enable-checking=@var{list}
1089 When you specify this option, the compiler is built to perform checking
1090 of tree node types when referencing fields of that node, and some other
1091 internal consistency checks. This does not change the generated code,
1092 but adds error checking within the compiler. This will slow down the
1093 compiler and may only work properly if you are building the compiler
1094 with GCC@. This is on by default when building from CVS or snapshots,
1095 but off for releases. More control over the checks may be had by
1096 specifying @var{list}; the categories of checks available are
1097 @samp{misc}, @samp{tree}, @samp{gc}, @samp{rtl}, @samp{rtlflag},
1098 @samp{fold}, @samp{gcac} and @samp{valgrind}. The check @samp{valgrind}
1099 requires the external @command{valgrind} simulator, available from
1100 @uref{http://valgrind.kde.org/}. The default when @var{list} is
1101 not specified is @samp{misc,tree,gc,rtlflag}; the checks @samp{rtl},
1102 @samp{gcac} and @samp{valgrind} are very expensive.
1104 @item --enable-coverage
1105 @itemx --enable-coverage=@var{level}
1106 With this option, the compiler is built to collect self coverage
1107 information, every time it is run. This is for internal development
1108 purposes, and only works when the compiler is being built with gcc. The
1109 @var{level} argument controls whether the compiler is built optimized or
1110 not, values are @samp{opt} and @samp{noopt}. For coverage analysis you
1111 want to disable optimization, for performance analysis you want to
1112 enable optimization. When coverage is enabled, the default level is
1113 without optimization.
1115 @item --enable-gather-detailed-mem-stats
1116 When this option is specified more detailed information on memory
1117 allocation is gathered. This information is printed when using
1118 @option{-fmem-report}.
1121 @itemx --disable-nls
1122 The @option{--enable-nls} option enables Native Language Support (NLS),
1123 which lets GCC output diagnostics in languages other than American
1124 English. Native Language Support is enabled by default if not doing a
1125 canadian cross build. The @option{--disable-nls} option disables NLS@.
1127 @item --with-included-gettext
1128 If NLS is enabled, the @option{--with-included-gettext} option causes the build
1129 procedure to prefer its copy of GNU @command{gettext}.
1131 @item --with-catgets
1132 If NLS is enabled, and if the host lacks @code{gettext} but has the
1133 inferior @code{catgets} interface, the GCC build procedure normally
1134 ignores @code{catgets} and instead uses GCC's copy of the GNU
1135 @code{gettext} library. The @option{--with-catgets} option causes the
1136 build procedure to use the host's @code{catgets} in this situation.
1138 @item --with-libiconv-prefix=@var{dir}
1139 Search for libiconv header files in @file{@var{dir}/include} and
1140 libiconv library files in @file{@var{dir}/lib}.
1142 @item --with-system-zlib
1143 Use installed zlib rather than that included with GCC@. This option
1144 only applies if the Java front end is being built.
1146 @item --enable-obsolete
1147 Enable configuration for an obsoleted system. If you attempt to
1148 configure GCC for a system (build, host, or target) which has been
1149 obsoleted, and you do not specify this flag, configure will halt with an
1152 All support for systems which have been obsoleted in one release of GCC
1153 is removed entirely in the next major release, unless someone steps
1154 forward to maintain the port.
1157 Some options which only apply to building cross compilers:
1159 @item --with-sysroot
1160 @itemx --with-sysroot=@var{dir}
1161 Tells GCC to consider @var{dir} as the root of a tree that contains a
1162 (subset of) the root filesystem of the target operating system.
1163 Target system headers, libraries and run-time object files will be
1164 searched in there. The specified directory is not copied into the
1165 install tree, unlike the options @option{--with-headers} and
1166 @option{--with-libs} that this option obsoletes. The default value,
1167 in case @option{--with-sysroot} is not given an argument, is
1168 @option{$@{gcc_tooldir@}/sys-root}. If the specified directory is a
1169 subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to
1170 the GCC binaries if the installation tree is moved.
1172 @item --with-headers
1173 @itemx --with-headers=@var{dir}
1174 Deprecated in favor of @option{--with-sysroot}.
1175 Specifies that target headers are available when building a cross compiler.
1176 The @var{dir} argument specifies a directory which has the target include
1177 files. These include files will be copied into the @file{gcc} install
1178 directory. @emph{This option with the @var{dir} argument is required} when
1179 building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include}
1180 doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does
1181 pre-exist, the @var{dir} argument may be omitted. @command{fixincludes}
1182 will be run on these files to make them compatible with GCC.
1184 @item --without-headers
1185 Tells GCC not use any target headers from a libc when building a cross
1186 compiler. When crossing to GNU/Linux, you need the headers so gcc
1187 can build the exception handling for libgcc.
1188 See @uref{http://www.objsw.com/CrossGCC/,,CrossGCC} for more information
1192 @itemx --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
1193 Deprecated in favor of @option{--with-sysroot}.
1194 Specifies a list of directories which contain the target runtime
1195 libraries. These libraries will be copied into the @file{gcc} install
1196 directory. If the directory list is omitted, this option has no
1199 Specifies that @samp{newlib} is
1200 being used as the target C library. This causes @code{__eprintf} to be
1201 omitted from @file{libgcc.a} on the assumption that it will be provided by
1205 Note that each @option{--enable} option has a corresponding
1206 @option{--disable} option and that each @option{--with} option has a
1207 corresponding @option{--without} option.
1214 @uref{./index.html,,Return to the GCC Installation page}
1218 @c ***Building****************************************************************
1220 @comment node-name, next, previous, up
1221 @node Building, Testing, Configuration, Installing GCC
1227 @cindex Installing GCC: Building
1229 Now that GCC is configured, you are ready to build the compiler and
1232 We @strong{highly} recommend that GCC be built using GNU make;
1233 other versions may work, then again they might not.
1234 GNU make is required for compiling GNAT (the Ada compiler) and the Java
1237 (For example, many broken versions of make will fail if you use the
1238 recommended setup where @var{objdir} is different from @var{srcdir}.
1239 Other broken versions may recompile parts of the compiler when
1240 installing the compiler.)
1242 Some commands executed when making the compiler may fail (return a
1243 nonzero status) and be ignored by @command{make}. These failures, which
1244 are often due to files that were not found, are expected, and can safely
1247 It is normal to have compiler warnings when compiling certain files.
1248 Unless you are a GCC developer, you can generally ignore these warnings
1249 unless they cause compilation to fail. Developers should attempt to fix
1250 any warnings encountered, however they can temporarily continue past
1251 warnings-as-errors by specifying the configure flag
1252 @option{--disable-werror}.
1254 On certain old systems, defining certain environment variables such as
1255 @env{CC} can interfere with the functioning of @command{make}.
1257 If you encounter seemingly strange errors when trying to build the
1258 compiler in a directory other than the source directory, it could be
1259 because you have previously configured the compiler in the source
1260 directory. Make sure you have done all the necessary preparations.
1262 If you build GCC on a BSD system using a directory stored in an old System
1263 V file system, problems may occur in running @command{fixincludes} if the
1264 System V file system doesn't support symbolic links. These problems
1265 result in a failure to fix the declaration of @code{size_t} in
1266 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
1267 that type mismatches occur, this could be the cause.
1269 The solution is not to use such a directory for building GCC@.
1271 When building from CVS or snapshots, or if you modify parser sources,
1272 you need the Bison parser generator installed. Any version 1.25 or
1273 later should work; older versions may also work. If you do not modify
1274 parser sources, releases contain the Bison-generated files and you do
1275 not need Bison installed to build them.
1277 When building from CVS or snapshots, or if you modify Texinfo
1278 documentation, you need version 4.2 or later of Texinfo installed if you
1279 want Info documentation to be regenerated. Releases contain Info
1280 documentation pre-built for the unmodified documentation in the release.
1282 @section Building a native compiler
1284 For a native build issue the command @samp{make bootstrap}. This
1285 will build the entire GCC system, which includes the following steps:
1289 Build host tools necessary to build the compiler such as texinfo, bison,
1293 Build target tools for use by the compiler such as binutils (bfd,
1294 binutils, gas, gprof, ld, and opcodes)
1295 if they have been individually linked
1296 or moved into the top level GCC source tree before configuring.
1299 Perform a 3-stage bootstrap of the compiler.
1302 Perform a comparison test of the stage2 and stage3 compilers.
1305 Build runtime libraries using the stage3 compiler from the previous step.
1309 If you are short on disk space you might consider @samp{make
1310 bootstrap-lean} instead. This is identical to @samp{make
1311 bootstrap} except that object files from the stage1 and
1312 stage2 of the 3-stage bootstrap of the compiler are deleted as
1313 soon as they are no longer needed.
1315 If you want to save additional space during the bootstrap and in
1316 the final installation as well, you can build the compiler binaries
1317 without debugging information as in the following example. This will save
1318 roughly 40% of disk space both for the bootstrap and the final installation.
1319 (Libraries will still contain debugging information.)
1322 make CFLAGS='-O' LIBCFLAGS='-g -O2' \
1323 LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap
1326 If you wish to use non-default GCC flags when compiling the stage2 and
1327 stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing
1328 @samp{make bootstrap}. Non-default optimization flags are less well
1329 tested here than the default of @samp{-g -O2}, but should still work.
1330 In a few cases, you may find that you need to specify special flags such
1331 as @option{-msoft-float} here to complete the bootstrap; or, if the
1332 native compiler miscompiles the stage1 compiler, you may need to work
1333 around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the
1334 stage1 compiler that were miscompiled, or by using @samp{make
1335 bootstrap4} to increase the number of stages of bootstrap.
1337 If you used the flag @option{--enable-languages=@dots{}} to restrict
1338 the compilers to be built, only those you've actually enabled will be
1339 built. This will of course only build those runtime libraries, for
1340 which the particular compiler has been built. Please note,
1341 that re-defining @env{LANGUAGES} when calling @samp{make bootstrap}
1342 @strong{does not} work anymore!
1344 If the comparison of stage2 and stage3 fails, this normally indicates
1345 that the stage2 compiler has compiled GCC incorrectly, and is therefore
1346 a potentially serious bug which you should investigate and report. (On
1347 a few systems, meaningful comparison of object files is impossible; they
1348 always appear ``different''. If you encounter this problem, you will
1349 need to disable comparison in the @file{Makefile}.)
1351 @section Building a cross compiler
1353 We recommend reading the
1354 @uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ}
1355 for information about building cross compilers.
1357 When building a cross compiler, it is not generally possible to do a
1358 3-stage bootstrap of the compiler. This makes for an interesting problem
1359 as parts of GCC can only be built with GCC@.
1361 To build a cross compiler, we first recommend building and installing a
1362 native compiler. You can then use the native GCC compiler to build the
1363 cross compiler. The installed native compiler needs to be GCC version
1366 Assuming you have already installed a native copy of GCC and configured
1367 your cross compiler, issue the command @command{make}, which performs the
1372 Build host tools necessary to build the compiler such as texinfo, bison,
1376 Build target tools for use by the compiler such as binutils (bfd,
1377 binutils, gas, gprof, ld, and opcodes)
1378 if they have been individually linked or moved into the top level GCC source
1379 tree before configuring.
1382 Build the compiler (single stage only).
1385 Build runtime libraries using the compiler from the previous step.
1388 Note that if an error occurs in any step the make process will exit.
1390 If you are not building GNU binutils in the same source tree as GCC,
1391 you will need a cross-assembler and cross-linker installed before
1392 configuring GCC@. Put them in the directory
1393 @file{@var{prefix}/@var{target}/bin}. Here is a table of the tools
1394 you should put in this directory:
1398 This should be the cross-assembler.
1401 This should be the cross-linker.
1404 This should be the cross-archiver: a program which can manipulate
1405 archive files (linker libraries) in the target machine's format.
1408 This should be a program to construct a symbol table in an archive file.
1411 The installation of GCC will find these programs in that directory,
1412 and copy or link them to the proper place to for the cross-compiler to
1413 find them when run later.
1415 The easiest way to provide these files is to build the Binutils package.
1416 Configure it with the same @option{--host} and @option{--target}
1417 options that you use for configuring GCC, then build and install
1418 them. They install their executables automatically into the proper
1419 directory. Alas, they do not support all the targets that GCC
1422 If you are not building a C library in the same source tree as GCC,
1423 you should also provide the target libraries and headers before
1424 configuring GCC, specifying the directories with
1425 @option{--with-sysroot} or @option{--with-headers} and
1426 @option{--with-libs}. Many targets also require ``start files'' such
1427 as @file{crt0.o} and
1428 @file{crtn.o} which are linked into each executable. There may be several
1429 alternatives for @file{crt0.o}, for use with profiling or other
1430 compilation options. Check your target's definition of
1431 @code{STARTFILE_SPEC} to find out what start files it uses.
1433 @section Building in parallel
1435 You can use @samp{make bootstrap MAKE="make -j 2" -j 2}, or just
1436 @samp{make -j 2 bootstrap} for GNU Make 3.79 and above, instead of
1437 @samp{make bootstrap} to build GCC in parallel.
1438 You can also specify a bigger number, and in most cases using a value
1439 greater than the number of processors in your machine will result in
1440 fewer and shorter I/O latency hits, thus improving overall throughput;
1441 this is especially true for slow drives and network filesystems.
1443 @section Building the Ada compiler
1445 In order to build GNAT, the Ada compiler, you need a working GNAT
1446 compiler (GNAT version 3.14 or later, or GCC version 3.1 or later),
1447 including GNAT tools such as @command{gnatmake} and @command{gnatlink},
1448 since the Ada front end is written in Ada (with some
1449 GNAT-specific extensions), and GNU make.
1451 @command{configure} does not test whether the GNAT installation works
1452 and has a sufficiently recent version; if too old a GNAT version is
1453 installed, the build will fail unless @option{--enable-languages} is
1454 used to disable building the Ada front end.
1456 @section Building with profile feedback
1458 It is possible to use profile feedback to optimize the compiler itself. This
1459 should result in a faster compiler binary. Experiments done on x86 using gcc
1460 3.3 showed approximately 7 percent speedup on compiling C programs. To
1461 bootstrap compiler with profile feedback, use @code{make profiledbootstrap}.
1463 When @samp{make profiledbootstrap} is run, it will first build a @code{stage1}
1464 compiler. This compiler is used to build a @code{stageprofile} compiler
1465 instrumented to collect execution counts of instruction and branch
1466 probabilities. Then runtime libraries are compiled with profile collected.
1467 Finally a @code{stagefeedback} compiler is built using the information collected.
1469 Unlike @samp{make bootstrap} several additional restrictions apply. The
1470 compiler used to build @code{stage1} needs to support a 64-bit integral type.
1471 It is recommended to only use GCC for this. Also parallel make is currently
1472 not supported since collisions in profile collecting may occur.
1479 @uref{./index.html,,Return to the GCC Installation page}
1483 @c ***Testing*****************************************************************
1485 @comment node-name, next, previous, up
1486 @node Testing, Final install, Building, Installing GCC
1490 @chapter Installing GCC: Testing
1493 @cindex Installing GCC: Testing
1496 Before you install GCC, we encourage you to run the testsuites and to
1497 compare your results with results from a similar configuration that have
1498 been submitted to the
1499 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
1500 Some of these archived results are linked from the build status lists
1501 at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who
1502 reports a successful build runs the testsuites and submits the results.
1503 This step is optional and may require you to download additional software,
1504 but it can give you confidence in your new GCC installation or point out
1505 problems before you install and start using your new GCC.
1507 First, you must have @uref{download.html,,downloaded the testsuites}.
1508 These are part of the full distribution, but if you downloaded the
1509 ``core'' compiler plus any front ends, you must download the testsuites
1512 Second, you must have the testing tools installed. This includes
1513 @uref{http://www.gnu.org/software/dejagnu/,,DejaGnu} 1.4.1 or 1.4.3
1514 and later, Tcl, and Expect; the DejaGnu site has links to these.
1516 If the directories where @command{runtest} and @command{expect} were
1517 installed are not in the @env{PATH}, you may need to set the following
1518 environment variables appropriately, as in the following example (which
1519 assumes that DejaGnu has been installed under @file{/usr/local}):
1522 TCL_LIBRARY = /usr/local/share/tcl8.0
1523 DEJAGNULIBS = /usr/local/share/dejagnu
1526 (On systems such as Cygwin, these paths are required to be actual
1527 paths, not mounts or links; presumably this is due to some lack of
1528 portability in the DejaGnu code.)
1531 Finally, you can run the testsuite (which may take a long time):
1533 cd @var{objdir}; make -k check
1536 This will test various components of GCC, such as compiler
1537 front ends and runtime libraries. While running the testsuite, DejaGnu
1538 might emit some harmless messages resembling
1539 @samp{WARNING: Couldn't find the global config file.} or
1540 @samp{WARNING: Couldn't find tool init file} that can be ignored.
1542 @section How can I run the test suite on selected tests?
1544 In order to run sets of tests selectively, there are targets
1545 @samp{make check-gcc} and @samp{make check-g++}
1546 in the @file{gcc} subdirectory of the object directory. You can also
1547 just run @samp{make check} in a subdirectory of the object directory.
1550 A more selective way to just run all @command{gcc} execute tests in the
1554 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
1557 Likewise, in order to run only the @command{g++} ``old-deja'' tests in
1558 the testsuite with filenames matching @samp{9805*}, you would use
1561 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
1564 The @file{*.exp} files are located in the testsuite directories of the GCC
1565 source, the most important ones being @file{compile.exp},
1566 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
1567 To get a list of the possible @file{*.exp} files, pipe the
1568 output of @samp{make check} into a file and look at the
1569 @samp{Running @dots{} .exp} lines.
1571 @section Passing options and running multiple testsuites
1573 You can pass multiple options to the testsuite using the
1574 @samp{--target_board} option of DejaGNU, either passed as part of
1575 @samp{RUNTESTFLAGS}, or directly to @command{runtest} if you prefer to
1576 work outside the makefiles. For example,
1579 make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fno-strength-reduce"
1582 will run the standard @command{g++} testsuites (``unix'' is the target name
1583 for a standard native testsuite situation), passing
1584 @samp{-O3 -fno-strength-reduce} to the compiler on every test, i.e.,
1585 slashes separate options.
1587 You can run the testsuites multiple times using combinations of options
1588 with a syntax similar to the brace expansion of popular shells:
1591 @dots{}"--target_board=arm-sim@{-mhard-float,-msoft-float@}@{-O1,-O2,-O3,@}"
1594 (Note the empty option caused by the trailing comma in the final group.)
1595 The following will run each testsuite eight times using the @samp{arm-sim}
1596 target, as if you had specified all possible combinations yourself:
1599 --target_board=arm-sim/-mhard-float/-O1
1600 --target_board=arm-sim/-mhard-float/-O2
1601 --target_board=arm-sim/-mhard-float/-O3
1602 --target_board=arm-sim/-mhard-float
1603 --target_board=arm-sim/-msoft-float/-O1
1604 --target_board=arm-sim/-msoft-float/-O2
1605 --target_board=arm-sim/-msoft-float/-O3
1606 --target_board=arm-sim/-msoft-float
1609 They can be combined as many times as you wish, in arbitrary ways. This
1613 @dots{}"--target_board=unix/-Wextra@{-O3,-fno-strength-reduce@}@{-fomit-frame-pointer,@}"
1616 will generate four combinations, all involving @samp{-Wextra}.
1618 The disadvantage to this method is that the testsuites are run in serial,
1619 which is a waste on multiprocessor systems. For users with GNU Make and
1620 a shell which performs brace expansion, you can run the testsuites in
1621 parallel by having the shell perform the combinations and @command{make}
1622 do the parallel runs. Instead of using @samp{--target_board}, use a
1623 special makefile target:
1626 make -j@var{N} check-@var{testsuite}//@var{test-target}/@var{option1}/@var{option2}/@dots{}
1632 make -j3 check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@}
1635 will run three concurrent ``make-gcc'' testsuites, eventually testing all
1636 ten combinations as described above. Note that this is currently only
1637 supported in the @file{gcc} subdirectory. (To see how this works, try
1638 typing @command{echo} before the example given here.)
1641 @section Additional testing for Java Class Libraries
1643 The Java runtime tests can be executed via @samp{make check}
1644 in the @file{@var{target}/libjava/testsuite} directory in
1647 The @uref{http://sources.redhat.com/mauve/,,Mauve Project} provides
1648 a suite of tests for the Java Class Libraries. This suite can be run
1649 as part of libgcj testing by placing the Mauve tree within the libjava
1650 testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by
1651 specifying the location of that tree when invoking @samp{make}, as in
1652 @samp{make MAUVEDIR=~/mauve check}.
1654 @uref{http://www-124.ibm.com/developerworks/oss/cvs/jikes/~checkout~/jacks/jacks.html,,Jacks}
1655 is a free test suite that tests Java compiler front ends. This suite
1656 can be run as part of libgcj testing by placing the Jacks tree within
1657 the libjava testsuite at @file{libjava/testsuite/libjava.jacks/jacks}.
1659 @section How to interpret test results
1661 The result of running the testsuite are various @file{*.sum} and @file{*.log}
1662 files in the testsuite subdirectories. The @file{*.log} files contain a
1663 detailed log of the compiler invocations and the corresponding
1664 results, the @file{*.sum} files summarize the results. These summaries
1665 contain status codes for all tests:
1669 PASS: the test passed as expected
1671 XPASS: the test unexpectedly passed
1673 FAIL: the test unexpectedly failed
1675 XFAIL: the test failed as expected
1677 UNSUPPORTED: the test is not supported on this platform
1679 ERROR: the testsuite detected an error
1681 WARNING: the testsuite detected a possible problem
1684 It is normal for some tests to report unexpected failures. At the
1685 current time our testing harness does not allow fine grained control
1686 over whether or not a test is expected to fail. We expect to fix this
1687 problem in future releases.
1690 @section Submitting test results
1692 If you want to report the results to the GCC project, use the
1693 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
1696 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
1697 -m gcc-testresults@@gcc.gnu.org |sh
1700 This script uses the @command{Mail} program to send the results, so
1701 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
1702 prepended to the testsuite summary and should contain any special
1703 remarks you have on your results or your build environment. Please
1704 do not edit the testsuite result block or the subject line, as these
1705 messages may be automatically processed.
1712 @uref{./index.html,,Return to the GCC Installation page}
1716 @c ***Final install***********************************************************
1718 @comment node-name, next, previous, up
1719 @node Final install, , Testing, Installing GCC
1721 @ifset finalinstallhtml
1723 @chapter Installing GCC: Final installation
1726 Now that GCC has been built (and optionally tested), you can install it with
1728 cd @var{objdir}; make install
1731 We strongly recommend to install into a target directory where there is
1732 no previous version of GCC present.
1734 That step completes the installation of GCC; user level binaries can
1735 be found in @file{@var{prefix}/bin} where @var{prefix} is the value
1736 you specified with the @option{--prefix} to configure (or
1737 @file{/usr/local} by default). (If you specified @option{--bindir},
1738 that directory will be used instead; otherwise, if you specified
1739 @option{--exec-prefix}, @file{@var{exec-prefix}/bin} will be used.)
1740 Headers for the C++ and Java libraries are installed in
1741 @file{@var{prefix}/include}; libraries in @file{@var{libdir}}
1742 (normally @file{@var{prefix}/lib}); internal parts of the compiler in
1743 @file{@var{libdir}/gcc} and @file{@var{libexecdir}/gcc}; documentation
1744 in info format in @file{@var{infodir}} (normally
1745 @file{@var{prefix}/info}).
1747 When installing cross-compilers, GCC's executables
1748 are not only installed into @file{@var{bindir}}, that
1749 is, @file{@var{exec-prefix}/bin}, but additionally into
1750 @file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory
1751 exists. Typically, such @dfn{tooldirs} hold target-specific
1752 binutils, including assembler and linker.
1754 Installation into a temporary staging area or into a @command{chroot}
1755 jail can be achieved with the command
1758 make DESTDIR=@var{path-to-rootdir} install
1761 @noindent where @var{path-to-rootdir} is the absolute path of
1762 a directory relative to which all installation paths will be
1763 interpreted. Note that the directory specified by @code{DESTDIR}
1764 need not exist yet; it will be created if necessary.
1766 There is a subtle point with tooldirs and @code{DESTDIR}:
1767 If you relocate a cross-compiler installation with
1768 e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory
1769 @file{@var{rootdir}/@var{exec-prefix}/@var{target-alias}/bin} will
1770 be filled with duplicated GCC executables only if it already exists,
1771 it will not be created otherwise. This is regarded as a feature,
1772 not as a bug, because it gives slightly more control to the packagers
1773 using the @code{DESTDIR} feature.
1775 If you built a released version of GCC using @samp{make bootstrap} then please
1776 quickly review the build status page for your release, available from
1777 @uref{http://gcc.gnu.org/buildstat.html}.
1778 If your system is not listed for the version of GCC that you built,
1780 @email{gcc@@gcc.gnu.org} indicating
1781 that you successfully built and installed GCC.
1782 Include the following information:
1786 Output from running @file{@var{srcdir}/config.guess}. Do not send us
1787 that file itself, just the one-line output from running it.
1790 The output of @samp{gcc -v} for your newly installed gcc.
1791 This tells us which version of GCC you built and the options you passed to
1795 Whether you enabled all languages or a subset of them. If you used a
1796 full distribution then this information is part of the configure
1797 options in the output of @samp{gcc -v}, but if you downloaded the
1798 ``core'' compiler plus additional front ends then it isn't apparent
1799 which ones you built unless you tell us about it.
1802 If the build was for GNU/Linux, also include:
1805 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
1806 this information should be available from @file{/etc/issue}.
1809 The version of the Linux kernel, available from @samp{uname --version}
1813 The version of glibc you used; for RPM-based systems like Red Hat,
1814 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
1815 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
1817 For other systems, you can include similar information if you think it is
1821 Any other information that you think would be useful to people building
1822 GCC on the same configuration. The new entry in the build status list
1823 will include a link to the archived copy of your message.
1826 We'd also like to know if the
1828 @ref{Specific, host/target specific installation notes}
1831 @uref{specific.html,,host/target specific installation notes}
1833 didn't include your host/target information or if that information is
1834 incomplete or out of date. Send a note to
1835 @email{gcc@@gcc.gnu.org} telling us how the information should be changed.
1837 If you find a bug, please report it following our
1838 @uref{../bugs.html,,bug reporting guidelines}.
1840 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
1841 dvi}. You will need to have @command{texi2dvi} (version at least 4.2)
1842 and @TeX{} installed. This creates a number of @file{.dvi} files in
1843 subdirectories of @file{@var{objdir}}; these may be converted for
1844 printing with programs such as @command{dvips}. You can also
1845 @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the
1846 Free Software Foundation}, though such manuals may not be for the most
1847 recent version of GCC@.
1854 @uref{./index.html,,Return to the GCC Installation page}
1858 @c ***Binaries****************************************************************
1860 @comment node-name, next, previous, up
1861 @node Binaries, Specific, Installing GCC, Top
1865 @chapter Installing GCC: Binaries
1868 @cindex Installing GCC: Binaries
1870 We are often asked about pre-compiled versions of GCC@. While we cannot
1871 provide these for all platforms, below you'll find links to binaries for
1872 various platforms where creating them by yourself is not easy due to various
1875 Please note that we did not create these binaries, nor do we
1876 support them. If you have any problems installing them, please
1877 contact their makers.
1884 @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX};
1887 @uref{http://aixpdslib.seas.ucla.edu,,UCLA Software Library for AIX}.
1891 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}.
1894 Renesas H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
1895 Development Tools for the Renesas H8/300[HS] Series}.
1901 @uref{http://hpux.cae.wisc.edu/,,HP-UX Porting Center};
1904 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
1908 Motorola 68HC11/68HC12---@uref{http://www.gnu-m68hc11.org,,GNU
1909 Development Tools for the Motorola 68HC11/68HC12}.
1912 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
1913 OpenServer/Unixware}.
1916 Sinix/Reliant Unix---@uref{ftp://ftp.fujitsu-siemens.com/pub/pd/gnu/gcc/,,Siemens}.
1919 Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware}.
1922 SGI---@uref{http://freeware.sgi.com/,,SGI Freeware}.
1928 The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project;
1930 The @uref{http://www.mingw.org/,,MinGW} project.
1934 @uref{ftp://ftp.thewrittenword.com/packages/by-name/,,The
1935 Written Word} offers binaries for
1938 Digital UNIX 4.0D and 5.1,
1940 HP-UX 10.20, 11.00, and 11.11, and
1941 Solaris/SPARC 2.5.1, 2.6, 2.7, 8, and 9,
1944 In addition to those specific offerings, you can get a binary
1945 distribution CD-ROM from the
1946 @uref{http://www.fsf.org/order/order.html,,Free Software Foundation}.
1947 It contains binaries for a number of platforms, and
1948 includes not only GCC, but other stuff as well. The current CD does
1949 not contain the latest version of GCC, but it should allow
1950 bootstrapping the compiler. An updated version of that disk is in the
1958 @uref{./index.html,,Return to the GCC Installation page}
1962 @c ***Specific****************************************************************
1964 @comment node-name, next, previous, up
1965 @node Specific, Old, Binaries, Top
1969 @chapter Host/target specific installation notes for GCC
1972 @cindex Specific installation notes
1973 @cindex Target specific installation
1974 @cindex Host specific installation
1975 @cindex Target specific installation notes
1977 Please read this document carefully @emph{before} installing the
1978 GNU Compiler Collection on your machine.
1983 @uref{#alpha*-*-*,,alpha*-*-*}
1985 @uref{#alpha*-dec-osf*,,alpha*-dec-osf*}
1987 @uref{#alphaev5-cray-unicosmk*,,alphaev5-cray-unicosmk*}
1989 @uref{#arc-*-elf,,arc-*-elf}
1991 @uref{#arm-*-elf,,arm-*-elf}
1992 @uref{#arm-*-coff,,arm-*-coff}
1993 @uref{#arm-*-aout,,arm-*-aout}
1995 @uref{#xscale-*-*,,xscale-*-*}
2003 @uref{#*-*-freebsd*,,*-*-freebsd*}
2005 @uref{#h8300-hms,,h8300-hms}
2007 @uref{#hppa*-hp-hpux*,,hppa*-hp-hpux*}
2009 @uref{#hppa*-hp-hpux10,,hppa*-hp-hpux10}
2011 @uref{#hppa*-hp-hpux11,,hppa*-hp-hpux11}
2013 @uref{#*-*-linux-gnu,,*-*-linux-gnu}
2015 @uref{#ix86-*-linux*aout,,i?86-*-linux*aout}
2017 @uref{#ix86-*-linux*,,i?86-*-linux*}
2019 @uref{#ix86-*-sco3.2v5*,,i?86-*-sco3.2v5*}
2021 @uref{#ix86-*-udk,,i?86-*-udk}
2023 @uref{#ix86-*-esix,,i?86-*-esix}
2025 @uref{#ia64-*-linux,,ia64-*-linux}
2027 @uref{#ia64-*-hpux*,,ia64-*-hpux*}
2029 @uref{#*-ibm-aix*,,*-ibm-aix*}
2031 @uref{#ip2k-*-elf,,ip2k-*-elf}
2033 @uref{#iq2000-*-elf,,iq2000-*-elf}
2035 @uref{#m32r-*-elf,,m32r-*-elf}
2037 @uref{#m6811-elf,,m6811-elf}
2039 @uref{#m6812-elf,,m6812-elf}
2041 @uref{#m68k-hp-hpux,,m68k-hp-hpux}
2043 @uref{#mips-*-*,,mips-*-*}
2045 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
2047 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
2049 @uref{#powerpc*-*-*,,powerpc*-*-*, powerpc-*-sysv4}
2051 @uref{#powerpc-*-darwin*,,powerpc-*-darwin*}
2053 @uref{#powerpc-*-elf,,powerpc-*-elf, powerpc-*-sysv4}
2055 @uref{#powerpc-*-linux-gnu*,,powerpc-*-linux-gnu*}
2057 @uref{#powerpc-*-netbsd*,,powerpc-*-netbsd*}
2059 @uref{#powerpc-*-eabiaix,,powerpc-*-eabiaix}
2061 @uref{#powerpc-*-eabisim,,powerpc-*-eabisim}
2063 @uref{#powerpc-*-eabi,,powerpc-*-eabi}
2065 @uref{#powerpcle-*-elf,,powerpcle-*-elf, powerpcle-*-sysv4}
2067 @uref{#powerpcle-*-eabisim,,powerpcle-*-eabisim}
2069 @uref{#powerpcle-*-eabi,,powerpcle-*-eabi}
2071 @uref{#s390-*-linux*,,s390-*-linux*}
2073 @uref{#s390x-*-linux*,,s390x-*-linux*}
2075 @uref{#s390x-ibm-tpf*,,s390x-ibm-tpf*}
2077 @uref{#*-*-solaris2*,,*-*-solaris2*}
2079 @uref{#sparc-sun-solaris2*,,sparc-sun-solaris2*}
2081 @uref{#sparc-sun-solaris2.7,,sparc-sun-solaris2.7}
2083 @uref{#sparc-*-linux*,,sparc-*-linux*}
2085 @uref{#sparc64-*-solaris2*,,sparc64-*-solaris2*}
2087 @uref{#sparcv9-*-solaris2*,,sparcv9-*-solaris2*}
2089 @uref{#*-*-sysv*,,*-*-sysv*}
2091 @uref{#vax-dec-ultrix,,vax-dec-ultrix}
2093 @uref{#*-*-vxworks*,,*-*-vxworks*}
2095 @uref{#x86_64-*-*,,x86_64-*-*, amd64-*-*}
2097 @uref{#xtensa-*-elf,,xtensa-*-elf}
2099 @uref{#xtensa-*-linux*,,xtensa-*-linux*}
2101 @uref{#windows,,Microsoft Windows}
2105 @uref{#older,,Older systems}
2110 @uref{#elf_targets,,all ELF targets} (SVR4, Solaris 2, etc.)
2116 <!-- -------- host/target specific issues start here ---------------- -->
2119 @heading @anchor{alpha*-*-*}alpha*-*-*
2121 This section contains general configuration information for all
2122 alpha-based platforms using ELF (in particular, ignore this section for
2123 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
2124 section, please read all other sections that match your target.
2126 We require binutils 2.11.2 or newer.
2127 Previous binutils releases had a number of problems with DWARF 2
2128 debugging information, not the least of which is incorrect linking of
2134 @heading @anchor{alpha*-dec-osf*}alpha*-dec-osf*
2135 Systems using processors that implement the DEC Alpha architecture and
2136 are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
2137 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
2139 As of GCC 3.2, versions before @code{alpha*-dec-osf4} are no longer
2140 supported. (These are the versions which identify themselves as DEC
2143 In Digital Unix V4.0, virtual memory exhausted bootstrap failures
2144 may be fixed by configuring with @option{--with-gc=simple},
2145 reconfiguring Kernel Virtual Memory and Swap parameters
2146 per the @command{/usr/sbin/sys_check} Tuning Suggestions,
2147 or applying the patch in
2148 @uref{http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html}.
2150 In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
2151 currently (2001-06-13) work with @command{mips-tfile}. As a workaround,
2152 we need to use the old assembler, invoked via the barely documented
2153 @option{-oldas} option. To bootstrap GCC, you either need to use the
2157 % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
2160 or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
2163 % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
2166 As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld}
2167 are supported on Tru64 UNIX, so you must not configure GCC with
2168 @option{--with-gnu-as} or @option{--with-gnu-ld}.
2170 GCC writes a @samp{.verstamp} directive to the assembler output file
2171 unless it is built as a cross-compiler. It gets the version to use from
2172 the system header file @file{/usr/include/stamp.h}. If you install a
2173 new version of DEC Unix, you should rebuild GCC to pick up the new version
2176 Note that since the Alpha is a 64-bit architecture, cross-compilers from
2177 32-bit machines will not generate code as efficient as that generated
2178 when the compiler is running on a 64-bit machine because many
2179 optimizations that depend on being able to represent a word on the
2180 target in an integral value on the host cannot be performed. Building
2181 cross-compilers on the Alpha for 32-bit machines has only been tested in
2182 a few cases and may not work properly.
2184 @samp{make compare} may fail on old versions of DEC Unix unless you add
2185 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
2186 assembler input file is stored in the object file, and that makes
2187 comparison fail if it differs between the @code{stage1} and
2188 @code{stage2} compilations. The option @option{-save-temps} forces a
2189 fixed name to be used for the assembler input file, instead of a
2190 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
2191 unless the comparisons fail without that option. If you add
2192 @option{-save-temps}, you will have to manually delete the @samp{.i} and
2193 @samp{.s} files after each series of compilations.
2195 GCC now supports both the native (ECOFF) debugging format used by DBX
2196 and GDB and an encapsulated STABS format for use only with GDB@. See the
2197 discussion of the @option{--with-stabs} option of @file{configure} above
2198 for more information on these formats and how to select them.
2200 There is a bug in DEC's assembler that produces incorrect line numbers
2201 for ECOFF format when the @samp{.align} directive is used. To work
2202 around this problem, GCC will not emit such alignment directives
2203 while writing ECOFF format debugging information even if optimization is
2204 being performed. Unfortunately, this has the very undesirable
2205 side-effect that code addresses when @option{-O} is specified are
2206 different depending on whether or not @option{-g} is also specified.
2208 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
2209 DBX@. DEC is now aware of this problem with the assembler and hopes to
2210 provide a fix shortly.
2215 @heading @anchor{alphaev5-cray-unicosmk*}alphaev5-cray-unicosmk*
2216 Cray T3E systems running Unicos/Mk.
2218 This port is incomplete and has many known bugs. We hope to improve the
2219 support for this target soon. Currently, only the C front end is supported,
2220 and it is not possible to build parallel applications. Cray modules are not
2221 supported; in particular, Craylibs are assumed to be in
2222 @file{/opt/ctl/craylibs/craylibs}.
2224 You absolutely @strong{must} use GNU make on this platform. Also, you
2225 need to tell GCC where to find the assembler and the linker. The
2226 simplest way to do so is by providing @option{--with-as} and
2227 @option{--with-ld} to @file{configure}, e.g.@:
2230 configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld \
2231 --enable-languages=c
2234 The comparison test during @samp{make bootstrap} fails on Unicos/Mk
2235 because the assembler inserts timestamps into object files. You should
2236 be able to work around this by doing @samp{make all} after getting this
2242 @heading @anchor{arc-*-elf}arc-*-elf
2243 Argonaut ARC processor.
2244 This configuration is intended for embedded systems.
2249 @heading @anchor{arm-*-elf}arm-*-elf
2250 @heading @anchor{xscale-*-*}xscale-*-*
2251 ARM-family processors. Subtargets that use the ELF object format
2252 require GNU binutils 2.13 or newer. Such subtargets include:
2253 @code{arm-*-freebsd}, @code{arm-*-netbsdelf}, @code{arm-*-*linux},
2254 @code{arm-*-rtems} and @code{arm-*-kaos}.
2259 @heading @anchor{arm-*-coff}arm-*-coff
2260 ARM-family processors. Note that there are two different varieties
2261 of PE format subtarget supported: @code{arm-wince-pe} and
2262 @code{arm-pe} as well as a standard COFF target @code{arm-*-coff}.
2267 @heading @anchor{arm-*-aout}arm-*-aout
2268 ARM-family processors. These targets support the AOUT file format:
2269 @code{arm-*-aout}, @code{arm-*-netbsd}.
2274 @heading @anchor{avr}avr
2276 ATMEL AVR-family micro controllers. These are used in embedded
2277 applications. There are no standard Unix configurations.
2279 @xref{AVR Options,, AVR Options, gcc, Using and Porting the GNU Compiler
2283 See ``AVR Options'' in the main manual
2285 for the list of supported MCU types.
2287 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
2289 Further installation notes and other useful information about AVR tools
2290 can also be obtained from:
2294 @uref{http://www.openavr.org,,http://www.openavr.org}
2296 @uref{http://home.overta.ru/users/denisc/,,http://home.overta.ru/users/denisc/}
2298 @uref{http://www.amelek.gda.pl/avr/,,http://www.amelek.gda.pl/avr/}
2301 We @emph{strongly} recommend using binutils 2.13 or newer.
2303 The following error:
2305 Error: register required
2308 indicates that you should upgrade to a newer version of the binutils.
2313 @heading @anchor{c4x}c4x
2315 Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal
2316 Processors. These are used in embedded applications. There are no
2317 standard Unix configurations.
2319 @xref{TMS320C3x/C4x Options,, TMS320C3x/C4x Options, gcc, Using and
2320 Porting the GNU Compiler Collection (GCC)},
2323 See ``TMS320C3x/C4x Options'' in the main manual
2325 for the list of supported MCU types.
2327 GCC can be configured as a cross compiler for both the C3x and C4x
2328 architectures on the same system. Use @samp{configure --target=c4x
2329 --enable-languages="c,c++"} to configure.
2332 Further installation notes and other useful information about C4x tools
2333 can also be obtained from:
2337 @uref{http://www.elec.canterbury.ac.nz/c4x/,,http://www.elec.canterbury.ac.nz/c4x/}
2343 @heading @anchor{cris}CRIS
2345 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
2346 series. These are used in embedded applications.
2349 @xref{CRIS Options,, CRIS Options, gcc, Using and Porting the GNU Compiler
2353 See ``CRIS Options'' in the main manual
2355 for a list of CRIS-specific options.
2357 There are a few different CRIS targets:
2359 @item cris-axis-aout
2360 Old target. Includes a multilib for the @samp{elinux} a.out-based
2361 target. No multilibs for newer architecture variants.
2363 Mainly for monolithic embedded systems. Includes a multilib for the
2364 @samp{v10} core used in @samp{ETRAX 100 LX}.
2365 @item cris-axis-linux-gnu
2366 A GNU/Linux port for the CRIS architecture, currently targeting
2367 @samp{ETRAX 100 LX} by default.
2370 For @code{cris-axis-aout} and @code{cris-axis-elf} you need binutils 2.11
2371 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
2373 Pre-packaged tools can be obtained from
2374 @uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More
2375 information about this platform is available at
2376 @uref{http://developer.axis.com/}.
2381 @heading @anchor{dos}DOS
2383 Please have a look at our @uref{binaries.html,,binaries page}.
2385 You cannot install GCC by itself on MSDOS; it will not compile under
2386 any MSDOS compiler except itself. You need to get the complete
2387 compilation package DJGPP, which includes binaries as well as sources,
2388 and includes all the necessary compilation tools and libraries.
2393 @heading @anchor{*-*-freebsd*}*-*-freebsd*
2395 The version of binutils installed in @file{/usr/bin} is known to work unless
2396 otherwise specified in any per-architecture notes. However, binutils
2397 2.12.1 or greater is known to improve overall testsuite results.
2399 Support for FreeBSD 1 was discontinued in GCC 3.2.
2401 For FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
2402 configuration support and files as shipped with GCC 2.95 are still in
2403 place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
2404 it is unknown which version of binutils was used (it is assumed that it
2405 was the system copy in @file{/usr/bin}) and C++ EH failures were noted.
2407 For FreeBSD using the ELF file format: DWARF 2 debugging is now the
2408 default for all CPU architectures. It had been the default on
2409 FreeBSD/alpha since its inception. You may use @option{-gstabs} instead
2410 of @option{-g}, if you really want the old debugging format. There are
2411 no known issues with mixing object files and libraries with different
2412 debugging formats. Otherwise, this release of GCC should now match more
2413 of the configuration used in the stock FreeBSD configuration of GCC. In
2414 particular, @option{--enable-threads} is now configured by default.
2415 However, as a general user, do not attempt to replace the system
2416 compiler with this release. Known to bootstrap and check with good
2417 results on FreeBSD 4.8-STABLE and 5-CURRENT@. In the past, known to
2418 bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2,
2419 4.3, 4.4, 4.5-STABLE@.
2421 In principle, @option{--enable-threads} is now compatible with
2422 @option{--enable-libgcj} on FreeBSD@. However, it has only been built
2423 and tested on @samp{i386-*-freebsd[45]} and @samp{alpha-*-freebsd[45]}.
2425 library may be incorrectly built (symbols are missing at link time).
2426 There is a rare timing-based startup hang (probably involves an
2427 assumption about the thread library). Multi-threaded boehm-gc (required for
2428 libjava) exposes severe threaded signal-handling bugs on FreeBSD before
2429 4.5-RELEASE@. Other CPU architectures
2430 supported by FreeBSD will require additional configuration tuning in, at
2431 the very least, both boehm-gc and libffi.
2433 Shared @file{libgcc_s.so} is now built and installed by default.
2438 @heading @anchor{h8300-hms}h8300-hms
2439 Renesas H8/300 series of processors.
2441 Please have a look at our @uref{binaries.html,,binaries page}.
2443 The calling convention and structure layout has changed in release 2.6.
2444 All code must be recompiled. The calling convention now passes the
2445 first three arguments in function calls in registers. Structures are no
2446 longer a multiple of 2 bytes.
2451 @heading @anchor{hppa*-hp-hpux*}hppa*-hp-hpux*
2452 Support for HP-UX version 9 and older was discontinued in GCC 3.4.
2454 We @emph{highly} recommend using gas/binutils 2.8 or newer on all hppa
2455 platforms; you may encounter a variety of problems when using the HP
2458 Specifically, @option{-g} does not work on HP-UX (since that system
2459 uses a peculiar debugging format which GCC does not know about), unless you
2460 use GAS and GDB and configure GCC with the
2461 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
2462 @option{--with-as=@dots{}} options.
2464 If you wish to use the pa-risc 2.0 architecture support with a 32-bit
2465 runtime, you must use either the HP assembler, gas/binutils 2.11 or newer,
2467 @uref{ftp://sources.redhat.com/pub/binutils/snapshots,,snapshot of gas}.
2469 There are two default scheduling models for instructions. These are
2470 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
2471 architecture specified for the target machine when configuring.
2472 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
2473 the target is a @samp{hppa1*} machine.
2475 The PROCESSOR_8000 model is not well suited to older processors. Thus,
2476 it is important to completely specify the machine architecture when
2477 configuring if you want a model other than PROCESSOR_8000. The macro
2478 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
2479 default scheduling model is desired.
2481 More specific information to @samp{hppa*-hp-hpux*} targets follows.
2486 @heading @anchor{hppa*-hp-hpux10}hppa*-hp-hpux10
2488 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
2489 @code{PHCO_19798} from HP@. HP has two sites which provide patches free of
2495 <a href="http://us.itrc.hp.com/service/home/home.do">US, Canada, Asia-Pacific, and
2499 @uref{http://us.itrc.hp.com/service/home/home.do,,} US, Canada, Asia-Pacific,
2503 @uref{http://europe.itrc.hp.com/service/home/home.do,,} Europe.
2506 The HP assembler on these systems has some problems. Most notably the
2507 assembler inserts timestamps into each object file it creates, causing
2508 the 3-stage comparison test to fail during a @samp{make bootstrap}.
2509 You should be able to continue by saying @samp{make all} after getting
2510 the failure from @samp{make bootstrap}.
2516 @heading @anchor{hppa*-hp-hpux11}hppa*-hp-hpux11
2518 GCC 3.0 and up support HP-UX 11. On 64-bit capable systems, there
2519 are two distinct ports. The @samp{hppa2.0w-hp-hpux11*} port generates
2520 code for the 32-bit pa-risc runtime architecture. It uses the HP
2521 linker. The @samp{hppa64-hp-hpux11*} port generates 64-bit code for the
2522 pa-risc 2.0 architecture. The script config.guess now selects the port
2523 type based on the type compiler detected during configuration. You must
2524 set your @env{PATH} or define @env{CC} so that configure finds an appropriate
2525 compiler for the initial bootstrap. Different prefixes must be used if
2526 both ports are to be installed on the same system.
2528 It is best to explicitly configure the @samp{hppa64-hp-hpux11*} target
2529 with the @option{--with-ld=@dots{}} option. We support both the HP
2530 and GNU linkers for this target. The two linkers require different
2531 link commands. Thus, it's not possible to switch linkers during a
2532 GCC build. This has been been reported to occur in a unified build
2533 of binutils and GCC.
2535 GCC 2.95.x is not supported under HP-UX 11 and cannot be used to
2536 compile GCC 3.0 and up. Refer to @uref{binaries.html,,binaries} for
2537 information about obtaining precompiled GCC binaries for HP-UX.
2539 You must use GNU binutils 2.11 or above with the 32-bit port. Thread
2540 support is not currently implemented, so @option{--enable-threads} does
2544 @item @uref{http://gcc.gnu.org/ml/gcc-prs/2002-01/msg00551.html}
2545 @item @uref{http://gcc.gnu.org/ml/gcc-bugs/2002-01/msg00663.html}
2548 GCC 3.3 and later support weak symbols on the 32-bit port using SOM
2549 secondary definition symbols. This feature is not enabled for earlier
2550 versions of HP-UX since there have been bugs in the linker support for
2551 secondary symbols. The HP linker patches @code{PHSS_26559} and
2552 @code{PHSS_24304} for HP-UX 11.00 and 11.11, respectively, correct the
2553 problem of linker core dumps creating C++ libraries. Earlier patches
2554 may work but they have not been tested.
2556 GCC 3.3 nows uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capability
2557 to run initializers and finalizers on the 64-bit port. The feature
2558 requires CVS binutils as of January 2, 2003, or a subsequent release
2559 to correct a problem arising from HP's non-standard use of the .init
2560 and .fini sections. The 32-bit port uses the linker @option{+init}
2561 and @option{+fini} options. As with the support for secondary symbols,
2562 there have been bugs in the order in which these options are executed
2563 by the HP linker. So, again a recent linker patch is recommended.
2565 The HP assembler has many limitations and is not recommended for either
2566 the 32 or 64-bit ports. For example, it does not support weak symbols
2567 or alias definitions. As a result, explicit template instantiations
2568 are required when using C++. This will make it difficult if not
2569 impossible to build many C++ applications. You also can't generate
2570 debugging information when using the HP assembler with GCC.
2572 There are a number of issues to consider in selecting which linker to
2573 use with the 64-bit port. The GNU 64-bit linker can only create dynamic
2574 binaries. The @option{-static} option causes linking with archive
2575 libraries but doesn't produce a truly static binary. Dynamic binaries
2576 still require final binding by the dynamic loader to resolve a set of
2577 dynamic-loader-defined symbols. The default behavior of the HP linker
2578 is the same as the GNU linker. However, it can generate true 64-bit
2579 static binaries using the @option{+compat} option.
2581 The HP 64-bit linker doesn't support linkonce semantics. As a
2582 result, C++ programs have many more sections than they should.
2584 The GNU 64-bit linker has some issues with shared library support
2585 and exceptions. As a result, we only support libgcc in archive
2586 format. For similar reasons, dwarf2 unwind and exception support
2587 are disabled. The GNU linker also has problems creating binaries
2588 with @option{-static}. It doesn't provide stubs for internal
2589 calls to global functions in shared libraries, so these calls
2590 can't be overloaded.
2592 There are several possible approaches to building the distribution.
2593 Binutils can be built first using the HP tools. Then, the GCC
2594 distribution can be built. The second approach is to build GCC
2595 first using the HP tools, then build binutils, then rebuild GCC.
2596 There have been problems with various binary distributions, so
2597 it is best not to start from a binary distribution.
2599 Starting with GCC 3.4 an ISO C compiler is required to bootstrap.
2600 The bundled compiler supports only traditional C; you will need
2601 either HP's unbundled compiler, or a binary distribution of GCC@.
2603 This port still is undergoing significant development.
2608 @heading @anchor{*-*-linux-gnu}*-*-linux-gnu
2610 Versions of libstdc++-v3 starting with 3.2.1 require bugfixes present
2611 in glibc 2.2.5 and later. More information is available in the
2612 libstdc++-v3 documentation.
2617 @heading @anchor{ix86-*-linux*aout}i?86-*-linux*aout
2618 Use this configuration to generate @file{a.out} binaries on Linux-based
2619 GNU systems. This configuration is being superseded.
2624 @heading @anchor{ix86-*-linux*}i?86-*-linux*
2626 As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
2627 See @uref{http://gcc.gnu.org/PR10877,,bug 10877} for more information.
2629 If you receive Signal 11 errors when building on GNU/Linux, then it is
2630 possible you have a hardware problem. Further information on this can be
2631 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
2636 @heading @anchor{ix86-*-sco3.2v5*}i?86-*-sco3.2v5*
2637 Use this for the SCO OpenServer Release 5 family of operating systems.
2639 Unlike earlier versions of GCC, the ability to generate COFF with this
2640 target is no longer provided.
2642 Earlier versions of GCC emitted DWARF 1 when generating ELF to allow
2643 the system debugger to be used. That support was too burdensome to
2644 maintain. GCC now emits only DWARF 2 for this target. This means you
2645 may use either the UDK debugger or GDB to debug programs built by this
2648 GCC is now only supported on releases 5.0.4 and later, and requires that
2649 you install Support Level Supplement OSS646B or later, and Support Level
2650 Supplement OSS631C or later. If you are using release 5.0.7 of
2651 OpenServer, you must have at least the first maintenance pack installed
2652 (this includes the relevant portions of OSS646). OSS646, also known as
2653 the "Execution Environment Update", provides updated link editors and
2654 assemblers, as well as updated standard C and math libraries. The C
2655 startup modules are also updated to support the System V gABI draft, and
2656 GCC relies on that behavior. OSS631 provides a collection of commonly
2657 used open source libraries, some of which GCC depends on (such as GNU
2658 gettext and zlib). SCO OpenServer Release 5.0.7 has all of this built
2659 in by default, but OSS631C and later also apply to that release. Please
2661 @uref{ftp://ftp.sco.com/pub/openserver5,,ftp://ftp.sco.com/pub/openserver5}
2662 for the latest versions of these (and other potentially useful)
2665 Although there is support for using the native assembler, it is
2666 recommended that you configure GCC to use the GNU assembler. You do
2667 this by using the flags
2668 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You should
2669 use a modern version of GNU binutils. Version 2.13.2.1 was used for all
2670 testing. In general, only the @option{--with-gnu-as} option is tested.
2671 A modern bintuils (as well as a plethora of other development related
2672 GNU utilities) can be found in Support Level Supplement OSS658A, the
2673 "GNU Development Tools" package. See the SCO web and ftp sites for details.
2674 That package also contains the currently "officially supported" version of
2675 GCC, version 2.95.3. It is useful for bootstrapping this version.
2680 @heading @anchor{ix86-*-udk}i?86-*-udk
2682 This target emulates the SCO Universal Development Kit and requires that
2683 package be installed. (If it is installed, you will have a
2684 @file{/udk/usr/ccs/bin/cc} file present.) It's very much like the
2685 @samp{i?86-*-unixware7*} target
2686 but is meant to be used when hosting on a system where UDK isn't the
2687 default compiler such as OpenServer 5 or Unixware 2. This target will
2688 generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
2689 with the same warnings and caveats as the SCO UDK@.
2691 This target is a little tricky to build because we have to distinguish
2692 it from the native tools (so it gets headers, startups, and libraries
2693 from the right place) while making the tools not think we're actually
2694 building a cross compiler. The easiest way to do this is with a configure
2698 CC=/udk/usr/ccs/bin/cc @var{/your/path/to}/gcc/configure \
2699 --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-
2702 @emph{You should substitute @samp{i686} in the above command with the appropriate
2703 processor for your host.}
2705 After the usual @samp{make bootstrap} and
2706 @samp{make install}, you can then access the UDK-targeted GCC
2707 tools by adding @command{udk-} before the commonly known name. For
2708 example, to invoke the C compiler, you would use @command{udk-gcc}.
2709 They will coexist peacefully with any native-target GCC tools you may
2716 @heading @anchor{ia64-*-linux}ia64-*-linux
2717 IA-64 processor (also known as IPF, or Itanium Processor Family)
2720 If you are using the optional libunwind library, then you must use
2721 libunwind 0.96 or later.
2723 None of the following versions of GCC has an ABI that is compatible
2724 with any of the other versions in this list, with the exception that
2725 Red Hat 2.96 and Trillian 000171 are compatible with each other:
2726 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
2727 This primarily affects C++ programs and programs that create shared libraries.
2728 GCC 3.1 or later is recommended for compiling linux, the kernel.
2729 As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
2730 more major ABI changes are expected.
2735 @heading @anchor{ia64-*-hpux*}ia64-*-hpux*
2736 Building GCC on this target requires the GNU Assembler. The bundled HP
2737 assembler will not work. To prevent GCC from using the wrong assembler,
2738 the option @option{--with-gnu-as} may be necessary.
2740 The GCC libunwind library has not been ported to HPUX. This means that for
2741 GCC versions 3.2.3 and earlier, @option{--enable-libunwind-exceptions}
2742 is required to build GCC. For GCC 3.3 and later, this is the default.
2746 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
2748 @heading @anchor{*-ibm-aix*}*-ibm-aix*
2749 Support for AIX version 3 and older was discontinued in GCC 3.4.
2751 AIX Make frequently has problems with GCC makefiles. GNU Make 3.79.1 or
2752 newer is recommended to build on this platform.
2754 Errors involving @code{alloca} when building GCC generally are due
2755 to an incorrect definition of @code{CC} in the Makefile or mixing files
2756 compiled with the native C compiler and GCC@. During the stage1 phase of
2757 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
2758 (not @command{xlc}). Once @command{configure} has been informed of
2759 @command{xlc}, one needs to use @samp{make distclean} to remove the
2760 configure cache files and ensure that @env{CC} environment variable
2761 does not provide a definition that will confuse @command{configure}.
2762 If this error occurs during stage2 or later, then the problem most likely
2763 is the version of Make (see above).
2765 The native @command{as} and @command{ld} are recommended for bootstrapping
2766 on AIX 4 and required for bootstrapping on AIX 5L. The GNU Assembler
2767 reports that it supports WEAK symbols on AIX 4, which causes GCC to try to
2768 utilize weak symbol functionality although it is not supported. The GNU
2769 Assembler and Linker do not support AIX 5L sufficiently to bootstrap GCC.
2770 The native AIX tools do interoperate with GCC@.
2772 Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
2773 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1).
2775 @samp{libstdc++} in GCC 3.2 increments the major version number of the
2776 shared object and GCC installation places the @file{libstdc++.a}
2777 shared library in a common location which will overwrite the GCC 3.1
2778 version of the shared library. Applications either need to be
2779 re-linked against the new shared library or the GCC 3.1 version of the
2780 @samp{libstdc++} shared object needs to be available to the AIX
2781 runtime loader. The GCC 3.1 @samp{libstdc++.so.4} shared object can
2782 be installed for runtime dynamic loading using the following steps to
2783 set the @samp{F_LOADONLY} flag in the shared object for @emph{each}
2784 multilib @file{libstdc++.a} installed:
2786 Extract the shared object from each the GCC 3.1 @file{libstdc++.a}
2789 % ar -x libstdc++.a libstdc++.so.4
2792 Enable the @samp{F_LOADONLY} flag so that the shared object will be
2793 available for runtime dynamic loading, but not linking:
2795 % strip -e libstdc++.so.4
2798 Archive the runtime-only shared object in the GCC 3.2
2799 @file{libstdc++.a} archive:
2801 % ar -q libstdc++.a libstdc++.so.4
2804 Linking executables and shared libraries may produce warnings of
2805 duplicate symbols. The assembly files generated by GCC for AIX always
2806 have included multiple symbol definitions for certain global variable
2807 and function declarations in the original program. The warnings should
2808 not prevent the linker from producing a correct library or runnable
2811 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
2812 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
2813 to parse archive libraries did not handle the new format correctly.
2814 These routines are used by GCC and result in error messages during
2815 linking such as ``not a COFF file''. The version of the routines shipped
2816 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
2817 option of the archive command may be used to create archives of 32-bit
2818 objects using the original ``small format''. A correct version of the
2819 routines is shipped with AIX 4.3.2 and above.
2821 Some versions of the AIX binder (linker) can fail with a relocation
2822 overflow severe error when the @option{-bbigtoc} option is used to link
2823 GCC-produced object files into an executable that overflows the TOC@. A fix
2824 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
2825 available from IBM Customer Support and from its
2826 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2827 website as PTF U455193.
2829 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
2830 with a segmentation fault when invoked by any version of GCC@. A fix for
2831 APAR IX87327 is available from IBM Customer Support and from its
2832 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2833 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
2835 The initial assembler shipped with AIX 4.3.0 generates incorrect object
2836 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
2837 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
2838 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2839 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
2841 AIX provides National Language Support (NLS)@. Compilers and assemblers
2842 use NLS to support locale-specific representations of various data
2843 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
2844 separating decimal fractions). There have been problems reported where
2845 GCC does not produce the same floating-point formats that the assembler
2846 expects. If one encounters this problem, set the @env{LANG}
2847 environment variable to @samp{C} or @samp{En_US}.
2849 By default, GCC for AIX 4.1 and above produces code that can be used on
2850 both Power or PowerPC processors.
2852 A default can be specified with the @option{-mcpu=@var{cpu_type}}
2853 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
2858 @heading @anchor{ip2k-*-elf}ip2k-*-elf
2859 Ubicom IP2022 micro controller.
2860 This configuration is intended for embedded systems.
2861 There are no standard Unix configurations.
2863 Use @samp{configure --target=ip2k-elf --enable-languages=c} to configure GCC@.
2868 @heading @anchor{iq2000-*-elf}iq2000-*-elf
2869 Vitesse IQ2000 processors. These are used in embedded
2870 applications. There are no standard Unix configurations.
2875 @heading @anchor{m32r-*-elf}m32r-*-elf
2876 Renesas M32R processor.
2877 This configuration is intended for embedded systems.
2882 @heading @anchor{m6811-elf}m6811-elf
2883 Motorola 68HC11 family micro controllers. These are used in embedded
2884 applications. There are no standard Unix configurations.
2889 @heading @anchor{m6812-elf}m6812-elf
2890 Motorola 68HC12 family micro controllers. These are used in embedded
2891 applications. There are no standard Unix configurations.
2896 @heading @anchor{m68k-hp-hpux}m68k-hp-hpux
2897 HP 9000 series 300 or 400 running HP-UX@. HP-UX version 8.0 has a bug in
2898 the assembler that prevents compilation of GCC@. This
2899 bug manifests itself during the first stage of compilation, while
2900 building @file{libgcc2.a}:
2904 cc1: warning: `-g' option not supported on this version of GCC
2905 cc1: warning: `-g1' option not supported on this version of GCC
2906 ./xgcc: Internal compiler error: program as got fatal signal 11
2909 A patched version of the assembler is available as the file
2910 @uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you
2911 have HP software support, the patch can also be obtained directly from
2912 HP, as described in the following note:
2915 This is the patched assembler, to patch SR#1653-010439, where the
2916 assembler aborts on floating point constants.
2918 The bug is not really in the assembler, but in the shared library
2919 version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is
2920 SR#4701-078451. Anyway, the attached assembler uses the archive
2921 library version of ``cvtnum(3c)'' and thus does not exhibit the bug.
2924 This patch is also known as PHCO_4484.
2926 In addition gdb does not understand that native HP-UX format, so
2927 you must use gas if you wish to use gdb.
2929 On HP-UX version 8.05, but not on 8.07 or more recent versions, the
2930 @command{fixproto} shell script triggers a bug in the system shell. If you
2931 encounter this problem, upgrade your operating system or use BASH (the
2932 GNU shell) to run @command{fixproto}. This bug will cause the fixproto
2933 program to report an error of the form:
2936 ./fixproto: sh internal 1K buffer overflow
2939 To fix this, you can also change the first line of the fixproto script
2949 @heading @anchor{mips-*-*}mips-*-*
2950 If on a MIPS system you get an error message saying ``does not have gp
2951 sections for all it's [sic] sectons [sic]'', don't worry about it. This
2952 happens whenever you use GAS with the MIPS linker, but there is not
2953 really anything wrong, and it is okay to use the output file. You can
2954 stop such warnings by installing the GNU linker.
2956 It would be nice to extend GAS to produce the gp tables, but they are
2957 optional, and there should not be a warning about their absence.
2959 The libstdc++ atomic locking routines for MIPS targets requires MIPS II
2960 and later. A patch went in just after the GCC 3.3 release to
2961 make @samp{mips*-*-*} use the generic implementation instead. You can also
2962 configure for @samp{mipsel-elf} as a workaround. The
2963 @samp{mips*-*-linux*} target continues to use the MIPS II routines. More
2964 work on this is expected in future releases.
2966 Cross-compilers for the Mips as target using the Mips assembler
2967 currently do not work, because the auxiliary programs
2968 @file{mips-tdump.c} and @file{mips-tfile.c} can't be compiled on
2969 anything but a Mips. It does work to cross compile for a Mips
2970 if you use the GNU assembler and linker.
2975 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
2977 This configuration has considerable problems, which will be fixed in a
2980 In order to compile GCC on an SGI running IRIX 5, the ``compiler_dev.hdr''
2981 subsystem must be installed from the IDO CD-ROM supplied by Silicon
2982 Graphics. It is also available for download from
2983 @uref{http://www.sgi.com/developers/devtools/apis/ido.html,,http://www.sgi.com/developers/devtools/apis/ido.html}.
2985 @samp{make compare} may fail on version 5 of IRIX unless you add
2986 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
2987 assembler input file is stored in the object file, and that makes
2988 comparison fail if it differs between the @code{stage1} and
2989 @code{stage2} compilations. The option @option{-save-temps} forces a
2990 fixed name to be used for the assembler input file, instead of a
2991 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
2992 unless the comparisons fail without that option. If you do you
2993 @option{-save-temps}, you will have to manually delete the @samp{.i} and
2994 @samp{.s} files after each series of compilations.
2996 If you use the MIPS C compiler to bootstrap, it may be necessary
2997 to increase its table size for switch statements with the
2998 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
2999 optimization option, you also need to use @option{-Olimit 3000}.
3001 To enable debugging under IRIX 5, you must use GNU @command{as} 2.11.2
3003 and use the @option{--with-gnu-as} configure option when configuring GCC.
3004 GNU @command{as} is distributed as part of the binutils package.
3005 When using release 2.11.2, you need to apply a patch
3006 @uref{http://sources.redhat.com/ml/binutils/2001-07/msg00352.html,,http://sources.redhat.com/ml/binutils/2001-07/msg00352.html}
3007 which will be included in the next release of binutils.
3009 When building GCC, the build process loops rebuilding @command{cc1} over
3010 and over again. This happens on @samp{mips-sgi-irix5.2}, and possibly
3011 other platforms. It has been reported that this is a known bug in the
3012 @command{make} shipped with IRIX 5.2. We recommend you use GNU
3013 @command{make} instead of the vendor supplied @command{make} program;
3014 however, you may have success with @command{smake} on IRIX 5.2 if you do
3015 not have GNU @command{make} available.
3020 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
3022 If you are using IRIX @command{cc} as your bootstrap compiler, you must
3023 ensure that the N32 ABI is in use. To test this, compile a simple C
3024 file with @command{cc} and then run @command{file} on the
3025 resulting object file. The output should look like:
3028 test.o: ELF N32 MSB @dots{}
3034 test.o: ELF 32-bit MSB @dots{}
3040 test.o: ELF 64-bit MSB @dots{}
3043 then your version of @command{cc} uses the O32 or N64 ABI by default. You
3044 should set the environment variable @env{CC} to @samp{cc -n32}
3045 before configuring GCC@.
3047 If you want the resulting @command{gcc} to run on old 32-bit systems
3048 with the MIPS R4400 CPU, you need to ensure that only code for the mips3
3049 instruction set architecture (ISA) is generated. While GCC 3.x does
3050 this correctly, both GCC 2.95 and SGI's MIPSpro @command{cc} may change
3051 the ISA depending on the machine where GCC is built. Using one of them
3052 as the bootstrap compiler may result in mips4 code, which won't run at
3053 all on mips3-only systems. For the test program above, you should see:
3056 test.o: ELF N32 MSB mips-3 @dots{}
3062 test.o: ELF N32 MSB mips-4 @dots{}
3065 instead, you should set the environment variable @env{CC} to @samp{cc
3066 -n32 -mips3} or @samp{gcc -mips3} respectively before configuring GCC@.
3068 GCC on IRIX 6 is usually built to support both the N32 and N64 ABIs. If
3069 you build GCC on a system that doesn't have the N64 libraries installed,
3070 you need to configure with @option{--disable-multilib} so GCC doesn't
3071 try to use them. Look for @file{/usr/lib64/libc.so.1} to see if you
3072 have the 64-bit libraries installed.
3074 You must @emph{not} use GNU @command{as} (which isn't built anyway as of
3075 binutils 2.11.2) on IRIX 6 platforms; doing so will only cause problems.
3077 GCC does not currently support generating O32 ABI binaries in the
3078 @samp{mips-sgi-irix6} configurations. It is possible to create a GCC
3079 with O32 ABI only support by configuring it for the @samp{mips-sgi-irix5}
3080 target and using a patched GNU @command{as} 2.11.2 as documented in the
3081 @uref{#mips-sgi-irix5,,@samp{mips-sgi-irix5}} section above. Using the
3082 native assembler requires patches to GCC which will be included in a
3083 future release. It is
3084 expected that O32 ABI support will be available again in a future release.
3086 The @option{--enable-threads} option doesn't currently work, a patch is
3087 in preparation for a future release. The @option{--enable-libgcj}
3088 option is disabled by default: IRIX 6 uses a very low default limit
3089 (20480) for the command line length. Although libtool contains a
3090 workaround for this problem, at least the N64 @samp{libgcj} is known not
3091 to build despite this, running into an internal error of the native
3092 @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
3093 its maximum of 262144 bytes. If you have root access, you can use the
3094 @command{systune} command to do this.
3096 GCC does not correctly pass/return structures which are
3097 smaller than 16 bytes and which are not 8 bytes. The problem is very
3098 involved and difficult to fix. It affects a number of other targets also,
3099 but IRIX 6 is affected the most, because it is a 64-bit target, and 4 byte
3100 structures are common. The exact problem is that structures are being padded
3101 at the wrong end, e.g.@: a 4 byte structure is loaded into the lower 4 bytes
3102 of the register when it should be loaded into the upper 4 bytes of the
3105 GCC is consistent with itself, but not consistent with the SGI C compiler
3106 (and the SGI supplied runtime libraries), so the only failures that can
3107 happen are when there are library functions that take/return such
3108 structures. There are very few such library functions. Currently this
3109 is known to affect @code{inet_ntoa}, @code{inet_lnaof},
3110 @code{inet_netof}, @code{inet_makeaddr}, and @code{semctl}. Until the
3111 bug is fixed, GCC contains workarounds for the known affected functions.
3113 See @uref{http://freeware.sgi.com/,,http://freeware.sgi.com/} for more
3114 information about using GCC on IRIX platforms.
3119 @heading @anchor{powerpc*-*-*}powerpc-*-*
3121 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
3122 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
3127 @heading @anchor{powerpc-*-darwin*}powerpc-*-darwin*
3128 PowerPC running Darwin (Mac OS X kernel).
3130 Pre-installed versions of Mac OS X may not include any developer tools,
3131 meaning that you will not be able to build GCC from source. Tool
3132 binaries are available at
3133 @uref{http://developer.apple.com/tools/compilers.html} (free
3134 registration required).
3136 The default stack limit of 512K is too small, which may cause compiles
3137 to fail with 'Bus error'. Set the stack larger, for instance
3138 by doing @samp{limit stack 800}. It's a good idea to use the GNU
3139 preprocessor instead of Apple's @file{cpp-precomp} during the first stage of
3140 bootstrapping; this is automatic when doing @samp{make bootstrap}, but
3141 to do it from the toplevel objdir you will need to say @samp{make
3142 CC='cc -no-cpp-precomp' bootstrap}.
3144 The version of GCC shipped by Apple typically includes a number of
3145 extensions not available in a standard GCC release. These extensions
3146 are generally specific to Mac programming.
3151 @heading @anchor{powerpc-*-elf}powerpc-*-elf, powerpc-*-sysv4
3152 PowerPC system in big endian mode, running System V.4.
3157 @heading @anchor{powerpc-*-linux-gnu*}powerpc-*-linux-gnu*
3160 @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.13.90.0.10}
3161 or newer for a working GCC@.
3166 @heading @anchor{powerpc-*-netbsd*}powerpc-*-netbsd*
3167 PowerPC system in big endian mode running NetBSD@. To build the
3168 documentation you will need Texinfo version 4.2 (NetBSD 1.5.1 included
3169 Texinfo version 3.12).
3174 @heading @anchor{powerpc-*-eabisim}powerpc-*-eabisim
3175 Embedded PowerPC system in big endian mode for use in running under the
3181 @heading @anchor{powerpc-*-eabi}powerpc-*-eabi
3182 Embedded PowerPC system in big endian mode.
3187 @heading @anchor{powerpcle-*-elf}powerpcle-*-elf, powerpcle-*-sysv4
3188 PowerPC system in little endian mode, running System V.4.
3193 @heading @anchor{powerpcle-*-eabisim}powerpcle-*-eabisim
3194 Embedded PowerPC system in little endian mode for use in running under
3200 @heading @anchor{powerpcle-*-eabi}powerpcle-*-eabi
3201 Embedded PowerPC system in little endian mode.
3206 @heading @anchor{s390-*-linux*}s390-*-linux*
3207 S/390 system running GNU/Linux for S/390@.
3212 @heading @anchor{s390x-*-linux*}s390x-*-linux*
3213 zSeries system (64-bit) running GNU/Linux for zSeries@.
3218 @heading @anchor{s390x-ibm-tpf*}s390x-ibm-tpf*
3219 zSeries system (64-bit) running TPF. This platform is
3220 supported as cross-compilation target only.
3225 @c Please use Solaris 2 to refer to all release of Solaris, starting
3226 @c with 2.0 until 2.6, 7, and 8. Solaris 1 was a marketing name for
3227 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
3228 @c alone is too unspecific and must be avoided.
3229 @heading @anchor{*-*-solaris2*}*-*-solaris2*
3231 Sun does not ship a C compiler with Solaris 2. To bootstrap and install
3232 GCC you first have to install a pre-built compiler, see our
3233 @uref{binaries.html,,binaries page} for details.
3235 The Solaris 2 @command{/bin/sh} will often fail to configure
3236 @file{libstdc++-v3}, @file{boehm-gc} or @file{libjava}. We therefore
3237 recommend to use the following sequence of commands to bootstrap and
3241 % CONFIG_SHELL=/bin/ksh
3242 % export CONFIG_SHELL
3245 and then proceed as described in @uref{build.html,,the build instructions},
3246 where we strongly recommend using GNU make and specifying an absolute path
3247 to invoke @var{srcdir}/configure.
3249 Solaris 2 comes with a number of optional OS packages. Some of these
3250 are needed to use GCC fully, namely @code{SUNWarc},
3251 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
3252 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
3253 optional packages when installing Solaris 2, you will need to verify that
3254 the packages that GCC needs are installed.
3256 To check whether an optional package is installed, use
3257 the @command{pkginfo} command. To add an optional package, use the
3258 @command{pkgadd} command. For further details, see the Solaris 2
3261 Trying to use the linker and other tools in
3262 @file{/usr/ucb} to install GCC has been observed to cause trouble.
3263 For example, the linker may hang indefinitely. The fix is to remove
3264 @file{/usr/ucb} from your @env{PATH}.
3266 The build process works more smoothly with the legacy Sun tools so, if you
3267 have @file{/usr/xpg4/bin} in your @env{PATH}, we recommend that you place
3268 @file{/usr/bin} before @file{/usr/xpg4/bin} for the duration of the build.
3270 All releases of GNU binutils prior to 2.11.2 have known bugs on this
3271 platform. We recommend the use of GNU binutils 2.11.2 or the vendor
3272 tools (Sun @command{as}, Sun @command{ld}).
3274 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3275 newer: @command{g++} will complain that types are missing. These headers assume
3276 that omitting the type means @code{int}; this assumption worked for C89 but
3277 is wrong for C++, and is now wrong for C99 also.
3279 @command{g++} accepts such (invalid) constructs with the option
3280 @option{-fpermissive}; it
3281 will assume that any missing type is @code{int} (as defined by C89).
3283 There are patches for Solaris 2.6 (105633-56 or newer for SPARC,
3284 106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC,
3285 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
3286 108653-22 for Intel) that fix this bug.
3291 @heading @anchor{sparc-sun-solaris2*}sparc-sun-solaris2*
3293 When GCC is configured to use binutils 2.11.2 or later the binaries
3294 produced are smaller than the ones produced using Sun's native tools;
3295 this difference is quite significant for binaries containing debugging
3298 Sun @command{as} 4.x is broken in that it cannot cope with long symbol names.
3299 A typical error message might look similar to the following:
3302 /usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error:
3303 can't compute value of an expression involving an external symbol.
3306 This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris
3307 2.6 and has been fixed in later (5.x) versions of the assembler,
3308 starting with Solaris 7.
3310 Starting with Solaris 7, the operating system is capable of executing
3311 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
3312 this; the @option{-m64} option enables 64-bit code generation.
3313 However, if all you want is code tuned for the UltraSPARC CPU, you
3314 should try the @option{-mtune=ultrasparc} option instead, which produces
3315 code that, unlike full 64-bit code, can still run on non-UltraSPARC
3318 When configuring on a Solaris 7 or later system that is running a kernel
3319 that supports only 32-bit binaries, one must configure with
3320 @option{--disable-multilib}, since we will not be able to build the
3321 64-bit target libraries.
3326 @heading @anchor{sparc-sun-solaris2.7}sparc-sun-solaris2.7
3328 Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
3329 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
3330 and later, including all EGCS releases. Sun formerly recommended
3331 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
3332 recommend it only for people who use Sun's compilers.
3334 Here are some workarounds to this problem:
3337 Do not install Sun patch 107058-01 until after Sun releases a
3338 complete patch for bug 4210064. This is the simplest course to take,
3339 unless you must also use Sun's C compiler. Unfortunately 107058-01
3340 is preinstalled on some new Solaris 7-based hosts, so you may have to
3344 Copy the original, unpatched Solaris 7
3345 @command{/usr/ccs/bin/as} into
3346 @command{/usr/local/libexec/gcc/sparc-sun-solaris2.7/3.4/as},
3347 adjusting the latter name to fit your local conventions and software
3351 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
3352 both 107058-01 and 106950-03 installed has reported the bug with GCC
3353 and Sun's dynamic linker. This last course of action is riskiest,
3354 for two reasons. First, you must install 106950 on all hosts that
3355 run code generated by GCC; it doesn't suffice to install it only on
3356 the hosts that run GCC itself. Second, Sun says that 106950-03 is
3357 only a partial fix for bug 4210064, but Sun doesn't know whether the
3358 partial fix is adequate for GCC@. Revision -08 or later should fix
3359 the bug. The current (as of 2001-09-24) revision is -14, and is included in
3360 the Solaris 7 Recommended Patch Cluster.
3363 GCC 3.3 triggers a bug in version 5.0 Alpha 03/27/98 of the Sun assembler,
3364 which causes a bootstrap failure when linking the 64-bit shared version of
3365 libgcc. A typical error message is:
3368 ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o:
3369 symbol <unknown>: offset 0xffffffff7ec133e7 is non-aligned.
3372 This bug has been fixed in the final 5.0 version of the assembler.
3377 @heading @anchor{sparc-*-linux*}sparc-*-linux*
3379 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
3380 or newer on this platform. All earlier binutils and glibc
3381 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
3387 @heading @anchor{sparc64-*-solaris2*}sparc64-*-solaris2*
3389 The following compiler flags must be specified in the configure
3390 step in order to bootstrap this target with the Sun compiler:
3393 % CC="cc -xildoff -xarch=v9" @var{srcdir}/configure [@var{options}] [@var{target}]
3396 @option{-xildoff} turns off the incremental linker, and @option{-xarch=v9}
3397 specifies the SPARC-V9 architecture to the Sun linker and assembler.
3402 @heading @anchor{sparcv9-*-solaris2*}sparcv9-*-solaris2*
3404 This is a synonym for sparc64-*-solaris2*.
3409 @heading @anchor{#*-*-sysv*}*-*-sysv*
3410 On System V release 3, you may get this error message
3414 ld fatal: failed to write symbol name @var{something}
3415 in strings table for file @var{whatever}
3418 This probably indicates that the disk is full or your ulimit won't allow
3419 the file to be as large as it needs to be.
3421 This problem can also result because the kernel parameter @code{MAXUMEM}
3422 is too small. If so, you must regenerate the kernel and make the value
3423 much larger. The default value is reported to be 1024; a value of 32768
3424 is said to work. Smaller values may also work.
3426 On System V, if you get an error like this,
3429 /usr/local/lib/bison.simple: In function `yyparse':
3430 /usr/local/lib/bison.simple:625: virtual memory exhausted
3434 that too indicates a problem with disk space, ulimit, or @code{MAXUMEM}.
3436 On a System V release 4 system, make sure @file{/usr/bin} precedes
3437 @file{/usr/ucb} in @code{PATH}. The @command{cc} command in
3438 @file{/usr/ucb} uses libraries which have bugs.
3443 @heading @anchor{vax-dec-ultrix}vax-dec-ultrix
3444 Don't try compiling with VAX C (@command{vcc}). It produces incorrect code
3445 in some cases (for example, when @code{alloca} is used).
3450 @heading @anchor{*-*-vxworks*}*-*-vxworks*
3451 Support for VxWorks is in flux. At present GCC supports @emph{only} the
3452 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC.
3453 We welcome patches for other architectures supported by VxWorks 5.5.
3454 Support for VxWorks AE would also be welcome; we believe this is merely
3455 a matter of writing an appropriate ``configlette'' (see below). We are
3456 not interested in supporting older, a.out or COFF-based, versions of
3459 VxWorks comes with an older version of GCC installed in
3460 @file{@var{$WIND_BASE}/host}; we recommend you do not overwrite it.
3461 Choose an installation @var{prefix} entirely outside @var{$WIND_BASE}.
3462 Before running @command{configure}, create the directories @file{@var{prefix}}
3463 and @file{@var{prefix}/bin}. Link or copy the appropriate assembler,
3464 linker, etc. into @file{@var{prefix}/bin}, and set your @var{PATH} to
3465 include that directory while running both @command{configure} and
3468 You must give @command{configure} the
3469 @option{--with-headers=@var{$WIND_BASE}/target/h} switch so that it can
3470 find the VxWorks system headers. Since VxWorks is a cross compilation
3471 target only, you must also specify @option{--target=@var{target}}.
3472 @command{configure} will attempt to create the directory
3473 @file{@var{prefix}/@var{target}/sys-include} and copy files into it;
3474 make sure the user running @command{configure} has sufficient privilege
3477 GCC's exception handling runtime requires a special ``configlette''
3478 module, @file{contrib/gthr_supp_vxw_5x.c}. Follow the instructions in
3479 that file to add the module to your kernel build. (Future versions of
3480 VxWorks will incorporate this module.)
3485 @heading @anchor{x86_64-*-*}x86_64-*-*, amd64-*-*
3487 GCC supports the x86-64 architecture implemented by the AMD64 processor
3488 (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD.
3489 On GNU/Linux the default is a bi-arch compiler which is able to generate
3490 both 64-bit x86-64 and 32-bit x86 code (via the @option{-m32} switch).
3495 @heading @anchor{xtensa-*-elf}xtensa-*-elf
3497 This target is intended for embedded Xtensa systems using the
3498 @samp{newlib} C library. It uses ELF but does not support shared
3499 objects. Designed-defined instructions specified via the
3500 Tensilica Instruction Extension (TIE) language are only supported
3501 through inline assembly.
3503 The Xtensa configuration information must be specified prior to
3504 building GCC@. The @file{include/xtensa-config.h} header
3505 file contains the configuration information. If you created your
3506 own Xtensa configuration with the Xtensa Processor Generator, the
3507 downloaded files include a customized copy of this header file,
3508 which you can use to replace the default header file.
3513 @heading @anchor{xtensa-*-linux*}xtensa-*-linux*
3515 This target is for Xtensa systems running GNU/Linux. It supports ELF
3516 shared objects and the GNU C library (glibc). It also generates
3517 position-independent code (PIC) regardless of whether the
3518 @option{-fpic} or @option{-fPIC} options are used. In other
3519 respects, this target is the same as the
3520 @uref{#xtensa-*-elf,,@samp{xtensa-*-elf}} target.
3525 @heading @anchor{windows}Microsoft Windows (32-bit)
3527 A port of GCC 2.95.2 and 3.x is included with the
3528 @uref{http://www.cygwin.com/,,Cygwin environment}.
3530 Current (as of early 2001) snapshots of GCC will build under Cygwin
3531 without modification.
3533 GCC does not currently build with Microsoft's C++ compiler and there
3534 are no plans to make it do so.
3539 @heading @anchor{os2}OS/2
3541 GCC does not currently support OS/2. However, Andrew Zabolotny has been
3542 working on a generic OS/2 port with pgcc. The current code can be found
3543 at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
3545 An older copy of GCC 2.8.1 is included with the EMX tools available at
3546 @uref{ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/,,
3547 ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/}.
3552 @heading @anchor{older}Older systems
3554 GCC contains support files for many older (1980s and early
3555 1990s) Unix variants. For the most part, support for these systems
3556 has not been deliberately removed, but it has not been maintained for
3557 several years and may suffer from bitrot.
3559 Starting with GCC 3.1, each release has a list of ``obsoleted'' systems.
3560 Support for these systems is still present in that release, but
3561 @command{configure} will fail unless the @option{--enable-obsolete}
3562 option is given. Unless a maintainer steps forward, support for these
3563 systems will be removed from the next release of GCC@.
3565 Support for old systems as hosts for GCC can cause problems if the
3566 workarounds for compiler, library and operating system bugs affect the
3567 cleanliness or maintainability of the rest of GCC@. In some cases, to
3568 bring GCC up on such a system, if still possible with current GCC, may
3569 require first installing an old version of GCC which did work on that
3570 system, and using it to compile a more recent GCC, to avoid bugs in the
3571 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
3572 @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror
3573 sites}. Header bugs may generally be avoided using
3574 @command{fixincludes}, but bugs or deficiencies in libraries and the
3575 operating system may still cause problems.
3577 Support for older systems as targets for cross-compilation is less
3578 problematic than support for them as hosts for GCC; if an enthusiast
3579 wishes to make such a target work again (including resurrecting any of
3580 the targets that never worked with GCC 2, starting from the last CVS
3581 version before they were removed), patches
3582 @uref{../contribute.html,,following the usual requirements} would be
3583 likely to be accepted, since they should not affect the support for more
3586 For some systems, old versions of GNU binutils may also be useful,
3587 and are available from @file{pub/binutils/old-releases} on
3588 @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}.
3590 Some of the information on specific systems above relates to
3591 such older systems, but much of the information
3592 about GCC on such systems (which may no longer be applicable to
3593 current GCC) is to be found in the GCC texinfo manual.
3598 @heading @anchor{elf_targets}all ELF targets (SVR4, Solaris 2, etc.)
3600 C++ support is significantly better on ELF targets if you use the
3601 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
3602 inlines, vtables and template instantiations will be discarded
3611 @uref{./index.html,,Return to the GCC Installation page}
3615 @c ***Old documentation******************************************************
3617 @include install-old.texi
3623 @uref{./index.html,,Return to the GCC Installation page}
3627 @c ***GFDL********************************************************************
3635 @uref{./index.html,,Return to the GCC Installation page}
3639 @c ***************************************************************************
3640 @c Part 6 The End of the Document
3642 @comment node-name, next, previous, up
3643 @node Concept Index, , GNU Free Documentation License, Top
3647 @unnumbered Concept Index