1 \input texinfo.tex @c -*-texinfo-*-
4 @setfilename install.info
5 @settitle Installing GCC
10 @c Specify title for specific html page
12 @settitle Installing GCC
15 @settitle Host/Target specific installation notes for GCC
18 @settitle Downloading GCC
21 @settitle Installing GCC: Configuration
24 @settitle Installing GCC: Building
27 @settitle Installing GCC: Testing
29 @ifset finalinstallhtml
30 @settitle Installing GCC: Final installation
33 @settitle Installing GCC: Binaries
36 @settitle Installing GCC: Old documentation
39 @settitle Installing GCC: GNU Free Documentation License
42 @c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
43 @c 1999, 2000, 2001, 2002 Free Software Foundation, Inc.
44 @c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com
46 @c Include everything if we're not making html
60 @c Part 2 Summary Description and Copyright
61 @macro copyrightnotice
62 Copyright @copyright{} 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
63 1999, 2000, 2001, 2002 Free Software Foundation, Inc.
65 Permission is granted to copy, distribute and/or modify this document
66 under the terms of the GNU Free Documentation License, Version 1.1 or
67 any later version published by the Free Software Foundation; with no
68 Invariant Sections, the Front-Cover texts being (a) (see below), and
69 with the Back-Cover Texts being (b) (see below). A copy of the
70 license is included in the section entitled ``@uref{./gfdl.html,,GNU
71 Free Documentation License}''.
73 (a) The FSF's Front-Cover Text is:
77 (b) The FSF's Back-Cover Text is:
79 You have freedom to copy and modify this GNU Manual, like GNU
80 software. Copies published by the Free Software Foundation raise
81 funds for GNU development.
87 @c Part 3 Titlepage and Copyright
90 @comment The title is printed in a large font.
91 @center @titlefont{Installing GCC}
93 @c The following two commands start the copyright page.
95 @vskip 0pt plus 1filll
99 @c Part 4 Top node and Master Menu
102 @comment node-name, next, Previous, up
105 * Installing GCC:: This document describes the generic installation
106 procedure for GCC as well as detailing some target
107 specific installation instructions.
109 * Specific:: Host/target specific installation notes for GCC.
110 * Binaries:: Where to get pre-compiled binaries.
112 * Old:: Old installation documentation.
114 * GNU Free Documentation License:: How you can copy and share this manual.
115 * Concept Index:: This index has two entries.
119 @c Part 5 The Body of the Document
120 @c ***Installing GCC**********************************************************
122 @comment node-name, next, previous, up
123 @node Installing GCC, Binaries, , Top
127 <h1 align="center">Installing GCC</h1>
130 @chapter Installing GCC
133 The latest version of this document is always available at
134 @uref{http://gcc.gnu.org/install/,,http://gcc.gnu.org/install/}.
136 This document describes the generic installation procedure for GCC as well
137 as detailing some target specific installation instructions.
139 GCC includes several components that previously were separate distributions
140 with their own installation instructions. This document supersedes all
141 package specific installation instructions.
143 @emph{Before} starting the build/install procedure please check the
145 @ref{Specific, host/target specific installation notes}.
148 @uref{specific.html,,host/target specific installation notes}.
150 We recommend you browse the entire generic installation instructions before
153 Lists of successful builds for released versions of GCC are
154 available at our web pages for
155 @uref{http://gcc.gnu.org/gcc-3.0/buildstat.html,,3.0}
157 @uref{http://gcc.gnu.org/gcc-2.95/buildstat.html,,2.95}.
158 These lists are updated as new information becomes available.
160 The installation procedure itself is broken into five steps.
164 * Downloading the source::
167 * Testing:: (optional)
174 @uref{download.html,,Downloading the source}
176 @uref{configure.html,,Configuration}
178 @uref{build.html,,Building}
180 @uref{test.html,,Testing} (optional)
182 @uref{finalinstall.html,,Final install}
186 Please note that GCC does not support @samp{make uninstall} and probably
187 won't do so in the near future as this would open a can of worms. Instead,
188 we suggest that you install GCC into a directory of its own and simply
189 remove that directory when you do not need that specific version of GCC
190 any longer, and, if shared libraries are installed there as well, no
191 more binaries exist that use them.
194 There are also some @uref{old.html,,old installation instructions},
195 which are mostly obsolete but still contain some information which has
196 not yet been merged into the main part of this manual.
204 @uref{./index.html,,Return to the GCC Installation page}
210 @c ***Downloading the source**************************************************
212 @comment node-name, next, previous, up
213 @node Downloading the source, Configuration, , Installing GCC
217 <h1 align="center">Downloading GCC</h1>
220 @chapter Downloading GCC
222 @cindex Downloading GCC
223 @cindex Downloading the Source
225 GCC is distributed via @uref{http://gcc.gnu.org/cvs.html,,CVS} and FTP
226 tarballs compressed with @command{gzip} or
227 @command{bzip2}. It is possible to download a full distribution or specific
230 Please refer to our @uref{http://gcc.gnu.org/releases.html,,releases web page}
231 for information on how to obtain GCC@.
233 The full distribution includes the C, C++, Objective-C, Fortran, Java,
234 and CHILL compilers. The full distribution also includes runtime libraries
235 for C++, Objective-C, Fortran, Java and CHILL. (GCC 3.0 does not
236 include CHILL.) In GCC 3.0 and later versions, GNU compiler testsuites
237 are also included in the full distribution.
239 If you choose to download specific components, you must download the core
240 GCC distribution plus any language specific distributions you wish to
241 use. The core distribution includes the C language front end as well as the
242 shared components. Each language has a tarball which includes the language
243 front end as well as the language runtime (when appropriate).
245 Unpack the core distribution as well as any language specific
246 distributions in the same directory.
248 If you also intend to build binutils (either to upgrade an existing
249 installation or for use in place of the corresponding tools of your
250 OS), unpack the binutils distribution either in the same directory or
251 a separate one. In the latter case, add symbolic links to any
252 components of the binutils you intend to build alongside the compiler
253 (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
254 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
261 @uref{./index.html,,Return to the GCC Installation page}
265 @c ***Configuration***********************************************************
267 @comment node-name, next, previous, up
268 @node Configuration, Building, Downloading the source, Installing GCC
272 <h1 align="center">Installing GCC: Configuration</h1>
275 @chapter Installing GCC: Configuration
277 @cindex Configuration
278 @cindex Installing GCC: Configuration
280 Like most GNU software, GCC must be configured before it can be built.
281 This document describes the recommended configuration procedure
282 for both native and cross targets.
284 We use @var{srcdir} to refer to the toplevel source directory for
285 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
287 If you obtained the sources via CVS, @var{srcdir} must refer to the top
288 @file{gcc} directory, the one where the @file{MAINTAINERS} can be found,
289 and not its @file{gcc} subdirectory, otherwise the build will fail.
291 First, in general, GCC @strong{must} be built into a separate directory
292 than the sources which does @strong{not} reside within the source tree.
293 This is how almost all developers build GCC; building where @var{srcdir}
294 == @var{objdir} is completely unsupported; building where @var{objdir}
295 is a subdirectory of @var{srcdir} is completely unsupported.
297 If you have previously built GCC in the same directory for a
298 different target machine, do @samp{make distclean} to delete all files
299 that might be invalid. One of the files this deletes is
300 @file{Makefile}; if @samp{make distclean} complains that @file{Makefile}
301 does not exist, it probably means that the directory is already suitably
302 clean. However, with the recommended method of building in a separate
303 @var{objdir}, you should simply use a different @var{objdir} for each
306 Second, when configuring a native system, either @command{cc} or
307 @command{gcc} must be in your path or you must set @env{CC} in
308 your environment before running configure. Otherwise the configuration
311 Note that the bootstrap compiler and the resulting GCC must be link
312 compatible, else the bootstrap will fail with linker errors about
313 incompatible object file formats. Several multilibed targets are
314 affected by this requirement, see
316 @ref{Specific, host/target specific installation notes}.
319 @uref{specific.html,,host/target specific installation notes}.
327 % @var{srcdir}/configure [@var{options}] [@var{target}]
331 @heading Target specification
334 GCC has code to correctly determine the correct value for @var{target}
335 for nearly all native systems. Therefore, we highly recommend you not
336 provide a configure target when configuring a native compiler.
339 @var{target} must be specified as @option{--target=@var{target}}
340 when configuring a cross compiler; examples of valid targets would be
341 i960-rtems, m68k-coff, sh-elf, etc.
344 Specifying just @var{target} instead of @option{--target=@var{target}}
345 implies that the host defaults to @var{target}.
349 @heading Options specification
351 Use @var{options} to override several configure time options for
352 GCC@. A list of supported @var{options} follows; @command{configure
353 --help} may list other options, but those not listed below may not
354 work and should not normally be used.
357 @item --prefix=@var{dirname}
358 Specify the toplevel installation
359 directory. This is the recommended way to install the tools into a directory
360 other than the default. The toplevel installation directory defaults to
363 We @strong{highly} recommend against @var{dirname} being the same or a
364 subdirectory of @var{objdir} or vice versa.
366 These additional options control where certain parts of the distribution
367 are installed. Normally you should not need to use these options.
370 @item --exec-prefix=@var{dirname}
371 Specify the toplevel installation directory for architecture-dependent
372 files. The default is @file{@var{prefix}}.
374 @item --bindir=@var{dirname}
375 Specify the installation directory for the executables called by users
376 (such as @command{gcc} and @command{g++}). The default is
377 @file{@var{exec-prefix}/bin}.
379 @item --libdir=@var{dirname}
380 Specify the installation directory for object code libraries and
381 internal parts of GCC@. The default is @file{@var{exec-prefix}/lib}.
383 @item --with-slibdir=@var{dirname}
384 Specify the installation directory for the shared libgcc library. The
385 default is @file{@var{libdir}}.
387 @item --infodir=@var{dirname}
388 Specify the installation directory for documentation in info format.
389 The default is @file{@var{prefix}/info}.
391 @item --mandir=@var{dirname}
392 Specify the installation directory for manual pages. The default is
393 @file{@var{prefix}/man}. (Note that the manual pages are only extracts from
394 the full GCC manuals, which are provided in Texinfo format. The
395 @command{g77} manpage is unmaintained and may be out of date; the others
396 are derived by an automatic conversion process from parts of the full
399 @item --with-gxx-include-dir=@var{dirname}
401 the installation directory for G++ header files. The default is
402 @file{@var{prefix}/include/g++-v3}.
406 @item --program-prefix=@var{prefix}
407 GCC supports some transformations of the names of its programs when
408 installing them. This option prepends @var{prefix} to the names of
409 programs to install in @var{bindir} (see above). For example, specifying
410 @option{--program-prefix=foo-} would result in @samp{gcc}
411 being installed as @file{/usr/local/bin/foo-gcc}.
413 @item --program-suffix=@var{suffix}
414 Appends @var{suffix} to the names of programs to install in @var{bindir}
415 (see above). For example, specifying @option{--program-suffix=-3.1}
416 would result in @samp{gcc} being installed as
417 @file{/usr/local/bin/gcc-3.1}.
419 @item --program-transform-name=@var{pattern}
420 Applies the @samp{sed} script @var{pattern} to be applied to the names
421 of programs to install in @var{bindir} (see above). @var{pattern} has to
422 consist of one or more basic @samp{sed} editing commands, separated by
423 semicolons. For example, if you want the @samp{gcc} program name to be
424 transformed to the installed program @file{/usr/local/bin/myowngcc} and
425 the @samp{g++} program name to be transformed to
426 @file{/usr/local/bin/gspecial++} without changing other program names,
427 you could use the pattern
428 @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}
429 to achieve this effect.
431 All three options can be combined and used together, resulting in more
432 complex conversion patterns. As a basic rule, @var{prefix} (and
433 @var{suffix}) are prepended (appended) before further transformations
434 can happen with a special transformation script @var{pattern}.
436 As currently implemented, this options only take effect for native
437 builds; cross compiler binaries' names are not transformed even when a
438 transformation is explicitly asked for by one of this options.
440 For native builds, some of the installed programs are also installed
441 with the target alias in front of their name, as in
442 @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
443 before the target alias is prepended to the name - so, specifying
444 @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
445 resulting binary would be installed as
446 @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.
448 As a last shortcoming, none of the installed CHILL and Ada programs are
449 transformed yet, which will be fixed in some time.
451 @item --with-local-prefix=@var{dirname}
453 installation directory for local include files. The default is
454 @file{/usr/local}. Specify this option if you want the compiler to
455 search directory @file{@var{dirname}/include} for locally installed
456 header files @emph{instead} of @file{/usr/local/include}.
458 You should specify @option{--with-local-prefix} @strong{only} if your
459 site has a different convention (not @file{/usr/local}) for where to put
462 The default value for @option{--with-local-prefix} is @file{/usr/local}
463 regardless of the value of @option{--prefix}. Specifying
464 @option{--prefix} has no effect on which directory GCC searches for
465 local header files. This may seem counterintuitive, but actually it is
468 The purpose of @option{--prefix} is to specify where to @emph{install
469 GCC}. The local header files in @file{/usr/local/include}---if you put
470 any in that directory---are not part of GCC@. They are part of other
471 programs---perhaps many others. (GCC installs its own header files in
472 another directory which is based on the @option{--prefix} value.)
474 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
475 The directory you use for @option{--with-local-prefix} @strong{must not}
476 contain any of the system's standard header files. If it did contain
477 them, certain programs would be miscompiled (including GNU Emacs, on
478 certain targets), because this would override and nullify the header
479 file corrections made by the @code{fixincludes} script.
481 Indications are that people who use this option use it based on mistaken
482 ideas of what it is for. People use it as if it specified where to
483 install part of GCC@. Perhaps they make this assumption because
484 installing GCC creates the directory.
486 @item --enable-shared[=@var{package}[,@dots{}]]
487 Build shared versions of libraries, if shared libraries are supported on
488 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
489 are enabled by default on all platforms that support shared libraries,
490 except for @samp{libobjc} which is built as a static library only by
493 If a list of packages is given as an argument, build shared libraries
494 only for the listed packages. For other packages, only static libraries
495 will be built. Package names currently recognized in the GCC tree are
496 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
497 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc} and
498 @samp{libjava}. Note that @samp{libobjc} does not recognize itself by
499 any name, so, if you list package names in @option{--enable-shared},
500 you will only get static Objective-C libraries. @samp{libf2c} and
501 @samp{libiberty} do not support shared libraries at all.
503 Use @option{--disable-shared} to build only static libraries. Note that
504 @option{--disable-shared} does not accept a list of package names as
505 argument, only @option{--enable-shared} does.
507 @item @anchor{with-gnu-as}--with-gnu-as
508 Specify that the compiler should assume that the
509 assembler it finds is the GNU assembler. However, this does not modify
510 the rules to find an assembler and will result in confusion if found
511 assembler is not actually the GNU assembler. (Confusion will also
512 result if the compiler finds the GNU assembler but has not been
513 configured with @option{--with-gnu-as}.) If you have more than one
514 assembler installed on your system, you may want to use this option in
515 connection with @option{--with-as=@var{pathname}}.
517 The systems where it makes a difference whether you use the GNU assembler are
518 @samp{hppa1.0-@var{any}-@var{any}}, @samp{hppa1.1-@var{any}-@var{any}},
519 @samp{i386-@var{any}-sysv}, @samp{i386-@var{any}-isc},
520 @samp{i860-@var{any}-bsd}, @samp{m68k-bull-sysv},
521 @samp{m68k-hp-hpux}, @samp{m68k-sony-bsd},
522 @samp{m68k-altos-sysv}, @samp{m68000-hp-hpux},
523 @samp{m68000-att-sysv}, @samp{@var{any}-lynx-lynxos},
524 and @samp{mips-@var{any}}.
525 On any other system, @option{--with-gnu-as} has no effect.
527 On the systems listed above (except for the HP-PA, for ISC on the
528 386, and for @samp{mips-sgi-irix5.*}), if you use the GNU assembler,
529 you should also use the GNU linker (and specify @option{--with-gnu-ld}).
531 @item --with-as=@var{pathname}
533 compiler should use the assembler pointed to by @var{pathname}, rather
534 than the one found by the standard rules to find an assembler, which
539 @file{@var{exec_prefix}/lib/gcc-lib/@var{target}/@var{version}}
540 directory, where @var{exec_prefix} defaults to @var{prefix} which
541 defaults to @file{/usr/local} unless overridden by the
542 @option{--prefix=@var{pathname}} switch described above. @var{target} is the
543 target system triple, such as @samp{sparc-sun-solaris2.7}, and
544 @var{version} denotes the GCC version, such as 3.0.
546 Check operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
549 Note that these rules do not check for the value of @env{PATH}. You may
550 want to use @option{--with-as} if no assembler is installed in the
551 directories listed above, or if you have multiple assemblers installed
552 and want to choose one that is not found by the above rules.
554 @item @anchor{with-gnu-ld}--with-gnu-ld
555 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
559 @item --with-ld=@var{pathname}
561 @option{--with-as}, but for the linker.
564 Specify that stabs debugging
565 information should be used instead of whatever format the host normally
566 uses. Normally GCC uses the same debug format as the host system.
568 On MIPS based systems and on Alphas, you must specify whether you want
569 GCC to create the normal ECOFF debugging format, or to use BSD-style
570 stabs passed through the ECOFF symbol table. The normal ECOFF debug
571 format cannot fully handle languages other than C@. BSD stabs format can
572 handle other languages, but it only works with the GNU debugger GDB@.
574 Normally, GCC uses the ECOFF debugging format by default; if you
575 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
577 No matter which default you choose when you configure GCC, the user
578 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
579 the debug format for a particular compilation.
581 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
582 @option{--with-gas} is used. It selects use of stabs debugging
583 information embedded in COFF output. This kind of debugging information
584 supports C++ well; ordinary COFF debugging information does not.
586 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
587 selects use of stabs debugging information embedded in ELF output. The
588 C++ compiler currently (2.6.0) does not support the DWARF debugging
589 information normally used on 386 SVR4 platforms; stabs provide a
590 workable alternative. This requires gas and gdb, as the normal SVR4
591 tools can not generate or interpret stabs.
593 @item --disable-multilib
594 Specify that multiple target
595 libraries to support different target variants, calling
596 conventions, etc should not be built. The default is to build a
597 predefined set of them.
599 Some targets provide finer-grained control over which multilibs are built
600 (e.g., @option{--disable-softfloat}):
607 fpu, 26bit, underscore, interwork, biendian, nofmult.
610 softfloat, m68881, m68000, m68020.
613 single-float, biendian, softfloat.
615 @item powerpc*-*-*, rs6000*-*-*
616 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
621 @item --enable-threads
622 Specify that the target
623 supports threads. This affects the Objective-C compiler and runtime
624 library, and exception handling for other languages like C++ and Java.
625 On some systems, this is the default.
627 In general, the best (and, in many cases, the only known) threading
628 model available will be configured for use. Beware that on some
629 systems, gcc has not been taught what threading models are generally
630 available for the system. In this case, @option{--enable-threads} is an
631 alias for @option{--enable-threads=single}.
633 @item --disable-threads
634 Specify that threading support should be disabled for the system.
635 This is an alias for @option{--enable-threads=single}.
637 @item --enable-threads=@var{lib}
639 @var{lib} is the thread support library. This affects the Objective-C
640 compiler and runtime library, and exception handling for other languages
641 like C++ and Java. The possibilities for @var{lib} are:
649 Generic MACH thread support, known to work on NeXTSTEP@. (Please note
650 that the file needed to support this configuration, @file{gthr-mach.h}, is
651 missing and thus this setting will cause a known bootstrap failure.)
653 This is an alias for @samp{single}.
655 Generic POSIX thread support.
657 Same as @samp{posix} on arm*-*-linux*, *-*-chorusos* and *-*-freebsd*
658 only. A future release of gcc might remove this alias or extend it
661 RTEMS thread support.
663 Disable thread support, should work for all platforms.
665 Sun Solaris 2 thread support.
667 VxWorks thread support.
669 Microsoft Win32 API thread support.
672 @item --with-cpu=@var{cpu}
673 Specify which cpu variant the
674 compiler should generate code for by default. This is currently
675 only supported on the some ports, specifically arm, powerpc, and
676 SPARC@. If configure does not recognize the model name (e.g.@: arm700,
677 603e, or ultrasparc) you provide, please check the configure script
678 for a complete list of supported models.
680 @item --enable-altivec
681 Specify that the target supports AltiVec vector enhancements. This
682 option will adjust the ABI for AltiVec enhancements, as well as generate
683 AltiVec code when appropriate. This option is only available for
686 @item --enable-target-optspace
688 libraries should be optimized for code space instead of code speed.
689 This is the default for the m32r platform.
692 Specify that a user visible @command{cpp} program should not be installed.
694 @item --with-cpp-install-dir=@var{dirname}
695 Specify that the user visible @command{cpp} program should be installed
696 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
698 @item --enable-maintainer-mode
700 regenerate the GCC master message catalog @file{gcc.pot} are normally
701 disabled. This is because it can only be rebuilt if the complete source
702 tree is present. If you have changed the sources and want to rebuild the
703 catalog, configuring with @option{--enable-maintainer-mode} will enable
704 this. Note that you need a recent version of the @code{gettext} tools
707 @item --enable-version-specific-runtime-libs
709 that runtime libraries should be installed in the compiler specific
710 subdirectory (@file{@var{libsubdir}}) rather than the usual places. In
711 addition, @samp{libstdc++}'s include files will be installed in
712 @file{@var{libsubdir}/include/g++} unless you overruled it by using
713 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
714 particularly useful if you intend to use several versions of GCC in
715 parallel. This is currently supported by @samp{libf2c} and
716 @samp{libstdc++}, and is the default for @samp{libobjc} which cannot be
717 changed in this case.
719 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
720 Specify that only a particular subset of compilers and
721 their runtime libraries should be built. For a list of valid values for
722 @var{langN} you can issue the following command in the
723 @file{gcc} directory of your GCC source tree:@*
725 grep language= */config-lang.in
727 Currently, you can use any of the following:
728 @code{ada}, @code{c}, @code{c++}, @code{f77}, @code{java}, @code{objc}.
729 @code{CHILL} is not currently maintained, and will almost
730 certainly fail to compile. Building the Ada compiler has special
731 requirements, see below.@*
732 If you do not pass this flag, all languages available in the @file{gcc}
733 sub-tree will be configured. Re-defining @code{LANGUAGES} when calling
734 @samp{make bootstrap} @strong{does not} work anymore, as those
735 language sub-directories might not have been configured!
737 @item --disable-libgcj
738 Specify that the run-time libraries
739 used by GCJ should not be built. This is useful in case you intend
740 to use GCJ with some other run-time, or you're going to install it
741 separately, or it just happens not to build on your particular
742 machine. In general, if the Java front end is enabled, the GCJ
743 libraries will be enabled too, unless they're known to not work on
744 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
745 may need to port it; in this case, before modifying the top-level
746 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
747 you may use @option{--enable-libgcj} to override the default.
750 Specify that the compiler should
751 use DWARF 2 debugging information as the default.
753 @item --enable-win32-registry
754 @itemx --enable-win32-registry=@var{key}
755 @itemx --disable-win32-registry
756 The @option{--enable-win32-registry} option enables Windows-hosted GCC
757 to look up installations paths in the registry using the following key:
760 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
763 @var{key} defaults to GCC version number, and can be overridden by the
764 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
765 who use custom installers are encouraged to provide a different key,
766 perhaps one comprised of vendor name and GCC version number, to
767 avoid conflict with existing installations. This feature is enabled
768 by default, and can be disabled by @option{--disable-win32-registry}
769 option. This option has no effect on the other hosts.
772 Specify that the machine does not have a floating point unit. This
773 option only applies to @samp{m68k-sun-sunos@var{n}} and
774 @samp{m68k-isi-bsd}. On any other system, @option{--nfp} has no effect.
776 @item --enable-checking
777 @itemx --enable-checking=@var{list}
778 When you specify this option, the compiler is built to perform checking
779 of tree node types when referencing fields of that node, and some other
780 internal consistency checks. This does not change the generated code,
781 but adds error checking within the compiler. This will slow down the
782 compiler and may only work properly if you are building the compiler
783 with GCC@. This is on by default when building from CVS or snapshots,
784 but off for releases. More control over the checks may be had by
785 specifying @var{list}; the categories of checks available are
786 @samp{misc}, @samp{tree}, @samp{gc}, @samp{rtl} and @samp{gcac}. The
787 default when @var{list} is not specified is @samp{misc,tree,gc}; the
788 checks @samp{rtl} and @samp{gcac} are very expensive.
792 The @option{--enable-nls} option enables Native Language Support (NLS),
793 which lets GCC output diagnostics in languages other than American
794 English. Native Language Support is enabled by default if not doing a
795 canadian cross build. The @option{--disable-nls} option disables NLS@.
797 @item --with-included-gettext
798 If NLS is enabled, the @option{--with-included-gettext} option causes the build
799 procedure to prefer its copy of GNU @command{gettext}.
802 If NLS is enabled, and if the host lacks @code{gettext} but has the
803 inferior @code{catgets} interface, the GCC build procedure normally
804 ignores @code{catgets} and instead uses GCC's copy of the GNU
805 @code{gettext} library. The @option{--with-catgets} option causes the
806 build procedure to use the host's @code{catgets} in this situation.
808 @item --with-libiconv-prefix=@var{dir}
809 Search for libiconv header files in @file{@var{dir}/include} and
810 libiconv library files in @file{@var{dir}/lib}.
812 @item --with-system-zlib
813 Use installed zlib rather than that included with GCC@. This option
814 only applies if the Java front end is being built.
817 Some options which only apply to building cross compilers:
819 @item --with-headers=@var{dir}
820 Specifies a directory
821 which has target include files.
822 @emph{This options is required} when building a cross
823 compiler, if @file{@var{prefix}/@var{target}/sys-include} doesn't pre-exist.
824 These include files will be copied into the @file{gcc} install directory.
825 Fixincludes will be run on these files to make them compatible with
827 @item --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
828 Specifies a list of directories which contain the target runtime
829 libraries. These libraries will be copied into the @file{gcc} install
832 Specifies that @samp{newlib} is
833 being used as the target C library. This causes @code{__eprintf} to be
834 omitted from @file{libgcc.a} on the assumption that it will be provided by
838 Note that each @option{--enable} option has a corresponding
839 @option{--disable} option and that each @option{--with} option has a
840 corresponding @option{--without} option.
847 @uref{./index.html,,Return to the GCC Installation page}
851 @c ***Building****************************************************************
853 @comment node-name, next, previous, up
854 @node Building, Testing, Configuration, Installing GCC
858 <h1 align="center">Installing GCC: Building</h1>
863 @cindex Installing GCC: Building
865 Now that GCC is configured, you are ready to build the compiler and
868 We @strong{highly} recommend that GCC be built using GNU make;
869 other versions may work, then again they might not.
870 GNU make is required for compiling GNAT, the Ada compiler.
872 (For example, many broken versions of make will fail if you use the
873 recommended setup where @var{objdir} is different from @var{srcdir}.
874 Other broken versions may recompile parts of the compiler when
875 installing the compiler.)
877 Some commands executed when making the compiler may fail (return a
878 nonzero status) and be ignored by @code{make}. These failures, which
879 are often due to files that were not found, are expected, and can safely
882 It is normal to have compiler warnings when compiling certain files.
883 Unless you are a GCC developer, you can generally ignore these warnings
884 unless they cause compilation to fail.
886 On certain old systems, defining certain environment variables such as
887 @env{CC} can interfere with the functioning of @command{make}.
889 If you encounter seemingly strange errors when trying to build the
890 compiler in a directory other than the source directory, it could be
891 because you have previously configured the compiler in the source
892 directory. Make sure you have done all the necessary preparations.
894 If you build GCC on a BSD system using a directory stored in an old System
895 V file system, problems may occur in running @code{fixincludes} if the
896 System V file system doesn't support symbolic links. These problems
897 result in a failure to fix the declaration of @code{size_t} in
898 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
899 that type mismatches occur, this could be the cause.
901 The solution is not to use such a directory for building GCC@.
903 When building from CVS or snapshots, or if you modify parser sources,
904 you need the Bison parser generator installed. Any version 1.25 or
905 later should work; older versions may also work. If you do not modify
906 parser sources, releases contain the Bison-generated files and you do
907 not need Bison installed to build them.
909 When building from CVS or snapshots, or if you modify Texinfo
910 documentation, you need version 4.0 or later of Texinfo installed if you
911 want Info documentation to be regenerated. Releases contain Info
912 documentation pre-built for the unmodified documentation in the release.
914 @section Building a native compiler
916 For a native build issue the command @samp{make bootstrap}. This
917 will build the entire GCC system, which includes the following steps:
921 Build host tools necessary to build the compiler such as texinfo, bison,
925 Build target tools for use by the compiler such as binutils (bfd,
926 binutils, gas, gprof, ld, and opcodes)
927 if they have been individually linked
928 or moved into the top level GCC source tree before configuring.
931 Perform a 3-stage bootstrap of the compiler.
934 Perform a comparison test of the stage2 and stage3 compilers.
937 Build runtime libraries using the stage3 compiler from the previous step.
941 If you are short on disk space you might consider @samp{make
942 bootstrap-lean} instead. This is identical to @samp{make
943 bootstrap} except that object files from the stage1 and
944 stage2 of the 3-stage bootstrap of the compiler are deleted as
945 soon as they are no longer needed.
948 If you want to save additional space during the bootstrap and in
949 the final installation as well, you can build the compiler binaries
950 without debugging information with @samp{make CFLAGS='-O' LIBCFLAGS='-g
951 -O2' LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap}. This will save
952 roughly 40% of disk space both for the bootstrap and the final installation.
953 (Libraries will still contain debugging information.)
955 If you wish to use non-default GCC flags when compiling the stage2 and
956 stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing
957 @samp{make bootstrap}. Non-default optimization flags are less well
958 tested here than the default of @samp{-g -O2}, but should still work.
959 In a few cases, you may find that you need to specify special flags such
960 as @option{-msoft-float} here to complete the bootstrap; or, if the
961 native compiler miscompiles the stage1 compiler, you may need to work
962 around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the
963 stage1 compiler that were miscompiled, or by using @samp{make
964 bootstrap4} to increase the number of stages of bootstrap.
966 If you used the flag @option{--enable-languages=@dots{}} to restrict
967 the compilers to be built, only those you've actually enabled will be
968 built. This will of course only build those runtime libraries, for
969 which the particular compiler has been built. Please note,
970 that re-defining @env{LANGUAGES} when calling @samp{make bootstrap}
971 @strong{does not} work anymore!
973 If the comparison of stage2 and stage3 fails, this normally indicates
974 that the stage2 compiler has compiled GCC incorrectly, and is therefore
975 a potentially serious bug which you should investigate and report. (On
976 a few systems, meaningful comparison of object files is impossible; they
977 always appear ``different''. If you encounter this problem, you will
978 need to disable comparison in the @file{Makefile}.)
980 @section Building a cross compiler
982 We recommend reading the
983 @uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ}
984 for information about building cross compilers.
986 When building a cross compiler, it is not generally possible to do a
987 3-stage bootstrap of the compiler. This makes for an interesting problem
988 as parts of GCC can only be built with GCC@.
990 To build a cross compiler, we first recommend building and installing a
991 native compiler. You can then use the native GCC compiler to build the
992 cross compiler. The installed native compiler needs to be GCC version
995 Assuming you have already installed a native copy of GCC and configured
996 your cross compiler, issue the command @command{make}, which performs the
1001 Build host tools necessary to build the compiler such as texinfo, bison,
1005 Build target tools for use by the compiler such as binutils (bfd,
1006 binutils, gas, gprof, ld, and opcodes)
1007 if they have been individually linked or moved into the top level GCC source
1008 tree before configuring.
1011 Build the compiler (single stage only).
1014 Build runtime libraries using the compiler from the previous step.
1017 Note that if an error occurs in any step the make process will exit.
1019 @section Building in parallel
1021 If you have a multiprocessor system you can use @samp{make bootstrap
1022 MAKE="make -j 2" -j 2} or just @samp{make -j 2 bootstrap}
1023 for GNU Make 3.79 and above instead of just @samp{make bootstrap}
1024 when building GCC@. You can use a bigger number instead of two if
1025 you like. In most cases, it won't help to use a number bigger than
1026 the number of processors in your machine.
1028 @section Building the Ada compiler
1030 In order to build GNAT, the Ada compiler, you need a working GNAT
1031 compiler, since the Ada front end is written in Ada (with some
1032 GNAT-specific extensions), and GNU make.
1034 However, you do not need a full installation of GNAT, just the GNAT
1035 binary @file{gnat1}, a copy of @file{gnatbind}, and a compiler driver
1036 which can deal with Ada input (by invoking the @file{gnat1} binary).
1037 You can specify this compiler driver by setting the @env{ADAC}
1038 environment variable at the configure step. @command{configure} can
1039 detect the driver automatically if it has got a common name such as
1040 @command{gcc} or @command{gnatgcc}. Of course, you still need a working
1041 C compiler (the compiler driver can be different or not).
1043 Additional build tools (such as @command{gnatmake}) or a working GNAT
1044 run-time library installation are usually @emph{not} required. However,
1045 if you want to boostrap the compiler using a minimal version of GNAT,
1046 you have to issue the following commands before invoking @samp{make
1047 boostrap} (this assumes that you start with an unmodified and consistent
1048 source distribution):
1051 cd @var{srcdir}/gcc/ada
1052 touch treeprs.ads [es]info.h nmake.ad[bs]
1055 At the moment, the GNAT library and several tools for GNAT are not built
1056 by @samp{make bootstrap}. You have to invoke
1057 @samp{make gnatlib_and_tools} in the @file{@var{objdir}/gcc}
1058 subdirectory before proceeding with the next steps.
1060 For example, you can build a native Ada compiler by issuing the
1061 following commands (assuming @command{make} is GNU make):
1065 @var{srcdir}/configure --enable-languages=c,ada
1066 cd @var{srcdir}/gcc/ada
1067 touch treeprs.ads [es]info.h nmake.ad[bs]
1071 make gnatlib_and_tools
1075 Currently, when compiling the Ada front end, you cannot use the parallel
1076 build feature described in the previous section.
1083 @uref{./index.html,,Return to the GCC Installation page}
1087 @c ***Testing*****************************************************************
1089 @comment node-name, next, previous, up
1090 @node Testing, Final install, Building, Installing GCC
1094 <h1 align="center">Installing GCC: Testing</h1>
1097 @chapter Installing GCC: Testing
1100 @cindex Installing GCC: Testing
1103 Before you install GCC, you might wish to run the testsuite. This
1104 step is optional and may require you to download additional software.
1106 First, you must have @uref{download.html,,downloaded the testsuites}.
1107 The full distribution contains testsuites; only if you downloaded the
1108 ``core'' compiler plus any front ends, you do not have the testsuites.
1110 Second, you must have a @uref{http://www.gnu.org/software/dejagnu/,,current version of DejaGnu} installed;
1111 dejagnu 1.3 is not sufficient.
1113 Now you may need specific preparations:
1118 The following environment variables may need to be set appropriately, as in
1119 the following example (which assumes that DejaGnu has been installed
1120 under @file{/usr/local}):
1123 TCL_LIBRARY = /usr/local/share/tcl8.0
1124 DEJAGNULIBS = /usr/local/share/dejagnu
1127 On systems such as Cygwin, these paths are required to be actual
1128 paths, not mounts or links; presumably this is due to some lack of
1129 portability in the DejaGnu code.
1131 If the directories where @command{runtest} and @command{expect} were
1132 installed are in the @env{PATH}, it should not be necessary to set these
1133 environment variables.
1137 Finally, you can run the testsuite (which may take a long time):
1139 cd @var{objdir}; make -k check
1142 The testing process will try to test as many components in the GCC
1143 distribution as possible, including the C, C++, Objective-C and Fortran
1144 compilers as well as the C++ and Java runtime libraries.
1146 @section How can I run the test suite on selected tests?
1148 As a first possibility to cut down the number of tests that are run it is
1149 possible to use @samp{make check-gcc} or @samp{make check-g++}
1150 in the @file{gcc} subdirectory of the object directory. To further cut down the
1151 tests the following is possible:
1154 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
1157 This will run all @command{gcc} execute tests in the testsuite.
1160 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
1163 This will run the @command{g++} ``old-deja'' tests in the testsuite where the filename
1164 matches @samp{9805*}.
1166 The @file{*.exp} files are located in the testsuite directories of the GCC
1167 source, the most important ones being @file{compile.exp},
1168 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
1169 To get a list of the possible @file{*.exp} files, pipe the
1170 output of @samp{make check} into a file and look at the
1171 @samp{Running @dots{} .exp} lines.
1173 @section How to interpret test results
1175 After the testsuite has run you'll find various @file{*.sum} and @file{*.log}
1176 files in the testsuite subdirectories. The @file{*.log} files contain a
1177 detailed log of the compiler invocations and the corresponding
1178 results, the @file{*.sum} files summarize the results. These summaries list
1179 all the tests that have been run with a corresponding status code:
1183 PASS: the test passed as expected
1185 XPASS: the test unexpectedly passed
1187 FAIL: the test unexpectedly failed
1189 XFAIL: the test failed as expected
1191 UNSUPPORTED: the test is not supported on this platform
1193 ERROR: the testsuite detected an error
1195 WARNING: the testsuite detected a possible problem
1198 It is normal for some tests to report unexpected failures. At the
1199 current time our testing harness does not allow fine grained control
1200 over whether or not a test is expected to fail. We expect to fix this
1201 problem in future releases.
1204 @section Submitting test results
1206 If you want to report the results to the GCC project, use the
1207 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
1210 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
1211 -m gcc-testresults@@gcc.gnu.org |sh
1214 This script uses the @command{Mail} program to send the results, so
1215 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
1216 prepended to the testsuite summary and should contain any special
1217 remarks you have on your results or your build environment. Please
1218 do not edit the testsuite result block or the subject line, as these
1219 messages are automatically parsed and presented at the
1220 @uref{http://gcc.gnu.org/testresults/,,GCC testresults} web
1221 page. Here you can also gather information on how specific tests
1222 behave on different platforms and compare them with your results. A
1223 few failing testcases are possible even on released versions and you
1224 should look here first if you think your results are unreasonable.
1231 @uref{./index.html,,Return to the GCC Installation page}
1235 @c ***Final install***********************************************************
1237 @comment node-name, next, previous, up
1238 @node Final install, , Testing, Installing GCC
1240 @ifset finalinstallhtml
1242 <h1 align="center">Installing GCC: Final installation</h1>
1245 @chapter Installing GCC: Final installation
1248 Now that GCC has been built (and optionally tested), you can install it with
1250 cd @var{objdir}; make install
1253 That step completes the installation of GCC; user level binaries can
1254 be found in @file{@var{prefix}/bin} where @var{prefix} is the value you
1255 specified with the @option{--prefix} to configure (or @file{/usr/local}
1256 by default). (If you specified @option{--bindir}, that directory will
1257 be used instead; otherwise, if you specified @option{--exec-prefix},
1258 @file{@var{exec-prefix}/bin} will be used.) Headers for the C++ and
1259 Java libraries are installed in @file{@var{prefix}/include}; libraries
1260 in @file{@var{libdir}} (normally @file{@var{prefix}/lib}); internal
1261 parts of the compiler in @file{@var{libdir}/gcc-lib}; documentation in
1262 info format in @file{@var{infodir}} (normally @file{@var{prefix}/info}).
1264 If you built a released version of GCC then if you don't mind, please
1265 quickly review the build status page for
1266 @uref{http://gcc.gnu.org/gcc-3.0/buildstat.html,,3.0} or
1267 @uref{http://gcc.gnu.org/gcc-2.95/buildstat.html,,2.95}.
1268 If your system is not listed for the version of GCC that you built,
1270 @email{gcc@@gcc.gnu.org} indicating
1271 that you successfully built and installed GCC.
1272 Include the following information:
1276 Output from running @file{@var{srcdir}/config.guess}. Do not send us
1277 that file itself, just the one-line output from running it.
1280 The output of @samp{gcc -v} for your newly installed gcc.
1281 This tells us which version of GCC you built and the options you passed to
1285 If the build was for GNU/Linux, also include:
1288 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
1289 this information should be available from @file{/etc/issue}.
1292 The version of the Linux kernel, available from @samp{uname --version}
1296 The version of glibc you used; for RPM-based systems like Red Hat,
1297 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
1298 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
1300 For other systems, you can include similar information if you think it is
1304 Any other information that you think would be useful to people building
1305 GCC on the same configuration. The new entry in the build status list
1306 will include a link to the archived copy of your message.
1309 We'd also like to know if the
1311 @ref{Specific, host/target specific installation notes}
1314 @uref{specific.html,,host/target specific installation notes}
1316 didn't include your host/target information or if that information is
1317 incomplete or out of date. Send a note to
1318 @email{gcc@@gcc.gnu.org} telling us how the information should be changed.
1320 If you find a bug, please report it following our
1321 @uref{../bugs.html,,bug reporting guidelines}.
1323 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
1324 dvi}. You will need to have @command{texi2dvi} (version at least 4.0)
1325 and @TeX{} installed. This creates a number of @file{.dvi} files in
1326 subdirectories of @file{@var{objdir}}; these may be converted for
1327 printing with programs such as @command{dvips}. You can also
1328 @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the
1329 Free Software Foundation}, though such manuals may not be for the most
1330 recent version of GCC@.
1337 @uref{./index.html,,Return to the GCC Installation page}
1341 @c ***Binaries****************************************************************
1343 @comment node-name, next, previous, up
1344 @node Binaries, Specific, Installing GCC, Top
1348 <h1 align="center">Installing GCC: Binaries</h1>
1351 @chapter Installing GCC: Binaries
1354 @cindex Installing GCC: Binaries
1356 We are often asked about pre-compiled versions of GCC@. While we cannot
1357 provide these for all platforms, below you'll find links to binaries for
1358 various platforms where creating them by yourself is not easy due to various
1361 Please note that we did not create these binaries, nor do we
1362 support them. If you have any problems installing them, please
1363 contact their makers.
1370 @uref{http://freeware.bull.net,,Bull's Freeware and Shareware Archive for AIX};
1373 @uref{http://aixpdslib.seas.ucla.edu,,UCLA Software Library for AIX};
1377 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP};
1383 @uref{http://hpux.cae.wisc.edu/,,HP-UX Porting Center};
1386 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
1390 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
1391 OpenServer/Unixware};
1394 Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware};
1397 SGI---@uref{http://freeware.sgi.com/,,SGI Freeware};
1400 Windows 95, 98, and NT:
1403 The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project;
1405 @uref{http://www.xraylith.wisc.edu/~khan/software/gnu-win32/,,GNU Win32}
1406 related projects by Mumit Khan.
1410 @uref{ftp://ftp.thewrittenword.com/packages/free/by-name/,,The
1411 Written Word} offers binaries for Solaris 2.5.1, 2.6, 2.7/SPARC, 2.7/Intel,
1412 IRIX 6.2, 6.5, Digital UNIX 4.0D, HP-UX 10.20, and HP-UX 11.00.
1415 Hitachi H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
1416 Development Tools for the Hitachi H8/300[HS] Series}
1420 In addition to those specific offerings, you can get a binary
1421 distribution CD-ROM from the
1422 @uref{http://www.fsf.org/order/order.html,,Free Software Foundation}.
1423 It contains binaries for a number of platforms, and
1424 includes not only GCC, but other stuff as well. The current CD does
1425 not contain the latest version of GCC, but it should allow
1426 bootstrapping the compiler. An updated version of that disk is in the
1434 @uref{./index.html,,Return to the GCC Installation page}
1438 @c ***Specific****************************************************************
1440 @comment node-name, next, previous, up
1441 @node Specific, Old, Binaries, Top
1445 <h1 align="center">Host/target specific installation notes for GCC</h1>
1448 @chapter Host/target specific installation notes for GCC
1451 @cindex Specific installation notes
1452 @cindex Target specific installation
1453 @cindex Host specific installation
1454 @cindex Target specific installation notes
1456 Please read this document carefully @emph{before} installing the
1457 GNU Compiler Collection on your machine.
1459 Lists of successful builds for released versions of GCC are
1460 available at our web pages for
1461 @uref{http://gcc.gnu.org/gcc-3.0/buildstat.html,,3.0}
1463 @uref{http://gcc.gnu.org/gcc-2.95/buildstat.html,,2.95}.
1464 These lists are updated as new information becomes available.
1469 @uref{#1750a-*-*,,1750a-*-*}
1473 @uref{#a29k-*-bsd,,a29k-*-bsd}
1475 @uref{#alpha*-*-*,,alpha*-*-*}
1477 @uref{#alpha*-dec-osf*,,alpha*-dec-osf*}
1479 @uref{#alphaev5-cray-unicosmk*,,alphaev5-cray-unicosmk*}
1481 @uref{#arc-*-elf,,arc-*-elf}
1483 @uref{#arm-*-aout,,arm-*-aout}
1485 @uref{#arm-*-elf,,arm-*-elf}
1487 @uref{#arm*-*-linux-gnu,,arm*-*-linux-gnu}
1489 @uref{#arm-*-riscix,,arm-*-riscix}
1497 @uref{#dsp16xx,,dsp16xx}
1499 @uref{#elxsi-elxsi-bsd,,elxsi-elxsi-bsd}
1501 @uref{#*-*-freebsd*,,*-*-freebsd*}
1503 @uref{#h8300-hms,,h8300-hms}
1505 @uref{#hppa*-hp-hpux*,,hppa*-hp-hpux*}
1507 @uref{#hppa*-hp-hpux9,,hppa*-hp-hpux9}
1509 @uref{#hppa*-hp-hpux10,,hppa*-hp-hpux10}
1511 @uref{#hppa*-hp-hpux11,,hppa*-hp-hpux11}
1513 @uref{#i370-*-*,,i370-*-*}
1515 @uref{#*-*-linux-gnu,,*-*-linux-gnu}
1517 @uref{#ix86-*-linux*oldld,,i?86-*-linux*oldld}
1519 @uref{#ix86-*-linux*aout,,i?86-*-linux*aout}
1521 @uref{#ix86-*-linux*,,i?86-*-linux*}
1523 @uref{#ix86-*-sco,,i?86-*-sco}
1525 @uref{#ix86-*-sco3.2v4,,i?86-*-sco3.2v4}
1527 @uref{#ix86-*-sco3.2v5*,,i?86-*-sco3.2v5*}
1529 @uref{#ix86-*-udk,,i?86-*-udk}
1531 @uref{#ix86-*-isc,,i?86-*-isc}
1533 @uref{#ix86-*-esix,,i?86-*-esix}
1535 @uref{#ix86-ibm-aix,,i?86-ibm-aix}
1537 @uref{#ix86-sequent-bsd,,i?86-sequent-bsd}
1539 @uref{#ix86-sequent-ptx1*,,i?86-sequent-ptx1*, i?86-sequent-ptx2*}
1541 @uref{#ix86-*-sysv3*,,i?86-*-sysv3*}
1543 @uref{#i860-intel-osf*,,i860-intel-osf*}
1545 @uref{#ia64-*-linux,,ia64-*-linux}
1547 @uref{#*-lynx-lynxos,,*-lynx-lynxos}
1549 @uref{#*-ibm-aix*,,*-ibm-aix*}
1551 @uref{#m32r-*-elf,,m32r-*-elf}
1553 @uref{#m68000-hp-bsd,,m68000-hp-bsd}
1555 @uref{#m6811-elf,,m6811-elf}
1557 @uref{#m6812-elf,,m6812-elf}
1559 @uref{#m68k-altos,,m68k-altos}
1561 @uref{#m68k-apple-aux,,m68k-apple-aux}
1563 @uref{#m68k-att-sysv,,m68k-att-sysv}
1565 @uref{#m68k-bull-sysv,,m68k-bull-sysv}
1567 @uref{#m68k-crds-unox,,m68k-crds-unox}
1569 @uref{#m68k-hp-hpux,,m68k-hp-hpux}
1571 @uref{#m68k-*-nextstep*,,m68k-*-nextstep*}
1573 @uref{#m68k-ncr-*,,m68k-ncr-*}
1575 @uref{#m68k-sun,,m68k-sun}
1577 @uref{#m68k-sun-sunos4.1.1,,m68k-sun-sunos4.1.1}
1579 @uref{#m88k-*-svr3,,m88k-*-svr3}
1581 @uref{#m88k-*-dgux,,m88k-*-dgux}
1583 @uref{#m88k-tektronix-sysv3,,m88k-tektronix-sysv3}
1585 @uref{#mips-*-*,,mips-*-*}
1587 @uref{#mips-dec-*,,mips-dec-*}
1589 @uref{#mips-mips-bsd,,mips-mips-bsd}
1591 @uref{#mips-mips-riscos*,,mips-mips-riscos*}
1593 @uref{#mips-sgi-irix4,,mips-sgi-irix4}
1595 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
1597 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
1599 @uref{#mips-sony-sysv,,mips-sony-sysv}
1601 @uref{#ns32k-encore,,ns32k-encore}
1603 @uref{#ns32k-*-genix,,ns32k-*-genix}
1605 @uref{#ns32k-sequent,,ns32k-sequent}
1607 @uref{#ns32k-utek,,ns32k-utek}
1609 @uref{#powerpc*-*-*,,powerpc*-*-*, powerpc-*-sysv4}
1611 @uref{#powerpc-*-darwin*,,powerpc-*-darwin*}
1613 @uref{#powerpc-*-elf,,powerpc-*-elf, powerpc-*-sysv4}
1615 @uref{#powerpc-*-linux-gnu*,,powerpc-*-linux-gnu*}
1617 @uref{#powerpc-*-netbsd*,,powerpc-*-netbsd*}
1619 @uref{#powerpc-*-eabiaix,,powerpc-*-eabiaix}
1621 @uref{#powerpc-*-eabisim,,powerpc-*-eabisim}
1623 @uref{#powerpc-*-eabi,,powerpc-*-eabi}
1625 @uref{#powerpcle-*-elf,,powerpcle-*-elf, powerpcle-*-sysv4}
1627 @uref{#powerpcle-*-eabisim,,powerpcle-*-eabisim}
1629 @uref{#powerpcle-*-eabi,,powerpcle-*-eabi}
1631 @uref{#powerpcle-*-winnt,,powerpcle-*-winnt, powerpcle-*-pe}
1633 @uref{#romp-*-aos,,romp-*-aos, romp-*-mach}
1635 @uref{#s390-*-linux*}
1637 @uref{#s390x-*-linux*}
1639 @uref{#*-*-solaris2*,,*-*-solaris2*}
1641 @uref{#sparc-sun-solaris2*,,sparc-sun-solaris2*}
1643 @uref{#sparc-sun-solaris2.7,,sparc-sun-solaris2.7}
1645 @uref{#*-*-solaris2.8,,*-*-solaris2.8}
1647 @uref{#sparc-sun-sunos4*,,sparc-sun-sunos4*}
1649 @uref{#sparc-unknown-linux-gnulibc1,,sparc-unknown-linux-gnulibc1}
1651 @uref{#sparc-*-linux*,,sparc-*-linux*}
1653 @uref{#sparc64-*-*,,sparc64-*-*}
1655 @uref{#sparcv9-*-solaris2*,,sparcv9-*-solaris2*}
1657 @uref{#*-*-sysv*,,*-*-sysv*}
1659 @uref{#vax-dec-ultrix,,vax-dec-ultrix}
1661 @uref{#we32k-*-*,,we32k-*-*}
1663 @uref{#xtensa-*-elf,,xtensa-*-elf}
1665 @uref{#xtensa-*-linux*,,xtensa-*-linux*}
1667 @uref{#windows,,Microsoft Windows}
1671 @uref{#older,,Older systems}
1676 @uref{#elf_targets,,all ELF targets} (SVR4, Solaris 2, etc.)
1682 <!-- -------- host/target specific issues start here ---------------- -->
1685 @heading @anchor{1750a-*-*}1750a-*-*
1686 MIL-STD-1750A processors.
1688 The MIL-STD-1750A cross configuration produces output for
1689 @code{as1750}, an assembler/linker available under the GNU General Public
1690 License for the 1750A@. @code{as1750} can be obtained at
1691 @uref{ftp://ftp.fta-berlin.de/pub/crossgcc/1750gals/}.
1692 A similarly licensed simulator for
1693 the 1750A is available from same address.
1695 You should ignore a fatal error during the building of @samp{libgcc}
1696 (@samp{libgcc} is not yet implemented for the 1750A@.)
1698 The @code{as1750} assembler requires the file @file{ms1750.inc}, which is
1699 found in the directory @file{gcc/config/1750a}.
1701 GCC produced the same sections as the Fairchild F9450 C Compiler,
1706 The program code section.
1709 The read/write (RAM) data section.
1712 The read-only (ROM) constants section.
1715 Initialization section (code to copy KREL to SREL)@.
1718 The smallest addressable unit is 16 bits (@code{BITS_PER_UNIT} is 16). This
1719 means that type @code{char} is represented with a 16-bit word per character.
1720 The 1750A's ``Load/Store Upper/Lower Byte'' instructions are not used by
1727 @heading @anchor{a29k}a29k
1728 AMD Am29k-family processors. These are normally used in embedded
1729 applications. There are no standard Unix configurations.
1731 corresponds to AMD's standard calling sequence and binary interface
1732 and is compatible with other 29k tools.
1734 You may need to make a variant of the file @file{a29k.h} for your
1735 particular configuration.
1741 @heading @anchor{a29k-*-bsd}a29k-*-bsd
1742 AMD Am29050 used in a system running a variant of BSD Unix.
1748 @heading @anchor{alpha*-*-*}alpha*-*-*
1750 This section contains general configuration information for all
1751 alpha-based platforms using ELF (in particular, ignore this section for
1752 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
1753 section, please read all other sections that match your target.
1755 We require binutils 2.11.2 or newer.
1756 Previous binutils releases had a number of problems with DWARF 2
1757 debugging information, not the least of which is incorrect linking of
1764 @heading @anchor{alpha*-dec-osf*}alpha*-dec-osf*
1765 Systems using processors that implement the DEC Alpha architecture and
1766 are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
1767 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
1769 In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
1770 currently (2001-06-13) work with @command{mips-tfile}. As a workaround,
1771 we need to use the old assembler, invoked via the barely documented
1772 @option{-oldas} option. To bootstrap GCC, you either need to use the
1776 % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
1779 or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
1782 % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
1785 As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld}
1786 are supported on Tru64 UNIX, so you must not configure GCC with
1787 @option{--with-gnu-as} or @option{--with-gnu-ld}.
1789 The @option{--enable-threads} options isn't supported yet. A patch is
1790 in preparation for a future release.
1792 GCC writes a @samp{.verstamp} directive to the assembler output file
1793 unless it is built as a cross-compiler. It gets the version to use from
1794 the system header file @file{/usr/include/stamp.h}. If you install a
1795 new version of DEC Unix, you should rebuild GCC to pick up the new version
1798 Note that since the Alpha is a 64-bit architecture, cross-compilers from
1799 32-bit machines will not generate code as efficient as that generated
1800 when the compiler is running on a 64-bit machine because many
1801 optimizations that depend on being able to represent a word on the
1802 target in an integral value on the host cannot be performed. Building
1803 cross-compilers on the Alpha for 32-bit machines has only been tested in
1804 a few cases and may not work properly.
1806 @code{make compare} may fail on old versions of DEC Unix unless you add
1807 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
1808 assembler input file is stored in the object file, and that makes
1809 comparison fail if it differs between the @code{stage1} and
1810 @code{stage2} compilations. The option @option{-save-temps} forces a
1811 fixed name to be used for the assembler input file, instead of a
1812 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
1813 unless the comparisons fail without that option. If you add
1814 @option{-save-temps}, you will have to manually delete the @samp{.i} and
1815 @samp{.s} files after each series of compilations.
1817 GCC now supports both the native (ECOFF) debugging format used by DBX
1818 and GDB and an encapsulated STABS format for use only with GDB@. See the
1819 discussion of the @option{--with-stabs} option of @file{configure} above
1820 for more information on these formats and how to select them.
1822 There is a bug in DEC's assembler that produces incorrect line numbers
1823 for ECOFF format when the @samp{.align} directive is used. To work
1824 around this problem, GCC will not emit such alignment directives
1825 while writing ECOFF format debugging information even if optimization is
1826 being performed. Unfortunately, this has the very undesirable
1827 side-effect that code addresses when @option{-O} is specified are
1828 different depending on whether or not @option{-g} is also specified.
1830 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
1831 DBX@. DEC is now aware of this problem with the assembler and hopes to
1832 provide a fix shortly.
1838 @heading @anchor{alphaev5-cray-unicosmk*}alphaev5-cray-unicosmk*
1839 Cray T3E systems running Unicos/Mk.
1841 This port is incomplete and has many known bugs. We hope to improve the
1842 support for this target soon. Currently, only the C front end is supported,
1843 and it is not possible to build parallel applications. Cray modules are not
1844 supported; in particular, Craylibs are assumed to be in
1845 @file{/opt/ctl/craylibs/craylibs}.
1847 You absolutely @strong{must} use GNU make on this platform. Also, you
1848 need to tell GCC where to find the assembler and the linker. The
1849 simplest way to do so is by providing @option{--with-as} and
1850 @option{--with-ld} to @file{configure}, e.g.@:
1852 @samp{configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld
1853 --enable-languages=c}
1855 The comparison test during @samp{make bootstrap} fails on Unicos/Mk
1856 because the assembler inserts timestamps into object files. You should
1857 be able to work around this by doing @samp{make all} after getting this
1864 @heading @anchor{arc-*-elf}arc-*-elf
1865 Argonaut ARC processor.
1866 This configuration is intended for embedded systems.
1872 @heading @anchor{arm-*-aout}arm-*-aout
1873 Advanced RISC Machines ARM-family processors. These are often used in
1874 embedded applications. There are no standard Unix configurations.
1875 This configuration corresponds to the basic instruction sequences and will
1876 produce @file{a.out} format object modules.
1878 You may need to make a variant of the file @file{arm.h} for your particular
1885 @heading @anchor{arm-*-elf}arm-*-elf
1886 This configuration is intended for embedded systems.
1892 @heading @anchor{arm*-*-linux-gnu}arm*-*-linux-gnu
1894 We require GNU binutils 2.10 or newer.
1900 @heading @anchor{arm-*-riscix}arm-*-riscix
1901 The ARM2 or ARM3 processor running RISC iX, Acorn's port of BSD Unix.
1902 If you are running a version of RISC iX prior to 1.2 then you must
1903 specify the version number during configuration. Note that the
1904 assembler shipped with RISC iX does not support stabs debugging
1905 information; a new version of the assembler, with stabs support
1906 included, is now available from Acorn and via ftp
1907 @uref{ftp://ftp.acorn.com/pub/riscix/as+xterm.tar.Z}. To enable stabs
1908 debugging, pass @option{--with-gnu-as} to configure.
1910 You will need to install GNU @command{sed} before you can run configure.
1916 @heading @anchor{avr}avr
1918 ATMEL AVR-family micro controllers. These are used in embedded
1919 applications. There are no standard Unix configurations.
1921 @xref{AVR Options,, AVR Options, gcc, Using and Porting the GNU Compiler
1925 See ``AVR Options'' in the main manual
1927 for the list of supported MCU types.
1929 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
1931 Further installation notes and other useful information about AVR tools
1932 can also be obtained from:
1936 @uref{http://home.overta.ru/users/denisc,,http://home.overta.ru/users/denisc}
1938 @uref{http://www.amelek.gda.pl/avr,,http://www.amelek.gda.pl/avr}
1941 We @emph{strongly} recommend using binutils 2.11 or newer.
1943 The following error:
1945 Error: register required
1948 indicates that you should upgrade to a newer version of the binutils.
1954 @heading @anchor{c4x}c4x
1956 Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal
1957 Processors. These are used in embedded applications. There are no
1958 standard Unix configurations.
1960 @xref{TMS320C3x/C4x Options,, TMS320C3x/C4x Options, gcc, Using and
1961 Porting the GNU Compiler Collection (GCC)},
1964 See ``TMS320C3x/C4x Options'' in the main manual
1966 for the list of supported MCU types.
1968 GCC can be configured as a cross compiler for both the C3x and C4x
1969 architectures on the same system. Use @samp{configure --target=c4x
1970 --enable-languages="c,c++"} to configure.
1973 Further installation notes and other useful information about C4x tools
1974 can also be obtained from:
1978 @uref{http://www.elec.canterbury.ac.nz/c4x/,,http://www.elec.canterbury.ac.nz/c4x/}
1985 @heading @anchor{cris}CRIS
1987 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
1988 series. These are used in embedded applications.
1991 @xref{CRIS Options,, CRIS Options, gcc, Using and Porting the GNU Compiler
1995 See ``CRIS Options'' in the main manual
1997 for a list of CRIS-specific options.
1999 There are a few different CRIS targets:
2001 @item cris-axis-aout
2002 Old target. Includes a multilib for the @samp{elinux} a.out-based
2003 target. No multilibs for newer architecture variants.
2005 Mainly for monolithic embedded systems. Includes a multilib for the
2006 @samp{v10} core used in @samp{ETRAX 100 LX}.
2007 @item cris-axis-linux-gnu
2008 A GNU/Linux port for the CRIS architecture, currently targeting
2009 @samp{ETRAX 100 LX} by default.
2012 For @code{cris-axis-aout} and @code{cris-axis-elf} you need binutils 2.11
2013 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
2015 Pre-packaged tools can be obtained from
2016 @uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More
2017 information about this platform is available at
2018 @uref{http://developer.axis.com/}.
2024 @heading @anchor{dos}DOS
2026 Please have a look at our @uref{binaries.html,,binaries page}.
2028 You cannot install GCC by itself on MSDOS; it will not compile under
2029 any MSDOS compiler except itself. You need to get the complete
2030 compilation package DJGPP, which includes binaries as well as sources,
2031 and includes all the necessary compilation tools and libraries.
2037 @heading @anchor{dsp16xx}dsp16xx
2038 A port to the AT&T DSP1610 family of processors.
2044 @heading @anchor{*-*-freebsd*}*-*-freebsd*
2046 The version of binutils installed in @file{/usr/bin} is known to work unless
2047 otherwise specified in any per-architecture notes. However, binutils
2048 2.11 or greater is known to improve overall testsuite results.
2050 For FreeBSD 1, FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
2051 configuration support and files as shipped with GCC 2.95 are still in
2052 place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
2053 it is unknown which version of binutils was used (it is assumed that it
2054 was the system copy in @file{/usr/bin}) and C++ EH failures were noted.
2056 For FreeBSD using the ELF file format: DWARF 2 debugging is now the
2057 default for all CPU architectures. It had been the default on
2058 FreeBSD/alpha since its inception. You may use @option{-gstabs} instead
2059 of @option{-g}, if you really want the old debugging format. There are
2060 no known issues with mixing object files and libraries with different
2061 debugging formats. Otherwise, this release of GCC should now match more
2062 of the configuration used in the stock FreeBSD configuration of GCC. In
2063 particular, @option{--enable-threads} is now configured by default.
2064 However, as a general user, do not attempt to replace the system
2065 compiler with this release. Known to bootstrap and check with good
2066 results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4, 4.5-STABLE and 5-CURRENT@.
2068 In principle, @option{--enable-threads} is now compatible with
2069 @option{--enable-libgcj} on FreeBSD@. However, it has only been built
2070 and tested on i386-*-freebsd4.5 and alpha-*-freebsd5.0 and important
2071 test suite failures remain. Multi-threaded boehm-gc (required for
2072 libjava) exposes severe threaded signal-handling bugs on FreeBSD before
2073 4.5-RELEASE. The alpha port may not fully bootstrap without some manual
2074 intervention: gcjh will crash with a floating-point exception while
2075 generating @file{java/lang/Double.h} (just copy the version built on
2076 i386-*-freebsd* and rerun the top-level gmake with no arguments and it
2077 should properly complete the bootstrap). Other CPU architectures
2078 supported by FreeBSD will require additional configuration tuning in, at
2079 the very least, both boehm-gc and libffi.
2081 Shared @file{libgcc_s.so} is now built and installed by default.
2087 @heading @anchor{elxsi-elxsi-bsd}elxsi-elxsi-bsd
2088 The Elxsi's C compiler has known limitations that prevent it from
2089 compiling GCC@. Please contact @email{mrs@@wrs.com} for more details.
2095 @heading @anchor{h8300-hms}h8300-hms
2096 Hitachi H8/300 series of processors.
2098 Please have a look at our @uref{binaries.html,,binaries page}.
2100 The calling convention and structure layout has changed in release 2.6.
2101 All code must be recompiled. The calling convention now passes the
2102 first three arguments in function calls in registers. Structures are no
2103 longer a multiple of 2 bytes.
2109 @heading @anchor{hppa*-hp-hpux*}hppa*-hp-hpux*
2111 We @emph{highly} recommend using gas/binutils 2.8 or newer on all hppa
2112 platforms; you may encounter a variety of problems when using the HP
2115 Specifically, @option{-g} does not work on HP-UX (since that system
2116 uses a peculiar debugging format which GCC does not know about), unless you
2117 use GAS and GDB and configure GCC with the
2118 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
2119 @option{--with-as=@dots{}} options.
2121 If you wish to use pa-risc 2.0 architecture support, you must use either
2122 the HP assembler, gas/binutils 2.11 or a recent
2123 @uref{ftp://sources.redhat.com/pub/binutils/snapshots,,snapshot of gas}.
2125 More specific information to @samp{hppa*-hp-hpux*} targets follows.
2131 @heading @anchor{hppa*-hp-hpux9}hppa*-hp-hpux9
2133 The HP assembler has major problems on this platform. We've tried to work
2134 around the worst of the problems. However, those workarounds may be causing
2135 linker crashes in some circumstances; the workarounds also probably prevent
2136 shared libraries from working. Use the GNU assembler to avoid these problems.
2139 The configuration scripts for GCC will also trigger a bug in the hpux9
2140 shell. To avoid this problem set @env{CONFIG_SHELL} to @file{/bin/ksh}
2141 and @env{SHELL} to @file{/bin/ksh} in your environment.
2148 @heading @anchor{hppa*-hp-hpux10}hppa*-hp-hpux10
2150 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
2151 @code{PHCO_19798} from HP@. HP has two sites which provide patches free of
2157 <a href="http://us-support.external.hp.com">US, Canada, Asia-Pacific, and
2161 @uref{http://us-support.external.hp.com,,}US, Canada, Asia-Pacific, and
2165 @uref{http://europe-support.external.hp.com,,Europe}
2168 The HP assembler on these systems is much better than the hpux9 assembler,
2169 but still has some problems. Most notably the assembler inserts timestamps
2170 into each object file it creates, causing the 3-stage comparison test to fail
2171 during a @samp{make bootstrap}. You should be able to continue by
2172 saying @samp{make all} after getting the failure from @samp{make
2180 @heading @anchor{hppa*-hp-hpux11}hppa*-hp-hpux11
2182 GCC 3.0 supports HP-UX 11. You must use GNU binutils 2.11 or above on
2183 this platform. Thread support is not currently implemented for this
2184 platform, so @option{--enable-threads} does not work.
2185 See @uref{http://gcc.gnu.org/ml/gcc-prs/2002-01/msg00551.html}
2186 and @uref{http://gcc.gnu.org/ml/gcc-bugs/2002-01/msg00663.html}.
2187 GCC 2.95.x is not supported under HP-UX 11 and cannot be used to
2188 compile GCC 3.0. Refer to @uref{binaries.html,,binaries} for information
2189 about obtaining precompiled GCC binaries for HP-UX.
2195 @heading @anchor{i370-*-*}i370-*-*
2196 This port is very preliminary and has many known bugs. We hope to
2197 have a higher-quality port for this machine soon.
2203 @heading @anchor{*-*-linux-gnu}*-*-linux-gnu
2205 If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install
2206 out-of-the-box. You'll get compile errors while building @samp{libstdc++}.
2207 The patch @uref{glibc-2.2.patch,,glibc-2.2.patch}, that is to be
2208 applied in the GCC source tree, fixes the compatibility problems.
2218 Currently Glibc 2.2.3 (and older releases) and GCC 3.0 are out of sync
2219 since the latest exception handling changes for GCC@. Compiling glibc
2220 with GCC 3.0 will give a binary incompatible glibc and therefore cause
2221 lots of problems and might make your system completly unusable. This
2222 will definitly need fixes in glibc but might also need fixes in GCC@. We
2223 strongly advise to wait for glibc 2.2.4 and to read the release notes of
2224 glibc 2.2.4 whether patches for GCC 3.0 are needed. You can use glibc
2225 2.2.3 with GCC 3.0, just do not try to recompile it.
2231 @heading @anchor{ix86-*-linux*oldld}i?86-*-linux*oldld
2232 Use this configuration to generate @file{a.out} binaries on Linux-based
2233 GNU systems if you do not have gas/binutils version 2.5.2 or later
2234 installed. This is an obsolete configuration.
2240 @heading @anchor{ix86-*-linux*aout}i?86-*-linux*aout
2241 Use this configuration to generate @file{a.out} binaries on Linux-based
2242 GNU systems. This configuration is being superseded. You must use
2243 gas/binutils version 2.5.2 or later.
2249 @heading @anchor{ix86-*-linux*}i?86-*-linux*
2251 You will need binutils 2.9.1.0.15 or newer for exception handling to work.
2253 If you receive Signal 11 errors when building on GNU/Linux, then it is
2254 possible you have a hardware problem. Further information on this can be
2255 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
2261 @heading @anchor{ix86-*-sco}i?86-*-sco
2262 Compilation with RCC is recommended. Also, it may be a good idea to
2263 link with GNU malloc instead of the malloc that comes with the system.
2269 @heading @anchor{ix86-*-sco3.2v4}i?86-*-sco3.2v4
2270 Use this configuration for SCO release 3.2 version 4.
2276 @heading @anchor{ix86-*-sco3.2v5*}i?86-*-sco3.2v5*
2277 Use this for the SCO OpenServer Release 5 family of operating systems.
2279 Unlike earlier versions of GCC, the ability to generate COFF with this
2280 target is no longer provided.
2282 Earlier versions of GCC emitted DWARF 1 when generating ELF to allow
2283 the system debugger to be used. That support was too burdensome to
2284 maintain. GCC now emits only DWARF 2 for this target. This means you
2285 may use either the UDK debugger or GDB to debug programs built by this
2288 Use of the @option{-march=pentiumpro} flag can result in
2289 unrecognized opcodes when using the native assembler on OS versions before
2290 5.0.6. (Support for P6 opcodes was added to the native ELF assembler in
2291 that version.) While it's rather rare to see these emitted by GCC yet,
2292 errors of the basic form:
2295 /usr/tmp/ccaNlqBc.s:22:unknown instruction: fcomip
2296 /usr/tmp/ccaNlqBc.s:50:unknown instruction: fucomip
2299 are symptoms of this problem. You may work around this by not
2300 building affected files with that flag, by using the GNU assembler, or
2301 by using the assembler provided with the current version of the OS@.
2302 Users of GNU assembler should see the note below for hazards on doing
2305 The native SCO assembler that is provided with the OS at no
2306 charge is normally required. If, however, you must be able to use
2307 the GNU assembler (perhaps you're compiling code with asms that
2308 require GAS syntax) you may configure this package using the flags
2309 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You must
2310 use a recent version of GNU binutils; versions past 2.9.1 seem to work
2313 In general, the @option{--with-gnu-as} option isn't as well tested
2314 as the native assembler.
2316 Look in @file{gcc/config/i386/sco5.h} (search for ``messy'') for
2317 additional OpenServer-specific flags.
2319 Systems based on OpenServer before 5.0.4 (@samp{uname -X}
2320 will tell you what you're running) require TLS597 from
2321 @uref{ftp://ftp.sco.com/TLS/,,ftp://ftp.sco.com/TLS/}
2322 for C++ constructors and destructors to work right.
2324 The system linker in (at least) 5.0.4 and 5.0.5 will sometimes
2325 do the wrong thing for a construct that GCC will emit for PIC
2326 code. This can be seen as execution testsuite failures when using
2327 @option{-fPIC} on @file{921215-1.c}, @file{931002-1.c}, @file{nestfunc-1.c}, and @file{gcov-1.c}.
2328 For 5.0.5, an updated linker that will cure this problem is
2329 available. You must install both
2330 @uref{ftp://ftp.sco.com/Supplements/rs505a/,,ftp://ftp.sco.com/Supplements/rs505a/}
2331 and @uref{ftp://ftp.sco.com/SLS/,,OSS499A}.
2333 The dynamic linker in OpenServer 5.0.5 (earlier versions may show
2334 the same problem) aborts on certain G77-compiled programs. It's particularly
2335 likely to be triggered by building Fortran code with the @option{-fPIC} flag.
2336 Although it's conceivable that the error could be triggered by other
2337 code, only G77-compiled code has been observed to cause this abort.
2338 If you are getting core dumps immediately upon execution of your
2339 G77 program---and especially if it's compiled with @option{-fPIC}---try applying
2340 @uref{sco_osr5_g77.patch,,@file{sco_osr5_g77.patch}} to your @samp{libf2c} and
2342 Affected faults, when analyzed in a debugger, will show a stack
2343 backtrace with a fault occurring in @code{rtld()} and the program
2344 running as @file{/usr/lib/ld.so.1}. This problem has been reported to SCO
2345 engineering and will hopefully be addressed in later releases.
2352 @heading @anchor{ix86-*-udk}i?86-*-udk
2354 This target emulates the SCO Universal Development Kit and requires that
2355 package be installed. (If it is installed, you will have a
2356 @file{/udk/usr/ccs/bin/cc} file present.) It's very much like the
2357 @samp{i?86-*-unixware7*} target
2358 but is meant to be used when hosting on a system where UDK isn't the
2359 default compiler such as OpenServer 5 or Unixware 2. This target will
2360 generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
2361 with the same warnings and caveats as the SCO UDK@.
2363 This target is a little tricky to build because we have to distinguish
2364 it from the native tools (so it gets headers, startups, and libraries
2365 from the right place) while making the tools not think we're actually
2366 building a cross compiler. The easiest way to do this is with a configure
2369 @samp{CC=/udk/usr/ccs/bin/cc @var{/your/path/to}/gcc/configure
2370 --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-}
2372 @emph{You should substitute @samp{i686} in the above command with the appropriate
2373 processor for your host.}
2375 After the usual @samp{make bootstrap} and
2376 @samp{make install}, you can then access the UDK-targeted GCC
2377 tools by adding @command{udk-} before the commonly known name. For
2378 example, to invoke the C compiler, you would use @command{udk-gcc}.
2379 They will coexist peacefully with any native-target GCC tools you may
2387 @heading @anchor{ix86-*-isc}i?86-*-isc
2388 It may be a good idea to link with GNU malloc instead of the malloc that
2389 comes with the system.
2391 In ISC version 4.1, @command{sed} core dumps when building
2392 @file{deduced.h}. Use the version of @command{sed} from version 4.0.
2398 @heading @anchor{ix86-*-esix}i?86-*-esix
2399 It may be good idea to link with GNU malloc instead of the malloc that
2400 comes with the system.
2406 @heading @anchor{ix86-ibm-aix}i?86-ibm-aix
2407 You need to use GAS version 2.1 or later, and LD from
2408 GNU binutils version 2.2 or later.
2414 @heading @anchor{ix86-sequent-bsd}i?86-sequent-bsd
2415 Go to the Berkeley universe before compiling.
2421 @heading @anchor{ix86-sequent-ptx1*}i?86-sequent-ptx1*, i?86-sequent-ptx2*
2422 You must install GNU @command{sed} before running @command{configure}.
2428 @heading @anchor{#ix86-*-sysv3*}i?86-*-sysv3*
2429 The @code{fixproto} shell script may trigger a bug in the system shell.
2430 If you encounter this problem, upgrade your operating system or
2431 use @command{bash} (the GNU shell) to run @code{fixproto}.
2438 @heading @anchor{i860-intel-osf*}i860-intel-osf*
2439 On the Intel Paragon (an i860 machine), if you are using operating
2440 system version 1.0, you will get warnings or errors about redefinition
2441 of @code{va_arg} when you build GCC@.
2443 If this happens, then you need to link most programs with the library
2444 @file{iclib.a}. You must also modify @file{stdio.h} as follows: before
2448 #if defined(__i860__) && !defined(_VA_LIST)
2449 #include <va_list.h>
2463 extern int vprintf(const char *, va_list );
2464 extern int vsprintf(char *, const char *, va_list );
2472 #endif /* __PGC__ */
2475 These problems don't exist in operating system version 1.1.
2481 @heading @anchor{ia64-*-linux}ia64-*-linux
2482 IA-64 processor (also known as IPF, or Itanium Processor Family)
2485 The toolchain is not completely finished, so requirements will continue
2487 GCC 3.0.1 and later require glibc 2.2.4.
2488 GCC 3.0.2 requires binutils from 2001-09-05 or later.
2489 GCC 3.0.1 requires binutils 2.11.1 or later.
2491 None of the following versions of GCC has an ABI that is compatible
2492 with any of the other versions in this list, with the exception that
2493 Red Hat 2.96 and Trillian 000171 are compatible with each other:
2494 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
2495 This primarily affects C++ programs and programs that create shared libraries.
2496 Because of these ABI incompatibilities, GCC 3.0.2 is not recommended for
2497 user programs on GNU/Linux systems built using earlier compiler releases.
2498 GCC 3.0.2 is recommended for compiling linux, the kernel.
2499 GCC 3.0.2 is believed to be fully ABI compliant, and hence no more major
2500 ABI changes are expected.
2506 @heading @anchor{*-lynx-lynxos}*-lynx-lynxos
2507 LynxOS 2.2 and earlier comes with GCC 1.x already installed as
2508 @file{/bin/gcc}. You should compile with this instead of @file{/bin/cc}.
2509 You can tell GCC to use the GNU assembler and linker, by specifying
2510 @samp{--with-gnu-as --with-gnu-ld} when configuring. These will produce
2511 COFF format object files and executables; otherwise GCC will use the
2512 installed tools, which produce @file{a.out} format executables.
2517 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
2519 @heading @anchor{*-ibm-aix*}*-ibm-aix*
2521 AIX Make frequently has problems with GCC makefiles. GNU Make 3.76 or
2522 newer is recommended to build on this platform.
2524 Errors involving @code{alloca} when building GCC generally are due
2525 to an incorrect definition of @code{CC} in the Makefile or mixing files
2526 compiled with the native C compiler and GCC@. During the stage1 phase of
2527 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
2528 (not @command{xlc}). Once @command{configure} has been informed of
2529 @command{xlc}, one needs to use @samp{make distclean} to remove the
2530 configure cache files and ensure that @env{CC} environment variable
2531 does not provide a definition that will confuse @command{configure}.
2532 If this error occurs during stage2 or later, then the problem most likely
2533 is the version of Make (see above).
2535 The GNU Assembler incorrectly reports that it supports WEAK symbols on
2536 AIX which causes GCC to try to utilize weak symbol functionality which
2537 is not really supported on the platform. The native @command{as} and
2538 @command{ld} still are recommended. The native AIX tools do
2539 interoperate with GCC@.
2541 Building @file{libstdc++.a} requires a fix for a AIX Assembler bug
2542 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1).
2544 Linking executables and shared libraries may produce warnings of
2545 duplicate symbols. The assembly files generated by GCC for AIX always
2546 have included multiple symbol definitions for certain global variable
2547 and function declarations in the original program. The warnings should
2548 not prevent the linker from producing a correct library or runnable
2551 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
2552 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
2553 to parse archive libraries did not handle the new format correctly.
2554 These routines are used by GCC and result in error messages during
2555 linking such as ``not a COFF file''. The version of the routines shipped
2556 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
2557 option of the archive command may be used to create archives of 32-bit
2558 objects using the original ``small format''. A correct version of the
2559 routines is shipped with AIX 4.3.2 and above.
2561 Some versions of the AIX binder (linker) can fail with a relocation
2562 overflow severe error when the @option{-bbigtoc} option is used to link
2563 GCC-produced object files into an executable that overflows the TOC@. A fix
2564 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
2565 available from IBM Customer Support and from its
2566 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2567 website as PTF U455193.
2569 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
2570 with a segmentation fault when invoked by any version of GCC@. A fix for
2571 APAR IX87327 is available from IBM Customer Support and from its
2572 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2573 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
2575 The initial assembler shipped with AIX 4.3.0 generates incorrect object
2576 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
2577 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
2578 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2579 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
2581 AIX provides National Language Support (NLS)@. Compilers and assemblers
2582 use NLS to support locale-specific representations of various data
2583 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
2584 separating decimal fractions). There have been problems reported where
2585 GCC does not produce the same floating-point formats that the assembler
2586 expects. If one encounters this problem, set the @env{LANG}
2587 environment variable to @samp{C} or @samp{En_US}.
2589 By default, GCC for AIX 4.1 and above produces code that can be used on
2590 both Power or PowerPC processors.
2592 A default can be specified with the @option{-mcpu=@var{cpu_type}}
2593 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
2599 @heading @anchor{m32r-*-elf}m32r-*-elf
2600 Mitsubishi M32R processor.
2601 This configuration is intended for embedded systems.
2607 @heading @anchor{m68000-hp-bsd}m68000-hp-bsd
2608 HP 9000 series 200 running BSD@. Note that the C compiler that comes
2609 with this system cannot compile GCC; contact @email{law@@cygnus.com}
2610 to get binaries of GCC for bootstrapping.
2616 @heading @anchor{m6811-elf}m6811-elf
2617 Motorola 68HC11 family micro controllers. These are used in embedded
2618 applications. There are no standard Unix configurations.
2624 @heading @anchor{m6812-elf}m6812-elf
2625 Motorola 68HC12 family micro controllers. These are used in embedded
2626 applications. There are no standard Unix configurations.
2632 @heading @anchor{m68k-altos}m68k-altos
2633 Altos 3068. You must use the GNU assembler, linker and debugger.
2634 Also, you must fix a kernel bug.
2640 @heading @anchor{m68k-apple-aux}m68k-apple-aux
2641 Apple Macintosh running A/UX@.
2642 You may configure GCC to use either the system assembler and
2643 linker or the GNU assembler and linker. You should use the GNU configuration
2644 if you can, especially if you also want to use G++. You enable
2645 that configuration with the @option{--with-gnu-as} and @option{--with-gnu-ld}
2646 options to @code{configure}.
2648 Note the C compiler that comes
2649 with this system cannot compile GCC@. You can find binaries of GCC
2650 for bootstrapping on @code{jagubox.gsfc.nasa.gov}.
2651 You will also a patched version of @file{/bin/ld} there that
2652 raises some of the arbitrary limits found in the original.
2658 @heading @anchor{m68k-att-sysv}m68k-att-sysv
2659 AT&T 3b1, a.k.a.@: 7300 PC@. This version of GCC cannot
2660 be compiled with the system C compiler, which is too buggy.
2661 You will need to get a previous version of GCC and use it to
2662 bootstrap. Binaries are available from the OSU-CIS archive, at
2663 @uref{ftp://archive.cis.ohio-state.edu/pub/att7300/}.
2669 @heading @anchor{m68k-bull-sysv}m68k-bull-sysv
2670 Bull DPX/2 series 200 and 300 with BOS-2.00.45 up to BOS-2.01. GCC works
2671 either with native assembler or GNU assembler. You can use
2672 GNU assembler with native COFF generation by providing @option{--with-gnu-as} to
2673 the configure script or use GNU assembler with stabs-in-COFF encapsulation
2674 by providing @samp{--with-gnu-as --stabs}. For any problem with the native
2675 assembler or for availability of the DPX/2 port of GAS, contact
2676 @email{F.Pierresteguy@@frcl.bull.fr}.
2682 @heading @anchor{m68k-crds-unox}m68k-crds-unox
2683 Use @samp{configure unos} for building on Unos.
2685 The Unos assembler is named @code{casm} instead of @code{as}. For some
2686 strange reason linking @file{/bin/as} to @file{/bin/casm} changes the
2687 behavior, and does not work. So, when installing GCC, you should
2688 install the following script as @file{as} in the subdirectory where
2689 the passes of GCC are installed:
2696 The default Unos library is named @file{libunos.a} instead of
2697 @file{libc.a}. To allow GCC to function, either change all
2698 references to @option{-lc} in @file{gcc.c} to @option{-lunos} or link
2699 @file{/lib/libc.a} to @file{/lib/libunos.a}.
2701 @cindex @code{alloca}, for Unos
2702 When compiling GCC with the standard compiler, to overcome bugs in
2703 the support of @code{alloca}, do not use @option{-O} when making stage 2.
2704 Then use the stage 2 compiler with @option{-O} to make the stage 3
2705 compiler. This compiler will have the same characteristics as the usual
2706 stage 2 compiler on other systems. Use it to make a stage 4 compiler
2707 and compare that with stage 3 to verify proper compilation.
2709 (Perhaps simply defining @code{ALLOCA} in @file{x-crds} as described in
2710 the comments there will make the above paragraph superfluous. Please
2711 inform us of whether this works.)
2713 Unos uses memory segmentation instead of demand paging, so you will need
2714 a lot of memory. 5 Mb is barely enough if no other tasks are running.
2715 If linking @file{cc1} fails, try putting the object files into a library
2716 and linking from that library.
2722 @heading @anchor{m68k-hp-hpux}m68k-hp-hpux
2723 HP 9000 series 300 or 400 running HP-UX@. HP-UX version 8.0 has a bug in
2724 the assembler that prevents compilation of GCC@. This
2725 bug manifests itself during the first stage of compilation, while
2726 building @file{libgcc2.a}:
2730 cc1: warning: `-g' option not supported on this version of GCC
2731 cc1: warning: `-g1' option not supported on this version of GCC
2732 ./xgcc: Internal compiler error: program as got fatal signal 11
2735 A patched version of the assembler is available as the file
2736 @uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you
2737 have HP software support, the patch can also be obtained directly from
2738 HP, as described in the following note:
2741 This is the patched assembler, to patch SR#1653-010439, where the
2742 assembler aborts on floating point constants.
2744 The bug is not really in the assembler, but in the shared library
2745 version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is
2746 SR#4701-078451. Anyway, the attached assembler uses the archive
2747 library version of ``cvtnum(3c)'' and thus does not exhibit the bug.
2750 This patch is also known as PHCO_4484.
2752 In addition, if you wish to use gas, you must use
2753 gas version 2.1 or later, and you must use the GNU linker version 2.1 or
2754 later. Earlier versions of gas relied upon a program which converted the
2755 gas output into the native HP-UX format, but that program has not been
2756 kept up to date. gdb does not understand that native HP-UX format, so
2757 you must use gas if you wish to use gdb.
2759 On HP-UX version 8.05, but not on 8.07 or more recent versions, the
2760 @code{fixproto} shell script triggers a bug in the system shell. If you
2761 encounter this problem, upgrade your operating system or use BASH (the
2762 GNU shell) to run @code{fixproto}. This bug will cause the fixproto
2763 program to report an error of the form:
2766 ./fixproto: sh internal 1K buffer overflow
2769 To fix this, you can also change the first line of the fixproto script
2781 @heading @anchor{m68k-*-nextstep*}m68k-*-nextstep*
2783 Current GCC versions probably do not work on version 2 of the NeXT
2786 On NeXTStep 3.0, the Objective-C compiler does not work, due,
2787 apparently, to a kernel bug that it happens to trigger. This problem
2788 does not happen on 3.1.
2790 You absolutely @strong{must} use GNU sed and GNU make on this platform.
2793 On NeXTSTEP 3.x where x < 3 the build of GCC will abort during
2794 stage1 with an error message like this:
2798 /usr/tmp/ccbbsZ0U.s:987:Unknown pseudo-op: .section
2799 /usr/tmp/ccbbsZ0U.s:987:Rest of line ignored. 1st junk character
2803 The reason for this is the fact that NeXT's assembler for these
2804 versions of the operating system does not support the @samp{.section}
2805 pseudo op that's needed for full C++ exception functionality.
2807 As NeXT's assembler is a derived work from GNU as, a free
2808 replacement that does can be obtained at
2809 @uref{ftp://ftp.next.peak.org:/next-ftp/next/apps/devtools/as.3.3.NIHS.s.tar.gz,,ftp://ftp.next.peak.org:/next-ftp/next/apps/devtools/as.3.3.NIHS.s.tar.gz}.
2811 If you try to build the integrated C++ & C++ runtime libraries on this system
2812 you will run into trouble with include files. The way to get around this is
2813 to use the following sequence. Note you must have write permission to
2814 the directory @var{prefix} you specified in the configuration process of GCC
2815 for this sequence to work.
2819 make all-texinfo all-bison all-byacc all-binutils all-gas all-ld
2822 make install-headers-tar
2831 @heading @anchor{m68k-ncr-*}m68k-ncr-*
2832 On the Tower models 4@var{n}0 and 6@var{n}0, by default a process is not
2833 allowed to have more than one megabyte of memory. GCC cannot compile
2834 itself (or many other programs) with @option{-O} in that much memory.
2836 To solve this problem, reconfigure the kernel adding the following line
2837 to the configuration file:
2848 @heading @anchor{m68k-sun}m68k-sun
2849 Sun 3. We do not provide a configuration file to use the Sun FPA by
2850 default, because programs that establish signal handlers for floating
2851 point traps inherently cannot work with the FPA@.
2857 @heading @anchor{m68k-sun-sunos4.1.1}m68k-sun-sunos4.1.1
2859 It is reported that you may need the GNU assembler on this platform.
2866 @heading @anchor{m88k-*-svr3}m88k-*-svr3
2867 Motorola m88k running the AT&T/Unisoft/Motorola V.3 reference port.
2868 These systems tend to use the Green Hills C, revision 1.8.5, as the
2869 standard C compiler. There are apparently bugs in this compiler that
2870 result in object files differences between stage 2 and stage 3. If this
2871 happens, make the stage 4 compiler and compare it to the stage 3
2872 compiler. If the stage 3 and stage 4 object files are identical, this
2873 suggests you encountered a problem with the standard C compiler; the
2874 stage 3 and 4 compilers may be usable.
2876 It is best, however, to use an older version of GCC for bootstrapping
2883 @heading @anchor{m88k-*-dgux}m88k-*-dgux
2884 Motorola m88k running DG/UX@. To build 88open BCS native or cross
2885 compilers on DG/UX, specify the configuration name as
2886 @samp{m88k-*-dguxbcs} and build in the 88open BCS software development
2887 environment. To build ELF native or cross compilers on DG/UX, specify
2888 @samp{m88k-*-dgux} and build in the DG/UX ELF development environment.
2889 You set the software development environment by issuing
2890 @samp{sde-target} command and specifying either @samp{m88kbcs} or
2891 @samp{m88kdguxelf} as the operand.
2893 If you do not specify a configuration name, @file{configure} guesses the
2894 configuration based on the current software development environment.
2900 @heading @anchor{m88k-tektronix-sysv3}m88k-tektronix-sysv3
2901 Tektronix XD88 running UTekV 3.2e. Do not turn on
2902 optimization while building stage1 if you bootstrap with
2903 the buggy Green Hills compiler. Also, the bundled LAI
2904 System V NFS is buggy so if you build in an NFS mounted
2905 directory, start from a fresh reboot, or avoid NFS all together.
2906 Otherwise you may have trouble getting clean comparisons
2913 @heading @anchor{mips-*-*}mips-*-*
2914 If you use the 1.31 version of the MIPS assembler (such as was shipped
2915 with Ultrix 3.1), you will need to use the @option{-fno-delayed-branch} switch
2916 when optimizing floating point code. Otherwise, the assembler will
2917 complain when the GCC compiler fills a branch delay slot with a
2918 floating point instruction, such as @code{add.d}.
2920 If on a MIPS system you get an error message saying ``does not have gp
2921 sections for all it's [sic] sectons [sic]'', don't worry about it. This
2922 happens whenever you use GAS with the MIPS linker, but there is not
2923 really anything wrong, and it is okay to use the output file. You can
2924 stop such warnings by installing the GNU linker.
2926 It would be nice to extend GAS to produce the gp tables, but they are
2927 optional, and there should not be a warning about their absence.
2929 Users have reported some problems with version 2.0 of the MIPS
2930 compiler tools that were shipped with Ultrix 4.1. Version 2.10
2931 which came with Ultrix 4.2 seems to work fine.
2933 Users have also reported some problems with version 2.20 of the
2934 MIPS compiler tools that were shipped with RISC/os 4.x. The earlier
2935 version 2.11 seems to work fine.
2937 Some versions of the MIPS linker will issue an assertion failure
2938 when linking code that uses @code{alloca} against shared
2939 libraries on RISC-OS 5.0, and DEC's OSF/1 systems. This is a bug
2940 in the linker, that is supposed to be fixed in future revisions.
2941 To protect against this, GCC passes @option{-non_shared} to the
2942 linker unless you pass an explicit @option{-shared} or
2943 @option{-call_shared} switch.
2945 @heading @anchor{mips-mips-bsd}mips-mips-bsd
2946 MIPS machines running the MIPS operating system in BSD mode. It's
2947 possible that some old versions of the system lack the functions
2948 @code{memcpy}, @code{memmove}, @code{memcmp}, and @code{memset}. If your
2949 system lacks these, you must remove or undo the definition of
2950 @code{TARGET_MEM_FUNCTIONS} in @file{mips-bsd.h}.
2952 If you use the MIPS C compiler to bootstrap, it may be necessary
2953 to increase its table size for switch statements with the
2954 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
2955 optimization option, you also need to use @option{-Olimit 3000}.
2956 Both of these options are automatically generated in the
2957 @file{Makefile} that the shell script @file{configure} builds.
2958 If you override the @code{CC} make variable and use the MIPS
2959 compilers, you may need to add @option{-Wf,-XNg1500 -Olimit 3000}.
2965 @heading @anchor{mips-dec-*}mips-dec-*
2966 MIPS-based DECstations can support three different personalities:
2967 Ultrix, DEC OSF/1, and OSF/rose. (Alpha-based DECstation products have
2968 a configuration name beginning with @samp{alpha*-dec}.) To configure GCC
2969 for these platforms use the following configurations:
2972 @item mips-dec-ultrix
2973 Ultrix configuration.
2976 DEC's version of OSF/1.
2978 @item mips-dec-osfrose
2979 Open Software Foundation reference port of OSF/1 which uses the
2980 OSF/rose object file format instead of ECOFF@. Normally, you
2981 would not select this configuration.
2984 If you use the MIPS C compiler to bootstrap, it may be necessary
2985 to increase its table size for switch statements with the
2986 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
2987 optimization option, you also need to use @option{-Olimit 3000}.
2988 Both of these options are automatically generated in the
2989 @file{Makefile} that the shell script @file{configure} builds.
2990 If you override the @code{CC} make variable and use the MIPS
2991 compilers, you may need to add @option{-Wf,-XNg1500 -Olimit 3000}.
2997 @heading @anchor{mips-mips-riscos*}mips-mips-riscos*
2998 If you use the MIPS C compiler to bootstrap, it may be necessary
2999 to increase its table size for switch statements with the
3000 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
3001 optimization option, you also need to use @option{-Olimit 3000}.
3002 Both of these options are automatically generated in the
3003 @file{Makefile} that the shell script @file{configure} builds.
3004 If you override the @code{CC} make variable and use the MIPS
3005 compilers, you may need to add @samp{-Wf,-XNg1500 -Olimit 3000}.
3007 MIPS computers running RISC-OS can support four different
3008 personalities: default, BSD 4.3, System V.3, and System V.4
3009 (older versions of RISC-OS don't support V.4). To configure GCC
3010 for these platforms use the following configurations:
3013 @item mips-mips-riscos@var{rev}
3014 Default configuration for RISC-OS, revision @var{rev}.
3016 @item mips-mips-riscos@var{rev}bsd
3017 BSD 4.3 configuration for RISC-OS, revision @var{rev}.
3019 @item mips-mips-riscos@var{rev}sysv4
3020 System V.4 configuration for RISC-OS, revision @var{rev}.
3026 @item mips-mips-riscos@var{rev}sysv
3027 System V.3 configuration for RISC-OS, revision @var{rev}.
3030 The revision @code{rev} mentioned above is the revision of
3031 RISC-OS to use. You must reconfigure GCC when going from a
3032 RISC-OS revision 4 to RISC-OS revision 5. This has the effect of
3033 avoiding a linker bug.
3039 @heading @anchor{mips-sgi-irix4}mips-sgi-irix4
3041 In order to compile GCC on an SGI running IRIX 4, the ``c.hdr.lib''
3042 option must be installed from the CD-ROM supplied from Silicon Graphics.
3043 This is found on the 2nd CD in release 4.0.1.
3045 On IRIX version 4.0.5F, and perhaps on some other versions as well,
3046 there is an assembler bug that reorders instructions incorrectly. To
3047 work around it, specify the target configuration
3048 @samp{mips-sgi-irix4loser}. This configuration inhibits assembler
3051 In a compiler configured with target @samp{mips-sgi-irix4}, you can turn
3052 off assembler optimization by using the @option{-noasmopt} option. This
3053 compiler option passes the option @option{-O0} to the assembler, to
3056 The @option{-noasmopt} option can be useful for testing whether a problem
3057 is due to erroneous assembler reordering. Even if a problem does not go
3058 away with @option{-noasmopt}, it may still be due to assembler
3059 reordering---perhaps GCC itself was miscompiled as a result.
3061 You may get the following warning on IRIX 4 platforms, it can be safely
3064 warning: foo.o does not have gp tables for all its sections.
3071 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
3073 This configuration has considerable problems, which will be fixed in a
3076 In order to compile GCC on an SGI running IRIX 5, the ``compiler_dev.hdr''
3077 subsystem must be installed from the IDO CD-ROM supplied by Silicon
3078 Graphics. It is also available for download from
3079 @uref{http://www.sgi.com/developers/devtools/apis/ido.html,,http://www.sgi.com/developers/devtools/apis/ido.html}.
3081 @code{make compare} may fail on version 5 of IRIX unless you add
3082 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
3083 assembler input file is stored in the object file, and that makes
3084 comparison fail if it differs between the @code{stage1} and
3085 @code{stage2} compilations. The option @option{-save-temps} forces a
3086 fixed name to be used for the assembler input file, instead of a
3087 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
3088 unless the comparisons fail without that option. If you do you
3089 @option{-save-temps}, you will have to manually delete the @samp{.i} and
3090 @samp{.s} files after each series of compilations.
3092 If you use the MIPS C compiler to bootstrap, it may be necessary
3093 to increase its table size for switch statements with the
3094 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
3095 optimization option, you also need to use @option{-Olimit 3000}.
3097 To enable debugging under IRIX 5, you must use GNU @command{as} 2.11.2
3099 and use the @option{--with-gnu-as} configure option when configuring GCC.
3100 GNU @command{as} is distributed as part of the binutils package.
3101 When using release 2.11.2, you need to apply a patch
3102 @uref{http://sources.redhat.com/ml/binutils/2001-07/msg00352.html,,http://sources.redhat.com/ml/binutils/2001-07/msg00352.html}
3103 which will be included in the next release of binutils.
3105 When building GCC, the build process loops rebuilding @command{cc1} over
3106 and over again. This happens on @samp{mips-sgi-irix5.2}, and possibly
3107 other platforms. It has been reported that this is a known bug in the
3108 @command{make} shipped with IRIX 5.2. We recommend you use GNU
3109 @command{make} instead of the vendor supplied @command{make} program;
3110 however, you may have success with @command{smake} on IRIX 5.2 if you do
3111 not have GNU @command{make} available.
3117 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
3119 If you are using IRIX @command{cc} as your bootstrap compiler, you must
3120 ensure that the N32 ABI is in use. To test this, compile a simple C
3121 file with @command{cc} and then run @command{file} on the
3122 resulting object file. The output should look like:
3125 test.o: ELF N32 MSB @dots{}
3131 test.o: ELF 32-bit MSB @dots{}
3137 test.o: ELF 64-bit MSB @dots{}
3140 then your version of @command{cc} uses the O32 or N64 ABI by default. You
3141 should set the environment variable @env{CC} to @samp{cc -n32}
3142 before configuring GCC@.
3144 GCC on IRIX 6 is usually built to support both the N32 and N64 ABIs. If
3145 you build GCC on a system that doesn't have the N64 libraries installed,
3146 you need to configure with @option{--disable-multilib} so GCC doesn't
3147 try to use them. Look for @file{/usr/lib64/libc.so.1} to see if you
3148 have the 64-bit libraries installed.
3150 You must @emph{not} use GNU @command{as} (which isn't built anyway as of
3151 binutils 2.11.2) on IRIX 6 platforms; doing so will only cause problems.
3153 GCC does not currently support generating O32 ABI binaries in the
3154 @samp{mips-sgi-irix6} configurations. It is possible to create a GCC
3155 with O32 ABI only support by configuring it for the @samp{mips-sgi-irix5}
3156 target and using a patched GNU @command{as} 2.11.2 as documented in the
3157 @uref{#mips-sgi-irix5,,@samp{mips-sgi-irix5}} section above. Using the
3158 native assembler requires patches to GCC which will be included in a
3159 future release. It is
3160 expected that O32 ABI support will be available again in a future release.
3162 The @option{--enable-threads} option doesn't currently work, a patch is
3163 in preparation for a future release. The @option{--enable-libgcj}
3164 option is disabled by default: IRIX 6 uses a very low default limit
3165 (20480) for the command line length. Although libtool contains a
3166 workaround for this problem, at least the N64 @samp{libgcj} is known not
3167 to build despite this, running into an internal error of the native
3168 @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
3169 its maximum of 262144 bytes. If you have root access, you can use the
3170 @command{systune} command to do this.
3172 GCC does not correctly pass/return structures which are
3173 smaller than 16 bytes and which are not 8 bytes. The problem is very
3174 involved and difficult to fix. It affects a number of other targets also,
3175 but IRIX 6 is affected the most, because it is a 64 bit target, and 4 byte
3176 structures are common. The exact problem is that structures are being padded
3177 at the wrong end, e.g.@: a 4 byte structure is loaded into the lower 4 bytes
3178 of the register when it should be loaded into the upper 4 bytes of the
3181 GCC is consistent with itself, but not consistent with the SGI C compiler
3182 (and the SGI supplied runtime libraries), so the only failures that can
3183 happen are when there are library functions that take/return such
3184 structures. There are very few such library functions. Currently this
3185 is known to affect @code{inet_ntoa}, @code{inet_lnaof},
3186 @code{inet_netof}, @code{inet_makeaddr}, and @code{semctl}. Until the
3187 bug is fixed, GCC contains workarounds for the known affected functions.
3189 See @uref{http://freeware.sgi.com/,,http://freeware.sgi.com/} for more
3190 information about using GCC on IRIX platforms.
3196 @heading @anchor{mips-sony-sysv}mips-sony-sysv
3197 Sony MIPS NEWS@. This works in NEWSOS 5.0.1, but not in 5.0.2 (which
3198 uses ELF instead of COFF)@. Support for 5.0.2 will probably be provided
3199 soon by volunteers. In particular, the linker does not like the
3200 code generated by GCC when shared libraries are linked in.
3207 @heading @anchor{ns32k-encore}ns32k-encore
3208 Encore ns32000 system. Encore systems are supported only under BSD@.
3214 @heading @anchor{ns32k-*-genix}ns32k-*-genix
3215 National Semiconductor ns32000 system. Genix has bugs in @code{alloca}
3216 and @code{malloc}; you must get the compiled versions of these from GNU
3223 @heading @anchor{ns32k-sequent}ns32k-sequent
3224 Go to the Berkeley universe before compiling.
3230 @heading @anchor{ns32k-utek}ns32k-utek
3231 UTEK ns32000 system (``merlin''). The C compiler that comes with this
3232 system cannot compile GCC; contact @samp{tektronix!reed!mason} to get
3233 binaries of GCC for bootstrapping.
3240 @heading @anchor{powerpc*-*-*}powerpc-*-*
3242 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
3243 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
3249 @heading @anchor{powerpc-*-darwin*}powerpc-*-darwin*
3250 PowerPC running Darwin (Mac OS X kernel).
3252 GCC 3.0 does not support Darwin, but 3.1 and later releases will work.
3254 Pre-installed versions of Mac OS X may not include any developer tools,
3255 meaning that you will not be able to build GCC from source. Tool
3256 binaries are available at
3257 @uref{http://www.opensource.apple.com/projects/darwin} (free
3258 registration required).
3260 Versions of the assembler prior to ``cctools-364'' cannot handle the
3261 4-argument form of rlwinm and related mask-using instructions. Darwin
3262 1.3 (Mac OS X 10.0) uses cctools-353 for instance. To get cctools-364,
3263 check out @file{cctools} with tag @samp{Apple-364}, build it, and
3264 install the assembler as @file{usr/bin/as}. See
3265 @uref{http://www.opensource.apple.com/tools/cvs/docs.html} for details.
3267 Also, the default stack limit of 512K is too small, and a bootstrap will
3268 typically fail when self-compiling @file{expr.c}. Set the stack to 800K
3269 or more, for instance by doing @samp{limit stack 800}. It's also
3270 convenient to use the GNU preprocessor instead of Apple's during the
3271 first stage of bootstrapping; this is automatic when doing @samp{make
3272 bootstrap}, but to do it from the toplevel objdir you will need to say
3273 @samp{make CC='cc -no-cpp-precomp' bootstrap}.
3275 Note that the version of GCC shipped by Apple typically includes a
3276 number of extensions not available in a standard GCC release. These
3277 extensions are generally specific to Mac programming.
3283 @heading @anchor{powerpc-*-elf}powerpc-*-elf, powerpc-*-sysv4
3284 PowerPC system in big endian mode, running System V.4.
3290 @heading @anchor{powerpc-*-linux-gnu*}powerpc-*-linux-gnu*
3293 @uref{ftp://ftp.varesearch.com/pub/support/hjl/binutils,,binutils 2.9.4.0.8}
3294 or newer for a working GCC@. It is strongly recommended to recompile binutils
3295 if you initially built it with gcc-2.7.2.x.
3301 @heading @anchor{powerpc-*-netbsd*}powerpc-*-netbsd*
3302 PowerPC system in big endian mode running NetBSD@. To build the
3303 documentation you will need Texinfo version 4.0 (NetBSD 1.5.1 included
3304 Texinfo version 3.12).
3310 @heading @anchor{powerpc-*-eabiaix}powerpc-*-eabiaix
3311 Embedded PowerPC system in big endian mode with @option{-mcall-aix} selected as
3318 @heading @anchor{powerpc-*-eabisim}powerpc-*-eabisim
3319 Embedded PowerPC system in big endian mode for use in running under the
3326 @heading @anchor{powerpc-*-eabi}powerpc-*-eabi
3327 Embedded PowerPC system in big endian mode.
3333 @heading @anchor{powerpcle-*-elf}powerpcle-*-elf, powerpcle-*-sysv4
3334 PowerPC system in little endian mode, running System V.4.
3340 @heading @anchor{powerpcle-*-eabisim}powerpcle-*-eabisim
3341 Embedded PowerPC system in little endian mode for use in running under
3348 @heading @anchor{powerpcle-*-eabi}powerpcle-*-eabi
3349 Embedded PowerPC system in little endian mode.
3355 @heading @anchor{powerpcle-*-winnt}powerpcle-*-winnt, powerpcle-*-pe
3356 PowerPC system in little endian mode running Windows NT@.
3362 @heading @anchor{romp-*-aos}romp-*-aos, romp-*-mach
3363 The only operating systems supported for the IBM RT PC are AOS and
3364 MACH@. GCC does not support AIX running on the RT@. We recommend you
3365 compile GCC with an earlier version of itself; if you compile GCC
3366 with @command{hc}, the Metaware compiler, it will work, but you will get
3367 mismatches between the stage 2 and stage 3 compilers in various files.
3368 These errors are minor differences in some floating-point constants and
3369 can be safely ignored; the stage 3 compiler is correct.
3375 @heading @anchor{s390-*-linux*}s390-*-linux*
3376 S/390 system running Linux for S/390@.
3382 @heading @anchor{s390x-*-linux*}s390x-*-linux*
3383 zSeries system (64 Bit) running Linux for zSeries@.
3389 @c Please use Solaris 2 to refer to all release of Solaris, starting
3390 @c with 2.0 until 2.6, 7, and 8. Solaris 1 was a marketing name for
3391 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
3392 @c alone is too unspecific and must be avoided.
3393 @heading @anchor{*-*-solaris2*}*-*-solaris2*
3395 Sun does not ship a C compiler with Solaris 2. To bootstrap and install
3396 GCC you first have to install a pre-built compiler, see our
3397 @uref{binaries.html,,binaries page} for details.
3399 The Solaris 2 @command{/bin/sh} will often fail to configure
3400 @file{libstdc++-v3}, @file{boehm-gc} or
3401 @file{libjava}. If you encounter this problem, set @env{CONFIG_SHELL} to
3402 @command{/bin/ksh} in your environment and run @command{make bootstrap} again.
3403 Another possibility that sometimes helps is to remove
3404 @file{*-*-solaris2*/config.cache}.
3406 Solaris 2 comes with a number of optional OS packages. Some of these
3407 packages are needed to use GCC fully, namely @code{SUNWarc},
3408 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
3409 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
3410 optional packages when installing Solaris 2, you will need to verify that
3411 the packages that GCC needs are installed.
3413 To check whether an optional package is installed, use
3414 the @command{pkginfo} command. To add an optional package, use the
3415 @command{pkgadd} command. For further details, see the Solaris 2
3418 Trying to use the linker and other tools in
3419 @file{/usr/ucb} to install GCC has been observed to cause trouble.
3420 For example, the linker may hang indefinitely. The fix is to remove
3421 @file{/usr/ucb} from your @env{PATH}.
3423 All releases of GNU binutils prior to 2.11.2 have known bugs on this
3424 platform. We recommend the use of GNU binutils 2.11.2 or the vendor
3425 tools (Sun @command{as}, Sun @command{ld}).
3427 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3428 newer: @command{g++} will complain that types are missing. These headers assume
3429 that omitting the type means @code{int}; this assumption worked for C89 but
3430 is wrong for C++, and is now wrong for C99 also.
3432 @command{g++} accepts such (invalid) constructs with the option
3433 @option{-fpermissive}; it
3434 will assume that any missing type is @code{int} (as defined by C89).
3436 There are patches for Solaris 2.6 (105633-56 or newer for SPARC,
3437 106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC,
3438 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
3439 108653-22 for Intel) that fix this bug.
3445 @heading @anchor{sparc-sun-solaris2*}sparc-sun-solaris2*
3447 Sun @command{as} 4.x is broken in that it cannot cope with long symbol names.
3448 A typical error message might look similar to the following:
3450 @samp{/usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041:
3451 error: can't compute value of an expression involving an external symbol.}
3453 This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris
3454 2.6 and has been fixed in later (5.x) versions of the assembler,
3455 starting with Solaris 7.
3457 Starting with Solaris 7, the operating system is capable of executing
3458 64-bit SPARC V9 binaries. GCC 3.1 and later should properly support
3459 this. GCC 3.0 lacks the infrastructure necessary to support this
3460 configuration properly. However, if all you want is code tuned for
3461 the UltraSPARC CPU, you should try the @option{-mtune=ultrasparc}
3462 option instead, which should be safe from those bugs and produce code
3463 that, unlike full 64-bit code, can still run on non-UltraSPARC
3466 The target tuple @code{sparc-sun-solaris} will be used for
3467 configurations in which only 32-bit SPARC binaries may be executed;
3468 @code{sparcv9-sun-solaris} will be used when either 32-bit or 64-bit
3469 binaries may be executed, but the compiler will produce 32-bit
3470 binaries unless the @option{-m64} switch is used; @code{sparc64-sun-solaris}
3471 should be used when the compiler should produce 64-bit binaries
3474 Unless otherwise specified, @command{configure} will select either
3475 @code{sparc} or @code{sparcv9} based on the output of @command{isalist}.
3476 It will never select @code{sparc64} by default.
3482 @heading @anchor{sparc-sun-solaris2.7}sparc-sun-solaris2.7
3484 Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
3485 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
3486 and later, including all EGCS releases. Sun formerly recommended
3487 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
3488 recommend it only for people who use Sun's compilers.
3490 Here are some workarounds to this problem:
3493 Do not install Sun patch 107058-01 until after Sun releases a
3494 complete patch for bug 4210064. This is the simplest course to take,
3495 unless you must also use Sun's C compiler. Unfortunately 107058-01
3496 is preinstalled on some new Solaris 7-based hosts, so you may have to
3500 Copy the original, unpatched Solaris 7
3501 @command{/usr/ccs/bin/as} into
3502 @command{/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/3.0/as},
3503 adjusting the latter name to fit your local conventions and software
3507 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
3508 both 107058-01 and 106950-03 installed has reported the bug with GCC
3509 and Sun's dynamic linker. This last course of action is riskiest,
3510 for two reasons. First, you must install 106950 on all hosts that
3511 run code generated by GCC; it doesn't suffice to install it only on
3512 the hosts that run GCC itself. Second, Sun says that 106950-03 is
3513 only a partial fix for bug 4210064, but Sun doesn't know whether the
3514 partial fix is adequate for GCC@. Revision -08 or later should fix
3515 the bug. The current (as of 2001-09-24) revision is -14, and is included in
3516 the Solaris 7 Recommended Patch Cluster.
3524 @heading @anchor{*-*-solaris2.8}*-*-solaris2.8
3526 The Solaris 8 linker fails to link some @samp{libjava} programs if
3527 previously-installed GCC java libraries already exist in the configured
3528 prefix. For this reason, @samp{libgcj} is disabled by default on Solaris 8.
3529 If you use GNU @command{ld}, or if you don't have a previously-installed @samp{libgcj} in
3530 the same prefix, use @option{--enable-libgcj} to build and install the
3537 @heading @anchor{sparc-sun-sunos4*}sparc-sun-sunos4*
3539 A bug in the SunOS 4 linker will cause it to crash when linking
3540 @option{-fPIC} compiled objects (and will therefore not allow you to build
3543 To fix this problem you can either use the most recent version of
3544 binutils or get the latest SunOS 4 linker patch (patch ID 100170-10)
3545 from Sun's patch site.
3547 Sometimes on a Sun 4 you may observe a crash in the program
3548 @command{genflags} or @command{genoutput} while building GCC. This is said to
3549 be due to a bug in @command{sh}. You can probably get around it by running
3550 @command{genflags} or @command{genoutput} manually and then retrying the
3557 @heading @anchor{sparc-unknown-linux-gnulibc1}sparc-unknown-linux-gnulibc1
3559 It has been reported that you might need
3560 @uref{ftp://ftp.yggdrasil.com/private/hjl,,binutils 2.8.1.0.23}
3561 for this platform, too.
3568 @heading @anchor{sparc-*-linux*}sparc-*-linux*
3570 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
3571 or newer on this platform. All earlier binutils and glibc
3572 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
3579 @heading @anchor{sparc64-*-*}sparc64-*-*
3581 GCC version 2.95 is not able to compile code correctly for
3582 @code{sparc64} targets. Users of the Linux kernel, at least,
3583 can use the @code{sparc32} program to start up a new shell
3584 invocation with an environment that causes @command{configure} to
3585 recognize (via @samp{uname -a}) the system as @samp{sparc-*-*} instead.
3591 @heading @anchor{sparcv9-*-solaris2*}sparcv9-*-solaris2*
3593 The following compiler flags must be specified in the configure
3594 step in order to bootstrap this target with the Sun compiler:
3597 % CC="cc -xildoff -xarch=v9" @var{srcdir}/configure [@var{options}] [@var{target}]
3600 @option{-xildoff} turns off the incremental linker, and @option{-xarch=v9}
3601 specifies the v9 architecture to the Sun linker and assembler.
3607 @heading @anchor{#*-*-sysv*}*-*-sysv*
3608 On System V release 3, you may get this error message
3612 ld fatal: failed to write symbol name @var{something}
3613 in strings table for file @var{whatever}
3616 This probably indicates that the disk is full or your ulimit won't allow
3617 the file to be as large as it needs to be.
3619 This problem can also result because the kernel parameter @code{MAXUMEM}
3620 is too small. If so, you must regenerate the kernel and make the value
3621 much larger. The default value is reported to be 1024; a value of 32768
3622 is said to work. Smaller values may also work.
3624 On System V, if you get an error like this,
3627 /usr/local/lib/bison.simple: In function `yyparse':
3628 /usr/local/lib/bison.simple:625: virtual memory exhausted
3632 that too indicates a problem with disk space, ulimit, or @code{MAXUMEM}.
3634 On a System V release 4 system, make sure @file{/usr/bin} precedes
3635 @file{/usr/ucb} in @code{PATH}. The @code{cc} command in
3636 @file{/usr/ucb} uses libraries which have bugs.
3642 @heading @anchor{vax-dec-ultrix}vax-dec-ultrix
3643 Don't try compiling with VAX C (@code{vcc}). It produces incorrect code
3644 in some cases (for example, when @code{alloca} is used).
3650 @heading @anchor{we32k-*-*}we32k-*-*
3651 These computers are also known as the 3b2, 3b5, 3b20 and other similar
3652 names. (However, the 3b1 is actually a 68000.)
3654 Don't use @option{-g} when compiling with the system's compiler. The
3655 system's linker seems to be unable to handle such a large program with
3656 debugging information.
3658 The system's compiler runs out of capacity when compiling @file{stmt.c}
3659 in GCC@. You can work around this by building @file{cpp} in GCC
3660 first, then use that instead of the system's preprocessor with the
3661 system's C compiler to compile @file{stmt.c}. Here is how:
3664 mv /lib/cpp /lib/cpp.att
3666 echo '/lib/cpp.gnu -traditional $@{1+"$@@"@}' > /lib/cpp
3670 The system's compiler produces bad code for some of the GCC
3671 optimization files. So you must build the stage 2 compiler without
3672 optimization. Then build a stage 3 compiler with optimization.
3673 That executable should work. Here are the necessary commands:
3676 make LANGUAGES=c CC=stage1/xgcc CFLAGS="-Bstage1/ -g"
3678 make CC=stage2/xgcc CFLAGS="-Bstage2/ -g -O"
3681 You may need to raise the ULIMIT setting to build a C++ compiler,
3682 as the file @file{cc1plus} is larger than one megabyte.
3688 @heading @anchor{xtensa-*-elf}xtensa-*-elf
3690 This target is intended for embedded Xtensa systems using the
3691 @samp{newlib} C library. It uses ELF but does not support shared
3692 objects. Designed-defined instructions specified via the
3693 Tensilica Instruction Extension (TIE) language are only supported
3694 through inline assembly.
3696 The Xtensa configuration information must be specified prior to
3697 building GCC@. The @file{gcc/config/xtensa/xtensa-config.h} header
3698 file contains the configuration information. If you created your
3699 own Xtensa configuration with the Xtensa Processor Generator, the
3700 downloaded files include a customized copy of this header file,
3701 which you can use to replace the default header file.
3707 @heading @anchor{xtensa-*-linux*}xtensa-*-linux*
3709 This target is for Xtensa systems running GNU/Linux. It supports ELF
3710 shared objects and the GNU C library (glibc). It also generates
3711 position-independent code (PIC) regardless of whether the
3712 @option{-fpic} or @option{-fPIC} options are used. In other
3713 respects, this target is the same as the
3714 @uref{#xtensa-*-elf,,@samp{xtensa-*-elf}} target.
3720 @heading @anchor{windows}Microsoft Windows (32 bit)
3722 A port of GCC 2.95.x is included with the
3723 @uref{http://www.cygwin.com/,,Cygwin environment}.
3725 Current (as of early 2001) snapshots of GCC will build under Cygwin
3726 without modification.
3732 @heading @anchor{os2}OS/2
3734 GCC does not currently support OS/2. However, Andrew Zabolotny has been
3735 working on a generic OS/2 port with pgcc. The current code can be found
3736 at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
3738 An older copy of GCC 2.8.1 is included with the EMX tools available at
3739 @uref{ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/,,
3740 ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/}.
3746 @heading @anchor{older}Older systems
3748 GCC contains support files for many older (1980s and early
3749 1990s) Unix variants. For the most part, support for these systems
3750 has not been deliberately removed, but it has not been maintained for
3751 several years and may suffer from bitrot. Support from some systems
3752 has been removed from GCC 3: fx80, ns32-ns-genix, pyramid, tahoe,
3753 gmicro, spur; most of these targets had not been updated since GCC
3756 Support for older systems as targets for cross-compilation is less
3757 problematic than support for them as hosts for GCC; if an enthusiast
3758 wishes to make such a target work again (including resurrecting any
3759 of the targets that never worked with GCC 2, starting from the last
3760 CVS version before they were removed), patches
3761 @uref{../contribute.html,,following the usual requirements}
3762 would be likely to be accepted, since they should not affect the
3763 support for more modern targets.
3765 Support for old systems as hosts for GCC can cause problems if the
3766 workarounds for compiler, library and operating system bugs affect the
3767 cleanliness or maintainability of the rest of GCC@. In some cases, to
3768 bring GCC up on such a system, if still possible with current GCC, may
3769 require first installing an old version of GCC which did work on that
3770 system, and using it to compile a more recent GCC, to avoid bugs in
3771 the vendor compiler. Old releases of GCC 1 and GCC 2 are available in
3772 the @file{old-releases} directory on the
3773 @uref{../mirrors.html,,GCC mirror sites}. Header bugs may generally
3774 be avoided using @command{fixincludes}, but bugs or deficiencies in
3775 libraries and the operating system may still cause problems.
3777 For some systems, old versions of GNU binutils may also be useful,
3778 and are available from @file{pub/binutils/old-releases} on
3779 @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}.
3781 Some of the information on specific systems above relates to
3782 such older systems, but much of the information
3783 about GCC on such systems (which may no longer be applicable to
3784 current GCC) is to be found in the GCC texinfo manual.
3790 @heading @anchor{elf_targets}all ELF targets (SVR4, Solaris 2, etc.)
3792 C++ support is significantly better on ELF targets if you use the
3793 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
3794 inlines, vtables and template instantiations will be discarded
3804 @uref{./index.html,,Return to the GCC Installation page}
3808 @c ***Old documentation******************************************************
3810 @include install-old.texi
3817 @uref{./index.html,,Return to the GCC Installation page}
3821 @c ***GFDL********************************************************************
3830 @uref{./index.html,,Return to the GCC Installation page}
3834 @c ***************************************************************************
3835 @c Part 6 The End of the Document
3837 @comment node-name, next, previous, up
3838 @node Concept Index, , GNU Free Documentation License, Top
3842 @unnumbered Concept Index