1 \input texinfo.tex @c -*-texinfo-*-
4 @setfilename install.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
18 @settitle Downloading GCC
21 @settitle Installing GCC: Configuration
24 @settitle Installing GCC: Building
27 @settitle Installing GCC: Testing
29 @ifset finalinstallhtml
30 @settitle Installing GCC: Final installation
33 @settitle Installing GCC: Binaries
36 @settitle Installing GCC: Old documentation
39 @settitle Installing GCC: GNU Free Documentation License
42 @c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
43 @c 1999, 2000, 2001, 2002 Free Software Foundation, Inc.
44 @c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com
46 @c Include everything if we're not making html
60 @c Part 2 Summary Description and Copyright
61 @macro copyrightnotice
62 Copyright @copyright{} 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
63 1999, 2000, 2001, 2002 Free Software Foundation, Inc.
65 Permission is granted to copy, distribute and/or modify this document
66 under the terms of the GNU Free Documentation License, Version 1.1 or
67 any later version published by the Free Software Foundation; with no
68 Invariant Sections, the Front-Cover texts being (a) (see below), and
69 with the Back-Cover Texts being (b) (see below). A copy of the
70 license is included in the section entitled ``@uref{./gfdl.html,,GNU
71 Free Documentation License}''.
73 (a) The FSF's Front-Cover Text is:
77 (b) The FSF's Back-Cover Text is:
79 You have freedom to copy and modify this GNU Manual, like GNU
80 software. Copies published by the Free Software Foundation raise
81 funds for GNU development.
87 @c Part 3 Titlepage and Copyright
90 @comment The title is printed in a large font.
91 @center @titlefont{Installing GCC}
93 @c The following two commands start the copyright page.
95 @vskip 0pt plus 1filll
99 @c Part 4 Top node and Master Menu
102 @comment node-name, next, Previous, up
105 * Installing GCC:: This document describes the generic installation
106 procedure for GCC as well as detailing some target
107 specific installation instructions.
109 * Specific:: Host/target specific installation notes for GCC.
110 * Binaries:: Where to get pre-compiled binaries.
112 * Old:: Old installation documentation.
114 * GNU Free Documentation License:: How you can copy and share this manual.
115 * Concept Index:: This index has two entries.
119 @c Part 5 The Body of the Document
120 @c ***Installing GCC**********************************************************
122 @comment node-name, next, previous, up
123 @node Installing GCC, Binaries, , Top
127 @chapter Installing GCC
130 The latest version of this document is always available at
131 @uref{http://gcc.gnu.org/install/,,http://gcc.gnu.org/install/}.
133 This document describes the generic installation procedure for GCC as well
134 as detailing some target specific installation instructions.
136 GCC includes several components that previously were separate distributions
137 with their own installation instructions. This document supersedes all
138 package specific installation instructions.
140 @emph{Before} starting the build/install procedure please check the
142 @ref{Specific, host/target specific installation notes}.
145 @uref{specific.html,,host/target specific installation notes}.
147 We recommend you browse the entire generic installation instructions before
150 Lists of successful builds for released versions of GCC are
151 available at our web pages for
152 @uref{http://gcc.gnu.org/gcc-3.1/buildstat.html,,3.1},
153 @uref{http://gcc.gnu.org/gcc-3.0/buildstat.html,,3.0}
155 @uref{http://gcc.gnu.org/gcc-2.95/buildstat.html,,2.95}.
156 These lists are updated as new information becomes available.
158 The installation procedure itself is broken into five steps.
162 * Downloading the source::
165 * Testing:: (optional)
172 @uref{download.html,,Downloading the source}
174 @uref{configure.html,,Configuration}
176 @uref{build.html,,Building}
178 @uref{test.html,,Testing} (optional)
180 @uref{finalinstall.html,,Final install}
184 Please note that GCC does not support @samp{make uninstall} and probably
185 won't do so in the near future as this would open a can of worms. Instead,
186 we suggest that you install GCC into a directory of its own and simply
187 remove that directory when you do not need that specific version of GCC
188 any longer, and, if shared libraries are installed there as well, no
189 more binaries exist that use them.
192 There are also some @uref{old.html,,old installation instructions},
193 which are mostly obsolete but still contain some information which has
194 not yet been merged into the main part of this manual.
202 @uref{./index.html,,Return to the GCC Installation page}
208 @c ***Downloading the source**************************************************
210 @comment node-name, next, previous, up
211 @node Downloading the source, Configuration, , Installing GCC
215 @chapter Downloading GCC
217 @cindex Downloading GCC
218 @cindex Downloading the Source
220 GCC is distributed via @uref{http://gcc.gnu.org/cvs.html,,CVS} and FTP
221 tarballs compressed with @command{gzip} or
222 @command{bzip2}. It is possible to download a full distribution or specific
225 Please refer to our @uref{http://gcc.gnu.org/releases.html,,releases web page}
226 for information on how to obtain GCC@.
228 The full distribution includes the C, C++, Objective-C, Fortran, Java,
229 and Ada (in case of GCC 3.1 and later) compilers. The full distribution
230 also includes runtime libraries for C++, Objective-C, Fortran, and Java.
231 In GCC 3.0 and later versions, GNU compiler testsuites are also included
232 in the full distribution.
234 If you choose to download specific components, you must download the core
235 GCC distribution plus any language specific distributions you wish to
236 use. The core distribution includes the C language front end as well as the
237 shared components. Each language has a tarball which includes the language
238 front end as well as the language runtime (when appropriate).
240 Unpack the core distribution as well as any language specific
241 distributions in the same directory.
243 If you also intend to build binutils (either to upgrade an existing
244 installation or for use in place of the corresponding tools of your
245 OS), unpack the binutils distribution either in the same directory or
246 a separate one. In the latter case, add symbolic links to any
247 components of the binutils you intend to build alongside the compiler
248 (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
249 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
256 @uref{./index.html,,Return to the GCC Installation page}
260 @c ***Configuration***********************************************************
262 @comment node-name, next, previous, up
263 @node Configuration, Building, Downloading the source, Installing GCC
267 @chapter Installing GCC: Configuration
269 @cindex Configuration
270 @cindex Installing GCC: Configuration
272 Like most GNU software, GCC must be configured before it can be built.
273 This document describes the recommended configuration procedure
274 for both native and cross targets.
276 We use @var{srcdir} to refer to the toplevel source directory for
277 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
279 If you obtained the sources via CVS, @var{srcdir} must refer to the top
280 @file{gcc} directory, the one where the @file{MAINTAINERS} can be found,
281 and not its @file{gcc} subdirectory, otherwise the build will fail.
283 If either @var{srcdir} or @var{objdir} is located on an automounted NFS
284 file system, the shell's built-in @command{pwd} command will return
285 temporary pathnames. Using these can lead to various sorts of build
286 problems. To avoid this issue, set the @env{PWDCMD} environment
287 variable to an automounter-aware @command{pwd} command, e.g.,
288 @command{pawd} or @command{amq -w}, during the configuration and build
291 First, in general, GCC @strong{must} be built into a separate directory
292 than the sources which does @strong{not} reside within the source tree.
293 This is how almost all developers build GCC; building where @var{srcdir}
294 == @var{objdir} is completely unsupported; building where @var{objdir}
295 is a subdirectory of @var{srcdir} is completely unsupported.
297 If you have previously built GCC in the same directory for a
298 different target machine, do @samp{make distclean} to delete all files
299 that might be invalid. One of the files this deletes is
300 @file{Makefile}; if @samp{make distclean} complains that @file{Makefile}
301 does not exist, it probably means that the directory is already suitably
302 clean. However, with the recommended method of building in a separate
303 @var{objdir}, you should simply use a different @var{objdir} for each
306 Second, when configuring a native system, either @command{cc} or
307 @command{gcc} must be in your path or you must set @env{CC} in
308 your environment before running configure. Otherwise the configuration
311 Note that the bootstrap compiler and the resulting GCC must be link
312 compatible, else the bootstrap will fail with linker errors about
313 incompatible object file formats. Several multilibed targets are
314 affected by this requirement, see
316 @ref{Specific, host/target specific installation notes}.
319 @uref{specific.html,,host/target specific installation notes}.
327 % @var{srcdir}/configure [@var{options}] [@var{target}]
331 @heading Target specification
334 GCC has code to correctly determine the correct value for @var{target}
335 for nearly all native systems. Therefore, we highly recommend you not
336 provide a configure target when configuring a native compiler.
339 @var{target} must be specified as @option{--target=@var{target}}
340 when configuring a cross compiler; examples of valid targets would be
341 i960-rtems, m68k-coff, sh-elf, etc.
344 Specifying just @var{target} instead of @option{--target=@var{target}}
345 implies that the host defaults to @var{target}.
349 @heading Options specification
351 Use @var{options} to override several configure time options for
352 GCC@. A list of supported @var{options} follows; @command{configure
353 --help} may list other options, but those not listed below may not
354 work and should not normally be used.
357 @item --prefix=@var{dirname}
358 Specify the toplevel installation
359 directory. This is the recommended way to install the tools into a directory
360 other than the default. The toplevel installation directory defaults to
363 We @strong{highly} recommend against @var{dirname} being the same or a
364 subdirectory of @var{objdir} or vice versa.
366 These additional options control where certain parts of the distribution
367 are installed. Normally you should not need to use these options.
370 @item --exec-prefix=@var{dirname}
371 Specify the toplevel installation directory for architecture-dependent
372 files. The default is @file{@var{prefix}}.
374 @item --bindir=@var{dirname}
375 Specify the installation directory for the executables called by users
376 (such as @command{gcc} and @command{g++}). The default is
377 @file{@var{exec-prefix}/bin}.
379 @item --libdir=@var{dirname}
380 Specify the installation directory for object code libraries and
381 internal parts of GCC@. The default is @file{@var{exec-prefix}/lib}.
383 @item --with-slibdir=@var{dirname}
384 Specify the installation directory for the shared libgcc library. The
385 default is @file{@var{libdir}}.
387 @item --infodir=@var{dirname}
388 Specify the installation directory for documentation in info format.
389 The default is @file{@var{prefix}/info}.
391 @item --mandir=@var{dirname}
392 Specify the installation directory for manual pages. The default is
393 @file{@var{prefix}/man}. (Note that the manual pages are only extracts from
394 the full GCC manuals, which are provided in Texinfo format. The
395 @command{g77} manpage is unmaintained and may be out of date; the others
396 are derived by an automatic conversion process from parts of the full
399 @item --with-gxx-include-dir=@var{dirname}
401 the installation directory for G++ header files. The default is
402 @file{@var{prefix}/include/g++-v3}.
406 @item --program-prefix=@var{prefix}
407 GCC supports some transformations of the names of its programs when
408 installing them. This option prepends @var{prefix} to the names of
409 programs to install in @var{bindir} (see above). For example, specifying
410 @option{--program-prefix=foo-} would result in @samp{gcc}
411 being installed as @file{/usr/local/bin/foo-gcc}.
413 @item --program-suffix=@var{suffix}
414 Appends @var{suffix} to the names of programs to install in @var{bindir}
415 (see above). For example, specifying @option{--program-suffix=-3.1}
416 would result in @samp{gcc} being installed as
417 @file{/usr/local/bin/gcc-3.1}.
419 @item --program-transform-name=@var{pattern}
420 Applies the @samp{sed} script @var{pattern} to be applied to the names
421 of programs to install in @var{bindir} (see above). @var{pattern} has to
422 consist of one or more basic @samp{sed} editing commands, separated by
423 semicolons. For example, if you want the @samp{gcc} program name to be
424 transformed to the installed program @file{/usr/local/bin/myowngcc} and
425 the @samp{g++} program name to be transformed to
426 @file{/usr/local/bin/gspecial++} without changing other program names,
427 you could use the pattern
428 @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}
429 to achieve this effect.
431 All three options can be combined and used together, resulting in more
432 complex conversion patterns. As a basic rule, @var{prefix} (and
433 @var{suffix}) are prepended (appended) before further transformations
434 can happen with a special transformation script @var{pattern}.
436 As currently implemented, this options only take effect for native
437 builds; cross compiler binaries' names are not transformed even when a
438 transformation is explicitly asked for by one of this options.
440 For native builds, some of the installed programs are also installed
441 with the target alias in front of their name, as in
442 @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
443 before the target alias is prepended to the name - so, specifying
444 @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
445 resulting binary would be installed as
446 @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.
448 As a last shortcoming, none of the installed Ada programs are
449 transformed yet, which will be fixed in some time.
451 @item --with-local-prefix=@var{dirname}
453 installation directory for local include files. The default is
454 @file{/usr/local}. Specify this option if you want the compiler to
455 search directory @file{@var{dirname}/include} for locally installed
456 header files @emph{instead} of @file{/usr/local/include}.
458 You should specify @option{--with-local-prefix} @strong{only} if your
459 site has a different convention (not @file{/usr/local}) for where to put
462 The default value for @option{--with-local-prefix} is @file{/usr/local}
463 regardless of the value of @option{--prefix}. Specifying
464 @option{--prefix} has no effect on which directory GCC searches for
465 local header files. This may seem counterintuitive, but actually it is
468 The purpose of @option{--prefix} is to specify where to @emph{install
469 GCC}. The local header files in @file{/usr/local/include}---if you put
470 any in that directory---are not part of GCC@. They are part of other
471 programs---perhaps many others. (GCC installs its own header files in
472 another directory which is based on the @option{--prefix} value.)
474 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
475 The directory you use for @option{--with-local-prefix} @strong{must not}
476 contain any of the system's standard header files. If it did contain
477 them, certain programs would be miscompiled (including GNU Emacs, on
478 certain targets), because this would override and nullify the header
479 file corrections made by the @code{fixincludes} script.
481 Indications are that people who use this option use it based on mistaken
482 ideas of what it is for. People use it as if it specified where to
483 install part of GCC@. Perhaps they make this assumption because
484 installing GCC creates the directory.
486 @item --enable-shared[=@var{package}[,@dots{}]]
487 Build shared versions of libraries, if shared libraries are supported on
488 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
489 are enabled by default on all platforms that support shared libraries,
490 except for @samp{libobjc} which is built as a static library only by
493 If a list of packages is given as an argument, build shared libraries
494 only for the listed packages. For other packages, only static libraries
495 will be built. Package names currently recognized in the GCC tree are
496 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
497 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc} and
498 @samp{libjava}. Note that @samp{libobjc} does not recognize itself by
499 any name, so, if you list package names in @option{--enable-shared},
500 you will only get static Objective-C libraries. @samp{libf2c} and
501 @samp{libiberty} do not support shared libraries at all.
503 Use @option{--disable-shared} to build only static libraries. Note that
504 @option{--disable-shared} does not accept a list of package names as
505 argument, only @option{--enable-shared} does.
507 @item @anchor{with-gnu-as}--with-gnu-as
508 Specify that the compiler should assume that the
509 assembler it finds is the GNU assembler. However, this does not modify
510 the rules to find an assembler and will result in confusion if found
511 assembler is not actually the GNU assembler. (Confusion will also
512 result if the compiler finds the GNU assembler but has not been
513 configured with @option{--with-gnu-as}.) If you have more than one
514 assembler installed on your system, you may want to use this option in
515 connection with @option{--with-as=@var{pathname}}.
517 The systems where it makes a difference whether you use the GNU assembler are
518 @samp{hppa1.0-@var{any}-@var{any}}, @samp{hppa1.1-@var{any}-@var{any}},
519 @samp{i386-@var{any}-sysv}, @samp{i386-@var{any}-isc},
520 @samp{i860-@var{any}-bsd}, @samp{m68k-bull-sysv},
521 @samp{m68k-hp-hpux}, @samp{m68k-sony-bsd},
522 @samp{m68k-altos-sysv}, @samp{m68000-hp-hpux},
523 @samp{m68000-att-sysv}, @samp{@var{any}-lynx-lynxos},
524 and @samp{mips-@var{any}}.
525 On any other system, @option{--with-gnu-as} has no effect.
527 On the systems listed above (except for the HP-PA, for ISC on the
528 386, and for @samp{mips-sgi-irix5.*}), if you use the GNU assembler,
529 you should also use the GNU linker (and specify @option{--with-gnu-ld}).
531 @item --with-as=@var{pathname}
533 compiler should use the assembler pointed to by @var{pathname}, rather
534 than the one found by the standard rules to find an assembler, which
539 @file{@var{exec_prefix}/lib/gcc-lib/@var{target}/@var{version}}
540 directory, where @var{exec_prefix} defaults to @var{prefix} which
541 defaults to @file{/usr/local} unless overridden by the
542 @option{--prefix=@var{pathname}} switch described above. @var{target} is the
543 target system triple, such as @samp{sparc-sun-solaris2.7}, and
544 @var{version} denotes the GCC version, such as 3.0.
546 Check operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
549 Note that these rules do not check for the value of @env{PATH}. You may
550 want to use @option{--with-as} if no assembler is installed in the
551 directories listed above, or if you have multiple assemblers installed
552 and want to choose one that is not found by the above rules.
554 @item @anchor{with-gnu-ld}--with-gnu-ld
555 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
559 @item --with-ld=@var{pathname}
561 @option{--with-as}, but for the linker.
564 Specify that stabs debugging
565 information should be used instead of whatever format the host normally
566 uses. Normally GCC uses the same debug format as the host system.
568 On MIPS based systems and on Alphas, you must specify whether you want
569 GCC to create the normal ECOFF debugging format, or to use BSD-style
570 stabs passed through the ECOFF symbol table. The normal ECOFF debug
571 format cannot fully handle languages other than C@. BSD stabs format can
572 handle other languages, but it only works with the GNU debugger GDB@.
574 Normally, GCC uses the ECOFF debugging format by default; if you
575 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
577 No matter which default you choose when you configure GCC, the user
578 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
579 the debug format for a particular compilation.
581 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
582 @option{--with-gas} is used. It selects use of stabs debugging
583 information embedded in COFF output. This kind of debugging information
584 supports C++ well; ordinary COFF debugging information does not.
586 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
587 selects use of stabs debugging information embedded in ELF output. The
588 C++ compiler currently (2.6.0) does not support the DWARF debugging
589 information normally used on 386 SVR4 platforms; stabs provide a
590 workable alternative. This requires gas and gdb, as the normal SVR4
591 tools can not generate or interpret stabs.
593 @item --disable-multilib
594 Specify that multiple target
595 libraries to support different target variants, calling
596 conventions, etc should not be built. The default is to build a
597 predefined set of them.
599 Some targets provide finer-grained control over which multilibs are built
600 (e.g., @option{--disable-softfloat}):
607 fpu, 26bit, underscore, interwork, biendian, nofmult.
610 softfloat, m68881, m68000, m68020.
613 single-float, biendian, softfloat.
615 @item powerpc*-*-*, rs6000*-*-*
616 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
621 @item --enable-threads
622 Specify that the target
623 supports threads. This affects the Objective-C compiler and runtime
624 library, and exception handling for other languages like C++ and Java.
625 On some systems, this is the default.
627 In general, the best (and, in many cases, the only known) threading
628 model available will be configured for use. Beware that on some
629 systems, gcc has not been taught what threading models are generally
630 available for the system. In this case, @option{--enable-threads} is an
631 alias for @option{--enable-threads=single}.
633 @item --disable-threads
634 Specify that threading support should be disabled for the system.
635 This is an alias for @option{--enable-threads=single}.
637 @item --enable-threads=@var{lib}
639 @var{lib} is the thread support library. This affects the Objective-C
640 compiler and runtime library, and exception handling for other languages
641 like C++ and Java. The possibilities for @var{lib} are:
649 Generic MACH thread support, known to work on NeXTSTEP@. (Please note
650 that the file needed to support this configuration, @file{gthr-mach.h}, is
651 missing and thus this setting will cause a known bootstrap failure.)
653 This is an alias for @samp{single}.
655 Generic POSIX thread support.
657 Same as @samp{posix} on arm*-*-linux*, *-*-chorusos* and *-*-freebsd*
658 only. A future release of gcc might remove this alias or extend it
661 RTEMS thread support.
663 Disable thread support, should work for all platforms.
665 Sun Solaris 2 thread support.
667 VxWorks thread support.
669 Microsoft Win32 API thread support.
672 @item --with-cpu=@var{cpu}
673 Specify which cpu variant the
674 compiler should generate code for by default. This is currently
675 only supported on the some ports, specifically arm, powerpc, and
676 SPARC@. If configure does not recognize the model name (e.g.@: arm700,
677 603e, or ultrasparc) you provide, please check the configure script
678 for a complete list of supported models.
680 @item --enable-altivec
681 Specify that the target supports AltiVec vector enhancements. This
682 option will adjust the ABI for AltiVec enhancements, as well as generate
683 AltiVec code when appropriate. This option is only available for
686 @item --enable-target-optspace
688 libraries should be optimized for code space instead of code speed.
689 This is the default for the m32r platform.
692 Specify that a user visible @command{cpp} program should not be installed.
694 @item --with-cpp-install-dir=@var{dirname}
695 Specify that the user visible @command{cpp} program should be installed
696 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
698 @item --enable-maintainer-mode
700 regenerate the GCC master message catalog @file{gcc.pot} are normally
701 disabled. This is because it can only be rebuilt if the complete source
702 tree is present. If you have changed the sources and want to rebuild the
703 catalog, configuring with @option{--enable-maintainer-mode} will enable
704 this. Note that you need a recent version of the @code{gettext} tools
707 @item --enable-version-specific-runtime-libs
709 that runtime libraries should be installed in the compiler specific
710 subdirectory (@file{@var{libsubdir}}) rather than the usual places. In
711 addition, @samp{libstdc++}'s include files will be installed in
712 @file{@var{libsubdir}/include/g++} unless you overruled it by using
713 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
714 particularly useful if you intend to use several versions of GCC in
715 parallel. This is currently supported by @samp{libf2c} and
716 @samp{libstdc++}, and is the default for @samp{libobjc} which cannot be
717 changed in this case.
719 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
720 Specify that only a particular subset of compilers and
721 their runtime libraries should be built. For a list of valid values for
722 @var{langN} you can issue the following command in the
723 @file{gcc} directory of your GCC source tree:@*
725 grep language= */config-lang.in
727 Currently, you can use any of the following:
728 @code{ada}, @code{c}, @code{c++}, @code{f77}, @code{java}, @code{objc}.
729 Building the Ada compiler has special requirements, see below.@*
730 If you do not pass this flag, all languages available in the @file{gcc}
731 sub-tree will be configured. Re-defining @code{LANGUAGES} when calling
732 @samp{make bootstrap} @strong{does not} work anymore, as those
733 language sub-directories might not have been configured!
735 @item --disable-libgcj
736 Specify that the run-time libraries
737 used by GCJ should not be built. This is useful in case you intend
738 to use GCJ with some other run-time, or you're going to install it
739 separately, or it just happens not to build on your particular
740 machine. In general, if the Java front end is enabled, the GCJ
741 libraries will be enabled too, unless they're known to not work on
742 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
743 may need to port it; in this case, before modifying the top-level
744 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
745 you may use @option{--enable-libgcj} to override the default.
748 Specify that the compiler should
749 use DWARF 2 debugging information as the default.
751 @item --enable-win32-registry
752 @itemx --enable-win32-registry=@var{key}
753 @itemx --disable-win32-registry
754 The @option{--enable-win32-registry} option enables Windows-hosted GCC
755 to look up installations paths in the registry using the following key:
758 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
761 @var{key} defaults to GCC version number, and can be overridden by the
762 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
763 who use custom installers are encouraged to provide a different key,
764 perhaps one comprised of vendor name and GCC version number, to
765 avoid conflict with existing installations. This feature is enabled
766 by default, and can be disabled by @option{--disable-win32-registry}
767 option. This option has no effect on the other hosts.
770 Specify that the machine does not have a floating point unit. This
771 option only applies to @samp{m68k-sun-sunos@var{n}} and
772 @samp{m68k-isi-bsd}. On any other system, @option{--nfp} has no effect.
774 @item --enable-checking
775 @itemx --enable-checking=@var{list}
776 When you specify this option, the compiler is built to perform checking
777 of tree node types when referencing fields of that node, and some other
778 internal consistency checks. This does not change the generated code,
779 but adds error checking within the compiler. This will slow down the
780 compiler and may only work properly if you are building the compiler
781 with GCC@. This is on by default when building from CVS or snapshots,
782 but off for releases. More control over the checks may be had by
783 specifying @var{list}; the categories of checks available are
784 @samp{misc}, @samp{tree}, @samp{gc}, @samp{rtl}, @samp{rtlflag} and
786 default when @var{list} is not specified is @samp{misc,tree,gc,rtlflag}; the
787 checks @samp{rtl} and @samp{gcac} are very expensive.
791 The @option{--enable-nls} option enables Native Language Support (NLS),
792 which lets GCC output diagnostics in languages other than American
793 English. Native Language Support is enabled by default if not doing a
794 canadian cross build. The @option{--disable-nls} option disables NLS@.
796 @item --with-included-gettext
797 If NLS is enabled, the @option{--with-included-gettext} option causes the build
798 procedure to prefer its copy of GNU @command{gettext}.
801 If NLS is enabled, and if the host lacks @code{gettext} but has the
802 inferior @code{catgets} interface, the GCC build procedure normally
803 ignores @code{catgets} and instead uses GCC's copy of the GNU
804 @code{gettext} library. The @option{--with-catgets} option causes the
805 build procedure to use the host's @code{catgets} in this situation.
807 @item --with-libiconv-prefix=@var{dir}
808 Search for libiconv header files in @file{@var{dir}/include} and
809 libiconv library files in @file{@var{dir}/lib}.
811 @item --with-system-zlib
812 Use installed zlib rather than that included with GCC@. This option
813 only applies if the Java front end is being built.
815 @item --enable-obsolete
816 Enable configuration for an obsoleted system. If you attempt to
817 configure GCC for a system (build, host, or target) which has been
818 obsoleted, and you do not specify this flag, configure will halt with an
821 All support for systems which have been obsoleted in one release of GCC
822 is removed entirely in the next major release, unless someone steps
823 forward to maintain the port.
826 Some options which only apply to building cross compilers:
828 @item --with-headers=@var{dir}
829 Specifies a directory
830 which has target include files.
831 @emph{This options is required} when building a cross
832 compiler, if @file{@var{prefix}/@var{target}/sys-include} doesn't pre-exist.
833 These include files will be copied into the @file{gcc} install directory.
834 Fixincludes will be run on these files to make them compatible with
836 @item --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
837 Specifies a list of directories which contain the target runtime
838 libraries. These libraries will be copied into the @file{gcc} install
841 Specifies that @samp{newlib} is
842 being used as the target C library. This causes @code{__eprintf} to be
843 omitted from @file{libgcc.a} on the assumption that it will be provided by
847 Note that each @option{--enable} option has a corresponding
848 @option{--disable} option and that each @option{--with} option has a
849 corresponding @option{--without} option.
856 @uref{./index.html,,Return to the GCC Installation page}
860 @c ***Building****************************************************************
862 @comment node-name, next, previous, up
863 @node Building, Testing, Configuration, Installing GCC
869 @cindex Installing GCC: Building
871 Now that GCC is configured, you are ready to build the compiler and
874 We @strong{highly} recommend that GCC be built using GNU make;
875 other versions may work, then again they might not.
876 GNU make is required for compiling GNAT (the Ada compiler) and the Java
879 (For example, many broken versions of make will fail if you use the
880 recommended setup where @var{objdir} is different from @var{srcdir}.
881 Other broken versions may recompile parts of the compiler when
882 installing the compiler.)
884 Some commands executed when making the compiler may fail (return a
885 nonzero status) and be ignored by @code{make}. These failures, which
886 are often due to files that were not found, are expected, and can safely
889 It is normal to have compiler warnings when compiling certain files.
890 Unless you are a GCC developer, you can generally ignore these warnings
891 unless they cause compilation to fail.
893 On certain old systems, defining certain environment variables such as
894 @env{CC} can interfere with the functioning of @command{make}.
896 If you encounter seemingly strange errors when trying to build the
897 compiler in a directory other than the source directory, it could be
898 because you have previously configured the compiler in the source
899 directory. Make sure you have done all the necessary preparations.
901 If you build GCC on a BSD system using a directory stored in an old System
902 V file system, problems may occur in running @code{fixincludes} if the
903 System V file system doesn't support symbolic links. These problems
904 result in a failure to fix the declaration of @code{size_t} in
905 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
906 that type mismatches occur, this could be the cause.
908 The solution is not to use such a directory for building GCC@.
910 When building from CVS or snapshots, or if you modify parser sources,
911 you need the Bison parser generator installed. Any version 1.25 or
912 later should work; older versions may also work. If you do not modify
913 parser sources, releases contain the Bison-generated files and you do
914 not need Bison installed to build them.
916 When building from CVS or snapshots, or if you modify Texinfo
917 documentation, you need version 4.1 or later of Texinfo installed if you
918 want Info documentation to be regenerated. Releases contain Info
919 documentation pre-built for the unmodified documentation in the release.
921 @section Building a native compiler
923 For a native build issue the command @samp{make bootstrap}. This
924 will build the entire GCC system, which includes the following steps:
928 Build host tools necessary to build the compiler such as texinfo, bison,
932 Build target tools for use by the compiler such as binutils (bfd,
933 binutils, gas, gprof, ld, and opcodes)
934 if they have been individually linked
935 or moved into the top level GCC source tree before configuring.
938 Perform a 3-stage bootstrap of the compiler.
941 Perform a comparison test of the stage2 and stage3 compilers.
944 Build runtime libraries using the stage3 compiler from the previous step.
948 If you are short on disk space you might consider @samp{make
949 bootstrap-lean} instead. This is identical to @samp{make
950 bootstrap} except that object files from the stage1 and
951 stage2 of the 3-stage bootstrap of the compiler are deleted as
952 soon as they are no longer needed.
955 If you want to save additional space during the bootstrap and in
956 the final installation as well, you can build the compiler binaries
957 without debugging information with @samp{make CFLAGS='-O' LIBCFLAGS='-g
958 -O2' LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap}. This will save
959 roughly 40% of disk space both for the bootstrap and the final installation.
960 (Libraries will still contain debugging information.)
962 If you wish to use non-default GCC flags when compiling the stage2 and
963 stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing
964 @samp{make bootstrap}. Non-default optimization flags are less well
965 tested here than the default of @samp{-g -O2}, but should still work.
966 In a few cases, you may find that you need to specify special flags such
967 as @option{-msoft-float} here to complete the bootstrap; or, if the
968 native compiler miscompiles the stage1 compiler, you may need to work
969 around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the
970 stage1 compiler that were miscompiled, or by using @samp{make
971 bootstrap4} to increase the number of stages of bootstrap.
973 If you used the flag @option{--enable-languages=@dots{}} to restrict
974 the compilers to be built, only those you've actually enabled will be
975 built. This will of course only build those runtime libraries, for
976 which the particular compiler has been built. Please note,
977 that re-defining @env{LANGUAGES} when calling @samp{make bootstrap}
978 @strong{does not} work anymore!
980 If the comparison of stage2 and stage3 fails, this normally indicates
981 that the stage2 compiler has compiled GCC incorrectly, and is therefore
982 a potentially serious bug which you should investigate and report. (On
983 a few systems, meaningful comparison of object files is impossible; they
984 always appear ``different''. If you encounter this problem, you will
985 need to disable comparison in the @file{Makefile}.)
987 @section Building a cross compiler
989 We recommend reading the
990 @uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ}
991 for information about building cross compilers.
993 When building a cross compiler, it is not generally possible to do a
994 3-stage bootstrap of the compiler. This makes for an interesting problem
995 as parts of GCC can only be built with GCC@.
997 To build a cross compiler, we first recommend building and installing a
998 native compiler. You can then use the native GCC compiler to build the
999 cross compiler. The installed native compiler needs to be GCC version
1002 Assuming you have already installed a native copy of GCC and configured
1003 your cross compiler, issue the command @command{make}, which performs the
1008 Build host tools necessary to build the compiler such as texinfo, bison,
1012 Build target tools for use by the compiler such as binutils (bfd,
1013 binutils, gas, gprof, ld, and opcodes)
1014 if they have been individually linked or moved into the top level GCC source
1015 tree before configuring.
1018 Build the compiler (single stage only).
1021 Build runtime libraries using the compiler from the previous step.
1024 Note that if an error occurs in any step the make process will exit.
1026 @section Building in parallel
1028 If you have a multiprocessor system you can use @samp{make bootstrap
1029 MAKE="make -j 2" -j 2} or just @samp{make -j 2 bootstrap}
1030 for GNU Make 3.79 and above instead of just @samp{make bootstrap}
1031 when building GCC@. You can use a bigger number instead of two if
1032 you like. In most cases, it won't help to use a number bigger than
1033 the number of processors in your machine.
1035 @section Building the Ada compiler
1037 In order to build GNAT, the Ada compiler, you need a working GNAT
1038 compiler (GNAT version 3.13 or later, or GCC version 3.1 or later),
1039 since the Ada front end is written in Ada (with some
1040 GNAT-specific extensions), and GNU make.
1042 However, you do not need a full installation of GNAT, just the GNAT
1043 binary @file{gnat1}, a copy of @file{gnatbind}, and a compiler driver
1044 which can deal with Ada input (by invoking the @file{gnat1} binary).
1045 You can specify this compiler driver by setting the @env{ADAC}
1046 environment variable at the configure step. @command{configure} can
1047 detect the driver automatically if it has got a common name such as
1048 @command{gcc} or @command{gnatgcc}. Of course, you still need a working
1049 C compiler (the compiler driver can be different or not).
1050 @command{configure} does not test whether the GNAT installation works
1051 and has a sufficiently recent version; if too old a GNAT version is
1052 installed, the build will fail unless @option{--enable-languages} is
1053 used to disable building the Ada front end.
1055 Additional build tools (such as @command{gnatmake}) or a working GNAT
1056 run-time library installation are usually @emph{not} required. However,
1057 if you want to boostrap the compiler using a minimal version of GNAT,
1058 you have to issue the following commands before invoking @samp{make
1059 boostrap} (this assumes that you start with an unmodified and consistent
1060 source distribution):
1063 cd @var{srcdir}/gcc/ada
1064 touch treeprs.ads [es]info.h nmake.ad[bs]
1067 At the moment, the GNAT library and several tools for GNAT are not built
1068 by @samp{make bootstrap}. You have to invoke
1069 @samp{make gnatlib_and_tools} in the @file{@var{objdir}/gcc}
1070 subdirectory before proceeding with the next steps.
1072 For example, you can build a native Ada compiler by issuing the
1073 following commands (assuming @command{make} is GNU make):
1077 @var{srcdir}/configure --enable-languages=c,ada
1078 cd @var{srcdir}/gcc/ada
1079 touch treeprs.ads [es]info.h nmake.ad[bs]
1083 make gnatlib_and_tools
1087 Currently, when compiling the Ada front end, you cannot use the parallel
1088 build feature described in the previous section.
1095 @uref{./index.html,,Return to the GCC Installation page}
1099 @c ***Testing*****************************************************************
1101 @comment node-name, next, previous, up
1102 @node Testing, Final install, Building, Installing GCC
1106 @chapter Installing GCC: Testing
1109 @cindex Installing GCC: Testing
1112 Before you install GCC, we encourage you to run the testsuites and to
1113 compare your results with results from a similar configuration that have
1114 been submitted to the
1115 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
1116 This step is optional and may require you to download additional software,
1117 but it can give you confidence in your new GCC installation or point out
1118 problems before you install and start using your new GCC.
1120 First, you must have @uref{download.html,,downloaded the testsuites}.
1121 These are part of the full distribution, but if you downloaded the
1122 ``core'' compiler plus any front ends, you must download the testsuites
1125 Second, you must have the testing tools installed. This includes
1126 a @uref{http://www.gnu.org/software/dejagnu/,,current version of DejaGnu};
1127 dejagnu 1.3 is not sufficient.
1128 It also includes Tcl and Expect; the DejaGnu site has links to these.
1130 Now you may need specific preparations:
1135 The following environment variables may need to be set appropriately, as in
1136 the following example (which assumes that DejaGnu has been installed
1137 under @file{/usr/local}):
1140 TCL_LIBRARY = /usr/local/share/tcl8.0
1141 DEJAGNULIBS = /usr/local/share/dejagnu
1144 On systems such as Cygwin, these paths are required to be actual
1145 paths, not mounts or links; presumably this is due to some lack of
1146 portability in the DejaGnu code.
1148 If the directories where @command{runtest} and @command{expect} were
1149 installed are in the @env{PATH}, it should not be necessary to set these
1150 environment variables.
1154 Finally, you can run the testsuite (which may take a long time):
1156 cd @var{objdir}; make -k check
1159 The testing process will try to test as many components in the GCC
1160 distribution as possible, including the C, C++, Objective-C and Fortran
1161 compilers as well as the C++ and Java runtime libraries.
1163 While running the testsuite, DejaGnu might emit messages resembling
1164 @samp{WARNING: Couldn't find the global config file.} or
1165 @samp{WARNING: Couldn't find tool init file}.
1166 These messages are harmless and do not affect the validity of the tests.
1168 @section How can I run the test suite on selected tests?
1170 As a first possibility to cut down the number of tests that are run it is
1171 possible to use @samp{make check-gcc} or @samp{make check-g++}
1172 in the @file{gcc} subdirectory of the object directory. To further cut down the
1173 tests the following is possible:
1176 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
1179 This will run all @command{gcc} execute tests in the testsuite.
1182 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
1185 This will run the @command{g++} ``old-deja'' tests in the testsuite where the filename
1186 matches @samp{9805*}.
1188 The @file{*.exp} files are located in the testsuite directories of the GCC
1189 source, the most important ones being @file{compile.exp},
1190 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
1191 To get a list of the possible @file{*.exp} files, pipe the
1192 output of @samp{make check} into a file and look at the
1193 @samp{Running @dots{} .exp} lines.
1195 @section How to interpret test results
1197 After the testsuite has run you'll find various @file{*.sum} and @file{*.log}
1198 files in the testsuite subdirectories. The @file{*.log} files contain a
1199 detailed log of the compiler invocations and the corresponding
1200 results, the @file{*.sum} files summarize the results. These summaries list
1201 all the tests that have been run with a corresponding status code:
1205 PASS: the test passed as expected
1207 XPASS: the test unexpectedly passed
1209 FAIL: the test unexpectedly failed
1211 XFAIL: the test failed as expected
1213 UNSUPPORTED: the test is not supported on this platform
1215 ERROR: the testsuite detected an error
1217 WARNING: the testsuite detected a possible problem
1220 It is normal for some tests to report unexpected failures. At the
1221 current time our testing harness does not allow fine grained control
1222 over whether or not a test is expected to fail. We expect to fix this
1223 problem in future releases.
1226 @section Submitting test results
1228 If you want to report the results to the GCC project, use the
1229 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
1232 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
1233 -m gcc-testresults@@gcc.gnu.org |sh
1236 This script uses the @command{Mail} program to send the results, so
1237 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
1238 prepended to the testsuite summary and should contain any special
1239 remarks you have on your results or your build environment. Please
1240 do not edit the testsuite result block or the subject line, as these
1241 messages are automatically parsed and presented at the
1242 @uref{http://gcc.gnu.org/testresults/,,GCC testresults} web
1243 page. Here you can also gather information on how specific tests
1244 behave on different platforms and compare them with your results. A
1245 few failing testcases are possible even on released versions and you
1246 should look here first if you think your results are unreasonable.
1253 @uref{./index.html,,Return to the GCC Installation page}
1257 @c ***Final install***********************************************************
1259 @comment node-name, next, previous, up
1260 @node Final install, , Testing, Installing GCC
1262 @ifset finalinstallhtml
1264 @chapter Installing GCC: Final installation
1267 Now that GCC has been built (and optionally tested), you can install it with
1269 cd @var{objdir}; make install
1272 We strongly recommend to install into a target directory where there is
1273 no previous version of GCC present.
1275 That step completes the installation of GCC; user level binaries can
1276 be found in @file{@var{prefix}/bin} where @var{prefix} is the value you
1277 specified with the @option{--prefix} to configure (or @file{/usr/local}
1278 by default). (If you specified @option{--bindir}, that directory will
1279 be used instead; otherwise, if you specified @option{--exec-prefix},
1280 @file{@var{exec-prefix}/bin} will be used.) Headers for the C++ and
1281 Java libraries are installed in @file{@var{prefix}/include}; libraries
1282 in @file{@var{libdir}} (normally @file{@var{prefix}/lib}); internal
1283 parts of the compiler in @file{@var{libdir}/gcc-lib}; documentation in
1284 info format in @file{@var{infodir}} (normally @file{@var{prefix}/info}).
1286 If you built a released version of GCC using @samp{make bootstrap} then please
1287 quickly review the build status page for
1288 @uref{http://gcc.gnu.org/gcc-3.1/buildstat.html,,3.1},
1289 @uref{http://gcc.gnu.org/gcc-3.0/buildstat.html,,3.0}, or
1290 @uref{http://gcc.gnu.org/gcc-2.95/buildstat.html,,2.95}.
1291 If your system is not listed for the version of GCC that you built,
1293 @email{gcc@@gcc.gnu.org} indicating
1294 that you successfully built and installed GCC.
1295 Include the following information:
1299 Output from running @file{@var{srcdir}/config.guess}. Do not send us
1300 that file itself, just the one-line output from running it.
1303 The output of @samp{gcc -v} for your newly installed gcc.
1304 This tells us which version of GCC you built and the options you passed to
1308 Whether you enabled all languages or a subset of them. If you used a
1309 full distribution then this information is part of the configure
1310 options in the output of @samp{gcc -v}, but if you downloaded the
1311 ``core'' compiler plus additional front ends then it isn't apparent
1312 which ones you built unless you tell us about it.
1315 If the build was for GNU/Linux, also include:
1318 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
1319 this information should be available from @file{/etc/issue}.
1322 The version of the Linux kernel, available from @samp{uname --version}
1326 The version of glibc you used; for RPM-based systems like Red Hat,
1327 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
1328 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
1330 For other systems, you can include similar information if you think it is
1334 Any other information that you think would be useful to people building
1335 GCC on the same configuration. The new entry in the build status list
1336 will include a link to the archived copy of your message.
1339 We'd also like to know if the
1341 @ref{Specific, host/target specific installation notes}
1344 @uref{specific.html,,host/target specific installation notes}
1346 didn't include your host/target information or if that information is
1347 incomplete or out of date. Send a note to
1348 @email{gcc@@gcc.gnu.org} telling us how the information should be changed.
1350 If you find a bug, please report it following our
1351 @uref{../bugs.html,,bug reporting guidelines}.
1353 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
1354 dvi}. You will need to have @command{texi2dvi} (version at least 4.1)
1355 and @TeX{} installed. This creates a number of @file{.dvi} files in
1356 subdirectories of @file{@var{objdir}}; these may be converted for
1357 printing with programs such as @command{dvips}. You can also
1358 @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the
1359 Free Software Foundation}, though such manuals may not be for the most
1360 recent version of GCC@.
1367 @uref{./index.html,,Return to the GCC Installation page}
1371 @c ***Binaries****************************************************************
1373 @comment node-name, next, previous, up
1374 @node Binaries, Specific, Installing GCC, Top
1378 @chapter Installing GCC: Binaries
1381 @cindex Installing GCC: Binaries
1383 We are often asked about pre-compiled versions of GCC@. While we cannot
1384 provide these for all platforms, below you'll find links to binaries for
1385 various platforms where creating them by yourself is not easy due to various
1388 Please note that we did not create these binaries, nor do we
1389 support them. If you have any problems installing them, please
1390 contact their makers.
1397 @uref{http://freeware.bull.net,,Bull's Freeware and Shareware Archive for AIX};
1400 @uref{http://aixpdslib.seas.ucla.edu,,UCLA Software Library for AIX};
1404 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP};
1410 @uref{http://hpux.cae.wisc.edu/,,HP-UX Porting Center};
1413 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
1417 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
1418 OpenServer/Unixware};
1421 Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware};
1424 SGI---@uref{http://freeware.sgi.com/,,SGI Freeware};
1427 Windows 95, 98, and NT:
1430 The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project;
1432 @uref{http://www.xraylith.wisc.edu/~khan/software/gnu-win32/,,GNU Win32}
1433 related projects by Mumit Khan.
1437 @uref{ftp://ftp.thewrittenword.com/packages/free/by-name/,,The
1438 Written Word} offers binaries for Solaris 2.5.1, 2.6, 2.7/SPARC, 2.7/Intel,
1439 IRIX 6.2, 6.5, Digital UNIX 4.0D, HP-UX 10.20, and HP-UX 11.00.
1442 Hitachi H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
1443 Development Tools for the Hitachi H8/300[HS] Series}
1447 In addition to those specific offerings, you can get a binary
1448 distribution CD-ROM from the
1449 @uref{http://www.fsf.org/order/order.html,,Free Software Foundation}.
1450 It contains binaries for a number of platforms, and
1451 includes not only GCC, but other stuff as well. The current CD does
1452 not contain the latest version of GCC, but it should allow
1453 bootstrapping the compiler. An updated version of that disk is in the
1461 @uref{./index.html,,Return to the GCC Installation page}
1465 @c ***Specific****************************************************************
1467 @comment node-name, next, previous, up
1468 @node Specific, Old, Binaries, Top
1472 @chapter Host/target specific installation notes for GCC
1475 @cindex Specific installation notes
1476 @cindex Target specific installation
1477 @cindex Host specific installation
1478 @cindex Target specific installation notes
1480 Please read this document carefully @emph{before} installing the
1481 GNU Compiler Collection on your machine.
1486 @uref{#alpha*-*-*,,alpha*-*-*}
1488 @uref{#alpha*-dec-osf*,,alpha*-dec-osf*}
1490 @uref{#alphaev5-cray-unicosmk*,,alphaev5-cray-unicosmk*}
1492 @uref{#arc-*-elf,,arc-*-elf}
1494 @uref{#arm-*-aout,,arm-*-aout}
1496 @uref{#arm-*-elf,,arm-*-elf}
1498 @uref{#arm*-*-linux-gnu,,arm*-*-linux-gnu}
1506 @uref{#dsp16xx,,dsp16xx}
1508 @uref{#*-*-freebsd*,,*-*-freebsd*}
1510 @uref{#h8300-hms,,h8300-hms}
1512 @uref{#hppa*-hp-hpux*,,hppa*-hp-hpux*}
1514 @uref{#hppa*-hp-hpux9,,hppa*-hp-hpux9}
1516 @uref{#hppa*-hp-hpux10,,hppa*-hp-hpux10}
1518 @uref{#hppa*-hp-hpux11,,hppa*-hp-hpux11}
1520 @uref{#i370-*-*,,i370-*-*}
1522 @uref{#*-*-linux-gnu,,*-*-linux-gnu}
1524 @uref{#ix86-*-linux*aout,,i?86-*-linux*aout}
1526 @uref{#ix86-*-linux*,,i?86-*-linux*}
1528 @uref{#ix86-*-sco,,i?86-*-sco}
1530 @uref{#ix86-*-sco3.2v4,,i?86-*-sco3.2v4}
1532 @uref{#ix86-*-sco3.2v5*,,i?86-*-sco3.2v5*}
1534 @uref{#ix86-*-udk,,i?86-*-udk}
1536 @uref{#ix86-*-esix,,i?86-*-esix}
1538 @uref{#ia64-*-linux,,ia64-*-linux}
1540 @uref{#*-lynx-lynxos,,*-lynx-lynxos}
1542 @uref{#*-ibm-aix*,,*-ibm-aix*}
1544 @uref{#m32r-*-elf,,m32r-*-elf}
1546 @uref{#m68000-hp-bsd,,m68000-hp-bsd}
1548 @uref{#m6811-elf,,m6811-elf}
1550 @uref{#m6812-elf,,m6812-elf}
1552 @uref{#m68k-att-sysv,,m68k-att-sysv}
1554 @uref{#m68k-crds-unos,,m68k-crds-unos}
1556 @uref{#m68k-hp-hpux,,m68k-hp-hpux}
1558 @uref{#m68k-ncr-*,,m68k-ncr-*}
1560 @uref{#m68k-sun,,m68k-sun}
1562 @uref{#m68k-sun-sunos4.1.1,,m68k-sun-sunos4.1.1}
1564 @uref{#mips-*-*,,mips-*-*}
1566 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
1568 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
1570 @uref{#powerpc*-*-*,,powerpc*-*-*, powerpc-*-sysv4}
1572 @uref{#powerpc-*-darwin*,,powerpc-*-darwin*}
1574 @uref{#powerpc-*-elf,,powerpc-*-elf, powerpc-*-sysv4}
1576 @uref{#powerpc-*-linux-gnu*,,powerpc-*-linux-gnu*}
1578 @uref{#powerpc-*-netbsd*,,powerpc-*-netbsd*}
1580 @uref{#powerpc-*-eabiaix,,powerpc-*-eabiaix}
1582 @uref{#powerpc-*-eabisim,,powerpc-*-eabisim}
1584 @uref{#powerpc-*-eabi,,powerpc-*-eabi}
1586 @uref{#powerpcle-*-elf,,powerpcle-*-elf, powerpcle-*-sysv4}
1588 @uref{#powerpcle-*-eabisim,,powerpcle-*-eabisim}
1590 @uref{#powerpcle-*-eabi,,powerpcle-*-eabi}
1592 @uref{#powerpcle-*-winnt,,powerpcle-*-winnt, powerpcle-*-pe}
1594 @uref{#s390-*-linux*}
1596 @uref{#s390x-*-linux*}
1598 @uref{#*-*-solaris2*,,*-*-solaris2*}
1600 @uref{#sparc-sun-solaris2*,,sparc-sun-solaris2*}
1602 @uref{#sparc-sun-solaris2.7,,sparc-sun-solaris2.7}
1604 @uref{#sparc-sun-sunos4*,,sparc-sun-sunos4*}
1606 @uref{#sparc-unknown-linux-gnulibc1,,sparc-unknown-linux-gnulibc1}
1608 @uref{#sparc-*-linux*,,sparc-*-linux*}
1610 @uref{#sparc64-*-*,,sparc64-*-*}
1612 @uref{#sparcv9-*-solaris2*,,sparcv9-*-solaris2*}
1614 @uref{#*-*-sysv*,,*-*-sysv*}
1616 @uref{#vax-dec-ultrix,,vax-dec-ultrix}
1618 @uref{#xtensa-*-elf,,xtensa-*-elf}
1620 @uref{#xtensa-*-linux*,,xtensa-*-linux*}
1622 @uref{#windows,,Microsoft Windows}
1626 @uref{#older,,Older systems}
1631 @uref{#elf_targets,,all ELF targets} (SVR4, Solaris 2, etc.)
1637 <!-- -------- host/target specific issues start here ---------------- -->
1640 @heading @anchor{alpha*-*-*}alpha*-*-*
1642 This section contains general configuration information for all
1643 alpha-based platforms using ELF (in particular, ignore this section for
1644 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
1645 section, please read all other sections that match your target.
1647 We require binutils 2.11.2 or newer.
1648 Previous binutils releases had a number of problems with DWARF 2
1649 debugging information, not the least of which is incorrect linking of
1656 @heading @anchor{alpha*-dec-osf*}alpha*-dec-osf*
1657 Systems using processors that implement the DEC Alpha architecture and
1658 are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
1659 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
1661 As of GCC 3.2, versions before @code{alpha*-dec-osf4} are no longer
1662 supported. (These are the versions which identify themselves as DEC
1665 In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
1666 currently (2001-06-13) work with @command{mips-tfile}. As a workaround,
1667 we need to use the old assembler, invoked via the barely documented
1668 @option{-oldas} option. To bootstrap GCC, you either need to use the
1672 % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
1675 or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
1678 % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
1681 As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld}
1682 are supported on Tru64 UNIX, so you must not configure GCC with
1683 @option{--with-gnu-as} or @option{--with-gnu-ld}.
1685 The @option{--enable-threads} options isn't supported yet. A patch is
1686 in preparation for a future release.
1688 GCC writes a @samp{.verstamp} directive to the assembler output file
1689 unless it is built as a cross-compiler. It gets the version to use from
1690 the system header file @file{/usr/include/stamp.h}. If you install a
1691 new version of DEC Unix, you should rebuild GCC to pick up the new version
1694 Note that since the Alpha is a 64-bit architecture, cross-compilers from
1695 32-bit machines will not generate code as efficient as that generated
1696 when the compiler is running on a 64-bit machine because many
1697 optimizations that depend on being able to represent a word on the
1698 target in an integral value on the host cannot be performed. Building
1699 cross-compilers on the Alpha for 32-bit machines has only been tested in
1700 a few cases and may not work properly.
1702 @code{make compare} may fail on old versions of DEC Unix unless you add
1703 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
1704 assembler input file is stored in the object file, and that makes
1705 comparison fail if it differs between the @code{stage1} and
1706 @code{stage2} compilations. The option @option{-save-temps} forces a
1707 fixed name to be used for the assembler input file, instead of a
1708 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
1709 unless the comparisons fail without that option. If you add
1710 @option{-save-temps}, you will have to manually delete the @samp{.i} and
1711 @samp{.s} files after each series of compilations.
1713 GCC now supports both the native (ECOFF) debugging format used by DBX
1714 and GDB and an encapsulated STABS format for use only with GDB@. See the
1715 discussion of the @option{--with-stabs} option of @file{configure} above
1716 for more information on these formats and how to select them.
1718 There is a bug in DEC's assembler that produces incorrect line numbers
1719 for ECOFF format when the @samp{.align} directive is used. To work
1720 around this problem, GCC will not emit such alignment directives
1721 while writing ECOFF format debugging information even if optimization is
1722 being performed. Unfortunately, this has the very undesirable
1723 side-effect that code addresses when @option{-O} is specified are
1724 different depending on whether or not @option{-g} is also specified.
1726 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
1727 DBX@. DEC is now aware of this problem with the assembler and hopes to
1728 provide a fix shortly.
1734 @heading @anchor{alphaev5-cray-unicosmk*}alphaev5-cray-unicosmk*
1735 Cray T3E systems running Unicos/Mk.
1737 This port is incomplete and has many known bugs. We hope to improve the
1738 support for this target soon. Currently, only the C front end is supported,
1739 and it is not possible to build parallel applications. Cray modules are not
1740 supported; in particular, Craylibs are assumed to be in
1741 @file{/opt/ctl/craylibs/craylibs}.
1743 You absolutely @strong{must} use GNU make on this platform. Also, you
1744 need to tell GCC where to find the assembler and the linker. The
1745 simplest way to do so is by providing @option{--with-as} and
1746 @option{--with-ld} to @file{configure}, e.g.@:
1748 @samp{configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld
1749 --enable-languages=c}
1751 The comparison test during @samp{make bootstrap} fails on Unicos/Mk
1752 because the assembler inserts timestamps into object files. You should
1753 be able to work around this by doing @samp{make all} after getting this
1760 @heading @anchor{arc-*-elf}arc-*-elf
1761 Argonaut ARC processor.
1762 This configuration is intended for embedded systems.
1768 @heading @anchor{arm-*-aout}arm-*-aout
1769 Advanced RISC Machines ARM-family processors. These are often used in
1770 embedded applications. There are no standard Unix configurations.
1771 This configuration corresponds to the basic instruction sequences and will
1772 produce @file{a.out} format object modules.
1774 You may need to make a variant of the file @file{arm.h} for your particular
1781 @heading @anchor{arm-*-elf}arm-*-elf
1782 This configuration is intended for embedded systems.
1788 @heading @anchor{arm*-*-linux-gnu}arm*-*-linux-gnu
1790 We require GNU binutils 2.10 or newer.
1796 @heading @anchor{avr}avr
1798 ATMEL AVR-family micro controllers. These are used in embedded
1799 applications. There are no standard Unix configurations.
1801 @xref{AVR Options,, AVR Options, gcc, Using and Porting the GNU Compiler
1805 See ``AVR Options'' in the main manual
1807 for the list of supported MCU types.
1809 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
1811 Further installation notes and other useful information about AVR tools
1812 can also be obtained from:
1816 @uref{http://home.overta.ru/users/denisc,,http://home.overta.ru/users/denisc}
1818 @uref{http://www.amelek.gda.pl/avr,,http://www.amelek.gda.pl/avr}
1821 We @emph{strongly} recommend using binutils 2.11 or newer.
1823 The following error:
1825 Error: register required
1828 indicates that you should upgrade to a newer version of the binutils.
1834 @heading @anchor{c4x}c4x
1836 Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal
1837 Processors. These are used in embedded applications. There are no
1838 standard Unix configurations.
1840 @xref{TMS320C3x/C4x Options,, TMS320C3x/C4x Options, gcc, Using and
1841 Porting the GNU Compiler Collection (GCC)},
1844 See ``TMS320C3x/C4x Options'' in the main manual
1846 for the list of supported MCU types.
1848 GCC can be configured as a cross compiler for both the C3x and C4x
1849 architectures on the same system. Use @samp{configure --target=c4x
1850 --enable-languages="c,c++"} to configure.
1853 Further installation notes and other useful information about C4x tools
1854 can also be obtained from:
1858 @uref{http://www.elec.canterbury.ac.nz/c4x/,,http://www.elec.canterbury.ac.nz/c4x/}
1865 @heading @anchor{cris}CRIS
1867 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
1868 series. These are used in embedded applications.
1871 @xref{CRIS Options,, CRIS Options, gcc, Using and Porting the GNU Compiler
1875 See ``CRIS Options'' in the main manual
1877 for a list of CRIS-specific options.
1879 There are a few different CRIS targets:
1881 @item cris-axis-aout
1882 Old target. Includes a multilib for the @samp{elinux} a.out-based
1883 target. No multilibs for newer architecture variants.
1885 Mainly for monolithic embedded systems. Includes a multilib for the
1886 @samp{v10} core used in @samp{ETRAX 100 LX}.
1887 @item cris-axis-linux-gnu
1888 A GNU/Linux port for the CRIS architecture, currently targeting
1889 @samp{ETRAX 100 LX} by default.
1892 For @code{cris-axis-aout} and @code{cris-axis-elf} you need binutils 2.11
1893 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
1895 Pre-packaged tools can be obtained from
1896 @uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More
1897 information about this platform is available at
1898 @uref{http://developer.axis.com/}.
1904 @heading @anchor{dos}DOS
1906 Please have a look at our @uref{binaries.html,,binaries page}.
1908 You cannot install GCC by itself on MSDOS; it will not compile under
1909 any MSDOS compiler except itself. You need to get the complete
1910 compilation package DJGPP, which includes binaries as well as sources,
1911 and includes all the necessary compilation tools and libraries.
1917 @heading @anchor{dsp16xx}dsp16xx
1918 A port to the AT&T DSP1610 family of processors.
1924 @heading @anchor{*-*-freebsd*}*-*-freebsd*
1926 The version of binutils installed in @file{/usr/bin} is known to work unless
1927 otherwise specified in any per-architecture notes. However, binutils
1928 2.12.1 or greater is known to improve overall testsuite results.
1930 FreeBSD 1 is no longer supported in GCC 3.2.
1932 For FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
1933 configuration support and files as shipped with GCC 2.95 are still in
1934 place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
1935 it is unknown which version of binutils was used (it is assumed that it
1936 was the system copy in @file{/usr/bin}) and C++ EH failures were noted.
1938 For FreeBSD using the ELF file format: DWARF 2 debugging is now the
1939 default for all CPU architectures. It had been the default on
1940 FreeBSD/alpha since its inception. You may use @option{-gstabs} instead
1941 of @option{-g}, if you really want the old debugging format. There are
1942 no known issues with mixing object files and libraries with different
1943 debugging formats. Otherwise, this release of GCC should now match more
1944 of the configuration used in the stock FreeBSD configuration of GCC. In
1945 particular, @option{--enable-threads} is now configured by default.
1946 However, as a general user, do not attempt to replace the system
1947 compiler with this release. Known to bootstrap and check with good
1948 results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4, 4.5-STABLE and 5-CURRENT@.
1950 In principle, @option{--enable-threads} is now compatible with
1951 @option{--enable-libgcj} on FreeBSD@. However, it has only been built
1952 and tested on i386-*-freebsd4.5 and alpha-*-freebsd5.0. The static
1953 library may be incorrectly built (symbols are missing at link time).
1954 There is a rare timing-based startup hang (probably involves an
1955 assupmtion about the thread library). Multi-threaded boehm-gc (required for
1956 libjava) exposes severe threaded signal-handling bugs on FreeBSD before
1957 4.5-RELEASE. The alpha port may not fully bootstrap without some manual
1958 intervention: gcjh will crash with a floating-point exception while
1959 generating @file{java/lang/Double.h} (just copy the version built on
1960 i386-*-freebsd* and rerun the top-level gmake with no arguments and it
1961 should properly complete the bootstrap). Other CPU architectures
1962 supported by FreeBSD will require additional configuration tuning in, at
1963 the very least, both boehm-gc and libffi.
1965 Shared @file{libgcc_s.so} is now built and installed by default.
1971 @heading @anchor{h8300-hms}h8300-hms
1972 Hitachi H8/300 series of processors.
1974 Please have a look at our @uref{binaries.html,,binaries page}.
1976 The calling convention and structure layout has changed in release 2.6.
1977 All code must be recompiled. The calling convention now passes the
1978 first three arguments in function calls in registers. Structures are no
1979 longer a multiple of 2 bytes.
1985 @heading @anchor{hppa*-hp-hpux*}hppa*-hp-hpux*
1987 We @emph{highly} recommend using gas/binutils 2.8 or newer on all hppa
1988 platforms; you may encounter a variety of problems when using the HP
1991 Specifically, @option{-g} does not work on HP-UX (since that system
1992 uses a peculiar debugging format which GCC does not know about), unless you
1993 use GAS and GDB and configure GCC with the
1994 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
1995 @option{--with-as=@dots{}} options.
1997 If you wish to use pa-risc 2.0 architecture support, you must use either
1998 the HP assembler, gas/binutils 2.11 or a recent
1999 @uref{ftp://sources.redhat.com/pub/binutils/snapshots,,snapshot of gas}.
2001 More specific information to @samp{hppa*-hp-hpux*} targets follows.
2007 @heading @anchor{hppa*-hp-hpux9}hppa*-hp-hpux9
2009 The HP assembler has major problems on this platform. We've tried to work
2010 around the worst of the problems. However, those workarounds may be causing
2011 linker crashes in some circumstances; the workarounds also probably prevent
2012 shared libraries from working. Use the GNU assembler to avoid these problems.
2015 The configuration scripts for GCC will also trigger a bug in the hpux9
2016 shell. To avoid this problem set @env{CONFIG_SHELL} to @file{/bin/ksh}
2017 and @env{SHELL} to @file{/bin/ksh} in your environment.
2024 @heading @anchor{hppa*-hp-hpux10}hppa*-hp-hpux10
2026 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
2027 @code{PHCO_19798} from HP@. HP has two sites which provide patches free of
2033 <a href="http://us-support.external.hp.com">US, Canada, Asia-Pacific, and
2037 @uref{http://us-support.external.hp.com,,}US, Canada, Asia-Pacific, and
2041 @uref{http://europe-support.external.hp.com,,Europe}
2044 The HP assembler on these systems is much better than the hpux9 assembler,
2045 but still has some problems. Most notably the assembler inserts timestamps
2046 into each object file it creates, causing the 3-stage comparison test to fail
2047 during a @samp{make bootstrap}. You should be able to continue by
2048 saying @samp{make all} after getting the failure from @samp{make
2056 @heading @anchor{hppa*-hp-hpux11}hppa*-hp-hpux11
2058 GCC 3.0 and up support HP-UX 11. You must use GNU binutils 2.11 or above on
2059 this platform. Thread support is not currently implemented for this
2060 platform, so @option{--enable-threads} does not work.
2061 See @uref{http://gcc.gnu.org/ml/gcc-prs/2002-01/msg00551.html}
2062 and @uref{http://gcc.gnu.org/ml/gcc-bugs/2002-01/msg00663.html}.
2063 GCC 2.95.x is not supported under HP-UX 11 and cannot be used to
2064 compile GCC 3.0 and up. Refer to @uref{binaries.html,,binaries} for
2065 information about obtaining precompiled GCC binaries for HP-UX.
2071 @heading @anchor{i370-*-*}i370-*-*
2072 This port is very preliminary and has many known bugs. We hope to
2073 have a higher-quality port for this machine soon.
2079 @heading @anchor{*-*-linux-gnu}*-*-linux-gnu
2081 If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install
2082 out-of-the-box. You'll get compile errors while building @samp{libstdc++}.
2083 The patch @uref{glibc-2.2.patch,,glibc-2.2.patch}, that is to be
2084 applied in the GCC source tree, fixes the compatibility problems.
2094 Currently Glibc 2.2.3 (and older releases) and GCC 3.0 are out of sync
2095 since the latest exception handling changes for GCC@. Compiling glibc
2096 with GCC 3.0 will give a binary incompatible glibc and therefore cause
2097 lots of problems and might make your system completly unusable. This
2098 will definitly need fixes in glibc but might also need fixes in GCC@. We
2099 strongly advise to wait for glibc 2.2.4 and to read the release notes of
2100 glibc 2.2.4 whether patches for GCC 3.0 are needed. You can use glibc
2101 2.2.3 with GCC 3.0, just do not try to recompile it.
2107 @heading @anchor{ix86-*-linux*aout}i?86-*-linux*aout
2108 Use this configuration to generate @file{a.out} binaries on Linux-based
2109 GNU systems. This configuration is being superseded. You must use
2110 gas/binutils version 2.5.2 or later.
2116 @heading @anchor{ix86-*-linux*}i?86-*-linux*
2118 You will need binutils 2.9.1.0.15 or newer for exception handling to work.
2120 If you receive Signal 11 errors when building on GNU/Linux, then it is
2121 possible you have a hardware problem. Further information on this can be
2122 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
2128 @heading @anchor{ix86-*-sco}i?86-*-sco
2129 Compilation with RCC is recommended. Also, it may be a good idea to
2130 link with GNU malloc instead of the malloc that comes with the system.
2136 @heading @anchor{ix86-*-sco3.2v4}i?86-*-sco3.2v4
2137 Use this configuration for SCO release 3.2 version 4.
2143 @heading @anchor{ix86-*-sco3.2v5*}i?86-*-sco3.2v5*
2144 Use this for the SCO OpenServer Release 5 family of operating systems.
2146 Unlike earlier versions of GCC, the ability to generate COFF with this
2147 target is no longer provided.
2149 Earlier versions of GCC emitted DWARF 1 when generating ELF to allow
2150 the system debugger to be used. That support was too burdensome to
2151 maintain. GCC now emits only DWARF 2 for this target. This means you
2152 may use either the UDK debugger or GDB to debug programs built by this
2155 Use of the @option{-march=pentiumpro} flag can result in
2156 unrecognized opcodes when using the native assembler on OS versions before
2157 5.0.6. (Support for P6 opcodes was added to the native ELF assembler in
2158 that version.) While it's rather rare to see these emitted by GCC yet,
2159 errors of the basic form:
2162 /usr/tmp/ccaNlqBc.s:22:unknown instruction: fcomip
2163 /usr/tmp/ccaNlqBc.s:50:unknown instruction: fucomip
2166 are symptoms of this problem. You may work around this by not
2167 building affected files with that flag, by using the GNU assembler, or
2168 by using the assembler provided with the current version of the OS@.
2169 Users of GNU assembler should see the note below for hazards on doing
2172 The native SCO assembler that is provided with the OS at no
2173 charge is normally required. If, however, you must be able to use
2174 the GNU assembler (perhaps you're compiling code with asms that
2175 require GAS syntax) you may configure this package using the flags
2176 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You must
2177 use a recent version of GNU binutils; versions past 2.9.1 seem to work
2180 In general, the @option{--with-gnu-as} option isn't as well tested
2181 as the native assembler.
2183 Look in @file{gcc/config/i386/sco5.h} (search for ``messy'') for
2184 additional OpenServer-specific flags.
2186 Systems based on OpenServer before 5.0.4 (@samp{uname -X}
2187 will tell you what you're running) require TLS597 from
2188 @uref{ftp://ftp.sco.com/TLS/,,ftp://ftp.sco.com/TLS/}
2189 for C++ constructors and destructors to work right.
2191 The system linker in (at least) 5.0.4 and 5.0.5 will sometimes
2192 do the wrong thing for a construct that GCC will emit for PIC
2193 code. This can be seen as execution testsuite failures when using
2194 @option{-fPIC} on @file{921215-1.c}, @file{931002-1.c}, @file{nestfunc-1.c}, and @file{gcov-1.c}.
2195 For 5.0.5, an updated linker that will cure this problem is
2196 available. You must install both
2197 @uref{ftp://ftp.sco.com/Supplements/rs505a/,,ftp://ftp.sco.com/Supplements/rs505a/}
2198 and @uref{ftp://ftp.sco.com/SLS/,,OSS499A}.
2200 The dynamic linker in OpenServer 5.0.5 (earlier versions may show
2201 the same problem) aborts on certain G77-compiled programs. It's particularly
2202 likely to be triggered by building Fortran code with the @option{-fPIC} flag.
2203 Although it's conceivable that the error could be triggered by other
2204 code, only G77-compiled code has been observed to cause this abort.
2205 If you are getting core dumps immediately upon execution of your
2206 G77 program---and especially if it's compiled with @option{-fPIC}---try applying
2207 @uref{sco_osr5_g77.patch,,@file{sco_osr5_g77.patch}} to your @samp{libf2c} and
2209 Affected faults, when analyzed in a debugger, will show a stack
2210 backtrace with a fault occurring in @code{rtld()} and the program
2211 running as @file{/usr/lib/ld.so.1}. This problem has been reported to SCO
2212 engineering and will hopefully be addressed in later releases.
2219 @heading @anchor{ix86-*-udk}i?86-*-udk
2221 This target emulates the SCO Universal Development Kit and requires that
2222 package be installed. (If it is installed, you will have a
2223 @file{/udk/usr/ccs/bin/cc} file present.) It's very much like the
2224 @samp{i?86-*-unixware7*} target
2225 but is meant to be used when hosting on a system where UDK isn't the
2226 default compiler such as OpenServer 5 or Unixware 2. This target will
2227 generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
2228 with the same warnings and caveats as the SCO UDK@.
2230 This target is a little tricky to build because we have to distinguish
2231 it from the native tools (so it gets headers, startups, and libraries
2232 from the right place) while making the tools not think we're actually
2233 building a cross compiler. The easiest way to do this is with a configure
2236 @samp{CC=/udk/usr/ccs/bin/cc @var{/your/path/to}/gcc/configure
2237 --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-}
2239 @emph{You should substitute @samp{i686} in the above command with the appropriate
2240 processor for your host.}
2242 After the usual @samp{make bootstrap} and
2243 @samp{make install}, you can then access the UDK-targeted GCC
2244 tools by adding @command{udk-} before the commonly known name. For
2245 example, to invoke the C compiler, you would use @command{udk-gcc}.
2246 They will coexist peacefully with any native-target GCC tools you may
2254 @heading @anchor{ia64-*-linux}ia64-*-linux
2255 IA-64 processor (also known as IPF, or Itanium Processor Family)
2258 The toolchain is not completely finished, so requirements will continue
2260 GCC 3.0.1 and later require glibc 2.2.4.
2261 GCC 3.0.2 requires binutils from 2001-09-05 or later.
2262 GCC 3.0.1 requires binutils 2.11.1 or later.
2264 None of the following versions of GCC has an ABI that is compatible
2265 with any of the other versions in this list, with the exception that
2266 Red Hat 2.96 and Trillian 000171 are compatible with each other:
2267 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
2268 This primarily affects C++ programs and programs that create shared libraries.
2269 Because of these ABI incompatibilities, GCC 3.0.2 is not recommended for
2270 user programs on GNU/Linux systems built using earlier compiler releases.
2271 GCC 3.0.2 is recommended for compiling linux, the kernel.
2272 GCC 3.0.2 is believed to be fully ABI compliant, and hence no more major
2273 ABI changes are expected.
2279 @heading @anchor{*-lynx-lynxos}*-lynx-lynxos
2280 LynxOS 2.2 and earlier comes with GCC 1.x already installed as
2281 @file{/bin/gcc}. You should compile with this instead of @file{/bin/cc}.
2282 You can tell GCC to use the GNU assembler and linker, by specifying
2283 @samp{--with-gnu-as --with-gnu-ld} when configuring. These will produce
2284 COFF format object files and executables; otherwise GCC will use the
2285 installed tools, which produce @file{a.out} format executables.
2290 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
2292 @heading @anchor{*-ibm-aix*}*-ibm-aix*
2294 AIX Make frequently has problems with GCC makefiles. GNU Make 3.76 or
2295 newer is recommended to build on this platform.
2297 Errors involving @code{alloca} when building GCC generally are due
2298 to an incorrect definition of @code{CC} in the Makefile or mixing files
2299 compiled with the native C compiler and GCC@. During the stage1 phase of
2300 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
2301 (not @command{xlc}). Once @command{configure} has been informed of
2302 @command{xlc}, one needs to use @samp{make distclean} to remove the
2303 configure cache files and ensure that @env{CC} environment variable
2304 does not provide a definition that will confuse @command{configure}.
2305 If this error occurs during stage2 or later, then the problem most likely
2306 is the version of Make (see above).
2308 The GNU Assembler incorrectly reports that it supports WEAK symbols on
2309 AIX which causes GCC to try to utilize weak symbol functionality which
2310 is not really supported on the platform. The native @command{as} and
2311 @command{ld} still are recommended. The native AIX tools do
2312 interoperate with GCC@.
2314 Building @file{libstdc++.a} requires a fix for a AIX Assembler bug
2315 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1).
2317 Linking executables and shared libraries may produce warnings of
2318 duplicate symbols. The assembly files generated by GCC for AIX always
2319 have included multiple symbol definitions for certain global variable
2320 and function declarations in the original program. The warnings should
2321 not prevent the linker from producing a correct library or runnable
2324 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
2325 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
2326 to parse archive libraries did not handle the new format correctly.
2327 These routines are used by GCC and result in error messages during
2328 linking such as ``not a COFF file''. The version of the routines shipped
2329 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
2330 option of the archive command may be used to create archives of 32-bit
2331 objects using the original ``small format''. A correct version of the
2332 routines is shipped with AIX 4.3.2 and above.
2334 Some versions of the AIX binder (linker) can fail with a relocation
2335 overflow severe error when the @option{-bbigtoc} option is used to link
2336 GCC-produced object files into an executable that overflows the TOC@. A fix
2337 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
2338 available from IBM Customer Support and from its
2339 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2340 website as PTF U455193.
2342 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
2343 with a segmentation fault when invoked by any version of GCC@. A fix for
2344 APAR IX87327 is available from IBM Customer Support and from its
2345 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2346 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
2348 The initial assembler shipped with AIX 4.3.0 generates incorrect object
2349 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
2350 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
2351 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2352 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
2354 AIX provides National Language Support (NLS)@. Compilers and assemblers
2355 use NLS to support locale-specific representations of various data
2356 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
2357 separating decimal fractions). There have been problems reported where
2358 GCC does not produce the same floating-point formats that the assembler
2359 expects. If one encounters this problem, set the @env{LANG}
2360 environment variable to @samp{C} or @samp{En_US}.
2362 By default, GCC for AIX 4.1 and above produces code that can be used on
2363 both Power or PowerPC processors.
2365 A default can be specified with the @option{-mcpu=@var{cpu_type}}
2366 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
2372 @heading @anchor{m32r-*-elf}m32r-*-elf
2373 Mitsubishi M32R processor.
2374 This configuration is intended for embedded systems.
2380 @heading @anchor{m68000-hp-bsd}m68000-hp-bsd
2381 HP 9000 series 200 running BSD@. Note that the C compiler that comes
2382 with this system cannot compile GCC; contact @email{law@@cygnus.com}
2383 to get binaries of GCC for bootstrapping.
2389 @heading @anchor{m6811-elf}m6811-elf
2390 Motorola 68HC11 family micro controllers. These are used in embedded
2391 applications. There are no standard Unix configurations.
2397 @heading @anchor{m6812-elf}m6812-elf
2398 Motorola 68HC12 family micro controllers. These are used in embedded
2399 applications. There are no standard Unix configurations.
2405 @heading @anchor{m68k-att-sysv}m68k-att-sysv
2406 AT&T 3b1, a.k.a.@: 7300 PC@. This version of GCC cannot
2407 be compiled with the system C compiler, which is too buggy.
2408 You will need to get a previous version of GCC and use it to
2409 bootstrap. Binaries are available from the OSU-CIS archive, at
2410 @uref{ftp://archive.cis.ohio-state.edu/pub/att7300/}.
2416 @heading @anchor{m68k-crds-unos}m68k-crds-unos
2417 Use @samp{configure unos} for building on Unos.
2419 The Unos assembler is named @code{casm} instead of @code{as}. For some
2420 strange reason linking @file{/bin/as} to @file{/bin/casm} changes the
2421 behavior, and does not work. So, when installing GCC, you should
2422 install the following script as @file{as} in the subdirectory where
2423 the passes of GCC are installed:
2430 The default Unos library is named @file{libunos.a} instead of
2431 @file{libc.a}. To allow GCC to function, either change all
2432 references to @option{-lc} in @file{gcc.c} to @option{-lunos} or link
2433 @file{/lib/libc.a} to @file{/lib/libunos.a}.
2435 @cindex @code{alloca}, for Unos
2436 When compiling GCC with the standard compiler, to overcome bugs in
2437 the support of @code{alloca}, do not use @option{-O} when making stage 2.
2438 Then use the stage 2 compiler with @option{-O} to make the stage 3
2439 compiler. This compiler will have the same characteristics as the usual
2440 stage 2 compiler on other systems. Use it to make a stage 4 compiler
2441 and compare that with stage 3 to verify proper compilation.
2443 (Perhaps simply defining @code{ALLOCA} in @file{x-crds} as described in
2444 the comments there will make the above paragraph superfluous. Please
2445 inform us of whether this works.)
2447 Unos uses memory segmentation instead of demand paging, so you will need
2448 a lot of memory. 5 Mb is barely enough if no other tasks are running.
2449 If linking @file{cc1} fails, try putting the object files into a library
2450 and linking from that library.
2456 @heading @anchor{m68k-hp-hpux}m68k-hp-hpux
2457 HP 9000 series 300 or 400 running HP-UX@. HP-UX version 8.0 has a bug in
2458 the assembler that prevents compilation of GCC@. This
2459 bug manifests itself during the first stage of compilation, while
2460 building @file{libgcc2.a}:
2464 cc1: warning: `-g' option not supported on this version of GCC
2465 cc1: warning: `-g1' option not supported on this version of GCC
2466 ./xgcc: Internal compiler error: program as got fatal signal 11
2469 A patched version of the assembler is available as the file
2470 @uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you
2471 have HP software support, the patch can also be obtained directly from
2472 HP, as described in the following note:
2475 This is the patched assembler, to patch SR#1653-010439, where the
2476 assembler aborts on floating point constants.
2478 The bug is not really in the assembler, but in the shared library
2479 version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is
2480 SR#4701-078451. Anyway, the attached assembler uses the archive
2481 library version of ``cvtnum(3c)'' and thus does not exhibit the bug.
2484 This patch is also known as PHCO_4484.
2486 In addition, if you wish to use gas, you must use
2487 gas version 2.1 or later, and you must use the GNU linker version 2.1 or
2488 later. Earlier versions of gas relied upon a program which converted the
2489 gas output into the native HP-UX format, but that program has not been
2490 kept up to date. gdb does not understand that native HP-UX format, so
2491 you must use gas if you wish to use gdb.
2493 On HP-UX version 8.05, but not on 8.07 or more recent versions, the
2494 @code{fixproto} shell script triggers a bug in the system shell. If you
2495 encounter this problem, upgrade your operating system or use BASH (the
2496 GNU shell) to run @code{fixproto}. This bug will cause the fixproto
2497 program to report an error of the form:
2500 ./fixproto: sh internal 1K buffer overflow
2503 To fix this, you can also change the first line of the fixproto script
2515 @heading @anchor{m68k-ncr-*}m68k-ncr-*
2516 On the Tower models 4@var{n}0 and 6@var{n}0, by default a process is not
2517 allowed to have more than one megabyte of memory. GCC cannot compile
2518 itself (or many other programs) with @option{-O} in that much memory.
2520 To solve this problem, reconfigure the kernel adding the following line
2521 to the configuration file:
2532 @heading @anchor{m68k-sun}m68k-sun
2533 Sun 3. We do not provide a configuration file to use the Sun FPA by
2534 default, because programs that establish signal handlers for floating
2535 point traps inherently cannot work with the FPA@.
2541 @heading @anchor{m68k-sun-sunos4.1.1}m68k-sun-sunos4.1.1
2543 It is reported that you may need the GNU assembler on this platform.
2550 @heading @anchor{mips-*-*}mips-*-*
2551 If on a MIPS system you get an error message saying ``does not have gp
2552 sections for all it's [sic] sectons [sic]'', don't worry about it. This
2553 happens whenever you use GAS with the MIPS linker, but there is not
2554 really anything wrong, and it is okay to use the output file. You can
2555 stop such warnings by installing the GNU linker.
2557 It would be nice to extend GAS to produce the gp tables, but they are
2558 optional, and there should not be a warning about their absence.
2560 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
2562 This configuration has considerable problems, which will be fixed in a
2565 In order to compile GCC on an SGI running IRIX 5, the ``compiler_dev.hdr''
2566 subsystem must be installed from the IDO CD-ROM supplied by Silicon
2567 Graphics. It is also available for download from
2568 @uref{http://www.sgi.com/developers/devtools/apis/ido.html,,http://www.sgi.com/developers/devtools/apis/ido.html}.
2570 @code{make compare} may fail on version 5 of IRIX unless you add
2571 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
2572 assembler input file is stored in the object file, and that makes
2573 comparison fail if it differs between the @code{stage1} and
2574 @code{stage2} compilations. The option @option{-save-temps} forces a
2575 fixed name to be used for the assembler input file, instead of a
2576 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
2577 unless the comparisons fail without that option. If you do you
2578 @option{-save-temps}, you will have to manually delete the @samp{.i} and
2579 @samp{.s} files after each series of compilations.
2581 If you use the MIPS C compiler to bootstrap, it may be necessary
2582 to increase its table size for switch statements with the
2583 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
2584 optimization option, you also need to use @option{-Olimit 3000}.
2586 To enable debugging under IRIX 5, you must use GNU @command{as} 2.11.2
2588 and use the @option{--with-gnu-as} configure option when configuring GCC.
2589 GNU @command{as} is distributed as part of the binutils package.
2590 When using release 2.11.2, you need to apply a patch
2591 @uref{http://sources.redhat.com/ml/binutils/2001-07/msg00352.html,,http://sources.redhat.com/ml/binutils/2001-07/msg00352.html}
2592 which will be included in the next release of binutils.
2594 When building GCC, the build process loops rebuilding @command{cc1} over
2595 and over again. This happens on @samp{mips-sgi-irix5.2}, and possibly
2596 other platforms. It has been reported that this is a known bug in the
2597 @command{make} shipped with IRIX 5.2. We recommend you use GNU
2598 @command{make} instead of the vendor supplied @command{make} program;
2599 however, you may have success with @command{smake} on IRIX 5.2 if you do
2600 not have GNU @command{make} available.
2606 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
2608 If you are using IRIX @command{cc} as your bootstrap compiler, you must
2609 ensure that the N32 ABI is in use. To test this, compile a simple C
2610 file with @command{cc} and then run @command{file} on the
2611 resulting object file. The output should look like:
2614 test.o: ELF N32 MSB @dots{}
2620 test.o: ELF 32-bit MSB @dots{}
2626 test.o: ELF 64-bit MSB @dots{}
2629 then your version of @command{cc} uses the O32 or N64 ABI by default. You
2630 should set the environment variable @env{CC} to @samp{cc -n32}
2631 before configuring GCC@.
2633 If you want the resulting @command{gcc} to run on old 32-bit systems
2634 with the MIPS R4400 CPU, you need to ensure that only code for the mips3
2635 instruction set architecture (ISA) is generated. While GCC 3.x does
2636 this correctly, both GCC 2.95 and SGI's MIPSpro @command{cc} may change
2637 the ISA depending on the machine where GCC is built. Using one of them
2638 as the bootstrap compiler may result in mips4 code, which won't run at
2639 all on mips3-only systems. For the test program above, you should see:
2642 test.o: ELF N32 MSB mips-3 @dots{}
2648 test.o: ELF N32 MSB mips-4 @dots{}
2651 instead, you should set the environment variable @env{CC} to @samp{cc
2652 -n32 -mips3} or @samp{gcc -mips3} respectively before configuring GCC@.
2654 GCC on IRIX 6 is usually built to support both the N32 and N64 ABIs. If
2655 you build GCC on a system that doesn't have the N64 libraries installed,
2656 you need to configure with @option{--disable-multilib} so GCC doesn't
2657 try to use them. Look for @file{/usr/lib64/libc.so.1} to see if you
2658 have the 64-bit libraries installed.
2660 You must @emph{not} use GNU @command{as} (which isn't built anyway as of
2661 binutils 2.11.2) on IRIX 6 platforms; doing so will only cause problems.
2663 GCC does not currently support generating O32 ABI binaries in the
2664 @samp{mips-sgi-irix6} configurations. It is possible to create a GCC
2665 with O32 ABI only support by configuring it for the @samp{mips-sgi-irix5}
2666 target and using a patched GNU @command{as} 2.11.2 as documented in the
2667 @uref{#mips-sgi-irix5,,@samp{mips-sgi-irix5}} section above. Using the
2668 native assembler requires patches to GCC which will be included in a
2669 future release. It is
2670 expected that O32 ABI support will be available again in a future release.
2672 The @option{--enable-threads} option doesn't currently work, a patch is
2673 in preparation for a future release. The @option{--enable-libgcj}
2674 option is disabled by default: IRIX 6 uses a very low default limit
2675 (20480) for the command line length. Although libtool contains a
2676 workaround for this problem, at least the N64 @samp{libgcj} is known not
2677 to build despite this, running into an internal error of the native
2678 @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
2679 its maximum of 262144 bytes. If you have root access, you can use the
2680 @command{systune} command to do this.
2682 GCC does not correctly pass/return structures which are
2683 smaller than 16 bytes and which are not 8 bytes. The problem is very
2684 involved and difficult to fix. It affects a number of other targets also,
2685 but IRIX 6 is affected the most, because it is a 64 bit target, and 4 byte
2686 structures are common. The exact problem is that structures are being padded
2687 at the wrong end, e.g.@: a 4 byte structure is loaded into the lower 4 bytes
2688 of the register when it should be loaded into the upper 4 bytes of the
2691 GCC is consistent with itself, but not consistent with the SGI C compiler
2692 (and the SGI supplied runtime libraries), so the only failures that can
2693 happen are when there are library functions that take/return such
2694 structures. There are very few such library functions. Currently this
2695 is known to affect @code{inet_ntoa}, @code{inet_lnaof},
2696 @code{inet_netof}, @code{inet_makeaddr}, and @code{semctl}. Until the
2697 bug is fixed, GCC contains workarounds for the known affected functions.
2699 See @uref{http://freeware.sgi.com/,,http://freeware.sgi.com/} for more
2700 information about using GCC on IRIX platforms.
2706 @heading @anchor{powerpc*-*-*}powerpc-*-*
2708 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
2709 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
2715 @heading @anchor{powerpc-*-darwin*}powerpc-*-darwin*
2716 PowerPC running Darwin (Mac OS X kernel).
2718 GCC 3.0 does not support Darwin, but 3.1 and later releases will work.
2720 Pre-installed versions of Mac OS X may not include any developer tools,
2721 meaning that you will not be able to build GCC from source. Tool
2722 binaries are available at
2723 @uref{http://www.opensource.apple.com/projects/darwin} (free
2724 registration required).
2726 Versions of the assembler prior to ``cctools-364'' cannot handle the
2727 4-argument form of rlwinm and related mask-using instructions. Darwin
2728 1.3 (Mac OS X 10.0) uses cctools-353 for instance. To get cctools-364,
2729 check out @file{cctools} with tag @samp{Apple-364}, build it, and
2730 install the assembler as @file{usr/bin/as}. See
2731 @uref{http://www.opensource.apple.com/tools/cvs/docs.html} for details.
2733 Also, the default stack limit of 512K is too small, and a bootstrap will
2734 typically fail when self-compiling @file{expr.c}. Set the stack to 800K
2735 or more, for instance by doing @samp{limit stack 800}. It's also
2736 convenient to use the GNU preprocessor instead of Apple's during the
2737 first stage of bootstrapping; this is automatic when doing @samp{make
2738 bootstrap}, but to do it from the toplevel objdir you will need to say
2739 @samp{make CC='cc -no-cpp-precomp' bootstrap}.
2741 Note that the version of GCC shipped by Apple typically includes a
2742 number of extensions not available in a standard GCC release. These
2743 extensions are generally specific to Mac programming.
2749 @heading @anchor{powerpc-*-elf}powerpc-*-elf, powerpc-*-sysv4
2750 PowerPC system in big endian mode, running System V.4.
2756 @heading @anchor{powerpc-*-linux-gnu*}powerpc-*-linux-gnu*
2759 @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.12.90.0.7}
2760 or newer for a working GCC@.
2766 @heading @anchor{powerpc-*-netbsd*}powerpc-*-netbsd*
2767 PowerPC system in big endian mode running NetBSD@. To build the
2768 documentation you will need Texinfo version 4.1 (NetBSD 1.5.1 included
2769 Texinfo version 3.12).
2775 @heading @anchor{powerpc-*-eabiaix}powerpc-*-eabiaix
2776 Embedded PowerPC system in big endian mode with @option{-mcall-aix} selected as
2783 @heading @anchor{powerpc-*-eabisim}powerpc-*-eabisim
2784 Embedded PowerPC system in big endian mode for use in running under the
2791 @heading @anchor{powerpc-*-eabi}powerpc-*-eabi
2792 Embedded PowerPC system in big endian mode.
2798 @heading @anchor{powerpcle-*-elf}powerpcle-*-elf, powerpcle-*-sysv4
2799 PowerPC system in little endian mode, running System V.4.
2805 @heading @anchor{powerpcle-*-eabisim}powerpcle-*-eabisim
2806 Embedded PowerPC system in little endian mode for use in running under
2813 @heading @anchor{powerpcle-*-eabi}powerpcle-*-eabi
2814 Embedded PowerPC system in little endian mode.
2820 @heading @anchor{powerpcle-*-winnt}powerpcle-*-winnt, powerpcle-*-pe
2821 PowerPC system in little endian mode running Windows NT@.
2827 @heading @anchor{s390-*-linux*}s390-*-linux*
2828 S/390 system running Linux for S/390@.
2834 @heading @anchor{s390x-*-linux*}s390x-*-linux*
2835 zSeries system (64 Bit) running Linux for zSeries@.
2841 @c Please use Solaris 2 to refer to all release of Solaris, starting
2842 @c with 2.0 until 2.6, 7, and 8. Solaris 1 was a marketing name for
2843 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
2844 @c alone is too unspecific and must be avoided.
2845 @heading @anchor{*-*-solaris2*}*-*-solaris2*
2847 Sun does not ship a C compiler with Solaris 2. To bootstrap and install
2848 GCC you first have to install a pre-built compiler, see our
2849 @uref{binaries.html,,binaries page} for details.
2851 The Solaris 2 @command{/bin/sh} will often fail to configure
2852 @file{libstdc++-v3}, @file{boehm-gc} or
2853 @file{libjava}. If you encounter this problem, set @env{CONFIG_SHELL} to
2854 @command{/bin/ksh} in your environment before running @command{configure}.
2856 Solaris 2 comes with a number of optional OS packages. Some of these
2857 packages are needed to use GCC fully, namely @code{SUNWarc},
2858 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
2859 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
2860 optional packages when installing Solaris 2, you will need to verify that
2861 the packages that GCC needs are installed.
2863 To check whether an optional package is installed, use
2864 the @command{pkginfo} command. To add an optional package, use the
2865 @command{pkgadd} command. For further details, see the Solaris 2
2868 Trying to use the linker and other tools in
2869 @file{/usr/ucb} to install GCC has been observed to cause trouble.
2870 For example, the linker may hang indefinitely. The fix is to remove
2871 @file{/usr/ucb} from your @env{PATH}.
2873 All releases of GNU binutils prior to 2.11.2 have known bugs on this
2874 platform. We recommend the use of GNU binutils 2.11.2 or the vendor
2875 tools (Sun @command{as}, Sun @command{ld}).
2877 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
2878 newer: @command{g++} will complain that types are missing. These headers assume
2879 that omitting the type means @code{int}; this assumption worked for C89 but
2880 is wrong for C++, and is now wrong for C99 also.
2882 @command{g++} accepts such (invalid) constructs with the option
2883 @option{-fpermissive}; it
2884 will assume that any missing type is @code{int} (as defined by C89).
2886 There are patches for Solaris 2.6 (105633-56 or newer for SPARC,
2887 106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC,
2888 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
2889 108653-22 for Intel) that fix this bug.
2895 @heading @anchor{sparc-sun-solaris2*}sparc-sun-solaris2*
2897 When GCC is configured to use binutils 2.11.2 or later the binaries
2898 produced are smaller than the ones produced using Sun's native tools;
2899 this difference is quite significant for binaries containing debugging
2902 Sun @command{as} 4.x is broken in that it cannot cope with long symbol names.
2903 A typical error message might look similar to the following:
2905 @samp{/usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041:
2906 error: can't compute value of an expression involving an external symbol.}
2908 This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris
2909 2.6 and has been fixed in later (5.x) versions of the assembler,
2910 starting with Solaris 7.
2912 Starting with Solaris 7, the operating system is capable of executing
2913 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
2914 this; the @option{-m64} option enables 64-bit code generation.
2915 However, if all you want is code tuned for the UltraSPARC CPU, you
2916 should try the @option{-mtune=ultrasparc} option instead, which produces
2917 code that, unlike full 64-bit code, can still run on non-UltraSPARC
2920 When configuring on a Solaris 7 or later system that is running a kernel
2921 that supports only 32-bit binaries, one must configure with
2922 @option{--disable-multilib}, since we will not be able to build the
2923 64-bit target libraries.
2929 @heading @anchor{sparc-sun-solaris2.7}sparc-sun-solaris2.7
2931 Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
2932 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
2933 and later, including all EGCS releases. Sun formerly recommended
2934 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
2935 recommend it only for people who use Sun's compilers.
2937 Here are some workarounds to this problem:
2940 Do not install Sun patch 107058-01 until after Sun releases a
2941 complete patch for bug 4210064. This is the simplest course to take,
2942 unless you must also use Sun's C compiler. Unfortunately 107058-01
2943 is preinstalled on some new Solaris 7-based hosts, so you may have to
2947 Copy the original, unpatched Solaris 7
2948 @command{/usr/ccs/bin/as} into
2949 @command{/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/3.1/as},
2950 adjusting the latter name to fit your local conventions and software
2954 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
2955 both 107058-01 and 106950-03 installed has reported the bug with GCC
2956 and Sun's dynamic linker. This last course of action is riskiest,
2957 for two reasons. First, you must install 106950 on all hosts that
2958 run code generated by GCC; it doesn't suffice to install it only on
2959 the hosts that run GCC itself. Second, Sun says that 106950-03 is
2960 only a partial fix for bug 4210064, but Sun doesn't know whether the
2961 partial fix is adequate for GCC@. Revision -08 or later should fix
2962 the bug. The current (as of 2001-09-24) revision is -14, and is included in
2963 the Solaris 7 Recommended Patch Cluster.
2971 @heading @anchor{sparc-sun-sunos4*}sparc-sun-sunos4*
2973 A bug in the SunOS 4 linker will cause it to crash when linking
2974 @option{-fPIC} compiled objects (and will therefore not allow you to build
2977 To fix this problem you can either use the most recent version of
2978 binutils or get the latest SunOS 4 linker patch (patch ID 100170-10)
2979 from Sun's patch site.
2981 Sometimes on a Sun 4 you may observe a crash in the program
2982 @command{genflags} or @command{genoutput} while building GCC. This is said to
2983 be due to a bug in @command{sh}. You can probably get around it by running
2984 @command{genflags} or @command{genoutput} manually and then retrying the
2991 @heading @anchor{sparc-unknown-linux-gnulibc1}sparc-unknown-linux-gnulibc1
2993 It has been reported that you might need
2994 @uref{ftp://ftp.yggdrasil.com/private/hjl,,binutils 2.8.1.0.23}
2995 for this platform, too.
3002 @heading @anchor{sparc-*-linux*}sparc-*-linux*
3004 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
3005 or newer on this platform. All earlier binutils and glibc
3006 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
3013 @heading @anchor{sparc64-*-*}sparc64-*-*
3015 GCC version 2.95 is not able to compile code correctly for
3016 @code{sparc64} targets. Users of the Linux kernel, at least,
3017 can use the @code{sparc32} program to start up a new shell
3018 invocation with an environment that causes @command{configure} to
3019 recognize (via @samp{uname -a}) the system as @samp{sparc-*-*} instead.
3025 @heading @anchor{sparcv9-*-solaris2*}sparcv9-*-solaris2*
3027 The following compiler flags must be specified in the configure
3028 step in order to bootstrap this target with the Sun compiler:
3031 % CC="cc -xildoff -xarch=v9" @var{srcdir}/configure [@var{options}] [@var{target}]
3034 @option{-xildoff} turns off the incremental linker, and @option{-xarch=v9}
3035 specifies the v9 architecture to the Sun linker and assembler.
3041 @heading @anchor{#*-*-sysv*}*-*-sysv*
3042 On System V release 3, you may get this error message
3046 ld fatal: failed to write symbol name @var{something}
3047 in strings table for file @var{whatever}
3050 This probably indicates that the disk is full or your ulimit won't allow
3051 the file to be as large as it needs to be.
3053 This problem can also result because the kernel parameter @code{MAXUMEM}
3054 is too small. If so, you must regenerate the kernel and make the value
3055 much larger. The default value is reported to be 1024; a value of 32768
3056 is said to work. Smaller values may also work.
3058 On System V, if you get an error like this,
3061 /usr/local/lib/bison.simple: In function `yyparse':
3062 /usr/local/lib/bison.simple:625: virtual memory exhausted
3066 that too indicates a problem with disk space, ulimit, or @code{MAXUMEM}.
3068 On a System V release 4 system, make sure @file{/usr/bin} precedes
3069 @file{/usr/ucb} in @code{PATH}. The @code{cc} command in
3070 @file{/usr/ucb} uses libraries which have bugs.
3076 @heading @anchor{vax-dec-ultrix}vax-dec-ultrix
3077 Don't try compiling with VAX C (@code{vcc}). It produces incorrect code
3078 in some cases (for example, when @code{alloca} is used).
3084 @heading @anchor{xtensa-*-elf}xtensa-*-elf
3086 This target is intended for embedded Xtensa systems using the
3087 @samp{newlib} C library. It uses ELF but does not support shared
3088 objects. Designed-defined instructions specified via the
3089 Tensilica Instruction Extension (TIE) language are only supported
3090 through inline assembly.
3092 The Xtensa configuration information must be specified prior to
3093 building GCC@. The @file{gcc/config/xtensa/xtensa-config.h} header
3094 file contains the configuration information. If you created your
3095 own Xtensa configuration with the Xtensa Processor Generator, the
3096 downloaded files include a customized copy of this header file,
3097 which you can use to replace the default header file.
3103 @heading @anchor{xtensa-*-linux*}xtensa-*-linux*
3105 This target is for Xtensa systems running GNU/Linux. It supports ELF
3106 shared objects and the GNU C library (glibc). It also generates
3107 position-independent code (PIC) regardless of whether the
3108 @option{-fpic} or @option{-fPIC} options are used. In other
3109 respects, this target is the same as the
3110 @uref{#xtensa-*-elf,,@samp{xtensa-*-elf}} target.
3116 @heading @anchor{windows}Microsoft Windows (32 bit)
3118 A port of GCC 2.95.x is included with the
3119 @uref{http://www.cygwin.com/,,Cygwin environment}.
3121 Current (as of early 2001) snapshots of GCC will build under Cygwin
3122 without modification.
3128 @heading @anchor{os2}OS/2
3130 GCC does not currently support OS/2. However, Andrew Zabolotny has been
3131 working on a generic OS/2 port with pgcc. The current code can be found
3132 at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
3134 An older copy of GCC 2.8.1 is included with the EMX tools available at
3135 @uref{ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/,,
3136 ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/}.
3142 @heading @anchor{older}Older systems
3144 GCC contains support files for many older (1980s and early
3145 1990s) Unix variants. For the most part, support for these systems
3146 has not been deliberately removed, but it has not been maintained for
3147 several years and may suffer from bitrot.
3149 Starting with GCC 3.1, each release has a list of ``obsoleted'' systems.
3150 Support for these systems is still present in that release, but
3151 @command{configure} will fail unless the @option{--enable-obsolete}
3152 option is given. Unless a maintainer steps forward, support for these
3153 systems will be removed from the next release of GCC@.
3155 Support for old systems as hosts for GCC can cause problems if the
3156 workarounds for compiler, library and operating system bugs affect the
3157 cleanliness or maintainability of the rest of GCC@. In some cases, to
3158 bring GCC up on such a system, if still possible with current GCC, may
3159 require first installing an old version of GCC which did work on that
3160 system, and using it to compile a more recent GCC, to avoid bugs in the
3161 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
3162 @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror
3163 sites}. Header bugs may generally be avoided using
3164 @command{fixincludes}, but bugs or deficiencies in libraries and the
3165 operating system may still cause problems.
3167 Support for older systems as targets for cross-compilation is less
3168 problematic than support for them as hosts for GCC; if an enthusiast
3169 wishes to make such a target work again (including resurrecting any of
3170 the targets that never worked with GCC 2, starting from the last CVS
3171 version before they were removed), patches
3172 @uref{../contribute.html,,following the usual requirements} would be
3173 likely to be accepted, since they should not affect the support for more
3176 For some systems, old versions of GNU binutils may also be useful,
3177 and are available from @file{pub/binutils/old-releases} on
3178 @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}.
3180 Some of the information on specific systems above relates to
3181 such older systems, but much of the information
3182 about GCC on such systems (which may no longer be applicable to
3183 current GCC) is to be found in the GCC texinfo manual.
3189 @heading @anchor{elf_targets}all ELF targets (SVR4, Solaris 2, etc.)
3191 C++ support is significantly better on ELF targets if you use the
3192 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
3193 inlines, vtables and template instantiations will be discarded
3203 @uref{./index.html,,Return to the GCC Installation page}
3207 @c ***Old documentation******************************************************
3209 @include install-old.texi
3216 @uref{./index.html,,Return to the GCC Installation page}
3220 @c ***GFDL********************************************************************
3229 @uref{./index.html,,Return to the GCC Installation page}
3233 @c ***************************************************************************
3234 @c Part 6 The End of the Document
3236 @comment node-name, next, previous, up
3237 @node Concept Index, , GNU Free Documentation License, Top
3241 @unnumbered Concept Index