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 @c Copyright (C) 2001 Free Software Foundation, Inc.
37 @c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com
39 @c Include everything if we're not making html
51 @c Part 2 Summary Description and Copyright
54 Copyright @copyright{} 2001 Free Software Foundation, Inc.
57 @c Part 3 Titlepage and Copyright
60 @comment The title is printed in a large font.
61 @center @titlefont{Installing GCC}
63 @c The following two commands start the copyright page.
65 @vskip 0pt plus 1filll
66 Copyright @copyright{} 2001 Free Software Foundation, Inc.
69 @c Part 4 Top node and Master Menu
72 @comment node-name, next, Previous, up
75 * Installing GCC:: This document describes the generic installation
76 procedure for GCC as well as detailing some target
77 specific installation instructions.
79 * Specific:: Host/target specific installation notes for GCC.
80 * Binaries:: Where to get pre-compiled binaries.
82 * Concept Index:: This index has two entries.
86 @c Part 5 The Body of the Document
87 @c ***Installing GCC**********************************************************
89 @comment node-name, next, previous, up
90 @node Installing GCC, Binaries, , Top
94 <h1 align="center">Installing GCC</h1>
97 @chapter Installing GCC
100 The latest version of this document is always available at
101 @uref{http://gcc.gnu.org/install/,,http://gcc.gnu.org/install/}.
103 This document describes the generic installation procedure for GCC as well
104 as detailing some target specific installation instructions.
106 GCC includes several components that previously were separate distributions
107 with their own installation instructions. This document supersedes all
108 package specific installation instructions.
110 @emph{Before} starting the build/install procedure please check the
112 @ref{Specific, host/target specific installation notes}.
115 @uref{specific.html,,host/target specific installation notes}.
117 We recommend you browse the entire generic installation instructions before
120 Lists of successful builds for released versions of GCC are
121 available at our web pages for
122 @uref{http://gcc.gnu.org/gcc-3.0/buildstat.html,,3.0}
124 @uref{http://gcc.gnu.org/gcc-2.95/buildstat.html,,2.95}.
125 These lists are updated as new information becomes available.
127 The installation procedure itself is broken into five steps.
131 * Downloading the source::
134 * Testing:: (optional)
141 @uref{download.html,,Downloading the source}
143 @uref{configure.html,,Configuration}
145 @uref{build.html,,Building}
147 @uref{test.html,,Testing} (optional)
149 @uref{finalinstall.html,,Final install}
153 Please note that GCC does not support @samp{make uninstall} and probably
154 won't do so in the near future as this would open a can of worms. Instead,
155 we suggest that you install GCC into a directory of its own and simply
156 remove that directory when you do not need that specific version of GCC
157 any longer, and, if shared libraries are installed there as well, no
158 more binaries exist that use them.
165 @uref{./index.html,,Return to the GCC Installation page}
169 @c ***Downloading the source**************************************************
171 @comment node-name, next, previous, up
172 @node Downloading the source, Configuration, , Installing GCC
176 <h1 align="center">Downloading GCC</h1>
179 @chapter Downloading GCC
181 @cindex Downloading GCC
182 @cindex Downloading the Source
184 GCC is distributed via @uref{http://gcc.gnu.org/cvs.html,,CVS} and FTP
185 tarballs compressed with @command{gzip} or
186 @command{bzip2}. It is possible to download a full distribution or specific
189 Please refer to our @uref{http://gcc.gnu.org/releases.html,,releases web page}
190 for information on how to obtain GCC@.
192 The full distribution includes the C, C++, Objective-C, Fortran, Java,
193 and CHILL compilers. The full distribution also includes runtime libraries
194 for C++, Objective-C, Fortran, Java and CHILL. (GCC 3.0 does not
195 include CHILL.) In GCC 3.0 and later versions, GNU compiler testsuites
196 are also included in the full distribution.
198 If you choose to download specific components, you must download the core
199 GCC distribution plus any language specific distributions you wish to
200 use. The core distribution includes the C language front end as well as the
201 shared components. Each language has a tarball which includes the language
202 front end as well as the language runtime (when appropriate).
204 Unpack the core distribution as well as any language specific
205 distributions in the same directory.
207 If you also intend to build binutils (either to upgrade an existing
208 installation or for use in place of the corresponding tools of your
209 OS), unpack the binutils distribution either in the same directory or
210 a separate one. In the latter case, add symbolic links to any
211 components of the binutils you intend to build alongside the compiler
212 (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
213 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
220 @uref{./index.html,,Return to the GCC Installation page}
224 @c ***Configuration***********************************************************
226 @comment node-name, next, previous, up
227 @node Configuration, Building, Downloading the source, Installing GCC
231 <h1 align="center">Installing GCC: Configuration</h1>
234 @chapter Installing GCC: Configuration
236 @cindex Configuration
237 @cindex Installing GCC: Configuration
239 Like most GNU software, GCC must be configured before it can be built.
240 This document describes the recommended configuration procedure
241 for both native and cross targets.
243 We use @var{srcdir} to refer to the toplevel source directory for
244 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
246 If you obtained the sources via CVS, @var{srcdir} must refer to the top
247 @file{gcc} directory, the one where the @file{MAINTAINERS} can be found,
248 and not its @file{gcc} subdirectory, otherwise the build will fail.
250 First, we @strong{highly} recommend that GCC be built into a
251 separate directory than the sources which does @strong{not} reside
252 within the source tree. This is how we generally build GCC; building
253 where @var{srcdir} == @var{objdir} should still work, but doesn't
254 get extensive testing; building where @var{objdir} is a subdirectory
255 of @var{srcdir} is unsupported.
257 If you have previously built GCC in the same directory for a
258 different target machine, do @samp{make distclean} to delete all files
259 that might be invalid. One of the files this deletes is
260 @file{Makefile}; if @samp{make distclean} complains that @file{Makefile}
261 does not exist, it probably means that the directory is already suitably
262 clean. However, with the recommended method of building in a separate
263 @var{objdir}, you should simply use a different @var{objdir} for each
266 Second, when configuring a native system, either @command{cc} or
267 @command{gcc} must be in your path or you must set @env{CC} in
268 your environment before running configure. Otherwise the configuration
271 Note that the bootstrap compiler and the resulting GCC must be link
272 compatible, else the bootstrap will fail with linker errors about
273 incompatible object file formats. Several multilibed targets are
274 affected by this requirement, see
276 @ref{Specific, host/target specific installation notes}.
279 @uref{specific.html,,host/target specific installation notes}.
287 % @var{srcdir}/configure [@var{options}] [@var{target}]
291 @heading Target specification
294 GCC has code to correctly determine the correct value for @var{target}
295 for nearly all native systems. Therefore, we highly recommend you not
296 provide a configure target when configuring a native compiler.
299 @var{target} must be specified as @option{--target=@var{target}}
300 when configuring a cross compiler; examples of valid targets would be
301 i960-rtems, m68k-coff, sh-elf, etc.
304 Specifying just @var{target} instead of @option{--target=@var{target}}
305 implies that the host defaults to @var{target}.
309 @heading Options specification
311 Use @var{options} to override several configure time options for
312 GCC@. A list of supported @var{options} follows; @command{configure
313 --help} may list other options, but those not listed below may not
314 work and should not normally be used.
317 @item --prefix=@var{dirname}
318 Specify the toplevel installation
319 directory. This is the recommended way to install the tools into a directory
320 other than the default. The toplevel installation directory defaults to
323 We @strong{highly} recommend against @var{dirname} being the same or a
324 subdirectory of @var{objdir} or vice versa.
326 These additional options control where certain parts of the distribution
327 are installed. Normally you should not need to use these options.
330 @item --exec-prefix=@var{dirname}
331 Specify the toplevel installation directory for architecture-dependent
332 files. The default is @file{@var{prefix}}.
334 @item --bindir=@var{dirname}
335 Specify the installation directory for the executables called by users
336 (such as @command{gcc} and @command{g++}). The default is
337 @file{@var{exec-prefix}/bin}.
339 @item --libdir=@var{dirname}
340 Specify the installation directory for object code libraries and
341 internal parts of GCC@. The default is @file{@var{exec-prefix}/lib}.
343 @item --with-slibdir=@var{dirname}
344 Specify the installation directory for the shared libgcc library. The
345 default is @file{@var{libdir}}.
347 @item --infodir=@var{dirname}
348 Specify the installation directory for documentation in info format.
349 The default is @file{@var{prefix}/info}.
351 @item --mandir=@var{dirname}
352 Specify the installation directory for manual pages. The default is
353 @file{@var{prefix}/man}. (Note that the manual pages are only extracts from
354 the full GCC manuals, which are provided in Texinfo format. The
355 @command{g77} manpage is unmaintained and may be out of date; the others
356 are derived by an automatic conversion process from parts of the full
359 @item --with-gxx-include-dir=@var{dirname}
361 the installation directory for G++ header files. The default is
362 @file{@var{prefix}/include/g++-v3}.
366 @item --program-prefix=@var{prefix}
367 GCC supports some transformations of the names of its programs when
368 installing them. This option prepends @var{prefix} to the names of
369 programs to install in @var{bindir} (see above). For example, specifying
370 @option{--program-prefix=foo-} would result in @samp{gcc}
371 being installed as @file{/usr/local/bin/foo-gcc}.
373 @item --program-suffix=@var{suffix}
374 Appends @var{suffix} to the names of programs to install in @var{bindir}
375 (see above). For example, specifying @option{--program-suffix=-3.1}
376 would result in @samp{gcc} being installed as
377 @file{/usr/local/bin/gcc-3.1}.
379 @item --program-transform-name=@var{pattern}
380 Applies the @samp{sed} script @var{pattern} to be applied to the names
381 of programs to install in @var{bindir} (see above). @var{pattern} has to
382 consist of one or more basic @samp{sed} editing commands, separated by
383 semicolons. For example, if you want the @samp{gcc} program name to be
384 transformed to the installed program @file{/usr/local/bin/myowngcc} and
385 the @samp{g++} program name to be transformed to
386 @file{/usr/local/bin/gspecial++} without changing other program names,
387 you could use the pattern
388 @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}
389 to achieve this effect.
391 All three options can be combined and used together, resulting in more
392 complex conversion patterns. As a basic rule, @var{prefix} (and
393 @var{suffix}) are prepended (appended) before further transformations
394 can happen with a special transformation script @var{pattern}.
396 As currently implemented, this options only take effect for native
397 builds; cross compiler binaries' names are not transformed even when a
398 transformation is explicitly asked for by one of this options.
400 For native builds, some of the installed programs are also installed
401 with the target alias in front of their name, as in
402 @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
403 before the target alias is prepended to the name - so, specifying
404 @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
405 resulting binary would be installed as
406 @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.
408 As a last shortcoming, none of the installed CHILL and Ada programs are
409 transformed yet, which will be fixed in some time.
411 @item --with-local-prefix=@var{dirname}
413 installation directory for local include files. The default is
414 @file{/usr/local}. Specify this option if you want the compiler to
415 search directory @file{@var{dirname}/include} for locally installed
416 header files @emph{instead} of @file{/usr/local/include}.
418 You should specify @option{--with-local-prefix} @strong{only} if your
419 site has a different convention (not @file{/usr/local}) for where to put
422 The default value for @option{--with-local-prefix} is @file{/usr/local}
423 regardless of the value of @option{--prefix}. Specifying
424 @option{--prefix} has no effect on which directory GCC searches for
425 local header files. This may seem counterintuitive, but actually it is
428 The purpose of @option{--prefix} is to specify where to @emph{install
429 GCC}. The local header files in @file{/usr/local/include}---if you put
430 any in that directory---are not part of GCC@. They are part of other
431 programs---perhaps many others. (GCC installs its own header files in
432 another directory which is based on the @option{--prefix} value.)
434 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
435 The directory you use for @option{--with-local-prefix} @strong{must not}
436 contain any of the system's standard header files. If it did contain
437 them, certain programs would be miscompiled (including GNU Emacs, on
438 certain targets), because this would override and nullify the header
439 file corrections made by the @code{fixincludes} script.
441 Indications are that people who use this option use it based on mistaken
442 ideas of what it is for. People use it as if it specified where to
443 install part of GCC@. Perhaps they make this assumption because
444 installing GCC creates the directory.
446 @item --enable-shared[=@var{package}[,@dots{}]]
447 Build shared versions of libraries, if shared libraries are supported on
448 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
449 are enabled by default on all platforms that support shared libraries,
450 except for @samp{libobjc} which is built as a static library only by
453 If a list of packages is given as an argument, build shared libraries
454 only for the listed packages. For other packages, only static libraries
455 will be built. Package names currently recognized in the GCC tree are
456 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
457 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc} and
458 @samp{libjava}. Note that @samp{libobjc} does not recognize itself by
459 any name, so, if you list package names in @option{--enable-shared},
460 you will only get static Objective-C libraries. @samp{libf2c} and
461 @samp{libiberty} do not support shared libraries at all.
463 Use @option{--disable-shared} to build only static libraries. Note that
464 @option{--disable-shared} does not accept a list of package names as
465 argument, only @option{--enable-shared} does.
467 @item @anchor{with-gnu-as}--with-gnu-as
468 Specify that the compiler should assume that the
469 assembler it finds is the GNU assembler. However, this does not modify
470 the rules to find an assembler and will result in confusion if found
471 assembler is not actually the GNU assembler. (Confusion will also
472 result if the compiler finds the GNU assembler but has not been
473 configured with @option{--with-gnu-as}.) If you have more than one
474 assembler installed on your system, you may want to use this option in
475 connection with @option{--with-as=@var{pathname}}.
477 The systems where it makes a difference whether you use the GNU assembler are
478 @samp{hppa1.0-@var{any}-@var{any}}, @samp{hppa1.1-@var{any}-@var{any}},
479 @samp{i386-@var{any}-sysv}, @samp{i386-@var{any}-isc},
480 @samp{i860-@var{any}-bsd}, @samp{m68k-bull-sysv},
481 @samp{m68k-hp-hpux}, @samp{m68k-sony-bsd},
482 @samp{m68k-altos-sysv}, @samp{m68000-hp-hpux},
483 @samp{m68000-att-sysv}, @samp{@var{any}-lynx-lynxos},
484 and @samp{mips-@var{any}}.
485 On any other system, @option{--with-gnu-as} has no effect.
487 On the systems listed above (except for the HP-PA, for ISC on the
488 386, and for @samp{mips-sgi-irix5.*}), if you use the GNU assembler,
489 you should also use the GNU linker (and specify @option{--with-gnu-ld}).
491 @item --with-as=@var{pathname}
493 compiler should use the assembler pointed to by @var{pathname}, rather
494 than the one found by the standard rules to find an assembler, which
499 @file{@var{exec_prefix}/lib/gcc-lib/@var{target}/@var{version}}
500 directory, where @var{exec_prefix} defaults to @var{prefix} which
501 defaults to @file{/usr/local} unless overridden by the
502 @option{--prefix=@var{pathname}} switch described above. @var{target} is the
503 target system triple, such as @samp{sparc-sun-solaris2.7}, and
504 @var{version} denotes the GCC version, such as 3.0.
506 Check operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
509 Note that these rules do not check for the value of @env{PATH}. You may
510 want to use @option{--with-as} if no assembler is installed in the
511 directories listed above, or if you have multiple assemblers installed
512 and want to choose one that is not found by the above rules.
514 @item @anchor{with-gnu-ld}--with-gnu-ld
515 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
519 @item --with-ld=@var{pathname}
521 @option{--with-as}, but for the linker.
524 Specify that stabs debugging
525 information should be used instead of whatever format the host normally
526 uses. Normally GCC uses the same debug format as the host system.
528 On MIPS based systems and on Alphas, you must specify whether you want
529 GCC to create the normal ECOFF debugging format, or to use BSD-style
530 stabs passed through the ECOFF symbol table. The normal ECOFF debug
531 format cannot fully handle languages other than C@. BSD stabs format can
532 handle other languages, but it only works with the GNU debugger GDB@.
534 Normally, GCC uses the ECOFF debugging format by default; if you
535 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
537 No matter which default you choose when you configure GCC, the user
538 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
539 the debug format for a particular compilation.
541 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
542 @option{--with-gas} is used. It selects use of stabs debugging
543 information embedded in COFF output. This kind of debugging information
544 supports C++ well; ordinary COFF debugging information does not.
546 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
547 selects use of stabs debugging information embedded in ELF output. The
548 C++ compiler currently (2.6.0) does not support the DWARF debugging
549 information normally used on 386 SVR4 platforms; stabs provide a
550 workable alternative. This requires gas and gdb, as the normal SVR4
551 tools can not generate or interpret stabs.
553 @item --disable-multilib
554 Specify that multiple target
555 libraries to support different target variants, calling
556 conventions, etc should not be built. The default is to build a
557 predefined set of them.
559 Some targets provide finer-grained control over which multilibs are built
560 (e.g., @option{--disable-softfloat}):
567 fpu, 26bit, underscore, interwork, biendian, nofmult.
570 softfloat, m68881, m68000, m68020.
573 single-float, biendian, softfloat.
575 @item powerpc*-*-*, rs6000*-*-*
576 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
581 @item --enable-threads
582 Specify that the target
583 supports threads. This affects the Objective-C compiler and runtime
584 library, and exception handling for other languages like C++ and Java.
585 On some systems, this is the default.
587 In general, the best (and, in many cases, the only known) threading
588 model available will be configured for use. Beware that on some
589 systems, gcc has not been taught what threading models are generally
590 available for the system. In this case, @option{--enable-threads} is an
591 alias for @option{--enable-threads=single}.
593 @item --disable-threads
594 Specify that threading support should be disabled for the system.
595 This is an alias for @option{--enable-threads=single}.
597 @item --enable-threads=@var{lib}
599 @var{lib} is the thread support library. This affects the Objective-C
600 compiler and runtime library, and exception handling for other languages
601 like C++ and Java. The possibilities for @var{lib} are:
609 Generic MACH thread support, known to work on NeXTSTEP@. (Please note
610 that the file needed to support this configuration, @file{gthr-mach.h}, is
611 missing and thus this setting will cause a known bootstrap failure.)
613 This is an alias for @samp{single}.
615 Generic POSIX thread support.
617 Same as @samp{posix} on arm*-*-linux*, *-*-chorusos* and *-*-freebsd*
618 only. A future release of gcc might remove this alias or extend it
621 RTEMS thread support.
623 Disable thread support, should work for all platforms.
625 Sun Solaris 2 thread support.
627 VxWorks thread support.
629 Microsoft Win32 API thread support.
632 @item --with-cpu=@var{cpu}
633 Specify which cpu variant the
634 compiler should generate code for by default. This is currently
635 only supported on the some ports, specifically arm, powerpc, and
636 SPARC@. If configure does not recognize the model name (e.g.@: arm700,
637 603e, or ultrasparc) you provide, please check the configure script
638 for a complete list of supported models.
640 @item --enable-target-optspace
642 libraries should be optimized for code space instead of code speed.
643 This is the default for the m32r platform.
646 Specify that a user visible @command{cpp} program should not be installed.
648 @item --with-cpp-install-dir=@var{dirname}
649 Specify that the user visible @command{cpp} program should be installed
650 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
652 @item --enable-maintainer-mode
654 regenerate the GCC master message catalog @file{gcc.pot} are normally
655 disabled. This is because it can only be rebuilt if the complete source
656 tree is present. If you have changed the sources and want to rebuild the
657 catalog, configuring with @option{--enable-maintainer-mode} will enable
658 this. Note that you need a recent version of the @code{gettext} tools
661 @item --enable-version-specific-runtime-libs
663 that runtime libraries should be installed in the compiler specific
664 subdirectory (@file{@var{libsubdir}}) rather than the usual places. In
665 addition, @samp{libstdc++}'s include files will be installed in
666 @file{@var{libsubdir}/include/g++} unless you overruled it by using
667 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
668 particularly useful if you intend to use several versions of GCC in
669 parallel. This is currently supported by @samp{libf2c} and
670 @samp{libstdc++}, and is the default for @samp{libobjc} which cannot be
671 changed in this case.
673 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
674 Specify that only a particular subset of compilers and
675 their runtime libraries should be built. For a list of valid values for
676 @var{langN} you can issue the following command in the
677 @file{gcc} directory of your GCC source tree:@*
679 grep language= */config-lang.in
681 Currently, you can use any of the following:
682 @code{ada}, @code{c}, @code{c++}, @code{f77}, @code{java}, @code{objc}.
683 @code{CHILL} is not currently maintained, and will almost
684 certainly fail to compile. Building the Ada compiler has special
685 requirements, see below.@*
686 If you do not pass this flag, all languages available in the @file{gcc}
687 sub-tree will be configured. Re-defining @code{LANGUAGES} when calling
688 @samp{make bootstrap} @strong{does not} work anymore, as those
689 language sub-directories might not have been configured!
691 @item --disable-libgcj
692 Specify that the run-time libraries
693 used by GCJ should not be built. This is useful in case you intend
694 to use GCJ with some other run-time, or you're going to install it
695 separately, or it just happens not to build on your particular
696 machine. In general, if the Java front end is enabled, the GCJ
697 libraries will be enabled too, unless they're known to not work on
698 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
699 may need to port it; in this case, before modifying the top-level
700 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
701 you may use @option{--enable-libgcj} to override the default.
704 Specify that the compiler should
705 use DWARF 2 debugging information as the default.
707 @item --enable-win32-registry
708 @itemx --enable-win32-registry=@var{key}
709 @itemx --disable-win32-registry
710 The @option{--enable-win32-registry} option enables Windows-hosted GCC
711 to look up installations paths in the registry using the following key:
714 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
717 @var{key} defaults to GCC version number, and can be overridden by the
718 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
719 who use custom installers are encouraged to provide a different key,
720 perhaps one comprised of vendor name and GCC version number, to
721 avoid conflict with existing installations. This feature is enabled
722 by default, and can be disabled by @option{--disable-win32-registry}
723 option. This option has no effect on the other hosts.
726 Specify that the machine does not have a floating point unit. This
727 option only applies to @samp{m68k-sun-sunos@var{n}} and
728 @samp{m68k-isi-bsd}. On any other system, @option{--nfp} has no effect.
730 @item --enable-checking
731 @itemx --enable-checking=@var{list}
732 When you specify this option, the compiler is built to perform checking
733 of tree node types when referencing fields of that node, and some other
734 internal consistency checks. This does not change the generated code,
735 but adds error checking within the compiler. This will slow down the
736 compiler and may only work properly if you are building the compiler
737 with GCC@. This is on by default when building from CVS or snapshots,
738 but off for releases. More control over the checks may be had by
739 specifying @var{list}; the categories of checks available are
740 @samp{misc}, @samp{tree}, @samp{gc}, @samp{rtl} and @samp{gcac}. The
741 default when @var{list} is not specified is @samp{misc,tree,gc}; the
742 checks @samp{rtl} and @samp{gcac} are very expensive.
746 The @option{--enable-nls} option enables Native Language Support (NLS),
747 which lets GCC output diagnostics in languages other than American
748 English. Native Language Support is enabled by default if not doing a
749 canadian cross build. The @option{--disable-nls} option disables NLS@.
751 @item --with-included-gettext
752 If NLS is enabled, the @option{--with-included-gettext} option causes the build
753 procedure to prefer its copy of GNU @command{gettext}.
756 If NLS is enabled, and if the host lacks @code{gettext} but has the
757 inferior @code{catgets} interface, the GCC build procedure normally
758 ignores @code{catgets} and instead uses GCC's copy of the GNU
759 @code{gettext} library. The @option{--with-catgets} option causes the
760 build procedure to use the host's @code{catgets} in this situation.
762 @item --with-system-zlib
763 Use installed zlib rather than that included with GCC@. This option
764 only applies if the Java front end is being built.
767 Some options which only apply to building cross compilers:
769 @item --with-headers=@var{dir}
770 Specifies a directory
771 which has target include files.
772 @emph{This options is required} when building a cross
773 compiler, if @file{@var{prefix}/@var{target}/sys-include} doesn't pre-exist.
774 These include files will be copied into the @file{gcc} install directory.
775 Fixincludes will be run on these files to make them compatible with
777 @item --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
778 Specifies a list of directories which contain the target runtime
779 libraries. These libraries will be copied into the @file{gcc} install
782 Specifies that @samp{newlib} is
783 being used as the target C library. This causes @code{__eprintf} to be
784 omitted from @file{libgcc.a} on the assumption that it will be provided by
788 Note that each @option{--enable} option has a corresponding
789 @option{--disable} option and that each @option{--with} option has a
790 corresponding @option{--without} option.
797 @uref{./index.html,,Return to the GCC Installation page}
801 @c ***Building****************************************************************
803 @comment node-name, next, previous, up
804 @node Building, Testing, Configuration, Installing GCC
808 <h1 align="center">Installing GCC: Building</h1>
813 @cindex Installing GCC: Building
815 Now that GCC is configured, you are ready to build the compiler and
818 We @strong{highly} recommend that GCC be built using GNU make;
819 other versions may work, then again they might not.
820 GNU make is required for compiling GNAT, the Ada compiler.
822 (For example, many broken versions of make will fail if you use the
823 recommended setup where @var{objdir} is different from @var{srcdir}.
824 Other broken versions may recompile parts of the compiler when
825 installing the compiler.)
827 Some commands executed when making the compiler may fail (return a
828 nonzero status) and be ignored by @code{make}. These failures, which
829 are often due to files that were not found, are expected, and can safely
832 It is normal to have compiler warnings when compiling certain files.
833 Unless you are a GCC developer, you can generally ignore these warnings
834 unless they cause compilation to fail.
836 On certain old systems, defining certain environment variables such as
837 @env{CC} can interfere with the functioning of @command{make}.
839 If you encounter seemingly strange errors when trying to build the
840 compiler in a directory other than the source directory, it could be
841 because you have previously configured the compiler in the source
842 directory. Make sure you have done all the necessary preparations.
844 If you build GCC on a BSD system using a directory stored in an old System
845 V file system, problems may occur in running @code{fixincludes} if the
846 System V file system doesn't support symbolic links. These problems
847 result in a failure to fix the declaration of @code{size_t} in
848 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
849 that type mismatches occur, this could be the cause.
851 The solution is not to use such a directory for building GCC@.
853 When building from CVS or snapshots, or if you modify parser sources,
854 you need the Bison parser generator installed. Any version 1.25 or
855 later should work; older versions may also work. If you do not modify
856 parser sources, releases contain the Bison-generated files and you do
857 not need Bison installed to build them.
859 When building from CVS or snapshots, or if you modify Texinfo
860 documentation, you need version 4.0 or later of Texinfo installed if you
861 want Info documentation to be regenerated. Releases contain Info
862 documentation pre-built for the unmodified documentation in the release.
864 @section Building a native compiler
866 For a native build issue the command @samp{make bootstrap}. This
867 will build the entire GCC system, which includes the following steps:
871 Build host tools necessary to build the compiler such as texinfo, bison,
875 Build target tools for use by the compiler such as binutils (bfd,
876 binutils, gas, gprof, ld, and opcodes)
877 if they have been individually linked
878 or moved into the top level GCC source tree before configuring.
881 Perform a 3-stage bootstrap of the compiler.
884 Perform a comparison test of the stage2 and stage3 compilers.
887 Build runtime libraries using the stage3 compiler from the previous step.
891 If you are short on disk space you might consider @samp{make
892 bootstrap-lean} instead. This is identical to @samp{make
893 bootstrap} except that object files from the stage1 and
894 stage2 of the 3-stage bootstrap of the compiler are deleted as
895 soon as they are no longer needed.
898 If you want to save additional space during the bootstrap and in
899 the final installation as well, you can build the compiler binaries
900 without debugging information with @samp{make CFLAGS='-O' LIBCFLAGS='-g
901 -O2' LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap}. This will save
902 roughly 40% of disk space both for the bootstrap and the final installation.
903 (Libraries will still contain debugging information.)
905 If you wish to use non-default GCC flags when compiling the stage2 and
906 stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing
907 @samp{make bootstrap}. Non-default optimization flags are less well
908 tested here than the default of @samp{-g -O2}, but should still work.
909 In a few cases, you may find that you need to specify special flags such
910 as @option{-msoft-float} here to complete the bootstrap; or, if the
911 native compiler miscompiles the stage1 compiler, you may need to work
912 around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the
913 stage1 compiler that were miscompiled, or by using @samp{make
914 bootstrap4} to increase the number of stages of bootstrap.
916 If you used the flag @option{--enable-languages=@dots{}} to restrict
917 the compilers to be built, only those you've actually enabled will be
918 built. This will of course only build those runtime libraries, for
919 which the particular compiler has been built. Please note,
920 that re-defining @env{LANGUAGES} when calling @samp{make bootstrap}
921 @strong{does not} work anymore!
923 If the comparison of stage2 and stage3 fails, this normally indicates
924 that the stage2 compiler has compiled GCC incorrectly, and is therefore
925 a potentially serious bug which you should investigate and report. (On
926 a few systems, meaningful comparison of object files is impossible; they
927 always appear ``different''. If you encounter this problem, you will
928 need to disable comparison in the @file{Makefile}.)
930 @section Building a cross compiler
932 We recommend reading the
933 @uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ}
934 for information about building cross compilers.
936 When building a cross compiler, it is not generally possible to do a
937 3-stage bootstrap of the compiler. This makes for an interesting problem
938 as parts of GCC can only be built with GCC@.
940 To build a cross compiler, we first recommend building and installing a
941 native compiler. You can then use the native GCC compiler to build the
944 Assuming you have already installed a native copy of GCC and configured
945 your cross compiler, issue the command @command{make}, which performs the
950 Build host tools necessary to build the compiler such as texinfo, bison,
954 Build target tools for use by the compiler such as binutils (bfd,
955 binutils, gas, gprof, ld, and opcodes)
956 if they have been individually linked or moved into the top level GCC source
957 tree before configuring.
960 Build the compiler (single stage only).
963 Build runtime libraries using the compiler from the previous step.
966 Note that if an error occurs in any step the make process will exit.
968 @section Building in parallel
970 If you have a multiprocessor system you can use @samp{make bootstrap
971 MAKE="make -j 2" -j 2} or just @samp{make -j 2 bootstrap}
972 for GNU Make 3.79 and above instead of just @samp{make bootstrap}
973 when building GCC@. You can use a bigger number instead of two if
974 you like. In most cases, it won't help to use a number bigger than
975 the number of processors in your machine.
977 @section Building the Ada compiler
979 In order to build GNAT, the Ada compiler, you need a working GNAT
980 compiler, since the Ada front end is written in Ada (with some
981 GNAT-specific extensions), and GNU make.
983 However, you do not need a full installation of GNAT, just the GNAT
984 binary @file{gnat1}, a copy of @file{gnatbind}, and a compiler driver
985 which can deal with Ada input (by invoking the @file{gnat1} binary).
986 You can specify this compiler driver by setting the @env{ADAC}
987 environment variable at the configure step. @command{configure} can
988 detect the driver automatically if it has got a common name such as
989 @command{gcc} or @command{gnatgcc}. Of course, you still need a working
990 C compiler (the compiler driver can be different or not).
992 Additional build tools (such as @command{gnatmake}) or a working GNAT
993 run-time library installation are usually @emph{not} required. However,
994 if you want to boostrap the compiler using a minimal version of GNAT,
995 you have to issue the following commands before invoking @samp{make
996 boostrap} (this assumes that you start with an unmodified and consistent
997 source distribution):
1000 cd @var{srcdir}/gcc/ada
1001 touch treeprs.ads [es]info.h nmake.ad[bs]
1004 At the moment, the GNAT library and several tools for GNAT are not built
1005 by @samp{make bootstrap}. You have to invoke
1006 @samp{make gnatlib_and_tools} in the @file{@var{objdir}/gcc}
1007 subdirectory before proceeding with the next steps.
1009 For example, you can build a native Ada compiler by issuing the
1010 following commands (assuming @command{make} is GNU make):
1014 @var{srcdir}/configure --enable-languages=c,ada
1015 cd @var{srcdir}/gcc/ada
1016 touch treeprs.ads [es]info.h nmake.ad[bs]
1020 make gnatlib_and_tools
1024 Currently, when compiling the Ada front end, you cannot use the parallel
1025 build feature described in the previous section.
1032 @uref{./index.html,,Return to the GCC Installation page}
1036 @c ***Testing*****************************************************************
1038 @comment node-name, next, previous, up
1039 @node Testing, Final install, Building, Installing GCC
1043 <h1 align="center">Installing GCC: Testing</h1>
1046 @chapter Installing GCC: Testing
1049 @cindex Installing GCC: Testing
1052 Before you install GCC, you might wish to run the testsuite. This
1053 step is optional and may require you to download additional software.
1055 First, you must have @uref{download.html,,downloaded the testsuites}.
1056 The full distribution contains testsuites; only if you downloaded the
1057 ``core'' compiler plus any front ends, you do not have the testsuites.
1059 Second, you must have a @uref{http://www.gnu.org/software/dejagnu/,,current version of DejaGnu} installed;
1060 dejagnu 1.3 is not sufficient.
1062 Now you may need specific preparations:
1067 The following environment variables may need to be set appropriately, as in
1068 the following example (which assumes that DejaGnu has been installed
1069 under @file{/usr/local}):
1072 TCL_LIBRARY = /usr/local/share/tcl8.0
1073 DEJAGNULIBS = /usr/local/share/dejagnu
1076 On systems such as Cygwin, these paths are required to be actual
1077 paths, not mounts or links; presumably this is due to some lack of
1078 portability in the DejaGnu code.
1080 If the directories where @command{runtest} and @command{expect} were
1081 installed are in the @env{PATH}, it should not be necessary to set these
1082 environment variables.
1086 Finally, you can run the testsuite (which may take a long time):
1088 cd @var{objdir}; make -k check
1091 The testing process will try to test as many components in the GCC
1092 distribution as possible, including the C, C++, Objective-C and Fortran
1093 compilers as well as the C++ and Java runtime libraries.
1095 @section How can I run the test suite on selected tests?
1097 As a first possibility to cut down the number of tests that are run it is
1098 possible to use @samp{make check-gcc} or @samp{make check-g++}
1099 in the @file{gcc} subdirectory of the object directory. To further cut down the
1100 tests the following is possible:
1103 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
1106 This will run all @command{gcc} execute tests in the testsuite.
1109 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
1112 This will run the @command{g++} ``old-deja'' tests in the testsuite where the filename
1113 matches @samp{9805*}.
1115 The @file{*.exp} files are located in the testsuite directories of the GCC
1116 source, the most important ones being @file{compile.exp},
1117 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
1118 To get a list of the possible @file{*.exp} files, pipe the
1119 output of @samp{make check} into a file and look at the
1120 @samp{Running @dots{} .exp} lines.
1122 @section How to interpret test results
1124 After the testsuite has run you'll find various @file{*.sum} and @file{*.log}
1125 files in the testsuite subdirectories. The @file{*.log} files contain a
1126 detailed log of the compiler invocations and the corresponding
1127 results, the @file{*.sum} files summarize the results. These summaries list
1128 all the tests that have been run with a corresponding status code:
1132 PASS: the test passed as expected
1134 XPASS: the test unexpectedly passed
1136 FAIL: the test unexpectedly failed
1138 XFAIL: the test failed as expected
1140 UNSUPPORTED: the test is not supported on this platform
1142 ERROR: the testsuite detected an error
1144 WARNING: the testsuite detected a possible problem
1147 It is normal for some tests to report unexpected failures. At the
1148 current time our testing harness does not allow fine grained control
1149 over whether or not a test is expected to fail. We expect to fix this
1150 problem in future releases.
1153 @section Submitting test results
1155 If you want to report the results to the GCC project, use the
1156 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
1159 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
1160 -m gcc-testresults@@gcc.gnu.org |sh
1163 This script uses the @command{Mail} program to send the results, so
1164 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
1165 prepended to the testsuite summary and should contain any special
1166 remarks you have on your results or your build environment. Please
1167 do not edit the testsuite result block or the subject line, as these
1168 messages are automatically parsed and presented at the
1169 @uref{http://gcc.gnu.org/testresults/,,GCC testresults} web
1170 page. Here you can also gather information on how specific tests
1171 behave on different platforms and compare them with your results. A
1172 few failing testcases are possible even on released versions and you
1173 should look here first if you think your results are unreasonable.
1177 @c ***Final install***********************************************************
1179 @comment node-name, next, previous, up
1180 @node Final install, , Testing, Installing GCC
1182 @ifset finalinstallhtml
1184 <h1 align="center">Installing GCC: Final installation</h1>
1187 @chapter Installing GCC: Final installation
1190 Now that GCC has been built (and optionally tested), you can install it with
1192 cd @var{objdir}; make install
1195 That step completes the installation of GCC; user level binaries can
1196 be found in @file{@var{prefix}/bin} where @var{prefix} is the value you
1197 specified with the @option{--prefix} to configure (or @file{/usr/local}
1198 by default). (If you specified @option{--bindir}, that directory will
1199 be used instead; otherwise, if you specified @option{--exec-prefix},
1200 @file{@var{exec-prefix}/bin} will be used.) Headers for the C++ and
1201 Java libraries are installed in @file{@var{prefix}/include}; libraries
1202 in @file{@var{libdir}} (normally @file{@var{prefix}/lib}); internal
1203 parts of the compiler in @file{@var{libdir}/gcc-lib}; documentation in
1204 info format in @file{@var{infodir}} (normally @file{@var{prefix}/info}).
1206 If you built a released version of GCC then if you don't mind, please
1207 quickly review the build status page for
1208 @uref{http://gcc.gnu.org/gcc-3.0/buildstat.html,,3.0} or
1209 @uref{http://gcc.gnu.org/gcc-2.95/buildstat.html,,2.95}.
1210 If your system is not listed, send a note to
1211 @email{gcc@@gcc.gnu.org} indicating
1212 that you successfully built and installed GCC.
1214 Include the output from running @file{@var{srcdir}/config.guess}. (Do
1215 not send us the @file{config.guess} file itself, just the one-line output from
1216 running it!) Also specify which version you built.
1217 If the build was for GNU/Linux, also include the distribution name and version
1218 (e.g., Red Hat 7.1 or Debian 2.2.3, available from @file{/etc/issue})
1219 and the version of glibc you used; for RPM-based systems like Red Hat,
1220 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
1221 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
1223 We'd also like to know if the
1225 @ref{Specific, host/target specific installation notes}
1228 @uref{specific.html,,host/target specific installation notes}
1230 didn't include your host/target information or if that information is
1231 incomplete or out of date. Send a note to
1232 @email{gcc@@gcc.gnu.org} telling us how the information should be changed.
1234 If you find a bug, please report it following our
1235 @uref{../bugs.html,,bug reporting guidelines}.
1237 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
1238 dvi}. You will need to have @command{texi2dvi} (version at least 4.0)
1239 and @TeX{} installed. This creates a number of @file{.dvi} files in
1240 subdirectories of @file{@var{objdir}}; these may be converted for
1241 printing with programs such as @command{dvips}. You can also
1242 @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the
1243 Free Software Foundation}, though such manuals may not be for the most
1244 recent version of GCC@.
1251 @uref{./index.html,,Return to the GCC Installation page}
1255 @c ***Binaries****************************************************************
1257 @comment node-name, next, previous, up
1258 @node Binaries, Specific, Installing GCC, Top
1262 <h1 align="center">Installing GCC: Binaries</h1>
1265 @chapter Installing GCC: Binaries
1268 @cindex Installing GCC: Binaries
1270 We are often asked about pre-compiled versions of GCC@. While we cannot
1271 provide these for all platforms, below you'll find links to binaries for
1272 various platforms where creating them by yourself is not easy due to various
1275 Please note that we did not create these binaries, nor do we
1276 support them. If you have any problems installing them, please
1277 contact their makers.
1284 @uref{http://freeware.bull.net,,Bull's Freeware and Shareware Archive for AIX};
1287 @uref{http://aixpdslib.seas.ucla.edu,,UCLA Software Library for AIX};
1291 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP};
1297 @uref{http://hpux.cae.wisc.edu/,,HP-UX Porting Center};
1300 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
1304 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
1305 OpenServer/Unixware};
1308 Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware};
1311 SGI---@uref{http://freeware.sgi.com/,,SGI Freeware};
1314 Windows 95, 98, and NT:
1317 The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project;
1319 @uref{http://www.xraylith.wisc.edu/~khan/software/gnu-win32/,,GNU Win32}
1320 related projects by Mumit Khan.
1324 @uref{ftp://ftp.thewrittenword.com/packages/free/by-name/gcc-2.95.2/,,The
1325 Written Word} offers binaries for Solaris 2.5.1, 2.6, 2.7/SPARC, 2.7/Intel,
1326 IRIX 6.2, 6.5, Digital UNIX 4.0D, HP-UX 10.20, and HP-UX 11.00.
1329 Hitachi H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
1330 Development Tools for the Hitachi H8/300[HS] Series}
1334 In addition to those specific offerings, you can get a binary
1335 distribution CD-ROM from the
1336 @uref{http://www.fsf.org/order/order.html,,Free Software Foundation}.
1337 It contains binaries for a number of platforms, and
1338 includes not only GCC, but other stuff as well. The current CD does
1339 not contain the latest version of GCC, but it should allow
1340 bootstrapping the compiler. An updated version of that disk is in the
1348 @uref{./index.html,,Return to the GCC Installation page}
1352 @c ***Specific****************************************************************
1354 @comment node-name, next, previous, up
1355 @node Specific, Concept Index, Binaries, Top
1359 <h1 align="center">Host/target specific installation notes for GCC</h1>
1362 @chapter Host/target specific installation notes for GCC
1365 @cindex Specific installation notes
1366 @cindex Target specific installation
1367 @cindex Host specific installation
1368 @cindex Target specific installation notes
1370 Please read this document carefully @emph{before} installing the
1371 GNU Compiler Collection on your machine.
1373 Lists of successful builds for released versions of GCC are
1374 available at our web pages for
1375 @uref{http://gcc.gnu.org/gcc-3.0/buildstat.html,,3.0}
1377 @uref{http://gcc.gnu.org/gcc-2.95/buildstat.html,,2.95}.
1378 These lists are updated as new information becomes available.
1383 @uref{#1750a-*-*,,1750a-*-*}
1387 @uref{#a29k-*-bsd,,a29k-*-bsd}
1389 @uref{#alpha*-*-*,,alpha*-*-*}
1391 @uref{#alpha*-dec-osf*,,alpha*-dec-osf*}
1393 @uref{#alphaev5-cray-unicosmk*,,alphaev5-cray-unicosmk*}
1395 @uref{#arc-*-elf,,arc-*-elf}
1397 @uref{#arm-*-aout,,arm-*-aout}
1399 @uref{#arm-*-elf,,arm-*-elf}
1401 @uref{#arm*-*-linux-gnu,,arm*-*-linux-gnu}
1403 @uref{#arm-*-riscix,,arm-*-riscix}
1411 @uref{#dsp16xx,,dsp16xx}
1413 @uref{#elxsi-elxsi-bsd,,elxsi-elxsi-bsd}
1415 @uref{#*-*-freebsd*,,*-*-freebsd*}
1417 @uref{#h8300-hms,,h8300-hms}
1419 @uref{#hppa*-hp-hpux*,,hppa*-hp-hpux*}
1421 @uref{#hppa*-hp-hpux9,,hppa*-hp-hpux9}
1423 @uref{#hppa*-hp-hpux10,,hppa*-hp-hpux10}
1425 @uref{#hppa*-hp-hpux11,,hppa*-hp-hpux11}
1427 @uref{#i370-*-*,,i370-*-*}
1429 @uref{#*-*-linux-gnu,,*-*-linux-gnu}
1431 @uref{#ix86-*-linux*oldld,,i?86-*-linux*oldld}
1433 @uref{#ix86-*-linux*aout,,i?86-*-linux*aout}
1435 @uref{#ix86-*-linux*,,i?86-*-linux*}
1437 @uref{#ix86-*-sco,,i?86-*-sco}
1439 @uref{#ix86-*-sco3.2v4,,i?86-*-sco3.2v4}
1441 @uref{#ix86-*-sco3.2v5*,,i?86-*-sco3.2v5*}
1443 @uref{#ix86-*-udk,,i?86-*-udk}
1445 @uref{#ix86-*-isc,,i?86-*-isc}
1447 @uref{#ix86-*-esix,,i?86-*-esix}
1449 @uref{#ix86-ibm-aix,,i?86-ibm-aix}
1451 @uref{#ix86-sequent-bsd,,i?86-sequent-bsd}
1453 @uref{#ix86-sequent-ptx1*,,i?86-sequent-ptx1*, i?86-sequent-ptx2*}
1455 @uref{#ix86-*-sysv3*,,i?86-*-sysv3*}
1457 @uref{#i860-intel-osf*,,i860-intel-osf*}
1459 @uref{#ia64-*-linux,,ia64-*-linux}
1461 @uref{#*-lynx-lynxos,,*-lynx-lynxos}
1463 @uref{#*-ibm-aix*,,*-ibm-aix*}
1465 @uref{#m32r-*-elf,,m32r-*-elf}
1467 @uref{#m68000-hp-bsd,,m68000-hp-bsd}
1469 @uref{#m6811-elf,,m6811-elf}
1471 @uref{#m6812-elf,,m6812-elf}
1473 @uref{#m68k-altos,,m68k-altos}
1475 @uref{#m68k-apple-aux,,m68k-apple-aux}
1477 @uref{#m68k-att-sysv,,m68k-att-sysv}
1479 @uref{#m68k-bull-sysv,,m68k-bull-sysv}
1481 @uref{#m68k-crds-unox,,m68k-crds-unox}
1483 @uref{#m68k-hp-hpux,,m68k-hp-hpux}
1485 @uref{#m68k-*-nextstep*,,m68k-*-nextstep*}
1487 @uref{#m68k-ncr-*,,m68k-ncr-*}
1489 @uref{#m68k-sun,,m68k-sun}
1491 @uref{#m68k-sun-sunos4.1.1,,m68k-sun-sunos4.1.1}
1493 @uref{#m88k-*-svr3,,m88k-*-svr3}
1495 @uref{#m88k-*-dgux,,m88k-*-dgux}
1497 @uref{#m88k-tektronix-sysv3,,m88k-tektronix-sysv3}
1499 @uref{#mips-*-*,,mips-*-*}
1501 @uref{#mips-dec-*,,mips-dec-*}
1503 @uref{#mips-mips-bsd,,mips-mips-bsd}
1505 @uref{#mips-mips-riscos*,,mips-mips-riscos*}
1507 @uref{#mips-sgi-irix4,,mips-sgi-irix4}
1509 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
1511 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
1513 @uref{#mips-sony-sysv,,mips-sony-sysv}
1515 @uref{#ns32k-encore,,ns32k-encore}
1517 @uref{#ns32k-*-genix,,ns32k-*-genix}
1519 @uref{#ns32k-sequent,,ns32k-sequent}
1521 @uref{#ns32k-utek,,ns32k-utek}
1523 @uref{#powerpc*-*-*,,powerpc*-*-*, powerpc-*-sysv4}
1525 @uref{#powerpc-*-darwin*,,powerpc-*-darwin*}
1527 @uref{#powerpc-*-elf,,powerpc-*-elf, powerpc-*-sysv4}
1529 @uref{#powerpc-*-linux-gnu*,,powerpc-*-linux-gnu*}
1531 @uref{#powerpc-*-netbsd*,,powerpc-*-netbsd*}
1533 @uref{#powerpc-*-eabiaix,,powerpc-*-eabiaix}
1535 @uref{#powerpc-*-eabisim,,powerpc-*-eabisim}
1537 @uref{#powerpc-*-eabi,,powerpc-*-eabi}
1539 @uref{#powerpcle-*-elf,,powerpcle-*-elf, powerpcle-*-sysv4}
1541 @uref{#powerpcle-*-eabisim,,powerpcle-*-eabisim}
1543 @uref{#powerpcle-*-eabi,,powerpcle-*-eabi}
1545 @uref{#powerpcle-*-winnt,,powerpcle-*-winnt, powerpcle-*-pe}
1547 @uref{#romp-*-aos,,romp-*-aos, romp-*-mach}
1549 @uref{#s390-*-linux*}
1551 @uref{#s390x-*-linux*}
1553 @uref{#*-*-solaris2*,,*-*-solaris2*}
1555 @uref{#sparc-sun-solaris2*,,sparc-sun-solaris2*}
1557 @uref{#sparc-sun-solaris2.7,,sparc-sun-solaris2.7}
1559 @uref{#*-*-solaris2.8,,*-*-solaris2.8}
1561 @uref{#sparc-sun-sunos4*,,sparc-sun-sunos4*}
1563 @uref{#sparc-unknown-linux-gnulibc1,,sparc-unknown-linux-gnulibc1}
1565 @uref{#sparc-*-linux*,,sparc-*-linux*}
1567 @uref{#sparc64-*-*,,sparc64-*-*}
1569 @uref{#*-*-sysv*,,*-*-sysv*}
1571 @uref{#vax-dec-ultrix,,vax-dec-ultrix}
1573 @uref{#we32k-*-*,,we32k-*-*}
1575 @uref{#windows,,Microsoft Windows}
1579 @uref{#older,,Older systems}
1584 @uref{#elf_targets,,all ELF targets} (SVR4, Solaris 2, etc.)
1590 <!-- -------- host/target specific issues start here ---------------- -->
1593 @heading @anchor{1750a-*-*}1750a-*-*
1594 MIL-STD-1750A processors.
1596 The MIL-STD-1750A cross configuration produces output for
1597 @code{as1750}, an assembler/linker available under the GNU General Public
1598 License for the 1750A@. @code{as1750} can be obtained at
1599 @uref{ftp://ftp.fta-berlin.de/pub/crossgcc/1750gals/}.
1600 A similarly licensed simulator for
1601 the 1750A is available from same address.
1603 You should ignore a fatal error during the building of @samp{libgcc}
1604 (@samp{libgcc} is not yet implemented for the 1750A@.)
1606 The @code{as1750} assembler requires the file @file{ms1750.inc}, which is
1607 found in the directory @file{gcc/config/1750a}.
1609 GCC produced the same sections as the Fairchild F9450 C Compiler,
1614 The program code section.
1617 The read/write (RAM) data section.
1620 The read-only (ROM) constants section.
1623 Initialization section (code to copy KREL to SREL)@.
1626 The smallest addressable unit is 16 bits (@code{BITS_PER_UNIT} is 16). This
1627 means that type @code{char} is represented with a 16-bit word per character.
1628 The 1750A's ``Load/Store Upper/Lower Byte'' instructions are not used by
1635 @heading @anchor{a29k}a29k
1636 AMD Am29k-family processors. These are normally used in embedded
1637 applications. There are no standard Unix configurations.
1639 corresponds to AMD's standard calling sequence and binary interface
1640 and is compatible with other 29k tools.
1642 You may need to make a variant of the file @file{a29k.h} for your
1643 particular configuration.
1649 @heading @anchor{a29k-*-bsd}a29k-*-bsd
1650 AMD Am29050 used in a system running a variant of BSD Unix.
1656 @heading @anchor{alpha*-*-*}alpha*-*-*
1658 This section contains general configuration information for all
1659 alpha-based platforms using ELF (in particular, ignore this section for
1660 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
1661 section, please read all other sections that match your target.
1663 We require binutils 2.11.2 or newer.
1664 Previous binutils releases had a number of problems with DWARF 2
1665 debugging information, not the least of which is incorrect linking of
1672 @heading @anchor{alpha*-dec-osf*}alpha*-dec-osf*
1673 Systems using processors that implement the DEC Alpha architecture and
1674 are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
1675 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
1677 In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
1678 currently (2001-06-13) work with @command{mips-tfile}. As a workaround,
1679 we need to use the old assembler, invoked via the barely documented
1680 @option{-oldas} option. To bootstrap GCC, you either need to use the
1684 % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
1687 or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
1690 % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
1693 As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld}
1694 are supported on Tru64 UNIX, so you must not configure GCC with
1695 @option{--with-gnu-as} or @option{--with-gnu-ld}.
1697 The @option{--enable-threads} options isn't supported yet. A patch is
1698 in preparation for a future release. The Java runtime library has been
1699 reported to work on Tru64 UNIX V4.0F, V5.0, and V5.1, so you may try
1700 @option{--enable-libgcj} and report your results.
1702 GCC writes a @samp{.verstamp} directive to the assembler output file
1703 unless it is built as a cross-compiler. It gets the version to use from
1704 the system header file @file{/usr/include/stamp.h}. If you install a
1705 new version of DEC Unix, you should rebuild GCC to pick up the new version
1708 Note that since the Alpha is a 64-bit architecture, cross-compilers from
1709 32-bit machines will not generate code as efficient as that generated
1710 when the compiler is running on a 64-bit machine because many
1711 optimizations that depend on being able to represent a word on the
1712 target in an integral value on the host cannot be performed. Building
1713 cross-compilers on the Alpha for 32-bit machines has only been tested in
1714 a few cases and may not work properly.
1716 @code{make compare} may fail on old versions of DEC Unix unless you add
1717 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
1718 assembler input file is stored in the object file, and that makes
1719 comparison fail if it differs between the @code{stage1} and
1720 @code{stage2} compilations. The option @option{-save-temps} forces a
1721 fixed name to be used for the assembler input file, instead of a
1722 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
1723 unless the comparisons fail without that option. If you add
1724 @option{-save-temps}, you will have to manually delete the @samp{.i} and
1725 @samp{.s} files after each series of compilations.
1727 GCC now supports both the native (ECOFF) debugging format used by DBX
1728 and GDB and an encapsulated STABS format for use only with GDB@. See the
1729 discussion of the @option{--with-stabs} option of @file{configure} above
1730 for more information on these formats and how to select them.
1732 There is a bug in DEC's assembler that produces incorrect line numbers
1733 for ECOFF format when the @samp{.align} directive is used. To work
1734 around this problem, GCC will not emit such alignment directives
1735 while writing ECOFF format debugging information even if optimization is
1736 being performed. Unfortunately, this has the very undesirable
1737 side-effect that code addresses when @option{-O} is specified are
1738 different depending on whether or not @option{-g} is also specified.
1740 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
1741 DBX@. DEC is now aware of this problem with the assembler and hopes to
1742 provide a fix shortly.
1748 @heading @anchor{alphaev5-cray-unicosmk*}alphaev5-cray-unicosmk*
1749 Cray T3E systems running Unicos/Mk.
1751 This port is incomplete and has many known bugs. We hope to improve the
1752 support for this target soon. Currently, only the C front end is supported,
1753 and it is not possible to build parallel applications. Cray modules are not
1754 supported; in particular, Craylibs are assumed to be in
1755 @file{/opt/ctl/craylibs/craylibs}.
1757 You absolutely @strong{must} use GNU make on this platform. Also, you
1758 need to tell GCC where to find the assembler and the linker. The
1759 simplest way to do so is by providing @option{--with-as} and
1760 @option{--with-ld} to @file{configure}, e.g.@:
1762 @samp{configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld
1763 --enable-languages=c}
1765 The comparison test during @samp{make bootstrap} fails on Unicos/Mk
1766 because the assembler inserts timestamps into object files. You should
1767 be able to work around this by doing @samp{make all} after getting this
1774 @heading @anchor{arc-*-elf}arc-*-elf
1775 Argonaut ARC processor.
1776 This configuration is intended for embedded systems.
1782 @heading @anchor{arm-*-aout}arm-*-aout
1783 Advanced RISC Machines ARM-family processors. These are often used in
1784 embedded applications. There are no standard Unix configurations.
1785 This configuration corresponds to the basic instruction sequences and will
1786 produce @file{a.out} format object modules.
1788 You may need to make a variant of the file @file{arm.h} for your particular
1795 @heading @anchor{arm-*-elf}arm-*-elf
1796 This configuration is intended for embedded systems.
1802 @heading @anchor{arm*-*-linux-gnu}arm*-*-linux-gnu
1804 We require GNU binutils 2.10 or newer.
1810 @heading @anchor{arm-*-riscix}arm-*-riscix
1811 The ARM2 or ARM3 processor running RISC iX, Acorn's port of BSD Unix.
1812 If you are running a version of RISC iX prior to 1.2 then you must
1813 specify the version number during configuration. Note that the
1814 assembler shipped with RISC iX does not support stabs debugging
1815 information; a new version of the assembler, with stabs support
1816 included, is now available from Acorn and via ftp
1817 @uref{ftp://ftp.acorn.com/pub/riscix/as+xterm.tar.Z}. To enable stabs
1818 debugging, pass @option{--with-gnu-as} to configure.
1820 You will need to install GNU @command{sed} before you can run configure.
1826 @heading @anchor{avr}avr
1828 ATMEL AVR-family micro controllers. These are used in embedded
1829 applications. There are no standard Unix configurations.
1831 @xref{AVR Options,, AVR Options, gcc, Using and Porting the GNU Compiler
1835 See ``AVR Options'' in the main manual
1837 for the list of supported MCU types.
1839 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
1841 Further installation notes and other useful information about AVR tools
1842 can also be obtained from:
1846 @uref{http://home.overta.ru/users/denisc,,http://home.overta.ru/users/denisc}
1848 @uref{http://www.itnet.pl/amelektr/avr,,http://www.itnet.pl/amelektr/avr}
1851 We @emph{strongly} recommend using binutils 2.11 or newer.
1853 The following error:
1855 Error: register required
1858 indicates that you should upgrade to a newer version of the binutils.
1864 @heading @anchor{c4x}c4x
1866 Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal
1867 Processors. These are used in embedded applications. There are no
1868 standard Unix configurations.
1870 @xref{TMS320C3x/C4x Options,, TMS320C3x/C4x Options, gcc, Using and
1871 Porting the GNU Compiler Collection (GCC)},
1874 See ``TMS320C3x/C4x Options'' in the main manual
1876 for the list of supported MCU types.
1878 GCC can be configured as a cross compiler for both the C3x and C4x
1879 architectures on the same system. Use @samp{configure --target=c4x
1880 --enable-languages="c,c++"} to configure.
1883 Further installation notes and other useful information about C4x tools
1884 can also be obtained from:
1888 @uref{http://www.elec.canterbury.ac.nz/c4x/,,http://www.elec.canterbury.ac.nz/c4x/}
1895 @heading @anchor{cris}CRIS
1897 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
1898 series. These are used in embedded applications.
1901 @xref{CRIS Options,, CRIS Options, gcc, Using and Porting the GNU Compiler
1905 See ``CRIS Options'' in the main manual
1907 for a list of CRIS-specific options.
1909 There are a few different CRIS targets:
1911 @item cris-axis-aout
1912 Old target. Includes a multilib for the @samp{elinux} a.out-based
1913 target. No multilibs for newer architecture variants.
1915 Mainly for monolithic embedded systems. Includes a multilib for the
1916 @samp{v10} core used in @samp{ETRAX 100 LX}.
1917 @item cris-axis-linux-gnu
1918 A GNU/Linux port for the CRIS architecture, currently targeting
1919 @samp{ETRAX 100 LX} by default.
1922 For @code{cris-axis-aout} and @code{cris-axis-elf} you need binutils 2.11
1923 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
1925 Pre-packaged tools can be obtained from
1926 @uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More
1927 information about this platform is available at
1928 @uref{http://developer.axis.com/}.
1934 @heading @anchor{dos}DOS
1936 Please have a look at our @uref{binaries.html,,binaries page}.
1938 You cannot install GCC by itself on MSDOS; it will not compile under
1939 any MSDOS compiler except itself. You need to get the complete
1940 compilation package DJGPP, which includes binaries as well as sources,
1941 and includes all the necessary compilation tools and libraries.
1947 @heading @anchor{dsp16xx}dsp16xx
1948 A port to the AT&T DSP1610 family of processors.
1954 @heading @anchor{*-*-freebsd*}*-*-freebsd*
1956 The version of binutils installed in @file{/usr/bin} is known to work unless
1957 otherwise specified in any per-architecture notes. However, binutils
1958 2.11 is known to improve overall testsuite results.
1960 For FreeBSD 1, FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
1961 configuration support and files as shipped with GCC 2.95 are still in
1962 place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
1963 it is unknown which version of binutils was used (it is assumed that it
1964 was the system copy in @file{/usr/bin}) and C++ EH failures were noted.
1966 For FreeBSD using the ELF file format: DWARF 2 debugging is now the
1967 default for all CPU architectures. It had been the default on
1968 FreeBSD/alpha since its inception. You may use @option{-gstabs} instead
1969 of @option{-g}, if you really want the old debugging format. There are
1970 no known issues with mixing object files and libraries with different
1971 debugging formats. Otherwise, this release of GCC should now match more
1972 of the configuration used in the stock FreeBSD configuration of GCC. In
1973 particular, @option{--enable-threads} is now configured by default.
1974 However, as a general user, do not attempt to replace the system
1975 compiler with this release. Known to bootstrap and check with good
1976 results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3 and 5-CURRENT@.
1978 At this time, @option{--enable-threads} is not compatible with
1979 @option{--enable-libgcj} on FreeBSD@.
1985 @heading @anchor{elxsi-elxsi-bsd}elxsi-elxsi-bsd
1986 The Elxsi's C compiler has known limitations that prevent it from
1987 compiling GCC@. Please contact @email{mrs@@wrs.com} for more details.
1993 @heading @anchor{h8300-hms}h8300-hms
1994 Hitachi H8/300 series of processors.
1996 Please have a look at our @uref{binaries.html,,binaries page}.
1998 The calling convention and structure layout has changed in release 2.6.
1999 All code must be recompiled. The calling convention now passes the
2000 first three arguments in function calls in registers. Structures are no
2001 longer a multiple of 2 bytes.
2007 @heading @anchor{hppa*-hp-hpux*}hppa*-hp-hpux*
2009 We @emph{highly} recommend using gas/binutils 2.8 or newer on all hppa
2010 platforms; you may encounter a variety of problems when using the HP
2013 Specifically, @option{-g} does not work on HP-UX (since that system
2014 uses a peculiar debugging format which GCC does not know about), unless you
2015 use GAS and GDB and configure GCC with the
2016 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
2017 @option{--with-as=@dots{}} options.
2019 If you wish to use pa-risc 2.0 architecture support, you must use either
2020 the HP assembler, gas/binutils 2.11 or a recent
2021 @uref{ftp://sources.redhat.com/pub/binutils/snapshots,,snapshot of gas}.
2023 More specific information to @samp{hppa*-hp-hpux*} targets follows.
2029 @heading @anchor{hppa*-hp-hpux9}hppa*-hp-hpux9
2031 The HP assembler has major problems on this platform. We've tried to work
2032 around the worst of the problems. However, those workarounds may be causing
2033 linker crashes in some circumstances; the workarounds also probably prevent
2034 shared libraries from working. Use the GNU assembler to avoid these problems.
2037 The configuration scripts for GCC will also trigger a bug in the hpux9
2038 shell. To avoid this problem set @env{CONFIG_SHELL} to @file{/bin/ksh}
2039 and @env{SHELL} to @file{/bin/ksh} in your environment.
2046 @heading @anchor{hppa*-hp-hpux10}hppa*-hp-hpux10
2048 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
2049 @code{PHCO_19798} from HP@. HP has two sites which provide patches free of
2055 <a href="http://us-support.external.hp.com">US, Canada, Asia-Pacific, and
2059 @uref{http://us-support.external.hp.com,,}US, Canada, Asia-Pacific, and
2063 @uref{http://europe-support.external.hp.com,,Europe}
2066 The HP assembler on these systems is much better than the hpux9 assembler,
2067 but still has some problems. Most notably the assembler inserts timestamps
2068 into each object file it creates, causing the 3-stage comparison test to fail
2069 during a @samp{make bootstrap}. You should be able to continue by
2070 saying @samp{make all} after getting the failure from @samp{make
2078 @heading @anchor{hppa*-hp-hpux11}hppa*-hp-hpux11
2080 GCC 3.0 supports HP-UX 11. You must use GNU binutils 2.11 or above on
2087 @heading @anchor{i370-*-*}i370-*-*
2088 This port is very preliminary and has many known bugs. We hope to
2089 have a higher-quality port for this machine soon.
2095 @heading @anchor{*-*-linux-gnu}*-*-linux-gnu
2097 If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install
2098 out-of-the-box. You'll get compile errors while building @samp{libstdc++}.
2099 The patch @uref{glibc-2.2.patch,,glibc-2.2.patch}, that is to be
2100 applied in the GCC source tree, fixes the compatibility problems.
2110 Currently Glibc 2.2.3 (and older releases) and GCC 3.0 are out of sync
2111 since the latest exception handling changes for GCC@. Compiling glibc
2112 with GCC 3.0 will give a binary incompatible glibc and therefore cause
2113 lots of problems and might make your system completly unusable. This
2114 will definitly need fixes in glibc but might also need fixes in GCC@. We
2115 strongly advise to wait for glibc 2.2.4 and to read the release notes of
2116 glibc 2.2.4 whether patches for GCC 3.0 are needed. You can use glibc
2117 2.2.3 with GCC 3.0, just do not try to recompile it.
2123 @heading @anchor{ix86-*-linux*oldld}i?86-*-linux*oldld
2124 Use this configuration to generate @file{a.out} binaries on Linux-based
2125 GNU systems if you do not have gas/binutils version 2.5.2 or later
2126 installed. This is an obsolete configuration.
2132 @heading @anchor{ix86-*-linux*aout}i?86-*-linux*aout
2133 Use this configuration to generate @file{a.out} binaries on Linux-based
2134 GNU systems. This configuration is being superseded. You must use
2135 gas/binutils version 2.5.2 or later.
2141 @heading @anchor{ix86-*-linux*}i?86-*-linux*
2143 You will need binutils 2.9.1.0.15 or newer for exception handling to work.
2145 If you receive Signal 11 errors when building on GNU/Linux, then it is
2146 possible you have a hardware problem. Further information on this can be
2147 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
2153 @heading @anchor{ix86-*-sco}i?86-*-sco
2154 Compilation with RCC is recommended. Also, it may be a good idea to
2155 link with GNU malloc instead of the malloc that comes with the system.
2161 @heading @anchor{ix86-*-sco3.2v4}i?86-*-sco3.2v4
2162 Use this configuration for SCO release 3.2 version 4.
2168 @heading @anchor{ix86-*-sco3.2v5*}i?86-*-sco3.2v5*
2169 Use this for the SCO OpenServer Release 5 family of operating systems.
2171 Unlike earlier versions of GCC, the ability to generate COFF with this
2172 target is no longer provided.
2174 Earlier versions of GCC emitted DWARF 1 when generating ELF to allow
2175 the system debugger to be used. That support was too burdensome to
2176 maintain. GCC now emits only DWARF 2 for this target. This means you
2177 may use either the UDK debugger or GDB to debug programs built by this
2180 Use of the @option{-march=pentiumpro} flag can result in
2181 unrecognized opcodes when using the native assembler on OS versions before
2182 5.0.6. (Support for P6 opcodes was added to the native ELF assembler in
2183 that version.) While it's rather rare to see these emitted by GCC yet,
2184 errors of the basic form:
2187 /usr/tmp/ccaNlqBc.s:22:unknown instruction: fcomip
2188 /usr/tmp/ccaNlqBc.s:50:unknown instruction: fucomip
2191 are symptoms of this problem. You may work around this by not
2192 building affected files with that flag, by using the GNU assembler, or
2193 by using the assembler provided with the current version of the OS@.
2194 Users of GNU assembler should see the note below for hazards on doing
2197 The native SCO assembler that is provided with the OS at no
2198 charge is normally required. If, however, you must be able to use
2199 the GNU assembler (perhaps you're compiling code with asms that
2200 require GAS syntax) you may configure this package using the flags
2201 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You must
2202 use a recent version of GNU binutils; versions past 2.9.1 seem to work
2205 In general, the @option{--with-gnu-as} option isn't as well tested
2206 as the native assembler.
2208 Look in @file{gcc/config/i386/sco5.h} (search for ``messy'') for
2209 additional OpenServer-specific flags.
2211 Systems based on OpenServer before 5.0.4 (@samp{uname -X}
2212 will tell you what you're running) require TLS597 from
2213 @uref{ftp://ftp.sco.com/TLS/,,ftp://ftp.sco.com/TLS/}
2214 for C++ constructors and destructors to work right.
2216 The system linker in (at least) 5.0.4 and 5.0.5 will sometimes
2217 do the wrong thing for a construct that GCC will emit for PIC
2218 code. This can be seen as execution testsuite failures when using
2219 @option{-fPIC} on @file{921215-1.c}, @file{931002-1.c}, @file{nestfunc-1.c}, and @file{gcov-1.c}.
2220 For 5.0.5, an updated linker that will cure this problem is
2221 available. You must install both
2222 @uref{ftp://ftp.sco.com/Supplements/rs505a/,,ftp://ftp.sco.com/Supplements/rs505a/}
2223 and @uref{ftp://ftp.sco.com/SLS/,,OSS499A}.
2225 The dynamic linker in OpenServer 5.0.5 (earlier versions may show
2226 the same problem) aborts on certain G77-compiled programs. It's particularly
2227 likely to be triggered by building Fortran code with the @option{-fPIC} flag.
2228 Although it's conceivable that the error could be triggered by other
2229 code, only G77-compiled code has been observed to cause this abort.
2230 If you are getting core dumps immediately upon execution of your
2231 G77 program---and especially if it's compiled with @option{-fPIC}---try applying
2232 @uref{sco_osr5_g77.patch,,@file{sco_osr5_g77.patch}} to your @samp{libf2c} and
2234 Affected faults, when analyzed in a debugger, will show a stack
2235 backtrace with a fault occurring in @code{rtld()} and the program
2236 running as @file{/usr/lib/ld.so.1}. This problem has been reported to SCO
2237 engineering and will hopefully be addressed in later releases.
2244 @heading @anchor{ix86-*-udk}i?86-*-udk
2246 This target emulates the SCO Universal Development Kit and requires that
2247 package be installed. (If it is installed, you will have a
2248 @file{/udk/usr/ccs/bin/cc} file present.) It's very much like the
2249 @samp{i?86-*-unixware7*} target
2250 but is meant to be used when hosting on a system where UDK isn't the
2251 default compiler such as OpenServer 5 or Unixware 2. This target will
2252 generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
2253 with the same warnings and caveats as the SCO UDK@.
2255 This target is a little tricky to build because we have to distinguish
2256 it from the native tools (so it gets headers, startups, and libraries
2257 from the right place) while making the tools not think we're actually
2258 building a cross compiler. The easiest way to do this is with a configure
2261 @samp{CC=/udk/usr/ccs/bin/cc @var{/your/path/to}/gcc/configure
2262 --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-}
2264 @emph{You should substitute @samp{i686} in the above command with the appropriate
2265 processor for your host.}
2267 After the usual @samp{make bootstrap} and
2268 @samp{make install}, you can then access the UDK-targeted GCC
2269 tools by adding @command{udk-} before the commonly known name. For
2270 example, to invoke the C compiler, you would use @command{udk-gcc}.
2271 They will coexist peacefully with any native-target GCC tools you may
2279 @heading @anchor{ix86-*-isc}i?86-*-isc
2280 It may be a good idea to link with GNU malloc instead of the malloc that
2281 comes with the system.
2283 In ISC version 4.1, @command{sed} core dumps when building
2284 @file{deduced.h}. Use the version of @command{sed} from version 4.0.
2290 @heading @anchor{ix86-*-esix}i?86-*-esix
2291 It may be good idea to link with GNU malloc instead of the malloc that
2292 comes with the system.
2298 @heading @anchor{ix86-ibm-aix}i?86-ibm-aix
2299 You need to use GAS version 2.1 or later, and LD from
2300 GNU binutils version 2.2 or later.
2306 @heading @anchor{ix86-sequent-bsd}i?86-sequent-bsd
2307 Go to the Berkeley universe before compiling.
2313 @heading @anchor{ix86-sequent-ptx1*}i?86-sequent-ptx1*, i?86-sequent-ptx2*
2314 You must install GNU @command{sed} before running @command{configure}.
2320 @heading @anchor{#ix86-*-sysv3*}i?86-*-sysv3*
2321 The @code{fixproto} shell script may trigger a bug in the system shell.
2322 If you encounter this problem, upgrade your operating system or
2323 use @command{bash} (the GNU shell) to run @code{fixproto}.
2330 @heading @anchor{i860-intel-osf*}i860-intel-osf*
2331 On the Intel Paragon (an i860 machine), if you are using operating
2332 system version 1.0, you will get warnings or errors about redefinition
2333 of @code{va_arg} when you build GCC@.
2335 If this happens, then you need to link most programs with the library
2336 @file{iclib.a}. You must also modify @file{stdio.h} as follows: before
2340 #if defined(__i860__) && !defined(_VA_LIST)
2341 #include <va_list.h>
2355 extern int vprintf(const char *, va_list );
2356 extern int vsprintf(char *, const char *, va_list );
2364 #endif /* __PGC__ */
2367 These problems don't exist in operating system version 1.1.
2373 @heading @anchor{ia64-*-linux}ia64-*-linux
2374 IA-64 processor (also known as IPF, or Itanium Processor Family)
2377 The toolchain is not completely finished, so requirements will continue
2379 GCC 3.0.1 and later require glibc 2.2.4.
2380 GCC 3.0.2 requires binutils from 2001-09-05 or later.
2381 GCC 3.0.1 requires binutils 2.11.1 or later.
2383 None of the following versions of GCC has an ABI that is compatible
2384 with any of the other versions in this list, with the exception that
2385 Red Hat 2.96 and Trillian 000171 are compatible with each other:
2386 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
2387 This primarily affects C++ programs and programs that create shared libraries.
2388 Because of these ABI incompatibilities, GCC 3.0.2 is not recommended for
2389 user programs on GNU/Linux systems built using earlier compiler releases.
2390 GCC 3.0.2 is recommended for compiling linux, the kernel.
2391 GCC 3.0.2 is believed to be fully ABI compliant, and hence no more major
2392 ABI changes are expected.
2398 @heading @anchor{*-lynx-lynxos}*-lynx-lynxos
2399 LynxOS 2.2 and earlier comes with GCC 1.x already installed as
2400 @file{/bin/gcc}. You should compile with this instead of @file{/bin/cc}.
2401 You can tell GCC to use the GNU assembler and linker, by specifying
2402 @samp{--with-gnu-as --with-gnu-ld} when configuring. These will produce
2403 COFF format object files and executables; otherwise GCC will use the
2404 installed tools, which produce @file{a.out} format executables.
2409 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
2411 @heading @anchor{*-ibm-aix*}*-ibm-aix*
2413 AIX Make frequently has problems with GCC makefiles. GNU Make 3.76 or
2414 newer is recommended to build on this platform.
2416 Errors involving @code{alloca} when building GCC generally are due
2417 to an incorrect definition of @code{CC} in the Makefile or mixing files
2418 compiled with the native C compiler and GCC@. During the stage1 phase of
2419 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
2420 (not @command{xlc}). Once @command{configure} has been informed of
2421 @command{xlc}, one needs to use @samp{make distclean} to remove the
2422 configure cache files and ensure that @env{CC} environment variable
2423 does not provide a definition that will confuse @command{configure}.
2424 If this error occurs during stage2 or later, then the problem most likely
2425 is the version of Make (see above).
2427 Binutils 2.10 does not support AIX 4.3. Binutils available from the
2428 @uref{http://www-1.ibm.com/servers/aix/products/aixos/linux/,,AIX
2429 Toolbox for Linux: GNU and Open Source tools for AIX};
2430 website does work. Binutils 2.11 is expected to include AIX 4.3
2431 support. The GNU Assembler is necessary for @samp{libstdc++} to build. The
2432 AIX native @command{ld} still is recommended. The native AIX tools do
2433 interoperate with GCC@.
2435 Linking executables and shared libraries may produce warnings of
2436 duplicate symbols. The assembly files generated by GCC for AIX always
2437 have included multiple symbol definitions for certain global variable
2438 and function declarations in the original program. The warnings should
2439 not prevent the linker from producing a correct library or runnable
2442 GCC's exception handling implementation stores process-specific data in
2443 the shared library which prevents exception handling from working
2444 correctly on AIX in a default installation. To work around this, the
2445 shared objects need to be loaded in the process private segment to
2446 prevent them from being shared and marked read-only. This is
2447 accomplished on AIX by installing the shared libraries
2448 (@file{libgcc_s.a} and @file{libstdc++.a}) with file permissions
2449 disallowing read-other (@samp{chmod a+x,o-r}). If the shared libraries
2450 have been used, the shared library segment can be cleaned using the
2451 @samp{/usr/sbin/slibclean} command.
2453 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
2454 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
2455 to parse archive libraries did not handle the new format correctly.
2456 These routines are used by GCC and result in error messages during
2457 linking such as ``not a COFF file''. The version of the routines shipped
2458 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
2459 option of the archive command may be used to create archives of 32-bit
2460 objects using the original ``small format''. A correct version of the
2461 routines is shipped with AIX 4.3.2 and above.
2463 Some versions of the AIX binder (linker) can fail with a relocation
2464 overflow severe error when the @option{-bbigtoc} option is used to link
2465 GCC-produced object files into an executable that overflows the TOC@. A fix
2466 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
2467 available from IBM Customer Support and from its
2468 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2469 website as PTF U455193.
2471 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
2472 with a segmentation fault when invoked by any version of GCC@. A fix for
2473 APAR IX87327 is available from IBM Customer Support and from its
2474 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2475 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
2477 The initial assembler shipped with AIX 4.3.0 generates incorrect object
2478 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
2479 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
2480 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2481 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
2483 AIX provides National Language Support (NLS)@. Compilers and assemblers
2484 use NLS to support locale-specific representations of various data
2485 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
2486 separating decimal fractions). There have been problems reported where
2487 GCC does not produce the same floating-point formats that the assembler
2488 expects. If one encounters this problem, set the @env{LANG}
2489 environment variable to @samp{C} or @samp{En_US}.
2491 By default, GCC for AIX 4.1 and above produces code that can be used on
2492 both Power or PowerPC processors.
2494 A default can be specified with the @option{-mcpu=@var{cpu_type}}
2495 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
2501 @heading @anchor{m32r-*-elf}m32r-*-elf
2502 Mitsubishi M32R processor.
2503 This configuration is intended for embedded systems.
2509 @heading @anchor{m68000-hp-bsd}m68000-hp-bsd
2510 HP 9000 series 200 running BSD@. Note that the C compiler that comes
2511 with this system cannot compile GCC; contact @email{law@@cygnus.com}
2512 to get binaries of GCC for bootstrapping.
2518 @heading @anchor{m6811-elf}m6811-elf
2519 Motorola 68HC11 family micro controllers. These are used in embedded
2520 applications. There are no standard Unix configurations.
2526 @heading @anchor{m6812-elf}m6812-elf
2527 Motorola 68HC12 family micro controllers. These are used in embedded
2528 applications. There are no standard Unix configurations.
2534 @heading @anchor{m68k-altos}m68k-altos
2535 Altos 3068. You must use the GNU assembler, linker and debugger.
2536 Also, you must fix a kernel bug.
2542 @heading @anchor{m68k-apple-aux}m68k-apple-aux
2543 Apple Macintosh running A/UX@.
2544 You may configure GCC to use either the system assembler and
2545 linker or the GNU assembler and linker. You should use the GNU configuration
2546 if you can, especially if you also want to use G++. You enable
2547 that configuration with the @option{--with-gnu-as} and @option{--with-gnu-ld}
2548 options to @code{configure}.
2550 Note the C compiler that comes
2551 with this system cannot compile GCC@. You can find binaries of GCC
2552 for bootstrapping on @code{jagubox.gsfc.nasa.gov}.
2553 You will also a patched version of @file{/bin/ld} there that
2554 raises some of the arbitrary limits found in the original.
2560 @heading @anchor{m68k-att-sysv}m68k-att-sysv
2561 AT&T 3b1, a.k.a.@: 7300 PC@. This version of GCC cannot
2562 be compiled with the system C compiler, which is too buggy.
2563 You will need to get a previous version of GCC and use it to
2564 bootstrap. Binaries are available from the OSU-CIS archive, at
2565 @uref{ftp://archive.cis.ohio-state.edu/pub/att7300/}.
2571 @heading @anchor{m68k-bull-sysv}m68k-bull-sysv
2572 Bull DPX/2 series 200 and 300 with BOS-2.00.45 up to BOS-2.01. GCC works
2573 either with native assembler or GNU assembler. You can use
2574 GNU assembler with native COFF generation by providing @option{--with-gnu-as} to
2575 the configure script or use GNU assembler with stabs-in-COFF encapsulation
2576 by providing @samp{--with-gnu-as --stabs}. For any problem with the native
2577 assembler or for availability of the DPX/2 port of GAS, contact
2578 @email{F.Pierresteguy@@frcl.bull.fr}.
2584 @heading @anchor{m68k-crds-unox}m68k-crds-unox
2585 Use @samp{configure unos} for building on Unos.
2587 The Unos assembler is named @code{casm} instead of @code{as}. For some
2588 strange reason linking @file{/bin/as} to @file{/bin/casm} changes the
2589 behavior, and does not work. So, when installing GCC, you should
2590 install the following script as @file{as} in the subdirectory where
2591 the passes of GCC are installed:
2598 The default Unos library is named @file{libunos.a} instead of
2599 @file{libc.a}. To allow GCC to function, either change all
2600 references to @option{-lc} in @file{gcc.c} to @option{-lunos} or link
2601 @file{/lib/libc.a} to @file{/lib/libunos.a}.
2603 @cindex @code{alloca}, for Unos
2604 When compiling GCC with the standard compiler, to overcome bugs in
2605 the support of @code{alloca}, do not use @option{-O} when making stage 2.
2606 Then use the stage 2 compiler with @option{-O} to make the stage 3
2607 compiler. This compiler will have the same characteristics as the usual
2608 stage 2 compiler on other systems. Use it to make a stage 4 compiler
2609 and compare that with stage 3 to verify proper compilation.
2611 (Perhaps simply defining @code{ALLOCA} in @file{x-crds} as described in
2612 the comments there will make the above paragraph superfluous. Please
2613 inform us of whether this works.)
2615 Unos uses memory segmentation instead of demand paging, so you will need
2616 a lot of memory. 5 Mb is barely enough if no other tasks are running.
2617 If linking @file{cc1} fails, try putting the object files into a library
2618 and linking from that library.
2624 @heading @anchor{m68k-hp-hpux}m68k-hp-hpux
2625 HP 9000 series 300 or 400 running HP-UX@. HP-UX version 8.0 has a bug in
2626 the assembler that prevents compilation of GCC@. This
2627 bug manifests itself during the first stage of compilation, while
2628 building @file{libgcc2.a}:
2632 cc1: warning: `-g' option not supported on this version of GCC
2633 cc1: warning: `-g1' option not supported on this version of GCC
2634 ./xgcc: Internal compiler error: program as got fatal signal 11
2637 A patched version of the assembler is available as the file
2638 @uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you
2639 have HP software support, the patch can also be obtained directly from
2640 HP, as described in the following note:
2643 This is the patched assembler, to patch SR#1653-010439, where the
2644 assembler aborts on floating point constants.
2646 The bug is not really in the assembler, but in the shared library
2647 version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is
2648 SR#4701-078451. Anyway, the attached assembler uses the archive
2649 library version of ``cvtnum(3c)'' and thus does not exhibit the bug.
2652 This patch is also known as PHCO_4484.
2654 In addition, if you wish to use gas, you must use
2655 gas version 2.1 or later, and you must use the GNU linker version 2.1 or
2656 later. Earlier versions of gas relied upon a program which converted the
2657 gas output into the native HP-UX format, but that program has not been
2658 kept up to date. gdb does not understand that native HP-UX format, so
2659 you must use gas if you wish to use gdb.
2661 On HP-UX version 8.05, but not on 8.07 or more recent versions, the
2662 @code{fixproto} shell script triggers a bug in the system shell. If you
2663 encounter this problem, upgrade your operating system or use BASH (the
2664 GNU shell) to run @code{fixproto}. This bug will cause the fixproto
2665 program to report an error of the form:
2668 ./fixproto: sh internal 1K buffer overflow
2671 To fix this, you can also change the first line of the fixproto script
2683 @heading @anchor{m68k-*-nextstep*}m68k-*-nextstep*
2685 Current GCC versions probably do not work on version 2 of the NeXT
2688 On NeXTStep 3.0, the Objective-C compiler does not work, due,
2689 apparently, to a kernel bug that it happens to trigger. This problem
2690 does not happen on 3.1.
2692 You absolutely @strong{must} use GNU sed and GNU make on this platform.
2695 On NeXTSTEP 3.x where x < 3 the build of GCC will abort during
2696 stage1 with an error message like this:
2700 /usr/tmp/ccbbsZ0U.s:987:Unknown pseudo-op: .section
2701 /usr/tmp/ccbbsZ0U.s:987:Rest of line ignored. 1st junk character
2705 The reason for this is the fact that NeXT's assembler for these
2706 versions of the operating system does not support the @samp{.section}
2707 pseudo op that's needed for full C++ exception functionality.
2709 As NeXT's assembler is a derived work from GNU as, a free
2710 replacement that does can be obtained at
2711 @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}.
2713 If you try to build the integrated C++ & C++ runtime libraries on this system
2714 you will run into trouble with include files. The way to get around this is
2715 to use the following sequence. Note you must have write permission to
2716 the directory @var{prefix} you specified in the configuration process of GCC
2717 for this sequence to work.
2721 make all-texinfo all-bison all-byacc all-binutils all-gas all-ld
2724 make install-headers-tar
2733 @heading @anchor{m68k-ncr-*}m68k-ncr-*
2734 On the Tower models 4@var{n}0 and 6@var{n}0, by default a process is not
2735 allowed to have more than one megabyte of memory. GCC cannot compile
2736 itself (or many other programs) with @option{-O} in that much memory.
2738 To solve this problem, reconfigure the kernel adding the following line
2739 to the configuration file:
2750 @heading @anchor{m68k-sun}m68k-sun
2751 Sun 3. We do not provide a configuration file to use the Sun FPA by
2752 default, because programs that establish signal handlers for floating
2753 point traps inherently cannot work with the FPA@.
2759 @heading @anchor{m68k-sun-sunos4.1.1}m68k-sun-sunos4.1.1
2761 It is reported that you may need the GNU assembler on this platform.
2768 @heading @anchor{m88k-*-svr3}m88k-*-svr3
2769 Motorola m88k running the AT&T/Unisoft/Motorola V.3 reference port.
2770 These systems tend to use the Green Hills C, revision 1.8.5, as the
2771 standard C compiler. There are apparently bugs in this compiler that
2772 result in object files differences between stage 2 and stage 3. If this
2773 happens, make the stage 4 compiler and compare it to the stage 3
2774 compiler. If the stage 3 and stage 4 object files are identical, this
2775 suggests you encountered a problem with the standard C compiler; the
2776 stage 3 and 4 compilers may be usable.
2778 It is best, however, to use an older version of GCC for bootstrapping
2785 @heading @anchor{m88k-*-dgux}m88k-*-dgux
2786 Motorola m88k running DG/UX@. To build 88open BCS native or cross
2787 compilers on DG/UX, specify the configuration name as
2788 @samp{m88k-*-dguxbcs} and build in the 88open BCS software development
2789 environment. To build ELF native or cross compilers on DG/UX, specify
2790 @samp{m88k-*-dgux} and build in the DG/UX ELF development environment.
2791 You set the software development environment by issuing
2792 @samp{sde-target} command and specifying either @samp{m88kbcs} or
2793 @samp{m88kdguxelf} as the operand.
2795 If you do not specify a configuration name, @file{configure} guesses the
2796 configuration based on the current software development environment.
2802 @heading @anchor{m88k-tektronix-sysv3}m88k-tektronix-sysv3
2803 Tektronix XD88 running UTekV 3.2e. Do not turn on
2804 optimization while building stage1 if you bootstrap with
2805 the buggy Green Hills compiler. Also, the bundled LAI
2806 System V NFS is buggy so if you build in an NFS mounted
2807 directory, start from a fresh reboot, or avoid NFS all together.
2808 Otherwise you may have trouble getting clean comparisons
2815 @heading @anchor{mips-*-*}mips-*-*
2816 If you use the 1.31 version of the MIPS assembler (such as was shipped
2817 with Ultrix 3.1), you will need to use the @option{-fno-delayed-branch} switch
2818 when optimizing floating point code. Otherwise, the assembler will
2819 complain when the GCC compiler fills a branch delay slot with a
2820 floating point instruction, such as @code{add.d}.
2822 If on a MIPS system you get an error message saying ``does not have gp
2823 sections for all it's [sic] sectons [sic]'', don't worry about it. This
2824 happens whenever you use GAS with the MIPS linker, but there is not
2825 really anything wrong, and it is okay to use the output file. You can
2826 stop such warnings by installing the GNU linker.
2828 It would be nice to extend GAS to produce the gp tables, but they are
2829 optional, and there should not be a warning about their absence.
2831 Users have reported some problems with version 2.0 of the MIPS
2832 compiler tools that were shipped with Ultrix 4.1. Version 2.10
2833 which came with Ultrix 4.2 seems to work fine.
2835 Users have also reported some problems with version 2.20 of the
2836 MIPS compiler tools that were shipped with RISC/os 4.x. The earlier
2837 version 2.11 seems to work fine.
2839 Some versions of the MIPS linker will issue an assertion failure
2840 when linking code that uses @code{alloca} against shared
2841 libraries on RISC-OS 5.0, and DEC's OSF/1 systems. This is a bug
2842 in the linker, that is supposed to be fixed in future revisions.
2843 To protect against this, GCC passes @option{-non_shared} to the
2844 linker unless you pass an explicit @option{-shared} or
2845 @option{-call_shared} switch.
2847 @heading @anchor{mips-mips-bsd}mips-mips-bsd
2848 MIPS machines running the MIPS operating system in BSD mode. It's
2849 possible that some old versions of the system lack the functions
2850 @code{memcpy}, @code{memmove}, @code{memcmp}, and @code{memset}. If your
2851 system lacks these, you must remove or undo the definition of
2852 @code{TARGET_MEM_FUNCTIONS} in @file{mips-bsd.h}.
2854 If you use the MIPS C compiler to bootstrap, it may be necessary
2855 to increase its table size for switch statements with the
2856 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
2857 optimization option, you also need to use @option{-Olimit 3000}.
2858 Both of these options are automatically generated in the
2859 @file{Makefile} that the shell script @file{configure} builds.
2860 If you override the @code{CC} make variable and use the MIPS
2861 compilers, you may need to add @option{-Wf,-XNg1500 -Olimit 3000}.
2867 @heading @anchor{mips-dec-*}mips-dec-*
2868 MIPS-based DECstations can support three different personalities:
2869 Ultrix, DEC OSF/1, and OSF/rose. (Alpha-based DECstation products have
2870 a configuration name beginning with @samp{alpha*-dec}.) To configure GCC
2871 for these platforms use the following configurations:
2874 @item mips-dec-ultrix
2875 Ultrix configuration.
2878 DEC's version of OSF/1.
2880 @item mips-dec-osfrose
2881 Open Software Foundation reference port of OSF/1 which uses the
2882 OSF/rose object file format instead of ECOFF@. Normally, you
2883 would not select this configuration.
2886 If you use the MIPS C compiler to bootstrap, it may be necessary
2887 to increase its table size for switch statements with the
2888 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
2889 optimization option, you also need to use @option{-Olimit 3000}.
2890 Both of these options are automatically generated in the
2891 @file{Makefile} that the shell script @file{configure} builds.
2892 If you override the @code{CC} make variable and use the MIPS
2893 compilers, you may need to add @option{-Wf,-XNg1500 -Olimit 3000}.
2899 @heading @anchor{mips-mips-riscos*}mips-mips-riscos*
2900 If you use the MIPS C compiler to bootstrap, it may be necessary
2901 to increase its table size for switch statements with the
2902 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
2903 optimization option, you also need to use @option{-Olimit 3000}.
2904 Both of these options are automatically generated in the
2905 @file{Makefile} that the shell script @file{configure} builds.
2906 If you override the @code{CC} make variable and use the MIPS
2907 compilers, you may need to add @samp{-Wf,-XNg1500 -Olimit 3000}.
2909 MIPS computers running RISC-OS can support four different
2910 personalities: default, BSD 4.3, System V.3, and System V.4
2911 (older versions of RISC-OS don't support V.4). To configure GCC
2912 for these platforms use the following configurations:
2915 @item mips-mips-riscos@var{rev}
2916 Default configuration for RISC-OS, revision @var{rev}.
2918 @item mips-mips-riscos@var{rev}bsd
2919 BSD 4.3 configuration for RISC-OS, revision @var{rev}.
2921 @item mips-mips-riscos@var{rev}sysv4
2922 System V.4 configuration for RISC-OS, revision @var{rev}.
2928 @item mips-mips-riscos@var{rev}sysv
2929 System V.3 configuration for RISC-OS, revision @var{rev}.
2932 The revision @code{rev} mentioned above is the revision of
2933 RISC-OS to use. You must reconfigure GCC when going from a
2934 RISC-OS revision 4 to RISC-OS revision 5. This has the effect of
2935 avoiding a linker bug.
2941 @heading @anchor{mips-sgi-irix4}mips-sgi-irix4
2943 In order to compile GCC on an SGI running IRIX 4, the ``c.hdr.lib''
2944 option must be installed from the CD-ROM supplied from Silicon Graphics.
2945 This is found on the 2nd CD in release 4.0.1.
2947 On IRIX version 4.0.5F, and perhaps on some other versions as well,
2948 there is an assembler bug that reorders instructions incorrectly. To
2949 work around it, specify the target configuration
2950 @samp{mips-sgi-irix4loser}. This configuration inhibits assembler
2953 In a compiler configured with target @samp{mips-sgi-irix4}, you can turn
2954 off assembler optimization by using the @option{-noasmopt} option. This
2955 compiler option passes the option @option{-O0} to the assembler, to
2958 The @option{-noasmopt} option can be useful for testing whether a problem
2959 is due to erroneous assembler reordering. Even if a problem does not go
2960 away with @option{-noasmopt}, it may still be due to assembler
2961 reordering---perhaps GCC itself was miscompiled as a result.
2963 You may get the following warning on IRIX 4 platforms, it can be safely
2966 warning: foo.o does not have gp tables for all its sections.
2973 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
2975 This configuration has considerable problems, which will be fixed in a
2978 In order to compile GCC on an SGI running IRIX 5, the ``compiler_dev.hdr''
2979 subsystem must be installed from the IDO CD-ROM supplied by Silicon
2980 Graphics. It is also available for download from
2981 @uref{http://www.sgi.com/developers/devtools/apis/ido.html,,http://www.sgi.com/developers/devtools/apis/ido.html}.
2983 @code{make compare} may fail on version 5 of IRIX unless you add
2984 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
2985 assembler input file is stored in the object file, and that makes
2986 comparison fail if it differs between the @code{stage1} and
2987 @code{stage2} compilations. The option @option{-save-temps} forces a
2988 fixed name to be used for the assembler input file, instead of a
2989 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
2990 unless the comparisons fail without that option. If you do you
2991 @option{-save-temps}, you will have to manually delete the @samp{.i} and
2992 @samp{.s} files after each series of compilations.
2994 If you use the MIPS C compiler to bootstrap, it may be necessary
2995 to increase its table size for switch statements with the
2996 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
2997 optimization option, you also need to use @option{-Olimit 3000}.
2999 To enable debugging under IRIX 5, you must use GNU @command{as} 2.11.2
3001 and use the @option{--with-gnu-as} configure option when configuring GCC.
3002 GNU @command{as} is distributed as part of the binutils package.
3003 When using release 2.11.2, you need to apply a patch
3004 @uref{http://sources.redhat.com/ml/binutils/2001-07/msg00352.html,,http://sources.redhat.com/ml/binutils/2001-07/msg00352.html}
3005 which will be included in the next release of binutils.
3007 When building GCC, the build process loops rebuilding @command{cc1} over
3008 and over again. This happens on @samp{mips-sgi-irix5.2}, and possibly
3009 other platforms. It has been reported that this is a known bug in the
3010 @command{make} shipped with IRIX 5.2. We recommend you use GNU
3011 @command{make} instead of the vendor supplied @command{make} program;
3012 however, you may have success with @command{smake} on IRIX 5.2 if you do
3013 not have GNU @command{make} available.
3019 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
3021 If you are using IRIX @command{cc} as your bootstrap compiler, you must
3022 ensure that the N32 ABI is in use. To test this, compile a simple C
3023 file with @command{cc} and then run @command{file} on the
3024 resulting object file. The output should look like:
3027 test.o: ELF N32 MSB @dots{}
3033 test.o: ELF 32-bit MSB @dots{}
3039 test.o: ELF 64-bit MSB @dots{}
3042 then your version of @command{cc} uses the O32 or N64 ABI by default. You
3043 should set the environment variable @env{CC} to @samp{cc -n32}
3044 before configuring GCC@.
3046 GCC on IRIX 6 is usually built to support both the N32 and N64 ABIs. If
3047 you build GCC on a system that doesn't have the N64 libraries installed,
3048 you need to configure with @option{--disable-multilib} so GCC doesn't
3049 try to use them. Look for @file{/usr/lib64/libc.so.1} to see if you
3050 have the 64-bit libraries installed.
3052 You must @emph{not} use GNU @command{as} (which isn't built anyway as of
3053 binutils 2.11.2) on IRIX 6 platforms; doing so will only cause problems.
3055 GCC does not currently support generating O32 ABI binaries in the
3056 @samp{mips-sgi-irix6} configurations. It is possible to create a GCC
3057 with O32 ABI only support by configuring it for the @samp{mips-sgi-irix5}
3058 target and using a patched GNU @command{as} 2.11.2 as documented in the
3059 @uref{#mips-sgi-irix5,,@samp{mips-sgi-irix5}} section above. Using the
3060 native assembler requires patches to GCC which will be included in a
3061 future release. It is
3062 expected that O32 ABI support will be available again in a future release.
3064 The @option{--enable-threads} option doesn't currently work, a patch is
3065 in preparation for a future release. The @option{--enable-libgcj}
3066 option is disabled by default: IRIX 6 uses a very low default limit
3067 (20480) for the command line length. Although libtool contains a
3068 workaround for this problem, at least the N64 @samp{libgcj} is known not
3069 to build despite this, running into an internal error of the native
3070 @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
3071 its maximum of 262144 bytes. If you have root access, you can use the
3072 @command{systune} command to do this.
3074 GCC does not correctly pass/return structures which are
3075 smaller than 16 bytes and which are not 8 bytes. The problem is very
3076 involved and difficult to fix. It affects a number of other targets also,
3077 but IRIX 6 is affected the most, because it is a 64 bit target, and 4 byte
3078 structures are common. The exact problem is that structures are being padded
3079 at the wrong end, e.g.@: a 4 byte structure is loaded into the lower 4 bytes
3080 of the register when it should be loaded into the upper 4 bytes of the
3083 GCC is consistent with itself, but not consistent with the SGI C compiler
3084 (and the SGI supplied runtime libraries), so the only failures that can
3085 happen are when there are library functions that take/return such
3086 structures. There are very few such library functions. Currently this
3087 is known to affect @code{inet_ntoa}, @code{inet_lnaof},
3088 @code{inet_netof}, @code{inet_makeaddr}, and @code{semctl}. Until the
3089 bug is fixed, GCC contains workarounds for the known affected functions.
3091 See @uref{http://freeware.sgi.com/,,http://freeware.sgi.com/} for more
3092 information about using GCC on IRIX platforms.
3098 @heading @anchor{mips-sony-sysv}mips-sony-sysv
3099 Sony MIPS NEWS@. This works in NEWSOS 5.0.1, but not in 5.0.2 (which
3100 uses ELF instead of COFF)@. Support for 5.0.2 will probably be provided
3101 soon by volunteers. In particular, the linker does not like the
3102 code generated by GCC when shared libraries are linked in.
3109 @heading @anchor{ns32k-encore}ns32k-encore
3110 Encore ns32000 system. Encore systems are supported only under BSD@.
3116 @heading @anchor{ns32k-*-genix}ns32k-*-genix
3117 National Semiconductor ns32000 system. Genix has bugs in @code{alloca}
3118 and @code{malloc}; you must get the compiled versions of these from GNU
3125 @heading @anchor{ns32k-sequent}ns32k-sequent
3126 Go to the Berkeley universe before compiling.
3132 @heading @anchor{ns32k-utek}ns32k-utek
3133 UTEK ns32000 system (``merlin''). The C compiler that comes with this
3134 system cannot compile GCC; contact @samp{tektronix!reed!mason} to get
3135 binaries of GCC for bootstrapping.
3142 @heading @anchor{powerpc*-*-*}powerpc-*-*
3144 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
3145 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
3151 @heading @anchor{powerpc-*-darwin*}powerpc-*-darwin*
3152 PowerPC running Darwin (Mac OS X kernel).
3154 GCC 3.0 does not support Darwin, but 3.1 and later releases will work.
3156 Pre-installed versions of Mac OS X may not include any developer tools,
3157 meaning that you will not be able to build GCC from source. Tool
3158 binaries are available at
3159 @uref{http://www.opensource.apple.com/projects/darwin} (free
3160 registration required).
3162 Versions of the assembler prior to ``cctools-364'' cannot handle the
3163 4-argument form of rlwinm and related mask-using instructions. Darwin
3164 1.3 (Mac OS X 10.0) uses cctools-353 for instance. To get cctools-364,
3165 check out @file{cctools} with tag @samp{Apple-364}, build it, and
3166 install the assembler as @file{usr/bin/as}. See
3167 @uref{http://www.opensource.apple.com/tools/cvs/docs.html} for details.
3169 Also, the default stack limit of 512K is too small, and a bootstrap will
3170 typically fail when self-compiling @file{expr.c}. Set the stack to 800K
3171 or more, for instance by doing @samp{limit stack 800}. It's also
3172 convenient to use the GNU preprocessor instead of Apple's during the
3173 first stage of bootstrapping; this is automatic when doing @samp{make
3174 bootstrap}, but to do it from the toplevel objdir you will need to say
3175 @samp{make CC='cc -no-cpp-precomp' bootstrap}.
3177 Note that the version of GCC shipped by Apple typically includes a
3178 number of extensions not available in a standard GCC release. These
3179 extensions are generally specific to Mac programming.
3185 @heading @anchor{powerpc-*-elf}powerpc-*-elf, powerpc-*-sysv4
3186 PowerPC system in big endian mode, running System V.4.
3192 @heading @anchor{powerpc-*-linux-gnu*}powerpc-*-linux-gnu*
3195 @uref{ftp://ftp.varesearch.com/pub/support/hjl/binutils,,binutils 2.9.4.0.8}
3196 or newer for a working GCC@. It is strongly recommended to recompile binutils
3197 if you initially built it with gcc-2.7.2.x.
3203 @heading @anchor{powerpc-*-netbsd*}powerpc-*-netbsd*
3204 PowerPC system in big endian mode running NetBSD@. To build the
3205 documentation you will need Texinfo version 4.0 (NetBSD 1.5.1 included
3206 Texinfo version 3.12).
3212 @heading @anchor{powerpc-*-eabiaix}powerpc-*-eabiaix
3213 Embedded PowerPC system in big endian mode with @option{-mcall-aix} selected as
3220 @heading @anchor{powerpc-*-eabisim}powerpc-*-eabisim
3221 Embedded PowerPC system in big endian mode for use in running under the
3228 @heading @anchor{powerpc-*-eabi}powerpc-*-eabi
3229 Embedded PowerPC system in big endian mode.
3235 @heading @anchor{powerpcle-*-elf}powerpcle-*-elf, powerpcle-*-sysv4
3236 PowerPC system in little endian mode, running System V.4.
3242 @heading @anchor{powerpcle-*-eabisim}powerpcle-*-eabisim
3243 Embedded PowerPC system in little endian mode for use in running under
3250 @heading @anchor{powerpcle-*-eabi}powerpcle-*-eabi
3251 Embedded PowerPC system in little endian mode.
3257 @heading @anchor{powerpcle-*-winnt}powerpcle-*-winnt, powerpcle-*-pe
3258 PowerPC system in little endian mode running Windows NT@.
3264 @heading @anchor{romp-*-aos}romp-*-aos, romp-*-mach
3265 The only operating systems supported for the IBM RT PC are AOS and
3266 MACH@. GCC does not support AIX running on the RT@. We recommend you
3267 compile GCC with an earlier version of itself; if you compile GCC
3268 with @command{hc}, the Metaware compiler, it will work, but you will get
3269 mismatches between the stage 2 and stage 3 compilers in various files.
3270 These errors are minor differences in some floating-point constants and
3271 can be safely ignored; the stage 3 compiler is correct.
3277 @heading @anchor{s390-*-linux*}s390-*-linux*
3278 S/390 system running Linux for S/390@.
3284 @heading @anchor{s390x-*-linux*}s390x-*-linux*
3285 zSeries system (64 Bit) running Linux for zSeries@.
3291 @c Please use Solaris 2 to refer to all release of Solaris, starting
3292 @c with 2.0 until 2.6, 7, and 8. Solaris 1 was a marketing name for
3293 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
3294 @c alone is too unspecific and must be avoided.
3295 @heading @anchor{*-*-solaris2*}*-*-solaris2*
3297 Sun does not ship a C compiler with Solaris 2. To bootstrap and install
3298 GCC you first have to install a pre-built compiler, see our
3299 @uref{binaries.html,,binaries page} for details.
3301 The Solaris 2 @command{/bin/sh} will often fail to configure
3302 @file{libstdc++-v3}, @file{boehm-gc} or
3303 @file{libjava}. If you encounter this problem, set @env{CONFIG_SHELL} to
3304 @command{/bin/ksh} in your environment and run @command{make bootstrap} again.
3305 Another possibility that sometimes helps is to remove
3306 @file{*-*-solaris2*/config.cache}.
3308 Solaris 2 comes with a number of optional OS packages. Some of these
3309 packages are needed to use GCC fully, namely @code{SUNWarc},
3310 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
3311 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
3312 optional packages when installing Solaris 2, you will need to verify that
3313 the packages that GCC needs are installed.
3315 To check whether an optional package is installed, use
3316 the @command{pkginfo} command. To add an optional package, use the
3317 @command{pkgadd} command. For further details, see the Solaris 2
3320 Trying to use the linker and other tools in
3321 @file{/usr/ucb} to install GCC has been observed to cause trouble.
3322 For example, the linker may hang indefinitely. The fix is to remove
3323 @file{/usr/ucb} from your @env{PATH}.
3325 All releases of GNU binutils prior to 2.11.2 have known bugs on this
3326 platform. We recommend the use of GNU binutils 2.11.2 or the vendor
3327 tools (Sun @command{as}, Sun @command{ld}).
3329 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3330 newer: @command{g++} will complain that types are missing. These headers assume
3331 that omitting the type means @code{int}; this assumption worked for C89 but
3332 is wrong for C++, and is now wrong for C99 also.
3334 @command{g++} accepts such (invalid) constructs with the option
3335 @option{-fpermissive}; it
3336 will assume that any missing type is @code{int} (as defined by C89).
3338 There are patches for Solaris 2.6 (105633-56 or newer for SPARC,
3339 106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC,
3340 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
3341 108653-22 for Intel) that fix this bug.
3347 @heading @anchor{sparc-sun-solaris2*}sparc-sun-solaris2*
3349 Sun @command{as} 4.x is broken in that it cannot cope with long symbol names.
3350 A typical error message might look similar to the following:
3352 @samp{/usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041:
3353 error: can't compute value of an expression involving an external symbol.}
3355 This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris
3356 2.6 and has been fixed in later (5.x) versions of the assembler,
3357 starting with Solaris 7.
3359 Starting with Solaris 7, the operating system is capable of executing
3360 64-bit SPARC V9 binaries. GCC 3.1 and later should properly support
3361 this. GCC 3.0 lacks the infrastructure necessary to support this
3362 configuration properly. However, if all you want is code tuned for
3363 the UltraSPARC CPU, you should try the @option{-mtune=ultrasparc}
3364 option instead, which should be safe from those bugs and produce code
3365 that, unlike full 64-bit code, can still run on non-UltraSPARC
3372 @heading @anchor{sparc-sun-solaris2.7}sparc-sun-solaris2.7
3374 Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
3375 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
3376 and later, including all EGCS releases. Sun formerly recommended
3377 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
3378 recommend it only for people who use Sun's compilers.
3380 Here are some workarounds to this problem:
3383 Do not install Sun patch 107058-01 until after Sun releases a
3384 complete patch for bug 4210064. This is the simplest course to take,
3385 unless you must also use Sun's C compiler. Unfortunately 107058-01
3386 is preinstalled on some new Solaris 7-based hosts, so you may have to
3390 Copy the original, unpatched Solaris 7
3391 @command{/usr/ccs/bin/as} into
3392 @command{/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/3.0/as},
3393 adjusting the latter name to fit your local conventions and software
3397 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
3398 both 107058-01 and 106950-03 installed has reported the bug with GCC
3399 and Sun's dynamic linker. This last course of action is riskiest,
3400 for two reasons. First, you must install 106950 on all hosts that
3401 run code generated by GCC; it doesn't suffice to install it only on
3402 the hosts that run GCC itself. Second, Sun says that 106950-03 is
3403 only a partial fix for bug 4210064, but Sun doesn't know whether the
3404 partial fix is adequate for GCC@. Revision -08 or later should fix
3405 the bug. The current (as of 2001-09-24) revision is -14, and is included in
3406 the Solaris 7 Recommended Patch Cluster.
3414 @heading @anchor{*-*-solaris2.8}*-*-solaris2.8
3416 The Solaris 8 linker fails to link some @samp{libjava} programs if
3417 previously-installed GCC java libraries already exist in the configured
3418 prefix. For this reason, @samp{libgcj} is disabled by default on Solaris 8.
3419 If you use GNU @command{ld}, or if you don't have a previously-installed @samp{libgcj} in
3420 the same prefix, use @option{--enable-libgcj} to build and install the
3427 @heading @anchor{sparc-sun-sunos4*}sparc-sun-sunos4*
3429 A bug in the SunOS 4 linker will cause it to crash when linking
3430 @option{-fPIC} compiled objects (and will therefore not allow you to build
3433 To fix this problem you can either use the most recent version of
3434 binutils or get the latest SunOS 4 linker patch (patch ID 100170-10)
3435 from Sun's patch site.
3437 Sometimes on a Sun 4 you may observe a crash in the program
3438 @command{genflags} or @command{genoutput} while building GCC. This is said to
3439 be due to a bug in @command{sh}. You can probably get around it by running
3440 @command{genflags} or @command{genoutput} manually and then retrying the
3447 @heading @anchor{sparc-unknown-linux-gnulibc1}sparc-unknown-linux-gnulibc1
3449 It has been reported that you might need
3450 @uref{ftp://ftp.yggdrasil.com/private/hjl,,binutils 2.8.1.0.23}
3451 for this platform, too.
3458 @heading @anchor{sparc-*-linux*}sparc-*-linux*
3460 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
3461 or newer on this platform. All earlier binutils and glibc
3462 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
3469 @heading @anchor{sparc64-*-*}sparc64-*-*
3471 GCC version 2.95 is not able to compile code correctly for
3472 @code{sparc64} targets. Users of the Linux kernel, at least,
3473 can use the @code{sparc32} program to start up a new shell
3474 invocation with an environment that causes @command{configure} to
3475 recognize (via @samp{uname -a}) the system as @samp{sparc-*-*} instead.
3482 @heading @anchor{#*-*-sysv*}*-*-sysv*
3483 On System V release 3, you may get this error message
3487 ld fatal: failed to write symbol name @var{something}
3488 in strings table for file @var{whatever}
3491 This probably indicates that the disk is full or your ulimit won't allow
3492 the file to be as large as it needs to be.
3494 This problem can also result because the kernel parameter @code{MAXUMEM}
3495 is too small. If so, you must regenerate the kernel and make the value
3496 much larger. The default value is reported to be 1024; a value of 32768
3497 is said to work. Smaller values may also work.
3499 On System V, if you get an error like this,
3502 /usr/local/lib/bison.simple: In function `yyparse':
3503 /usr/local/lib/bison.simple:625: virtual memory exhausted
3507 that too indicates a problem with disk space, ulimit, or @code{MAXUMEM}.
3509 On a System V release 4 system, make sure @file{/usr/bin} precedes
3510 @file{/usr/ucb} in @code{PATH}. The @code{cc} command in
3511 @file{/usr/ucb} uses libraries which have bugs.
3517 @heading @anchor{vax-dec-ultrix}vax-dec-ultrix
3518 Don't try compiling with VAX C (@code{vcc}). It produces incorrect code
3519 in some cases (for example, when @code{alloca} is used).
3525 @heading @anchor{we32k-*-*}we32k-*-*
3526 These computers are also known as the 3b2, 3b5, 3b20 and other similar
3527 names. (However, the 3b1 is actually a 68000.)
3529 Don't use @option{-g} when compiling with the system's compiler. The
3530 system's linker seems to be unable to handle such a large program with
3531 debugging information.
3533 The system's compiler runs out of capacity when compiling @file{stmt.c}
3534 in GCC@. You can work around this by building @file{cpp} in GCC
3535 first, then use that instead of the system's preprocessor with the
3536 system's C compiler to compile @file{stmt.c}. Here is how:
3539 mv /lib/cpp /lib/cpp.att
3541 echo '/lib/cpp.gnu -traditional $@{1+"$@@"@}' > /lib/cpp
3545 The system's compiler produces bad code for some of the GCC
3546 optimization files. So you must build the stage 2 compiler without
3547 optimization. Then build a stage 3 compiler with optimization.
3548 That executable should work. Here are the necessary commands:
3551 make LANGUAGES=c CC=stage1/xgcc CFLAGS="-Bstage1/ -g"
3553 make CC=stage2/xgcc CFLAGS="-Bstage2/ -g -O"
3556 You may need to raise the ULIMIT setting to build a C++ compiler,
3557 as the file @file{cc1plus} is larger than one megabyte.
3563 @heading @anchor{windows}Microsoft Windows (32 bit)
3565 A port of GCC 2.95.x is included with the
3566 @uref{http://www.cygwin.com/,,Cygwin environment}.
3568 Current (as of early 2001) snapshots of GCC will build under Cygwin
3569 without modification.
3575 @heading @anchor{os2}OS/2
3577 GCC does not currently support OS/2. However, Andrew Zabolotny has been
3578 working on a generic OS/2 port with pgcc. The current code can be found
3579 at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
3581 An older copy of GCC 2.8.1 is included with the EMX tools available at
3582 @uref{ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/,,
3583 ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/}.
3589 @heading @anchor{older}Older systems
3591 GCC contains support files for many older (1980s and early
3592 1990s) Unix variants. For the most part, support for these systems
3593 has not been deliberately removed, but it has not been maintained for
3594 several years and may suffer from bitrot. Support from some systems
3595 has been removed from GCC 3: fx80, ns32-ns-genix, pyramid, tahoe,
3596 gmicro, spur; most of these targets had not been updated since GCC
3599 Support for older systems as targets for cross-compilation is less
3600 problematic than support for them as hosts for GCC; if an enthusiast
3601 wishes to make such a target work again (including resurrecting any
3602 of the targets that never worked with GCC 2, starting from the last
3603 CVS version before they were removed), patches
3604 @uref{../contribute.html,,following the usual requirements}
3605 would be likely to be accepted, since they should not affect the
3606 support for more modern targets.
3608 Support for old systems as hosts for GCC can cause problems if the
3609 workarounds for compiler, library and operating system bugs affect the
3610 cleanliness or maintainability of the rest of GCC@. In some cases, to
3611 bring GCC up on such a system, if still possible with current GCC, may
3612 require first installing an old version of GCC which did work on that
3613 system, and using it to compile a more recent GCC, to avoid bugs in
3614 the vendor compiler. Old releases of GCC 1 and GCC 2 are available in
3615 the @file{old-releases} directory on the
3616 @uref{../mirrors.html,,GCC mirror sites}. Header bugs may generally
3617 be avoided using @command{fixincludes}, but bugs or deficiencies in
3618 libraries and the operating system may still cause problems.
3620 For some systems, old versions of GNU binutils may also be useful,
3621 and are available from @file{pub/binutils/old-releases} on
3622 @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}.
3624 Some of the information on specific systems above relates to
3625 such older systems, but much of the information
3626 about GCC on such systems (which may no longer be applicable to
3627 current GCC) is to be found in the GCC texinfo manual.
3633 @heading @anchor{elf_targets}all ELF targets (SVR4, Solaris 2, etc.)
3635 C++ support is significantly better on ELF targets if you use the
3636 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
3637 inlines, vtables and template instantiations will be discarded
3647 @uref{./index.html,,Return to the GCC Installation page}
3651 @c ***************************************************************************
3652 @c Part 6 The End of the Document
3654 @comment node-name, next, previous, up
3655 @node Concept Index, , Specific, Top
3659 @unnumbered Concept Index