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, in general, GCC @strong{must} be built into a separate directory
288 than the sources which does @strong{not} reside within the source tree.
289 This is how almost all developers build GCC; building where @var{srcdir}
290 == @var{objdir} is completely unsupported; building where @var{objdir}
291 is a subdirectory of @var{srcdir} is completely unsupported.
293 If you have previously built GCC in the same directory for a
294 different target machine, do @samp{make distclean} to delete all files
295 that might be invalid. One of the files this deletes is
296 @file{Makefile}; if @samp{make distclean} complains that @file{Makefile}
297 does not exist, it probably means that the directory is already suitably
298 clean. However, with the recommended method of building in a separate
299 @var{objdir}, you should simply use a different @var{objdir} for each
302 Second, when configuring a native system, either @command{cc} or
303 @command{gcc} must be in your path or you must set @env{CC} in
304 your environment before running configure. Otherwise the configuration
307 Note that the bootstrap compiler and the resulting GCC must be link
308 compatible, else the bootstrap will fail with linker errors about
309 incompatible object file formats. Several multilibed targets are
310 affected by this requirement, see
312 @ref{Specific, host/target specific installation notes}.
315 @uref{specific.html,,host/target specific installation notes}.
323 % @var{srcdir}/configure [@var{options}] [@var{target}]
327 @heading Target specification
330 GCC has code to correctly determine the correct value for @var{target}
331 for nearly all native systems. Therefore, we highly recommend you not
332 provide a configure target when configuring a native compiler.
335 @var{target} must be specified as @option{--target=@var{target}}
336 when configuring a cross compiler; examples of valid targets would be
337 i960-rtems, m68k-coff, sh-elf, etc.
340 Specifying just @var{target} instead of @option{--target=@var{target}}
341 implies that the host defaults to @var{target}.
345 @heading Options specification
347 Use @var{options} to override several configure time options for
348 GCC@. A list of supported @var{options} follows; @command{configure
349 --help} may list other options, but those not listed below may not
350 work and should not normally be used.
353 @item --prefix=@var{dirname}
354 Specify the toplevel installation
355 directory. This is the recommended way to install the tools into a directory
356 other than the default. The toplevel installation directory defaults to
359 We @strong{highly} recommend against @var{dirname} being the same or a
360 subdirectory of @var{objdir} or vice versa.
362 These additional options control where certain parts of the distribution
363 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 options only take effect for native
437 builds; cross compiler binaries' names are not transformed even when a
438 transformation is explicitly asked for by one of this options.
440 For native builds, some of the installed programs are also installed
441 with the target alias in front of their name, as in
442 @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
443 before the target alias is prepended to the name - so, specifying
444 @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
445 resulting binary would be installed as
446 @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.
448 As a last shortcoming, none of the installed Ada programs are
449 transformed yet, which will be fixed in some time.
451 @item --with-local-prefix=@var{dirname}
453 installation directory for local include files. The default is
454 @file{/usr/local}. Specify this option if you want the compiler to
455 search directory @file{@var{dirname}/include} for locally installed
456 header files @emph{instead} of @file{/usr/local/include}.
458 You should specify @option{--with-local-prefix} @strong{only} if your
459 site has a different convention (not @file{/usr/local}) for where to put
462 The default value for @option{--with-local-prefix} is @file{/usr/local}
463 regardless of the value of @option{--prefix}. Specifying
464 @option{--prefix} has no effect on which directory GCC searches for
465 local header files. This may seem counterintuitive, but actually it is
468 The purpose of @option{--prefix} is to specify where to @emph{install
469 GCC}. The local header files in @file{/usr/local/include}---if you put
470 any in that directory---are not part of GCC@. They are part of other
471 programs---perhaps many others. (GCC installs its own header files in
472 another directory which is based on the @option{--prefix} value.)
474 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 @code{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 found
548 assembler is not actually the GNU assembler. (Confusion will 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 systems where it makes a difference whether you use the GNU assembler are
555 @samp{hppa1.0-@var{any}-@var{any}}, @samp{hppa1.1-@var{any}-@var{any}},
556 @samp{i386-@var{any}-sysv}, @samp{i386-@var{any}-isc},
557 @samp{i860-@var{any}-bsd}, @samp{m68k-bull-sysv},
558 @samp{m68k-hp-hpux}, @samp{m68k-sony-bsd},
559 @samp{m68k-altos-sysv}, @samp{m68000-hp-hpux},
560 @samp{m68000-att-sysv}, @samp{@var{any}-lynx-lynxos},
561 and @samp{mips-@var{any}}.
562 On any other system, @option{--with-gnu-as} has no effect.
564 On the systems listed above (except for the HP-PA, for ISC on the
565 386, and for @samp{mips-sgi-irix5.*}), if you use the GNU assembler,
566 you should also use the GNU linker (and specify @option{--with-gnu-ld}).
568 @item --with-as=@var{pathname}
570 compiler should use the assembler pointed to by @var{pathname}, rather
571 than the one found by the standard rules to find an assembler, which
576 @file{@var{exec_prefix}/lib/gcc-lib/@var{target}/@var{version}}
577 directory, where @var{exec_prefix} defaults to @var{prefix} which
578 defaults to @file{/usr/local} unless overridden by the
579 @option{--prefix=@var{pathname}} switch described above. @var{target} is the
580 target system triple, such as @samp{sparc-sun-solaris2.7}, and
581 @var{version} denotes the GCC version, such as 3.0.
583 Check operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
586 Note that these rules do not check for the value of @env{PATH}. You may
587 want to use @option{--with-as} if no assembler is installed in the
588 directories listed above, or if you have multiple assemblers installed
589 and want to choose one that is not found by the above rules.
591 @item @anchor{with-gnu-ld}--with-gnu-ld
592 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
596 @item --with-ld=@var{pathname}
598 @option{--with-as}, but for the linker.
601 Specify that stabs debugging
602 information should be used instead of whatever format the host normally
603 uses. Normally GCC uses the same debug format as the host system.
605 On MIPS based systems and on Alphas, you must specify whether you want
606 GCC to create the normal ECOFF debugging format, or to use BSD-style
607 stabs passed through the ECOFF symbol table. The normal ECOFF debug
608 format cannot fully handle languages other than C@. BSD stabs format can
609 handle other languages, but it only works with the GNU debugger GDB@.
611 Normally, GCC uses the ECOFF debugging format by default; if you
612 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
614 No matter which default you choose when you configure GCC, the user
615 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
616 the debug format for a particular compilation.
618 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
619 @option{--with-gas} is used. It selects use of stabs debugging
620 information embedded in COFF output. This kind of debugging information
621 supports C++ well; ordinary COFF debugging information does not.
623 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
624 selects use of stabs debugging information embedded in ELF output. The
625 C++ compiler currently (2.6.0) does not support the DWARF debugging
626 information normally used on 386 SVR4 platforms; stabs provide a
627 workable alternative. This requires gas and gdb, as the normal SVR4
628 tools can not generate or interpret stabs.
630 @item --disable-multilib
631 Specify that multiple target
632 libraries to support different target variants, calling
633 conventions, etc should not be built. The default is to build a
634 predefined set of them.
636 Some targets provide finer-grained control over which multilibs are built
637 (e.g., @option{--disable-softfloat}):
644 fpu, 26bit, underscore, interwork, biendian, nofmult.
647 softfloat, m68881, m68000, m68020.
650 single-float, biendian, softfloat.
652 @item powerpc*-*-*, rs6000*-*-*
653 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
658 @item --enable-threads
659 Specify that the target
660 supports threads. This affects the Objective-C compiler and runtime
661 library, and exception handling for other languages like C++ and Java.
662 On some systems, this is the default.
664 In general, the best (and, in many cases, the only known) threading
665 model available will be configured for use. Beware that on some
666 systems, gcc has not been taught what threading models are generally
667 available for the system. In this case, @option{--enable-threads} is an
668 alias for @option{--enable-threads=single}.
670 @item --disable-threads
671 Specify that threading support should be disabled for the system.
672 This is an alias for @option{--enable-threads=single}.
674 @item --enable-threads=@var{lib}
676 @var{lib} is the thread support library. This affects the Objective-C
677 compiler and runtime library, and exception handling for other languages
678 like C++ and Java. The possibilities for @var{lib} are:
686 Generic MACH thread support, known to work on NeXTSTEP@. (Please note
687 that the file needed to support this configuration, @file{gthr-mach.h}, is
688 missing and thus this setting will cause a known bootstrap failure.)
690 This is an alias for @samp{single}.
692 Generic POSIX thread support.
694 Same as @samp{posix} on arm*-*-linux*, *-*-chorusos* and *-*-freebsd*
695 only. A future release of gcc might remove this alias or extend it
698 RTEMS thread support.
700 Disable thread support, should work for all platforms.
702 Sun Solaris 2 thread support.
704 VxWorks thread support.
706 Microsoft Win32 API thread support.
709 @item --with-cpu=@var{cpu}
710 Specify which cpu variant the
711 compiler should generate code for by default. This is currently
712 only supported on the some ports, specifically arm, powerpc, and
713 SPARC@. If configure does not recognize the model name (e.g.@: arm700,
714 603e, or ultrasparc) you provide, please check the configure script
715 for a complete list of supported models.
717 @item --enable-altivec
718 Specify that the target supports AltiVec vector enhancements. This
719 option will adjust the ABI for AltiVec enhancements, as well as generate
720 AltiVec code when appropriate. This option is only available for
723 @item --enable-target-optspace
725 libraries should be optimized for code space instead of code speed.
726 This is the default for the m32r platform.
729 Specify that a user visible @command{cpp} program should not be installed.
731 @item --with-cpp-install-dir=@var{dirname}
732 Specify that the user visible @command{cpp} program should be installed
733 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
735 @item --enable-maintainer-mode
737 regenerate the GCC master message catalog @file{gcc.pot} are normally
738 disabled. This is because it can only be rebuilt if the complete source
739 tree is present. If you have changed the sources and want to rebuild the
740 catalog, configuring with @option{--enable-maintainer-mode} will enable
741 this. Note that you need a recent version of the @code{gettext} tools
744 @item --enable-version-specific-runtime-libs
746 that runtime libraries should be installed in the compiler specific
747 subdirectory (@file{@var{libsubdir}}) rather than the usual places. In
748 addition, @samp{libstdc++}'s include files will be installed in
749 @file{@var{libsubdir}/include/g++} unless you overruled it by using
750 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
751 particularly useful if you intend to use several versions of GCC in
752 parallel. This is currently supported by @samp{libf2c} and
753 @samp{libstdc++}, and is the default for @samp{libobjc} which cannot be
754 changed in this case.
756 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
757 Specify that only a particular subset of compilers and
758 their runtime libraries should be built. For a list of valid values for
759 @var{langN} you can issue the following command in the
760 @file{gcc} directory of your GCC source tree:@*
762 grep language= */config-lang.in
764 Currently, you can use any of the following:
765 @code{ada}, @code{c}, @code{c++}, @code{f77}, @code{java}, @code{objc}.
766 Building the Ada compiler has special requirements, see below.@*
767 If you do not pass this flag, all languages available in the @file{gcc}
768 sub-tree will be configured. Re-defining @code{LANGUAGES} when calling
769 @samp{make bootstrap} @strong{does not} work anymore, as those
770 language sub-directories might not have been configured!
772 @item --disable-libgcj
773 Specify that the run-time libraries
774 used by GCJ should not be built. This is useful in case you intend
775 to use GCJ with some other run-time, or you're going to install it
776 separately, or it just happens not to build on your particular
777 machine. In general, if the Java front end is enabled, the GCJ
778 libraries will be enabled too, unless they're known to not work on
779 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
780 may need to port it; in this case, before modifying the top-level
781 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
782 you may use @option{--enable-libgcj} to override the default.
785 Specify that the compiler should
786 use DWARF 2 debugging information as the default.
788 @item --enable-win32-registry
789 @itemx --enable-win32-registry=@var{key}
790 @itemx --disable-win32-registry
791 The @option{--enable-win32-registry} option enables Windows-hosted GCC
792 to look up installations paths in the registry using the following key:
795 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
798 @var{key} defaults to GCC version number, and can be overridden by the
799 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
800 who use custom installers are encouraged to provide a different key,
801 perhaps one comprised of vendor name and GCC version number, to
802 avoid conflict with existing installations. This feature is enabled
803 by default, and can be disabled by @option{--disable-win32-registry}
804 option. This option has no effect on the other hosts.
807 Specify that the machine does not have a floating point unit. This
808 option only applies to @samp{m68k-sun-sunos@var{n}} and
809 @samp{m68k-isi-bsd}. On any other system, @option{--nfp} has no effect.
811 @item --enable-checking
812 @itemx --enable-checking=@var{list}
813 When you specify this option, the compiler is built to perform checking
814 of tree node types when referencing fields of that node, and some other
815 internal consistency checks. This does not change the generated code,
816 but adds error checking within the compiler. This will slow down the
817 compiler and may only work properly if you are building the compiler
818 with GCC@. This is on by default when building from CVS or snapshots,
819 but off for releases. More control over the checks may be had by
820 specifying @var{list}; the categories of checks available are
821 @samp{misc}, @samp{tree}, @samp{gc}, @samp{rtl}, @samp{rtlflag} and
823 default when @var{list} is not specified is @samp{misc,tree,gc,rtlflag}; the
824 checks @samp{rtl} and @samp{gcac} are very expensive.
826 @item --enable-coverage
827 @item --enable-coverage=@var{level}
828 With this option, the compiler is built to collect self coverage
829 information, every time it is run. This is for internal development
830 purposes, and only works when the compiler is being built with gcc. The
831 @var{level} argument controls whether the compiler is built optimized or
832 not, values are @samp{opt} and @samp{noopt}. For coverage analysis you
833 want to disable optimization, for performance analysis you want to
834 enable optimization. When coverage is enabled, the default level is
835 without optimization.
839 The @option{--enable-nls} option enables Native Language Support (NLS),
840 which lets GCC output diagnostics in languages other than American
841 English. Native Language Support is enabled by default if not doing a
842 canadian cross build. The @option{--disable-nls} option disables NLS@.
844 @item --with-included-gettext
845 If NLS is enabled, the @option{--with-included-gettext} option causes the build
846 procedure to prefer its copy of GNU @command{gettext}.
849 If NLS is enabled, and if the host lacks @code{gettext} but has the
850 inferior @code{catgets} interface, the GCC build procedure normally
851 ignores @code{catgets} and instead uses GCC's copy of the GNU
852 @code{gettext} library. The @option{--with-catgets} option causes the
853 build procedure to use the host's @code{catgets} in this situation.
855 @item --with-libiconv-prefix=@var{dir}
856 Search for libiconv header files in @file{@var{dir}/include} and
857 libiconv library files in @file{@var{dir}/lib}.
859 @item --with-system-zlib
860 Use installed zlib rather than that included with GCC@. This option
861 only applies if the Java front end is being built.
863 @item --enable-obsolete
864 Enable configuration for an obsoleted system. If you attempt to
865 configure GCC for a system (build, host, or target) which has been
866 obsoleted, and you do not specify this flag, configure will halt with an
869 All support for systems which have been obsoleted in one release of GCC
870 is removed entirely in the next major release, unless someone steps
871 forward to maintain the port.
874 Some options which only apply to building cross compilers:
876 @item --with-headers=@var{dir}
877 Specifies a directory
878 which has target include files.
879 @emph{This options is required} when building a cross
880 compiler, if @file{@var{prefix}/@var{target}/sys-include} doesn't pre-exist.
881 These include files will be copied into the @file{gcc} install directory.
882 Fixincludes will be run on these files to make them compatible with
884 @item --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
885 Specifies a list of directories which contain the target runtime
886 libraries. These libraries will be copied into the @file{gcc} install
889 Specifies that @samp{newlib} is
890 being used as the target C library. This causes @code{__eprintf} to be
891 omitted from @file{libgcc.a} on the assumption that it will be provided by
895 Note that each @option{--enable} option has a corresponding
896 @option{--disable} option and that each @option{--with} option has a
897 corresponding @option{--without} option.
904 @uref{./index.html,,Return to the GCC Installation page}
908 @c ***Building****************************************************************
910 @comment node-name, next, previous, up
911 @node Building, Testing, Configuration, Installing GCC
917 @cindex Installing GCC: Building
919 Now that GCC is configured, you are ready to build the compiler and
922 We @strong{highly} recommend that GCC be built using GNU make;
923 other versions may work, then again they might not.
924 GNU make is required for compiling GNAT (the Ada compiler) and the Java
927 (For example, many broken versions of make will fail if you use the
928 recommended setup where @var{objdir} is different from @var{srcdir}.
929 Other broken versions may recompile parts of the compiler when
930 installing the compiler.)
932 Some commands executed when making the compiler may fail (return a
933 nonzero status) and be ignored by @code{make}. These failures, which
934 are often due to files that were not found, are expected, and can safely
937 It is normal to have compiler warnings when compiling certain files.
938 Unless you are a GCC developer, you can generally ignore these warnings
939 unless they cause compilation to fail.
941 On certain old systems, defining certain environment variables such as
942 @env{CC} can interfere with the functioning of @command{make}.
944 If you encounter seemingly strange errors when trying to build the
945 compiler in a directory other than the source directory, it could be
946 because you have previously configured the compiler in the source
947 directory. Make sure you have done all the necessary preparations.
949 If you build GCC on a BSD system using a directory stored in an old System
950 V file system, problems may occur in running @code{fixincludes} if the
951 System V file system doesn't support symbolic links. These problems
952 result in a failure to fix the declaration of @code{size_t} in
953 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
954 that type mismatches occur, this could be the cause.
956 The solution is not to use such a directory for building GCC@.
958 When building from CVS or snapshots, or if you modify parser sources,
959 you need the Bison parser generator installed. Any version 1.25 or
960 later should work; older versions may also work. If you do not modify
961 parser sources, releases contain the Bison-generated files and you do
962 not need Bison installed to build them.
964 When building from CVS or snapshots, or if you modify Texinfo
965 documentation, you need version 4.1 or later of Texinfo installed if you
966 want Info documentation to be regenerated. Releases contain Info
967 documentation pre-built for the unmodified documentation in the release.
969 @section Building a native compiler
971 For a native build issue the command @samp{make bootstrap}. This
972 will build the entire GCC system, which includes the following steps:
976 Build host tools necessary to build the compiler such as texinfo, bison,
980 Build target tools for use by the compiler such as binutils (bfd,
981 binutils, gas, gprof, ld, and opcodes)
982 if they have been individually linked
983 or moved into the top level GCC source tree before configuring.
986 Perform a 3-stage bootstrap of the compiler.
989 Perform a comparison test of the stage2 and stage3 compilers.
992 Build runtime libraries using the stage3 compiler from the previous step.
996 If you are short on disk space you might consider @samp{make
997 bootstrap-lean} instead. This is identical to @samp{make
998 bootstrap} except that object files from the stage1 and
999 stage2 of the 3-stage bootstrap of the compiler are deleted as
1000 soon as they are no longer needed.
1003 If you want to save additional space during the bootstrap and in
1004 the final installation as well, you can build the compiler binaries
1005 without debugging information with @samp{make CFLAGS='-O' LIBCFLAGS='-g
1006 -O2' LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap}. This will save
1007 roughly 40% of disk space both for the bootstrap and the final installation.
1008 (Libraries will still contain debugging information.)
1010 If you wish to use non-default GCC flags when compiling the stage2 and
1011 stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing
1012 @samp{make bootstrap}. Non-default optimization flags are less well
1013 tested here than the default of @samp{-g -O2}, but should still work.
1014 In a few cases, you may find that you need to specify special flags such
1015 as @option{-msoft-float} here to complete the bootstrap; or, if the
1016 native compiler miscompiles the stage1 compiler, you may need to work
1017 around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the
1018 stage1 compiler that were miscompiled, or by using @samp{make
1019 bootstrap4} to increase the number of stages of bootstrap.
1021 If you used the flag @option{--enable-languages=@dots{}} to restrict
1022 the compilers to be built, only those you've actually enabled will be
1023 built. This will of course only build those runtime libraries, for
1024 which the particular compiler has been built. Please note,
1025 that re-defining @env{LANGUAGES} when calling @samp{make bootstrap}
1026 @strong{does not} work anymore!
1028 If the comparison of stage2 and stage3 fails, this normally indicates
1029 that the stage2 compiler has compiled GCC incorrectly, and is therefore
1030 a potentially serious bug which you should investigate and report. (On
1031 a few systems, meaningful comparison of object files is impossible; they
1032 always appear ``different''. If you encounter this problem, you will
1033 need to disable comparison in the @file{Makefile}.)
1035 @section Building a cross compiler
1037 We recommend reading the
1038 @uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ}
1039 for information about building cross compilers.
1041 When building a cross compiler, it is not generally possible to do a
1042 3-stage bootstrap of the compiler. This makes for an interesting problem
1043 as parts of GCC can only be built with GCC@.
1045 To build a cross compiler, we first recommend building and installing a
1046 native compiler. You can then use the native GCC compiler to build the
1047 cross compiler. The installed native compiler needs to be GCC version
1050 Assuming you have already installed a native copy of GCC and configured
1051 your cross compiler, issue the command @command{make}, which performs the
1056 Build host tools necessary to build the compiler such as texinfo, bison,
1060 Build target tools for use by the compiler such as binutils (bfd,
1061 binutils, gas, gprof, ld, and opcodes)
1062 if they have been individually linked or moved into the top level GCC source
1063 tree before configuring.
1066 Build the compiler (single stage only).
1069 Build runtime libraries using the compiler from the previous step.
1072 Note that if an error occurs in any step the make process will exit.
1074 @section Building in parallel
1076 If you have a multiprocessor system you can use @samp{make bootstrap
1077 MAKE="make -j 2" -j 2} or just @samp{make -j 2 bootstrap}
1078 for GNU Make 3.79 and above instead of just @samp{make bootstrap}
1079 when building GCC@. You can use a bigger number instead of two if
1080 you like. In most cases, it won't help to use a number bigger than
1081 the number of processors in your machine.
1083 @section Building the Ada compiler
1085 In order to build GNAT, the Ada compiler, you need a working GNAT
1086 compiler (GNAT version 3.13 or later, or GCC version 3.1 or later),
1087 since the Ada front end is written in Ada (with some
1088 GNAT-specific extensions), and GNU make.
1090 However, you do not need a full installation of GNAT, just the GNAT
1091 binary @file{gnat1}, a copy of @file{gnatbind}, and a compiler driver
1092 which can deal with Ada input (by invoking the @file{gnat1} binary).
1093 You can specify this compiler driver by setting the @env{ADAC}
1094 environment variable at the configure step. @command{configure} can
1095 detect the driver automatically if it has got a common name such as
1096 @command{gcc} or @command{gnatgcc}. Of course, you still need a working
1097 C compiler (the compiler driver can be different or not).
1098 @command{configure} does not test whether the GNAT installation works
1099 and has a sufficiently recent version; if too old a GNAT version is
1100 installed, the build will fail unless @option{--enable-languages} is
1101 used to disable building the Ada front end.
1103 Additional build tools (such as @command{gnatmake}) or a working GNAT
1104 run-time library installation are usually @emph{not} required. However,
1105 if you want to boostrap the compiler using a minimal version of GNAT,
1106 you have to issue the following commands before invoking @samp{make
1107 boostrap} (this assumes that you start with an unmodified and consistent
1108 source distribution):
1111 cd @var{srcdir}/gcc/ada
1112 touch treeprs.ads [es]info.h nmake.ad[bs]
1115 At the moment, the GNAT library and several tools for GNAT are not built
1116 by @samp{make bootstrap}. You have to invoke
1117 @samp{make gnatlib_and_tools} in the @file{@var{objdir}/gcc}
1118 subdirectory before proceeding with the next steps.
1120 For example, you can build a native Ada compiler by issuing the
1121 following commands (assuming @command{make} is GNU make):
1125 @var{srcdir}/configure --enable-languages=c,ada
1126 cd @var{srcdir}/gcc/ada
1127 touch treeprs.ads [es]info.h nmake.ad[bs]
1131 make gnatlib_and_tools
1135 Currently, when compiling the Ada front end, you cannot use the parallel
1136 build feature described in the previous section.
1143 @uref{./index.html,,Return to the GCC Installation page}
1147 @c ***Testing*****************************************************************
1149 @comment node-name, next, previous, up
1150 @node Testing, Final install, Building, Installing GCC
1154 @chapter Installing GCC: Testing
1157 @cindex Installing GCC: Testing
1160 Before you install GCC, we encourage you to run the testsuites and to
1161 compare your results with results from a similar configuration that have
1162 been submitted to the
1163 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
1164 This step is optional and may require you to download additional software,
1165 but it can give you confidence in your new GCC installation or point out
1166 problems before you install and start using your new GCC.
1168 First, you must have @uref{download.html,,downloaded the testsuites}.
1169 These are part of the full distribution, but if you downloaded the
1170 ``core'' compiler plus any front ends, you must download the testsuites
1173 Second, you must have the testing tools installed. This includes
1174 a @uref{http://www.gnu.org/software/dejagnu/,,current version of DejaGnu};
1175 dejagnu 1.3 is not sufficient.
1176 It also includes Tcl and Expect; the DejaGnu site has links to these.
1178 Now you may need specific preparations:
1183 The following environment variables may need to be set appropriately, as in
1184 the following example (which assumes that DejaGnu has been installed
1185 under @file{/usr/local}):
1188 TCL_LIBRARY = /usr/local/share/tcl8.0
1189 DEJAGNULIBS = /usr/local/share/dejagnu
1192 On systems such as Cygwin, these paths are required to be actual
1193 paths, not mounts or links; presumably this is due to some lack of
1194 portability in the DejaGnu code.
1196 If the directories where @command{runtest} and @command{expect} were
1197 installed are in the @env{PATH}, it should not be necessary to set these
1198 environment variables.
1202 Finally, you can run the testsuite (which may take a long time):
1204 cd @var{objdir}; make -k check
1207 The testing process will try to test as many components in the GCC
1208 distribution as possible, including the C, C++, Objective-C and Fortran
1209 compilers as well as the C++ and Java runtime libraries.
1211 While running the testsuite, DejaGnu might emit messages resembling
1212 @samp{WARNING: Couldn't find the global config file.} or
1213 @samp{WARNING: Couldn't find tool init file}.
1214 These messages are harmless and do not affect the validity of the tests.
1216 @section How can I run the test suite on selected tests?
1218 As a first possibility to cut down the number of tests that are run it is
1219 possible to use @samp{make check-gcc} or @samp{make check-g++}
1220 in the @file{gcc} subdirectory of the object directory. To further cut down the
1221 tests the following is possible:
1224 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
1227 This will run all @command{gcc} execute tests in the testsuite.
1230 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
1233 This will run the @command{g++} ``old-deja'' tests in the testsuite where the filename
1234 matches @samp{9805*}.
1236 The @file{*.exp} files are located in the testsuite directories of the GCC
1237 source, the most important ones being @file{compile.exp},
1238 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
1239 To get a list of the possible @file{*.exp} files, pipe the
1240 output of @samp{make check} into a file and look at the
1241 @samp{Running @dots{} .exp} lines.
1243 @section How to interpret test results
1245 After the testsuite has run you'll find various @file{*.sum} and @file{*.log}
1246 files in the testsuite subdirectories. The @file{*.log} files contain a
1247 detailed log of the compiler invocations and the corresponding
1248 results, the @file{*.sum} files summarize the results. These summaries list
1249 all the tests that have been run with a corresponding status code:
1253 PASS: the test passed as expected
1255 XPASS: the test unexpectedly passed
1257 FAIL: the test unexpectedly failed
1259 XFAIL: the test failed as expected
1261 UNSUPPORTED: the test is not supported on this platform
1263 ERROR: the testsuite detected an error
1265 WARNING: the testsuite detected a possible problem
1268 It is normal for some tests to report unexpected failures. At the
1269 current time our testing harness does not allow fine grained control
1270 over whether or not a test is expected to fail. We expect to fix this
1271 problem in future releases.
1274 @section Submitting test results
1276 If you want to report the results to the GCC project, use the
1277 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
1280 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
1281 -m gcc-testresults@@gcc.gnu.org |sh
1284 This script uses the @command{Mail} program to send the results, so
1285 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
1286 prepended to the testsuite summary and should contain any special
1287 remarks you have on your results or your build environment. Please
1288 do not edit the testsuite result block or the subject line, as these
1289 messages are automatically parsed and presented at the
1290 @uref{http://gcc.gnu.org/testresults/,,GCC testresults} web
1291 page. Here you can also gather information on how specific tests
1292 behave on different platforms and compare them with your results. A
1293 few failing testcases are possible even on released versions and you
1294 should look here first if you think your results are unreasonable.
1301 @uref{./index.html,,Return to the GCC Installation page}
1305 @c ***Final install***********************************************************
1307 @comment node-name, next, previous, up
1308 @node Final install, , Testing, Installing GCC
1310 @ifset finalinstallhtml
1312 @chapter Installing GCC: Final installation
1315 Now that GCC has been built (and optionally tested), you can install it with
1317 cd @var{objdir}; make install
1320 We strongly recommend to install into a target directory where there is
1321 no previous version of GCC present.
1323 That step completes the installation of GCC; user level binaries can
1324 be found in @file{@var{prefix}/bin} where @var{prefix} is the value you
1325 specified with the @option{--prefix} to configure (or @file{/usr/local}
1326 by default). (If you specified @option{--bindir}, that directory will
1327 be used instead; otherwise, if you specified @option{--exec-prefix},
1328 @file{@var{exec-prefix}/bin} will be used.) Headers for the C++ and
1329 Java libraries are installed in @file{@var{prefix}/include}; libraries
1330 in @file{@var{libdir}} (normally @file{@var{prefix}/lib}); internal
1331 parts of the compiler in @file{@var{libdir}/gcc-lib}; documentation in
1332 info format in @file{@var{infodir}} (normally @file{@var{prefix}/info}).
1334 If you built a released version of GCC using @samp{make bootstrap} then please
1335 quickly review the build status page for your release, available from
1336 @uref{http://gcc.gnu.org/buildstat.html}.
1337 If your system is not listed for the version of GCC that you built,
1339 @email{gcc@@gcc.gnu.org} indicating
1340 that you successfully built and installed GCC.
1341 Include the following information:
1345 Output from running @file{@var{srcdir}/config.guess}. Do not send us
1346 that file itself, just the one-line output from running it.
1349 The output of @samp{gcc -v} for your newly installed gcc.
1350 This tells us which version of GCC you built and the options you passed to
1354 Whether you enabled all languages or a subset of them. If you used a
1355 full distribution then this information is part of the configure
1356 options in the output of @samp{gcc -v}, but if you downloaded the
1357 ``core'' compiler plus additional front ends then it isn't apparent
1358 which ones you built unless you tell us about it.
1361 If the build was for GNU/Linux, also include:
1364 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
1365 this information should be available from @file{/etc/issue}.
1368 The version of the Linux kernel, available from @samp{uname --version}
1372 The version of glibc you used; for RPM-based systems like Red Hat,
1373 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
1374 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
1376 For other systems, you can include similar information if you think it is
1380 Any other information that you think would be useful to people building
1381 GCC on the same configuration. The new entry in the build status list
1382 will include a link to the archived copy of your message.
1385 We'd also like to know if the
1387 @ref{Specific, host/target specific installation notes}
1390 @uref{specific.html,,host/target specific installation notes}
1392 didn't include your host/target information or if that information is
1393 incomplete or out of date. Send a note to
1394 @email{gcc@@gcc.gnu.org} telling us how the information should be changed.
1396 If you find a bug, please report it following our
1397 @uref{../bugs.html,,bug reporting guidelines}.
1399 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
1400 dvi}. You will need to have @command{texi2dvi} (version at least 4.1)
1401 and @TeX{} installed. This creates a number of @file{.dvi} files in
1402 subdirectories of @file{@var{objdir}}; these may be converted for
1403 printing with programs such as @command{dvips}. You can also
1404 @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the
1405 Free Software Foundation}, though such manuals may not be for the most
1406 recent version of GCC@.
1413 @uref{./index.html,,Return to the GCC Installation page}
1417 @c ***Binaries****************************************************************
1419 @comment node-name, next, previous, up
1420 @node Binaries, Specific, Installing GCC, Top
1424 @chapter Installing GCC: Binaries
1427 @cindex Installing GCC: Binaries
1429 We are often asked about pre-compiled versions of GCC@. While we cannot
1430 provide these for all platforms, below you'll find links to binaries for
1431 various platforms where creating them by yourself is not easy due to various
1434 Please note that we did not create these binaries, nor do we
1435 support them. If you have any problems installing them, please
1436 contact their makers.
1443 @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX};
1446 @uref{http://aixpdslib.seas.ucla.edu,,UCLA Software Library for AIX}.
1450 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}.
1453 Hitachi H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
1454 Development Tools for the Hitachi H8/300[HS] Series}.
1460 @uref{http://hpux.cae.wisc.edu/,,HP-UX Porting Center};
1463 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
1467 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
1468 OpenServer/Unixware}.
1471 Sinix/Reliant Unix---@uref{ftp://ftp.siemens.de/sni/mr/pd/gnu/gcc,,Siemens}.
1474 Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware}.
1477 SGI---@uref{http://freeware.sgi.com/,,SGI Freeware}.
1480 Windows 95, 98, and NT:
1483 The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project;
1485 The @uref{http://www.mingw.org/,,MinGW} project.
1489 @uref{ftp://ftp.thewrittenword.com/packages/free/by-name/,,The
1490 Written Word} offers binaries for Solaris 2.5.1, 2.6, 2.7/SPARC, 2.7/Intel,
1491 IRIX 6.2, 6.5, Digital UNIX 4.0D, HP-UX 10.20, and HP-UX 11.00.
1495 In addition to those specific offerings, you can get a binary
1496 distribution CD-ROM from the
1497 @uref{http://www.fsf.org/order/order.html,,Free Software Foundation}.
1498 It contains binaries for a number of platforms, and
1499 includes not only GCC, but other stuff as well. The current CD does
1500 not contain the latest version of GCC, but it should allow
1501 bootstrapping the compiler. An updated version of that disk is in the
1509 @uref{./index.html,,Return to the GCC Installation page}
1513 @c ***Specific****************************************************************
1515 @comment node-name, next, previous, up
1516 @node Specific, Old, Binaries, Top
1520 @chapter Host/target specific installation notes for GCC
1523 @cindex Specific installation notes
1524 @cindex Target specific installation
1525 @cindex Host specific installation
1526 @cindex Target specific installation notes
1528 Please read this document carefully @emph{before} installing the
1529 GNU Compiler Collection on your machine.
1534 @uref{#alpha*-*-*,,alpha*-*-*}
1536 @uref{#alpha*-dec-osf*,,alpha*-dec-osf*}
1538 @uref{#alphaev5-cray-unicosmk*,,alphaev5-cray-unicosmk*}
1540 @uref{#arc-*-elf,,arc-*-elf}
1542 @uref{#arm-*-aout,,arm-*-aout}
1544 @uref{#arm-*-elf,,arm-*-elf}
1546 @uref{#arm*-*-linux-gnu,,arm*-*-linux-gnu}
1554 @uref{#dsp16xx,,dsp16xx}
1556 @uref{#*-*-freebsd*,,*-*-freebsd*}
1558 @uref{#h8300-hms,,h8300-hms}
1560 @uref{#hppa*-hp-hpux*,,hppa*-hp-hpux*}
1562 @uref{#hppa*-hp-hpux9,,hppa*-hp-hpux9}
1564 @uref{#hppa*-hp-hpux10,,hppa*-hp-hpux10}
1566 @uref{#hppa*-hp-hpux11,,hppa*-hp-hpux11}
1568 @uref{#i370-*-*,,i370-*-*}
1570 @uref{#*-*-linux-gnu,,*-*-linux-gnu}
1572 @uref{#ix86-*-linux*aout,,i?86-*-linux*aout}
1574 @uref{#ix86-*-linux*,,i?86-*-linux*}
1576 @uref{#ix86-*-sco,,i?86-*-sco}
1578 @uref{#ix86-*-sco3.2v4,,i?86-*-sco3.2v4}
1580 @uref{#ix86-*-sco3.2v5*,,i?86-*-sco3.2v5*}
1582 @uref{#ix86-*-udk,,i?86-*-udk}
1584 @uref{#ix86-*-esix,,i?86-*-esix}
1586 @uref{#ia64-*-linux,,ia64-*-linux}
1588 @uref{#*-lynx-lynxos,,*-lynx-lynxos}
1590 @uref{#*-ibm-aix*,,*-ibm-aix*}
1592 @uref{#ip2k-*-elf,,ip2k-*-elf}
1594 @uref{#m32r-*-elf,,m32r-*-elf}
1596 @uref{#m68000-hp-bsd,,m68000-hp-bsd}
1598 @uref{#m6811-elf,,m6811-elf}
1600 @uref{#m6812-elf,,m6812-elf}
1602 @uref{#m68k-att-sysv,,m68k-att-sysv}
1604 @uref{#m68k-crds-unos,,m68k-crds-unos}
1606 @uref{#m68k-hp-hpux,,m68k-hp-hpux}
1608 @uref{#m68k-ncr-*,,m68k-ncr-*}
1610 @uref{#m68k-sun,,m68k-sun}
1612 @uref{#m68k-sun-sunos4.1.1,,m68k-sun-sunos4.1.1}
1614 @uref{#mips-*-*,,mips-*-*}
1616 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
1618 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
1620 @uref{#powerpc*-*-*,,powerpc*-*-*, powerpc-*-sysv4}
1622 @uref{#powerpc-*-darwin*,,powerpc-*-darwin*}
1624 @uref{#powerpc-*-elf,,powerpc-*-elf, powerpc-*-sysv4}
1626 @uref{#powerpc-*-linux-gnu*,,powerpc-*-linux-gnu*}
1628 @uref{#powerpc-*-netbsd*,,powerpc-*-netbsd*}
1630 @uref{#powerpc-*-eabiaix,,powerpc-*-eabiaix}
1632 @uref{#powerpc-*-eabisim,,powerpc-*-eabisim}
1634 @uref{#powerpc-*-eabi,,powerpc-*-eabi}
1636 @uref{#powerpcle-*-elf,,powerpcle-*-elf, powerpcle-*-sysv4}
1638 @uref{#powerpcle-*-eabisim,,powerpcle-*-eabisim}
1640 @uref{#powerpcle-*-eabi,,powerpcle-*-eabi}
1642 @uref{#powerpcle-*-winnt,,powerpcle-*-winnt, powerpcle-*-pe}
1644 @uref{#s390-*-linux*}
1646 @uref{#s390x-*-linux*}
1648 @uref{#*-*-solaris2*,,*-*-solaris2*}
1650 @uref{#sparc-sun-solaris2*,,sparc-sun-solaris2*}
1652 @uref{#sparc-sun-solaris2.7,,sparc-sun-solaris2.7}
1654 @uref{#sparc-sun-sunos4*,,sparc-sun-sunos4*}
1656 @uref{#sparc-unknown-linux-gnulibc1,,sparc-unknown-linux-gnulibc1}
1658 @uref{#sparc-*-linux*,,sparc-*-linux*}
1660 @uref{#sparc64-*-*,,sparc64-*-*}
1662 @uref{#sparcv9-*-solaris2*,,sparcv9-*-solaris2*}
1664 @uref{#*-*-sysv*,,*-*-sysv*}
1666 @uref{#vax-dec-ultrix,,vax-dec-ultrix}
1668 @uref{#xtensa-*-elf,,xtensa-*-elf}
1670 @uref{#xtensa-*-linux*,,xtensa-*-linux*}
1672 @uref{#windows,,Microsoft Windows}
1676 @uref{#older,,Older systems}
1681 @uref{#elf_targets,,all ELF targets} (SVR4, Solaris 2, etc.)
1687 <!-- -------- host/target specific issues start here ---------------- -->
1690 @heading @anchor{alpha*-*-*}alpha*-*-*
1692 This section contains general configuration information for all
1693 alpha-based platforms using ELF (in particular, ignore this section for
1694 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
1695 section, please read all other sections that match your target.
1697 We require binutils 2.11.2 or newer.
1698 Previous binutils releases had a number of problems with DWARF 2
1699 debugging information, not the least of which is incorrect linking of
1706 @heading @anchor{alpha*-dec-osf*}alpha*-dec-osf*
1707 Systems using processors that implement the DEC Alpha architecture and
1708 are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
1709 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
1711 As of GCC 3.2, versions before @code{alpha*-dec-osf4} are no longer
1712 supported. (These are the versions which identify themselves as DEC
1715 In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
1716 currently (2001-06-13) work with @command{mips-tfile}. As a workaround,
1717 we need to use the old assembler, invoked via the barely documented
1718 @option{-oldas} option. To bootstrap GCC, you either need to use the
1722 % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
1725 or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
1728 % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
1731 As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld}
1732 are supported on Tru64 UNIX, so you must not configure GCC with
1733 @option{--with-gnu-as} or @option{--with-gnu-ld}.
1735 The @option{--enable-threads} options isn't supported yet. A patch is
1736 in preparation for a future release.
1738 GCC writes a @samp{.verstamp} directive to the assembler output file
1739 unless it is built as a cross-compiler. It gets the version to use from
1740 the system header file @file{/usr/include/stamp.h}. If you install a
1741 new version of DEC Unix, you should rebuild GCC to pick up the new version
1744 Note that since the Alpha is a 64-bit architecture, cross-compilers from
1745 32-bit machines will not generate code as efficient as that generated
1746 when the compiler is running on a 64-bit machine because many
1747 optimizations that depend on being able to represent a word on the
1748 target in an integral value on the host cannot be performed. Building
1749 cross-compilers on the Alpha for 32-bit machines has only been tested in
1750 a few cases and may not work properly.
1752 @code{make compare} may fail on old versions of DEC Unix unless you add
1753 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
1754 assembler input file is stored in the object file, and that makes
1755 comparison fail if it differs between the @code{stage1} and
1756 @code{stage2} compilations. The option @option{-save-temps} forces a
1757 fixed name to be used for the assembler input file, instead of a
1758 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
1759 unless the comparisons fail without that option. If you add
1760 @option{-save-temps}, you will have to manually delete the @samp{.i} and
1761 @samp{.s} files after each series of compilations.
1763 GCC now supports both the native (ECOFF) debugging format used by DBX
1764 and GDB and an encapsulated STABS format for use only with GDB@. See the
1765 discussion of the @option{--with-stabs} option of @file{configure} above
1766 for more information on these formats and how to select them.
1768 There is a bug in DEC's assembler that produces incorrect line numbers
1769 for ECOFF format when the @samp{.align} directive is used. To work
1770 around this problem, GCC will not emit such alignment directives
1771 while writing ECOFF format debugging information even if optimization is
1772 being performed. Unfortunately, this has the very undesirable
1773 side-effect that code addresses when @option{-O} is specified are
1774 different depending on whether or not @option{-g} is also specified.
1776 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
1777 DBX@. DEC is now aware of this problem with the assembler and hopes to
1778 provide a fix shortly.
1784 @heading @anchor{alphaev5-cray-unicosmk*}alphaev5-cray-unicosmk*
1785 Cray T3E systems running Unicos/Mk.
1787 This port is incomplete and has many known bugs. We hope to improve the
1788 support for this target soon. Currently, only the C front end is supported,
1789 and it is not possible to build parallel applications. Cray modules are not
1790 supported; in particular, Craylibs are assumed to be in
1791 @file{/opt/ctl/craylibs/craylibs}.
1793 You absolutely @strong{must} use GNU make on this platform. Also, you
1794 need to tell GCC where to find the assembler and the linker. The
1795 simplest way to do so is by providing @option{--with-as} and
1796 @option{--with-ld} to @file{configure}, e.g.@:
1798 @samp{configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld
1799 --enable-languages=c}
1801 The comparison test during @samp{make bootstrap} fails on Unicos/Mk
1802 because the assembler inserts timestamps into object files. You should
1803 be able to work around this by doing @samp{make all} after getting this
1810 @heading @anchor{arc-*-elf}arc-*-elf
1811 Argonaut ARC processor.
1812 This configuration is intended for embedded systems.
1818 @heading @anchor{arm-*-aout}arm-*-aout
1819 Advanced RISC Machines ARM-family processors. These are often used in
1820 embedded applications. There are no standard Unix configurations.
1821 This configuration corresponds to the basic instruction sequences and will
1822 produce @file{a.out} format object modules.
1824 You may need to make a variant of the file @file{arm.h} for your particular
1831 @heading @anchor{arm-*-elf}arm-*-elf
1832 This configuration is intended for embedded systems.
1838 @heading @anchor{arm*-*-linux-gnu}arm*-*-linux-gnu
1840 We require GNU binutils 2.10 or newer.
1846 @heading @anchor{avr}avr
1848 ATMEL AVR-family micro controllers. These are used in embedded
1849 applications. There are no standard Unix configurations.
1851 @xref{AVR Options,, AVR Options, gcc, Using and Porting the GNU Compiler
1855 See ``AVR Options'' in the main manual
1857 for the list of supported MCU types.
1859 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
1861 Further installation notes and other useful information about AVR tools
1862 can also be obtained from:
1866 @uref{http://home.overta.ru/users/denisc,,http://home.overta.ru/users/denisc}
1868 @uref{http://www.amelek.gda.pl/avr,,http://www.amelek.gda.pl/avr}
1871 We @emph{strongly} recommend using binutils 2.11 or newer.
1873 The following error:
1875 Error: register required
1878 indicates that you should upgrade to a newer version of the binutils.
1884 @heading @anchor{c4x}c4x
1886 Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal
1887 Processors. These are used in embedded applications. There are no
1888 standard Unix configurations.
1890 @xref{TMS320C3x/C4x Options,, TMS320C3x/C4x Options, gcc, Using and
1891 Porting the GNU Compiler Collection (GCC)},
1894 See ``TMS320C3x/C4x Options'' in the main manual
1896 for the list of supported MCU types.
1898 GCC can be configured as a cross compiler for both the C3x and C4x
1899 architectures on the same system. Use @samp{configure --target=c4x
1900 --enable-languages="c,c++"} to configure.
1903 Further installation notes and other useful information about C4x tools
1904 can also be obtained from:
1908 @uref{http://www.elec.canterbury.ac.nz/c4x/,,http://www.elec.canterbury.ac.nz/c4x/}
1915 @heading @anchor{cris}CRIS
1917 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
1918 series. These are used in embedded applications.
1921 @xref{CRIS Options,, CRIS Options, gcc, Using and Porting the GNU Compiler
1925 See ``CRIS Options'' in the main manual
1927 for a list of CRIS-specific options.
1929 There are a few different CRIS targets:
1931 @item cris-axis-aout
1932 Old target. Includes a multilib for the @samp{elinux} a.out-based
1933 target. No multilibs for newer architecture variants.
1935 Mainly for monolithic embedded systems. Includes a multilib for the
1936 @samp{v10} core used in @samp{ETRAX 100 LX}.
1937 @item cris-axis-linux-gnu
1938 A GNU/Linux port for the CRIS architecture, currently targeting
1939 @samp{ETRAX 100 LX} by default.
1942 For @code{cris-axis-aout} and @code{cris-axis-elf} you need binutils 2.11
1943 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
1945 Pre-packaged tools can be obtained from
1946 @uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More
1947 information about this platform is available at
1948 @uref{http://developer.axis.com/}.
1954 @heading @anchor{dos}DOS
1956 Please have a look at our @uref{binaries.html,,binaries page}.
1958 You cannot install GCC by itself on MSDOS; it will not compile under
1959 any MSDOS compiler except itself. You need to get the complete
1960 compilation package DJGPP, which includes binaries as well as sources,
1961 and includes all the necessary compilation tools and libraries.
1967 @heading @anchor{dsp16xx}dsp16xx
1968 A port to the AT&T DSP1610 family of processors.
1974 @heading @anchor{*-*-freebsd*}*-*-freebsd*
1976 The version of binutils installed in @file{/usr/bin} is known to work unless
1977 otherwise specified in any per-architecture notes. However, binutils
1978 2.12.1 or greater is known to improve overall testsuite results.
1980 FreeBSD 1 is no longer supported in GCC 3.2.
1982 For FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
1983 configuration support and files as shipped with GCC 2.95 are still in
1984 place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
1985 it is unknown which version of binutils was used (it is assumed that it
1986 was the system copy in @file{/usr/bin}) and C++ EH failures were noted.
1988 For FreeBSD using the ELF file format: DWARF 2 debugging is now the
1989 default for all CPU architectures. It had been the default on
1990 FreeBSD/alpha since its inception. You may use @option{-gstabs} instead
1991 of @option{-g}, if you really want the old debugging format. There are
1992 no known issues with mixing object files and libraries with different
1993 debugging formats. Otherwise, this release of GCC should now match more
1994 of the configuration used in the stock FreeBSD configuration of GCC. In
1995 particular, @option{--enable-threads} is now configured by default.
1996 However, as a general user, do not attempt to replace the system
1997 compiler with this release. Known to bootstrap and check with good
1998 results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4, 4.5-STABLE and 5-CURRENT@.
2000 In principle, @option{--enable-threads} is now compatible with
2001 @option{--enable-libgcj} on FreeBSD@. However, it has only been built
2002 and tested on i386-*-freebsd4.5 and alpha-*-freebsd5.0. The static
2003 library may be incorrectly built (symbols are missing at link time).
2004 There is a rare timing-based startup hang (probably involves an
2005 assupmtion about the thread library). Multi-threaded boehm-gc (required for
2006 libjava) exposes severe threaded signal-handling bugs on FreeBSD before
2007 4.5-RELEASE. The alpha port may not fully bootstrap without some manual
2008 intervention: gcjh will crash with a floating-point exception while
2009 generating @file{java/lang/Double.h} (just copy the version built on
2010 i386-*-freebsd* and rerun the top-level gmake with no arguments and it
2011 should properly complete the bootstrap). Other CPU architectures
2012 supported by FreeBSD will require additional configuration tuning in, at
2013 the very least, both boehm-gc and libffi.
2015 Shared @file{libgcc_s.so} is now built and installed by default.
2021 @heading @anchor{h8300-hms}h8300-hms
2022 Hitachi H8/300 series of processors.
2024 Please have a look at our @uref{binaries.html,,binaries page}.
2026 The calling convention and structure layout has changed in release 2.6.
2027 All code must be recompiled. The calling convention now passes the
2028 first three arguments in function calls in registers. Structures are no
2029 longer a multiple of 2 bytes.
2035 @heading @anchor{hppa*-hp-hpux*}hppa*-hp-hpux*
2037 We @emph{highly} recommend using gas/binutils 2.8 or newer on all hppa
2038 platforms; you may encounter a variety of problems when using the HP
2039 assembler. The HP assembler does not work with the @samp{hppa64-hp-hpux11*}
2042 Specifically, @option{-g} does not work on HP-UX (since that system
2043 uses a peculiar debugging format which GCC does not know about), unless you
2044 use GAS and GDB and configure GCC with the
2045 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
2046 @option{--with-as=@dots{}} options.
2048 If you wish to use the pa-risc 2.0 architecture support with a 32-bit
2049 runtime, you must use either the HP assembler, gas/binutils 2.11 or newer,
2051 @uref{ftp://sources.redhat.com/pub/binutils/snapshots,,snapshot of gas}.
2053 There are two default scheduling models for instructions. These are
2054 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
2055 architecture specified for the target machine when configuring.
2056 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
2057 the target is a @samp{hppa1*} machine.
2059 The PROCESSOR_8000 model is not well suited to older processors. Thus,
2060 it is important to completely specify the machine architecture when
2061 configuring if you want a model other than PROCESSOR_8000. The macro
2062 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
2063 default scheduling model is desired.
2065 More specific information to @samp{hppa*-hp-hpux*} targets follows.
2071 @heading @anchor{hppa*-hp-hpux9}hppa*-hp-hpux9
2073 The HP assembler has major problems on this platform. We've tried to work
2074 around the worst of the problems. However, those workarounds may be causing
2075 linker crashes in some circumstances; the workarounds also probably prevent
2076 shared libraries from working. Use the GNU assembler to avoid these problems.
2079 The configuration scripts for GCC will also trigger a bug in the hpux9
2080 shell. To avoid this problem set @env{CONFIG_SHELL} to @file{/bin/ksh}
2081 and @env{SHELL} to @file{/bin/ksh} in your environment.
2088 @heading @anchor{hppa*-hp-hpux10}hppa*-hp-hpux10
2090 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
2091 @code{PHCO_19798} from HP@. HP has two sites which provide patches free of
2097 <a href="http://us-support.external.hp.com">US, Canada, Asia-Pacific, and
2101 @uref{http://us-support.external.hp.com,,}US, Canada, Asia-Pacific, and
2105 @uref{http://europe-support.external.hp.com,,Europe}
2108 The HP assembler on these systems is much better than the hpux9 assembler,
2109 but still has some problems. Most notably the assembler inserts timestamps
2110 into each object file it creates, causing the 3-stage comparison test to fail
2111 during a @samp{make bootstrap}. You should be able to continue by
2112 saying @samp{make all} after getting the failure from @samp{make
2120 @heading @anchor{hppa*-hp-hpux11}hppa*-hp-hpux11
2122 GCC 3.0 and up support HP-UX 11. On 64-bit capable systems, there
2123 are two distinct ports. The @samp{hppa2.0w-hp-hpux11*} port generates
2124 code for the 32-bit pa-risc runtime architecture. It uses the HP
2125 linker and is currently the default selected by config.guess. The
2126 optional @samp{hppa64-hp-hpux11*} port generates 64-bit code for the
2127 pa-risc 2.0 architecture. It must be explicitly selected using the
2128 @samp{--host=hppa64-hp-hpux11*} configure option. Different prefixes
2129 must be used if both ports are to be installed on the same system.
2131 You must use GNU binutils 2.11 or above with the 32-bit port. Thread
2132 support is not currently implemented, so @option{--enable-threads} does
2133 not work. See @uref{http://gcc.gnu.org/ml/gcc-prs/2002-01/msg00551.html}
2134 and @uref{http://gcc.gnu.org/ml/gcc-bugs/2002-01/msg00663.html}.
2135 GCC 2.95.x is not supported under HP-UX 11 and cannot be used to
2136 compile GCC 3.0 and up. Refer to @uref{binaries.html,,binaries} for
2137 information about obtaining precompiled GCC binaries for HP-UX.
2139 GNU binutils 2.13 or later is recommended with the 64-bit port.
2140 The HP assembler is not supported. It is @emph{highly} recommended
2141 that the GNU linker be used as well. Either binutils must be built
2142 prior to gcc, or a binary distribution of gcc or binutils must be
2143 obtained for the initial builds. When starting with a HP compiler,
2144 it is preferable to use the ANSI compiler as the bundled compiler
2145 only supports traditional C. Bootstrapping with the bundled compiler
2146 is tested infrequently and problems often arise because of the subtle
2147 differences in semantics between traditional and ISO C. There also
2148 have been problems reported with various binary distributions. This
2149 port still is undergoing significant development.
2155 @heading @anchor{i370-*-*}i370-*-*
2156 This port is very preliminary and has many known bugs. We hope to
2157 have a higher-quality port for this machine soon.
2163 @heading @anchor{*-*-linux-gnu}*-*-linux-gnu
2165 If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install
2166 out-of-the-box. You'll get compile errors while building @samp{libstdc++}.
2167 The patch @uref{glibc-2.2.patch,,glibc-2.2.patch}, that is to be
2168 applied in the GCC source tree, fixes the compatibility problems.
2178 Currently Glibc 2.2.3 (and older releases) and GCC 3.0 are out of sync
2179 since the latest exception handling changes for GCC@. Compiling glibc
2180 with GCC 3.0 will give a binary incompatible glibc and therefore cause
2181 lots of problems and might make your system completly unusable. This
2182 will definitly need fixes in glibc but might also need fixes in GCC@. We
2183 strongly advise to wait for glibc 2.2.4 and to read the release notes of
2184 glibc 2.2.4 whether patches for GCC 3.0 are needed. You can use glibc
2185 2.2.3 with GCC 3.0, just do not try to recompile it.
2191 @heading @anchor{ix86-*-linux*aout}i?86-*-linux*aout
2192 Use this configuration to generate @file{a.out} binaries on Linux-based
2193 GNU systems. This configuration is being superseded. You must use
2194 gas/binutils version 2.5.2 or later.
2200 @heading @anchor{ix86-*-linux*}i?86-*-linux*
2202 You will need binutils 2.9.1.0.15 or newer for exception handling to work.
2204 If you receive Signal 11 errors when building on GNU/Linux, then it is
2205 possible you have a hardware problem. Further information on this can be
2206 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
2212 @heading @anchor{ix86-*-sco}i?86-*-sco
2213 Compilation with RCC is recommended. Also, it may be a good idea to
2214 link with GNU malloc instead of the malloc that comes with the system.
2220 @heading @anchor{ix86-*-sco3.2v4}i?86-*-sco3.2v4
2221 Use this configuration for SCO release 3.2 version 4.
2227 @heading @anchor{ix86-*-sco3.2v5*}i?86-*-sco3.2v5*
2228 Use this for the SCO OpenServer Release 5 family of operating systems.
2230 Unlike earlier versions of GCC, the ability to generate COFF with this
2231 target is no longer provided.
2233 Earlier versions of GCC emitted DWARF 1 when generating ELF to allow
2234 the system debugger to be used. That support was too burdensome to
2235 maintain. GCC now emits only DWARF 2 for this target. This means you
2236 may use either the UDK debugger or GDB to debug programs built by this
2239 Use of the @option{-march=pentiumpro} flag can result in
2240 unrecognized opcodes when using the native assembler on OS versions before
2241 5.0.6. (Support for P6 opcodes was added to the native ELF assembler in
2242 that version.) While it's rather rare to see these emitted by GCC yet,
2243 errors of the basic form:
2246 /usr/tmp/ccaNlqBc.s:22:unknown instruction: fcomip
2247 /usr/tmp/ccaNlqBc.s:50:unknown instruction: fucomip
2250 are symptoms of this problem. You may work around this by not
2251 building affected files with that flag, by using the GNU assembler, or
2252 by using the assembler provided with the current version of the OS@.
2253 Users of GNU assembler should see the note below for hazards on doing
2256 The native SCO assembler that is provided with the OS at no
2257 charge is normally required. If, however, you must be able to use
2258 the GNU assembler (perhaps you're compiling code with asms that
2259 require GAS syntax) you may configure this package using the flags
2260 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You must
2261 use a recent version of GNU binutils; versions past 2.9.1 seem to work
2264 In general, the @option{--with-gnu-as} option isn't as well tested
2265 as the native assembler.
2267 Look in @file{gcc/config/i386/sco5.h} (search for ``messy'') for
2268 additional OpenServer-specific flags.
2270 Systems based on OpenServer before 5.0.4 (@samp{uname -X}
2271 will tell you what you're running) require TLS597 from
2272 @uref{ftp://ftp.sco.com/TLS/,,ftp://ftp.sco.com/TLS/}
2273 for C++ constructors and destructors to work right.
2275 The system linker in (at least) 5.0.4 and 5.0.5 will sometimes
2276 do the wrong thing for a construct that GCC will emit for PIC
2277 code. This can be seen as execution testsuite failures when using
2278 @option{-fPIC} on @file{921215-1.c}, @file{931002-1.c}, @file{nestfunc-1.c}, and @file{gcov-1.c}.
2279 For 5.0.5, an updated linker that will cure this problem is
2280 available. You must install both
2281 @uref{ftp://ftp.sco.com/Supplements/rs505a/,,ftp://ftp.sco.com/Supplements/rs505a/}
2282 and @uref{ftp://ftp.sco.com/SLS/,,OSS499A}.
2284 The dynamic linker in OpenServer 5.0.5 (earlier versions may show
2285 the same problem) aborts on certain G77-compiled programs. It's particularly
2286 likely to be triggered by building Fortran code with the @option{-fPIC} flag.
2287 Although it's conceivable that the error could be triggered by other
2288 code, only G77-compiled code has been observed to cause this abort.
2289 If you are getting core dumps immediately upon execution of your
2290 G77 program---and especially if it's compiled with @option{-fPIC}---try applying
2291 @uref{sco_osr5_g77.patch,,@file{sco_osr5_g77.patch}} to your @samp{libf2c} and
2293 Affected faults, when analyzed in a debugger, will show a stack
2294 backtrace with a fault occurring in @code{rtld()} and the program
2295 running as @file{/usr/lib/ld.so.1}. This problem has been reported to SCO
2296 engineering and will hopefully be addressed in later releases.
2303 @heading @anchor{ix86-*-udk}i?86-*-udk
2305 This target emulates the SCO Universal Development Kit and requires that
2306 package be installed. (If it is installed, you will have a
2307 @file{/udk/usr/ccs/bin/cc} file present.) It's very much like the
2308 @samp{i?86-*-unixware7*} target
2309 but is meant to be used when hosting on a system where UDK isn't the
2310 default compiler such as OpenServer 5 or Unixware 2. This target will
2311 generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
2312 with the same warnings and caveats as the SCO UDK@.
2314 This target is a little tricky to build because we have to distinguish
2315 it from the native tools (so it gets headers, startups, and libraries
2316 from the right place) while making the tools not think we're actually
2317 building a cross compiler. The easiest way to do this is with a configure
2320 @samp{CC=/udk/usr/ccs/bin/cc @var{/your/path/to}/gcc/configure
2321 --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-}
2323 @emph{You should substitute @samp{i686} in the above command with the appropriate
2324 processor for your host.}
2326 After the usual @samp{make bootstrap} and
2327 @samp{make install}, you can then access the UDK-targeted GCC
2328 tools by adding @command{udk-} before the commonly known name. For
2329 example, to invoke the C compiler, you would use @command{udk-gcc}.
2330 They will coexist peacefully with any native-target GCC tools you may
2338 @heading @anchor{ia64-*-linux}ia64-*-linux
2339 IA-64 processor (also known as IPF, or Itanium Processor Family)
2342 The toolchain is not completely finished, so requirements will continue
2344 GCC 3.0.1 and later require glibc 2.2.4.
2345 GCC 3.0.2 requires binutils from 2001-09-05 or later.
2346 GCC 3.0.1 requires binutils 2.11.1 or later.
2348 None of the following versions of GCC has an ABI that is compatible
2349 with any of the other versions in this list, with the exception that
2350 Red Hat 2.96 and Trillian 000171 are compatible with each other:
2351 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
2352 This primarily affects C++ programs and programs that create shared libraries.
2353 Because of these ABI incompatibilities, GCC 3.0.2 is not recommended for
2354 user programs on GNU/Linux systems built using earlier compiler releases.
2355 GCC 3.0.2 is recommended for compiling linux, the kernel.
2356 GCC 3.0.2 is believed to be fully ABI compliant, and hence no more major
2357 ABI changes are expected.
2363 @heading @anchor{*-lynx-lynxos}*-lynx-lynxos
2364 LynxOS 2.2 and earlier comes with GCC 1.x already installed as
2365 @file{/bin/gcc}. You should compile with this instead of @file{/bin/cc}.
2366 You can tell GCC to use the GNU assembler and linker, by specifying
2367 @samp{--with-gnu-as --with-gnu-ld} when configuring. These will produce
2368 COFF format object files and executables; otherwise GCC will use the
2369 installed tools, which produce @file{a.out} format executables.
2374 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
2376 @heading @anchor{*-ibm-aix*}*-ibm-aix*
2378 AIX Make frequently has problems with GCC makefiles. GNU Make 3.76 or
2379 newer is recommended to build on this platform.
2381 Errors involving @code{alloca} when building GCC generally are due
2382 to an incorrect definition of @code{CC} in the Makefile or mixing files
2383 compiled with the native C compiler and GCC@. During the stage1 phase of
2384 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
2385 (not @command{xlc}). Once @command{configure} has been informed of
2386 @command{xlc}, one needs to use @samp{make distclean} to remove the
2387 configure cache files and ensure that @env{CC} environment variable
2388 does not provide a definition that will confuse @command{configure}.
2389 If this error occurs during stage2 or later, then the problem most likely
2390 is the version of Make (see above).
2392 The GNU Assembler incorrectly reports that it supports WEAK symbols on
2393 AIX which causes GCC to try to utilize weak symbol functionality which
2394 is not really supported on the platform. The native @command{as} and
2395 @command{ld} still are recommended. The native AIX tools do
2396 interoperate with GCC@.
2398 Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
2399 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1).
2401 @samp{libstdc++} in GCC 3.2 increments the major version number of the
2402 shared object and GCC installation places the @file{libstdc++.a}
2403 shared library in a common location which will overwrite the GCC 3.1
2404 version of the shared library. Applications either need to be
2405 re-linked against the new shared library or the GCC 3.1 version of the
2406 @samp{libstdc++} shared object needs to be available to the AIX
2407 runtime loader. The GCC 3.1 @samp{libstdc++.so.4} shared object can
2408 be installed for runtime dynamic loading using the following steps to
2409 set the @samp{F_LOADONLY} flag in the shared object for @emph{each}
2410 multilib @file{libstdc++.a} installed:
2412 Extract the shared object from each the GCC 3.1 @file{libstdc++.a}
2415 % ar -x libstdc++.a libstdc++.so.4
2418 Enable the @samp{F_LOADONLY} flag so that the shared object will be
2419 available for runtime dynamic loading, but not linking:
2421 % strip -e libstdc++.so.4
2424 Archive the runtime-only shared object in the GCC 3.2
2425 @file{libstdc++.a} archive:
2427 % ar -q libstdc++.a libstdc++.so.4
2430 Linking executables and shared libraries may produce warnings of
2431 duplicate symbols. The assembly files generated by GCC for AIX always
2432 have included multiple symbol definitions for certain global variable
2433 and function declarations in the original program. The warnings should
2434 not prevent the linker from producing a correct library or runnable
2437 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
2438 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
2439 to parse archive libraries did not handle the new format correctly.
2440 These routines are used by GCC and result in error messages during
2441 linking such as ``not a COFF file''. The version of the routines shipped
2442 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
2443 option of the archive command may be used to create archives of 32-bit
2444 objects using the original ``small format''. A correct version of the
2445 routines is shipped with AIX 4.3.2 and above.
2447 Some versions of the AIX binder (linker) can fail with a relocation
2448 overflow severe error when the @option{-bbigtoc} option is used to link
2449 GCC-produced object files into an executable that overflows the TOC@. A fix
2450 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
2451 available from IBM Customer Support and from its
2452 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2453 website as PTF U455193.
2455 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
2456 with a segmentation fault when invoked by any version of GCC@. A fix for
2457 APAR IX87327 is available from IBM Customer Support and from its
2458 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2459 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
2461 The initial assembler shipped with AIX 4.3.0 generates incorrect object
2462 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
2463 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
2464 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2465 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
2467 AIX provides National Language Support (NLS)@. Compilers and assemblers
2468 use NLS to support locale-specific representations of various data
2469 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
2470 separating decimal fractions). There have been problems reported where
2471 GCC does not produce the same floating-point formats that the assembler
2472 expects. If one encounters this problem, set the @env{LANG}
2473 environment variable to @samp{C} or @samp{En_US}.
2475 By default, GCC for AIX 4.1 and above produces code that can be used on
2476 both Power or PowerPC processors.
2478 A default can be specified with the @option{-mcpu=@var{cpu_type}}
2479 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
2485 @heading @anchor{ip2k-*-elf}ip2k-*-elf
2486 Ubicom IP2022 micro controller.
2487 This configuration is intended for embedded systems.
2488 There are no standard Unix configurations.
2490 Use @samp{configure --target=ip2k-elf --enable-languages=c} to configure GCC@.
2496 @heading @anchor{m32r-*-elf}m32r-*-elf
2497 Mitsubishi M32R processor.
2498 This configuration is intended for embedded systems.
2504 @heading @anchor{m68000-hp-bsd}m68000-hp-bsd
2505 HP 9000 series 200 running BSD@. Note that the C compiler that comes
2506 with this system cannot compile GCC; contact @email{law@@cygnus.com}
2507 to get binaries of GCC for bootstrapping.
2513 @heading @anchor{m6811-elf}m6811-elf
2514 Motorola 68HC11 family micro controllers. These are used in embedded
2515 applications. There are no standard Unix configurations.
2521 @heading @anchor{m6812-elf}m6812-elf
2522 Motorola 68HC12 family micro controllers. These are used in embedded
2523 applications. There are no standard Unix configurations.
2529 @heading @anchor{m68k-att-sysv}m68k-att-sysv
2530 AT&T 3b1, a.k.a.@: 7300 PC@. This version of GCC cannot
2531 be compiled with the system C compiler, which is too buggy.
2532 You will need to get a previous version of GCC and use it to
2533 bootstrap. Binaries are available from the OSU-CIS archive, at
2534 @uref{ftp://archive.cis.ohio-state.edu/pub/att7300/}.
2540 @heading @anchor{m68k-crds-unos}m68k-crds-unos
2541 Use @samp{configure unos} for building on Unos.
2543 The Unos assembler is named @code{casm} instead of @code{as}. For some
2544 strange reason linking @file{/bin/as} to @file{/bin/casm} changes the
2545 behavior, and does not work. So, when installing GCC, you should
2546 install the following script as @file{as} in the subdirectory where
2547 the passes of GCC are installed:
2554 The default Unos library is named @file{libunos.a} instead of
2555 @file{libc.a}. To allow GCC to function, either change all
2556 references to @option{-lc} in @file{gcc.c} to @option{-lunos} or link
2557 @file{/lib/libc.a} to @file{/lib/libunos.a}.
2559 @cindex @code{alloca}, for Unos
2560 When compiling GCC with the standard compiler, to overcome bugs in
2561 the support of @code{alloca}, do not use @option{-O} when making stage 2.
2562 Then use the stage 2 compiler with @option{-O} to make the stage 3
2563 compiler. This compiler will have the same characteristics as the usual
2564 stage 2 compiler on other systems. Use it to make a stage 4 compiler
2565 and compare that with stage 3 to verify proper compilation.
2567 (Perhaps simply defining @code{ALLOCA} in @file{x-crds} as described in
2568 the comments there will make the above paragraph superfluous. Please
2569 inform us of whether this works.)
2571 Unos uses memory segmentation instead of demand paging, so you will need
2572 a lot of memory. 5 Mb is barely enough if no other tasks are running.
2573 If linking @file{cc1} fails, try putting the object files into a library
2574 and linking from that library.
2580 @heading @anchor{m68k-hp-hpux}m68k-hp-hpux
2581 HP 9000 series 300 or 400 running HP-UX@. HP-UX version 8.0 has a bug in
2582 the assembler that prevents compilation of GCC@. This
2583 bug manifests itself during the first stage of compilation, while
2584 building @file{libgcc2.a}:
2588 cc1: warning: `-g' option not supported on this version of GCC
2589 cc1: warning: `-g1' option not supported on this version of GCC
2590 ./xgcc: Internal compiler error: program as got fatal signal 11
2593 A patched version of the assembler is available as the file
2594 @uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you
2595 have HP software support, the patch can also be obtained directly from
2596 HP, as described in the following note:
2599 This is the patched assembler, to patch SR#1653-010439, where the
2600 assembler aborts on floating point constants.
2602 The bug is not really in the assembler, but in the shared library
2603 version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is
2604 SR#4701-078451. Anyway, the attached assembler uses the archive
2605 library version of ``cvtnum(3c)'' and thus does not exhibit the bug.
2608 This patch is also known as PHCO_4484.
2610 In addition, if you wish to use gas, you must use
2611 gas version 2.1 or later, and you must use the GNU linker version 2.1 or
2612 later. Earlier versions of gas relied upon a program which converted the
2613 gas output into the native HP-UX format, but that program has not been
2614 kept up to date. gdb does not understand that native HP-UX format, so
2615 you must use gas if you wish to use gdb.
2617 On HP-UX version 8.05, but not on 8.07 or more recent versions, the
2618 @code{fixproto} shell script triggers a bug in the system shell. If you
2619 encounter this problem, upgrade your operating system or use BASH (the
2620 GNU shell) to run @code{fixproto}. This bug will cause the fixproto
2621 program to report an error of the form:
2624 ./fixproto: sh internal 1K buffer overflow
2627 To fix this, you can also change the first line of the fixproto script
2639 @heading @anchor{m68k-ncr-*}m68k-ncr-*
2640 On the Tower models 4@var{n}0 and 6@var{n}0, by default a process is not
2641 allowed to have more than one megabyte of memory. GCC cannot compile
2642 itself (or many other programs) with @option{-O} in that much memory.
2644 To solve this problem, reconfigure the kernel adding the following line
2645 to the configuration file:
2656 @heading @anchor{m68k-sun}m68k-sun
2657 Sun 3. We do not provide a configuration file to use the Sun FPA by
2658 default, because programs that establish signal handlers for floating
2659 point traps inherently cannot work with the FPA@.
2665 @heading @anchor{m68k-sun-sunos4.1.1}m68k-sun-sunos4.1.1
2667 It is reported that you may need the GNU assembler on this platform.
2674 @heading @anchor{mips-*-*}mips-*-*
2675 If on a MIPS system you get an error message saying ``does not have gp
2676 sections for all it's [sic] sectons [sic]'', don't worry about it. This
2677 happens whenever you use GAS with the MIPS linker, but there is not
2678 really anything wrong, and it is okay to use the output file. You can
2679 stop such warnings by installing the GNU linker.
2681 It would be nice to extend GAS to produce the gp tables, but they are
2682 optional, and there should not be a warning about their absence.
2684 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
2686 This configuration has considerable problems, which will be fixed in a
2689 In order to compile GCC on an SGI running IRIX 5, the ``compiler_dev.hdr''
2690 subsystem must be installed from the IDO CD-ROM supplied by Silicon
2691 Graphics. It is also available for download from
2692 @uref{http://www.sgi.com/developers/devtools/apis/ido.html,,http://www.sgi.com/developers/devtools/apis/ido.html}.
2694 @code{make compare} may fail on version 5 of IRIX unless you add
2695 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
2696 assembler input file is stored in the object file, and that makes
2697 comparison fail if it differs between the @code{stage1} and
2698 @code{stage2} compilations. The option @option{-save-temps} forces a
2699 fixed name to be used for the assembler input file, instead of a
2700 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
2701 unless the comparisons fail without that option. If you do you
2702 @option{-save-temps}, you will have to manually delete the @samp{.i} and
2703 @samp{.s} files after each series of compilations.
2705 If you use the MIPS C compiler to bootstrap, it may be necessary
2706 to increase its table size for switch statements with the
2707 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
2708 optimization option, you also need to use @option{-Olimit 3000}.
2710 To enable debugging under IRIX 5, you must use GNU @command{as} 2.11.2
2712 and use the @option{--with-gnu-as} configure option when configuring GCC.
2713 GNU @command{as} is distributed as part of the binutils package.
2714 When using release 2.11.2, you need to apply a patch
2715 @uref{http://sources.redhat.com/ml/binutils/2001-07/msg00352.html,,http://sources.redhat.com/ml/binutils/2001-07/msg00352.html}
2716 which will be included in the next release of binutils.
2718 When building GCC, the build process loops rebuilding @command{cc1} over
2719 and over again. This happens on @samp{mips-sgi-irix5.2}, and possibly
2720 other platforms. It has been reported that this is a known bug in the
2721 @command{make} shipped with IRIX 5.2. We recommend you use GNU
2722 @command{make} instead of the vendor supplied @command{make} program;
2723 however, you may have success with @command{smake} on IRIX 5.2 if you do
2724 not have GNU @command{make} available.
2730 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
2732 If you are using IRIX @command{cc} as your bootstrap compiler, you must
2733 ensure that the N32 ABI is in use. To test this, compile a simple C
2734 file with @command{cc} and then run @command{file} on the
2735 resulting object file. The output should look like:
2738 test.o: ELF N32 MSB @dots{}
2744 test.o: ELF 32-bit MSB @dots{}
2750 test.o: ELF 64-bit MSB @dots{}
2753 then your version of @command{cc} uses the O32 or N64 ABI by default. You
2754 should set the environment variable @env{CC} to @samp{cc -n32}
2755 before configuring GCC@.
2757 If you want the resulting @command{gcc} to run on old 32-bit systems
2758 with the MIPS R4400 CPU, you need to ensure that only code for the mips3
2759 instruction set architecture (ISA) is generated. While GCC 3.x does
2760 this correctly, both GCC 2.95 and SGI's MIPSpro @command{cc} may change
2761 the ISA depending on the machine where GCC is built. Using one of them
2762 as the bootstrap compiler may result in mips4 code, which won't run at
2763 all on mips3-only systems. For the test program above, you should see:
2766 test.o: ELF N32 MSB mips-3 @dots{}
2772 test.o: ELF N32 MSB mips-4 @dots{}
2775 instead, you should set the environment variable @env{CC} to @samp{cc
2776 -n32 -mips3} or @samp{gcc -mips3} respectively before configuring GCC@.
2778 GCC on IRIX 6 is usually built to support both the N32 and N64 ABIs. If
2779 you build GCC on a system that doesn't have the N64 libraries installed,
2780 you need to configure with @option{--disable-multilib} so GCC doesn't
2781 try to use them. Look for @file{/usr/lib64/libc.so.1} to see if you
2782 have the 64-bit libraries installed.
2784 You must @emph{not} use GNU @command{as} (which isn't built anyway as of
2785 binutils 2.11.2) on IRIX 6 platforms; doing so will only cause problems.
2787 GCC does not currently support generating O32 ABI binaries in the
2788 @samp{mips-sgi-irix6} configurations. It is possible to create a GCC
2789 with O32 ABI only support by configuring it for the @samp{mips-sgi-irix5}
2790 target and using a patched GNU @command{as} 2.11.2 as documented in the
2791 @uref{#mips-sgi-irix5,,@samp{mips-sgi-irix5}} section above. Using the
2792 native assembler requires patches to GCC which will be included in a
2793 future release. It is
2794 expected that O32 ABI support will be available again in a future release.
2796 The @option{--enable-threads} option doesn't currently work, a patch is
2797 in preparation for a future release. The @option{--enable-libgcj}
2798 option is disabled by default: IRIX 6 uses a very low default limit
2799 (20480) for the command line length. Although libtool contains a
2800 workaround for this problem, at least the N64 @samp{libgcj} is known not
2801 to build despite this, running into an internal error of the native
2802 @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
2803 its maximum of 262144 bytes. If you have root access, you can use the
2804 @command{systune} command to do this.
2806 GCC does not correctly pass/return structures which are
2807 smaller than 16 bytes and which are not 8 bytes. The problem is very
2808 involved and difficult to fix. It affects a number of other targets also,
2809 but IRIX 6 is affected the most, because it is a 64-bit target, and 4 byte
2810 structures are common. The exact problem is that structures are being padded
2811 at the wrong end, e.g.@: a 4 byte structure is loaded into the lower 4 bytes
2812 of the register when it should be loaded into the upper 4 bytes of the
2815 GCC is consistent with itself, but not consistent with the SGI C compiler
2816 (and the SGI supplied runtime libraries), so the only failures that can
2817 happen are when there are library functions that take/return such
2818 structures. There are very few such library functions. Currently this
2819 is known to affect @code{inet_ntoa}, @code{inet_lnaof},
2820 @code{inet_netof}, @code{inet_makeaddr}, and @code{semctl}. Until the
2821 bug is fixed, GCC contains workarounds for the known affected functions.
2823 See @uref{http://freeware.sgi.com/,,http://freeware.sgi.com/} for more
2824 information about using GCC on IRIX platforms.
2830 @heading @anchor{powerpc*-*-*}powerpc-*-*
2832 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
2833 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
2839 @heading @anchor{powerpc-*-darwin*}powerpc-*-darwin*
2840 PowerPC running Darwin (Mac OS X kernel).
2842 GCC 3.0 does not support Darwin, but 3.1 and later releases will work.
2844 Pre-installed versions of Mac OS X may not include any developer tools,
2845 meaning that you will not be able to build GCC from source. Tool
2846 binaries are available at
2847 @uref{http://www.opensource.apple.com/projects/darwin} (free
2848 registration required).
2850 Versions of the assembler prior to ``cctools-364'' cannot handle the
2851 4-argument form of rlwinm and related mask-using instructions. Darwin
2852 1.3 (Mac OS X 10.0) uses cctools-353 for instance. To get cctools-364,
2853 check out @file{cctools} with tag @samp{Apple-364}, build it, and
2854 install the assembler as @file{usr/bin/as}. See
2855 @uref{http://www.opensource.apple.com/tools/cvs/docs.html} for details.
2857 Also, the default stack limit of 512K is too small, and a bootstrap will
2858 typically fail when self-compiling @file{expr.c}. Set the stack to 800K
2859 or more, for instance by doing @samp{limit stack 800}. It's also
2860 convenient to use the GNU preprocessor instead of Apple's during the
2861 first stage of bootstrapping; this is automatic when doing @samp{make
2862 bootstrap}, but to do it from the toplevel objdir you will need to say
2863 @samp{make CC='cc -no-cpp-precomp' bootstrap}.
2865 Note that the version of GCC shipped by Apple typically includes a
2866 number of extensions not available in a standard GCC release. These
2867 extensions are generally specific to Mac programming.
2873 @heading @anchor{powerpc-*-elf}powerpc-*-elf, powerpc-*-sysv4
2874 PowerPC system in big endian mode, running System V.4.
2880 @heading @anchor{powerpc-*-linux-gnu*}powerpc-*-linux-gnu*
2883 @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.12.90.0.7}
2884 or newer for a working GCC@.
2890 @heading @anchor{powerpc-*-netbsd*}powerpc-*-netbsd*
2891 PowerPC system in big endian mode running NetBSD@. To build the
2892 documentation you will need Texinfo version 4.1 (NetBSD 1.5.1 included
2893 Texinfo version 3.12).
2899 @heading @anchor{powerpc-*-eabiaix}powerpc-*-eabiaix
2900 Embedded PowerPC system in big endian mode with @option{-mcall-aix} selected as
2907 @heading @anchor{powerpc-*-eabisim}powerpc-*-eabisim
2908 Embedded PowerPC system in big endian mode for use in running under the
2915 @heading @anchor{powerpc-*-eabi}powerpc-*-eabi
2916 Embedded PowerPC system in big endian mode.
2922 @heading @anchor{powerpcle-*-elf}powerpcle-*-elf, powerpcle-*-sysv4
2923 PowerPC system in little endian mode, running System V.4.
2929 @heading @anchor{powerpcle-*-eabisim}powerpcle-*-eabisim
2930 Embedded PowerPC system in little endian mode for use in running under
2937 @heading @anchor{powerpcle-*-eabi}powerpcle-*-eabi
2938 Embedded PowerPC system in little endian mode.
2944 @heading @anchor{powerpcle-*-winnt}powerpcle-*-winnt, powerpcle-*-pe
2945 PowerPC system in little endian mode running Windows NT@.
2951 @heading @anchor{s390-*-linux*}s390-*-linux*
2952 S/390 system running Linux for S/390@.
2958 @heading @anchor{s390x-*-linux*}s390x-*-linux*
2959 zSeries system (64-bit) running Linux for zSeries@.
2965 @c Please use Solaris 2 to refer to all release of Solaris, starting
2966 @c with 2.0 until 2.6, 7, and 8. Solaris 1 was a marketing name for
2967 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
2968 @c alone is too unspecific and must be avoided.
2969 @heading @anchor{*-*-solaris2*}*-*-solaris2*
2971 Sun does not ship a C compiler with Solaris 2. To bootstrap and install
2972 GCC you first have to install a pre-built compiler, see our
2973 @uref{binaries.html,,binaries page} for details.
2975 The Solaris 2 @command{/bin/sh} will often fail to configure
2976 @file{libstdc++-v3}, @file{boehm-gc} or
2977 @file{libjava}. If you encounter this problem, set @env{CONFIG_SHELL} to
2978 @command{/bin/ksh} in your environment before running @command{configure}.
2980 Solaris 2 comes with a number of optional OS packages. Some of these
2981 packages are needed to use GCC fully, namely @code{SUNWarc},
2982 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
2983 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
2984 optional packages when installing Solaris 2, you will need to verify that
2985 the packages that GCC needs are installed.
2987 To check whether an optional package is installed, use
2988 the @command{pkginfo} command. To add an optional package, use the
2989 @command{pkgadd} command. For further details, see the Solaris 2
2992 Trying to use the linker and other tools in
2993 @file{/usr/ucb} to install GCC has been observed to cause trouble.
2994 For example, the linker may hang indefinitely. The fix is to remove
2995 @file{/usr/ucb} from your @env{PATH}.
2997 All releases of GNU binutils prior to 2.11.2 have known bugs on this
2998 platform. We recommend the use of GNU binutils 2.11.2 or the vendor
2999 tools (Sun @command{as}, Sun @command{ld}).
3001 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3002 newer: @command{g++} will complain that types are missing. These headers assume
3003 that omitting the type means @code{int}; this assumption worked for C89 but
3004 is wrong for C++, and is now wrong for C99 also.
3006 @command{g++} accepts such (invalid) constructs with the option
3007 @option{-fpermissive}; it
3008 will assume that any missing type is @code{int} (as defined by C89).
3010 There are patches for Solaris 2.6 (105633-56 or newer for SPARC,
3011 106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC,
3012 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
3013 108653-22 for Intel) that fix this bug.
3019 @heading @anchor{sparc-sun-solaris2*}sparc-sun-solaris2*
3021 When GCC is configured to use binutils 2.11.2 or later the binaries
3022 produced are smaller than the ones produced using Sun's native tools;
3023 this difference is quite significant for binaries containing debugging
3026 Sun @command{as} 4.x is broken in that it cannot cope with long symbol names.
3027 A typical error message might look similar to the following:
3029 @samp{/usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041:
3030 error: can't compute value of an expression involving an external symbol.}
3032 This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris
3033 2.6 and has been fixed in later (5.x) versions of the assembler,
3034 starting with Solaris 7.
3036 Starting with Solaris 7, the operating system is capable of executing
3037 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
3038 this; the @option{-m64} option enables 64-bit code generation.
3039 However, if all you want is code tuned for the UltraSPARC CPU, you
3040 should try the @option{-mtune=ultrasparc} option instead, which produces
3041 code that, unlike full 64-bit code, can still run on non-UltraSPARC
3044 When configuring on a Solaris 7 or later system that is running a kernel
3045 that supports only 32-bit binaries, one must configure with
3046 @option{--disable-multilib}, since we will not be able to build the
3047 64-bit target libraries.
3053 @heading @anchor{sparc-sun-solaris2.7}sparc-sun-solaris2.7
3055 Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
3056 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
3057 and later, including all EGCS releases. Sun formerly recommended
3058 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
3059 recommend it only for people who use Sun's compilers.
3061 Here are some workarounds to this problem:
3064 Do not install Sun patch 107058-01 until after Sun releases a
3065 complete patch for bug 4210064. This is the simplest course to take,
3066 unless you must also use Sun's C compiler. Unfortunately 107058-01
3067 is preinstalled on some new Solaris 7-based hosts, so you may have to
3071 Copy the original, unpatched Solaris 7
3072 @command{/usr/ccs/bin/as} into
3073 @command{/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/3.1/as},
3074 adjusting the latter name to fit your local conventions and software
3078 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
3079 both 107058-01 and 106950-03 installed has reported the bug with GCC
3080 and Sun's dynamic linker. This last course of action is riskiest,
3081 for two reasons. First, you must install 106950 on all hosts that
3082 run code generated by GCC; it doesn't suffice to install it only on
3083 the hosts that run GCC itself. Second, Sun says that 106950-03 is
3084 only a partial fix for bug 4210064, but Sun doesn't know whether the
3085 partial fix is adequate for GCC@. Revision -08 or later should fix
3086 the bug. The current (as of 2001-09-24) revision is -14, and is included in
3087 the Solaris 7 Recommended Patch Cluster.
3095 @heading @anchor{sparc-sun-sunos4*}sparc-sun-sunos4*
3097 A bug in the SunOS 4 linker will cause it to crash when linking
3098 @option{-fPIC} compiled objects (and will therefore not allow you to build
3101 To fix this problem you can either use the most recent version of
3102 binutils or get the latest SunOS 4 linker patch (patch ID 100170-10)
3103 from Sun's patch site.
3105 Sometimes on a Sun 4 you may observe a crash in the program
3106 @command{genflags} or @command{genoutput} while building GCC. This is said to
3107 be due to a bug in @command{sh}. You can probably get around it by running
3108 @command{genflags} or @command{genoutput} manually and then retrying the
3115 @heading @anchor{sparc-unknown-linux-gnulibc1}sparc-unknown-linux-gnulibc1
3117 It has been reported that you might need
3118 @uref{ftp://ftp.yggdrasil.com/private/hjl,,binutils 2.8.1.0.23}
3119 for this platform, too.
3126 @heading @anchor{sparc-*-linux*}sparc-*-linux*
3128 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
3129 or newer on this platform. All earlier binutils and glibc
3130 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
3137 @heading @anchor{sparc64-*-*}sparc64-*-*
3139 GCC version 2.95 is not able to compile code correctly for
3140 @code{sparc64} targets. Users of the Linux kernel, at least,
3141 can use the @code{sparc32} program to start up a new shell
3142 invocation with an environment that causes @command{configure} to
3143 recognize (via @samp{uname -a}) the system as @samp{sparc-*-*} instead.
3149 @heading @anchor{sparcv9-*-solaris2*}sparcv9-*-solaris2*
3151 The following compiler flags must be specified in the configure
3152 step in order to bootstrap this target with the Sun compiler:
3155 % CC="cc -xildoff -xarch=v9" @var{srcdir}/configure [@var{options}] [@var{target}]
3158 @option{-xildoff} turns off the incremental linker, and @option{-xarch=v9}
3159 specifies the v9 architecture to the Sun linker and assembler.
3165 @heading @anchor{#*-*-sysv*}*-*-sysv*
3166 On System V release 3, you may get this error message
3170 ld fatal: failed to write symbol name @var{something}
3171 in strings table for file @var{whatever}
3174 This probably indicates that the disk is full or your ulimit won't allow
3175 the file to be as large as it needs to be.
3177 This problem can also result because the kernel parameter @code{MAXUMEM}
3178 is too small. If so, you must regenerate the kernel and make the value
3179 much larger. The default value is reported to be 1024; a value of 32768
3180 is said to work. Smaller values may also work.
3182 On System V, if you get an error like this,
3185 /usr/local/lib/bison.simple: In function `yyparse':
3186 /usr/local/lib/bison.simple:625: virtual memory exhausted
3190 that too indicates a problem with disk space, ulimit, or @code{MAXUMEM}.
3192 On a System V release 4 system, make sure @file{/usr/bin} precedes
3193 @file{/usr/ucb} in @code{PATH}. The @code{cc} command in
3194 @file{/usr/ucb} uses libraries which have bugs.
3200 @heading @anchor{vax-dec-ultrix}vax-dec-ultrix
3201 Don't try compiling with VAX C (@code{vcc}). It produces incorrect code
3202 in some cases (for example, when @code{alloca} is used).
3208 @heading @anchor{xtensa-*-elf}xtensa-*-elf
3210 This target is intended for embedded Xtensa systems using the
3211 @samp{newlib} C library. It uses ELF but does not support shared
3212 objects. Designed-defined instructions specified via the
3213 Tensilica Instruction Extension (TIE) language are only supported
3214 through inline assembly.
3216 The Xtensa configuration information must be specified prior to
3217 building GCC@. The @file{gcc/config/xtensa/xtensa-config.h} header
3218 file contains the configuration information. If you created your
3219 own Xtensa configuration with the Xtensa Processor Generator, the
3220 downloaded files include a customized copy of this header file,
3221 which you can use to replace the default header file.
3227 @heading @anchor{xtensa-*-linux*}xtensa-*-linux*
3229 This target is for Xtensa systems running GNU/Linux. It supports ELF
3230 shared objects and the GNU C library (glibc). It also generates
3231 position-independent code (PIC) regardless of whether the
3232 @option{-fpic} or @option{-fPIC} options are used. In other
3233 respects, this target is the same as the
3234 @uref{#xtensa-*-elf,,@samp{xtensa-*-elf}} target.
3240 @heading @anchor{windows}Microsoft Windows (32-bit)
3242 A port of GCC 2.95.x is included with the
3243 @uref{http://www.cygwin.com/,,Cygwin environment}.
3245 Current (as of early 2001) snapshots of GCC will build under Cygwin
3246 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/}.
3266 @heading @anchor{older}Older systems
3268 GCC contains support files for many older (1980s and early
3269 1990s) Unix variants. For the most part, support for these systems
3270 has not been deliberately removed, but it has not been maintained for
3271 several years and may suffer from bitrot.
3273 Starting with GCC 3.1, each release has a list of ``obsoleted'' systems.
3274 Support for these systems is still present in that release, but
3275 @command{configure} will fail unless the @option{--enable-obsolete}
3276 option is given. Unless a maintainer steps forward, support for these
3277 systems will be removed from the next release of GCC@.
3279 Support for old systems as hosts for GCC can cause problems if the
3280 workarounds for compiler, library and operating system bugs affect the
3281 cleanliness or maintainability of the rest of GCC@. In some cases, to
3282 bring GCC up on such a system, if still possible with current GCC, may
3283 require first installing an old version of GCC which did work on that
3284 system, and using it to compile a more recent GCC, to avoid bugs in the
3285 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
3286 @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror
3287 sites}. Header bugs may generally be avoided using
3288 @command{fixincludes}, but bugs or deficiencies in libraries and the
3289 operating system may still cause problems.
3291 Support for older systems as targets for cross-compilation is less
3292 problematic than support for them as hosts for GCC; if an enthusiast
3293 wishes to make such a target work again (including resurrecting any of
3294 the targets that never worked with GCC 2, starting from the last CVS
3295 version before they were removed), patches
3296 @uref{../contribute.html,,following the usual requirements} would be
3297 likely to be accepted, since they should not affect the support for more
3300 For some systems, old versions of GNU binutils may also be useful,
3301 and are available from @file{pub/binutils/old-releases} on
3302 @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}.
3304 Some of the information on specific systems above relates to
3305 such older systems, but much of the information
3306 about GCC on such systems (which may no longer be applicable to
3307 current GCC) is to be found in the GCC texinfo manual.
3313 @heading @anchor{elf_targets}all ELF targets (SVR4, Solaris 2, etc.)
3315 C++ support is significantly better on ELF targets if you use the
3316 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
3317 inlines, vtables and template instantiations will be discarded
3327 @uref{./index.html,,Return to the GCC Installation page}
3331 @c ***Old documentation******************************************************
3333 @include install-old.texi
3340 @uref{./index.html,,Return to the GCC Installation page}
3344 @c ***GFDL********************************************************************
3353 @uref{./index.html,,Return to the GCC Installation page}
3357 @c ***************************************************************************
3358 @c Part 6 The End of the Document
3360 @comment node-name, next, previous, up
3361 @node Concept Index, , GNU Free Documentation License, Top
3365 @unnumbered Concept Index