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{i386-@var{any}-isc}
563 @item @samp{i860-@var{any}-bsd}
564 @item @samp{m68k-bull-sysv}
565 @item @samp{m68k-hp-hpux}
566 @item @samp{m68k-sony-bsd}
567 @item @samp{m68k-altos-sysv}
568 @item @samp{m68000-hp-hpux}
569 @item @samp{m68000-att-sysv}
570 @item @samp{@var{any}-lynx-lynxos}
571 @item @samp{mips-@var{any}}
574 On the systems listed above (except for the HP-PA, for ISC on the
575 386, and for @samp{mips-sgi-irix5.*}), if you use the GNU assembler,
576 you should also use the GNU linker (and specify @option{--with-gnu-ld}).
578 @item --with-as=@var{pathname}
580 compiler should use the assembler pointed to by @var{pathname}, rather
581 than the one found by the standard rules to find an assembler, which
586 @file{@var{exec_prefix}/lib/gcc-lib/@var{target}/@var{version}}
587 directory, where @var{exec_prefix} defaults to @var{prefix} which
588 defaults to @file{/usr/local} unless overridden by the
589 @option{--prefix=@var{pathname}} switch described above. @var{target} is the
590 target system triple, such as @samp{sparc-sun-solaris2.7}, and
591 @var{version} denotes the GCC version, such as 3.0.
593 Check operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
596 Note that these rules do not check for the value of @env{PATH}. You may
597 want to use @option{--with-as} if no assembler is installed in the
598 directories listed above, or if you have multiple assemblers installed
599 and want to choose one that is not found by the above rules.
601 @item @anchor{with-gnu-ld}--with-gnu-ld
602 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
606 @item --with-ld=@var{pathname}
608 @option{--with-as}, but for the linker.
611 Specify that stabs debugging
612 information should be used instead of whatever format the host normally
613 uses. Normally GCC uses the same debug format as the host system.
615 On MIPS based systems and on Alphas, you must specify whether you want
616 GCC to create the normal ECOFF debugging format, or to use BSD-style
617 stabs passed through the ECOFF symbol table. The normal ECOFF debug
618 format cannot fully handle languages other than C@. BSD stabs format can
619 handle other languages, but it only works with the GNU debugger GDB@.
621 Normally, GCC uses the ECOFF debugging format by default; if you
622 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
624 No matter which default you choose when you configure GCC, the user
625 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
626 the debug format for a particular compilation.
628 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
629 @option{--with-gas} is used. It selects use of stabs debugging
630 information embedded in COFF output. This kind of debugging information
631 supports C++ well; ordinary COFF debugging information does not.
633 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
634 selects use of stabs debugging information embedded in ELF output. The
635 C++ compiler currently (2.6.0) does not support the DWARF debugging
636 information normally used on 386 SVR4 platforms; stabs provide a
637 workable alternative. This requires gas and gdb, as the normal SVR4
638 tools can not generate or interpret stabs.
640 @item --disable-multilib
641 Specify that multiple target
642 libraries to support different target variants, calling
643 conventions, etc should not be built. The default is to build a
644 predefined set of them.
646 Some targets provide finer-grained control over which multilibs are built
647 (e.g., @option{--disable-softfloat}):
653 fpu, 26bit, underscore, interwork, biendian, nofmult.
656 softfloat, m68881, m68000, m68020.
659 single-float, biendian, softfloat.
661 @item powerpc*-*-*, rs6000*-*-*
662 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
667 @item --enable-threads
668 Specify that the target
669 supports threads. This affects the Objective-C compiler and runtime
670 library, and exception handling for other languages like C++ and Java.
671 On some systems, this is the default.
673 In general, the best (and, in many cases, the only known) threading
674 model available will be configured for use. Beware that on some
675 systems, gcc has not been taught what threading models are generally
676 available for the system. In this case, @option{--enable-threads} is an
677 alias for @option{--enable-threads=single}.
679 @item --disable-threads
680 Specify that threading support should be disabled for the system.
681 This is an alias for @option{--enable-threads=single}.
683 @item --enable-threads=@var{lib}
685 @var{lib} is the thread support library. This affects the Objective-C
686 compiler and runtime library, and exception handling for other languages
687 like C++ and Java. The possibilities for @var{lib} are:
695 Generic MACH thread support, known to work on NeXTSTEP@. (Please note
696 that the file needed to support this configuration, @file{gthr-mach.h}, is
697 missing and thus this setting will cause a known bootstrap failure.)
699 This is an alias for @samp{single}.
701 Generic POSIX thread support.
703 Same as @samp{posix} on arm*-*-linux*, *-*-chorusos* and *-*-freebsd*
704 only. A future release of gcc might remove this alias or extend it
707 RTEMS thread support.
709 Disable thread support, should work for all platforms.
711 Sun Solaris 2 thread support.
713 VxWorks thread support.
715 Microsoft Win32 API thread support.
718 @item --with-cpu=@var{cpu}
719 Specify which cpu variant the
720 compiler should generate code for by default. This is currently
721 only supported on some ports, specifically arm, powerpc, and
722 SPARC@. If configure does not recognize the model name (e.g.@: arm700,
723 603e, or ultrasparc) you provide, please check the configure script
724 for a complete list of supported models.
726 @item --enable-altivec
727 Specify that the target supports AltiVec vector enhancements. This
728 option will adjust the ABI for AltiVec enhancements, as well as generate
729 AltiVec code when appropriate. This option is only available for
732 @item --enable-target-optspace
734 libraries should be optimized for code space instead of code speed.
735 This is the default for the m32r platform.
738 Specify that a user visible @command{cpp} program should not be installed.
740 @item --with-cpp-install-dir=@var{dirname}
741 Specify that the user visible @command{cpp} program should be installed
742 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
744 @item --enable-initfini-array
745 Force the use of sections @code{.init_array} and @code{.fini_array}
746 (instead of @code{.init} and @code{.fini}) for constructors and
747 destructors. Option @option{--disable-initfini-array} has the
748 opposite effect. If neither option is specified, the configure script
749 will try to guess whether the @code{.init_array} and
750 @code{.fini_array} sections are supported and, if they are, use them.
752 @item --enable-maintainer-mode
754 regenerate the GCC master message catalog @file{gcc.pot} are normally
755 disabled. This is because it can only be rebuilt if the complete source
756 tree is present. If you have changed the sources and want to rebuild the
757 catalog, configuring with @option{--enable-maintainer-mode} will enable
758 this. Note that you need a recent version of the @code{gettext} tools
761 @item --enable-version-specific-runtime-libs
763 that runtime libraries should be installed in the compiler specific
764 subdirectory (@file{@var{libsubdir}}) rather than the usual places. In
765 addition, @samp{libstdc++}'s include files will be installed in
766 @file{@var{libsubdir}/include/g++} unless you overruled it by using
767 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
768 particularly useful if you intend to use several versions of GCC in
769 parallel. This is currently supported by @samp{libf2c} and
770 @samp{libstdc++}, and is the default for @samp{libobjc} which cannot be
771 changed in this case.
773 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
774 Specify that only a particular subset of compilers and
775 their runtime libraries should be built. For a list of valid values for
776 @var{langN} you can issue the following command in the
777 @file{gcc} directory of your GCC source tree:@*
779 grep language= */config-lang.in
781 Currently, you can use any of the following:
782 @code{ada}, @code{c}, @code{c++}, @code{f77}, @code{java}, @code{objc}.
783 Building the Ada compiler has special requirements, see below.@*
784 If you do not pass this flag, all languages available in the @file{gcc}
785 sub-tree will be configured. Re-defining @code{LANGUAGES} when calling
786 @samp{make bootstrap} @strong{does not} work anymore, as those
787 language sub-directories might not have been configured!
789 @item --disable-libgcj
790 Specify that the run-time libraries
791 used by GCJ should not be built. This is useful in case you intend
792 to use GCJ with some other run-time, or you're going to install it
793 separately, or it just happens not to build on your particular
794 machine. In general, if the Java front end is enabled, the GCJ
795 libraries will be enabled too, unless they're known to not work on
796 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
797 may need to port it; in this case, before modifying the top-level
798 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
799 you may use @option{--enable-libgcj} to override the default.
802 Specify that the compiler should
803 use DWARF 2 debugging information as the default.
805 @item --enable-win32-registry
806 @itemx --enable-win32-registry=@var{key}
807 @itemx --disable-win32-registry
808 The @option{--enable-win32-registry} option enables Windows-hosted GCC
809 to look up installations paths in the registry using the following key:
812 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
815 @var{key} defaults to GCC version number, and can be overridden by the
816 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
817 who use custom installers are encouraged to provide a different key,
818 perhaps one comprised of vendor name and GCC version number, to
819 avoid conflict with existing installations. This feature is enabled
820 by default, and can be disabled by @option{--disable-win32-registry}
821 option. This option has no effect on the other hosts.
824 Specify that the machine does not have a floating point unit. This
825 option only applies to @samp{m68k-sun-sunos@var{n}} and
826 @samp{m68k-isi-bsd}. On any other system, @option{--nfp} has no effect.
828 @item --enable-checking
829 @itemx --enable-checking=@var{list}
830 When you specify this option, the compiler is built to perform checking
831 of tree node types when referencing fields of that node, and some other
832 internal consistency checks. This does not change the generated code,
833 but adds error checking within the compiler. This will slow down the
834 compiler and may only work properly if you are building the compiler
835 with GCC@. This is on by default when building from CVS or snapshots,
836 but off for releases. More control over the checks may be had by
837 specifying @var{list}; the categories of checks available are
838 @samp{misc}, @samp{tree}, @samp{gc}, @samp{rtl}, @samp{rtlflag} and
840 default when @var{list} is not specified is @samp{misc,tree,gc,rtlflag}; the
841 checks @samp{rtl} and @samp{gcac} are very expensive.
843 @item --enable-coverage
844 @item --enable-coverage=@var{level}
845 With this option, the compiler is built to collect self coverage
846 information, every time it is run. This is for internal development
847 purposes, and only works when the compiler is being built with gcc. The
848 @var{level} argument controls whether the compiler is built optimized or
849 not, values are @samp{opt} and @samp{noopt}. For coverage analysis you
850 want to disable optimization, for performance analysis you want to
851 enable optimization. When coverage is enabled, the default level is
852 without optimization.
856 The @option{--enable-nls} option enables Native Language Support (NLS),
857 which lets GCC output diagnostics in languages other than American
858 English. Native Language Support is enabled by default if not doing a
859 canadian cross build. The @option{--disable-nls} option disables NLS@.
861 @item --with-included-gettext
862 If NLS is enabled, the @option{--with-included-gettext} option causes the build
863 procedure to prefer its copy of GNU @command{gettext}.
866 If NLS is enabled, and if the host lacks @code{gettext} but has the
867 inferior @code{catgets} interface, the GCC build procedure normally
868 ignores @code{catgets} and instead uses GCC's copy of the GNU
869 @code{gettext} library. The @option{--with-catgets} option causes the
870 build procedure to use the host's @code{catgets} in this situation.
872 @item --with-libiconv-prefix=@var{dir}
873 Search for libiconv header files in @file{@var{dir}/include} and
874 libiconv library files in @file{@var{dir}/lib}.
876 @item --with-system-zlib
877 Use installed zlib rather than that included with GCC@. This option
878 only applies if the Java front end is being built.
880 @item --enable-obsolete
881 Enable configuration for an obsoleted system. If you attempt to
882 configure GCC for a system (build, host, or target) which has been
883 obsoleted, and you do not specify this flag, configure will halt with an
886 All support for systems which have been obsoleted in one release of GCC
887 is removed entirely in the next major release, unless someone steps
888 forward to maintain the port.
891 Some options which only apply to building cross compilers:
894 @itemx --with-headers=@var{dir}
895 Specifies that target headers are available when building a cross compiler.
896 The @var{dir} argument specifies a directory which has the target include
897 files. These include files will be copied into the @file{gcc} install
898 directory. @emph{This option with the @var{dir} argument is required} when
899 building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include}
900 doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does
901 pre-exist, the @var{dir} argument may be omitted. @command{fixincludes}
902 will be run on these files to make them compatible with GCC.
904 @itemx --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
905 Specifies a list of directories which contain the target runtime
906 libraries. These libraries will be copied into the @file{gcc} install
907 directory. If the directory list is omitted, this option has no
910 Specifies that @samp{newlib} is
911 being used as the target C library. This causes @code{__eprintf} to be
912 omitted from @file{libgcc.a} on the assumption that it will be provided by
916 Note that each @option{--enable} option has a corresponding
917 @option{--disable} option and that each @option{--with} option has a
918 corresponding @option{--without} option.
925 @uref{./index.html,,Return to the GCC Installation page}
929 @c ***Building****************************************************************
931 @comment node-name, next, previous, up
932 @node Building, Testing, Configuration, Installing GCC
938 @cindex Installing GCC: Building
940 Now that GCC is configured, you are ready to build the compiler and
943 We @strong{highly} recommend that GCC be built using GNU make;
944 other versions may work, then again they might not.
945 GNU make is required for compiling GNAT (the Ada compiler) and the Java
948 (For example, many broken versions of make will fail if you use the
949 recommended setup where @var{objdir} is different from @var{srcdir}.
950 Other broken versions may recompile parts of the compiler when
951 installing the compiler.)
953 Some commands executed when making the compiler may fail (return a
954 nonzero status) and be ignored by @code{make}. These failures, which
955 are often due to files that were not found, are expected, and can safely
958 It is normal to have compiler warnings when compiling certain files.
959 Unless you are a GCC developer, you can generally ignore these warnings
960 unless they cause compilation to fail.
962 On certain old systems, defining certain environment variables such as
963 @env{CC} can interfere with the functioning of @command{make}.
965 If you encounter seemingly strange errors when trying to build the
966 compiler in a directory other than the source directory, it could be
967 because you have previously configured the compiler in the source
968 directory. Make sure you have done all the necessary preparations.
970 If you build GCC on a BSD system using a directory stored in an old System
971 V file system, problems may occur in running @command{fixincludes} if the
972 System V file system doesn't support symbolic links. These problems
973 result in a failure to fix the declaration of @code{size_t} in
974 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
975 that type mismatches occur, this could be the cause.
977 The solution is not to use such a directory for building GCC@.
979 When building from CVS or snapshots, or if you modify parser sources,
980 you need the Bison parser generator installed. Any version 1.25 or
981 later should work; older versions may also work. If you do not modify
982 parser sources, releases contain the Bison-generated files and you do
983 not need Bison installed to build them.
985 When building from CVS or snapshots, or if you modify Texinfo
986 documentation, you need version 4.1 or later of Texinfo installed if you
987 want Info documentation to be regenerated. Releases contain Info
988 documentation pre-built for the unmodified documentation in the release.
990 @section Building a native compiler
992 For a native build issue the command @samp{make bootstrap}. This
993 will build the entire GCC system, which includes the following steps:
997 Build host tools necessary to build the compiler such as texinfo, bison,
1001 Build target tools for use by the compiler such as binutils (bfd,
1002 binutils, gas, gprof, ld, and opcodes)
1003 if they have been individually linked
1004 or moved into the top level GCC source tree before configuring.
1007 Perform a 3-stage bootstrap of the compiler.
1010 Perform a comparison test of the stage2 and stage3 compilers.
1013 Build runtime libraries using the stage3 compiler from the previous step.
1017 If you are short on disk space you might consider @samp{make
1018 bootstrap-lean} instead. This is identical to @samp{make
1019 bootstrap} except that object files from the stage1 and
1020 stage2 of the 3-stage bootstrap of the compiler are deleted as
1021 soon as they are no longer needed.
1023 If you want to save additional space during the bootstrap and in
1024 the final installation as well, you can build the compiler binaries
1025 without debugging information as in the following example. This will save
1026 roughly 40% of disk space both for the bootstrap and the final installation.
1027 (Libraries will still contain debugging information.)
1030 make CFLAGS='-O' LIBCFLAGS='-g -O2' \
1031 LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap
1034 If you wish to use non-default GCC flags when compiling the stage2 and
1035 stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing
1036 @samp{make bootstrap}. Non-default optimization flags are less well
1037 tested here than the default of @samp{-g -O2}, but should still work.
1038 In a few cases, you may find that you need to specify special flags such
1039 as @option{-msoft-float} here to complete the bootstrap; or, if the
1040 native compiler miscompiles the stage1 compiler, you may need to work
1041 around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the
1042 stage1 compiler that were miscompiled, or by using @samp{make
1043 bootstrap4} to increase the number of stages of bootstrap.
1045 If you used the flag @option{--enable-languages=@dots{}} to restrict
1046 the compilers to be built, only those you've actually enabled will be
1047 built. This will of course only build those runtime libraries, for
1048 which the particular compiler has been built. Please note,
1049 that re-defining @env{LANGUAGES} when calling @samp{make bootstrap}
1050 @strong{does not} work anymore!
1052 If the comparison of stage2 and stage3 fails, this normally indicates
1053 that the stage2 compiler has compiled GCC incorrectly, and is therefore
1054 a potentially serious bug which you should investigate and report. (On
1055 a few systems, meaningful comparison of object files is impossible; they
1056 always appear ``different''. If you encounter this problem, you will
1057 need to disable comparison in the @file{Makefile}.)
1059 @section Building a cross compiler
1061 We recommend reading the
1062 @uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ}
1063 for information about building cross compilers.
1065 When building a cross compiler, it is not generally possible to do a
1066 3-stage bootstrap of the compiler. This makes for an interesting problem
1067 as parts of GCC can only be built with GCC@.
1069 To build a cross compiler, we first recommend building and installing a
1070 native compiler. You can then use the native GCC compiler to build the
1071 cross compiler. The installed native compiler needs to be GCC version
1074 Assuming you have already installed a native copy of GCC and configured
1075 your cross compiler, issue the command @command{make}, which performs the
1080 Build host tools necessary to build the compiler such as texinfo, bison,
1084 Build target tools for use by the compiler such as binutils (bfd,
1085 binutils, gas, gprof, ld, and opcodes)
1086 if they have been individually linked or moved into the top level GCC source
1087 tree before configuring.
1090 Build the compiler (single stage only).
1093 Build runtime libraries using the compiler from the previous step.
1096 Note that if an error occurs in any step the make process will exit.
1098 @section Building in parallel
1100 If you have a multiprocessor system you can use @samp{make bootstrap
1101 MAKE="make -j 2" -j 2} or just @samp{make -j 2 bootstrap}
1102 for GNU Make 3.79 and above instead of just @samp{make bootstrap}
1103 when building GCC@. You can use a bigger number instead of two if
1104 you like. In most cases, it won't help to use a number bigger than
1105 the number of processors in your machine.
1107 @section Building the Ada compiler
1109 In order to build GNAT, the Ada compiler, you need a working GNAT
1110 compiler (GNAT version 3.13 or later, or GCC version 3.1 or later),
1111 since the Ada front end is written in Ada (with some
1112 GNAT-specific extensions), and GNU make.
1114 However, you do not need a full installation of GNAT, just the GNAT
1115 binary @file{gnat1}, a copy of @file{gnatbind}, and a compiler driver
1116 which can deal with Ada input (by invoking the @file{gnat1} binary).
1117 You can specify this compiler driver by setting the @env{ADAC}
1118 environment variable at the configure step. @command{configure} can
1119 detect the driver automatically if it has got a common name such as
1120 @command{gcc} or @command{gnatgcc}. Of course, you still need a working
1121 C compiler (the compiler driver can be different or not).
1122 @command{configure} does not test whether the GNAT installation works
1123 and has a sufficiently recent version; if too old a GNAT version is
1124 installed, the build will fail unless @option{--enable-languages} is
1125 used to disable building the Ada front end.
1127 Additional build tools (such as @command{gnatmake}) or a working GNAT
1128 run-time library installation are usually @emph{not} required. However,
1129 if you want to bootstrap the compiler using a minimal version of GNAT,
1130 you have to issue the following commands before invoking @samp{make
1131 bootstrap} (this assumes that you start with an unmodified and consistent
1132 source distribution):
1135 cd @var{srcdir}/gcc/ada
1136 touch treeprs.ads [es]info.h nmake.ad[bs]
1139 At the moment, the GNAT library and several tools for GNAT are not built
1140 by @samp{make bootstrap}. You have to invoke
1141 @samp{make gnatlib_and_tools} in the @file{@var{objdir}/gcc}
1142 subdirectory before proceeding with the next steps.
1144 For example, you can build a native Ada compiler by issuing the
1145 following commands (assuming @command{make} is GNU make):
1149 @var{srcdir}/configure --enable-languages=c,ada
1150 cd @var{srcdir}/gcc/ada
1151 touch treeprs.ads [es]info.h nmake.ad[bs]
1155 make gnatlib_and_tools
1159 Currently, when compiling the Ada front end, you cannot use the parallel
1160 build feature described in the previous section.
1167 @uref{./index.html,,Return to the GCC Installation page}
1171 @c ***Testing*****************************************************************
1173 @comment node-name, next, previous, up
1174 @node Testing, Final install, Building, Installing GCC
1178 @chapter Installing GCC: Testing
1181 @cindex Installing GCC: Testing
1184 Before you install GCC, we encourage you to run the testsuites and to
1185 compare your results with results from a similar configuration that have
1186 been submitted to the
1187 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
1188 This step is optional and may require you to download additional software,
1189 but it can give you confidence in your new GCC installation or point out
1190 problems before you install and start using your new GCC.
1192 First, you must have @uref{download.html,,downloaded the testsuites}.
1193 These are part of the full distribution, but if you downloaded the
1194 ``core'' compiler plus any front ends, you must download the testsuites
1197 Second, you must have the testing tools installed. This includes
1198 a @uref{http://www.gnu.org/software/dejagnu/,,current version of DejaGnu};
1199 dejagnu 1.3 is not sufficient.
1200 It also includes Tcl and Expect; the DejaGnu site has links to these.
1202 Now you may need specific preparations:
1207 The following environment variables may need to be set appropriately, as in
1208 the following example (which assumes that DejaGnu has been installed
1209 under @file{/usr/local}):
1212 TCL_LIBRARY = /usr/local/share/tcl8.0
1213 DEJAGNULIBS = /usr/local/share/dejagnu
1216 On systems such as Cygwin, these paths are required to be actual
1217 paths, not mounts or links; presumably this is due to some lack of
1218 portability in the DejaGnu code.
1220 If the directories where @command{runtest} and @command{expect} were
1221 installed are in the @env{PATH}, it should not be necessary to set these
1222 environment variables.
1226 Finally, you can run the testsuite (which may take a long time):
1228 cd @var{objdir}; make -k check
1231 The testing process will try to test as many components in the GCC
1232 distribution as possible, including the C, C++, Objective-C and Fortran
1233 compilers as well as the C++ and Java runtime libraries.
1235 While running the testsuite, DejaGnu might emit messages resembling
1236 @samp{WARNING: Couldn't find the global config file.} or
1237 @samp{WARNING: Couldn't find tool init file}.
1238 These messages are harmless and do not affect the validity of the tests.
1240 @section How can I run the test suite on selected tests?
1242 As a first possibility to cut down the number of tests that are run it is
1243 possible to use @samp{make check-gcc} or @samp{make check-g++}
1244 in the @file{gcc} subdirectory of the object directory. To further cut down the
1245 tests the following is possible:
1248 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
1251 This will run all @command{gcc} execute tests in the testsuite.
1254 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
1257 This will run the @command{g++} ``old-deja'' tests in the testsuite where the filename
1258 matches @samp{9805*}.
1260 The @file{*.exp} files are located in the testsuite directories of the GCC
1261 source, the most important ones being @file{compile.exp},
1262 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
1263 To get a list of the possible @file{*.exp} files, pipe the
1264 output of @samp{make check} into a file and look at the
1265 @samp{Running @dots{} .exp} lines.
1267 To run only the tests for a library, run @samp{make check} from the
1268 the library's testsuite in a subdirectory of the object directory:
1269 @file{libstdc++-v3/testsuite} or @file{libcgj/testsuite}.
1271 @section Additional testing for Java Class Libraries
1273 The @uref{http://sources.redhat.com/mauve/,,Mauve Project} provides
1274 a suite of tests for the Java Class Libraries. This suite can be run
1275 as part of libgcj testing by placing the Mauve tree within the libjava
1276 testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by
1277 specifying the location of that tree when invoking @samp{make}, as in
1278 @samp{make MAUVEDIR=~/mauve check}.
1280 @section How to interpret test results
1282 After the testsuite has run you'll find various @file{*.sum} and @file{*.log}
1283 files in the testsuite subdirectories. The @file{*.log} files contain a
1284 detailed log of the compiler invocations and the corresponding
1285 results, the @file{*.sum} files summarize the results. These summaries list
1286 all the tests that have been run with a corresponding status code:
1290 PASS: the test passed as expected
1292 XPASS: the test unexpectedly passed
1294 FAIL: the test unexpectedly failed
1296 XFAIL: the test failed as expected
1298 UNSUPPORTED: the test is not supported on this platform
1300 ERROR: the testsuite detected an error
1302 WARNING: the testsuite detected a possible problem
1305 It is normal for some tests to report unexpected failures. At the
1306 current time our testing harness does not allow fine grained control
1307 over whether or not a test is expected to fail. We expect to fix this
1308 problem in future releases.
1311 @section Submitting test results
1313 If you want to report the results to the GCC project, use the
1314 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
1317 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
1318 -m gcc-testresults@@gcc.gnu.org |sh
1321 This script uses the @command{Mail} program to send the results, so
1322 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
1323 prepended to the testsuite summary and should contain any special
1324 remarks you have on your results or your build environment. Please
1325 do not edit the testsuite result block or the subject line, as these
1326 messages are automatically parsed and presented at the
1327 @uref{http://gcc.gnu.org/testresults/,,GCC testresults} web
1328 page. Here you can also gather information on how specific tests
1329 behave on different platforms and compare them with your results. A
1330 few failing testcases are possible even on released versions and you
1331 should look here first if you think your results are unreasonable.
1338 @uref{./index.html,,Return to the GCC Installation page}
1342 @c ***Final install***********************************************************
1344 @comment node-name, next, previous, up
1345 @node Final install, , Testing, Installing GCC
1347 @ifset finalinstallhtml
1349 @chapter Installing GCC: Final installation
1352 Now that GCC has been built (and optionally tested), you can install it with
1354 cd @var{objdir}; make install
1357 We strongly recommend to install into a target directory where there is
1358 no previous version of GCC present.
1360 That step completes the installation of GCC; user level binaries can
1361 be found in @file{@var{prefix}/bin} where @var{prefix} is the value you
1362 specified with the @option{--prefix} to configure (or @file{/usr/local}
1363 by default). (If you specified @option{--bindir}, that directory will
1364 be used instead; otherwise, if you specified @option{--exec-prefix},
1365 @file{@var{exec-prefix}/bin} will be used.) Headers for the C++ and
1366 Java libraries are installed in @file{@var{prefix}/include}; libraries
1367 in @file{@var{libdir}} (normally @file{@var{prefix}/lib}); internal
1368 parts of the compiler in @file{@var{libdir}/gcc-lib}; documentation in
1369 info format in @file{@var{infodir}} (normally @file{@var{prefix}/info}).
1371 If you built a released version of GCC using @samp{make bootstrap} then please
1372 quickly review the build status page for your release, available from
1373 @uref{http://gcc.gnu.org/buildstat.html}.
1374 If your system is not listed for the version of GCC that you built,
1376 @email{gcc@@gcc.gnu.org} indicating
1377 that you successfully built and installed GCC.
1378 Include the following information:
1382 Output from running @file{@var{srcdir}/config.guess}. Do not send us
1383 that file itself, just the one-line output from running it.
1386 The output of @samp{gcc -v} for your newly installed gcc.
1387 This tells us which version of GCC you built and the options you passed to
1391 Whether you enabled all languages or a subset of them. If you used a
1392 full distribution then this information is part of the configure
1393 options in the output of @samp{gcc -v}, but if you downloaded the
1394 ``core'' compiler plus additional front ends then it isn't apparent
1395 which ones you built unless you tell us about it.
1398 If the build was for GNU/Linux, also include:
1401 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
1402 this information should be available from @file{/etc/issue}.
1405 The version of the Linux kernel, available from @samp{uname --version}
1409 The version of glibc you used; for RPM-based systems like Red Hat,
1410 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
1411 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
1413 For other systems, you can include similar information if you think it is
1417 Any other information that you think would be useful to people building
1418 GCC on the same configuration. The new entry in the build status list
1419 will include a link to the archived copy of your message.
1422 We'd also like to know if the
1424 @ref{Specific, host/target specific installation notes}
1427 @uref{specific.html,,host/target specific installation notes}
1429 didn't include your host/target information or if that information is
1430 incomplete or out of date. Send a note to
1431 @email{gcc@@gcc.gnu.org} telling us how the information should be changed.
1433 If you find a bug, please report it following our
1434 @uref{../bugs.html,,bug reporting guidelines}.
1436 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
1437 dvi}. You will need to have @command{texi2dvi} (version at least 4.1)
1438 and @TeX{} installed. This creates a number of @file{.dvi} files in
1439 subdirectories of @file{@var{objdir}}; these may be converted for
1440 printing with programs such as @command{dvips}. You can also
1441 @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the
1442 Free Software Foundation}, though such manuals may not be for the most
1443 recent version of GCC@.
1450 @uref{./index.html,,Return to the GCC Installation page}
1454 @c ***Binaries****************************************************************
1456 @comment node-name, next, previous, up
1457 @node Binaries, Specific, Installing GCC, Top
1461 @chapter Installing GCC: Binaries
1464 @cindex Installing GCC: Binaries
1466 We are often asked about pre-compiled versions of GCC@. While we cannot
1467 provide these for all platforms, below you'll find links to binaries for
1468 various platforms where creating them by yourself is not easy due to various
1471 Please note that we did not create these binaries, nor do we
1472 support them. If you have any problems installing them, please
1473 contact their makers.
1480 @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX};
1483 @uref{http://aixpdslib.seas.ucla.edu,,UCLA Software Library for AIX}.
1487 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}.
1490 Hitachi H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
1491 Development Tools for the Hitachi H8/300[HS] Series}.
1497 @uref{http://hpux.cae.wisc.edu/,,HP-UX Porting Center};
1500 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
1504 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
1505 OpenServer/Unixware}.
1508 Sinix/Reliant Unix---@uref{ftp://ftp.siemens.de/sni/mr/pd/gnu/gcc,,Siemens}.
1511 Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware}.
1514 SGI---@uref{http://freeware.sgi.com/,,SGI Freeware}.
1517 Windows 95, 98, and NT:
1520 The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project;
1522 The @uref{http://www.mingw.org/,,MinGW} project.
1526 @uref{ftp://ftp.thewrittenword.com/packages/free/by-name/,,The
1527 Written Word} offers binaries for Solaris 2.5.1, 2.6, 2.7/SPARC, 2.7/Intel,
1528 IRIX 6.2, 6.5, Digital UNIX 4.0D, HP-UX 10.20, and HP-UX 11.00.
1532 In addition to those specific offerings, you can get a binary
1533 distribution CD-ROM from the
1534 @uref{http://www.fsf.org/order/order.html,,Free Software Foundation}.
1535 It contains binaries for a number of platforms, and
1536 includes not only GCC, but other stuff as well. The current CD does
1537 not contain the latest version of GCC, but it should allow
1538 bootstrapping the compiler. An updated version of that disk is in the
1546 @uref{./index.html,,Return to the GCC Installation page}
1550 @c ***Specific****************************************************************
1552 @comment node-name, next, previous, up
1553 @node Specific, Old, Binaries, Top
1557 @chapter Host/target specific installation notes for GCC
1560 @cindex Specific installation notes
1561 @cindex Target specific installation
1562 @cindex Host specific installation
1563 @cindex Target specific installation notes
1565 Please read this document carefully @emph{before} installing the
1566 GNU Compiler Collection on your machine.
1571 @uref{#alpha*-*-*,,alpha*-*-*}
1573 @uref{#alpha*-dec-osf*,,alpha*-dec-osf*}
1575 @uref{#alphaev5-cray-unicosmk*,,alphaev5-cray-unicosmk*}
1577 @uref{#arc-*-elf,,arc-*-elf}
1579 @uref{#arm-*-aout,,arm-*-aout}
1581 @uref{#arm-*-elf,,arm-*-elf}
1583 @uref{#arm*-*-linux-gnu,,arm*-*-linux-gnu}
1591 @uref{#dsp16xx,,dsp16xx}
1593 @uref{#*-*-freebsd*,,*-*-freebsd*}
1595 @uref{#h8300-hms,,h8300-hms}
1597 @uref{#hppa*-hp-hpux*,,hppa*-hp-hpux*}
1599 @uref{#hppa*-hp-hpux9,,hppa*-hp-hpux9}
1601 @uref{#hppa*-hp-hpux10,,hppa*-hp-hpux10}
1603 @uref{#hppa*-hp-hpux11,,hppa*-hp-hpux11}
1605 @uref{#i370-*-*,,i370-*-*}
1607 @uref{#*-*-linux-gnu,,*-*-linux-gnu}
1609 @uref{#ix86-*-linux*aout,,i?86-*-linux*aout}
1611 @uref{#ix86-*-linux*,,i?86-*-linux*}
1613 @uref{#ix86-*-sco,,i?86-*-sco}
1615 @uref{#ix86-*-sco3.2v4,,i?86-*-sco3.2v4}
1617 @uref{#ix86-*-sco3.2v5*,,i?86-*-sco3.2v5*}
1619 @uref{#ix86-*-udk,,i?86-*-udk}
1621 @uref{#ix86-*-esix,,i?86-*-esix}
1623 @uref{#ia64-*-linux,,ia64-*-linux}
1625 @uref{#*-lynx-lynxos,,*-lynx-lynxos}
1627 @uref{#*-ibm-aix*,,*-ibm-aix*}
1629 @uref{#ip2k-*-elf,,ip2k-*-elf}
1631 @uref{#m32r-*-elf,,m32r-*-elf}
1633 @uref{#m68000-hp-bsd,,m68000-hp-bsd}
1635 @uref{#m6811-elf,,m6811-elf}
1637 @uref{#m6812-elf,,m6812-elf}
1639 @uref{#m68k-att-sysv,,m68k-att-sysv}
1641 @uref{#m68k-crds-unos,,m68k-crds-unos}
1643 @uref{#m68k-hp-hpux,,m68k-hp-hpux}
1645 @uref{#m68k-ncr-*,,m68k-ncr-*}
1647 @uref{#m68k-sun,,m68k-sun}
1649 @uref{#m68k-sun-sunos4.1.1,,m68k-sun-sunos4.1.1}
1651 @uref{#mips-*-*,,mips-*-*}
1653 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
1655 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
1657 @uref{#powerpc*-*-*,,powerpc*-*-*, powerpc-*-sysv4}
1659 @uref{#powerpc-*-darwin*,,powerpc-*-darwin*}
1661 @uref{#powerpc-*-elf,,powerpc-*-elf, powerpc-*-sysv4}
1663 @uref{#powerpc-*-linux-gnu*,,powerpc-*-linux-gnu*}
1665 @uref{#powerpc-*-netbsd*,,powerpc-*-netbsd*}
1667 @uref{#powerpc-*-eabiaix,,powerpc-*-eabiaix}
1669 @uref{#powerpc-*-eabisim,,powerpc-*-eabisim}
1671 @uref{#powerpc-*-eabi,,powerpc-*-eabi}
1673 @uref{#powerpcle-*-elf,,powerpcle-*-elf, powerpcle-*-sysv4}
1675 @uref{#powerpcle-*-eabisim,,powerpcle-*-eabisim}
1677 @uref{#powerpcle-*-eabi,,powerpcle-*-eabi}
1679 @uref{#powerpcle-*-winnt,,powerpcle-*-winnt, powerpcle-*-pe}
1681 @uref{#s390-*-linux*,,s390-*-linux*}
1683 @uref{#s390x-*-linux*,,s390x-*-linux*}
1685 @uref{#*-*-solaris2*,,*-*-solaris2*}
1687 @uref{#sparc-sun-solaris2*,,sparc-sun-solaris2*}
1689 @uref{#sparc-sun-solaris2.7,,sparc-sun-solaris2.7}
1691 @uref{#sparc-sun-sunos4*,,sparc-sun-sunos4*}
1693 @uref{#sparc-unknown-linux-gnulibc1,,sparc-unknown-linux-gnulibc1}
1695 @uref{#sparc-*-linux*,,sparc-*-linux*}
1697 @uref{#sparc64-*-*,,sparc64-*-*}
1699 @uref{#sparcv9-*-solaris2*,,sparcv9-*-solaris2*}
1701 @uref{#*-*-sysv*,,*-*-sysv*}
1703 @uref{#vax-dec-ultrix,,vax-dec-ultrix}
1705 @uref{#xtensa-*-elf,,xtensa-*-elf}
1707 @uref{#xtensa-*-linux*,,xtensa-*-linux*}
1709 @uref{#windows,,Microsoft Windows}
1713 @uref{#older,,Older systems}
1718 @uref{#elf_targets,,all ELF targets} (SVR4, Solaris 2, etc.)
1724 <!-- -------- host/target specific issues start here ---------------- -->
1727 @heading @anchor{alpha*-*-*}alpha*-*-*
1729 This section contains general configuration information for all
1730 alpha-based platforms using ELF (in particular, ignore this section for
1731 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
1732 section, please read all other sections that match your target.
1734 We require binutils 2.11.2 or newer.
1735 Previous binutils releases had a number of problems with DWARF 2
1736 debugging information, not the least of which is incorrect linking of
1742 @heading @anchor{alpha*-dec-osf*}alpha*-dec-osf*
1743 Systems using processors that implement the DEC Alpha architecture and
1744 are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
1745 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
1747 As of GCC 3.2, versions before @code{alpha*-dec-osf4} are no longer
1748 supported. (These are the versions which identify themselves as DEC
1751 In Digital Unix V4.0, virtual memory exhausted bootstrap failures
1752 may be fixed by configuring with @option{--with-gc=simple},
1753 reconfiguring Kernel Virtual Memory and Swap parameters
1754 per the @command{/usr/sbin/sys_check} Tuning Suggestions,
1755 or applying the patch in
1756 @uref{http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html}.
1758 In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
1759 currently (2001-06-13) work with @command{mips-tfile}. As a workaround,
1760 we need to use the old assembler, invoked via the barely documented
1761 @option{-oldas} option. To bootstrap GCC, you either need to use the
1765 % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
1768 or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
1771 % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
1774 As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld}
1775 are supported on Tru64 UNIX, so you must not configure GCC with
1776 @option{--with-gnu-as} or @option{--with-gnu-ld}.
1778 The @option{--enable-threads} options isn't supported yet. A patch is
1779 in preparation for a future release.
1781 GCC writes a @samp{.verstamp} directive to the assembler output file
1782 unless it is built as a cross-compiler. It gets the version to use from
1783 the system header file @file{/usr/include/stamp.h}. If you install a
1784 new version of DEC Unix, you should rebuild GCC to pick up the new version
1787 Note that since the Alpha is a 64-bit architecture, cross-compilers from
1788 32-bit machines will not generate code as efficient as that generated
1789 when the compiler is running on a 64-bit machine because many
1790 optimizations that depend on being able to represent a word on the
1791 target in an integral value on the host cannot be performed. Building
1792 cross-compilers on the Alpha for 32-bit machines has only been tested in
1793 a few cases and may not work properly.
1795 @code{make compare} may fail on old versions of DEC Unix unless you add
1796 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
1797 assembler input file is stored in the object file, and that makes
1798 comparison fail if it differs between the @code{stage1} and
1799 @code{stage2} compilations. The option @option{-save-temps} forces a
1800 fixed name to be used for the assembler input file, instead of a
1801 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
1802 unless the comparisons fail without that option. If you add
1803 @option{-save-temps}, you will have to manually delete the @samp{.i} and
1804 @samp{.s} files after each series of compilations.
1806 GCC now supports both the native (ECOFF) debugging format used by DBX
1807 and GDB and an encapsulated STABS format for use only with GDB@. See the
1808 discussion of the @option{--with-stabs} option of @file{configure} above
1809 for more information on these formats and how to select them.
1811 There is a bug in DEC's assembler that produces incorrect line numbers
1812 for ECOFF format when the @samp{.align} directive is used. To work
1813 around this problem, GCC will not emit such alignment directives
1814 while writing ECOFF format debugging information even if optimization is
1815 being performed. Unfortunately, this has the very undesirable
1816 side-effect that code addresses when @option{-O} is specified are
1817 different depending on whether or not @option{-g} is also specified.
1819 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
1820 DBX@. DEC is now aware of this problem with the assembler and hopes to
1821 provide a fix shortly.
1826 @heading @anchor{alphaev5-cray-unicosmk*}alphaev5-cray-unicosmk*
1827 Cray T3E systems running Unicos/Mk.
1829 This port is incomplete and has many known bugs. We hope to improve the
1830 support for this target soon. Currently, only the C front end is supported,
1831 and it is not possible to build parallel applications. Cray modules are not
1832 supported; in particular, Craylibs are assumed to be in
1833 @file{/opt/ctl/craylibs/craylibs}.
1835 You absolutely @strong{must} use GNU make on this platform. Also, you
1836 need to tell GCC where to find the assembler and the linker. The
1837 simplest way to do so is by providing @option{--with-as} and
1838 @option{--with-ld} to @file{configure}, e.g.@:
1841 configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld \
1842 --enable-languages=c
1845 The comparison test during @samp{make bootstrap} fails on Unicos/Mk
1846 because the assembler inserts timestamps into object files. You should
1847 be able to work around this by doing @samp{make all} after getting this
1853 @heading @anchor{arc-*-elf}arc-*-elf
1854 Argonaut ARC processor.
1855 This configuration is intended for embedded systems.
1860 @heading @anchor{arm-*-aout}arm-*-aout
1861 Advanced RISC Machines ARM-family processors. These are often used in
1862 embedded applications. There are no standard Unix configurations.
1863 This configuration corresponds to the basic instruction sequences and will
1864 produce @file{a.out} format object modules.
1866 You may need to make a variant of the file @file{arm.h} for your particular
1872 @heading @anchor{arm-*-elf}arm-*-elf
1873 This configuration is intended for embedded systems.
1878 @heading @anchor{arm*-*-linux-gnu}arm*-*-linux-gnu
1880 We require GNU binutils 2.10 or newer.
1885 @heading @anchor{avr}avr
1887 ATMEL AVR-family micro controllers. These are used in embedded
1888 applications. There are no standard Unix configurations.
1890 @xref{AVR Options,, AVR Options, gcc, Using and Porting the GNU Compiler
1894 See ``AVR Options'' in the main manual
1896 for the list of supported MCU types.
1898 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
1900 Further installation notes and other useful information about AVR tools
1901 can also be obtained from:
1905 @uref{http://www.openavr.org,,http://www.openavr.org}
1907 @uref{http://home.overta.ru/users/denisc,,http://home.overta.ru/users/denisc}
1909 @uref{http://www.amelek.gda.pl/avr,,http://www.amelek.gda.pl/avr}
1912 We @emph{strongly} recommend using binutils 2.13 or newer.
1914 The following error:
1916 Error: register required
1919 indicates that you should upgrade to a newer version of the binutils.
1924 @heading @anchor{c4x}c4x
1926 Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal
1927 Processors. These are used in embedded applications. There are no
1928 standard Unix configurations.
1930 @xref{TMS320C3x/C4x Options,, TMS320C3x/C4x Options, gcc, Using and
1931 Porting the GNU Compiler Collection (GCC)},
1934 See ``TMS320C3x/C4x Options'' in the main manual
1936 for the list of supported MCU types.
1938 GCC can be configured as a cross compiler for both the C3x and C4x
1939 architectures on the same system. Use @samp{configure --target=c4x
1940 --enable-languages="c,c++"} to configure.
1943 Further installation notes and other useful information about C4x tools
1944 can also be obtained from:
1948 @uref{http://www.elec.canterbury.ac.nz/c4x/,,http://www.elec.canterbury.ac.nz/c4x/}
1954 @heading @anchor{cris}CRIS
1956 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
1957 series. These are used in embedded applications.
1960 @xref{CRIS Options,, CRIS Options, gcc, Using and Porting the GNU Compiler
1964 See ``CRIS Options'' in the main manual
1966 for a list of CRIS-specific options.
1968 There are a few different CRIS targets:
1970 @item cris-axis-aout
1971 Old target. Includes a multilib for the @samp{elinux} a.out-based
1972 target. No multilibs for newer architecture variants.
1974 Mainly for monolithic embedded systems. Includes a multilib for the
1975 @samp{v10} core used in @samp{ETRAX 100 LX}.
1976 @item cris-axis-linux-gnu
1977 A GNU/Linux port for the CRIS architecture, currently targeting
1978 @samp{ETRAX 100 LX} by default.
1981 For @code{cris-axis-aout} and @code{cris-axis-elf} you need binutils 2.11
1982 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
1984 Pre-packaged tools can be obtained from
1985 @uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More
1986 information about this platform is available at
1987 @uref{http://developer.axis.com/}.
1992 @heading @anchor{dos}DOS
1994 Please have a look at our @uref{binaries.html,,binaries page}.
1996 You cannot install GCC by itself on MSDOS; it will not compile under
1997 any MSDOS compiler except itself. You need to get the complete
1998 compilation package DJGPP, which includes binaries as well as sources,
1999 and includes all the necessary compilation tools and libraries.
2004 @heading @anchor{dsp16xx}dsp16xx
2005 A port to the AT&T DSP1610 family of processors.
2010 @heading @anchor{*-*-freebsd*}*-*-freebsd*
2012 The version of binutils installed in @file{/usr/bin} is known to work unless
2013 otherwise specified in any per-architecture notes. However, binutils
2014 2.12.1 or greater is known to improve overall testsuite results.
2016 FreeBSD 1 is no longer supported in GCC 3.2.
2018 For FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
2019 configuration support and files as shipped with GCC 2.95 are still in
2020 place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
2021 it is unknown which version of binutils was used (it is assumed that it
2022 was the system copy in @file{/usr/bin}) and C++ EH failures were noted.
2024 For FreeBSD using the ELF file format: DWARF 2 debugging is now the
2025 default for all CPU architectures. It had been the default on
2026 FreeBSD/alpha since its inception. You may use @option{-gstabs} instead
2027 of @option{-g}, if you really want the old debugging format. There are
2028 no known issues with mixing object files and libraries with different
2029 debugging formats. Otherwise, this release of GCC should now match more
2030 of the configuration used in the stock FreeBSD configuration of GCC. In
2031 particular, @option{--enable-threads} is now configured by default.
2032 However, as a general user, do not attempt to replace the system
2033 compiler with this release. Known to bootstrap and check with good
2034 results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4, 4.5-STABLE and 5-CURRENT@.
2036 In principle, @option{--enable-threads} is now compatible with
2037 @option{--enable-libgcj} on FreeBSD@. However, it has only been built
2038 and tested on @samp{i386-*-freebsd4.5} and @samp{alpha-*-freebsd5.0}.
2040 library may be incorrectly built (symbols are missing at link time).
2041 There is a rare timing-based startup hang (probably involves an
2042 assupmtion about the thread library). Multi-threaded boehm-gc (required for
2043 libjava) exposes severe threaded signal-handling bugs on FreeBSD before
2044 4.5-RELEASE. The alpha port may not fully bootstrap without some manual
2045 intervention: @command{gcjh} will crash with a floating-point exception while
2046 generating @file{java/lang/Double.h} (just copy the version built on
2047 @samp{i386-*-freebsd*} and rerun the top-level @command{gmake} with no
2049 should properly complete the bootstrap). Other CPU architectures
2050 supported by FreeBSD will require additional configuration tuning in, at
2051 the very least, both boehm-gc and libffi.
2053 Shared @file{libgcc_s.so} is now built and installed by default.
2058 @heading @anchor{h8300-hms}h8300-hms
2059 Hitachi H8/300 series of processors.
2061 Please have a look at our @uref{binaries.html,,binaries page}.
2063 The calling convention and structure layout has changed in release 2.6.
2064 All code must be recompiled. The calling convention now passes the
2065 first three arguments in function calls in registers. Structures are no
2066 longer a multiple of 2 bytes.
2071 @heading @anchor{hppa*-hp-hpux*}hppa*-hp-hpux*
2073 We @emph{highly} recommend using gas/binutils 2.8 or newer on all hppa
2074 platforms; you may encounter a variety of problems when using the HP
2077 Specifically, @option{-g} does not work on HP-UX (since that system
2078 uses a peculiar debugging format which GCC does not know about), unless you
2079 use GAS and GDB and configure GCC with the
2080 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
2081 @option{--with-as=@dots{}} options.
2083 If you wish to use the pa-risc 2.0 architecture support with a 32-bit
2084 runtime, you must use either the HP assembler, gas/binutils 2.11 or newer,
2086 @uref{ftp://sources.redhat.com/pub/binutils/snapshots,,snapshot of gas}.
2088 There are two default scheduling models for instructions. These are
2089 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
2090 architecture specified for the target machine when configuring.
2091 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
2092 the target is a @samp{hppa1*} machine.
2094 The PROCESSOR_8000 model is not well suited to older processors. Thus,
2095 it is important to completely specify the machine architecture when
2096 configuring if you want a model other than PROCESSOR_8000. The macro
2097 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
2098 default scheduling model is desired.
2100 More specific information to @samp{hppa*-hp-hpux*} targets follows.
2105 @heading @anchor{hppa*-hp-hpux9}hppa*-hp-hpux9
2107 The HP assembler has major problems on this platform. We've tried to work
2108 around the worst of the problems. However, those workarounds may be causing
2109 linker crashes in some circumstances; the workarounds also probably prevent
2110 shared libraries from working. Use the GNU assembler to avoid these problems.
2113 The configuration scripts for GCC will also trigger a bug in the hpux9
2114 shell. To avoid this problem set @env{CONFIG_SHELL} to @file{/bin/ksh}
2115 and @env{SHELL} to @file{/bin/ksh} in your environment.
2121 @heading @anchor{hppa*-hp-hpux10}hppa*-hp-hpux10
2123 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
2124 @code{PHCO_19798} from HP@. HP has two sites which provide patches free of
2130 <a href="http://us-support.external.hp.com">US, Canada, Asia-Pacific, and
2134 @uref{http://us-support.external.hp.com,,}US, Canada, Asia-Pacific, and
2138 @uref{http://europe-support.external.hp.com,,Europe}
2141 The HP assembler on these systems is much better than the hpux9 assembler,
2142 but still has some problems. Most notably the assembler inserts timestamps
2143 into each object file it creates, causing the 3-stage comparison test to fail
2144 during a @samp{make bootstrap}. You should be able to continue by
2145 saying @samp{make all} after getting the failure from @samp{make
2152 @heading @anchor{hppa*-hp-hpux11}hppa*-hp-hpux11
2154 GCC 3.0 and up support HP-UX 11. On 64-bit capable systems, there
2155 are two distinct ports. The @samp{hppa2.0w-hp-hpux11*} port generates
2156 code for the 32-bit pa-risc runtime architecture. It uses the HP
2157 linker and is currently the default selected by config.guess. The
2158 optional @samp{hppa64-hp-hpux11*} port generates 64-bit code for the
2159 pa-risc 2.0 architecture. It must be explicitly selected using the
2160 @samp{--host=hppa64-hp-hpux11*} configure option. Different prefixes
2161 must be used if both ports are to be installed on the same system.
2163 You must use GNU binutils 2.11 or above with the 32-bit port. Thread
2164 support is not currently implemented, so @option{--enable-threads} does
2168 @item @uref{http://gcc.gnu.org/ml/gcc-prs/2002-01/msg00551.html}
2169 @item @uref{http://gcc.gnu.org/ml/gcc-bugs/2002-01/msg00663.html}
2172 GCC 2.95.x is not supported under HP-UX 11 and cannot be used to
2173 compile GCC 3.0 and up. Refer to @uref{binaries.html,,binaries} for
2174 information about obtaining precompiled GCC binaries for HP-UX.
2176 GNU binutils 2.13 or later is recommended with the 64-bit port.
2177 The HP assembler has many limitations and is not recommended. For
2178 example, it does not support weak symbols or alias definitions.
2179 As a result, explicit template instantiations are required when
2180 using C++. Either the HP or GNU linker can be used but it may be
2181 necessary to use the GNU linker when dwarf2 exception support is
2184 There are several possible approaches to building the distribution.
2185 Binutils can be built first using the HP tools. Then, the GCC
2186 distribution can be built. The second approach is to build GCC
2187 first using the HP tools, then build binutils, then rebuild GCC.
2188 There have been problems with various binary distributions, so
2189 it is best not to start from a binary distribution.
2191 When starting with a HP compiler, it is preferable to use the ANSI
2192 compiler as the bundled compiler only supports traditional C.
2193 Bootstrapping with the bundled compiler is tested infrequently and
2194 problems often arise because of the subtle differences in semantics
2195 between traditional and ISO C.
2197 This port still is undergoing significant development.
2202 @heading @anchor{i370-*-*}i370-*-*
2203 This port is very preliminary and has many known bugs. We hope to
2204 have a higher-quality port for this machine soon.
2209 @heading @anchor{*-*-linux-gnu}*-*-linux-gnu
2211 If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install
2212 out-of-the-box. You'll get compile errors while building @samp{libstdc++}.
2213 The patch @uref{glibc-2.2.patch,,glibc-2.2.patch}, that is to be
2214 applied in the GCC source tree, fixes the compatibility problems.
2223 Currently Glibc 2.2.3 (and older releases) and GCC 3.0 are out of sync
2224 since the latest exception handling changes for GCC@. Compiling glibc
2225 with GCC 3.0 will give a binary incompatible glibc and therefore cause
2226 lots of problems and might make your system completly unusable. This
2227 will definitly need fixes in glibc but might also need fixes in GCC@. We
2228 strongly advise to wait for glibc 2.2.4 and to read the release notes of
2229 glibc 2.2.4 whether patches for GCC 3.0 are needed. You can use glibc
2230 2.2.3 with GCC 3.0, just do not try to recompile it.
2235 @heading @anchor{ix86-*-linux*aout}i?86-*-linux*aout
2236 Use this configuration to generate @file{a.out} binaries on Linux-based
2237 GNU systems. This configuration is being superseded. You must use
2238 gas/binutils version 2.5.2 or later.
2243 @heading @anchor{ix86-*-linux*}i?86-*-linux*
2245 You will need binutils 2.9.1.0.15 or newer for exception handling to work.
2247 If you receive Signal 11 errors when building on GNU/Linux, then it is
2248 possible you have a hardware problem. Further information on this can be
2249 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
2254 @heading @anchor{ix86-*-sco}i?86-*-sco
2255 Compilation with RCC is recommended. Also, it may be a good idea to
2256 link with GNU malloc instead of the malloc that comes with the system.
2261 @heading @anchor{ix86-*-sco3.2v4}i?86-*-sco3.2v4
2262 Use this configuration for SCO release 3.2 version 4.
2267 @heading @anchor{ix86-*-sco3.2v5*}i?86-*-sco3.2v5*
2268 Use this for the SCO OpenServer Release 5 family of operating systems.
2270 Unlike earlier versions of GCC, the ability to generate COFF with this
2271 target is no longer provided.
2273 Earlier versions of GCC emitted DWARF 1 when generating ELF to allow
2274 the system debugger to be used. That support was too burdensome to
2275 maintain. GCC now emits only DWARF 2 for this target. This means you
2276 may use either the UDK debugger or GDB to debug programs built by this
2279 Use of the @option{-march=pentiumpro} flag can result in
2280 unrecognized opcodes when using the native assembler on OS versions before
2281 5.0.6. (Support for P6 opcodes was added to the native ELF assembler in
2282 that version.) While it's rather rare to see these emitted by GCC yet,
2283 errors of the basic form:
2286 /usr/tmp/ccaNlqBc.s:22:unknown instruction: fcomip
2287 /usr/tmp/ccaNlqBc.s:50:unknown instruction: fucomip
2290 are symptoms of this problem. You may work around this by not
2291 building affected files with that flag, by using the GNU assembler, or
2292 by using the assembler provided with the current version of the OS@.
2293 Users of GNU assembler should see the note below for hazards on doing
2296 The native SCO assembler that is provided with the OS at no
2297 charge is normally required. If, however, you must be able to use
2298 the GNU assembler (perhaps you're compiling code with asms that
2299 require GAS syntax) you may configure this package using the flags
2300 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You must
2301 use a recent version of GNU binutils; versions past 2.9.1 seem to work
2304 In general, the @option{--with-gnu-as} option isn't as well tested
2305 as the native assembler.
2307 Look in @file{gcc/config/i386/sco5.h} (search for ``messy'') for
2308 additional OpenServer-specific flags.
2310 Systems based on OpenServer before 5.0.4 (@samp{uname -X}
2311 will tell you what you're running) require TLS597 from
2312 @uref{ftp://ftp.sco.com/TLS/,,ftp://ftp.sco.com/TLS/}
2313 for C++ constructors and destructors to work right.
2315 The system linker in (at least) 5.0.4 and 5.0.5 will sometimes
2316 do the wrong thing for a construct that GCC will emit for PIC
2317 code. This can be seen as execution testsuite failures when using
2318 @option{-fPIC} on @file{921215-1.c}, @file{931002-1.c}, @file{nestfunc-1.c}, and @file{gcov-1.c}.
2319 For 5.0.5, an updated linker that will cure this problem is
2320 available. You must install both
2321 @uref{ftp://ftp.sco.com/Supplements/rs505a/,,ftp://ftp.sco.com/Supplements/rs505a/}
2322 and @uref{ftp://ftp.sco.com/SLS/,,OSS499A}.
2324 The dynamic linker in OpenServer 5.0.5 (earlier versions may show
2325 the same problem) aborts on certain G77-compiled programs. It's particularly
2326 likely to be triggered by building Fortran code with the @option{-fPIC} flag.
2327 Although it's conceivable that the error could be triggered by other
2328 code, only G77-compiled code has been observed to cause this abort.
2329 If you are getting core dumps immediately upon execution of your
2330 G77 program---and especially if it's compiled with @option{-fPIC}---try applying
2331 @uref{sco_osr5_g77.patch,,@file{sco_osr5_g77.patch}} to your @samp{libf2c} and
2333 Affected faults, when analyzed in a debugger, will show a stack
2334 backtrace with a fault occurring in @code{rtld()} and the program
2335 running as @file{/usr/lib/ld.so.1}. This problem has been reported to SCO
2336 engineering and will hopefully be addressed in later releases.
2342 @heading @anchor{ix86-*-udk}i?86-*-udk
2344 This target emulates the SCO Universal Development Kit and requires that
2345 package be installed. (If it is installed, you will have a
2346 @file{/udk/usr/ccs/bin/cc} file present.) It's very much like the
2347 @samp{i?86-*-unixware7*} target
2348 but is meant to be used when hosting on a system where UDK isn't the
2349 default compiler such as OpenServer 5 or Unixware 2. This target will
2350 generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
2351 with the same warnings and caveats as the SCO UDK@.
2353 This target is a little tricky to build because we have to distinguish
2354 it from the native tools (so it gets headers, startups, and libraries
2355 from the right place) while making the tools not think we're actually
2356 building a cross compiler. The easiest way to do this is with a configure
2360 CC=/udk/usr/ccs/bin/cc @var{/your/path/to}/gcc/configure \
2361 --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-
2364 @emph{You should substitute @samp{i686} in the above command with the appropriate
2365 processor for your host.}
2367 After the usual @samp{make bootstrap} and
2368 @samp{make install}, you can then access the UDK-targeted GCC
2369 tools by adding @command{udk-} before the commonly known name. For
2370 example, to invoke the C compiler, you would use @command{udk-gcc}.
2371 They will coexist peacefully with any native-target GCC tools you may
2378 @heading @anchor{ia64-*-linux}ia64-*-linux
2379 IA-64 processor (also known as IPF, or Itanium Processor Family)
2382 The toolchain is not completely finished, so requirements will continue
2384 GCC 3.0.1 and later require glibc 2.2.4.
2385 GCC 3.0.2 requires binutils from 2001-09-05 or later.
2386 GCC 3.0.1 requires binutils 2.11.1 or later.
2388 None of the following versions of GCC has an ABI that is compatible
2389 with any of the other versions in this list, with the exception that
2390 Red Hat 2.96 and Trillian 000171 are compatible with each other:
2391 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
2392 This primarily affects C++ programs and programs that create shared libraries.
2393 Because of these ABI incompatibilities, GCC 3.0.2 is not recommended for
2394 user programs on GNU/Linux systems built using earlier compiler releases.
2395 GCC 3.0.2 is recommended for compiling linux, the kernel.
2396 GCC 3.0.2 is believed to be fully ABI compliant, and hence no more major
2397 ABI changes are expected.
2402 @heading @anchor{*-lynx-lynxos}*-lynx-lynxos
2403 LynxOS 2.2 and earlier comes with GCC 1.x already installed as
2404 @file{/bin/gcc}. You should compile with this instead of @file{/bin/cc}.
2405 You can tell GCC to use the GNU assembler and linker, by specifying
2406 @samp{--with-gnu-as --with-gnu-ld} when configuring. These will produce
2407 COFF format object files and executables; otherwise GCC will use the
2408 installed tools, which produce @file{a.out} format executables.
2412 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
2414 @heading @anchor{*-ibm-aix*}*-ibm-aix*
2416 AIX Make frequently has problems with GCC makefiles. GNU Make 3.76 or
2417 newer is recommended to build on this platform.
2419 Errors involving @code{alloca} when building GCC generally are due
2420 to an incorrect definition of @code{CC} in the Makefile or mixing files
2421 compiled with the native C compiler and GCC@. During the stage1 phase of
2422 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
2423 (not @command{xlc}). Once @command{configure} has been informed of
2424 @command{xlc}, one needs to use @samp{make distclean} to remove the
2425 configure cache files and ensure that @env{CC} environment variable
2426 does not provide a definition that will confuse @command{configure}.
2427 If this error occurs during stage2 or later, then the problem most likely
2428 is the version of Make (see above).
2430 The GNU Assembler incorrectly reports that it supports WEAK symbols on
2431 AIX which causes GCC to try to utilize weak symbol functionality although
2432 it is not supported on the platform. The native @command{as} and
2433 @command{ld} still are recommended. The native AIX tools do
2434 interoperate with GCC@.
2436 Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
2437 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1).
2439 @samp{libstdc++} in GCC 3.2 increments the major version number of the
2440 shared object and GCC installation places the @file{libstdc++.a}
2441 shared library in a common location which will overwrite the GCC 3.1
2442 version of the shared library. Applications either need to be
2443 re-linked against the new shared library or the GCC 3.1 version of the
2444 @samp{libstdc++} shared object needs to be available to the AIX
2445 runtime loader. The GCC 3.1 @samp{libstdc++.so.4} shared object can
2446 be installed for runtime dynamic loading using the following steps to
2447 set the @samp{F_LOADONLY} flag in the shared object for @emph{each}
2448 multilib @file{libstdc++.a} installed:
2450 Extract the shared object from each the GCC 3.1 @file{libstdc++.a}
2453 % ar -x libstdc++.a libstdc++.so.4
2456 Enable the @samp{F_LOADONLY} flag so that the shared object will be
2457 available for runtime dynamic loading, but not linking:
2459 % strip -e libstdc++.so.4
2462 Archive the runtime-only shared object in the GCC 3.2
2463 @file{libstdc++.a} archive:
2465 % ar -q libstdc++.a libstdc++.so.4
2468 Linking executables and shared libraries may produce warnings of
2469 duplicate symbols. The assembly files generated by GCC for AIX always
2470 have included multiple symbol definitions for certain global variable
2471 and function declarations in the original program. The warnings should
2472 not prevent the linker from producing a correct library or runnable
2475 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
2476 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
2477 to parse archive libraries did not handle the new format correctly.
2478 These routines are used by GCC and result in error messages during
2479 linking such as ``not a COFF file''. The version of the routines shipped
2480 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
2481 option of the archive command may be used to create archives of 32-bit
2482 objects using the original ``small format''. A correct version of the
2483 routines is shipped with AIX 4.3.2 and above.
2485 Some versions of the AIX binder (linker) can fail with a relocation
2486 overflow severe error when the @option{-bbigtoc} option is used to link
2487 GCC-produced object files into an executable that overflows the TOC@. A fix
2488 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
2489 available from IBM Customer Support and from its
2490 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2491 website as PTF U455193.
2493 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
2494 with a segmentation fault when invoked by any version of GCC@. A fix for
2495 APAR IX87327 is available from IBM Customer Support and from its
2496 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2497 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
2499 The initial assembler shipped with AIX 4.3.0 generates incorrect object
2500 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
2501 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
2502 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2503 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
2505 AIX provides National Language Support (NLS)@. Compilers and assemblers
2506 use NLS to support locale-specific representations of various data
2507 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
2508 separating decimal fractions). There have been problems reported where
2509 GCC does not produce the same floating-point formats that the assembler
2510 expects. If one encounters this problem, set the @env{LANG}
2511 environment variable to @samp{C} or @samp{En_US}.
2513 By default, GCC for AIX 4.1 and above produces code that can be used on
2514 both Power or PowerPC processors.
2516 A default can be specified with the @option{-mcpu=@var{cpu_type}}
2517 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
2522 @heading @anchor{ip2k-*-elf}ip2k-*-elf
2523 Ubicom IP2022 micro controller.
2524 This configuration is intended for embedded systems.
2525 There are no standard Unix configurations.
2527 Use @samp{configure --target=ip2k-elf --enable-languages=c} to configure GCC@.
2532 @heading @anchor{m32r-*-elf}m32r-*-elf
2533 Mitsubishi M32R processor.
2534 This configuration is intended for embedded systems.
2539 @heading @anchor{m68000-hp-bsd}m68000-hp-bsd
2540 HP 9000 series 200 running BSD@. Note that the C compiler that comes
2541 with this system cannot compile GCC; contact @email{law@@cygnus.com}
2542 to get binaries of GCC for bootstrapping.
2547 @heading @anchor{m6811-elf}m6811-elf
2548 Motorola 68HC11 family micro controllers. These are used in embedded
2549 applications. There are no standard Unix configurations.
2554 @heading @anchor{m6812-elf}m6812-elf
2555 Motorola 68HC12 family micro controllers. These are used in embedded
2556 applications. There are no standard Unix configurations.
2561 @heading @anchor{m68k-att-sysv}m68k-att-sysv
2562 AT&T 3b1, a.k.a.@: 7300 PC@. This version of GCC cannot
2563 be compiled with the system C compiler, which is too buggy.
2564 You will need to get a previous version of GCC and use it to
2565 bootstrap. Binaries are available from the OSU-CIS archive, at
2566 @uref{ftp://archive.cis.ohio-state.edu/pub/att7300/}.
2571 @heading @anchor{m68k-crds-unos}m68k-crds-unos
2572 Use @samp{configure unos} for building on Unos.
2574 The Unos assembler is named @code{casm} instead of @code{as}. For some
2575 strange reason linking @file{/bin/as} to @file{/bin/casm} changes the
2576 behavior, and does not work. So, when installing GCC, you should
2577 install the following script as @file{as} in the subdirectory where
2578 the passes of GCC are installed:
2585 The default Unos library is named @file{libunos.a} instead of
2586 @file{libc.a}. To allow GCC to function, either change all
2587 references to @option{-lc} in @file{gcc.c} to @option{-lunos} or link
2588 @file{/lib/libc.a} to @file{/lib/libunos.a}.
2590 @cindex @code{alloca}, for Unos
2591 When compiling GCC with the standard compiler, to overcome bugs in
2592 the support of @code{alloca}, do not use @option{-O} when making stage 2.
2593 Then use the stage 2 compiler with @option{-O} to make the stage 3
2594 compiler. This compiler will have the same characteristics as the usual
2595 stage 2 compiler on other systems. Use it to make a stage 4 compiler
2596 and compare that with stage 3 to verify proper compilation.
2598 (Perhaps simply defining @code{ALLOCA} in @file{x-crds} as described in
2599 the comments there will make the above paragraph superfluous. Please
2600 inform us of whether this works.)
2602 Unos uses memory segmentation instead of demand paging, so you will need
2603 a lot of memory. 5 Mb is barely enough if no other tasks are running.
2604 If linking @file{cc1} fails, try putting the object files into a library
2605 and linking from that library.
2610 @heading @anchor{m68k-hp-hpux}m68k-hp-hpux
2611 HP 9000 series 300 or 400 running HP-UX@. HP-UX version 8.0 has a bug in
2612 the assembler that prevents compilation of GCC@. This
2613 bug manifests itself during the first stage of compilation, while
2614 building @file{libgcc2.a}:
2618 cc1: warning: `-g' option not supported on this version of GCC
2619 cc1: warning: `-g1' option not supported on this version of GCC
2620 ./xgcc: Internal compiler error: program as got fatal signal 11
2623 A patched version of the assembler is available as the file
2624 @uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you
2625 have HP software support, the patch can also be obtained directly from
2626 HP, as described in the following note:
2629 This is the patched assembler, to patch SR#1653-010439, where the
2630 assembler aborts on floating point constants.
2632 The bug is not really in the assembler, but in the shared library
2633 version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is
2634 SR#4701-078451. Anyway, the attached assembler uses the archive
2635 library version of ``cvtnum(3c)'' and thus does not exhibit the bug.
2638 This patch is also known as PHCO_4484.
2640 In addition, if you wish to use gas, you must use
2641 gas version 2.1 or later, and you must use the GNU linker version 2.1 or
2642 later. Earlier versions of gas relied upon a program which converted the
2643 gas output into the native HP-UX format, but that program has not been
2644 kept up to date. gdb does not understand that native HP-UX format, so
2645 you must use gas if you wish to use gdb.
2647 On HP-UX version 8.05, but not on 8.07 or more recent versions, the
2648 @code{fixproto} shell script triggers a bug in the system shell. If you
2649 encounter this problem, upgrade your operating system or use BASH (the
2650 GNU shell) to run @code{fixproto}. This bug will cause the fixproto
2651 program to report an error of the form:
2654 ./fixproto: sh internal 1K buffer overflow
2657 To fix this, you can also change the first line of the fixproto script
2668 @heading @anchor{m68k-ncr-*}m68k-ncr-*
2669 On the Tower models 4@var{n}0 and 6@var{n}0, by default a process is not
2670 allowed to have more than one megabyte of memory. GCC cannot compile
2671 itself (or many other programs) with @option{-O} in that much memory.
2673 To solve this problem, reconfigure the kernel adding the following line
2674 to the configuration file:
2684 @heading @anchor{m68k-sun}m68k-sun
2685 Sun 3. We do not provide a configuration file to use the Sun FPA by
2686 default, because programs that establish signal handlers for floating
2687 point traps inherently cannot work with the FPA@.
2692 @heading @anchor{m68k-sun-sunos4.1.1}m68k-sun-sunos4.1.1
2694 It is reported that you may need the GNU assembler on this platform.
2700 @heading @anchor{mips-*-*}mips-*-*
2701 If on a MIPS system you get an error message saying ``does not have gp
2702 sections for all it's [sic] sectons [sic]'', don't worry about it. This
2703 happens whenever you use GAS with the MIPS linker, but there is not
2704 really anything wrong, and it is okay to use the output file. You can
2705 stop such warnings by installing the GNU linker.
2707 It would be nice to extend GAS to produce the gp tables, but they are
2708 optional, and there should not be a warning about their absence.
2710 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
2712 This configuration has considerable problems, which will be fixed in a
2715 In order to compile GCC on an SGI running IRIX 5, the ``compiler_dev.hdr''
2716 subsystem must be installed from the IDO CD-ROM supplied by Silicon
2717 Graphics. It is also available for download from
2718 @uref{http://www.sgi.com/developers/devtools/apis/ido.html,,http://www.sgi.com/developers/devtools/apis/ido.html}.
2720 @code{make compare} may fail on version 5 of IRIX unless you add
2721 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
2722 assembler input file is stored in the object file, and that makes
2723 comparison fail if it differs between the @code{stage1} and
2724 @code{stage2} compilations. The option @option{-save-temps} forces a
2725 fixed name to be used for the assembler input file, instead of a
2726 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
2727 unless the comparisons fail without that option. If you do you
2728 @option{-save-temps}, you will have to manually delete the @samp{.i} and
2729 @samp{.s} files after each series of compilations.
2731 If you use the MIPS C compiler to bootstrap, it may be necessary
2732 to increase its table size for switch statements with the
2733 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
2734 optimization option, you also need to use @option{-Olimit 3000}.
2736 To enable debugging under IRIX 5, you must use GNU @command{as} 2.11.2
2738 and use the @option{--with-gnu-as} configure option when configuring GCC.
2739 GNU @command{as} is distributed as part of the binutils package.
2740 When using release 2.11.2, you need to apply a patch
2741 @uref{http://sources.redhat.com/ml/binutils/2001-07/msg00352.html,,http://sources.redhat.com/ml/binutils/2001-07/msg00352.html}
2742 which will be included in the next release of binutils.
2744 When building GCC, the build process loops rebuilding @command{cc1} over
2745 and over again. This happens on @samp{mips-sgi-irix5.2}, and possibly
2746 other platforms. It has been reported that this is a known bug in the
2747 @command{make} shipped with IRIX 5.2. We recommend you use GNU
2748 @command{make} instead of the vendor supplied @command{make} program;
2749 however, you may have success with @command{smake} on IRIX 5.2 if you do
2750 not have GNU @command{make} available.
2755 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
2757 If you are using IRIX @command{cc} as your bootstrap compiler, you must
2758 ensure that the N32 ABI is in use. To test this, compile a simple C
2759 file with @command{cc} and then run @command{file} on the
2760 resulting object file. The output should look like:
2763 test.o: ELF N32 MSB @dots{}
2769 test.o: ELF 32-bit MSB @dots{}
2775 test.o: ELF 64-bit MSB @dots{}
2778 then your version of @command{cc} uses the O32 or N64 ABI by default. You
2779 should set the environment variable @env{CC} to @samp{cc -n32}
2780 before configuring GCC@.
2782 If you want the resulting @command{gcc} to run on old 32-bit systems
2783 with the MIPS R4400 CPU, you need to ensure that only code for the mips3
2784 instruction set architecture (ISA) is generated. While GCC 3.x does
2785 this correctly, both GCC 2.95 and SGI's MIPSpro @command{cc} may change
2786 the ISA depending on the machine where GCC is built. Using one of them
2787 as the bootstrap compiler may result in mips4 code, which won't run at
2788 all on mips3-only systems. For the test program above, you should see:
2791 test.o: ELF N32 MSB mips-3 @dots{}
2797 test.o: ELF N32 MSB mips-4 @dots{}
2800 instead, you should set the environment variable @env{CC} to @samp{cc
2801 -n32 -mips3} or @samp{gcc -mips3} respectively before configuring GCC@.
2803 GCC on IRIX 6 is usually built to support both the N32 and N64 ABIs. If
2804 you build GCC on a system that doesn't have the N64 libraries installed,
2805 you need to configure with @option{--disable-multilib} so GCC doesn't
2806 try to use them. Look for @file{/usr/lib64/libc.so.1} to see if you
2807 have the 64-bit libraries installed.
2809 You must @emph{not} use GNU @command{as} (which isn't built anyway as of
2810 binutils 2.11.2) on IRIX 6 platforms; doing so will only cause problems.
2812 GCC does not currently support generating O32 ABI binaries in the
2813 @samp{mips-sgi-irix6} configurations. It is possible to create a GCC
2814 with O32 ABI only support by configuring it for the @samp{mips-sgi-irix5}
2815 target and using a patched GNU @command{as} 2.11.2 as documented in the
2816 @uref{#mips-sgi-irix5,,@samp{mips-sgi-irix5}} section above. Using the
2817 native assembler requires patches to GCC which will be included in a
2818 future release. It is
2819 expected that O32 ABI support will be available again in a future release.
2821 The @option{--enable-threads} option doesn't currently work, a patch is
2822 in preparation for a future release. The @option{--enable-libgcj}
2823 option is disabled by default: IRIX 6 uses a very low default limit
2824 (20480) for the command line length. Although libtool contains a
2825 workaround for this problem, at least the N64 @samp{libgcj} is known not
2826 to build despite this, running into an internal error of the native
2827 @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
2828 its maximum of 262144 bytes. If you have root access, you can use the
2829 @command{systune} command to do this.
2831 GCC does not correctly pass/return structures which are
2832 smaller than 16 bytes and which are not 8 bytes. The problem is very
2833 involved and difficult to fix. It affects a number of other targets also,
2834 but IRIX 6 is affected the most, because it is a 64-bit target, and 4 byte
2835 structures are common. The exact problem is that structures are being padded
2836 at the wrong end, e.g.@: a 4 byte structure is loaded into the lower 4 bytes
2837 of the register when it should be loaded into the upper 4 bytes of the
2840 GCC is consistent with itself, but not consistent with the SGI C compiler
2841 (and the SGI supplied runtime libraries), so the only failures that can
2842 happen are when there are library functions that take/return such
2843 structures. There are very few such library functions. Currently this
2844 is known to affect @code{inet_ntoa}, @code{inet_lnaof},
2845 @code{inet_netof}, @code{inet_makeaddr}, and @code{semctl}. Until the
2846 bug is fixed, GCC contains workarounds for the known affected functions.
2848 See @uref{http://freeware.sgi.com/,,http://freeware.sgi.com/} for more
2849 information about using GCC on IRIX platforms.
2854 @heading @anchor{powerpc*-*-*}powerpc-*-*
2856 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
2857 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
2862 @heading @anchor{powerpc-*-darwin*}powerpc-*-darwin*
2863 PowerPC running Darwin (Mac OS X kernel).
2865 GCC 3.0 does not support Darwin, but 3.1 and later releases will work.
2867 Pre-installed versions of Mac OS X may not include any developer tools,
2868 meaning that you will not be able to build GCC from source. Tool
2869 binaries are available at
2870 @uref{http://www.opensource.apple.com/projects/darwin} (free
2871 registration required).
2873 Versions of the assembler prior to ``cctools-364'' cannot handle the
2874 4-argument form of @code{rlwinm} and related mask-using instructions. Darwin
2875 1.3 (Mac OS X 10.0) uses cctools-353 for instance. To get cctools-364,
2876 check out @file{cctools} with tag @samp{Apple-364}, build it, and
2877 install the assembler as @file{usr/bin/as}. See
2878 @uref{http://www.opensource.apple.com/tools/cvs/docs.html} for details.
2880 Also, the default stack limit of 512K is too small, and a bootstrap will
2881 typically fail when self-compiling @file{expr.c}. Set the stack to 800K
2882 or more, for instance by doing @samp{limit stack 800}. It's also
2883 convenient to use the GNU preprocessor instead of Apple's during the
2884 first stage of bootstrapping; this is automatic when doing @samp{make
2885 bootstrap}, but to do it from the toplevel objdir you will need to say
2886 @samp{make CC='cc -no-cpp-precomp' bootstrap}.
2888 Note that the version of GCC shipped by Apple typically includes a
2889 number of extensions not available in a standard GCC release. These
2890 extensions are generally specific to Mac programming.
2895 @heading @anchor{powerpc-*-elf}powerpc-*-elf, powerpc-*-sysv4
2896 PowerPC system in big endian mode, running System V.4.
2901 @heading @anchor{powerpc-*-linux-gnu*}powerpc-*-linux-gnu*
2904 @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.13.90.0.10}
2905 or newer for a working GCC@.
2910 @heading @anchor{powerpc-*-netbsd*}powerpc-*-netbsd*
2911 PowerPC system in big endian mode running NetBSD@. To build the
2912 documentation you will need Texinfo version 4.1 (NetBSD 1.5.1 included
2913 Texinfo version 3.12).
2918 @heading @anchor{powerpc-*-eabiaix}powerpc-*-eabiaix
2919 Embedded PowerPC system in big endian mode with @option{-mcall-aix} selected as
2925 @heading @anchor{powerpc-*-eabisim}powerpc-*-eabisim
2926 Embedded PowerPC system in big endian mode for use in running under the
2932 @heading @anchor{powerpc-*-eabi}powerpc-*-eabi
2933 Embedded PowerPC system in big endian mode.
2938 @heading @anchor{powerpcle-*-elf}powerpcle-*-elf, powerpcle-*-sysv4
2939 PowerPC system in little endian mode, running System V.4.
2944 @heading @anchor{powerpcle-*-eabisim}powerpcle-*-eabisim
2945 Embedded PowerPC system in little endian mode for use in running under
2951 @heading @anchor{powerpcle-*-eabi}powerpcle-*-eabi
2952 Embedded PowerPC system in little endian mode.
2957 @heading @anchor{powerpcle-*-winnt}powerpcle-*-winnt, powerpcle-*-pe
2958 PowerPC system in little endian mode running Windows NT@.
2963 @heading @anchor{s390-*-linux*}s390-*-linux*
2964 S/390 system running Linux for S/390@.
2969 @heading @anchor{s390x-*-linux*}s390x-*-linux*
2970 zSeries system (64-bit) running Linux for zSeries@.
2975 @c Please use Solaris 2 to refer to all release of Solaris, starting
2976 @c with 2.0 until 2.6, 7, and 8. Solaris 1 was a marketing name for
2977 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
2978 @c alone is too unspecific and must be avoided.
2979 @heading @anchor{*-*-solaris2*}*-*-solaris2*
2981 Sun does not ship a C compiler with Solaris 2. To bootstrap and install
2982 GCC you first have to install a pre-built compiler, see our
2983 @uref{binaries.html,,binaries page} for details.
2985 The Solaris 2 @command{/bin/sh} will often fail to configure
2986 @file{libstdc++-v3}, @file{boehm-gc} or
2987 @file{libjava}. If you encounter this problem, set @env{CONFIG_SHELL} to
2988 @command{/bin/ksh} in your environment before running @command{configure}.
2990 Solaris 2 comes with a number of optional OS packages. Some of these
2991 packages are needed to use GCC fully, namely @code{SUNWarc},
2992 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
2993 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
2994 optional packages when installing Solaris 2, you will need to verify that
2995 the packages that GCC needs are installed.
2997 To check whether an optional package is installed, use
2998 the @command{pkginfo} command. To add an optional package, use the
2999 @command{pkgadd} command. For further details, see the Solaris 2
3002 Trying to use the linker and other tools in
3003 @file{/usr/ucb} to install GCC has been observed to cause trouble.
3004 For example, the linker may hang indefinitely. The fix is to remove
3005 @file{/usr/ucb} from your @env{PATH}.
3007 All releases of GNU binutils prior to 2.11.2 have known bugs on this
3008 platform. We recommend the use of GNU binutils 2.11.2 or the vendor
3009 tools (Sun @command{as}, Sun @command{ld}).
3011 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3012 newer: @command{g++} will complain that types are missing. These headers assume
3013 that omitting the type means @code{int}; this assumption worked for C89 but
3014 is wrong for C++, and is now wrong for C99 also.
3016 @command{g++} accepts such (invalid) constructs with the option
3017 @option{-fpermissive}; it
3018 will assume that any missing type is @code{int} (as defined by C89).
3020 There are patches for Solaris 2.6 (105633-56 or newer for SPARC,
3021 106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC,
3022 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
3023 108653-22 for Intel) that fix this bug.
3028 @heading @anchor{sparc-sun-solaris2*}sparc-sun-solaris2*
3030 When GCC is configured to use binutils 2.11.2 or later the binaries
3031 produced are smaller than the ones produced using Sun's native tools;
3032 this difference is quite significant for binaries containing debugging
3035 Sun @command{as} 4.x is broken in that it cannot cope with long symbol names.
3036 A typical error message might look similar to the following:
3039 /usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error:
3040 can't compute value of an expression involving an external symbol.
3043 This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris
3044 2.6 and has been fixed in later (5.x) versions of the assembler,
3045 starting with Solaris 7.
3047 Starting with Solaris 7, the operating system is capable of executing
3048 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
3049 this; the @option{-m64} option enables 64-bit code generation.
3050 However, if all you want is code tuned for the UltraSPARC CPU, you
3051 should try the @option{-mtune=ultrasparc} option instead, which produces
3052 code that, unlike full 64-bit code, can still run on non-UltraSPARC
3055 When configuring on a Solaris 7 or later system that is running a kernel
3056 that supports only 32-bit binaries, one must configure with
3057 @option{--disable-multilib}, since we will not be able to build the
3058 64-bit target libraries.
3063 @heading @anchor{sparc-sun-solaris2.7}sparc-sun-solaris2.7
3065 Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
3066 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
3067 and later, including all EGCS releases. Sun formerly recommended
3068 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
3069 recommend it only for people who use Sun's compilers.
3071 Here are some workarounds to this problem:
3074 Do not install Sun patch 107058-01 until after Sun releases a
3075 complete patch for bug 4210064. This is the simplest course to take,
3076 unless you must also use Sun's C compiler. Unfortunately 107058-01
3077 is preinstalled on some new Solaris 7-based hosts, so you may have to
3081 Copy the original, unpatched Solaris 7
3082 @command{/usr/ccs/bin/as} into
3083 @command{/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/3.1/as},
3084 adjusting the latter name to fit your local conventions and software
3088 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
3089 both 107058-01 and 106950-03 installed has reported the bug with GCC
3090 and Sun's dynamic linker. This last course of action is riskiest,
3091 for two reasons. First, you must install 106950 on all hosts that
3092 run code generated by GCC; it doesn't suffice to install it only on
3093 the hosts that run GCC itself. Second, Sun says that 106950-03 is
3094 only a partial fix for bug 4210064, but Sun doesn't know whether the
3095 partial fix is adequate for GCC@. Revision -08 or later should fix
3096 the bug. The current (as of 2001-09-24) revision is -14, and is included in
3097 the Solaris 7 Recommended Patch Cluster.
3105 @heading @anchor{sparc-sun-sunos4*}sparc-sun-sunos4*
3107 A bug in the SunOS 4 linker will cause it to crash when linking
3108 @option{-fPIC} compiled objects (and will therefore not allow you to build
3111 To fix this problem you can either use the most recent version of
3112 binutils or get the latest SunOS 4 linker patch (patch ID 100170-10)
3113 from Sun's patch site.
3115 Sometimes on a Sun 4 you may observe a crash in the program
3116 @command{genflags} or @command{genoutput} while building GCC. This is said to
3117 be due to a bug in @command{sh}. You can probably get around it by running
3118 @command{genflags} or @command{genoutput} manually and then retrying the
3124 @heading @anchor{sparc-unknown-linux-gnulibc1}sparc-unknown-linux-gnulibc1
3126 It has been reported that you might need
3127 @uref{ftp://ftp.yggdrasil.com/private/hjl,,binutils 2.8.1.0.23}
3128 for this platform, too.
3134 @heading @anchor{sparc-*-linux*}sparc-*-linux*
3136 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
3137 or newer on this platform. All earlier binutils and glibc
3138 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
3144 @heading @anchor{sparc64-*-*}sparc64-*-*
3146 GCC version 2.95 is not able to compile code correctly for
3147 @code{sparc64} targets. Users of the Linux kernel, at least,
3148 can use the @code{sparc32} program to start up a new shell
3149 invocation with an environment that causes @command{configure} to
3150 recognize (via @samp{uname -a}) the system as @samp{sparc-*-*} instead.
3155 @heading @anchor{sparcv9-*-solaris2*}sparcv9-*-solaris2*
3157 The following compiler flags must be specified in the configure
3158 step in order to bootstrap this target with the Sun compiler:
3161 % CC="cc -xildoff -xarch=v9" @var{srcdir}/configure [@var{options}] [@var{target}]
3164 @option{-xildoff} turns off the incremental linker, and @option{-xarch=v9}
3165 specifies the v9 architecture to the Sun linker and assembler.
3170 @heading @anchor{#*-*-sysv*}*-*-sysv*
3171 On System V release 3, you may get this error message
3175 ld fatal: failed to write symbol name @var{something}
3176 in strings table for file @var{whatever}
3179 This probably indicates that the disk is full or your ulimit won't allow
3180 the file to be as large as it needs to be.
3182 This problem can also result because the kernel parameter @code{MAXUMEM}
3183 is too small. If so, you must regenerate the kernel and make the value
3184 much larger. The default value is reported to be 1024; a value of 32768
3185 is said to work. Smaller values may also work.
3187 On System V, if you get an error like this,
3190 /usr/local/lib/bison.simple: In function `yyparse':
3191 /usr/local/lib/bison.simple:625: virtual memory exhausted
3195 that too indicates a problem with disk space, ulimit, or @code{MAXUMEM}.
3197 On a System V release 4 system, make sure @file{/usr/bin} precedes
3198 @file{/usr/ucb} in @code{PATH}. The @code{cc} command in
3199 @file{/usr/ucb} uses libraries which have bugs.
3204 @heading @anchor{vax-dec-ultrix}vax-dec-ultrix
3205 Don't try compiling with VAX C (@code{vcc}). It produces incorrect code
3206 in some cases (for example, when @code{alloca} is used).
3211 @heading @anchor{xtensa-*-elf}xtensa-*-elf
3213 This target is intended for embedded Xtensa systems using the
3214 @samp{newlib} C library. It uses ELF but does not support shared
3215 objects. Designed-defined instructions specified via the
3216 Tensilica Instruction Extension (TIE) language are only supported
3217 through inline assembly.
3219 The Xtensa configuration information must be specified prior to
3220 building GCC@. The @file{gcc/config/xtensa/xtensa-config.h} header
3221 file contains the configuration information. If you created your
3222 own Xtensa configuration with the Xtensa Processor Generator, the
3223 downloaded files include a customized copy of this header file,
3224 which you can use to replace the default header file.
3229 @heading @anchor{xtensa-*-linux*}xtensa-*-linux*
3231 This target is for Xtensa systems running GNU/Linux. It supports ELF
3232 shared objects and the GNU C library (glibc). It also generates
3233 position-independent code (PIC) regardless of whether the
3234 @option{-fpic} or @option{-fPIC} options are used. In other
3235 respects, this target is the same as the
3236 @uref{#xtensa-*-elf,,@samp{xtensa-*-elf}} target.
3241 @heading @anchor{windows}Microsoft Windows (32-bit)
3243 A port of GCC 2.95.x is included with the
3244 @uref{http://www.cygwin.com/,,Cygwin environment}.
3246 Current (as of early 2001) snapshots of GCC will build under Cygwin
3247 without modification.
3252 @heading @anchor{os2}OS/2
3254 GCC does not currently support OS/2. However, Andrew Zabolotny has been
3255 working on a generic OS/2 port with pgcc. The current code can be found
3256 at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
3258 An older copy of GCC 2.8.1 is included with the EMX tools available at
3259 @uref{ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/,,
3260 ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/}.
3265 @heading @anchor{older}Older systems
3267 GCC contains support files for many older (1980s and early
3268 1990s) Unix variants. For the most part, support for these systems
3269 has not been deliberately removed, but it has not been maintained for
3270 several years and may suffer from bitrot.
3272 Starting with GCC 3.1, each release has a list of ``obsoleted'' systems.
3273 Support for these systems is still present in that release, but
3274 @command{configure} will fail unless the @option{--enable-obsolete}
3275 option is given. Unless a maintainer steps forward, support for these
3276 systems will be removed from the next release of GCC@.
3278 Support for old systems as hosts for GCC can cause problems if the
3279 workarounds for compiler, library and operating system bugs affect the
3280 cleanliness or maintainability of the rest of GCC@. In some cases, to
3281 bring GCC up on such a system, if still possible with current GCC, may
3282 require first installing an old version of GCC which did work on that
3283 system, and using it to compile a more recent GCC, to avoid bugs in the
3284 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
3285 @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror
3286 sites}. Header bugs may generally be avoided using
3287 @command{fixincludes}, but bugs or deficiencies in libraries and the
3288 operating system may still cause problems.
3290 Support for older systems as targets for cross-compilation is less
3291 problematic than support for them as hosts for GCC; if an enthusiast
3292 wishes to make such a target work again (including resurrecting any of
3293 the targets that never worked with GCC 2, starting from the last CVS
3294 version before they were removed), patches
3295 @uref{../contribute.html,,following the usual requirements} would be
3296 likely to be accepted, since they should not affect the support for more
3299 For some systems, old versions of GNU binutils may also be useful,
3300 and are available from @file{pub/binutils/old-releases} on
3301 @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}.
3303 Some of the information on specific systems above relates to
3304 such older systems, but much of the information
3305 about GCC on such systems (which may no longer be applicable to
3306 current GCC) is to be found in the GCC texinfo manual.
3311 @heading @anchor{elf_targets}all ELF targets (SVR4, Solaris 2, etc.)
3313 C++ support is significantly better on ELF targets if you use the
3314 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
3315 inlines, vtables and template instantiations will be discarded
3324 @uref{./index.html,,Return to the GCC Installation page}
3328 @c ***Old documentation******************************************************
3330 @include install-old.texi
3336 @uref{./index.html,,Return to the GCC Installation page}
3340 @c ***GFDL********************************************************************
3348 @uref{./index.html,,Return to the GCC Installation page}
3352 @c ***************************************************************************
3353 @c Part 6 The End of the Document
3355 @comment node-name, next, previous, up
3356 @node Concept Index, , GNU Free Documentation License, Top
3360 @unnumbered Concept Index