1 \input texinfo.tex @c -*-texinfo-*-
4 @setfilename gccinstall.info
5 @settitle Installing GCC
10 @c Specify title for specific html page
12 @settitle Installing GCC
15 @settitle Host/Target specific installation notes for GCC
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 @uref{http://gcc.gnu.org/buildstat.html}.
152 These lists are updated as new information becomes available.
154 The installation procedure itself is broken into five steps.
158 * Downloading the source::
161 * Testing:: (optional)
168 @uref{download.html,,Downloading the source}
170 @uref{configure.html,,Configuration}
172 @uref{build.html,,Building}
174 @uref{test.html,,Testing} (optional)
176 @uref{finalinstall.html,,Final install}
180 Please note that GCC does not support @samp{make uninstall} and probably
181 won't do so in the near future as this would open a can of worms. Instead,
182 we suggest that you install GCC into a directory of its own and simply
183 remove that directory when you do not need that specific version of GCC
184 any longer, and, if shared libraries are installed there as well, no
185 more binaries exist that use them.
188 There are also some @uref{old.html,,old installation instructions},
189 which are mostly obsolete but still contain some information which has
190 not yet been merged into the main part of this manual.
198 @uref{./index.html,,Return to the GCC Installation page}
204 @c ***Downloading the source**************************************************
206 @comment node-name, next, previous, up
207 @node Downloading the source, Configuration, , Installing GCC
211 @chapter Downloading GCC
213 @cindex Downloading GCC
214 @cindex Downloading the Source
216 GCC is distributed via @uref{http://gcc.gnu.org/cvs.html,,CVS} and FTP
217 tarballs compressed with @command{gzip} or
218 @command{bzip2}. It is possible to download a full distribution or specific
221 Please refer to our @uref{http://gcc.gnu.org/releases.html,,releases web page}
222 for information on how to obtain GCC@.
224 The full distribution includes the C, C++, Objective-C, Fortran, Java,
225 and Ada (in case of GCC 3.1 and later) compilers. The full distribution
226 also includes runtime libraries for C++, Objective-C, Fortran, and Java.
227 In GCC 3.0 and later versions, GNU compiler testsuites are also included
228 in the full distribution.
230 If you choose to download specific components, you must download the core
231 GCC distribution plus any language specific distributions you wish to
232 use. The core distribution includes the C language front end as well as the
233 shared components. Each language has a tarball which includes the language
234 front end as well as the language runtime (when appropriate).
236 Unpack the core distribution as well as any language specific
237 distributions in the same directory.
239 If you also intend to build binutils (either to upgrade an existing
240 installation or for use in place of the corresponding tools of your
241 OS), unpack the binutils distribution either in the same directory or
242 a separate one. In the latter case, add symbolic links to any
243 components of the binutils you intend to build alongside the compiler
244 (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
245 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
252 @uref{./index.html,,Return to the GCC Installation page}
256 @c ***Configuration***********************************************************
258 @comment node-name, next, previous, up
259 @node Configuration, Building, Downloading the source, Installing GCC
263 @chapter Installing GCC: Configuration
265 @cindex Configuration
266 @cindex Installing GCC: Configuration
268 Like most GNU software, GCC must be configured before it can be built.
269 This document describes the recommended configuration procedure
270 for both native and cross targets.
272 We use @var{srcdir} to refer to the toplevel source directory for
273 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
275 If you obtained the sources via CVS, @var{srcdir} must refer to the top
276 @file{gcc} directory, the one where the @file{MAINTAINERS} can be found,
277 and not its @file{gcc} subdirectory, otherwise the build will fail.
279 If either @var{srcdir} or @var{objdir} is located on an automounted NFS
280 file system, the shell's built-in @command{pwd} command will return
281 temporary pathnames. Using these can lead to various sorts of build
282 problems. To avoid this issue, set the @env{PWDCMD} environment
283 variable to an automounter-aware @command{pwd} command, e.g.,
284 @command{pawd} or @command{amq -w}, during the configuration and build
287 First, we @strong{highly} recommend that GCC be built into a
288 separate directory than the sources which does @strong{not} reside
289 within the source tree. This is how we generally build GCC; building
290 where @var{srcdir} == @var{objdir} should still work, but doesn't
291 get extensive testing; building where @var{objdir} is a subdirectory
292 of @var{srcdir} is unsupported.
294 If you have previously built GCC in the same directory for a
295 different target machine, do @samp{make distclean} to delete all files
296 that might be invalid. One of the files this deletes is @file{Makefile};
297 if @samp{make distclean} complains that @file{Makefile} does not exist
298 or issues a message like ``don't know how to make distclean'' it probably
299 means that the directory is already suitably clean. However, with the
300 recommended method of building in a separate @var{objdir}, you should
301 simply use a different @var{objdir} for each target.
303 Second, when configuring a native system, either @command{cc} or
304 @command{gcc} must be in your path or you must set @env{CC} in
305 your environment before running configure. Otherwise the configuration
308 Note that the bootstrap compiler and the resulting GCC must be link
309 compatible, else the bootstrap will fail with linker errors about
310 incompatible object file formats. Several multilibed targets are
311 affected by this requirement, see
313 @ref{Specific, host/target specific installation notes}.
316 @uref{specific.html,,host/target specific installation notes}.
324 % @var{srcdir}/configure [@var{options}] [@var{target}]
328 @heading Target specification
331 GCC has code to correctly determine the correct value for @var{target}
332 for nearly all native systems. Therefore, we highly recommend you not
333 provide a configure target when configuring a native compiler.
336 @var{target} must be specified as @option{--target=@var{target}}
337 when configuring a cross compiler; examples of valid targets would be
338 i960-rtems, m68k-coff, sh-elf, etc.
341 Specifying just @var{target} instead of @option{--target=@var{target}}
342 implies that the host defaults to @var{target}.
346 @heading Options specification
348 Use @var{options} to override several configure time options for
349 GCC@. A list of supported @var{options} follows; @command{configure
350 --help} may list other options, but those not listed below may not
351 work and should not normally be used.
354 @item --prefix=@var{dirname}
355 Specify the toplevel installation
356 directory. This is the recommended way to install the tools into a directory
357 other than the default. The toplevel installation directory defaults to
360 We @strong{highly} recommend against @var{dirname} being the same or a
361 subdirectory of @var{objdir} or vice versa.
363 These additional options control where certain parts of the distribution
364 are installed. Normally you should not need to use these options.
366 @item --exec-prefix=@var{dirname}
367 Specify the toplevel installation directory for architecture-dependent
368 files. The default is @file{@var{prefix}}.
370 @item --bindir=@var{dirname}
371 Specify the installation directory for the executables called by users
372 (such as @command{gcc} and @command{g++}). The default is
373 @file{@var{exec-prefix}/bin}.
375 @item --libdir=@var{dirname}
376 Specify the installation directory for object code libraries and
377 internal parts of GCC@. The default is @file{@var{exec-prefix}/lib}.
379 @item --with-slibdir=@var{dirname}
380 Specify the installation directory for the shared libgcc library. The
381 default is @file{@var{libdir}}.
383 @item --infodir=@var{dirname}
384 Specify the installation directory for documentation in info format.
385 The default is @file{@var{prefix}/info}.
387 @item --datadir=@var{dirname}
388 Specify the installation directory for some architecture-independent
389 data files referenced by GCC@. The default is @file{@var{prefix}/share}.
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 option only takes effect for native
437 builds; cross compiler binaries' names are not transformed even when a
438 transformation is explicitly asked for by one of these 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 Both the local-prefix include directory and the GCC-prefix include
475 directory are part of GCC's "system include" directories. Although these
476 two directories are not fixed, they need to be searched in the proper
477 order for the correct processing of the include_next directive. The
478 local-prefix include directory is searched before the GCC-prefix
479 include directory. Another characteristic of system include directories
480 is that pedantic warnings are turned off for headers in these directories.
482 Some autoconf macros add @option{-I @var{directory}} options to the
483 compiler command line, to ensure that directories containing installed
484 packages' headers are searched. When @var{directory} is one of GCC's
485 system include directories, GCC will ignore the option so that system
486 directories continue to be processed in the correct order. This
487 may result in a search order different from what was specified but the
488 directory will still be searched.
490 GCC automatically searches for ordinary libraries using
491 @env{GCC_EXEC_PREFIX}. Thus, when the same installation prefix is
492 used for both GCC and packages, GCC will automatically search for
493 both headers and libraries. This provides a configuration that is
494 easy to use. GCC behaves in a manner similar to that when it is
495 installed as a system compiler in @file{/usr}.
497 Sites that need to install multiple versions of GCC may not want to
498 use the above simple configuration. It is possible to use the
499 @option{--program-prefix}, @option{--program-suffix} and
500 @option{--program-transform-name} options to install multiple versions
501 into a single directory, but it may be simpler to use different prefixes
502 and the @option{--with-local-prefix} option to specify the location of the
503 site-specific files for each version. It will then be necessary for
504 users to specify explicitly the location of local site libraries
505 (e.g., with @env{LIBRARY_PATH}).
507 The same value can be used for both @option{--with-local-prefix} and
508 @option{--prefix} provided it is not @file{/usr}. This can be used
509 to avoid the default search of @file{/usr/local/include}.
511 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
512 The directory you use for @option{--with-local-prefix} @strong{must not}
513 contain any of the system's standard header files. If it did contain
514 them, certain programs would be miscompiled (including GNU Emacs, on
515 certain targets), because this would override and nullify the header
516 file corrections made by the @command{fixincludes} script.
518 Indications are that people who use this option use it based on mistaken
519 ideas of what it is for. People use it as if it specified where to
520 install part of GCC@. Perhaps they make this assumption because
521 installing GCC creates the directory.
523 @item --enable-shared[=@var{package}[,@dots{}]]
524 Build shared versions of libraries, if shared libraries are supported on
525 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
526 are enabled by default on all platforms that support shared libraries,
527 except for @samp{libobjc} which is built as a static library only by
530 If a list of packages is given as an argument, build shared libraries
531 only for the listed packages. For other packages, only static libraries
532 will be built. Package names currently recognized in the GCC tree are
533 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
534 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc} and
535 @samp{libjava}. Note that @samp{libobjc} does not recognize itself by
536 any name, so, if you list package names in @option{--enable-shared},
537 you will only get static Objective-C libraries. @samp{libf2c} and
538 @samp{libiberty} do not support shared libraries at all.
540 Use @option{--disable-shared} to build only static libraries. Note that
541 @option{--disable-shared} does not accept a list of package names as
542 argument, only @option{--enable-shared} does.
544 @item @anchor{with-gnu-as}--with-gnu-as
545 Specify that the compiler should assume that the
546 assembler it finds is the GNU assembler. However, this does not modify
547 the rules to find an assembler and will result in confusion if the
548 assembler found is not actually the GNU assembler. (Confusion may also
549 result if the compiler finds the GNU assembler but has not been
550 configured with @option{--with-gnu-as}.) If you have more than one
551 assembler installed on your system, you may want to use this option in
552 connection with @option{--with-as=@var{pathname}}.
554 The following systems are the only ones where it makes a difference
555 whether you use the GNU assembler. On any other system,
556 @option{--with-gnu-as} has no effect.
559 @item @samp{hppa1.0-@var{any}-@var{any}}
560 @item @samp{hppa1.1-@var{any}-@var{any}}
561 @item @samp{i386-@var{any}-sysv}
562 @item @samp{m68k-bull-sysv}
563 @item @samp{m68k-hp-hpux}
564 @item @samp{m68000-hp-hpux}
565 @item @samp{m68000-att-sysv}
566 @item @samp{@var{any}-lynx-lynxos}
567 @item @samp{mips-@var{any}}
570 On the systems listed above (except for the HP-PA, for ISC on the
571 386, and for @samp{mips-sgi-irix5.*}), if you use the GNU assembler,
572 you should also use the GNU linker (and specify @option{--with-gnu-ld}).
574 @item --with-as=@var{pathname}
576 compiler should use the assembler pointed to by @var{pathname}, rather
577 than the one found by the standard rules to find an assembler, which
582 @file{@var{exec_prefix}/lib/gcc-lib/@var{target}/@var{version}}
583 directory, where @var{exec_prefix} defaults to @var{prefix} which
584 defaults to @file{/usr/local} unless overridden by the
585 @option{--prefix=@var{pathname}} switch described above. @var{target} is the
586 target system triple, such as @samp{sparc-sun-solaris2.7}, and
587 @var{version} denotes the GCC version, such as 3.0.
589 Check operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
592 Note that these rules do not check for the value of @env{PATH}. You may
593 want to use @option{--with-as} if no assembler is installed in the
594 directories listed above, or if you have multiple assemblers installed
595 and want to choose one that is not found by the above rules.
597 @item @anchor{with-gnu-ld}--with-gnu-ld
598 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
602 @item --with-ld=@var{pathname}
604 @option{--with-as}, but for the linker.
607 Specify that stabs debugging
608 information should be used instead of whatever format the host normally
609 uses. Normally GCC uses the same debug format as the host system.
611 On MIPS based systems and on Alphas, you must specify whether you want
612 GCC to create the normal ECOFF debugging format, or to use BSD-style
613 stabs passed through the ECOFF symbol table. The normal ECOFF debug
614 format cannot fully handle languages other than C@. BSD stabs format can
615 handle other languages, but it only works with the GNU debugger GDB@.
617 Normally, GCC uses the ECOFF debugging format by default; if you
618 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
620 No matter which default you choose when you configure GCC, the user
621 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
622 the debug format for a particular compilation.
624 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
625 @option{--with-gas} is used. It selects use of stabs debugging
626 information embedded in COFF output. This kind of debugging information
627 supports C++ well; ordinary COFF debugging information does not.
629 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
630 selects use of stabs debugging information embedded in ELF output. The
631 C++ compiler currently (2.6.0) does not support the DWARF debugging
632 information normally used on 386 SVR4 platforms; stabs provide a
633 workable alternative. This requires gas and gdb, as the normal SVR4
634 tools can not generate or interpret stabs.
636 @item --disable-multilib
637 Specify that multiple target
638 libraries to support different target variants, calling
639 conventions, etc should not be built. The default is to build a
640 predefined set of them.
642 Some targets provide finer-grained control over which multilibs are built
643 (e.g., @option{--disable-softfloat}):
649 fpu, 26bit, underscore, interwork, biendian, nofmult.
652 softfloat, m68881, m68000, m68020.
655 single-float, biendian, softfloat.
657 @item powerpc*-*-*, rs6000*-*-*
658 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
663 @item --enable-threads
664 Specify that the target
665 supports threads. This affects the Objective-C compiler and runtime
666 library, and exception handling for other languages like C++ and Java.
667 On some systems, this is the default.
669 In general, the best (and, in many cases, the only known) threading
670 model available will be configured for use. Beware that on some
671 systems, gcc has not been taught what threading models are generally
672 available for the system. In this case, @option{--enable-threads} is an
673 alias for @option{--enable-threads=single}.
675 @item --disable-threads
676 Specify that threading support should be disabled for the system.
677 This is an alias for @option{--enable-threads=single}.
679 @item --enable-threads=@var{lib}
681 @var{lib} is the thread support library. This affects the Objective-C
682 compiler and runtime library, and exception handling for other languages
683 like C++ and Java. The possibilities for @var{lib} are:
691 Generic MACH thread support, known to work on NeXTSTEP@. (Please note
692 that the file needed to support this configuration, @file{gthr-mach.h}, is
693 missing and thus this setting will cause a known bootstrap failure.)
695 This is an alias for @samp{single}.
697 Generic POSIX thread support.
699 Same as @samp{posix} on arm*-*-linux*, *-*-chorusos* and *-*-freebsd*
700 only. A future release of gcc might remove this alias or extend it
703 RTEMS thread support.
705 Disable thread support, should work for all platforms.
707 Sun Solaris 2 thread support.
709 VxWorks thread support.
711 Microsoft Win32 API thread support.
714 @item --with-cpu=@var{cpu}
715 Specify which cpu variant the
716 compiler should generate code for by default. This is currently
717 only supported on some ports, specifically arm, powerpc, and
718 SPARC@. If configure does not recognize the model name (e.g.@: arm700,
719 603e, or ultrasparc) you provide, please check the configure script
720 for a complete list of supported models.
722 @item --enable-altivec
723 Specify that the target supports AltiVec vector enhancements. This
724 option will adjust the ABI for AltiVec enhancements, as well as generate
725 AltiVec code when appropriate. This option is only available for
728 @item --enable-target-optspace
730 libraries should be optimized for code space instead of code speed.
731 This is the default for the m32r platform.
734 Specify that a user visible @command{cpp} program should not be installed.
736 @item --with-cpp-install-dir=@var{dirname}
737 Specify that the user visible @command{cpp} program should be installed
738 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
740 @item --enable-initfini-array
741 Force the use of sections @code{.init_array} and @code{.fini_array}
742 (instead of @code{.init} and @code{.fini}) for constructors and
743 destructors. Option @option{--disable-initfini-array} has the
744 opposite effect. If neither option is specified, the configure script
745 will try to guess whether the @code{.init_array} and
746 @code{.fini_array} sections are supported and, if they are, use them.
748 @item --enable-maintainer-mode
750 regenerate the GCC master message catalog @file{gcc.pot} are normally
751 disabled. This is because it can only be rebuilt if the complete source
752 tree is present. If you have changed the sources and want to rebuild the
753 catalog, configuring with @option{--enable-maintainer-mode} will enable
754 this. Note that you need a recent version of the @code{gettext} tools
757 @item --enable-version-specific-runtime-libs
759 that runtime libraries should be installed in the compiler specific
760 subdirectory (@file{@var{libsubdir}}) rather than the usual places. In
761 addition, @samp{libstdc++}'s include files will be installed in
762 @file{@var{libsubdir}/include/g++} unless you overruled it by using
763 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
764 particularly useful if you intend to use several versions of GCC in
765 parallel. This is currently supported by @samp{libf2c} and
766 @samp{libstdc++}, and is the default for @samp{libobjc} which cannot be
767 changed in this case.
769 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
770 Specify that only a particular subset of compilers and
771 their runtime libraries should be built. For a list of valid values for
772 @var{langN} you can issue the following command in the
773 @file{gcc} directory of your GCC source tree:@*
775 grep language= */config-lang.in
777 Currently, you can use any of the following:
778 @code{ada}, @code{c}, @code{c++}, @code{f77}, @code{java}, @code{objc}.
779 Building the Ada compiler has special requirements, see below.@*
780 If you do not pass this flag, all languages available in the @file{gcc}
781 sub-tree will be configured. Re-defining @code{LANGUAGES} when calling
782 @samp{make bootstrap} @strong{does not} work anymore, as those
783 language sub-directories might not have been configured!
785 @item --disable-libgcj
786 Specify that the run-time libraries
787 used by GCJ should not be built. This is useful in case you intend
788 to use GCJ with some other run-time, or you're going to install it
789 separately, or it just happens not to build on your particular
790 machine. In general, if the Java front end is enabled, the GCJ
791 libraries will be enabled too, unless they're known to not work on
792 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
793 may need to port it; in this case, before modifying the top-level
794 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
795 you may use @option{--enable-libgcj} to override the default.
798 Specify that the compiler should
799 use DWARF 2 debugging information as the default.
801 @item --enable-win32-registry
802 @itemx --enable-win32-registry=@var{key}
803 @itemx --disable-win32-registry
804 The @option{--enable-win32-registry} option enables Windows-hosted GCC
805 to look up installations paths in the registry using the following key:
808 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
811 @var{key} defaults to GCC version number, and can be overridden by the
812 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
813 who use custom installers are encouraged to provide a different key,
814 perhaps one comprised of vendor name and GCC version number, to
815 avoid conflict with existing installations. This feature is enabled
816 by default, and can be disabled by @option{--disable-win32-registry}
817 option. This option has no effect on the other hosts.
820 Specify that the machine does not have a floating point unit. This
821 option only applies to @samp{m68k-sun-sunos@var{n}}. On any other
822 system, @option{--nfp} has no effect.
824 @item --enable-checking
825 @itemx --enable-checking=@var{list}
826 When you specify this option, the compiler is built to perform checking
827 of tree node types when referencing fields of that node, and some other
828 internal consistency checks. This does not change the generated code,
829 but adds error checking within the compiler. This will slow down the
830 compiler and may only work properly if you are building the compiler
831 with GCC@. This is on by default when building from CVS or snapshots,
832 but off for releases. More control over the checks may be had by
833 specifying @var{list}; the categories of checks available are
834 @samp{misc}, @samp{tree}, @samp{gc}, @samp{rtl}, @samp{rtlflag} and
836 default when @var{list} is not specified is @samp{misc,tree,gc,rtlflag}; the
837 checks @samp{rtl} and @samp{gcac} are very expensive.
839 @item --enable-coverage
840 @item --enable-coverage=@var{level}
841 With this option, the compiler is built to collect self coverage
842 information, every time it is run. This is for internal development
843 purposes, and only works when the compiler is being built with gcc. The
844 @var{level} argument controls whether the compiler is built optimized or
845 not, values are @samp{opt} and @samp{noopt}. For coverage analysis you
846 want to disable optimization, for performance analysis you want to
847 enable optimization. When coverage is enabled, the default level is
848 without optimization.
852 The @option{--enable-nls} option enables Native Language Support (NLS),
853 which lets GCC output diagnostics in languages other than American
854 English. Native Language Support is enabled by default if not doing a
855 canadian cross build. The @option{--disable-nls} option disables NLS@.
857 @item --with-included-gettext
858 If NLS is enabled, the @option{--with-included-gettext} option causes the build
859 procedure to prefer its copy of GNU @command{gettext}.
862 If NLS is enabled, and if the host lacks @code{gettext} but has the
863 inferior @code{catgets} interface, the GCC build procedure normally
864 ignores @code{catgets} and instead uses GCC's copy of the GNU
865 @code{gettext} library. The @option{--with-catgets} option causes the
866 build procedure to use the host's @code{catgets} in this situation.
868 @item --with-libiconv-prefix=@var{dir}
869 Search for libiconv header files in @file{@var{dir}/include} and
870 libiconv library files in @file{@var{dir}/lib}.
872 @item --with-system-zlib
873 Use installed zlib rather than that included with GCC@. This option
874 only applies if the Java front end is being built.
876 @item --enable-obsolete
877 Enable configuration for an obsoleted system. If you attempt to
878 configure GCC for a system (build, host, or target) which has been
879 obsoleted, and you do not specify this flag, configure will halt with an
882 All support for systems which have been obsoleted in one release of GCC
883 is removed entirely in the next major release, unless someone steps
884 forward to maintain the port.
887 Some options which only apply to building cross compilers:
890 @itemx --with-sysroot=@var{dir}
891 Tells GCC to consider @var{dir} as the root of a tree that contains a
892 (subset of) the root filesystem of the target operating system.
893 Target system headers, libraries and run-time object files will be
894 searched in there. The specified directory is not copied into the
895 install tree, unlike the options @option{--with-headers} and
896 @option{--with-libs} that this option obsoletes. The default value,
897 in case @option{--with-sysroot} is not given an argument, is
898 @option{$@{gcc_tooldir@}/sys-root}. Starting the pathname with
899 @option{$@{gcc_tooldir@}/}, in such a way that this variable is not
900 expanded by the shell, but rather by the gcc Makefile, enables the
901 target sysroot directory to be relocatable along with the entire
902 install tree, but it will require the gcc tool directory to be created
903 @emph{before} the build is started. This directory, as well as its
904 intermediate pathnames, can be easily created by running @command{make
905 install-gcc-tooldir} the gcc build directory. This is not done
906 automatically to avoid touching the install tree without explicit
910 @itemx --with-headers=@var{dir}
911 Deprecated in favor of @option{--with-sysroot}.
912 Specifies that target headers are available when building a cross compiler.
913 The @var{dir} argument specifies a directory which has the target include
914 files. These include files will be copied into the @file{gcc} install
915 directory. @emph{This option with the @var{dir} argument is required} when
916 building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include}
917 doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does
918 pre-exist, the @var{dir} argument may be omitted. @command{fixincludes}
919 will be run on these files to make them compatible with GCC.
921 @itemx --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
922 Deprecated in favor of @option{--with-sysroot}.
923 Specifies a list of directories which contain the target runtime
924 libraries. These libraries will be copied into the @file{gcc} install
925 directory. If the directory list is omitted, this option has no
928 Specifies that @samp{newlib} is
929 being used as the target C library. This causes @code{__eprintf} to be
930 omitted from @file{libgcc.a} on the assumption that it will be provided by
934 Note that each @option{--enable} option has a corresponding
935 @option{--disable} option and that each @option{--with} option has a
936 corresponding @option{--without} option.
943 @uref{./index.html,,Return to the GCC Installation page}
947 @c ***Building****************************************************************
949 @comment node-name, next, previous, up
950 @node Building, Testing, Configuration, Installing GCC
956 @cindex Installing GCC: Building
958 Now that GCC is configured, you are ready to build the compiler and
961 We @strong{highly} recommend that GCC be built using GNU make;
962 other versions may work, then again they might not.
963 GNU make is required for compiling GNAT (the Ada compiler) and the Java
966 (For example, many broken versions of make will fail if you use the
967 recommended setup where @var{objdir} is different from @var{srcdir}.
968 Other broken versions may recompile parts of the compiler when
969 installing the compiler.)
971 Some commands executed when making the compiler may fail (return a
972 nonzero status) and be ignored by @code{make}. These failures, which
973 are often due to files that were not found, are expected, and can safely
976 It is normal to have compiler warnings when compiling certain files.
977 Unless you are a GCC developer, you can generally ignore these warnings
978 unless they cause compilation to fail.
980 On certain old systems, defining certain environment variables such as
981 @env{CC} can interfere with the functioning of @command{make}.
983 If you encounter seemingly strange errors when trying to build the
984 compiler in a directory other than the source directory, it could be
985 because you have previously configured the compiler in the source
986 directory. Make sure you have done all the necessary preparations.
988 If you build GCC on a BSD system using a directory stored in an old System
989 V file system, problems may occur in running @command{fixincludes} if the
990 System V file system doesn't support symbolic links. These problems
991 result in a failure to fix the declaration of @code{size_t} in
992 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
993 that type mismatches occur, this could be the cause.
995 The solution is not to use such a directory for building GCC@.
997 When building from CVS or snapshots, or if you modify parser sources,
998 you need the Bison parser generator installed. Any version 1.25 or
999 later should work; older versions may also work. If you do not modify
1000 parser sources, releases contain the Bison-generated files and you do
1001 not need Bison installed to build them.
1003 When building from CVS or snapshots, or if you modify Texinfo
1004 documentation, you need version 4.1 or later of Texinfo installed if you
1005 want Info documentation to be regenerated. Releases contain Info
1006 documentation pre-built for the unmodified documentation in the release.
1008 @section Building a native compiler
1010 For a native build issue the command @samp{make bootstrap}. This
1011 will build the entire GCC system, which includes the following steps:
1015 Build host tools necessary to build the compiler such as texinfo, bison,
1019 Build target tools for use by the compiler such as binutils (bfd,
1020 binutils, gas, gprof, ld, and opcodes)
1021 if they have been individually linked
1022 or moved into the top level GCC source tree before configuring.
1025 Perform a 3-stage bootstrap of the compiler.
1028 Perform a comparison test of the stage2 and stage3 compilers.
1031 Build runtime libraries using the stage3 compiler from the previous step.
1035 If you are short on disk space you might consider @samp{make
1036 bootstrap-lean} instead. This is identical to @samp{make
1037 bootstrap} except that object files from the stage1 and
1038 stage2 of the 3-stage bootstrap of the compiler are deleted as
1039 soon as they are no longer needed.
1041 If you want to save additional space during the bootstrap and in
1042 the final installation as well, you can build the compiler binaries
1043 without debugging information as in the following example. This will save
1044 roughly 40% of disk space both for the bootstrap and the final installation.
1045 (Libraries will still contain debugging information.)
1048 make CFLAGS='-O' LIBCFLAGS='-g -O2' \
1049 LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap
1052 If you wish to use non-default GCC flags when compiling the stage2 and
1053 stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing
1054 @samp{make bootstrap}. Non-default optimization flags are less well
1055 tested here than the default of @samp{-g -O2}, but should still work.
1056 In a few cases, you may find that you need to specify special flags such
1057 as @option{-msoft-float} here to complete the bootstrap; or, if the
1058 native compiler miscompiles the stage1 compiler, you may need to work
1059 around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the
1060 stage1 compiler that were miscompiled, or by using @samp{make
1061 bootstrap4} to increase the number of stages of bootstrap.
1063 If you used the flag @option{--enable-languages=@dots{}} to restrict
1064 the compilers to be built, only those you've actually enabled will be
1065 built. This will of course only build those runtime libraries, for
1066 which the particular compiler has been built. Please note,
1067 that re-defining @env{LANGUAGES} when calling @samp{make bootstrap}
1068 @strong{does not} work anymore!
1070 If the comparison of stage2 and stage3 fails, this normally indicates
1071 that the stage2 compiler has compiled GCC incorrectly, and is therefore
1072 a potentially serious bug which you should investigate and report. (On
1073 a few systems, meaningful comparison of object files is impossible; they
1074 always appear ``different''. If you encounter this problem, you will
1075 need to disable comparison in the @file{Makefile}.)
1077 @section Building a cross compiler
1079 We recommend reading the
1080 @uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ}
1081 for information about building cross compilers.
1083 When building a cross compiler, it is not generally possible to do a
1084 3-stage bootstrap of the compiler. This makes for an interesting problem
1085 as parts of GCC can only be built with GCC@.
1087 To build a cross compiler, we first recommend building and installing a
1088 native compiler. You can then use the native GCC compiler to build the
1089 cross compiler. The installed native compiler needs to be GCC version
1092 Assuming you have already installed a native copy of GCC and configured
1093 your cross compiler, issue the command @command{make}, which performs the
1098 Build host tools necessary to build the compiler such as texinfo, bison,
1102 Build target tools for use by the compiler such as binutils (bfd,
1103 binutils, gas, gprof, ld, and opcodes)
1104 if they have been individually linked or moved into the top level GCC source
1105 tree before configuring.
1108 Build the compiler (single stage only).
1111 Build runtime libraries using the compiler from the previous step.
1114 Note that if an error occurs in any step the make process will exit.
1116 @section Building in parallel
1118 If you have a multiprocessor system you can use @samp{make bootstrap
1119 MAKE="make -j 2" -j 2} or just @samp{make -j 2 bootstrap}
1120 for GNU Make 3.79 and above instead of just @samp{make bootstrap}
1121 when building GCC@. You can use a bigger number instead of two if
1122 you like. In most cases, it won't help to use a number bigger than
1123 the number of processors in your machine.
1125 @section Building the Ada compiler
1127 In order to build GNAT, the Ada compiler, you need a working GNAT
1128 compiler (GNAT version 3.13 or later, or GCC version 3.1 or later),
1129 since the Ada front end is written in Ada (with some
1130 GNAT-specific extensions), and GNU make.
1132 However, you do not need a full installation of GNAT, just the GNAT
1133 binary @file{gnat1}, a copy of @file{gnatbind}, and a compiler driver
1134 which can deal with Ada input (by invoking the @file{gnat1} binary).
1135 You can specify this compiler driver by setting the @env{ADAC}
1136 environment variable at the configure step. @command{configure} can
1137 detect the driver automatically if it has got a common name such as
1138 @command{gcc} or @command{gnatgcc}. Of course, you still need a working
1139 C compiler (the compiler driver can be different or not).
1140 @command{configure} does not test whether the GNAT installation works
1141 and has a sufficiently recent version; if too old a GNAT version is
1142 installed, the build will fail unless @option{--enable-languages} is
1143 used to disable building the Ada front end.
1145 Additional build tools (such as @command{gnatmake}) or a working GNAT
1146 run-time library installation are usually @emph{not} required. However,
1147 if you want to bootstrap the compiler using a minimal version of GNAT,
1148 you have to issue the following commands before invoking @samp{make
1149 bootstrap} (this assumes that you start with an unmodified and consistent
1150 source distribution):
1153 cd @var{srcdir}/gcc/ada
1154 touch treeprs.ads [es]info.h nmake.ad[bs]
1157 At the moment, the GNAT library and several tools for GNAT are not built
1158 by @samp{make bootstrap}. You have to invoke
1159 @samp{make gnatlib_and_tools} in the @file{@var{objdir}/gcc}
1160 subdirectory before proceeding with the next steps.
1162 For example, you can build a native Ada compiler by issuing the
1163 following commands (assuming @command{make} is GNU make):
1167 @var{srcdir}/configure --enable-languages=c,ada
1168 cd @var{srcdir}/gcc/ada
1169 touch treeprs.ads [es]info.h nmake.ad[bs]
1173 make gnatlib_and_tools
1177 Currently, when compiling the Ada front end, you cannot use the parallel
1178 build feature described in the previous section.
1185 @uref{./index.html,,Return to the GCC Installation page}
1189 @c ***Testing*****************************************************************
1191 @comment node-name, next, previous, up
1192 @node Testing, Final install, Building, Installing GCC
1196 @chapter Installing GCC: Testing
1199 @cindex Installing GCC: Testing
1202 Before you install GCC, we encourage you to run the testsuites and to
1203 compare your results with results from a similar configuration that have
1204 been submitted to the
1205 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
1206 This step is optional and may require you to download additional software,
1207 but it can give you confidence in your new GCC installation or point out
1208 problems before you install and start using your new GCC.
1210 First, you must have @uref{download.html,,downloaded the testsuites}.
1211 These are part of the full distribution, but if you downloaded the
1212 ``core'' compiler plus any front ends, you must download the testsuites
1215 Second, you must have the testing tools installed. This includes
1216 a @uref{http://www.gnu.org/software/dejagnu/,,current version of DejaGnu};
1217 dejagnu 1.3 is not sufficient.
1218 It also includes Tcl and Expect; the DejaGnu site has links to these.
1220 Now you may need specific preparations:
1225 The following environment variables may need to be set appropriately, as in
1226 the following example (which assumes that DejaGnu has been installed
1227 under @file{/usr/local}):
1230 TCL_LIBRARY = /usr/local/share/tcl8.0
1231 DEJAGNULIBS = /usr/local/share/dejagnu
1234 On systems such as Cygwin, these paths are required to be actual
1235 paths, not mounts or links; presumably this is due to some lack of
1236 portability in the DejaGnu code.
1238 If the directories where @command{runtest} and @command{expect} were
1239 installed are in the @env{PATH}, it should not be necessary to set these
1240 environment variables.
1244 Finally, you can run the testsuite (which may take a long time):
1246 cd @var{objdir}; make -k check
1249 The testing process will try to test as many components in the GCC
1250 distribution as possible, including the C, C++, Objective-C and Fortran
1251 compilers as well as the C++ and Java runtime libraries.
1253 While running the testsuite, DejaGnu might emit messages resembling
1254 @samp{WARNING: Couldn't find the global config file.} or
1255 @samp{WARNING: Couldn't find tool init file}.
1256 These messages are harmless and do not affect the validity of the tests.
1258 @section How can I run the test suite on selected tests?
1260 As a first possibility to cut down the number of tests that are run it is
1261 possible to use @samp{make check-gcc} or @samp{make check-g++}
1262 in the @file{gcc} subdirectory of the object directory. To further cut down the
1263 tests the following is possible:
1266 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
1269 This will run all @command{gcc} execute tests in the testsuite.
1272 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
1275 This will run the @command{g++} ``old-deja'' tests in the testsuite where the filename
1276 matches @samp{9805*}.
1278 The @file{*.exp} files are located in the testsuite directories of the GCC
1279 source, the most important ones being @file{compile.exp},
1280 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
1281 To get a list of the possible @file{*.exp} files, pipe the
1282 output of @samp{make check} into a file and look at the
1283 @samp{Running @dots{} .exp} lines.
1285 To run only the tests for a library, run @samp{make check} from the
1286 the library's testsuite in a subdirectory of the object directory:
1287 @file{libstdc++-v3/testsuite} or @file{libcgj/testsuite}.
1289 @section Additional testing for Java Class Libraries
1291 The @uref{http://sources.redhat.com/mauve/,,Mauve Project} provides
1292 a suite of tests for the Java Class Libraries. This suite can be run
1293 as part of libgcj testing by placing the Mauve tree within the libjava
1294 testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by
1295 specifying the location of that tree when invoking @samp{make}, as in
1296 @samp{make MAUVEDIR=~/mauve check}.
1298 @section How to interpret test results
1300 After the testsuite has run you'll find various @file{*.sum} and @file{*.log}
1301 files in the testsuite subdirectories. The @file{*.log} files contain a
1302 detailed log of the compiler invocations and the corresponding
1303 results, the @file{*.sum} files summarize the results. These summaries list
1304 all the tests that have been run with a corresponding status code:
1308 PASS: the test passed as expected
1310 XPASS: the test unexpectedly passed
1312 FAIL: the test unexpectedly failed
1314 XFAIL: the test failed as expected
1316 UNSUPPORTED: the test is not supported on this platform
1318 ERROR: the testsuite detected an error
1320 WARNING: the testsuite detected a possible problem
1323 It is normal for some tests to report unexpected failures. At the
1324 current time our testing harness does not allow fine grained control
1325 over whether or not a test is expected to fail. We expect to fix this
1326 problem in future releases.
1329 @section Submitting test results
1331 If you want to report the results to the GCC project, use the
1332 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
1335 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
1336 -m gcc-testresults@@gcc.gnu.org |sh
1339 This script uses the @command{Mail} program to send the results, so
1340 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
1341 prepended to the testsuite summary and should contain any special
1342 remarks you have on your results or your build environment. Please
1343 do not edit the testsuite result block or the subject line, as these
1344 messages are automatically parsed and presented at the
1345 @uref{http://gcc.gnu.org/testresults/,,GCC testresults} web
1346 page. Here you can also gather information on how specific tests
1347 behave on different platforms and compare them with your results. A
1348 few failing testcases are possible even on released versions and you
1349 should look here first if you think your results are unreasonable.
1356 @uref{./index.html,,Return to the GCC Installation page}
1360 @c ***Final install***********************************************************
1362 @comment node-name, next, previous, up
1363 @node Final install, , Testing, Installing GCC
1365 @ifset finalinstallhtml
1367 @chapter Installing GCC: Final installation
1370 Now that GCC has been built (and optionally tested), you can install it with
1372 cd @var{objdir}; make install
1375 We strongly recommend to install into a target directory where there is
1376 no previous version of GCC present.
1378 That step completes the installation of GCC; user level binaries can
1379 be found in @file{@var{prefix}/bin} where @var{prefix} is the value you
1380 specified with the @option{--prefix} to configure (or @file{/usr/local}
1381 by default). (If you specified @option{--bindir}, that directory will
1382 be used instead; otherwise, if you specified @option{--exec-prefix},
1383 @file{@var{exec-prefix}/bin} will be used.) Headers for the C++ and
1384 Java libraries are installed in @file{@var{prefix}/include}; libraries
1385 in @file{@var{libdir}} (normally @file{@var{prefix}/lib}); internal
1386 parts of the compiler in @file{@var{libdir}/gcc-lib}; documentation in
1387 info format in @file{@var{infodir}} (normally @file{@var{prefix}/info}).
1389 If you built a released version of GCC using @samp{make bootstrap} then please
1390 quickly review the build status page for your release, available from
1391 @uref{http://gcc.gnu.org/buildstat.html}.
1392 If your system is not listed for the version of GCC that you built,
1394 @email{gcc@@gcc.gnu.org} indicating
1395 that you successfully built and installed GCC.
1396 Include the following information:
1400 Output from running @file{@var{srcdir}/config.guess}. Do not send us
1401 that file itself, just the one-line output from running it.
1404 The output of @samp{gcc -v} for your newly installed gcc.
1405 This tells us which version of GCC you built and the options you passed to
1409 Whether you enabled all languages or a subset of them. If you used a
1410 full distribution then this information is part of the configure
1411 options in the output of @samp{gcc -v}, but if you downloaded the
1412 ``core'' compiler plus additional front ends then it isn't apparent
1413 which ones you built unless you tell us about it.
1416 If the build was for GNU/Linux, also include:
1419 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
1420 this information should be available from @file{/etc/issue}.
1423 The version of the Linux kernel, available from @samp{uname --version}
1427 The version of glibc you used; for RPM-based systems like Red Hat,
1428 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
1429 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
1431 For other systems, you can include similar information if you think it is
1435 Any other information that you think would be useful to people building
1436 GCC on the same configuration. The new entry in the build status list
1437 will include a link to the archived copy of your message.
1440 We'd also like to know if the
1442 @ref{Specific, host/target specific installation notes}
1445 @uref{specific.html,,host/target specific installation notes}
1447 didn't include your host/target information or if that information is
1448 incomplete or out of date. Send a note to
1449 @email{gcc@@gcc.gnu.org} telling us how the information should be changed.
1451 If you find a bug, please report it following our
1452 @uref{../bugs.html,,bug reporting guidelines}.
1454 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
1455 dvi}. You will need to have @command{texi2dvi} (version at least 4.1)
1456 and @TeX{} installed. This creates a number of @file{.dvi} files in
1457 subdirectories of @file{@var{objdir}}; these may be converted for
1458 printing with programs such as @command{dvips}. You can also
1459 @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the
1460 Free Software Foundation}, though such manuals may not be for the most
1461 recent version of GCC@.
1468 @uref{./index.html,,Return to the GCC Installation page}
1472 @c ***Binaries****************************************************************
1474 @comment node-name, next, previous, up
1475 @node Binaries, Specific, Installing GCC, Top
1479 @chapter Installing GCC: Binaries
1482 @cindex Installing GCC: Binaries
1484 We are often asked about pre-compiled versions of GCC@. While we cannot
1485 provide these for all platforms, below you'll find links to binaries for
1486 various platforms where creating them by yourself is not easy due to various
1489 Please note that we did not create these binaries, nor do we
1490 support them. If you have any problems installing them, please
1491 contact their makers.
1498 @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX};
1501 @uref{http://aixpdslib.seas.ucla.edu,,UCLA Software Library for AIX}.
1505 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}.
1508 Hitachi H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
1509 Development Tools for the Hitachi H8/300[HS] Series}.
1515 @uref{http://hpux.cae.wisc.edu/,,HP-UX Porting Center};
1518 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
1522 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
1523 OpenServer/Unixware}.
1526 Sinix/Reliant Unix---@uref{ftp://ftp.siemens.de/sni/mr/pd/gnu/gcc,,Siemens}.
1529 Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware}.
1532 SGI---@uref{http://freeware.sgi.com/,,SGI Freeware}.
1535 Windows 95, 98, and NT:
1538 The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project;
1540 The @uref{http://www.mingw.org/,,MinGW} project.
1544 @uref{ftp://ftp.thewrittenword.com/packages/free/by-name/,,The
1545 Written Word} offers binaries for Solaris 2.5.1, 2.6, 2.7/SPARC, 2.7/Intel,
1546 IRIX 6.2, 6.5, Digital UNIX 4.0D, HP-UX 10.20, and HP-UX 11.00.
1550 In addition to those specific offerings, you can get a binary
1551 distribution CD-ROM from the
1552 @uref{http://www.fsf.org/order/order.html,,Free Software Foundation}.
1553 It contains binaries for a number of platforms, and
1554 includes not only GCC, but other stuff as well. The current CD does
1555 not contain the latest version of GCC, but it should allow
1556 bootstrapping the compiler. An updated version of that disk is in the
1564 @uref{./index.html,,Return to the GCC Installation page}
1568 @c ***Specific****************************************************************
1570 @comment node-name, next, previous, up
1571 @node Specific, Old, Binaries, Top
1575 @chapter Host/target specific installation notes for GCC
1578 @cindex Specific installation notes
1579 @cindex Target specific installation
1580 @cindex Host specific installation
1581 @cindex Target specific installation notes
1583 Please read this document carefully @emph{before} installing the
1584 GNU Compiler Collection on your machine.
1589 @uref{#alpha*-*-*,,alpha*-*-*}
1591 @uref{#alpha*-dec-osf*,,alpha*-dec-osf*}
1593 @uref{#alphaev5-cray-unicosmk*,,alphaev5-cray-unicosmk*}
1595 @uref{#arc-*-elf,,arc-*-elf}
1597 @uref{#arm-*-aout,,arm-*-aout}
1599 @uref{#arm-*-elf,,arm-*-elf}
1601 @uref{#arm*-*-linux-gnu,,arm*-*-linux-gnu}
1609 @uref{#dsp16xx,,dsp16xx}
1611 @uref{#*-*-freebsd*,,*-*-freebsd*}
1613 @uref{#h8300-hms,,h8300-hms}
1615 @uref{#hppa*-hp-hpux*,,hppa*-hp-hpux*}
1617 @uref{#hppa*-hp-hpux9,,hppa*-hp-hpux9}
1619 @uref{#hppa*-hp-hpux10,,hppa*-hp-hpux10}
1621 @uref{#hppa*-hp-hpux11,,hppa*-hp-hpux11}
1623 @uref{#i370-*-*,,i370-*-*}
1625 @uref{#*-*-linux-gnu,,*-*-linux-gnu}
1627 @uref{#ix86-*-linux*aout,,i?86-*-linux*aout}
1629 @uref{#ix86-*-linux*,,i?86-*-linux*}
1631 @uref{#ix86-*-sco,,i?86-*-sco}
1633 @uref{#ix86-*-sco3.2v4,,i?86-*-sco3.2v4}
1635 @uref{#ix86-*-sco3.2v5*,,i?86-*-sco3.2v5*}
1637 @uref{#ix86-*-udk,,i?86-*-udk}
1639 @uref{#ix86-*-esix,,i?86-*-esix}
1641 @uref{#ia64-*-linux,,ia64-*-linux}
1643 @uref{#*-lynx-lynxos,,*-lynx-lynxos}
1645 @uref{#*-ibm-aix*,,*-ibm-aix*}
1647 @uref{#ip2k-*-elf,,ip2k-*-elf}
1649 @uref{#m32r-*-elf,,m32r-*-elf}
1651 @uref{#m68000-hp-bsd,,m68000-hp-bsd}
1653 @uref{#m6811-elf,,m6811-elf}
1655 @uref{#m6812-elf,,m6812-elf}
1657 @uref{#m68k-att-sysv,,m68k-att-sysv}
1659 @uref{#m68k-crds-unos,,m68k-crds-unos}
1661 @uref{#m68k-hp-hpux,,m68k-hp-hpux}
1663 @uref{#m68k-ncr-*,,m68k-ncr-*}
1665 @uref{#m68k-sun,,m68k-sun}
1667 @uref{#m68k-sun-sunos4.1.1,,m68k-sun-sunos4.1.1}
1669 @uref{#mips-*-*,,mips-*-*}
1671 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
1673 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
1675 @uref{#powerpc*-*-*,,powerpc*-*-*, powerpc-*-sysv4}
1677 @uref{#powerpc-*-darwin*,,powerpc-*-darwin*}
1679 @uref{#powerpc-*-elf,,powerpc-*-elf, powerpc-*-sysv4}
1681 @uref{#powerpc-*-linux-gnu*,,powerpc-*-linux-gnu*}
1683 @uref{#powerpc-*-netbsd*,,powerpc-*-netbsd*}
1685 @uref{#powerpc-*-eabiaix,,powerpc-*-eabiaix}
1687 @uref{#powerpc-*-eabisim,,powerpc-*-eabisim}
1689 @uref{#powerpc-*-eabi,,powerpc-*-eabi}
1691 @uref{#powerpcle-*-elf,,powerpcle-*-elf, powerpcle-*-sysv4}
1693 @uref{#powerpcle-*-eabisim,,powerpcle-*-eabisim}
1695 @uref{#powerpcle-*-eabi,,powerpcle-*-eabi}
1697 @uref{#powerpcle-*-winnt,,powerpcle-*-winnt, powerpcle-*-pe}
1699 @uref{#s390-*-linux*,,s390-*-linux*}
1701 @uref{#s390x-*-linux*,,s390x-*-linux*}
1703 @uref{#*-*-solaris2*,,*-*-solaris2*}
1705 @uref{#sparc-sun-solaris2*,,sparc-sun-solaris2*}
1707 @uref{#sparc-sun-solaris2.7,,sparc-sun-solaris2.7}
1709 @uref{#sparc-sun-sunos4*,,sparc-sun-sunos4*}
1711 @uref{#sparc-unknown-linux-gnulibc1,,sparc-unknown-linux-gnulibc1}
1713 @uref{#sparc-*-linux*,,sparc-*-linux*}
1715 @uref{#sparc64-*-*,,sparc64-*-*}
1717 @uref{#sparcv9-*-solaris2*,,sparcv9-*-solaris2*}
1719 @uref{#*-*-sysv*,,*-*-sysv*}
1721 @uref{#vax-dec-ultrix,,vax-dec-ultrix}
1723 @uref{#*-*-vxworks*,,*-*-vxworks*}
1725 @uref{#xtensa-*-elf,,xtensa-*-elf}
1727 @uref{#xtensa-*-linux*,,xtensa-*-linux*}
1729 @uref{#windows,,Microsoft Windows}
1733 @uref{#older,,Older systems}
1738 @uref{#elf_targets,,all ELF targets} (SVR4, Solaris 2, etc.)
1744 <!-- -------- host/target specific issues start here ---------------- -->
1747 @heading @anchor{alpha*-*-*}alpha*-*-*
1749 This section contains general configuration information for all
1750 alpha-based platforms using ELF (in particular, ignore this section for
1751 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
1752 section, please read all other sections that match your target.
1754 We require binutils 2.11.2 or newer.
1755 Previous binutils releases had a number of problems with DWARF 2
1756 debugging information, not the least of which is incorrect linking of
1762 @heading @anchor{alpha*-dec-osf*}alpha*-dec-osf*
1763 Systems using processors that implement the DEC Alpha architecture and
1764 are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
1765 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
1767 As of GCC 3.2, versions before @code{alpha*-dec-osf4} are no longer
1768 supported. (These are the versions which identify themselves as DEC
1771 In Digital Unix V4.0, virtual memory exhausted bootstrap failures
1772 may be fixed by configuring with @option{--with-gc=simple},
1773 reconfiguring Kernel Virtual Memory and Swap parameters
1774 per the @command{/usr/sbin/sys_check} Tuning Suggestions,
1775 or applying the patch in
1776 @uref{http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html}.
1778 In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
1779 currently (2001-06-13) work with @command{mips-tfile}. As a workaround,
1780 we need to use the old assembler, invoked via the barely documented
1781 @option{-oldas} option. To bootstrap GCC, you either need to use the
1785 % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
1788 or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
1791 % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
1794 As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld}
1795 are supported on Tru64 UNIX, so you must not configure GCC with
1796 @option{--with-gnu-as} or @option{--with-gnu-ld}.
1798 The @option{--enable-threads} options isn't supported yet. A patch is
1799 in preparation for a future release.
1801 GCC writes a @samp{.verstamp} directive to the assembler output file
1802 unless it is built as a cross-compiler. It gets the version to use from
1803 the system header file @file{/usr/include/stamp.h}. If you install a
1804 new version of DEC Unix, you should rebuild GCC to pick up the new version
1807 Note that since the Alpha is a 64-bit architecture, cross-compilers from
1808 32-bit machines will not generate code as efficient as that generated
1809 when the compiler is running on a 64-bit machine because many
1810 optimizations that depend on being able to represent a word on the
1811 target in an integral value on the host cannot be performed. Building
1812 cross-compilers on the Alpha for 32-bit machines has only been tested in
1813 a few cases and may not work properly.
1815 @code{make compare} may fail on old versions of DEC Unix unless you add
1816 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
1817 assembler input file is stored in the object file, and that makes
1818 comparison fail if it differs between the @code{stage1} and
1819 @code{stage2} compilations. The option @option{-save-temps} forces a
1820 fixed name to be used for the assembler input file, instead of a
1821 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
1822 unless the comparisons fail without that option. If you add
1823 @option{-save-temps}, you will have to manually delete the @samp{.i} and
1824 @samp{.s} files after each series of compilations.
1826 GCC now supports both the native (ECOFF) debugging format used by DBX
1827 and GDB and an encapsulated STABS format for use only with GDB@. See the
1828 discussion of the @option{--with-stabs} option of @file{configure} above
1829 for more information on these formats and how to select them.
1831 There is a bug in DEC's assembler that produces incorrect line numbers
1832 for ECOFF format when the @samp{.align} directive is used. To work
1833 around this problem, GCC will not emit such alignment directives
1834 while writing ECOFF format debugging information even if optimization is
1835 being performed. Unfortunately, this has the very undesirable
1836 side-effect that code addresses when @option{-O} is specified are
1837 different depending on whether or not @option{-g} is also specified.
1839 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
1840 DBX@. DEC is now aware of this problem with the assembler and hopes to
1841 provide a fix shortly.
1846 @heading @anchor{alphaev5-cray-unicosmk*}alphaev5-cray-unicosmk*
1847 Cray T3E systems running Unicos/Mk.
1849 This port is incomplete and has many known bugs. We hope to improve the
1850 support for this target soon. Currently, only the C front end is supported,
1851 and it is not possible to build parallel applications. Cray modules are not
1852 supported; in particular, Craylibs are assumed to be in
1853 @file{/opt/ctl/craylibs/craylibs}.
1855 You absolutely @strong{must} use GNU make on this platform. Also, you
1856 need to tell GCC where to find the assembler and the linker. The
1857 simplest way to do so is by providing @option{--with-as} and
1858 @option{--with-ld} to @file{configure}, e.g.@:
1861 configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld \
1862 --enable-languages=c
1865 The comparison test during @samp{make bootstrap} fails on Unicos/Mk
1866 because the assembler inserts timestamps into object files. You should
1867 be able to work around this by doing @samp{make all} after getting this
1873 @heading @anchor{arc-*-elf}arc-*-elf
1874 Argonaut ARC processor.
1875 This configuration is intended for embedded systems.
1880 @heading @anchor{arm-*-aout}arm-*-aout
1881 Advanced RISC Machines ARM-family processors. These are often used in
1882 embedded applications. There are no standard Unix configurations.
1883 This configuration corresponds to the basic instruction sequences and will
1884 produce @file{a.out} format object modules.
1886 You may need to make a variant of the file @file{arm.h} for your particular
1892 @heading @anchor{arm-*-elf}arm-*-elf
1893 This configuration is intended for embedded systems.
1898 @heading @anchor{arm*-*-linux-gnu}arm*-*-linux-gnu
1900 We require GNU binutils 2.10 or newer.
1905 @heading @anchor{avr}avr
1907 ATMEL AVR-family micro controllers. These are used in embedded
1908 applications. There are no standard Unix configurations.
1910 @xref{AVR Options,, AVR Options, gcc, Using and Porting the GNU Compiler
1914 See ``AVR Options'' in the main manual
1916 for the list of supported MCU types.
1918 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
1920 Further installation notes and other useful information about AVR tools
1921 can also be obtained from:
1925 @uref{http://www.openavr.org,,http://www.openavr.org}
1927 @uref{http://home.overta.ru/users/denisc,,http://home.overta.ru/users/denisc}
1929 @uref{http://www.amelek.gda.pl/avr,,http://www.amelek.gda.pl/avr}
1932 We @emph{strongly} recommend using binutils 2.13 or newer.
1934 The following error:
1936 Error: register required
1939 indicates that you should upgrade to a newer version of the binutils.
1944 @heading @anchor{c4x}c4x
1946 Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal
1947 Processors. These are used in embedded applications. There are no
1948 standard Unix configurations.
1950 @xref{TMS320C3x/C4x Options,, TMS320C3x/C4x Options, gcc, Using and
1951 Porting the GNU Compiler Collection (GCC)},
1954 See ``TMS320C3x/C4x Options'' in the main manual
1956 for the list of supported MCU types.
1958 GCC can be configured as a cross compiler for both the C3x and C4x
1959 architectures on the same system. Use @samp{configure --target=c4x
1960 --enable-languages="c,c++"} to configure.
1963 Further installation notes and other useful information about C4x tools
1964 can also be obtained from:
1968 @uref{http://www.elec.canterbury.ac.nz/c4x/,,http://www.elec.canterbury.ac.nz/c4x/}
1974 @heading @anchor{cris}CRIS
1976 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
1977 series. These are used in embedded applications.
1980 @xref{CRIS Options,, CRIS Options, gcc, Using and Porting the GNU Compiler
1984 See ``CRIS Options'' in the main manual
1986 for a list of CRIS-specific options.
1988 There are a few different CRIS targets:
1990 @item cris-axis-aout
1991 Old target. Includes a multilib for the @samp{elinux} a.out-based
1992 target. No multilibs for newer architecture variants.
1994 Mainly for monolithic embedded systems. Includes a multilib for the
1995 @samp{v10} core used in @samp{ETRAX 100 LX}.
1996 @item cris-axis-linux-gnu
1997 A GNU/Linux port for the CRIS architecture, currently targeting
1998 @samp{ETRAX 100 LX} by default.
2001 For @code{cris-axis-aout} and @code{cris-axis-elf} you need binutils 2.11
2002 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
2004 Pre-packaged tools can be obtained from
2005 @uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More
2006 information about this platform is available at
2007 @uref{http://developer.axis.com/}.
2012 @heading @anchor{dos}DOS
2014 Please have a look at our @uref{binaries.html,,binaries page}.
2016 You cannot install GCC by itself on MSDOS; it will not compile under
2017 any MSDOS compiler except itself. You need to get the complete
2018 compilation package DJGPP, which includes binaries as well as sources,
2019 and includes all the necessary compilation tools and libraries.
2024 @heading @anchor{dsp16xx}dsp16xx
2025 A port to the AT&T DSP1610 family of processors.
2030 @heading @anchor{*-*-freebsd*}*-*-freebsd*
2032 The version of binutils installed in @file{/usr/bin} is known to work unless
2033 otherwise specified in any per-architecture notes. However, binutils
2034 2.12.1 or greater is known to improve overall testsuite results.
2036 FreeBSD 1 is no longer supported in GCC 3.2.
2038 For FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
2039 configuration support and files as shipped with GCC 2.95 are still in
2040 place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
2041 it is unknown which version of binutils was used (it is assumed that it
2042 was the system copy in @file{/usr/bin}) and C++ EH failures were noted.
2044 For FreeBSD using the ELF file format: DWARF 2 debugging is now the
2045 default for all CPU architectures. It had been the default on
2046 FreeBSD/alpha since its inception. You may use @option{-gstabs} instead
2047 of @option{-g}, if you really want the old debugging format. There are
2048 no known issues with mixing object files and libraries with different
2049 debugging formats. Otherwise, this release of GCC should now match more
2050 of the configuration used in the stock FreeBSD configuration of GCC. In
2051 particular, @option{--enable-threads} is now configured by default.
2052 However, as a general user, do not attempt to replace the system
2053 compiler with this release. Known to bootstrap and check with good
2054 results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4, 4.5-STABLE and 5-CURRENT@.
2056 In principle, @option{--enable-threads} is now compatible with
2057 @option{--enable-libgcj} on FreeBSD@. However, it has only been built
2058 and tested on @samp{i386-*-freebsd4.5} and @samp{alpha-*-freebsd5.0}.
2060 library may be incorrectly built (symbols are missing at link time).
2061 There is a rare timing-based startup hang (probably involves an
2062 assumption about the thread library). Multi-threaded boehm-gc (required for
2063 libjava) exposes severe threaded signal-handling bugs on FreeBSD before
2064 4.5-RELEASE. The alpha port may not fully bootstrap without some manual
2065 intervention: @command{gcjh} will crash with a floating-point exception while
2066 generating @file{java/lang/Double.h} (just copy the version built on
2067 @samp{i386-*-freebsd*} and rerun the top-level @command{gmake} with no
2069 should properly complete the bootstrap). Other CPU architectures
2070 supported by FreeBSD will require additional configuration tuning in, at
2071 the very least, both boehm-gc and libffi.
2073 Shared @file{libgcc_s.so} is now built and installed by default.
2078 @heading @anchor{h8300-hms}h8300-hms
2079 Hitachi H8/300 series of processors.
2081 Please have a look at our @uref{binaries.html,,binaries page}.
2083 The calling convention and structure layout has changed in release 2.6.
2084 All code must be recompiled. The calling convention now passes the
2085 first three arguments in function calls in registers. Structures are no
2086 longer a multiple of 2 bytes.
2091 @heading @anchor{hppa*-hp-hpux*}hppa*-hp-hpux*
2093 We @emph{highly} recommend using gas/binutils 2.8 or newer on all hppa
2094 platforms; you may encounter a variety of problems when using the HP
2097 Specifically, @option{-g} does not work on HP-UX (since that system
2098 uses a peculiar debugging format which GCC does not know about), unless you
2099 use GAS and GDB and configure GCC with the
2100 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
2101 @option{--with-as=@dots{}} options.
2103 If you wish to use the pa-risc 2.0 architecture support with a 32-bit
2104 runtime, you must use either the HP assembler, gas/binutils 2.11 or newer,
2106 @uref{ftp://sources.redhat.com/pub/binutils/snapshots,,snapshot of gas}.
2108 There are two default scheduling models for instructions. These are
2109 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
2110 architecture specified for the target machine when configuring.
2111 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
2112 the target is a @samp{hppa1*} machine.
2114 The PROCESSOR_8000 model is not well suited to older processors. Thus,
2115 it is important to completely specify the machine architecture when
2116 configuring if you want a model other than PROCESSOR_8000. The macro
2117 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
2118 default scheduling model is desired.
2120 More specific information to @samp{hppa*-hp-hpux*} targets follows.
2125 @heading @anchor{hppa*-hp-hpux9}hppa*-hp-hpux9
2127 The HP assembler has major problems on this platform. We've tried to work
2128 around the worst of the problems. However, those workarounds may be causing
2129 linker crashes in some circumstances; the workarounds also probably prevent
2130 shared libraries from working. Use the GNU assembler to avoid these problems.
2133 The configuration scripts for GCC will also trigger a bug in the hpux9
2134 shell. To avoid this problem set @env{CONFIG_SHELL} to @file{/bin/ksh}
2135 and @env{SHELL} to @file{/bin/ksh} in your environment.
2141 @heading @anchor{hppa*-hp-hpux10}hppa*-hp-hpux10
2143 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
2144 @code{PHCO_19798} from HP@. HP has two sites which provide patches free of
2150 <a href="http://us-support.external.hp.com">US, Canada, Asia-Pacific, and
2154 @uref{http://us-support.external.hp.com,,}US, Canada, Asia-Pacific, and
2158 @uref{http://europe-support.external.hp.com,,Europe}
2161 The HP assembler on these systems is much better than the hpux9 assembler,
2162 but still has some problems. Most notably the assembler inserts timestamps
2163 into each object file it creates, causing the 3-stage comparison test to fail
2164 during a @samp{make bootstrap}. You should be able to continue by
2165 saying @samp{make all} after getting the failure from @samp{make
2172 @heading @anchor{hppa*-hp-hpux11}hppa*-hp-hpux11
2174 GCC 3.0 and up support HP-UX 11. On 64-bit capable systems, there
2175 are two distinct ports. The @samp{hppa2.0w-hp-hpux11*} port generates
2176 code for the 32-bit pa-risc runtime architecture. It uses the HP
2177 linker and is currently the default selected by config.guess. The
2178 optional @samp{hppa64-hp-hpux11*} port generates 64-bit code for the
2179 pa-risc 2.0 architecture. It must be explicitly selected using the
2180 @samp{--host=hppa64-hp-hpux11*} configure option. Different prefixes
2181 must be used if both ports are to be installed on the same system.
2183 You must use GNU binutils 2.11 or above with the 32-bit port. Thread
2184 support is not currently implemented, so @option{--enable-threads} does
2188 @item @uref{http://gcc.gnu.org/ml/gcc-prs/2002-01/msg00551.html}
2189 @item @uref{http://gcc.gnu.org/ml/gcc-bugs/2002-01/msg00663.html}
2192 GCC 2.95.x is not supported under HP-UX 11 and cannot be used to
2193 compile GCC 3.0 and up. Refer to @uref{binaries.html,,binaries} for
2194 information about obtaining precompiled GCC binaries for HP-UX.
2196 GNU binutils 2.13 or later is recommended with the 64-bit port.
2197 The HP assembler has many limitations and is not recommended. For
2198 example, it does not support weak symbols or alias definitions.
2199 As a result, explicit template instantiations are required when
2200 using C++. Either the HP or GNU linker can be used but it may be
2201 necessary to use the GNU linker when dwarf2 exception support is
2204 There are several possible approaches to building the distribution.
2205 Binutils can be built first using the HP tools. Then, the GCC
2206 distribution can be built. The second approach is to build GCC
2207 first using the HP tools, then build binutils, then rebuild GCC.
2208 There have been problems with various binary distributions, so
2209 it is best not to start from a binary distribution.
2211 When starting with a HP compiler, it is preferable to use the ANSI
2212 compiler as the bundled compiler only supports traditional C.
2213 Bootstrapping with the bundled compiler is tested infrequently and
2214 problems often arise because of the subtle differences in semantics
2215 between traditional and ISO C.
2217 This port still is undergoing significant development.
2222 @heading @anchor{i370-*-*}i370-*-*
2223 This port is very preliminary and has many known bugs. We hope to
2224 have a higher-quality port for this machine soon.
2229 @heading @anchor{*-*-linux-gnu}*-*-linux-gnu
2231 If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install
2232 out-of-the-box. You'll get compile errors while building @samp{libstdc++}.
2233 The patch @uref{glibc-2.2.patch,,glibc-2.2.patch}, that is to be
2234 applied in the GCC source tree, fixes the compatibility problems.
2243 Currently Glibc 2.2.3 (and older releases) and GCC 3.0 are out of sync
2244 since the latest exception handling changes for GCC@. Compiling glibc
2245 with GCC 3.0 will give a binary incompatible glibc and therefore cause
2246 lots of problems and might make your system completly unusable. This
2247 will definitly need fixes in glibc but might also need fixes in GCC@. We
2248 strongly advise to wait for glibc 2.2.4 and to read the release notes of
2249 glibc 2.2.4 whether patches for GCC 3.0 are needed. You can use glibc
2250 2.2.3 with GCC 3.0, just do not try to recompile it.
2255 @heading @anchor{ix86-*-linux*aout}i?86-*-linux*aout
2256 Use this configuration to generate @file{a.out} binaries on Linux-based
2257 GNU systems. This configuration is being superseded. You must use
2258 gas/binutils version 2.5.2 or later.
2263 @heading @anchor{ix86-*-linux*}i?86-*-linux*
2265 You will need binutils 2.9.1.0.15 or newer for exception handling to work.
2267 If you receive Signal 11 errors when building on GNU/Linux, then it is
2268 possible you have a hardware problem. Further information on this can be
2269 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
2274 @heading @anchor{ix86-*-sco}i?86-*-sco
2275 Compilation with RCC is recommended. Also, it may be a good idea to
2276 link with GNU malloc instead of the malloc that comes with the system.
2281 @heading @anchor{ix86-*-sco3.2v4}i?86-*-sco3.2v4
2282 Use this configuration for SCO release 3.2 version 4.
2287 @heading @anchor{ix86-*-sco3.2v5*}i?86-*-sco3.2v5*
2288 Use this for the SCO OpenServer Release 5 family of operating systems.
2290 Unlike earlier versions of GCC, the ability to generate COFF with this
2291 target is no longer provided.
2293 Earlier versions of GCC emitted DWARF 1 when generating ELF to allow
2294 the system debugger to be used. That support was too burdensome to
2295 maintain. GCC now emits only DWARF 2 for this target. This means you
2296 may use either the UDK debugger or GDB to debug programs built by this
2299 Use of the @option{-march=pentiumpro} flag can result in
2300 unrecognized opcodes when using the native assembler on OS versions before
2301 5.0.6. (Support for P6 opcodes was added to the native ELF assembler in
2302 that version.) While it's rather rare to see these emitted by GCC yet,
2303 errors of the basic form:
2306 /usr/tmp/ccaNlqBc.s:22:unknown instruction: fcomip
2307 /usr/tmp/ccaNlqBc.s:50:unknown instruction: fucomip
2310 are symptoms of this problem. You may work around this by not
2311 building affected files with that flag, by using the GNU assembler, or
2312 by using the assembler provided with the current version of the OS@.
2313 Users of GNU assembler should see the note below for hazards on doing
2316 The native SCO assembler that is provided with the OS at no
2317 charge is normally required. If, however, you must be able to use
2318 the GNU assembler (perhaps you're compiling code with asms that
2319 require GAS syntax) you may configure this package using the flags
2320 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You must
2321 use a recent version of GNU binutils; versions past 2.9.1 seem to work
2324 In general, the @option{--with-gnu-as} option isn't as well tested
2325 as the native assembler.
2327 Look in @file{gcc/config/i386/sco5.h} (search for ``messy'') for
2328 additional OpenServer-specific flags.
2330 Systems based on OpenServer before 5.0.4 (@samp{uname -X}
2331 will tell you what you're running) require TLS597 from
2332 @uref{ftp://ftp.sco.com/TLS/,,ftp://ftp.sco.com/TLS/}
2333 for C++ constructors and destructors to work right.
2335 The system linker in (at least) 5.0.4 and 5.0.5 will sometimes
2336 do the wrong thing for a construct that GCC will emit for PIC
2337 code. This can be seen as execution testsuite failures when using
2338 @option{-fPIC} on @file{921215-1.c}, @file{931002-1.c}, @file{nestfunc-1.c}, and @file{gcov-1.c}.
2339 For 5.0.5, an updated linker that will cure this problem is
2340 available. You must install both
2341 @uref{ftp://ftp.sco.com/Supplements/rs505a/,,ftp://ftp.sco.com/Supplements/rs505a/}
2342 and @uref{ftp://ftp.sco.com/SLS/,,OSS499A}.
2344 The dynamic linker in OpenServer 5.0.5 (earlier versions may show
2345 the same problem) aborts on certain G77-compiled programs. It's particularly
2346 likely to be triggered by building Fortran code with the @option{-fPIC} flag.
2347 Although it's conceivable that the error could be triggered by other
2348 code, only G77-compiled code has been observed to cause this abort.
2349 If you are getting core dumps immediately upon execution of your
2350 G77 program---and especially if it's compiled with @option{-fPIC}---try applying
2351 @uref{sco_osr5_g77.patch,,@file{sco_osr5_g77.patch}} to your @samp{libf2c} and
2353 Affected faults, when analyzed in a debugger, will show a stack
2354 backtrace with a fault occurring in @code{rtld()} and the program
2355 running as @file{/usr/lib/ld.so.1}. This problem has been reported to SCO
2356 engineering and will hopefully be addressed in later releases.
2362 @heading @anchor{ix86-*-udk}i?86-*-udk
2364 This target emulates the SCO Universal Development Kit and requires that
2365 package be installed. (If it is installed, you will have a
2366 @file{/udk/usr/ccs/bin/cc} file present.) It's very much like the
2367 @samp{i?86-*-unixware7*} target
2368 but is meant to be used when hosting on a system where UDK isn't the
2369 default compiler such as OpenServer 5 or Unixware 2. This target will
2370 generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
2371 with the same warnings and caveats as the SCO UDK@.
2373 This target is a little tricky to build because we have to distinguish
2374 it from the native tools (so it gets headers, startups, and libraries
2375 from the right place) while making the tools not think we're actually
2376 building a cross compiler. The easiest way to do this is with a configure
2380 CC=/udk/usr/ccs/bin/cc @var{/your/path/to}/gcc/configure \
2381 --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-
2384 @emph{You should substitute @samp{i686} in the above command with the appropriate
2385 processor for your host.}
2387 After the usual @samp{make bootstrap} and
2388 @samp{make install}, you can then access the UDK-targeted GCC
2389 tools by adding @command{udk-} before the commonly known name. For
2390 example, to invoke the C compiler, you would use @command{udk-gcc}.
2391 They will coexist peacefully with any native-target GCC tools you may
2398 @heading @anchor{ia64-*-linux}ia64-*-linux
2399 IA-64 processor (also known as IPF, or Itanium Processor Family)
2402 The toolchain is not completely finished, so requirements will continue
2404 GCC 3.0.1 and later require glibc 2.2.4.
2405 GCC 3.0.2 requires binutils from 2001-09-05 or later.
2406 GCC 3.0.1 requires binutils 2.11.1 or later.
2408 None of the following versions of GCC has an ABI that is compatible
2409 with any of the other versions in this list, with the exception that
2410 Red Hat 2.96 and Trillian 000171 are compatible with each other:
2411 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
2412 This primarily affects C++ programs and programs that create shared libraries.
2413 Because of these ABI incompatibilities, GCC 3.0.2 is not recommended for
2414 user programs on GNU/Linux systems built using earlier compiler releases.
2415 GCC 3.0.2 is recommended for compiling linux, the kernel.
2416 GCC 3.0.2 is believed to be fully ABI compliant, and hence no more major
2417 ABI changes are expected.
2422 @heading @anchor{*-lynx-lynxos}*-lynx-lynxos
2423 LynxOS 2.2 and earlier comes with GCC 1.x already installed as
2424 @file{/bin/gcc}. You should compile with this instead of @file{/bin/cc}.
2425 You can tell GCC to use the GNU assembler and linker, by specifying
2426 @samp{--with-gnu-as --with-gnu-ld} when configuring. These will produce
2427 COFF format object files and executables; otherwise GCC will use the
2428 installed tools, which produce @file{a.out} format executables.
2432 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
2434 @heading @anchor{*-ibm-aix*}*-ibm-aix*
2436 AIX Make frequently has problems with GCC makefiles. GNU Make 3.76 or
2437 newer is recommended to build on this platform.
2439 Errors involving @code{alloca} when building GCC generally are due
2440 to an incorrect definition of @code{CC} in the Makefile or mixing files
2441 compiled with the native C compiler and GCC@. During the stage1 phase of
2442 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
2443 (not @command{xlc}). Once @command{configure} has been informed of
2444 @command{xlc}, one needs to use @samp{make distclean} to remove the
2445 configure cache files and ensure that @env{CC} environment variable
2446 does not provide a definition that will confuse @command{configure}.
2447 If this error occurs during stage2 or later, then the problem most likely
2448 is the version of Make (see above).
2450 The GNU Assembler incorrectly reports that it supports WEAK symbols on
2451 AIX which causes GCC to try to utilize weak symbol functionality although
2452 it is not supported on the platform. The native @command{as} and
2453 @command{ld} still are recommended. The native AIX tools do
2454 interoperate with GCC@.
2456 Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
2457 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1).
2459 @samp{libstdc++} in GCC 3.2 increments the major version number of the
2460 shared object and GCC installation places the @file{libstdc++.a}
2461 shared library in a common location which will overwrite the GCC 3.1
2462 version of the shared library. Applications either need to be
2463 re-linked against the new shared library or the GCC 3.1 version of the
2464 @samp{libstdc++} shared object needs to be available to the AIX
2465 runtime loader. The GCC 3.1 @samp{libstdc++.so.4} shared object can
2466 be installed for runtime dynamic loading using the following steps to
2467 set the @samp{F_LOADONLY} flag in the shared object for @emph{each}
2468 multilib @file{libstdc++.a} installed:
2470 Extract the shared object from each the GCC 3.1 @file{libstdc++.a}
2473 % ar -x libstdc++.a libstdc++.so.4
2476 Enable the @samp{F_LOADONLY} flag so that the shared object will be
2477 available for runtime dynamic loading, but not linking:
2479 % strip -e libstdc++.so.4
2482 Archive the runtime-only shared object in the GCC 3.2
2483 @file{libstdc++.a} archive:
2485 % ar -q libstdc++.a libstdc++.so.4
2488 Linking executables and shared libraries may produce warnings of
2489 duplicate symbols. The assembly files generated by GCC for AIX always
2490 have included multiple symbol definitions for certain global variable
2491 and function declarations in the original program. The warnings should
2492 not prevent the linker from producing a correct library or runnable
2495 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
2496 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
2497 to parse archive libraries did not handle the new format correctly.
2498 These routines are used by GCC and result in error messages during
2499 linking such as ``not a COFF file''. The version of the routines shipped
2500 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
2501 option of the archive command may be used to create archives of 32-bit
2502 objects using the original ``small format''. A correct version of the
2503 routines is shipped with AIX 4.3.2 and above.
2505 Some versions of the AIX binder (linker) can fail with a relocation
2506 overflow severe error when the @option{-bbigtoc} option is used to link
2507 GCC-produced object files into an executable that overflows the TOC@. A fix
2508 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
2509 available from IBM Customer Support and from its
2510 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2511 website as PTF U455193.
2513 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
2514 with a segmentation fault when invoked by any version of GCC@. A fix for
2515 APAR IX87327 is available from IBM Customer Support and from its
2516 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2517 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
2519 The initial assembler shipped with AIX 4.3.0 generates incorrect object
2520 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
2521 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
2522 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2523 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
2525 AIX provides National Language Support (NLS)@. Compilers and assemblers
2526 use NLS to support locale-specific representations of various data
2527 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
2528 separating decimal fractions). There have been problems reported where
2529 GCC does not produce the same floating-point formats that the assembler
2530 expects. If one encounters this problem, set the @env{LANG}
2531 environment variable to @samp{C} or @samp{En_US}.
2533 By default, GCC for AIX 4.1 and above produces code that can be used on
2534 both Power or PowerPC processors.
2536 A default can be specified with the @option{-mcpu=@var{cpu_type}}
2537 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
2542 @heading @anchor{ip2k-*-elf}ip2k-*-elf
2543 Ubicom IP2022 micro controller.
2544 This configuration is intended for embedded systems.
2545 There are no standard Unix configurations.
2547 Use @samp{configure --target=ip2k-elf --enable-languages=c} to configure GCC@.
2552 @heading @anchor{m32r-*-elf}m32r-*-elf
2553 Mitsubishi M32R processor.
2554 This configuration is intended for embedded systems.
2559 @heading @anchor{m68000-hp-bsd}m68000-hp-bsd
2560 HP 9000 series 200 running BSD@. Note that the C compiler that comes
2561 with this system cannot compile GCC; contact @email{law@@cygnus.com}
2562 to get binaries of GCC for bootstrapping.
2567 @heading @anchor{m6811-elf}m6811-elf
2568 Motorola 68HC11 family micro controllers. These are used in embedded
2569 applications. There are no standard Unix configurations.
2574 @heading @anchor{m6812-elf}m6812-elf
2575 Motorola 68HC12 family micro controllers. These are used in embedded
2576 applications. There are no standard Unix configurations.
2581 @heading @anchor{m68k-att-sysv}m68k-att-sysv
2582 AT&T 3b1, a.k.a.@: 7300 PC@. This version of GCC cannot
2583 be compiled with the system C compiler, which is too buggy.
2584 You will need to get a previous version of GCC and use it to
2585 bootstrap. Binaries are available from the OSU-CIS archive, at
2586 @uref{ftp://archive.cis.ohio-state.edu/pub/att7300/}.
2591 @heading @anchor{m68k-crds-unos}m68k-crds-unos
2592 Use @samp{configure unos} for building on Unos.
2594 The Unos assembler is named @code{casm} instead of @code{as}. For some
2595 strange reason linking @file{/bin/as} to @file{/bin/casm} changes the
2596 behavior, and does not work. So, when installing GCC, you should
2597 install the following script as @file{as} in the subdirectory where
2598 the passes of GCC are installed:
2605 The default Unos library is named @file{libunos.a} instead of
2606 @file{libc.a}. To allow GCC to function, either change all
2607 references to @option{-lc} in @file{gcc.c} to @option{-lunos} or link
2608 @file{/lib/libc.a} to @file{/lib/libunos.a}.
2610 @cindex @code{alloca}, for Unos
2611 When compiling GCC with the standard compiler, to overcome bugs in
2612 the support of @code{alloca}, do not use @option{-O} when making stage 2.
2613 Then use the stage 2 compiler with @option{-O} to make the stage 3
2614 compiler. This compiler will have the same characteristics as the usual
2615 stage 2 compiler on other systems. Use it to make a stage 4 compiler
2616 and compare that with stage 3 to verify proper compilation.
2618 (Perhaps simply defining @code{ALLOCA} in @file{x-crds} as described in
2619 the comments there will make the above paragraph superfluous. Please
2620 inform us of whether this works.)
2622 Unos uses memory segmentation instead of demand paging, so you will need
2623 a lot of memory. 5 Mb is barely enough if no other tasks are running.
2624 If linking @file{cc1} fails, try putting the object files into a library
2625 and linking from that library.
2630 @heading @anchor{m68k-hp-hpux}m68k-hp-hpux
2631 HP 9000 series 300 or 400 running HP-UX@. HP-UX version 8.0 has a bug in
2632 the assembler that prevents compilation of GCC@. This
2633 bug manifests itself during the first stage of compilation, while
2634 building @file{libgcc2.a}:
2638 cc1: warning: `-g' option not supported on this version of GCC
2639 cc1: warning: `-g1' option not supported on this version of GCC
2640 ./xgcc: Internal compiler error: program as got fatal signal 11
2643 A patched version of the assembler is available as the file
2644 @uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you
2645 have HP software support, the patch can also be obtained directly from
2646 HP, as described in the following note:
2649 This is the patched assembler, to patch SR#1653-010439, where the
2650 assembler aborts on floating point constants.
2652 The bug is not really in the assembler, but in the shared library
2653 version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is
2654 SR#4701-078451. Anyway, the attached assembler uses the archive
2655 library version of ``cvtnum(3c)'' and thus does not exhibit the bug.
2658 This patch is also known as PHCO_4484.
2660 In addition, if you wish to use gas, you must use
2661 gas version 2.1 or later, and you must use the GNU linker version 2.1 or
2662 later. Earlier versions of gas relied upon a program which converted the
2663 gas output into the native HP-UX format, but that program has not been
2664 kept up to date. gdb does not understand that native HP-UX format, so
2665 you must use gas if you wish to use gdb.
2667 On HP-UX version 8.05, but not on 8.07 or more recent versions, the
2668 @code{fixproto} shell script triggers a bug in the system shell. If you
2669 encounter this problem, upgrade your operating system or use BASH (the
2670 GNU shell) to run @code{fixproto}. This bug will cause the fixproto
2671 program to report an error of the form:
2674 ./fixproto: sh internal 1K buffer overflow
2677 To fix this, you can also change the first line of the fixproto script
2688 @heading @anchor{m68k-ncr-*}m68k-ncr-*
2689 On the Tower models 4@var{n}0 and 6@var{n}0, by default a process is not
2690 allowed to have more than one megabyte of memory. GCC cannot compile
2691 itself (or many other programs) with @option{-O} in that much memory.
2693 To solve this problem, reconfigure the kernel adding the following line
2694 to the configuration file:
2704 @heading @anchor{m68k-sun}m68k-sun
2705 Sun 3. We do not provide a configuration file to use the Sun FPA by
2706 default, because programs that establish signal handlers for floating
2707 point traps inherently cannot work with the FPA@.
2712 @heading @anchor{m68k-sun-sunos4.1.1}m68k-sun-sunos4.1.1
2714 It is reported that you may need the GNU assembler on this platform.
2720 @heading @anchor{mips-*-*}mips-*-*
2721 If on a MIPS system you get an error message saying ``does not have gp
2722 sections for all it's [sic] sectons [sic]'', don't worry about it. This
2723 happens whenever you use GAS with the MIPS linker, but there is not
2724 really anything wrong, and it is okay to use the output file. You can
2725 stop such warnings by installing the GNU linker.
2727 It would be nice to extend GAS to produce the gp tables, but they are
2728 optional, and there should not be a warning about their absence.
2730 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
2732 This configuration has considerable problems, which will be fixed in a
2735 In order to compile GCC on an SGI running IRIX 5, the ``compiler_dev.hdr''
2736 subsystem must be installed from the IDO CD-ROM supplied by Silicon
2737 Graphics. It is also available for download from
2738 @uref{http://www.sgi.com/developers/devtools/apis/ido.html,,http://www.sgi.com/developers/devtools/apis/ido.html}.
2740 @code{make compare} may fail on version 5 of IRIX unless you add
2741 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
2742 assembler input file is stored in the object file, and that makes
2743 comparison fail if it differs between the @code{stage1} and
2744 @code{stage2} compilations. The option @option{-save-temps} forces a
2745 fixed name to be used for the assembler input file, instead of a
2746 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
2747 unless the comparisons fail without that option. If you do you
2748 @option{-save-temps}, you will have to manually delete the @samp{.i} and
2749 @samp{.s} files after each series of compilations.
2751 If you use the MIPS C compiler to bootstrap, it may be necessary
2752 to increase its table size for switch statements with the
2753 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
2754 optimization option, you also need to use @option{-Olimit 3000}.
2756 To enable debugging under IRIX 5, you must use GNU @command{as} 2.11.2
2758 and use the @option{--with-gnu-as} configure option when configuring GCC.
2759 GNU @command{as} is distributed as part of the binutils package.
2760 When using release 2.11.2, you need to apply a patch
2761 @uref{http://sources.redhat.com/ml/binutils/2001-07/msg00352.html,,http://sources.redhat.com/ml/binutils/2001-07/msg00352.html}
2762 which will be included in the next release of binutils.
2764 When building GCC, the build process loops rebuilding @command{cc1} over
2765 and over again. This happens on @samp{mips-sgi-irix5.2}, and possibly
2766 other platforms. It has been reported that this is a known bug in the
2767 @command{make} shipped with IRIX 5.2. We recommend you use GNU
2768 @command{make} instead of the vendor supplied @command{make} program;
2769 however, you may have success with @command{smake} on IRIX 5.2 if you do
2770 not have GNU @command{make} available.
2775 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
2777 If you are using IRIX @command{cc} as your bootstrap compiler, you must
2778 ensure that the N32 ABI is in use. To test this, compile a simple C
2779 file with @command{cc} and then run @command{file} on the
2780 resulting object file. The output should look like:
2783 test.o: ELF N32 MSB @dots{}
2789 test.o: ELF 32-bit MSB @dots{}
2795 test.o: ELF 64-bit MSB @dots{}
2798 then your version of @command{cc} uses the O32 or N64 ABI by default. You
2799 should set the environment variable @env{CC} to @samp{cc -n32}
2800 before configuring GCC@.
2802 If you want the resulting @command{gcc} to run on old 32-bit systems
2803 with the MIPS R4400 CPU, you need to ensure that only code for the mips3
2804 instruction set architecture (ISA) is generated. While GCC 3.x does
2805 this correctly, both GCC 2.95 and SGI's MIPSpro @command{cc} may change
2806 the ISA depending on the machine where GCC is built. Using one of them
2807 as the bootstrap compiler may result in mips4 code, which won't run at
2808 all on mips3-only systems. For the test program above, you should see:
2811 test.o: ELF N32 MSB mips-3 @dots{}
2817 test.o: ELF N32 MSB mips-4 @dots{}
2820 instead, you should set the environment variable @env{CC} to @samp{cc
2821 -n32 -mips3} or @samp{gcc -mips3} respectively before configuring GCC@.
2823 GCC on IRIX 6 is usually built to support both the N32 and N64 ABIs. If
2824 you build GCC on a system that doesn't have the N64 libraries installed,
2825 you need to configure with @option{--disable-multilib} so GCC doesn't
2826 try to use them. Look for @file{/usr/lib64/libc.so.1} to see if you
2827 have the 64-bit libraries installed.
2829 You must @emph{not} use GNU @command{as} (which isn't built anyway as of
2830 binutils 2.11.2) on IRIX 6 platforms; doing so will only cause problems.
2832 GCC does not currently support generating O32 ABI binaries in the
2833 @samp{mips-sgi-irix6} configurations. It is possible to create a GCC
2834 with O32 ABI only support by configuring it for the @samp{mips-sgi-irix5}
2835 target and using a patched GNU @command{as} 2.11.2 as documented in the
2836 @uref{#mips-sgi-irix5,,@samp{mips-sgi-irix5}} section above. Using the
2837 native assembler requires patches to GCC which will be included in a
2838 future release. It is
2839 expected that O32 ABI support will be available again in a future release.
2841 The @option{--enable-threads} option doesn't currently work, a patch is
2842 in preparation for a future release. The @option{--enable-libgcj}
2843 option is disabled by default: IRIX 6 uses a very low default limit
2844 (20480) for the command line length. Although libtool contains a
2845 workaround for this problem, at least the N64 @samp{libgcj} is known not
2846 to build despite this, running into an internal error of the native
2847 @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
2848 its maximum of 262144 bytes. If you have root access, you can use the
2849 @command{systune} command to do this.
2851 GCC does not correctly pass/return structures which are
2852 smaller than 16 bytes and which are not 8 bytes. The problem is very
2853 involved and difficult to fix. It affects a number of other targets also,
2854 but IRIX 6 is affected the most, because it is a 64-bit target, and 4 byte
2855 structures are common. The exact problem is that structures are being padded
2856 at the wrong end, e.g.@: a 4 byte structure is loaded into the lower 4 bytes
2857 of the register when it should be loaded into the upper 4 bytes of the
2860 GCC is consistent with itself, but not consistent with the SGI C compiler
2861 (and the SGI supplied runtime libraries), so the only failures that can
2862 happen are when there are library functions that take/return such
2863 structures. There are very few such library functions. Currently this
2864 is known to affect @code{inet_ntoa}, @code{inet_lnaof},
2865 @code{inet_netof}, @code{inet_makeaddr}, and @code{semctl}. Until the
2866 bug is fixed, GCC contains workarounds for the known affected functions.
2868 See @uref{http://freeware.sgi.com/,,http://freeware.sgi.com/} for more
2869 information about using GCC on IRIX platforms.
2874 @heading @anchor{powerpc*-*-*}powerpc-*-*
2876 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
2877 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
2882 @heading @anchor{powerpc-*-darwin*}powerpc-*-darwin*
2883 PowerPC running Darwin (Mac OS X kernel).
2885 GCC 3.0 does not support Darwin, but 3.1 and later releases will work.
2887 Pre-installed versions of Mac OS X may not include any developer tools,
2888 meaning that you will not be able to build GCC from source. Tool
2889 binaries are available at
2890 @uref{http://www.opensource.apple.com/projects/darwin} (free
2891 registration required).
2893 Versions of the assembler prior to ``cctools-364'' cannot handle the
2894 4-argument form of @code{rlwinm} and related mask-using instructions. Darwin
2895 1.3 (Mac OS X 10.0) uses cctools-353 for instance. To get cctools-364,
2896 check out @file{cctools} with tag @samp{Apple-364}, build it, and
2897 install the assembler as @file{usr/bin/as}. See
2898 @uref{http://www.opensource.apple.com/tools/cvs/docs.html} for details.
2900 Also, the default stack limit of 512K is too small, and a bootstrap will
2901 typically fail when self-compiling @file{expr.c}. Set the stack to 800K
2902 or more, for instance by doing @samp{limit stack 800}. It's also
2903 convenient to use the GNU preprocessor instead of Apple's during the
2904 first stage of bootstrapping; this is automatic when doing @samp{make
2905 bootstrap}, but to do it from the toplevel objdir you will need to say
2906 @samp{make CC='cc -no-cpp-precomp' bootstrap}.
2908 Note that the version of GCC shipped by Apple typically includes a
2909 number of extensions not available in a standard GCC release. These
2910 extensions are generally specific to Mac programming.
2915 @heading @anchor{powerpc-*-elf}powerpc-*-elf, powerpc-*-sysv4
2916 PowerPC system in big endian mode, running System V.4.
2921 @heading @anchor{powerpc-*-linux-gnu*}powerpc-*-linux-gnu*
2924 @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.13.90.0.10}
2925 or newer for a working GCC@.
2930 @heading @anchor{powerpc-*-netbsd*}powerpc-*-netbsd*
2931 PowerPC system in big endian mode running NetBSD@. To build the
2932 documentation you will need Texinfo version 4.1 (NetBSD 1.5.1 included
2933 Texinfo version 3.12).
2938 @heading @anchor{powerpc-*-eabiaix}powerpc-*-eabiaix
2939 Embedded PowerPC system in big endian mode with @option{-mcall-aix} selected as
2945 @heading @anchor{powerpc-*-eabisim}powerpc-*-eabisim
2946 Embedded PowerPC system in big endian mode for use in running under the
2952 @heading @anchor{powerpc-*-eabi}powerpc-*-eabi
2953 Embedded PowerPC system in big endian mode.
2958 @heading @anchor{powerpcle-*-elf}powerpcle-*-elf, powerpcle-*-sysv4
2959 PowerPC system in little endian mode, running System V.4.
2964 @heading @anchor{powerpcle-*-eabisim}powerpcle-*-eabisim
2965 Embedded PowerPC system in little endian mode for use in running under
2971 @heading @anchor{powerpcle-*-eabi}powerpcle-*-eabi
2972 Embedded PowerPC system in little endian mode.
2977 @heading @anchor{powerpcle-*-winnt}powerpcle-*-winnt, powerpcle-*-pe
2978 PowerPC system in little endian mode running Windows NT@.
2983 @heading @anchor{s390-*-linux*}s390-*-linux*
2984 S/390 system running Linux for S/390@.
2989 @heading @anchor{s390x-*-linux*}s390x-*-linux*
2990 zSeries system (64-bit) running Linux for zSeries@.
2995 @c Please use Solaris 2 to refer to all release of Solaris, starting
2996 @c with 2.0 until 2.6, 7, and 8. Solaris 1 was a marketing name for
2997 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
2998 @c alone is too unspecific and must be avoided.
2999 @heading @anchor{*-*-solaris2*}*-*-solaris2*
3001 Sun does not ship a C compiler with Solaris 2. To bootstrap and install
3002 GCC you first have to install a pre-built compiler, see our
3003 @uref{binaries.html,,binaries page} for details.
3005 The Solaris 2 @command{/bin/sh} will often fail to configure
3006 @file{libstdc++-v3}, @file{boehm-gc} or
3007 @file{libjava}. If you encounter this problem, set @env{CONFIG_SHELL} to
3008 @command{/bin/ksh} in your environment before running @command{configure}.
3010 Solaris 2 comes with a number of optional OS packages. Some of these
3011 packages are needed to use GCC fully, namely @code{SUNWarc},
3012 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
3013 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
3014 optional packages when installing Solaris 2, you will need to verify that
3015 the packages that GCC needs are installed.
3017 To check whether an optional package is installed, use
3018 the @command{pkginfo} command. To add an optional package, use the
3019 @command{pkgadd} command. For further details, see the Solaris 2
3022 Trying to use the linker and other tools in
3023 @file{/usr/ucb} to install GCC has been observed to cause trouble.
3024 For example, the linker may hang indefinitely. The fix is to remove
3025 @file{/usr/ucb} from your @env{PATH}.
3027 All releases of GNU binutils prior to 2.11.2 have known bugs on this
3028 platform. We recommend the use of GNU binutils 2.11.2 or the vendor
3029 tools (Sun @command{as}, Sun @command{ld}).
3031 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3032 newer: @command{g++} will complain that types are missing. These headers assume
3033 that omitting the type means @code{int}; this assumption worked for C89 but
3034 is wrong for C++, and is now wrong for C99 also.
3036 @command{g++} accepts such (invalid) constructs with the option
3037 @option{-fpermissive}; it
3038 will assume that any missing type is @code{int} (as defined by C89).
3040 There are patches for Solaris 2.6 (105633-56 or newer for SPARC,
3041 106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC,
3042 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
3043 108653-22 for Intel) that fix this bug.
3048 @heading @anchor{sparc-sun-solaris2*}sparc-sun-solaris2*
3050 When GCC is configured to use binutils 2.11.2 or later the binaries
3051 produced are smaller than the ones produced using Sun's native tools;
3052 this difference is quite significant for binaries containing debugging
3055 Sun @command{as} 4.x is broken in that it cannot cope with long symbol names.
3056 A typical error message might look similar to the following:
3059 /usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error:
3060 can't compute value of an expression involving an external symbol.
3063 This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris
3064 2.6 and has been fixed in later (5.x) versions of the assembler,
3065 starting with Solaris 7.
3067 Starting with Solaris 7, the operating system is capable of executing
3068 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
3069 this; the @option{-m64} option enables 64-bit code generation.
3070 However, if all you want is code tuned for the UltraSPARC CPU, you
3071 should try the @option{-mtune=ultrasparc} option instead, which produces
3072 code that, unlike full 64-bit code, can still run on non-UltraSPARC
3075 When configuring on a Solaris 7 or later system that is running a kernel
3076 that supports only 32-bit binaries, one must configure with
3077 @option{--disable-multilib}, since we will not be able to build the
3078 64-bit target libraries.
3083 @heading @anchor{sparc-sun-solaris2.7}sparc-sun-solaris2.7
3085 Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
3086 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
3087 and later, including all EGCS releases. Sun formerly recommended
3088 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
3089 recommend it only for people who use Sun's compilers.
3091 Here are some workarounds to this problem:
3094 Do not install Sun patch 107058-01 until after Sun releases a
3095 complete patch for bug 4210064. This is the simplest course to take,
3096 unless you must also use Sun's C compiler. Unfortunately 107058-01
3097 is preinstalled on some new Solaris 7-based hosts, so you may have to
3101 Copy the original, unpatched Solaris 7
3102 @command{/usr/ccs/bin/as} into
3103 @command{/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/3.1/as},
3104 adjusting the latter name to fit your local conventions and software
3108 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
3109 both 107058-01 and 106950-03 installed has reported the bug with GCC
3110 and Sun's dynamic linker. This last course of action is riskiest,
3111 for two reasons. First, you must install 106950 on all hosts that
3112 run code generated by GCC; it doesn't suffice to install it only on
3113 the hosts that run GCC itself. Second, Sun says that 106950-03 is
3114 only a partial fix for bug 4210064, but Sun doesn't know whether the
3115 partial fix is adequate for GCC@. Revision -08 or later should fix
3116 the bug. The current (as of 2001-09-24) revision is -14, and is included in
3117 the Solaris 7 Recommended Patch Cluster.
3125 @heading @anchor{sparc-sun-sunos4*}sparc-sun-sunos4*
3127 A bug in the SunOS 4 linker will cause it to crash when linking
3128 @option{-fPIC} compiled objects (and will therefore not allow you to build
3131 To fix this problem you can either use the most recent version of
3132 binutils or get the latest SunOS 4 linker patch (patch ID 100170-10)
3133 from Sun's patch site.
3135 Sometimes on a Sun 4 you may observe a crash in the program
3136 @command{genflags} or @command{genoutput} while building GCC. This is said to
3137 be due to a bug in @command{sh}. You can probably get around it by running
3138 @command{genflags} or @command{genoutput} manually and then retrying the
3144 @heading @anchor{sparc-unknown-linux-gnulibc1}sparc-unknown-linux-gnulibc1
3146 It has been reported that you might need
3147 @uref{ftp://ftp.yggdrasil.com/private/hjl,,binutils 2.8.1.0.23}
3148 for this platform, too.
3154 @heading @anchor{sparc-*-linux*}sparc-*-linux*
3156 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
3157 or newer on this platform. All earlier binutils and glibc
3158 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
3164 @heading @anchor{sparc64-*-*}sparc64-*-*
3166 GCC version 2.95 is not able to compile code correctly for
3167 @code{sparc64} targets. Users of the Linux kernel, at least,
3168 can use the @code{sparc32} program to start up a new shell
3169 invocation with an environment that causes @command{configure} to
3170 recognize (via @samp{uname -a}) the system as @samp{sparc-*-*} instead.
3175 @heading @anchor{sparcv9-*-solaris2*}sparcv9-*-solaris2*
3177 The following compiler flags must be specified in the configure
3178 step in order to bootstrap this target with the Sun compiler:
3181 % CC="cc -xildoff -xarch=v9" @var{srcdir}/configure [@var{options}] [@var{target}]
3184 @option{-xildoff} turns off the incremental linker, and @option{-xarch=v9}
3185 specifies the v9 architecture to the Sun linker and assembler.
3190 @heading @anchor{#*-*-sysv*}*-*-sysv*
3191 On System V release 3, you may get this error message
3195 ld fatal: failed to write symbol name @var{something}
3196 in strings table for file @var{whatever}
3199 This probably indicates that the disk is full or your ulimit won't allow
3200 the file to be as large as it needs to be.
3202 This problem can also result because the kernel parameter @code{MAXUMEM}
3203 is too small. If so, you must regenerate the kernel and make the value
3204 much larger. The default value is reported to be 1024; a value of 32768
3205 is said to work. Smaller values may also work.
3207 On System V, if you get an error like this,
3210 /usr/local/lib/bison.simple: In function `yyparse':
3211 /usr/local/lib/bison.simple:625: virtual memory exhausted
3215 that too indicates a problem with disk space, ulimit, or @code{MAXUMEM}.
3217 On a System V release 4 system, make sure @file{/usr/bin} precedes
3218 @file{/usr/ucb} in @code{PATH}. The @code{cc} command in
3219 @file{/usr/ucb} uses libraries which have bugs.
3224 @heading @anchor{vax-dec-ultrix}vax-dec-ultrix
3225 Don't try compiling with VAX C (@code{vcc}). It produces incorrect code
3226 in some cases (for example, when @code{alloca} is used).
3231 @heading @anchor{*-*-vxworks*}*-*-vxworks*
3232 Support for VxWorks is in flux. At present GCC supports @emph{only} the
3233 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC.
3234 We welcome patches for other architectures supported by VxWorks 5.5.
3235 Support for VxWorks AE would also be welcome; we believe this is merely
3236 a matter of writing an appropriate ``configlette'' (see below). We are
3237 not interested in supporting older, a.out or COFF-based, versions of
3240 VxWorks comes with an older version of GCC installed in
3241 @file{@var{$WIND_BASE}/host}; we recommend you do not overwrite it.
3242 Choose an installation @var{prefix} entirely outside @var{$WIND_BASE}.
3243 Before running @command{configure}, create the directories @file{@var{prefix}}
3244 and @file{@var{prefix}/bin}. Link or copy the appropriate assembler,
3245 linker, etc. into @file{@var{prefix}/bin}, and set your @var{PATH} to
3246 include that directory while running both @command{configure} and
3249 You must give @command{configure} the
3250 @option{--with-headers=@var{$WIND_BASE}/target/h} switch so that it can
3251 find the VxWorks system headers. Since VxWorks is a cross compilation
3252 target only, you must also specify @option{--target=@var{target}}.
3253 @command{configure} will attempt to create the directory
3254 @file{@var{prefix}/@var{target}/sys-include} and copy files into it;
3255 make sure the user running @command{configure} has sufficient privilege
3258 GCC's exception handling runtime requires a special ``configlette''
3259 module, @file{contrib/gthr_supp_vxw_5x.c}. Follow the instructions in
3260 that file to add the module to your kernel build. (Future versions of
3261 VxWorks will incorporate this module.)
3266 @heading @anchor{xtensa-*-elf}xtensa-*-elf
3268 This target is intended for embedded Xtensa systems using the
3269 @samp{newlib} C library. It uses ELF but does not support shared
3270 objects. Designed-defined instructions specified via the
3271 Tensilica Instruction Extension (TIE) language are only supported
3272 through inline assembly.
3274 The Xtensa configuration information must be specified prior to
3275 building GCC@. The @file{gcc/config/xtensa/xtensa-config.h} header
3276 file contains the configuration information. If you created your
3277 own Xtensa configuration with the Xtensa Processor Generator, the
3278 downloaded files include a customized copy of this header file,
3279 which you can use to replace the default header file.
3284 @heading @anchor{xtensa-*-linux*}xtensa-*-linux*
3286 This target is for Xtensa systems running GNU/Linux. It supports ELF
3287 shared objects and the GNU C library (glibc). It also generates
3288 position-independent code (PIC) regardless of whether the
3289 @option{-fpic} or @option{-fPIC} options are used. In other
3290 respects, this target is the same as the
3291 @uref{#xtensa-*-elf,,@samp{xtensa-*-elf}} target.
3296 @heading @anchor{windows}Microsoft Windows (32-bit)
3298 A port of GCC 2.95.x is included with the
3299 @uref{http://www.cygwin.com/,,Cygwin environment}.
3301 Current (as of early 2001) snapshots of GCC will build under Cygwin
3302 without modification.
3307 @heading @anchor{os2}OS/2
3309 GCC does not currently support OS/2. However, Andrew Zabolotny has been
3310 working on a generic OS/2 port with pgcc. The current code can be found
3311 at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
3313 An older copy of GCC 2.8.1 is included with the EMX tools available at
3314 @uref{ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/,,
3315 ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/}.
3320 @heading @anchor{older}Older systems
3322 GCC contains support files for many older (1980s and early
3323 1990s) Unix variants. For the most part, support for these systems
3324 has not been deliberately removed, but it has not been maintained for
3325 several years and may suffer from bitrot.
3327 Starting with GCC 3.1, each release has a list of ``obsoleted'' systems.
3328 Support for these systems is still present in that release, but
3329 @command{configure} will fail unless the @option{--enable-obsolete}
3330 option is given. Unless a maintainer steps forward, support for these
3331 systems will be removed from the next release of GCC@.
3333 Support for old systems as hosts for GCC can cause problems if the
3334 workarounds for compiler, library and operating system bugs affect the
3335 cleanliness or maintainability of the rest of GCC@. In some cases, to
3336 bring GCC up on such a system, if still possible with current GCC, may
3337 require first installing an old version of GCC which did work on that
3338 system, and using it to compile a more recent GCC, to avoid bugs in the
3339 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
3340 @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror
3341 sites}. Header bugs may generally be avoided using
3342 @command{fixincludes}, but bugs or deficiencies in libraries and the
3343 operating system may still cause problems.
3345 Support for older systems as targets for cross-compilation is less
3346 problematic than support for them as hosts for GCC; if an enthusiast
3347 wishes to make such a target work again (including resurrecting any of
3348 the targets that never worked with GCC 2, starting from the last CVS
3349 version before they were removed), patches
3350 @uref{../contribute.html,,following the usual requirements} would be
3351 likely to be accepted, since they should not affect the support for more
3354 For some systems, old versions of GNU binutils may also be useful,
3355 and are available from @file{pub/binutils/old-releases} on
3356 @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}.
3358 Some of the information on specific systems above relates to
3359 such older systems, but much of the information
3360 about GCC on such systems (which may no longer be applicable to
3361 current GCC) is to be found in the GCC texinfo manual.
3366 @heading @anchor{elf_targets}all ELF targets (SVR4, Solaris 2, etc.)
3368 C++ support is significantly better on ELF targets if you use the
3369 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
3370 inlines, vtables and template instantiations will be discarded
3379 @uref{./index.html,,Return to the GCC Installation page}
3383 @c ***Old documentation******************************************************
3385 @include install-old.texi
3391 @uref{./index.html,,Return to the GCC Installation page}
3395 @c ***GFDL********************************************************************
3403 @uref{./index.html,,Return to the GCC Installation page}
3407 @c ***************************************************************************
3408 @c Part 6 The End of the Document
3410 @comment node-name, next, previous, up
3411 @node Concept Index, , GNU Free Documentation License, Top
3415 @unnumbered Concept Index