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.1/buildstat.html,,3.1},
156 @uref{http://gcc.gnu.org/gcc-3.0/buildstat.html,,3.0}
158 @uref{http://gcc.gnu.org/gcc-2.95/buildstat.html,,2.95}.
159 These lists are updated as new information becomes available.
161 The installation procedure itself is broken into five steps.
165 * Downloading the source::
168 * Testing:: (optional)
175 @uref{download.html,,Downloading the source}
177 @uref{configure.html,,Configuration}
179 @uref{build.html,,Building}
181 @uref{test.html,,Testing} (optional)
183 @uref{finalinstall.html,,Final install}
187 Please note that GCC does not support @samp{make uninstall} and probably
188 won't do so in the near future as this would open a can of worms. Instead,
189 we suggest that you install GCC into a directory of its own and simply
190 remove that directory when you do not need that specific version of GCC
191 any longer, and, if shared libraries are installed there as well, no
192 more binaries exist that use them.
195 There are also some @uref{old.html,,old installation instructions},
196 which are mostly obsolete but still contain some information which has
197 not yet been merged into the main part of this manual.
205 @uref{./index.html,,Return to the GCC Installation page}
211 @c ***Downloading the source**************************************************
213 @comment node-name, next, previous, up
214 @node Downloading the source, Configuration, , Installing GCC
218 <h1 align="center">Downloading GCC</h1>
221 @chapter Downloading GCC
223 @cindex Downloading GCC
224 @cindex Downloading the Source
226 GCC is distributed via @uref{http://gcc.gnu.org/cvs.html,,CVS} and FTP
227 tarballs compressed with @command{gzip} or
228 @command{bzip2}. It is possible to download a full distribution or specific
231 Please refer to our @uref{http://gcc.gnu.org/releases.html,,releases web page}
232 for information on how to obtain GCC@.
234 The full distribution includes the C, C++, Objective-C, Fortran, Java,
235 and Ada (in case of GCC 3.1 and later) compilers. The full distribution
236 also includes runtime libraries for C++, Objective-C, Fortran, and Java.
237 In GCC 3.0 and later versions, GNU compiler testsuites are also included
238 in the full distribution.
240 If you choose to download specific components, you must download the core
241 GCC distribution plus any language specific distributions you wish to
242 use. The core distribution includes the C language front end as well as the
243 shared components. Each language has a tarball which includes the language
244 front end as well as the language runtime (when appropriate).
246 Unpack the core distribution as well as any language specific
247 distributions in the same directory.
249 If you also intend to build binutils (either to upgrade an existing
250 installation or for use in place of the corresponding tools of your
251 OS), unpack the binutils distribution either in the same directory or
252 a separate one. In the latter case, add symbolic links to any
253 components of the binutils you intend to build alongside the compiler
254 (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
255 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
262 @uref{./index.html,,Return to the GCC Installation page}
266 @c ***Configuration***********************************************************
268 @comment node-name, next, previous, up
269 @node Configuration, Building, Downloading the source, Installing GCC
273 <h1 align="center">Installing GCC: Configuration</h1>
276 @chapter Installing GCC: Configuration
278 @cindex Configuration
279 @cindex Installing GCC: Configuration
281 Like most GNU software, GCC must be configured before it can be built.
282 This document describes the recommended configuration procedure
283 for both native and cross targets.
285 We use @var{srcdir} to refer to the toplevel source directory for
286 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
288 If you obtained the sources via CVS, @var{srcdir} must refer to the top
289 @file{gcc} directory, the one where the @file{MAINTAINERS} can be found,
290 and not its @file{gcc} subdirectory, otherwise the build will fail.
292 First, in general, GCC @strong{must} be built into a separate directory
293 than the sources which does @strong{not} reside within the source tree.
294 This is how almost all developers build GCC; building where @var{srcdir}
295 == @var{objdir} is completely unsupported; building where @var{objdir}
296 is a subdirectory of @var{srcdir} is completely unsupported.
298 If you have previously built GCC in the same directory for a
299 different target machine, do @samp{make distclean} to delete all files
300 that might be invalid. One of the files this deletes is
301 @file{Makefile}; if @samp{make distclean} complains that @file{Makefile}
302 does not exist, it probably means that the directory is already suitably
303 clean. However, with the recommended method of building in a separate
304 @var{objdir}, you should simply use a different @var{objdir} for each
307 Second, when configuring a native system, either @command{cc} or
308 @command{gcc} must be in your path or you must set @env{CC} in
309 your environment before running configure. Otherwise the configuration
312 Note that the bootstrap compiler and the resulting GCC must be link
313 compatible, else the bootstrap will fail with linker errors about
314 incompatible object file formats. Several multilibed targets are
315 affected by this requirement, see
317 @ref{Specific, host/target specific installation notes}.
320 @uref{specific.html,,host/target specific installation notes}.
328 % @var{srcdir}/configure [@var{options}] [@var{target}]
332 @heading Target specification
335 GCC has code to correctly determine the correct value for @var{target}
336 for nearly all native systems. Therefore, we highly recommend you not
337 provide a configure target when configuring a native compiler.
340 @var{target} must be specified as @option{--target=@var{target}}
341 when configuring a cross compiler; examples of valid targets would be
342 i960-rtems, m68k-coff, sh-elf, etc.
345 Specifying just @var{target} instead of @option{--target=@var{target}}
346 implies that the host defaults to @var{target}.
350 @heading Options specification
352 Use @var{options} to override several configure time options for
353 GCC@. A list of supported @var{options} follows; @command{configure
354 --help} may list other options, but those not listed below may not
355 work and should not normally be used.
358 @item --prefix=@var{dirname}
359 Specify the toplevel installation
360 directory. This is the recommended way to install the tools into a directory
361 other than the default. The toplevel installation directory defaults to
364 We @strong{highly} recommend against @var{dirname} being the same or a
365 subdirectory of @var{objdir} or vice versa.
367 These additional options control where certain parts of the distribution
368 are installed. Normally you should not need to use these options.
371 @item --exec-prefix=@var{dirname}
372 Specify the toplevel installation directory for architecture-dependent
373 files. The default is @file{@var{prefix}}.
375 @item --bindir=@var{dirname}
376 Specify the installation directory for the executables called by users
377 (such as @command{gcc} and @command{g++}). The default is
378 @file{@var{exec-prefix}/bin}.
380 @item --libdir=@var{dirname}
381 Specify the installation directory for object code libraries and
382 internal parts of GCC@. The default is @file{@var{exec-prefix}/lib}.
384 @item --with-slibdir=@var{dirname}
385 Specify the installation directory for the shared libgcc library. The
386 default is @file{@var{libdir}}.
388 @item --infodir=@var{dirname}
389 Specify the installation directory for documentation in info format.
390 The default is @file{@var{prefix}/info}.
392 @item --mandir=@var{dirname}
393 Specify the installation directory for manual pages. The default is
394 @file{@var{prefix}/man}. (Note that the manual pages are only extracts from
395 the full GCC manuals, which are provided in Texinfo format. The
396 @command{g77} manpage is unmaintained and may be out of date; the others
397 are derived by an automatic conversion process from parts of the full
400 @item --with-gxx-include-dir=@var{dirname}
402 the installation directory for G++ header files. The default is
403 @file{@var{prefix}/include/g++-v3}.
407 @item --program-prefix=@var{prefix}
408 GCC supports some transformations of the names of its programs when
409 installing them. This option prepends @var{prefix} to the names of
410 programs to install in @var{bindir} (see above). For example, specifying
411 @option{--program-prefix=foo-} would result in @samp{gcc}
412 being installed as @file{/usr/local/bin/foo-gcc}.
414 @item --program-suffix=@var{suffix}
415 Appends @var{suffix} to the names of programs to install in @var{bindir}
416 (see above). For example, specifying @option{--program-suffix=-3.1}
417 would result in @samp{gcc} being installed as
418 @file{/usr/local/bin/gcc-3.1}.
420 @item --program-transform-name=@var{pattern}
421 Applies the @samp{sed} script @var{pattern} to be applied to the names
422 of programs to install in @var{bindir} (see above). @var{pattern} has to
423 consist of one or more basic @samp{sed} editing commands, separated by
424 semicolons. For example, if you want the @samp{gcc} program name to be
425 transformed to the installed program @file{/usr/local/bin/myowngcc} and
426 the @samp{g++} program name to be transformed to
427 @file{/usr/local/bin/gspecial++} without changing other program names,
428 you could use the pattern
429 @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}
430 to achieve this effect.
432 All three options can be combined and used together, resulting in more
433 complex conversion patterns. As a basic rule, @var{prefix} (and
434 @var{suffix}) are prepended (appended) before further transformations
435 can happen with a special transformation script @var{pattern}.
437 As currently implemented, this options only take effect for native
438 builds; cross compiler binaries' names are not transformed even when a
439 transformation is explicitly asked for by one of this options.
441 For native builds, some of the installed programs are also installed
442 with the target alias in front of their name, as in
443 @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
444 before the target alias is prepended to the name - so, specifying
445 @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
446 resulting binary would be installed as
447 @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.
449 As a last shortcoming, none of the installed Ada programs are
450 transformed yet, which will be fixed in some time.
452 @item --with-local-prefix=@var{dirname}
454 installation directory for local include files. The default is
455 @file{/usr/local}. Specify this option if you want the compiler to
456 search directory @file{@var{dirname}/include} for locally installed
457 header files @emph{instead} of @file{/usr/local/include}.
459 You should specify @option{--with-local-prefix} @strong{only} if your
460 site has a different convention (not @file{/usr/local}) for where to put
463 The default value for @option{--with-local-prefix} is @file{/usr/local}
464 regardless of the value of @option{--prefix}. Specifying
465 @option{--prefix} has no effect on which directory GCC searches for
466 local header files. This may seem counterintuitive, but actually it is
469 The purpose of @option{--prefix} is to specify where to @emph{install
470 GCC}. The local header files in @file{/usr/local/include}---if you put
471 any in that directory---are not part of GCC@. They are part of other
472 programs---perhaps many others. (GCC installs its own header files in
473 another directory which is based on the @option{--prefix} value.)
475 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
476 The directory you use for @option{--with-local-prefix} @strong{must not}
477 contain any of the system's standard header files. If it did contain
478 them, certain programs would be miscompiled (including GNU Emacs, on
479 certain targets), because this would override and nullify the header
480 file corrections made by the @code{fixincludes} script.
482 Indications are that people who use this option use it based on mistaken
483 ideas of what it is for. People use it as if it specified where to
484 install part of GCC@. Perhaps they make this assumption because
485 installing GCC creates the directory.
487 @item --enable-shared[=@var{package}[,@dots{}]]
488 Build shared versions of libraries, if shared libraries are supported on
489 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
490 are enabled by default on all platforms that support shared libraries,
491 except for @samp{libobjc} which is built as a static library only by
494 If a list of packages is given as an argument, build shared libraries
495 only for the listed packages. For other packages, only static libraries
496 will be built. Package names currently recognized in the GCC tree are
497 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
498 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc} and
499 @samp{libjava}. Note that @samp{libobjc} does not recognize itself by
500 any name, so, if you list package names in @option{--enable-shared},
501 you will only get static Objective-C libraries. @samp{libf2c} and
502 @samp{libiberty} do not support shared libraries at all.
504 Use @option{--disable-shared} to build only static libraries. Note that
505 @option{--disable-shared} does not accept a list of package names as
506 argument, only @option{--enable-shared} does.
508 @item @anchor{with-gnu-as}--with-gnu-as
509 Specify that the compiler should assume that the
510 assembler it finds is the GNU assembler. However, this does not modify
511 the rules to find an assembler and will result in confusion if found
512 assembler is not actually the GNU assembler. (Confusion will also
513 result if the compiler finds the GNU assembler but has not been
514 configured with @option{--with-gnu-as}.) If you have more than one
515 assembler installed on your system, you may want to use this option in
516 connection with @option{--with-as=@var{pathname}}.
518 The systems where it makes a difference whether you use the GNU assembler are
519 @samp{hppa1.0-@var{any}-@var{any}}, @samp{hppa1.1-@var{any}-@var{any}},
520 @samp{i386-@var{any}-sysv}, @samp{i386-@var{any}-isc},
521 @samp{i860-@var{any}-bsd}, @samp{m68k-bull-sysv},
522 @samp{m68k-hp-hpux}, @samp{m68k-sony-bsd},
523 @samp{m68k-altos-sysv}, @samp{m68000-hp-hpux},
524 @samp{m68000-att-sysv}, @samp{@var{any}-lynx-lynxos},
525 and @samp{mips-@var{any}}.
526 On any other system, @option{--with-gnu-as} has no effect.
528 On the systems listed above (except for the HP-PA, for ISC on the
529 386, and for @samp{mips-sgi-irix5.*}), if you use the GNU assembler,
530 you should also use the GNU linker (and specify @option{--with-gnu-ld}).
532 @item --with-as=@var{pathname}
534 compiler should use the assembler pointed to by @var{pathname}, rather
535 than the one found by the standard rules to find an assembler, which
540 @file{@var{exec_prefix}/lib/gcc-lib/@var{target}/@var{version}}
541 directory, where @var{exec_prefix} defaults to @var{prefix} which
542 defaults to @file{/usr/local} unless overridden by the
543 @option{--prefix=@var{pathname}} switch described above. @var{target} is the
544 target system triple, such as @samp{sparc-sun-solaris2.7}, and
545 @var{version} denotes the GCC version, such as 3.0.
547 Check operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
550 Note that these rules do not check for the value of @env{PATH}. You may
551 want to use @option{--with-as} if no assembler is installed in the
552 directories listed above, or if you have multiple assemblers installed
553 and want to choose one that is not found by the above rules.
555 @item @anchor{with-gnu-ld}--with-gnu-ld
556 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
560 @item --with-ld=@var{pathname}
562 @option{--with-as}, but for the linker.
565 Specify that stabs debugging
566 information should be used instead of whatever format the host normally
567 uses. Normally GCC uses the same debug format as the host system.
569 On MIPS based systems and on Alphas, you must specify whether you want
570 GCC to create the normal ECOFF debugging format, or to use BSD-style
571 stabs passed through the ECOFF symbol table. The normal ECOFF debug
572 format cannot fully handle languages other than C@. BSD stabs format can
573 handle other languages, but it only works with the GNU debugger GDB@.
575 Normally, GCC uses the ECOFF debugging format by default; if you
576 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
578 No matter which default you choose when you configure GCC, the user
579 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
580 the debug format for a particular compilation.
582 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
583 @option{--with-gas} is used. It selects use of stabs debugging
584 information embedded in COFF output. This kind of debugging information
585 supports C++ well; ordinary COFF debugging information does not.
587 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
588 selects use of stabs debugging information embedded in ELF output. The
589 C++ compiler currently (2.6.0) does not support the DWARF debugging
590 information normally used on 386 SVR4 platforms; stabs provide a
591 workable alternative. This requires gas and gdb, as the normal SVR4
592 tools can not generate or interpret stabs.
594 @item --disable-multilib
595 Specify that multiple target
596 libraries to support different target variants, calling
597 conventions, etc should not be built. The default is to build a
598 predefined set of them.
600 Some targets provide finer-grained control over which multilibs are built
601 (e.g., @option{--disable-softfloat}):
608 fpu, 26bit, underscore, interwork, biendian, nofmult.
611 softfloat, m68881, m68000, m68020.
614 single-float, biendian, softfloat.
616 @item powerpc*-*-*, rs6000*-*-*
617 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
622 @item --enable-threads
623 Specify that the target
624 supports threads. This affects the Objective-C compiler and runtime
625 library, and exception handling for other languages like C++ and Java.
626 On some systems, this is the default.
628 In general, the best (and, in many cases, the only known) threading
629 model available will be configured for use. Beware that on some
630 systems, gcc has not been taught what threading models are generally
631 available for the system. In this case, @option{--enable-threads} is an
632 alias for @option{--enable-threads=single}.
634 @item --disable-threads
635 Specify that threading support should be disabled for the system.
636 This is an alias for @option{--enable-threads=single}.
638 @item --enable-threads=@var{lib}
640 @var{lib} is the thread support library. This affects the Objective-C
641 compiler and runtime library, and exception handling for other languages
642 like C++ and Java. The possibilities for @var{lib} are:
650 Generic MACH thread support, known to work on NeXTSTEP@. (Please note
651 that the file needed to support this configuration, @file{gthr-mach.h}, is
652 missing and thus this setting will cause a known bootstrap failure.)
654 This is an alias for @samp{single}.
656 Generic POSIX thread support.
658 Same as @samp{posix} on arm*-*-linux*, *-*-chorusos* and *-*-freebsd*
659 only. A future release of gcc might remove this alias or extend it
662 RTEMS thread support.
664 Disable thread support, should work for all platforms.
666 Sun Solaris 2 thread support.
668 VxWorks thread support.
670 Microsoft Win32 API thread support.
673 @item --with-cpu=@var{cpu}
674 Specify which cpu variant the
675 compiler should generate code for by default. This is currently
676 only supported on the some ports, specifically arm, powerpc, and
677 SPARC@. If configure does not recognize the model name (e.g.@: arm700,
678 603e, or ultrasparc) you provide, please check the configure script
679 for a complete list of supported models.
681 @item --enable-altivec
682 Specify that the target supports AltiVec vector enhancements. This
683 option will adjust the ABI for AltiVec enhancements, as well as generate
684 AltiVec code when appropriate. This option is only available for
687 @item --enable-target-optspace
689 libraries should be optimized for code space instead of code speed.
690 This is the default for the m32r platform.
693 Specify that a user visible @command{cpp} program should not be installed.
695 @item --with-cpp-install-dir=@var{dirname}
696 Specify that the user visible @command{cpp} program should be installed
697 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
699 @item --enable-maintainer-mode
701 regenerate the GCC master message catalog @file{gcc.pot} are normally
702 disabled. This is because it can only be rebuilt if the complete source
703 tree is present. If you have changed the sources and want to rebuild the
704 catalog, configuring with @option{--enable-maintainer-mode} will enable
705 this. Note that you need a recent version of the @code{gettext} tools
708 @item --enable-version-specific-runtime-libs
710 that runtime libraries should be installed in the compiler specific
711 subdirectory (@file{@var{libsubdir}}) rather than the usual places. In
712 addition, @samp{libstdc++}'s include files will be installed in
713 @file{@var{libsubdir}/include/g++} unless you overruled it by using
714 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
715 particularly useful if you intend to use several versions of GCC in
716 parallel. This is currently supported by @samp{libf2c} and
717 @samp{libstdc++}, and is the default for @samp{libobjc} which cannot be
718 changed in this case.
720 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
721 Specify that only a particular subset of compilers and
722 their runtime libraries should be built. For a list of valid values for
723 @var{langN} you can issue the following command in the
724 @file{gcc} directory of your GCC source tree:@*
726 grep language= */config-lang.in
728 Currently, you can use any of the following:
729 @code{ada}, @code{c}, @code{c++}, @code{f77}, @code{java}, @code{objc}.
730 Building the Ada compiler has special requirements, see below.@*
731 If you do not pass this flag, all languages available in the @file{gcc}
732 sub-tree will be configured. Re-defining @code{LANGUAGES} when calling
733 @samp{make bootstrap} @strong{does not} work anymore, as those
734 language sub-directories might not have been configured!
736 @item --disable-libgcj
737 Specify that the run-time libraries
738 used by GCJ should not be built. This is useful in case you intend
739 to use GCJ with some other run-time, or you're going to install it
740 separately, or it just happens not to build on your particular
741 machine. In general, if the Java front end is enabled, the GCJ
742 libraries will be enabled too, unless they're known to not work on
743 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
744 may need to port it; in this case, before modifying the top-level
745 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
746 you may use @option{--enable-libgcj} to override the default.
749 Specify that the compiler should
750 use DWARF 2 debugging information as the default.
752 @item --enable-win32-registry
753 @itemx --enable-win32-registry=@var{key}
754 @itemx --disable-win32-registry
755 The @option{--enable-win32-registry} option enables Windows-hosted GCC
756 to look up installations paths in the registry using the following key:
759 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
762 @var{key} defaults to GCC version number, and can be overridden by the
763 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
764 who use custom installers are encouraged to provide a different key,
765 perhaps one comprised of vendor name and GCC version number, to
766 avoid conflict with existing installations. This feature is enabled
767 by default, and can be disabled by @option{--disable-win32-registry}
768 option. This option has no effect on the other hosts.
771 Specify that the machine does not have a floating point unit. This
772 option only applies to @samp{m68k-sun-sunos@var{n}} and
773 @samp{m68k-isi-bsd}. On any other system, @option{--nfp} has no effect.
775 @item --enable-checking
776 @itemx --enable-checking=@var{list}
777 When you specify this option, the compiler is built to perform checking
778 of tree node types when referencing fields of that node, and some other
779 internal consistency checks. This does not change the generated code,
780 but adds error checking within the compiler. This will slow down the
781 compiler and may only work properly if you are building the compiler
782 with GCC@. This is on by default when building from CVS or snapshots,
783 but off for releases. More control over the checks may be had by
784 specifying @var{list}; the categories of checks available are
785 @samp{misc}, @samp{tree}, @samp{gc}, @samp{rtl} and @samp{gcac}. The
786 default when @var{list} is not specified is @samp{misc,tree,gc}; the
787 checks @samp{rtl} and @samp{gcac} are very expensive.
791 The @option{--enable-nls} option enables Native Language Support (NLS),
792 which lets GCC output diagnostics in languages other than American
793 English. Native Language Support is enabled by default if not doing a
794 canadian cross build. The @option{--disable-nls} option disables NLS@.
796 @item --with-included-gettext
797 If NLS is enabled, the @option{--with-included-gettext} option causes the build
798 procedure to prefer its copy of GNU @command{gettext}.
801 If NLS is enabled, and if the host lacks @code{gettext} but has the
802 inferior @code{catgets} interface, the GCC build procedure normally
803 ignores @code{catgets} and instead uses GCC's copy of the GNU
804 @code{gettext} library. The @option{--with-catgets} option causes the
805 build procedure to use the host's @code{catgets} in this situation.
807 @item --with-libiconv-prefix=@var{dir}
808 Search for libiconv header files in @file{@var{dir}/include} and
809 libiconv library files in @file{@var{dir}/lib}.
811 @item --with-system-zlib
812 Use installed zlib rather than that included with GCC@. This option
813 only applies if the Java front end is being built.
815 @item --enable-obsolete
816 Enable configuration for an obsoleted system. If you attempt to
817 configure GCC for a system (build, host, or target) which has been
818 obsoleted, and you do not specify this flag, configure will halt with an
821 All support for systems which have been obsoleted in one release of GCC
822 is removed entirely in the next major release, unless someone steps
823 forward to maintain the port.
826 Some options which only apply to building cross compilers:
828 @item --with-headers=@var{dir}
829 Specifies a directory
830 which has target include files.
831 @emph{This options is required} when building a cross
832 compiler, if @file{@var{prefix}/@var{target}/sys-include} doesn't pre-exist.
833 These include files will be copied into the @file{gcc} install directory.
834 Fixincludes will be run on these files to make them compatible with
836 @item --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
837 Specifies a list of directories which contain the target runtime
838 libraries. These libraries will be copied into the @file{gcc} install
841 Specifies that @samp{newlib} is
842 being used as the target C library. This causes @code{__eprintf} to be
843 omitted from @file{libgcc.a} on the assumption that it will be provided by
847 Note that each @option{--enable} option has a corresponding
848 @option{--disable} option and that each @option{--with} option has a
849 corresponding @option{--without} option.
856 @uref{./index.html,,Return to the GCC Installation page}
860 @c ***Building****************************************************************
862 @comment node-name, next, previous, up
863 @node Building, Testing, Configuration, Installing GCC
867 <h1 align="center">Installing GCC: Building</h1>
872 @cindex Installing GCC: Building
874 Now that GCC is configured, you are ready to build the compiler and
877 We @strong{highly} recommend that GCC be built using GNU make;
878 other versions may work, then again they might not.
879 GNU make is required for compiling GNAT (the Ada compiler) and the Java
882 (For example, many broken versions of make will fail if you use the
883 recommended setup where @var{objdir} is different from @var{srcdir}.
884 Other broken versions may recompile parts of the compiler when
885 installing the compiler.)
887 Some commands executed when making the compiler may fail (return a
888 nonzero status) and be ignored by @code{make}. These failures, which
889 are often due to files that were not found, are expected, and can safely
892 It is normal to have compiler warnings when compiling certain files.
893 Unless you are a GCC developer, you can generally ignore these warnings
894 unless they cause compilation to fail.
896 On certain old systems, defining certain environment variables such as
897 @env{CC} can interfere with the functioning of @command{make}.
899 If you encounter seemingly strange errors when trying to build the
900 compiler in a directory other than the source directory, it could be
901 because you have previously configured the compiler in the source
902 directory. Make sure you have done all the necessary preparations.
904 If you build GCC on a BSD system using a directory stored in an old System
905 V file system, problems may occur in running @code{fixincludes} if the
906 System V file system doesn't support symbolic links. These problems
907 result in a failure to fix the declaration of @code{size_t} in
908 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
909 that type mismatches occur, this could be the cause.
911 The solution is not to use such a directory for building GCC@.
913 When building from CVS or snapshots, or if you modify parser sources,
914 you need the Bison parser generator installed. Any version 1.25 or
915 later should work; older versions may also work. If you do not modify
916 parser sources, releases contain the Bison-generated files and you do
917 not need Bison installed to build them.
919 When building from CVS or snapshots, or if you modify Texinfo
920 documentation, you need version 4.1 or later of Texinfo installed if you
921 want Info documentation to be regenerated. Releases contain Info
922 documentation pre-built for the unmodified documentation in the release.
924 @section Building a native compiler
926 For a native build issue the command @samp{make bootstrap}. This
927 will build the entire GCC system, which includes the following steps:
931 Build host tools necessary to build the compiler such as texinfo, bison,
935 Build target tools for use by the compiler such as binutils (bfd,
936 binutils, gas, gprof, ld, and opcodes)
937 if they have been individually linked
938 or moved into the top level GCC source tree before configuring.
941 Perform a 3-stage bootstrap of the compiler.
944 Perform a comparison test of the stage2 and stage3 compilers.
947 Build runtime libraries using the stage3 compiler from the previous step.
951 If you are short on disk space you might consider @samp{make
952 bootstrap-lean} instead. This is identical to @samp{make
953 bootstrap} except that object files from the stage1 and
954 stage2 of the 3-stage bootstrap of the compiler are deleted as
955 soon as they are no longer needed.
958 If you want to save additional space during the bootstrap and in
959 the final installation as well, you can build the compiler binaries
960 without debugging information with @samp{make CFLAGS='-O' LIBCFLAGS='-g
961 -O2' LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap}. This will save
962 roughly 40% of disk space both for the bootstrap and the final installation.
963 (Libraries will still contain debugging information.)
965 If you wish to use non-default GCC flags when compiling the stage2 and
966 stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing
967 @samp{make bootstrap}. Non-default optimization flags are less well
968 tested here than the default of @samp{-g -O2}, but should still work.
969 In a few cases, you may find that you need to specify special flags such
970 as @option{-msoft-float} here to complete the bootstrap; or, if the
971 native compiler miscompiles the stage1 compiler, you may need to work
972 around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the
973 stage1 compiler that were miscompiled, or by using @samp{make
974 bootstrap4} to increase the number of stages of bootstrap.
976 If you used the flag @option{--enable-languages=@dots{}} to restrict
977 the compilers to be built, only those you've actually enabled will be
978 built. This will of course only build those runtime libraries, for
979 which the particular compiler has been built. Please note,
980 that re-defining @env{LANGUAGES} when calling @samp{make bootstrap}
981 @strong{does not} work anymore!
983 If the comparison of stage2 and stage3 fails, this normally indicates
984 that the stage2 compiler has compiled GCC incorrectly, and is therefore
985 a potentially serious bug which you should investigate and report. (On
986 a few systems, meaningful comparison of object files is impossible; they
987 always appear ``different''. If you encounter this problem, you will
988 need to disable comparison in the @file{Makefile}.)
990 @section Building a cross compiler
992 We recommend reading the
993 @uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ}
994 for information about building cross compilers.
996 When building a cross compiler, it is not generally possible to do a
997 3-stage bootstrap of the compiler. This makes for an interesting problem
998 as parts of GCC can only be built with GCC@.
1000 To build a cross compiler, we first recommend building and installing a
1001 native compiler. You can then use the native GCC compiler to build the
1002 cross compiler. The installed native compiler needs to be GCC version
1005 Assuming you have already installed a native copy of GCC and configured
1006 your cross compiler, issue the command @command{make}, which performs the
1011 Build host tools necessary to build the compiler such as texinfo, bison,
1015 Build target tools for use by the compiler such as binutils (bfd,
1016 binutils, gas, gprof, ld, and opcodes)
1017 if they have been individually linked or moved into the top level GCC source
1018 tree before configuring.
1021 Build the compiler (single stage only).
1024 Build runtime libraries using the compiler from the previous step.
1027 Note that if an error occurs in any step the make process will exit.
1029 @section Building in parallel
1031 If you have a multiprocessor system you can use @samp{make bootstrap
1032 MAKE="make -j 2" -j 2} or just @samp{make -j 2 bootstrap}
1033 for GNU Make 3.79 and above instead of just @samp{make bootstrap}
1034 when building GCC@. You can use a bigger number instead of two if
1035 you like. In most cases, it won't help to use a number bigger than
1036 the number of processors in your machine.
1038 @section Building the Ada compiler
1040 In order to build GNAT, the Ada compiler, you need a working GNAT
1041 compiler (GNAT version 3.13 or later, or GCC version 3.1 or later),
1042 since the Ada front end is written in Ada (with some
1043 GNAT-specific extensions), and GNU make.
1045 However, you do not need a full installation of GNAT, just the GNAT
1046 binary @file{gnat1}, a copy of @file{gnatbind}, and a compiler driver
1047 which can deal with Ada input (by invoking the @file{gnat1} binary).
1048 You can specify this compiler driver by setting the @env{ADAC}
1049 environment variable at the configure step. @command{configure} can
1050 detect the driver automatically if it has got a common name such as
1051 @command{gcc} or @command{gnatgcc}. Of course, you still need a working
1052 C compiler (the compiler driver can be different or not).
1053 @command{configure} does not test whether the GNAT installation works
1054 and has a sufficiently recent version; if too old a GNAT version is
1055 installed, the build will fail unless @option{--enable-languages} is
1056 used to disable building the Ada front end.
1058 Additional build tools (such as @command{gnatmake}) or a working GNAT
1059 run-time library installation are usually @emph{not} required. However,
1060 if you want to boostrap the compiler using a minimal version of GNAT,
1061 you have to issue the following commands before invoking @samp{make
1062 boostrap} (this assumes that you start with an unmodified and consistent
1063 source distribution):
1066 cd @var{srcdir}/gcc/ada
1067 touch treeprs.ads [es]info.h nmake.ad[bs]
1070 At the moment, the GNAT library and several tools for GNAT are not built
1071 by @samp{make bootstrap}. You have to invoke
1072 @samp{make gnatlib_and_tools} in the @file{@var{objdir}/gcc}
1073 subdirectory before proceeding with the next steps.
1075 For example, you can build a native Ada compiler by issuing the
1076 following commands (assuming @command{make} is GNU make):
1080 @var{srcdir}/configure --enable-languages=c,ada
1081 cd @var{srcdir}/gcc/ada
1082 touch treeprs.ads [es]info.h nmake.ad[bs]
1086 make gnatlib_and_tools
1090 Currently, when compiling the Ada front end, you cannot use the parallel
1091 build feature described in the previous section.
1098 @uref{./index.html,,Return to the GCC Installation page}
1102 @c ***Testing*****************************************************************
1104 @comment node-name, next, previous, up
1105 @node Testing, Final install, Building, Installing GCC
1109 <h1 align="center">Installing GCC: Testing</h1>
1112 @chapter Installing GCC: Testing
1115 @cindex Installing GCC: Testing
1118 Before you install GCC, we encourage you to run the testsuites and to
1119 compare your results with results from a similar configuration that have
1120 been submitted to the
1121 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
1122 This step is optional and may require you to download additional software,
1123 but it can give you confidence in your new GCC installation or point out
1124 problems before you install and start using your new GCC.
1126 First, you must have @uref{download.html,,downloaded the testsuites}.
1127 These are part of the full distribution, but if you downloaded the
1128 ``core'' compiler plus any front ends, you must download the testsuites
1131 Second, you must have the testing tools installed. This includes
1132 a @uref{http://www.gnu.org/software/dejagnu/,,current version of DejaGnu};
1133 dejagnu 1.3 is not sufficient.
1134 It also includes Tcl and Expect; the DejaGnu site has links to these.
1136 Now you may need specific preparations:
1141 The following environment variables may need to be set appropriately, as in
1142 the following example (which assumes that DejaGnu has been installed
1143 under @file{/usr/local}):
1146 TCL_LIBRARY = /usr/local/share/tcl8.0
1147 DEJAGNULIBS = /usr/local/share/dejagnu
1150 On systems such as Cygwin, these paths are required to be actual
1151 paths, not mounts or links; presumably this is due to some lack of
1152 portability in the DejaGnu code.
1154 If the directories where @command{runtest} and @command{expect} were
1155 installed are in the @env{PATH}, it should not be necessary to set these
1156 environment variables.
1160 Finally, you can run the testsuite (which may take a long time):
1162 cd @var{objdir}; make -k check
1165 The testing process will try to test as many components in the GCC
1166 distribution as possible, including the C, C++, Objective-C and Fortran
1167 compilers as well as the C++ and Java runtime libraries.
1169 @section How can I run the test suite on selected tests?
1171 As a first possibility to cut down the number of tests that are run it is
1172 possible to use @samp{make check-gcc} or @samp{make check-g++}
1173 in the @file{gcc} subdirectory of the object directory. To further cut down the
1174 tests the following is possible:
1177 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
1180 This will run all @command{gcc} execute tests in the testsuite.
1183 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
1186 This will run the @command{g++} ``old-deja'' tests in the testsuite where the filename
1187 matches @samp{9805*}.
1189 The @file{*.exp} files are located in the testsuite directories of the GCC
1190 source, the most important ones being @file{compile.exp},
1191 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
1192 To get a list of the possible @file{*.exp} files, pipe the
1193 output of @samp{make check} into a file and look at the
1194 @samp{Running @dots{} .exp} lines.
1196 @section How to interpret test results
1198 After the testsuite has run you'll find various @file{*.sum} and @file{*.log}
1199 files in the testsuite subdirectories. The @file{*.log} files contain a
1200 detailed log of the compiler invocations and the corresponding
1201 results, the @file{*.sum} files summarize the results. These summaries list
1202 all the tests that have been run with a corresponding status code:
1206 PASS: the test passed as expected
1208 XPASS: the test unexpectedly passed
1210 FAIL: the test unexpectedly failed
1212 XFAIL: the test failed as expected
1214 UNSUPPORTED: the test is not supported on this platform
1216 ERROR: the testsuite detected an error
1218 WARNING: the testsuite detected a possible problem
1221 It is normal for some tests to report unexpected failures. At the
1222 current time our testing harness does not allow fine grained control
1223 over whether or not a test is expected to fail. We expect to fix this
1224 problem in future releases.
1227 @section Submitting test results
1229 If you want to report the results to the GCC project, use the
1230 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
1233 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
1234 -m gcc-testresults@@gcc.gnu.org |sh
1237 This script uses the @command{Mail} program to send the results, so
1238 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
1239 prepended to the testsuite summary and should contain any special
1240 remarks you have on your results or your build environment. Please
1241 do not edit the testsuite result block or the subject line, as these
1242 messages are automatically parsed and presented at the
1243 @uref{http://gcc.gnu.org/testresults/,,GCC testresults} web
1244 page. Here you can also gather information on how specific tests
1245 behave on different platforms and compare them with your results. A
1246 few failing testcases are possible even on released versions and you
1247 should look here first if you think your results are unreasonable.
1254 @uref{./index.html,,Return to the GCC Installation page}
1258 @c ***Final install***********************************************************
1260 @comment node-name, next, previous, up
1261 @node Final install, , Testing, Installing GCC
1263 @ifset finalinstallhtml
1265 <h1 align="center">Installing GCC: Final installation</h1>
1268 @chapter Installing GCC: Final installation
1271 Now that GCC has been built (and optionally tested), you can install it with
1273 cd @var{objdir}; make install
1276 That step completes the installation of GCC; user level binaries can
1277 be found in @file{@var{prefix}/bin} where @var{prefix} is the value you
1278 specified with the @option{--prefix} to configure (or @file{/usr/local}
1279 by default). (If you specified @option{--bindir}, that directory will
1280 be used instead; otherwise, if you specified @option{--exec-prefix},
1281 @file{@var{exec-prefix}/bin} will be used.) Headers for the C++ and
1282 Java libraries are installed in @file{@var{prefix}/include}; libraries
1283 in @file{@var{libdir}} (normally @file{@var{prefix}/lib}); internal
1284 parts of the compiler in @file{@var{libdir}/gcc-lib}; documentation in
1285 info format in @file{@var{infodir}} (normally @file{@var{prefix}/info}).
1287 If you built a released version of GCC using @samp{make bootstrap} then please
1288 quickly review the build status page for
1289 @uref{http://gcc.gnu.org/gcc-3.1/buildstat.html,,3.1},
1290 @uref{http://gcc.gnu.org/gcc-3.0/buildstat.html,,3.0}, or
1291 @uref{http://gcc.gnu.org/gcc-2.95/buildstat.html,,2.95}.
1292 If your system is not listed for the version of GCC that you built,
1294 @email{gcc@@gcc.gnu.org} indicating
1295 that you successfully built and installed GCC.
1296 Include the following information:
1300 Output from running @file{@var{srcdir}/config.guess}. Do not send us
1301 that file itself, just the one-line output from running it.
1304 The output of @samp{gcc -v} for your newly installed gcc.
1305 This tells us which version of GCC you built and the options you passed to
1309 Whether you enabled all languages or a subset of them. If you used a
1310 full distribution then this information is part of the configure
1311 options in the output of @samp{gcc -v}, but if you downloaded the
1312 ``core'' compiler plus additional front ends then it isn't apparent
1313 which ones you built unless you tell us about it.
1316 If the build was for GNU/Linux, also include:
1319 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
1320 this information should be available from @file{/etc/issue}.
1323 The version of the Linux kernel, available from @samp{uname --version}
1327 The version of glibc you used; for RPM-based systems like Red Hat,
1328 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
1329 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
1331 For other systems, you can include similar information if you think it is
1335 Any other information that you think would be useful to people building
1336 GCC on the same configuration. The new entry in the build status list
1337 will include a link to the archived copy of your message.
1340 We'd also like to know if the
1342 @ref{Specific, host/target specific installation notes}
1345 @uref{specific.html,,host/target specific installation notes}
1347 didn't include your host/target information or if that information is
1348 incomplete or out of date. Send a note to
1349 @email{gcc@@gcc.gnu.org} telling us how the information should be changed.
1351 If you find a bug, please report it following our
1352 @uref{../bugs.html,,bug reporting guidelines}.
1354 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
1355 dvi}. You will need to have @command{texi2dvi} (version at least 4.1)
1356 and @TeX{} installed. This creates a number of @file{.dvi} files in
1357 subdirectories of @file{@var{objdir}}; these may be converted for
1358 printing with programs such as @command{dvips}. You can also
1359 @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the
1360 Free Software Foundation}, though such manuals may not be for the most
1361 recent version of GCC@.
1368 @uref{./index.html,,Return to the GCC Installation page}
1372 @c ***Binaries****************************************************************
1374 @comment node-name, next, previous, up
1375 @node Binaries, Specific, Installing GCC, Top
1379 <h1 align="center">Installing GCC: Binaries</h1>
1382 @chapter Installing GCC: Binaries
1385 @cindex Installing GCC: Binaries
1387 We are often asked about pre-compiled versions of GCC@. While we cannot
1388 provide these for all platforms, below you'll find links to binaries for
1389 various platforms where creating them by yourself is not easy due to various
1392 Please note that we did not create these binaries, nor do we
1393 support them. If you have any problems installing them, please
1394 contact their makers.
1401 @uref{http://freeware.bull.net,,Bull's Freeware and Shareware Archive for AIX};
1404 @uref{http://aixpdslib.seas.ucla.edu,,UCLA Software Library for AIX};
1408 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP};
1414 @uref{http://hpux.cae.wisc.edu/,,HP-UX Porting Center};
1417 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
1421 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
1422 OpenServer/Unixware};
1425 Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware};
1428 SGI---@uref{http://freeware.sgi.com/,,SGI Freeware};
1431 Windows 95, 98, and NT:
1434 The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project;
1436 @uref{http://www.xraylith.wisc.edu/~khan/software/gnu-win32/,,GNU Win32}
1437 related projects by Mumit Khan.
1441 @uref{ftp://ftp.thewrittenword.com/packages/free/by-name/,,The
1442 Written Word} offers binaries for Solaris 2.5.1, 2.6, 2.7/SPARC, 2.7/Intel,
1443 IRIX 6.2, 6.5, Digital UNIX 4.0D, HP-UX 10.20, and HP-UX 11.00.
1446 Hitachi H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
1447 Development Tools for the Hitachi H8/300[HS] Series}
1451 In addition to those specific offerings, you can get a binary
1452 distribution CD-ROM from the
1453 @uref{http://www.fsf.org/order/order.html,,Free Software Foundation}.
1454 It contains binaries for a number of platforms, and
1455 includes not only GCC, but other stuff as well. The current CD does
1456 not contain the latest version of GCC, but it should allow
1457 bootstrapping the compiler. An updated version of that disk is in the
1465 @uref{./index.html,,Return to the GCC Installation page}
1469 @c ***Specific****************************************************************
1471 @comment node-name, next, previous, up
1472 @node Specific, Old, Binaries, Top
1476 <h1 align="center">Host/target specific installation notes for GCC</h1>
1479 @chapter Host/target specific installation notes for GCC
1482 @cindex Specific installation notes
1483 @cindex Target specific installation
1484 @cindex Host specific installation
1485 @cindex Target specific installation notes
1487 Please read this document carefully @emph{before} installing the
1488 GNU Compiler Collection on your machine.
1493 @uref{#1750a-*-*,,1750a-*-*}
1497 @uref{#a29k-*-bsd,,a29k-*-bsd}
1499 @uref{#alpha*-*-*,,alpha*-*-*}
1501 @uref{#alpha*-dec-osf*,,alpha*-dec-osf*}
1503 @uref{#alphaev5-cray-unicosmk*,,alphaev5-cray-unicosmk*}
1505 @uref{#arc-*-elf,,arc-*-elf}
1507 @uref{#arm-*-aout,,arm-*-aout}
1509 @uref{#arm-*-elf,,arm-*-elf}
1511 @uref{#arm*-*-linux-gnu,,arm*-*-linux-gnu}
1513 @uref{#arm-*-riscix,,arm-*-riscix}
1521 @uref{#dsp16xx,,dsp16xx}
1523 @uref{#elxsi-elxsi-bsd,,elxsi-elxsi-bsd}
1525 @uref{#*-*-freebsd*,,*-*-freebsd*}
1527 @uref{#h8300-hms,,h8300-hms}
1529 @uref{#hppa*-hp-hpux*,,hppa*-hp-hpux*}
1531 @uref{#hppa*-hp-hpux9,,hppa*-hp-hpux9}
1533 @uref{#hppa*-hp-hpux10,,hppa*-hp-hpux10}
1535 @uref{#hppa*-hp-hpux11,,hppa*-hp-hpux11}
1537 @uref{#i370-*-*,,i370-*-*}
1539 @uref{#*-*-linux-gnu,,*-*-linux-gnu}
1541 @uref{#ix86-*-linux*oldld,,i?86-*-linux*oldld}
1543 @uref{#ix86-*-linux*aout,,i?86-*-linux*aout}
1545 @uref{#ix86-*-linux*,,i?86-*-linux*}
1547 @uref{#ix86-*-sco,,i?86-*-sco}
1549 @uref{#ix86-*-sco3.2v4,,i?86-*-sco3.2v4}
1551 @uref{#ix86-*-sco3.2v5*,,i?86-*-sco3.2v5*}
1553 @uref{#ix86-*-udk,,i?86-*-udk}
1555 @uref{#ix86-*-isc,,i?86-*-isc}
1557 @uref{#ix86-*-esix,,i?86-*-esix}
1559 @uref{#ix86-ibm-aix,,i?86-ibm-aix}
1561 @uref{#ix86-sequent-bsd,,i?86-sequent-bsd}
1563 @uref{#ix86-sequent-ptx1*,,i?86-sequent-ptx1*, i?86-sequent-ptx2*, i?86-sequent-sysv3*}
1565 @uref{#i860-intel-osf*,,i860-intel-osf*}
1567 @uref{#ia64-*-linux,,ia64-*-linux}
1569 @uref{#*-lynx-lynxos,,*-lynx-lynxos}
1571 @uref{#*-ibm-aix*,,*-ibm-aix*}
1573 @uref{#m32r-*-elf,,m32r-*-elf}
1575 @uref{#m68000-hp-bsd,,m68000-hp-bsd}
1577 @uref{#m6811-elf,,m6811-elf}
1579 @uref{#m6812-elf,,m6812-elf}
1581 @uref{#m68k-altos,,m68k-altos}
1583 @uref{#m68k-apple-aux,,m68k-apple-aux}
1585 @uref{#m68k-att-sysv,,m68k-att-sysv}
1587 @uref{#m68k-bull-sysv,,m68k-bull-sysv}
1589 @uref{#m68k-crds-unos,,m68k-crds-unos}
1591 @uref{#m68k-hp-hpux,,m68k-hp-hpux}
1593 @uref{#m68k-*-nextstep*,,m68k-*-nextstep*}
1595 @uref{#m68k-ncr-*,,m68k-ncr-*}
1597 @uref{#m68k-sun,,m68k-sun}
1599 @uref{#m68k-sun-sunos4.1.1,,m68k-sun-sunos4.1.1}
1601 @uref{#m88k-*-svr3,,m88k-*-svr3}
1603 @uref{#m88k-*-dgux,,m88k-*-dgux}
1605 @uref{#m88k-tektronix-sysv3,,m88k-tektronix-sysv3}
1607 @uref{#mips-*-*,,mips-*-*}
1609 @uref{#mips-dec-*,,mips-dec-*}
1611 @uref{#mips-mips-bsd,,mips-mips-bsd}
1613 @uref{#mips-mips-riscos*,,mips-mips-riscos*}
1615 @uref{#mips-sgi-irix4,,mips-sgi-irix4}
1617 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
1619 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
1621 @uref{#mips-sony-sysv,,mips-sony-sysv}
1623 @uref{#ns32k-encore,,ns32k-encore}
1625 @uref{#ns32k-*-genix,,ns32k-*-genix}
1627 @uref{#ns32k-sequent,,ns32k-sequent}
1629 @uref{#ns32k-utek,,ns32k-utek}
1631 @uref{#powerpc*-*-*,,powerpc*-*-*, powerpc-*-sysv4}
1633 @uref{#powerpc-*-darwin*,,powerpc-*-darwin*}
1635 @uref{#powerpc-*-elf,,powerpc-*-elf, powerpc-*-sysv4}
1637 @uref{#powerpc-*-linux-gnu*,,powerpc-*-linux-gnu*}
1639 @uref{#powerpc-*-netbsd*,,powerpc-*-netbsd*}
1641 @uref{#powerpc-*-eabiaix,,powerpc-*-eabiaix}
1643 @uref{#powerpc-*-eabisim,,powerpc-*-eabisim}
1645 @uref{#powerpc-*-eabi,,powerpc-*-eabi}
1647 @uref{#powerpcle-*-elf,,powerpcle-*-elf, powerpcle-*-sysv4}
1649 @uref{#powerpcle-*-eabisim,,powerpcle-*-eabisim}
1651 @uref{#powerpcle-*-eabi,,powerpcle-*-eabi}
1653 @uref{#powerpcle-*-winnt,,powerpcle-*-winnt, powerpcle-*-pe}
1655 @uref{#romp-*-aos,,romp-*-aos, romp-*-mach}
1657 @uref{#s390-*-linux*}
1659 @uref{#s390x-*-linux*}
1661 @uref{#*-*-solaris2*,,*-*-solaris2*}
1663 @uref{#sparc-sun-solaris2*,,sparc-sun-solaris2*}
1665 @uref{#sparc-sun-solaris2.7,,sparc-sun-solaris2.7}
1667 @uref{#sparc-sun-sunos4*,,sparc-sun-sunos4*}
1669 @uref{#sparc-unknown-linux-gnulibc1,,sparc-unknown-linux-gnulibc1}
1671 @uref{#sparc-*-linux*,,sparc-*-linux*}
1673 @uref{#sparc64-*-*,,sparc64-*-*}
1675 @uref{#sparcv9-*-solaris2*,,sparcv9-*-solaris2*}
1677 @uref{#*-*-sysv*,,*-*-sysv*}
1679 @uref{#vax-dec-ultrix,,vax-dec-ultrix}
1681 @uref{#we32k-*-*,,we32k-*-*}
1683 @uref{#xtensa-*-elf,,xtensa-*-elf}
1685 @uref{#xtensa-*-linux*,,xtensa-*-linux*}
1687 @uref{#windows,,Microsoft Windows}
1691 @uref{#older,,Older systems}
1696 @uref{#elf_targets,,all ELF targets} (SVR4, Solaris 2, etc.)
1702 <!-- -------- host/target specific issues start here ---------------- -->
1705 @heading @anchor{1750a-*-*}1750a-*-*
1706 MIL-STD-1750A processors. This target is obsoleted in GCC 3.1.
1708 The MIL-STD-1750A cross configuration produces output for
1709 @code{as1750}, an assembler/linker available under the GNU General Public
1710 License for the 1750A@. @code{as1750} can be obtained at
1711 @uref{ftp://ftp.fta-berlin.de/pub/crossgcc/1750gals/}.
1712 A similarly licensed simulator for
1713 the 1750A is available from same address.
1715 You should ignore a fatal error during the building of @samp{libgcc}
1716 (@samp{libgcc} is not yet implemented for the 1750A@.)
1718 The @code{as1750} assembler requires the file @file{ms1750.inc}, which is
1719 found in the directory @file{gcc/config/1750a}.
1721 GCC produced the same sections as the Fairchild F9450 C Compiler,
1726 The program code section.
1729 The read/write (RAM) data section.
1732 The read-only (ROM) constants section.
1735 Initialization section (code to copy KREL to SREL)@.
1738 The smallest addressable unit is 16 bits (@code{BITS_PER_UNIT} is 16). This
1739 means that type @code{char} is represented with a 16-bit word per character.
1740 The 1750A's ``Load/Store Upper/Lower Byte'' instructions are not used by
1747 @heading @anchor{a29k}a29k
1748 AMD Am29k-family processors. These are normally used in embedded
1749 applications. This configuration corresponds to AMD's standard calling
1750 sequence and binary interface and is compatible with other 29k tools.
1752 AMD has abandoned this processor. All existing a29k targets are obsoleted
1755 You may need to make a variant of the file @file{a29k.h} for your
1756 particular configuration.
1762 @heading @anchor{a29k-*-bsd}a29k-*-bsd
1763 AMD Am29050 used in a system running a variant of BSD Unix.
1769 @heading @anchor{alpha*-*-*}alpha*-*-*
1771 This section contains general configuration information for all
1772 alpha-based platforms using ELF (in particular, ignore this section for
1773 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
1774 section, please read all other sections that match your target.
1776 We require binutils 2.11.2 or newer.
1777 Previous binutils releases had a number of problems with DWARF 2
1778 debugging information, not the least of which is incorrect linking of
1785 @heading @anchor{alpha*-dec-osf*}alpha*-dec-osf*
1786 Systems using processors that implement the DEC Alpha architecture and
1787 are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
1788 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
1790 Support for versions before @code{alpha*-dec-osf4} is obsoleted in GCC
1791 3.1. (These are the versions which identify themselves as DEC OSF/1.)
1793 In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
1794 currently (2001-06-13) work with @command{mips-tfile}. As a workaround,
1795 we need to use the old assembler, invoked via the barely documented
1796 @option{-oldas} option. To bootstrap GCC, you either need to use the
1800 % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
1803 or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
1806 % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
1809 As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld}
1810 are supported on Tru64 UNIX, so you must not configure GCC with
1811 @option{--with-gnu-as} or @option{--with-gnu-ld}.
1813 The @option{--enable-threads} options isn't supported yet. A patch is
1814 in preparation for a future release.
1816 GCC writes a @samp{.verstamp} directive to the assembler output file
1817 unless it is built as a cross-compiler. It gets the version to use from
1818 the system header file @file{/usr/include/stamp.h}. If you install a
1819 new version of DEC Unix, you should rebuild GCC to pick up the new version
1822 Note that since the Alpha is a 64-bit architecture, cross-compilers from
1823 32-bit machines will not generate code as efficient as that generated
1824 when the compiler is running on a 64-bit machine because many
1825 optimizations that depend on being able to represent a word on the
1826 target in an integral value on the host cannot be performed. Building
1827 cross-compilers on the Alpha for 32-bit machines has only been tested in
1828 a few cases and may not work properly.
1830 @code{make compare} may fail on old versions of DEC Unix unless you add
1831 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
1832 assembler input file is stored in the object file, and that makes
1833 comparison fail if it differs between the @code{stage1} and
1834 @code{stage2} compilations. The option @option{-save-temps} forces a
1835 fixed name to be used for the assembler input file, instead of a
1836 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
1837 unless the comparisons fail without that option. If you add
1838 @option{-save-temps}, you will have to manually delete the @samp{.i} and
1839 @samp{.s} files after each series of compilations.
1841 GCC now supports both the native (ECOFF) debugging format used by DBX
1842 and GDB and an encapsulated STABS format for use only with GDB@. See the
1843 discussion of the @option{--with-stabs} option of @file{configure} above
1844 for more information on these formats and how to select them.
1846 There is a bug in DEC's assembler that produces incorrect line numbers
1847 for ECOFF format when the @samp{.align} directive is used. To work
1848 around this problem, GCC will not emit such alignment directives
1849 while writing ECOFF format debugging information even if optimization is
1850 being performed. Unfortunately, this has the very undesirable
1851 side-effect that code addresses when @option{-O} is specified are
1852 different depending on whether or not @option{-g} is also specified.
1854 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
1855 DBX@. DEC is now aware of this problem with the assembler and hopes to
1856 provide a fix shortly.
1862 @heading @anchor{alphaev5-cray-unicosmk*}alphaev5-cray-unicosmk*
1863 Cray T3E systems running Unicos/Mk.
1865 This port is incomplete and has many known bugs. We hope to improve the
1866 support for this target soon. Currently, only the C front end is supported,
1867 and it is not possible to build parallel applications. Cray modules are not
1868 supported; in particular, Craylibs are assumed to be in
1869 @file{/opt/ctl/craylibs/craylibs}.
1871 You absolutely @strong{must} use GNU make on this platform. Also, you
1872 need to tell GCC where to find the assembler and the linker. The
1873 simplest way to do so is by providing @option{--with-as} and
1874 @option{--with-ld} to @file{configure}, e.g.@:
1876 @samp{configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld
1877 --enable-languages=c}
1879 The comparison test during @samp{make bootstrap} fails on Unicos/Mk
1880 because the assembler inserts timestamps into object files. You should
1881 be able to work around this by doing @samp{make all} after getting this
1888 @heading @anchor{arc-*-elf}arc-*-elf
1889 Argonaut ARC processor.
1890 This configuration is intended for embedded systems.
1896 @heading @anchor{arm-*-aout}arm-*-aout
1897 Advanced RISC Machines ARM-family processors. These are often used in
1898 embedded applications. There are no standard Unix configurations.
1899 This configuration corresponds to the basic instruction sequences and will
1900 produce @file{a.out} format object modules.
1902 You may need to make a variant of the file @file{arm.h} for your particular
1909 @heading @anchor{arm-*-elf}arm-*-elf
1910 This configuration is intended for embedded systems.
1916 @heading @anchor{arm*-*-linux-gnu}arm*-*-linux-gnu
1918 We require GNU binutils 2.10 or newer.
1924 @heading @anchor{arm-*-riscix}arm-*-riscix
1925 The ARM2 or ARM3 processor running RISC iX, Acorn's port of BSD Unix.
1926 This configuration is obsoleted in GCC 3.1.
1928 If you are running a version of RISC iX prior to 1.2 then you must
1929 specify the version number during configuration. Note that the
1930 assembler shipped with RISC iX does not support stabs debugging
1931 information; a new version of the assembler, with stabs support
1932 included, is now available from Acorn and via ftp
1933 @uref{ftp://ftp.acorn.com/pub/riscix/as+xterm.tar.Z}. To enable stabs
1934 debugging, pass @option{--with-gnu-as} to configure.
1936 You will need to install GNU @command{sed} before you can run configure.
1942 @heading @anchor{avr}avr
1944 ATMEL AVR-family micro controllers. These are used in embedded
1945 applications. There are no standard Unix configurations.
1947 @xref{AVR Options,, AVR Options, gcc, Using and Porting the GNU Compiler
1951 See ``AVR Options'' in the main manual
1953 for the list of supported MCU types.
1955 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
1957 Further installation notes and other useful information about AVR tools
1958 can also be obtained from:
1962 @uref{http://home.overta.ru/users/denisc,,http://home.overta.ru/users/denisc}
1964 @uref{http://www.amelek.gda.pl/avr,,http://www.amelek.gda.pl/avr}
1967 We @emph{strongly} recommend using binutils 2.11 or newer.
1969 The following error:
1971 Error: register required
1974 indicates that you should upgrade to a newer version of the binutils.
1980 @heading @anchor{c4x}c4x
1982 Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal
1983 Processors. These are used in embedded applications. There are no
1984 standard Unix configurations.
1986 @xref{TMS320C3x/C4x Options,, TMS320C3x/C4x Options, gcc, Using and
1987 Porting the GNU Compiler Collection (GCC)},
1990 See ``TMS320C3x/C4x Options'' in the main manual
1992 for the list of supported MCU types.
1994 GCC can be configured as a cross compiler for both the C3x and C4x
1995 architectures on the same system. Use @samp{configure --target=c4x
1996 --enable-languages="c,c++"} to configure.
1999 Further installation notes and other useful information about C4x tools
2000 can also be obtained from:
2004 @uref{http://www.elec.canterbury.ac.nz/c4x/,,http://www.elec.canterbury.ac.nz/c4x/}
2011 @heading @anchor{cris}CRIS
2013 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
2014 series. These are used in embedded applications.
2017 @xref{CRIS Options,, CRIS Options, gcc, Using and Porting the GNU Compiler
2021 See ``CRIS Options'' in the main manual
2023 for a list of CRIS-specific options.
2025 There are a few different CRIS targets:
2027 @item cris-axis-aout
2028 Old target. Includes a multilib for the @samp{elinux} a.out-based
2029 target. No multilibs for newer architecture variants.
2031 Mainly for monolithic embedded systems. Includes a multilib for the
2032 @samp{v10} core used in @samp{ETRAX 100 LX}.
2033 @item cris-axis-linux-gnu
2034 A GNU/Linux port for the CRIS architecture, currently targeting
2035 @samp{ETRAX 100 LX} by default.
2038 For @code{cris-axis-aout} and @code{cris-axis-elf} you need binutils 2.11
2039 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
2041 Pre-packaged tools can be obtained from
2042 @uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More
2043 information about this platform is available at
2044 @uref{http://developer.axis.com/}.
2050 @heading @anchor{dos}DOS
2052 Please have a look at our @uref{binaries.html,,binaries page}.
2054 You cannot install GCC by itself on MSDOS; it will not compile under
2055 any MSDOS compiler except itself. You need to get the complete
2056 compilation package DJGPP, which includes binaries as well as sources,
2057 and includes all the necessary compilation tools and libraries.
2063 @heading @anchor{dsp16xx}dsp16xx
2064 A port to the AT&T DSP1610 family of processors.
2070 @heading @anchor{*-*-freebsd*}*-*-freebsd*
2072 The version of binutils installed in @file{/usr/bin} is known to work unless
2073 otherwise specified in any per-architecture notes. However, binutils
2074 2.12.1 or greater is known to improve overall testsuite results.
2076 For FreeBSD 1, FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
2077 configuration support and files as shipped with GCC 2.95 are still in
2078 place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
2079 it is unknown which version of binutils was used (it is assumed that it
2080 was the system copy in @file{/usr/bin}) and C++ EH failures were noted.
2082 Support for FreeBSD 1 is obsoleted in GCC 3.1.
2084 For FreeBSD using the ELF file format: DWARF 2 debugging is now the
2085 default for all CPU architectures. It had been the default on
2086 FreeBSD/alpha since its inception. You may use @option{-gstabs} instead
2087 of @option{-g}, if you really want the old debugging format. There are
2088 no known issues with mixing object files and libraries with different
2089 debugging formats. Otherwise, this release of GCC should now match more
2090 of the configuration used in the stock FreeBSD configuration of GCC. In
2091 particular, @option{--enable-threads} is now configured by default.
2092 However, as a general user, do not attempt to replace the system
2093 compiler with this release. Known to bootstrap and check with good
2094 results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4, 4.5-STABLE and 5-CURRENT@.
2096 In principle, @option{--enable-threads} is now compatible with
2097 @option{--enable-libgcj} on FreeBSD@. However, it has only been built
2098 and tested on i386-*-freebsd4.5 and alpha-*-freebsd5.0. The static
2099 library may be incorrectly built (symbols are missing at link time).
2100 There is a rare timing-based startup hang (probably involves an
2101 assupmtion about the thread library). Multi-threaded boehm-gc (required for
2102 libjava) exposes severe threaded signal-handling bugs on FreeBSD before
2103 4.5-RELEASE. The alpha port may not fully bootstrap without some manual
2104 intervention: gcjh will crash with a floating-point exception while
2105 generating @file{java/lang/Double.h} (just copy the version built on
2106 i386-*-freebsd* and rerun the top-level gmake with no arguments and it
2107 should properly complete the bootstrap). Other CPU architectures
2108 supported by FreeBSD will require additional configuration tuning in, at
2109 the very least, both boehm-gc and libffi.
2111 Shared @file{libgcc_s.so} is now built and installed by default.
2117 @heading @anchor{elxsi-elxsi-bsd}elxsi-elxsi-bsd
2118 The Elxsi's C compiler has known limitations that prevent it from
2119 compiling GCC@. Please contact @email{mrs@@wrs.com} for more details.
2121 Support for this processor is obsoleted in GCC 3.1.
2127 @heading @anchor{h8300-hms}h8300-hms
2128 Hitachi H8/300 series of processors.
2130 Please have a look at our @uref{binaries.html,,binaries page}.
2132 The calling convention and structure layout has changed in release 2.6.
2133 All code must be recompiled. The calling convention now passes the
2134 first three arguments in function calls in registers. Structures are no
2135 longer a multiple of 2 bytes.
2141 @heading @anchor{hppa*-hp-hpux*}hppa*-hp-hpux*
2143 We @emph{highly} recommend using gas/binutils 2.8 or newer on all hppa
2144 platforms; you may encounter a variety of problems when using the HP
2147 Specifically, @option{-g} does not work on HP-UX (since that system
2148 uses a peculiar debugging format which GCC does not know about), unless you
2149 use GAS and GDB and configure GCC with the
2150 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
2151 @option{--with-as=@dots{}} options.
2153 If you wish to use pa-risc 2.0 architecture support, you must use either
2154 the HP assembler, gas/binutils 2.11 or a recent
2155 @uref{ftp://sources.redhat.com/pub/binutils/snapshots,,snapshot of gas}.
2157 More specific information to @samp{hppa*-hp-hpux*} targets follows.
2163 @heading @anchor{hppa*-hp-hpux9}hppa*-hp-hpux9
2165 The HP assembler has major problems on this platform. We've tried to work
2166 around the worst of the problems. However, those workarounds may be causing
2167 linker crashes in some circumstances; the workarounds also probably prevent
2168 shared libraries from working. Use the GNU assembler to avoid these problems.
2171 The configuration scripts for GCC will also trigger a bug in the hpux9
2172 shell. To avoid this problem set @env{CONFIG_SHELL} to @file{/bin/ksh}
2173 and @env{SHELL} to @file{/bin/ksh} in your environment.
2180 @heading @anchor{hppa*-hp-hpux10}hppa*-hp-hpux10
2182 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
2183 @code{PHCO_19798} from HP@. HP has two sites which provide patches free of
2189 <a href="http://us-support.external.hp.com">US, Canada, Asia-Pacific, and
2193 @uref{http://us-support.external.hp.com,,}US, Canada, Asia-Pacific, and
2197 @uref{http://europe-support.external.hp.com,,Europe}
2200 The HP assembler on these systems is much better than the hpux9 assembler,
2201 but still has some problems. Most notably the assembler inserts timestamps
2202 into each object file it creates, causing the 3-stage comparison test to fail
2203 during a @samp{make bootstrap}. You should be able to continue by
2204 saying @samp{make all} after getting the failure from @samp{make
2212 @heading @anchor{hppa*-hp-hpux11}hppa*-hp-hpux11
2214 GCC 3.0 and up support HP-UX 11. You must use GNU binutils 2.11 or above on
2215 this platform. Thread support is not currently implemented for this
2216 platform, so @option{--enable-threads} does not work.
2217 See @uref{http://gcc.gnu.org/ml/gcc-prs/2002-01/msg00551.html}
2218 and @uref{http://gcc.gnu.org/ml/gcc-bugs/2002-01/msg00663.html}.
2219 GCC 2.95.x is not supported under HP-UX 11 and cannot be used to
2220 compile GCC 3.0 and up. Refer to @uref{binaries.html,,binaries} for
2221 information about obtaining precompiled GCC binaries for HP-UX.
2227 @heading @anchor{i370-*-*}i370-*-*
2228 This port is very preliminary and has many known bugs. We hope to
2229 have a higher-quality port for this machine soon.
2235 @heading @anchor{*-*-linux-gnu}*-*-linux-gnu
2237 If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install
2238 out-of-the-box. You'll get compile errors while building @samp{libstdc++}.
2239 The patch @uref{glibc-2.2.patch,,glibc-2.2.patch}, that is to be
2240 applied in the GCC source tree, fixes the compatibility problems.
2250 Currently Glibc 2.2.3 (and older releases) and GCC 3.0 are out of sync
2251 since the latest exception handling changes for GCC@. Compiling glibc
2252 with GCC 3.0 will give a binary incompatible glibc and therefore cause
2253 lots of problems and might make your system completly unusable. This
2254 will definitly need fixes in glibc but might also need fixes in GCC@. We
2255 strongly advise to wait for glibc 2.2.4 and to read the release notes of
2256 glibc 2.2.4 whether patches for GCC 3.0 are needed. You can use glibc
2257 2.2.3 with GCC 3.0, just do not try to recompile it.
2263 @heading @anchor{ix86-*-linux*oldld}i?86-*-linux*oldld
2264 Use this configuration to generate @file{a.out} binaries on Linux-based
2265 GNU systems if you do not have gas/binutils version 2.5.2 or later
2268 This configuration is obsoleted in GCC 3.1.
2274 @heading @anchor{ix86-*-linux*aout}i?86-*-linux*aout
2275 Use this configuration to generate @file{a.out} binaries on Linux-based
2276 GNU systems. This configuration is being superseded. You must use
2277 gas/binutils version 2.5.2 or later.
2283 @heading @anchor{ix86-*-linux*}i?86-*-linux*
2285 You will need binutils 2.9.1.0.15 or newer for exception handling to work.
2287 If you receive Signal 11 errors when building on GNU/Linux, then it is
2288 possible you have a hardware problem. Further information on this can be
2289 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
2295 @heading @anchor{ix86-*-sco}i?86-*-sco
2296 Compilation with RCC is recommended. Also, it may be a good idea to
2297 link with GNU malloc instead of the malloc that comes with the system.
2303 @heading @anchor{ix86-*-sco3.2v4}i?86-*-sco3.2v4
2304 Use this configuration for SCO release 3.2 version 4.
2310 @heading @anchor{ix86-*-sco3.2v5*}i?86-*-sco3.2v5*
2311 Use this for the SCO OpenServer Release 5 family of operating systems.
2313 Unlike earlier versions of GCC, the ability to generate COFF with this
2314 target is no longer provided.
2316 Earlier versions of GCC emitted DWARF 1 when generating ELF to allow
2317 the system debugger to be used. That support was too burdensome to
2318 maintain. GCC now emits only DWARF 2 for this target. This means you
2319 may use either the UDK debugger or GDB to debug programs built by this
2322 Use of the @option{-march=pentiumpro} flag can result in
2323 unrecognized opcodes when using the native assembler on OS versions before
2324 5.0.6. (Support for P6 opcodes was added to the native ELF assembler in
2325 that version.) While it's rather rare to see these emitted by GCC yet,
2326 errors of the basic form:
2329 /usr/tmp/ccaNlqBc.s:22:unknown instruction: fcomip
2330 /usr/tmp/ccaNlqBc.s:50:unknown instruction: fucomip
2333 are symptoms of this problem. You may work around this by not
2334 building affected files with that flag, by using the GNU assembler, or
2335 by using the assembler provided with the current version of the OS@.
2336 Users of GNU assembler should see the note below for hazards on doing
2339 The native SCO assembler that is provided with the OS at no
2340 charge is normally required. If, however, you must be able to use
2341 the GNU assembler (perhaps you're compiling code with asms that
2342 require GAS syntax) you may configure this package using the flags
2343 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You must
2344 use a recent version of GNU binutils; versions past 2.9.1 seem to work
2347 In general, the @option{--with-gnu-as} option isn't as well tested
2348 as the native assembler.
2350 Look in @file{gcc/config/i386/sco5.h} (search for ``messy'') for
2351 additional OpenServer-specific flags.
2353 Systems based on OpenServer before 5.0.4 (@samp{uname -X}
2354 will tell you what you're running) require TLS597 from
2355 @uref{ftp://ftp.sco.com/TLS/,,ftp://ftp.sco.com/TLS/}
2356 for C++ constructors and destructors to work right.
2358 The system linker in (at least) 5.0.4 and 5.0.5 will sometimes
2359 do the wrong thing for a construct that GCC will emit for PIC
2360 code. This can be seen as execution testsuite failures when using
2361 @option{-fPIC} on @file{921215-1.c}, @file{931002-1.c}, @file{nestfunc-1.c}, and @file{gcov-1.c}.
2362 For 5.0.5, an updated linker that will cure this problem is
2363 available. You must install both
2364 @uref{ftp://ftp.sco.com/Supplements/rs505a/,,ftp://ftp.sco.com/Supplements/rs505a/}
2365 and @uref{ftp://ftp.sco.com/SLS/,,OSS499A}.
2367 The dynamic linker in OpenServer 5.0.5 (earlier versions may show
2368 the same problem) aborts on certain G77-compiled programs. It's particularly
2369 likely to be triggered by building Fortran code with the @option{-fPIC} flag.
2370 Although it's conceivable that the error could be triggered by other
2371 code, only G77-compiled code has been observed to cause this abort.
2372 If you are getting core dumps immediately upon execution of your
2373 G77 program---and especially if it's compiled with @option{-fPIC}---try applying
2374 @uref{sco_osr5_g77.patch,,@file{sco_osr5_g77.patch}} to your @samp{libf2c} and
2376 Affected faults, when analyzed in a debugger, will show a stack
2377 backtrace with a fault occurring in @code{rtld()} and the program
2378 running as @file{/usr/lib/ld.so.1}. This problem has been reported to SCO
2379 engineering and will hopefully be addressed in later releases.
2386 @heading @anchor{ix86-*-udk}i?86-*-udk
2388 This target emulates the SCO Universal Development Kit and requires that
2389 package be installed. (If it is installed, you will have a
2390 @file{/udk/usr/ccs/bin/cc} file present.) It's very much like the
2391 @samp{i?86-*-unixware7*} target
2392 but is meant to be used when hosting on a system where UDK isn't the
2393 default compiler such as OpenServer 5 or Unixware 2. This target will
2394 generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
2395 with the same warnings and caveats as the SCO UDK@.
2397 This target is a little tricky to build because we have to distinguish
2398 it from the native tools (so it gets headers, startups, and libraries
2399 from the right place) while making the tools not think we're actually
2400 building a cross compiler. The easiest way to do this is with a configure
2403 @samp{CC=/udk/usr/ccs/bin/cc @var{/your/path/to}/gcc/configure
2404 --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-}
2406 @emph{You should substitute @samp{i686} in the above command with the appropriate
2407 processor for your host.}
2409 After the usual @samp{make bootstrap} and
2410 @samp{make install}, you can then access the UDK-targeted GCC
2411 tools by adding @command{udk-} before the commonly known name. For
2412 example, to invoke the C compiler, you would use @command{udk-gcc}.
2413 They will coexist peacefully with any native-target GCC tools you may
2421 @heading @anchor{ix86-*-isc}i?86-*-isc
2422 This configuration is obsoleted in GCC 3.1.
2424 It may be a good idea to link with GNU malloc instead of the malloc that
2425 comes with the system.
2427 In ISC version 4.1, @command{sed} core dumps when building
2428 @file{deduced.h}. Use the version of @command{sed} from version 4.0.
2434 @heading @anchor{ix86-ibm-aix}i?86-ibm-aix
2435 This configuration is obsoleted in GCC 3.1.
2437 You need to use GAS version 2.1 or later, and LD from
2438 GNU binutils version 2.2 or later.
2444 @heading @anchor{ix86-sequent-bsd}i?86-sequent-bsd
2445 This configuration is obsoleted in GCC 3.1.
2447 Go to the Berkeley universe before compiling.
2453 @heading @anchor{ix86-sequent-ptx1*}i?86-sequent-ptx1*, i?86-sequent-ptx2*, i?86-sequent-sysv3*
2454 This configuration is obsoleted in GCC 3.1.
2456 You must install GNU @command{sed} before running @command{configure}.
2458 The @code{fixproto} shell script may trigger a bug in the system shell.
2459 If you encounter this problem, upgrade your operating system or
2460 use @command{bash} (the GNU shell) to run @code{fixproto}.
2466 @heading @anchor{i860-intel-osf*}i860-intel-osf*
2467 All support for the i860 processor is obsoleted in GCC 3.1.
2469 On the Intel Paragon (an i860 machine), if you are using operating
2470 system version 1.0, you will get warnings or errors about redefinition
2471 of @code{va_arg} when you build GCC@.
2473 If this happens, then you need to link most programs with the library
2474 @file{iclib.a}. You must also modify @file{stdio.h} as follows: before
2478 #if defined(__i860__) && !defined(_VA_LIST)
2479 #include <va_list.h>
2493 extern int vprintf(const char *, va_list );
2494 extern int vsprintf(char *, const char *, va_list );
2502 #endif /* __PGC__ */
2505 These problems don't exist in operating system version 1.1.
2511 @heading @anchor{ia64-*-linux}ia64-*-linux
2512 IA-64 processor (also known as IPF, or Itanium Processor Family)
2515 The toolchain is not completely finished, so requirements will continue
2517 GCC 3.0.1 and later require glibc 2.2.4.
2518 GCC 3.0.2 requires binutils from 2001-09-05 or later.
2519 GCC 3.0.1 requires binutils 2.11.1 or later.
2521 None of the following versions of GCC has an ABI that is compatible
2522 with any of the other versions in this list, with the exception that
2523 Red Hat 2.96 and Trillian 000171 are compatible with each other:
2524 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
2525 This primarily affects C++ programs and programs that create shared libraries.
2526 Because of these ABI incompatibilities, GCC 3.0.2 is not recommended for
2527 user programs on GNU/Linux systems built using earlier compiler releases.
2528 GCC 3.0.2 is recommended for compiling linux, the kernel.
2529 GCC 3.0.2 is believed to be fully ABI compliant, and hence no more major
2530 ABI changes are expected.
2536 @heading @anchor{*-lynx-lynxos}*-lynx-lynxos
2537 LynxOS 2.2 and earlier comes with GCC 1.x already installed as
2538 @file{/bin/gcc}. You should compile with this instead of @file{/bin/cc}.
2539 You can tell GCC to use the GNU assembler and linker, by specifying
2540 @samp{--with-gnu-as --with-gnu-ld} when configuring. These will produce
2541 COFF format object files and executables; otherwise GCC will use the
2542 installed tools, which produce @file{a.out} format executables.
2547 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
2549 @heading @anchor{*-ibm-aix*}*-ibm-aix*
2551 AIX Make frequently has problems with GCC makefiles. GNU Make 3.76 or
2552 newer is recommended to build on this platform.
2554 Errors involving @code{alloca} when building GCC generally are due
2555 to an incorrect definition of @code{CC} in the Makefile or mixing files
2556 compiled with the native C compiler and GCC@. During the stage1 phase of
2557 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
2558 (not @command{xlc}). Once @command{configure} has been informed of
2559 @command{xlc}, one needs to use @samp{make distclean} to remove the
2560 configure cache files and ensure that @env{CC} environment variable
2561 does not provide a definition that will confuse @command{configure}.
2562 If this error occurs during stage2 or later, then the problem most likely
2563 is the version of Make (see above).
2565 The GNU Assembler incorrectly reports that it supports WEAK symbols on
2566 AIX which causes GCC to try to utilize weak symbol functionality which
2567 is not really supported on the platform. The native @command{as} and
2568 @command{ld} still are recommended. The native AIX tools do
2569 interoperate with GCC@.
2571 Building @file{libstdc++.a} requires a fix for a AIX Assembler bug
2572 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1).
2574 Linking executables and shared libraries may produce warnings of
2575 duplicate symbols. The assembly files generated by GCC for AIX always
2576 have included multiple symbol definitions for certain global variable
2577 and function declarations in the original program. The warnings should
2578 not prevent the linker from producing a correct library or runnable
2581 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
2582 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
2583 to parse archive libraries did not handle the new format correctly.
2584 These routines are used by GCC and result in error messages during
2585 linking such as ``not a COFF file''. The version of the routines shipped
2586 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
2587 option of the archive command may be used to create archives of 32-bit
2588 objects using the original ``small format''. A correct version of the
2589 routines is shipped with AIX 4.3.2 and above.
2591 Some versions of the AIX binder (linker) can fail with a relocation
2592 overflow severe error when the @option{-bbigtoc} option is used to link
2593 GCC-produced object files into an executable that overflows the TOC@. A fix
2594 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
2595 available from IBM Customer Support and from its
2596 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2597 website as PTF U455193.
2599 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
2600 with a segmentation fault when invoked by any version of GCC@. A fix for
2601 APAR IX87327 is available from IBM Customer Support and from its
2602 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2603 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
2605 The initial assembler shipped with AIX 4.3.0 generates incorrect object
2606 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
2607 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
2608 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2609 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
2611 AIX provides National Language Support (NLS)@. Compilers and assemblers
2612 use NLS to support locale-specific representations of various data
2613 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
2614 separating decimal fractions). There have been problems reported where
2615 GCC does not produce the same floating-point formats that the assembler
2616 expects. If one encounters this problem, set the @env{LANG}
2617 environment variable to @samp{C} or @samp{En_US}.
2619 By default, GCC for AIX 4.1 and above produces code that can be used on
2620 both Power or PowerPC processors.
2622 A default can be specified with the @option{-mcpu=@var{cpu_type}}
2623 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
2629 @heading @anchor{m32r-*-elf}m32r-*-elf
2630 Mitsubishi M32R processor.
2631 This configuration is intended for embedded systems.
2637 @heading @anchor{m68000-hp-bsd}m68000-hp-bsd
2638 HP 9000 series 200 running BSD@. Note that the C compiler that comes
2639 with this system cannot compile GCC; contact @email{law@@cygnus.com}
2640 to get binaries of GCC for bootstrapping.
2646 @heading @anchor{m6811-elf}m6811-elf
2647 Motorola 68HC11 family micro controllers. These are used in embedded
2648 applications. There are no standard Unix configurations.
2654 @heading @anchor{m6812-elf}m6812-elf
2655 Motorola 68HC12 family micro controllers. These are used in embedded
2656 applications. There are no standard Unix configurations.
2662 @heading @anchor{m68k-altos}m68k-altos
2663 Altos 3068. This configuration is obsoleted in GCC 3.1.
2665 You must use the GNU assembler, linker and debugger.
2666 Also, you must fix a kernel bug.
2672 @heading @anchor{m68k-apple-aux}m68k-apple-aux
2673 Apple Macintosh running A/UX@.
2674 This configuration is obsoleted in GCC 3.1.
2676 You may configure GCC to use either the system assembler and
2677 linker or the GNU assembler and linker. You should use the GNU configuration
2678 if you can, especially if you also want to use G++. You enable
2679 that configuration with the @option{--with-gnu-as} and @option{--with-gnu-ld}
2680 options to @code{configure}.
2682 Note the C compiler that comes
2683 with this system cannot compile GCC@. You can find binaries of GCC
2684 for bootstrapping on @code{jagubox.gsfc.nasa.gov}.
2685 You will also a patched version of @file{/bin/ld} there that
2686 raises some of the arbitrary limits found in the original.
2692 @heading @anchor{m68k-att-sysv}m68k-att-sysv
2693 AT&T 3b1, a.k.a.@: 7300 PC@. This version of GCC cannot
2694 be compiled with the system C compiler, which is too buggy.
2695 You will need to get a previous version of GCC and use it to
2696 bootstrap. Binaries are available from the OSU-CIS archive, at
2697 @uref{ftp://archive.cis.ohio-state.edu/pub/att7300/}.
2703 @heading @anchor{m68k-bull-sysv}m68k-bull-sysv
2704 Bull DPX/2 series 200 and 300 with BOS-2.00.45 up to BOS-2.01.
2705 This configuration is obsoleted in GCC 3.1.
2708 either with native assembler or GNU assembler. You can use
2709 GNU assembler with native COFF generation by providing @option{--with-gnu-as} to
2710 the configure script or use GNU assembler with stabs-in-COFF encapsulation
2711 by providing @samp{--with-gnu-as --stabs}. For any problem with the native
2712 assembler or for availability of the DPX/2 port of GAS, contact
2713 @email{F.Pierresteguy@@frcl.bull.fr}.
2719 @heading @anchor{m68k-crds-unos}m68k-crds-unos
2720 Use @samp{configure unos} for building on Unos.
2722 The Unos assembler is named @code{casm} instead of @code{as}. For some
2723 strange reason linking @file{/bin/as} to @file{/bin/casm} changes the
2724 behavior, and does not work. So, when installing GCC, you should
2725 install the following script as @file{as} in the subdirectory where
2726 the passes of GCC are installed:
2733 The default Unos library is named @file{libunos.a} instead of
2734 @file{libc.a}. To allow GCC to function, either change all
2735 references to @option{-lc} in @file{gcc.c} to @option{-lunos} or link
2736 @file{/lib/libc.a} to @file{/lib/libunos.a}.
2738 @cindex @code{alloca}, for Unos
2739 When compiling GCC with the standard compiler, to overcome bugs in
2740 the support of @code{alloca}, do not use @option{-O} when making stage 2.
2741 Then use the stage 2 compiler with @option{-O} to make the stage 3
2742 compiler. This compiler will have the same characteristics as the usual
2743 stage 2 compiler on other systems. Use it to make a stage 4 compiler
2744 and compare that with stage 3 to verify proper compilation.
2746 (Perhaps simply defining @code{ALLOCA} in @file{x-crds} as described in
2747 the comments there will make the above paragraph superfluous. Please
2748 inform us of whether this works.)
2750 Unos uses memory segmentation instead of demand paging, so you will need
2751 a lot of memory. 5 Mb is barely enough if no other tasks are running.
2752 If linking @file{cc1} fails, try putting the object files into a library
2753 and linking from that library.
2759 @heading @anchor{m68k-hp-hpux}m68k-hp-hpux
2760 HP 9000 series 300 or 400 running HP-UX@. HP-UX version 8.0 has a bug in
2761 the assembler that prevents compilation of GCC@. This
2762 bug manifests itself during the first stage of compilation, while
2763 building @file{libgcc2.a}:
2767 cc1: warning: `-g' option not supported on this version of GCC
2768 cc1: warning: `-g1' option not supported on this version of GCC
2769 ./xgcc: Internal compiler error: program as got fatal signal 11
2772 A patched version of the assembler is available as the file
2773 @uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you
2774 have HP software support, the patch can also be obtained directly from
2775 HP, as described in the following note:
2778 This is the patched assembler, to patch SR#1653-010439, where the
2779 assembler aborts on floating point constants.
2781 The bug is not really in the assembler, but in the shared library
2782 version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is
2783 SR#4701-078451. Anyway, the attached assembler uses the archive
2784 library version of ``cvtnum(3c)'' and thus does not exhibit the bug.
2787 This patch is also known as PHCO_4484.
2789 In addition, if you wish to use gas, you must use
2790 gas version 2.1 or later, and you must use the GNU linker version 2.1 or
2791 later. Earlier versions of gas relied upon a program which converted the
2792 gas output into the native HP-UX format, but that program has not been
2793 kept up to date. gdb does not understand that native HP-UX format, so
2794 you must use gas if you wish to use gdb.
2796 On HP-UX version 8.05, but not on 8.07 or more recent versions, the
2797 @code{fixproto} shell script triggers a bug in the system shell. If you
2798 encounter this problem, upgrade your operating system or use BASH (the
2799 GNU shell) to run @code{fixproto}. This bug will cause the fixproto
2800 program to report an error of the form:
2803 ./fixproto: sh internal 1K buffer overflow
2806 To fix this, you can also change the first line of the fixproto script
2818 @heading @anchor{m68k-*-nextstep*}m68k-*-nextstep*
2819 These configurations are obsoleted in GCC 3.1.
2821 Current GCC versions probably do not work on version 2 of the NeXT
2824 On NeXTStep 3.0, the Objective-C compiler does not work, due,
2825 apparently, to a kernel bug that it happens to trigger. This problem
2826 does not happen on 3.1.
2828 You absolutely @strong{must} use GNU sed and GNU make on this platform.
2831 On NeXTSTEP 3.x where x < 3 the build of GCC will abort during
2832 stage1 with an error message like this:
2836 /usr/tmp/ccbbsZ0U.s:987:Unknown pseudo-op: .section
2837 /usr/tmp/ccbbsZ0U.s:987:Rest of line ignored. 1st junk character
2841 The reason for this is the fact that NeXT's assembler for these
2842 versions of the operating system does not support the @samp{.section}
2843 pseudo op that's needed for full C++ exception functionality.
2845 As NeXT's assembler is a derived work from GNU as, a free
2846 replacement that does can be obtained at
2847 @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}.
2849 If you try to build the integrated C++ & C++ runtime libraries on this system
2850 you will run into trouble with include files. The way to get around this is
2851 to use the following sequence. Note you must have write permission to
2852 the directory @var{prefix} you specified in the configuration process of GCC
2853 for this sequence to work.
2857 make all-texinfo all-bison all-byacc all-binutils all-gas all-ld
2860 make install-headers-tar
2869 @heading @anchor{m68k-ncr-*}m68k-ncr-*
2870 On the Tower models 4@var{n}0 and 6@var{n}0, by default a process is not
2871 allowed to have more than one megabyte of memory. GCC cannot compile
2872 itself (or many other programs) with @option{-O} in that much memory.
2874 To solve this problem, reconfigure the kernel adding the following line
2875 to the configuration file:
2886 @heading @anchor{m68k-sun}m68k-sun
2887 Sun 3. We do not provide a configuration file to use the Sun FPA by
2888 default, because programs that establish signal handlers for floating
2889 point traps inherently cannot work with the FPA@.
2895 @heading @anchor{m68k-sun-sunos4.1.1}m68k-sun-sunos4.1.1
2897 It is reported that you may need the GNU assembler on this platform.
2904 @heading @anchor{m88k-*-svr3}m88k-*-svr3
2905 Motorola m88k running the AT&T/Unisoft/Motorola V.3 reference port.
2906 These configurations are obsoleted in GCC 3.1.
2908 These systems tend to use the Green Hills C, revision 1.8.5, as the
2909 standard C compiler. There are apparently bugs in this compiler that
2910 result in object files differences between stage 2 and stage 3. If this
2911 happens, make the stage 4 compiler and compare it to the stage 3
2912 compiler. If the stage 3 and stage 4 object files are identical, this
2913 suggests you encountered a problem with the standard C compiler; the
2914 stage 3 and 4 compilers may be usable.
2916 It is best, however, to use an older version of GCC for bootstrapping
2923 @heading @anchor{m88k-*-dgux}m88k-*-dgux
2924 Motorola m88k running DG/UX@.
2925 These configurations are obsoleted in GCC 3.1.
2927 To build 88open BCS native or cross
2928 compilers on DG/UX, specify the configuration name as
2929 @samp{m88k-*-dguxbcs} and build in the 88open BCS software development
2930 environment. To build ELF native or cross compilers on DG/UX, specify
2931 @samp{m88k-*-dgux} and build in the DG/UX ELF development environment.
2932 You set the software development environment by issuing
2933 @samp{sde-target} command and specifying either @samp{m88kbcs} or
2934 @samp{m88kdguxelf} as the operand.
2936 If you do not specify a configuration name, @file{configure} guesses the
2937 configuration based on the current software development environment.
2943 @heading @anchor{m88k-tektronix-sysv3}m88k-tektronix-sysv3
2944 Tektronix XD88 running UTekV 3.2e.
2945 These configurations are obsoleted in GCC 3.1.
2948 optimization while building stage1 if you bootstrap with
2949 the buggy Green Hills compiler. Also, the bundled LAI
2950 System V NFS is buggy so if you build in an NFS mounted
2951 directory, start from a fresh reboot, or avoid NFS all together.
2952 Otherwise you may have trouble getting clean comparisons
2959 @heading @anchor{mips-*-*}mips-*-*
2960 If you use the 1.31 version of the MIPS assembler (such as was shipped
2961 with Ultrix 3.1), you will need to use the @option{-fno-delayed-branch} switch
2962 when optimizing floating point code. Otherwise, the assembler will
2963 complain when the GCC compiler fills a branch delay slot with a
2964 floating point instruction, such as @code{add.d}.
2966 If on a MIPS system you get an error message saying ``does not have gp
2967 sections for all it's [sic] sectons [sic]'', don't worry about it. This
2968 happens whenever you use GAS with the MIPS linker, but there is not
2969 really anything wrong, and it is okay to use the output file. You can
2970 stop such warnings by installing the GNU linker.
2972 It would be nice to extend GAS to produce the gp tables, but they are
2973 optional, and there should not be a warning about their absence.
2975 Users have reported some problems with version 2.0 of the MIPS
2976 compiler tools that were shipped with Ultrix 4.1. Version 2.10
2977 which came with Ultrix 4.2 seems to work fine.
2979 Users have also reported some problems with version 2.20 of the
2980 MIPS compiler tools that were shipped with RISC/os 4.x. The earlier
2981 version 2.11 seems to work fine.
2983 Some versions of the MIPS linker will issue an assertion failure
2984 when linking code that uses @code{alloca} against shared
2985 libraries on RISC-OS 5.0, and DEC's OSF/1 systems. This is a bug
2986 in the linker, that is supposed to be fixed in future revisions.
2987 To protect against this, GCC passes @option{-non_shared} to the
2988 linker unless you pass an explicit @option{-shared} or
2989 @option{-call_shared} switch.
2991 @heading @anchor{mips-mips-bsd}mips-mips-bsd
2992 MIPS machines running the MIPS operating system in BSD mode.
2993 These configurations are obsoleted in GCC 3.1.
2995 It's possible that some old versions of the system lack the functions
2996 @code{memcpy}, @code{memmove}, @code{memcmp}, and @code{memset}. If your
2997 system lacks these, you must remove or undo the definition of
2998 @code{TARGET_MEM_FUNCTIONS} in @file{mips-bsd.h}.
3000 If you use the MIPS C compiler to bootstrap, it may be necessary
3001 to increase its table size for switch statements with the
3002 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
3003 optimization option, you also need to use @option{-Olimit 3000}.
3004 Both of these options are automatically generated in the
3005 @file{Makefile} that the shell script @file{configure} builds.
3006 If you override the @code{CC} make variable and use the MIPS
3007 compilers, you may need to add @option{-Wf,-XNg1500 -Olimit 3000}.
3013 @heading @anchor{mips-dec-*}mips-dec-*
3014 These configurations are obsoleted in GCC 3.1.
3016 MIPS-based DECstations can support three different personalities:
3017 Ultrix, DEC OSF/1, and OSF/rose. (Alpha-based DECstation products have
3018 a configuration name beginning with @samp{alpha*-dec}.) To configure GCC
3019 for these platforms use the following configurations:
3022 @item mips-dec-ultrix
3023 Ultrix configuration.
3026 DEC's version of OSF/1.
3028 @item mips-dec-osfrose
3029 Open Software Foundation reference port of OSF/1 which uses the
3030 OSF/rose object file format instead of ECOFF@. Normally, you
3031 would not select this configuration.
3034 If you use the MIPS C compiler to bootstrap, it may be necessary
3035 to increase its table size for switch statements with the
3036 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
3037 optimization option, you also need to use @option{-Olimit 3000}.
3038 Both of these options are automatically generated in the
3039 @file{Makefile} that the shell script @file{configure} builds.
3040 If you override the @code{CC} make variable and use the MIPS
3041 compilers, you may need to add @option{-Wf,-XNg1500 -Olimit 3000}.
3047 @heading @anchor{mips-mips-riscos*}mips-mips-riscos*
3048 These configurations are obsoleted in GCC 3.1.
3050 If you use the MIPS C compiler to bootstrap, it may be necessary
3051 to increase its table size for switch statements with the
3052 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
3053 optimization option, you also need to use @option{-Olimit 3000}.
3054 Both of these options are automatically generated in the
3055 @file{Makefile} that the shell script @file{configure} builds.
3056 If you override the @code{CC} make variable and use the MIPS
3057 compilers, you may need to add @samp{-Wf,-XNg1500 -Olimit 3000}.
3059 MIPS computers running RISC-OS can support four different
3060 personalities: default, BSD 4.3, System V.3, and System V.4
3061 (older versions of RISC-OS don't support V.4). To configure GCC
3062 for these platforms use the following configurations:
3065 @item mips-mips-riscos@var{rev}
3066 Default configuration for RISC-OS, revision @var{rev}.
3068 @item mips-mips-riscos@var{rev}bsd
3069 BSD 4.3 configuration for RISC-OS, revision @var{rev}.
3071 @item mips-mips-riscos@var{rev}sysv4
3072 System V.4 configuration for RISC-OS, revision @var{rev}.
3078 @item mips-mips-riscos@var{rev}sysv
3079 System V.3 configuration for RISC-OS, revision @var{rev}.
3082 The revision @code{rev} mentioned above is the revision of
3083 RISC-OS to use. You must reconfigure GCC when going from a
3084 RISC-OS revision 4 to RISC-OS revision 5. This has the effect of
3085 avoiding a linker bug.
3091 @heading @anchor{mips-sgi-irix4}mips-sgi-irix4
3092 This configuration is obsoleted in GCC 3.1.
3094 In order to compile GCC on an SGI running IRIX 4, the ``c.hdr.lib''
3095 option must be installed from the CD-ROM supplied from Silicon Graphics.
3096 This is found on the 2nd CD in release 4.0.1.
3098 On IRIX version 4.0.5F, and perhaps on some other versions as well,
3099 there is an assembler bug that reorders instructions incorrectly. To
3100 work around it, specify the target configuration
3101 @samp{mips-sgi-irix4loser}. This configuration inhibits assembler
3104 In a compiler configured with target @samp{mips-sgi-irix4}, you can turn
3105 off assembler optimization by using the @option{-noasmopt} option. This
3106 compiler option passes the option @option{-O0} to the assembler, to
3109 The @option{-noasmopt} option can be useful for testing whether a problem
3110 is due to erroneous assembler reordering. Even if a problem does not go
3111 away with @option{-noasmopt}, it may still be due to assembler
3112 reordering---perhaps GCC itself was miscompiled as a result.
3114 You may get the following warning on IRIX 4 platforms, it can be safely
3117 warning: foo.o does not have gp tables for all its sections.
3124 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
3126 This configuration has considerable problems, which will be fixed in a
3129 In order to compile GCC on an SGI running IRIX 5, the ``compiler_dev.hdr''
3130 subsystem must be installed from the IDO CD-ROM supplied by Silicon
3131 Graphics. It is also available for download from
3132 @uref{http://www.sgi.com/developers/devtools/apis/ido.html,,http://www.sgi.com/developers/devtools/apis/ido.html}.
3134 @code{make compare} may fail on version 5 of IRIX unless you add
3135 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
3136 assembler input file is stored in the object file, and that makes
3137 comparison fail if it differs between the @code{stage1} and
3138 @code{stage2} compilations. The option @option{-save-temps} forces a
3139 fixed name to be used for the assembler input file, instead of a
3140 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
3141 unless the comparisons fail without that option. If you do you
3142 @option{-save-temps}, you will have to manually delete the @samp{.i} and
3143 @samp{.s} files after each series of compilations.
3145 If you use the MIPS C compiler to bootstrap, it may be necessary
3146 to increase its table size for switch statements with the
3147 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
3148 optimization option, you also need to use @option{-Olimit 3000}.
3150 To enable debugging under IRIX 5, you must use GNU @command{as} 2.11.2
3152 and use the @option{--with-gnu-as} configure option when configuring GCC.
3153 GNU @command{as} is distributed as part of the binutils package.
3154 When using release 2.11.2, you need to apply a patch
3155 @uref{http://sources.redhat.com/ml/binutils/2001-07/msg00352.html,,http://sources.redhat.com/ml/binutils/2001-07/msg00352.html}
3156 which will be included in the next release of binutils.
3158 When building GCC, the build process loops rebuilding @command{cc1} over
3159 and over again. This happens on @samp{mips-sgi-irix5.2}, and possibly
3160 other platforms. It has been reported that this is a known bug in the
3161 @command{make} shipped with IRIX 5.2. We recommend you use GNU
3162 @command{make} instead of the vendor supplied @command{make} program;
3163 however, you may have success with @command{smake} on IRIX 5.2 if you do
3164 not have GNU @command{make} available.
3170 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
3172 If you are using IRIX @command{cc} as your bootstrap compiler, you must
3173 ensure that the N32 ABI is in use. To test this, compile a simple C
3174 file with @command{cc} and then run @command{file} on the
3175 resulting object file. The output should look like:
3178 test.o: ELF N32 MSB @dots{}
3184 test.o: ELF 32-bit MSB @dots{}
3190 test.o: ELF 64-bit MSB @dots{}
3193 then your version of @command{cc} uses the O32 or N64 ABI by default. You
3194 should set the environment variable @env{CC} to @samp{cc -n32}
3195 before configuring GCC@.
3197 GCC on IRIX 6 is usually built to support both the N32 and N64 ABIs. If
3198 you build GCC on a system that doesn't have the N64 libraries installed,
3199 you need to configure with @option{--disable-multilib} so GCC doesn't
3200 try to use them. Look for @file{/usr/lib64/libc.so.1} to see if you
3201 have the 64-bit libraries installed.
3203 You must @emph{not} use GNU @command{as} (which isn't built anyway as of
3204 binutils 2.11.2) on IRIX 6 platforms; doing so will only cause problems.
3206 GCC does not currently support generating O32 ABI binaries in the
3207 @samp{mips-sgi-irix6} configurations. It is possible to create a GCC
3208 with O32 ABI only support by configuring it for the @samp{mips-sgi-irix5}
3209 target and using a patched GNU @command{as} 2.11.2 as documented in the
3210 @uref{#mips-sgi-irix5,,@samp{mips-sgi-irix5}} section above. Using the
3211 native assembler requires patches to GCC which will be included in a
3212 future release. It is
3213 expected that O32 ABI support will be available again in a future release.
3215 The @option{--enable-threads} option doesn't currently work, a patch is
3216 in preparation for a future release. The @option{--enable-libgcj}
3217 option is disabled by default: IRIX 6 uses a very low default limit
3218 (20480) for the command line length. Although libtool contains a
3219 workaround for this problem, at least the N64 @samp{libgcj} is known not
3220 to build despite this, running into an internal error of the native
3221 @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
3222 its maximum of 262144 bytes. If you have root access, you can use the
3223 @command{systune} command to do this.
3225 GCC does not correctly pass/return structures which are
3226 smaller than 16 bytes and which are not 8 bytes. The problem is very
3227 involved and difficult to fix. It affects a number of other targets also,
3228 but IRIX 6 is affected the most, because it is a 64 bit target, and 4 byte
3229 structures are common. The exact problem is that structures are being padded
3230 at the wrong end, e.g.@: a 4 byte structure is loaded into the lower 4 bytes
3231 of the register when it should be loaded into the upper 4 bytes of the
3234 GCC is consistent with itself, but not consistent with the SGI C compiler
3235 (and the SGI supplied runtime libraries), so the only failures that can
3236 happen are when there are library functions that take/return such
3237 structures. There are very few such library functions. Currently this
3238 is known to affect @code{inet_ntoa}, @code{inet_lnaof},
3239 @code{inet_netof}, @code{inet_makeaddr}, and @code{semctl}. Until the
3240 bug is fixed, GCC contains workarounds for the known affected functions.
3242 See @uref{http://freeware.sgi.com/,,http://freeware.sgi.com/} for more
3243 information about using GCC on IRIX platforms.
3249 @heading @anchor{mips-sony-sysv}mips-sony-sysv
3250 Sony MIPS NEWS@. This configuration is obsoleted in GCC 3.1.
3252 This works in NEWSOS 5.0.1, but not in 5.0.2 (which uses ELF instead of
3253 COFF)@. In particular, the linker does not like the code generated by
3254 GCC when shared libraries are linked in.
3260 @heading @anchor{ns32k-encore}ns32k-encore
3261 This configuration is obsoleted in GCC 3.1.
3263 Encore ns32000 system. Encore systems are supported only under BSD@.
3269 @heading @anchor{ns32k-*-genix}ns32k-*-genix
3270 National Semiconductor ns32000 system. This configuration is obsoleted
3273 Genix has bugs in @code{alloca} and @code{malloc}; you must get the
3274 compiled versions of these from GNU Emacs.
3280 @heading @anchor{ns32k-sequent}ns32k-sequent
3281 This configuration is obsoleted in GCC 3.1.
3283 Go to the Berkeley universe before compiling.
3289 @heading @anchor{ns32k-utek}ns32k-utek
3290 UTEK ns32000 system (``merlin''). This configuration is obsoleted in
3293 The C compiler that comes with this system cannot compile GCC; contact
3294 @samp{tektronix!reed!mason} to get binaries of GCC for bootstrapping.
3301 @heading @anchor{powerpc*-*-*}powerpc-*-*
3303 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
3304 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
3310 @heading @anchor{powerpc-*-darwin*}powerpc-*-darwin*
3311 PowerPC running Darwin (Mac OS X kernel).
3313 GCC 3.0 does not support Darwin, but 3.1 and later releases will work.
3315 Pre-installed versions of Mac OS X may not include any developer tools,
3316 meaning that you will not be able to build GCC from source. Tool
3317 binaries are available at
3318 @uref{http://www.opensource.apple.com/projects/darwin} (free
3319 registration required).
3321 Versions of the assembler prior to ``cctools-364'' cannot handle the
3322 4-argument form of rlwinm and related mask-using instructions. Darwin
3323 1.3 (Mac OS X 10.0) uses cctools-353 for instance. To get cctools-364,
3324 check out @file{cctools} with tag @samp{Apple-364}, build it, and
3325 install the assembler as @file{usr/bin/as}. See
3326 @uref{http://www.opensource.apple.com/tools/cvs/docs.html} for details.
3328 Also, the default stack limit of 512K is too small, and a bootstrap will
3329 typically fail when self-compiling @file{expr.c}. Set the stack to 800K
3330 or more, for instance by doing @samp{limit stack 800}. It's also
3331 convenient to use the GNU preprocessor instead of Apple's during the
3332 first stage of bootstrapping; this is automatic when doing @samp{make
3333 bootstrap}, but to do it from the toplevel objdir you will need to say
3334 @samp{make CC='cc -no-cpp-precomp' bootstrap}.
3336 Note that the version of GCC shipped by Apple typically includes a
3337 number of extensions not available in a standard GCC release. These
3338 extensions are generally specific to Mac programming.
3344 @heading @anchor{powerpc-*-elf}powerpc-*-elf, powerpc-*-sysv4
3345 PowerPC system in big endian mode, running System V.4.
3351 @heading @anchor{powerpc-*-linux-gnu*}powerpc-*-linux-gnu*
3354 @uref{ftp://ftp.varesearch.com/pub/support/hjl/binutils,,binutils 2.9.4.0.8}
3355 or newer for a working GCC@. It is strongly recommended to recompile binutils
3356 if you initially built it with gcc-2.7.2.x.
3362 @heading @anchor{powerpc-*-netbsd*}powerpc-*-netbsd*
3363 PowerPC system in big endian mode running NetBSD@. To build the
3364 documentation you will need Texinfo version 4.1 (NetBSD 1.5.1 included
3365 Texinfo version 3.12).
3371 @heading @anchor{powerpc-*-eabiaix}powerpc-*-eabiaix
3372 Embedded PowerPC system in big endian mode with @option{-mcall-aix} selected as
3379 @heading @anchor{powerpc-*-eabisim}powerpc-*-eabisim
3380 Embedded PowerPC system in big endian mode for use in running under the
3387 @heading @anchor{powerpc-*-eabi}powerpc-*-eabi
3388 Embedded PowerPC system in big endian mode.
3394 @heading @anchor{powerpcle-*-elf}powerpcle-*-elf, powerpcle-*-sysv4
3395 PowerPC system in little endian mode, running System V.4.
3401 @heading @anchor{powerpcle-*-eabisim}powerpcle-*-eabisim
3402 Embedded PowerPC system in little endian mode for use in running under
3409 @heading @anchor{powerpcle-*-eabi}powerpcle-*-eabi
3410 Embedded PowerPC system in little endian mode.
3416 @heading @anchor{powerpcle-*-winnt}powerpcle-*-winnt, powerpcle-*-pe
3417 PowerPC system in little endian mode running Windows NT@.
3423 @heading @anchor{romp-*-aos}romp-*-aos, romp-*-mach
3424 These configurations are obsoleted in GCC 3.1.
3426 We recommend you compile GCC with an earlier version of itself; if you
3427 compile GCC with @command{hc}, the Metaware compiler, it will work, but
3428 you will get mismatches between the stage 2 and stage 3 compilers in
3429 various files. These errors are minor differences in some
3430 floating-point constants and can be safely ignored; the stage 3 compiler
3437 @heading @anchor{s390-*-linux*}s390-*-linux*
3438 S/390 system running Linux for S/390@.
3444 @heading @anchor{s390x-*-linux*}s390x-*-linux*
3445 zSeries system (64 Bit) running Linux for zSeries@.
3451 @c Please use Solaris 2 to refer to all release of Solaris, starting
3452 @c with 2.0 until 2.6, 7, and 8. Solaris 1 was a marketing name for
3453 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
3454 @c alone is too unspecific and must be avoided.
3455 @heading @anchor{*-*-solaris2*}*-*-solaris2*
3457 Sun does not ship a C compiler with Solaris 2. To bootstrap and install
3458 GCC you first have to install a pre-built compiler, see our
3459 @uref{binaries.html,,binaries page} for details.
3461 The Solaris 2 @command{/bin/sh} will often fail to configure
3462 @file{libstdc++-v3}, @file{boehm-gc} or
3463 @file{libjava}. If you encounter this problem, set @env{CONFIG_SHELL} to
3464 @command{/bin/ksh} in your environment and run @command{make bootstrap} again.
3465 Another possibility that sometimes helps is to remove
3466 @file{*-*-solaris2*/config.cache}.
3468 Solaris 2 comes with a number of optional OS packages. Some of these
3469 packages are needed to use GCC fully, namely @code{SUNWarc},
3470 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
3471 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
3472 optional packages when installing Solaris 2, you will need to verify that
3473 the packages that GCC needs are installed.
3475 To check whether an optional package is installed, use
3476 the @command{pkginfo} command. To add an optional package, use the
3477 @command{pkgadd} command. For further details, see the Solaris 2
3480 Trying to use the linker and other tools in
3481 @file{/usr/ucb} to install GCC has been observed to cause trouble.
3482 For example, the linker may hang indefinitely. The fix is to remove
3483 @file{/usr/ucb} from your @env{PATH}.
3485 All releases of GNU binutils prior to 2.11.2 have known bugs on this
3486 platform. We recommend the use of GNU binutils 2.11.2 or the vendor
3487 tools (Sun @command{as}, Sun @command{ld}).
3489 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3490 newer: @command{g++} will complain that types are missing. These headers assume
3491 that omitting the type means @code{int}; this assumption worked for C89 but
3492 is wrong for C++, and is now wrong for C99 also.
3494 @command{g++} accepts such (invalid) constructs with the option
3495 @option{-fpermissive}; it
3496 will assume that any missing type is @code{int} (as defined by C89).
3498 There are patches for Solaris 2.6 (105633-56 or newer for SPARC,
3499 106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC,
3500 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
3501 108653-22 for Intel) that fix this bug.
3507 @heading @anchor{sparc-sun-solaris2*}sparc-sun-solaris2*
3509 When GCC is configured to use binutils 2.11.2 or later the binaries
3510 produced are smaller than the ones produced using Sun's native tools;
3511 this difference is quite significant for binaries containing debugging
3514 Sun @command{as} 4.x is broken in that it cannot cope with long symbol names.
3515 A typical error message might look similar to the following:
3517 @samp{/usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041:
3518 error: can't compute value of an expression involving an external symbol.}
3520 This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris
3521 2.6 and has been fixed in later (5.x) versions of the assembler,
3522 starting with Solaris 7.
3524 Starting with Solaris 7, the operating system is capable of executing
3525 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
3526 this; the @option{-m64} option enables 64-bit code generation.
3527 However, if all you want is code tuned for the UltraSPARC CPU, you
3528 should try the @option{-mtune=ultrasparc} option instead, which produces
3529 code that, unlike full 64-bit code, can still run on non-UltraSPARC
3532 When configuring on a Solaris 7 or later system that is running a kernel
3533 that supports only 32-bit binaries, one must configure with
3534 @option{--disable-multilib}, since we will not be able to build the
3535 64-bit target libraries.
3541 @heading @anchor{sparc-sun-solaris2.7}sparc-sun-solaris2.7
3543 Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
3544 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
3545 and later, including all EGCS releases. Sun formerly recommended
3546 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
3547 recommend it only for people who use Sun's compilers.
3549 Here are some workarounds to this problem:
3552 Do not install Sun patch 107058-01 until after Sun releases a
3553 complete patch for bug 4210064. This is the simplest course to take,
3554 unless you must also use Sun's C compiler. Unfortunately 107058-01
3555 is preinstalled on some new Solaris 7-based hosts, so you may have to
3559 Copy the original, unpatched Solaris 7
3560 @command{/usr/ccs/bin/as} into
3561 @command{/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/3.1/as},
3562 adjusting the latter name to fit your local conventions and software
3566 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
3567 both 107058-01 and 106950-03 installed has reported the bug with GCC
3568 and Sun's dynamic linker. This last course of action is riskiest,
3569 for two reasons. First, you must install 106950 on all hosts that
3570 run code generated by GCC; it doesn't suffice to install it only on
3571 the hosts that run GCC itself. Second, Sun says that 106950-03 is
3572 only a partial fix for bug 4210064, but Sun doesn't know whether the
3573 partial fix is adequate for GCC@. Revision -08 or later should fix
3574 the bug. The current (as of 2001-09-24) revision is -14, and is included in
3575 the Solaris 7 Recommended Patch Cluster.
3583 @heading @anchor{sparc-sun-sunos4*}sparc-sun-sunos4*
3585 A bug in the SunOS 4 linker will cause it to crash when linking
3586 @option{-fPIC} compiled objects (and will therefore not allow you to build
3589 To fix this problem you can either use the most recent version of
3590 binutils or get the latest SunOS 4 linker patch (patch ID 100170-10)
3591 from Sun's patch site.
3593 Sometimes on a Sun 4 you may observe a crash in the program
3594 @command{genflags} or @command{genoutput} while building GCC. This is said to
3595 be due to a bug in @command{sh}. You can probably get around it by running
3596 @command{genflags} or @command{genoutput} manually and then retrying the
3603 @heading @anchor{sparc-unknown-linux-gnulibc1}sparc-unknown-linux-gnulibc1
3605 It has been reported that you might need
3606 @uref{ftp://ftp.yggdrasil.com/private/hjl,,binutils 2.8.1.0.23}
3607 for this platform, too.
3614 @heading @anchor{sparc-*-linux*}sparc-*-linux*
3616 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
3617 or newer on this platform. All earlier binutils and glibc
3618 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
3625 @heading @anchor{sparc64-*-*}sparc64-*-*
3627 GCC version 2.95 is not able to compile code correctly for
3628 @code{sparc64} targets. Users of the Linux kernel, at least,
3629 can use the @code{sparc32} program to start up a new shell
3630 invocation with an environment that causes @command{configure} to
3631 recognize (via @samp{uname -a}) the system as @samp{sparc-*-*} instead.
3637 @heading @anchor{sparcv9-*-solaris2*}sparcv9-*-solaris2*
3639 The following compiler flags must be specified in the configure
3640 step in order to bootstrap this target with the Sun compiler:
3643 % CC="cc -xildoff -xarch=v9" @var{srcdir}/configure [@var{options}] [@var{target}]
3646 @option{-xildoff} turns off the incremental linker, and @option{-xarch=v9}
3647 specifies the v9 architecture to the Sun linker and assembler.
3653 @heading @anchor{#*-*-sysv*}*-*-sysv*
3654 On System V release 3, you may get this error message
3658 ld fatal: failed to write symbol name @var{something}
3659 in strings table for file @var{whatever}
3662 This probably indicates that the disk is full or your ulimit won't allow
3663 the file to be as large as it needs to be.
3665 This problem can also result because the kernel parameter @code{MAXUMEM}
3666 is too small. If so, you must regenerate the kernel and make the value
3667 much larger. The default value is reported to be 1024; a value of 32768
3668 is said to work. Smaller values may also work.
3670 On System V, if you get an error like this,
3673 /usr/local/lib/bison.simple: In function `yyparse':
3674 /usr/local/lib/bison.simple:625: virtual memory exhausted
3678 that too indicates a problem with disk space, ulimit, or @code{MAXUMEM}.
3680 On a System V release 4 system, make sure @file{/usr/bin} precedes
3681 @file{/usr/ucb} in @code{PATH}. The @code{cc} command in
3682 @file{/usr/ucb} uses libraries which have bugs.
3688 @heading @anchor{vax-dec-ultrix}vax-dec-ultrix
3689 Don't try compiling with VAX C (@code{vcc}). It produces incorrect code
3690 in some cases (for example, when @code{alloca} is used).
3696 @heading @anchor{we32k-*-*}we32k-*-*
3697 These computers are also known as the 3b2, 3b5, 3b20 and other similar
3698 names. (However, the 3b1 is actually a 68000.)
3699 These configurations are obsoleted in GCC 3.1.
3701 Don't use @option{-g} when compiling with the system's compiler. The
3702 system's linker seems to be unable to handle such a large program with
3703 debugging information.
3705 The system's compiler runs out of capacity when compiling @file{stmt.c}
3706 in GCC@. You can work around this by building @file{cpp} in GCC
3707 first, then use that instead of the system's preprocessor with the
3708 system's C compiler to compile @file{stmt.c}. Here is how:
3711 mv /lib/cpp /lib/cpp.att
3713 echo '/lib/cpp.gnu -traditional $@{1+"$@@"@}' > /lib/cpp
3717 The system's compiler produces bad code for some of the GCC
3718 optimization files. So you must build the stage 2 compiler without
3719 optimization. Then build a stage 3 compiler with optimization.
3720 That executable should work. Here are the necessary commands:
3723 make LANGUAGES=c CC=stage1/xgcc CFLAGS="-Bstage1/ -g"
3725 make CC=stage2/xgcc CFLAGS="-Bstage2/ -g -O"
3728 You may need to raise the ULIMIT setting to build a C++ compiler,
3729 as the file @file{cc1plus} is larger than one megabyte.
3735 @heading @anchor{xtensa-*-elf}xtensa-*-elf
3737 This target is intended for embedded Xtensa systems using the
3738 @samp{newlib} C library. It uses ELF but does not support shared
3739 objects. Designed-defined instructions specified via the
3740 Tensilica Instruction Extension (TIE) language are only supported
3741 through inline assembly.
3743 The Xtensa configuration information must be specified prior to
3744 building GCC@. The @file{gcc/config/xtensa/xtensa-config.h} header
3745 file contains the configuration information. If you created your
3746 own Xtensa configuration with the Xtensa Processor Generator, the
3747 downloaded files include a customized copy of this header file,
3748 which you can use to replace the default header file.
3754 @heading @anchor{xtensa-*-linux*}xtensa-*-linux*
3756 This target is for Xtensa systems running GNU/Linux. It supports ELF
3757 shared objects and the GNU C library (glibc). It also generates
3758 position-independent code (PIC) regardless of whether the
3759 @option{-fpic} or @option{-fPIC} options are used. In other
3760 respects, this target is the same as the
3761 @uref{#xtensa-*-elf,,@samp{xtensa-*-elf}} target.
3767 @heading @anchor{windows}Microsoft Windows (32 bit)
3769 A port of GCC 2.95.x is included with the
3770 @uref{http://www.cygwin.com/,,Cygwin environment}.
3772 Current (as of early 2001) snapshots of GCC will build under Cygwin
3773 without modification.
3779 @heading @anchor{os2}OS/2
3781 GCC does not currently support OS/2. However, Andrew Zabolotny has been
3782 working on a generic OS/2 port with pgcc. The current code can be found
3783 at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
3785 An older copy of GCC 2.8.1 is included with the EMX tools available at
3786 @uref{ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/,,
3787 ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/}.
3793 @heading @anchor{older}Older systems
3795 GCC contains support files for many older (1980s and early
3796 1990s) Unix variants. For the most part, support for these systems
3797 has not been deliberately removed, but it has not been maintained for
3798 several years and may suffer from bitrot. Support from some systems
3799 has been removed from GCC 3: fx80, ns32-ns-genix, pyramid, tahoe,
3800 gmicro, spur; most of these targets had not been updated since GCC
3803 We are planning to remove support for more older systems, starting in
3804 GCC 3.1. Each release will have a list of ``obsoleted'' systems.
3805 Support for these systems is still present in that release, but
3806 @command{configure} will fail unless the @option{--enable-obsolete}
3807 option is given. Unless a maintainer steps forward, support for
3808 these systems will be removed from the next release of GCC@.
3810 Support for older systems as targets for cross-compilation is less
3811 problematic than support for them as hosts for GCC; if an enthusiast
3812 wishes to make such a target work again (including resurrecting any
3813 of the targets that never worked with GCC 2, starting from the last
3814 CVS version before they were removed), patches
3815 @uref{../contribute.html,,following the usual requirements}
3816 would be likely to be accepted, since they should not affect the
3817 support for more modern targets.
3819 Support for old systems as hosts for GCC can cause problems if the
3820 workarounds for compiler, library and operating system bugs affect the
3821 cleanliness or maintainability of the rest of GCC@. In some cases, to
3822 bring GCC up on such a system, if still possible with current GCC, may
3823 require first installing an old version of GCC which did work on that
3824 system, and using it to compile a more recent GCC, to avoid bugs in
3825 the vendor compiler. Old releases of GCC 1 and GCC 2 are available in
3826 the @file{old-releases} directory on the
3827 @uref{../mirrors.html,,GCC mirror sites}. Header bugs may generally
3828 be avoided using @command{fixincludes}, but bugs or deficiencies in
3829 libraries and the operating system may still cause problems.
3831 For some systems, old versions of GNU binutils may also be useful,
3832 and are available from @file{pub/binutils/old-releases} on
3833 @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}.
3835 Some of the information on specific systems above relates to
3836 such older systems, but much of the information
3837 about GCC on such systems (which may no longer be applicable to
3838 current GCC) is to be found in the GCC texinfo manual.
3844 @heading @anchor{elf_targets}all ELF targets (SVR4, Solaris 2, etc.)
3846 C++ support is significantly better on ELF targets if you use the
3847 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
3848 inlines, vtables and template instantiations will be discarded
3858 @uref{./index.html,,Return to the GCC Installation page}
3862 @c ***Old documentation******************************************************
3864 @include install-old.texi
3871 @uref{./index.html,,Return to the GCC Installation page}
3875 @c ***GFDL********************************************************************
3884 @uref{./index.html,,Return to the GCC Installation page}
3888 @c ***************************************************************************
3889 @c Part 6 The End of the Document
3891 @comment node-name, next, previous, up
3892 @node Concept Index, , GNU Free Documentation License, Top
3896 @unnumbered Concept Index