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 The installation procedure itself is broken into five steps.
124 * Downloading the source::
127 * Testing:: (optional)
134 @uref{download.html,,Downloading the source}
136 @uref{configure.html,,Configuration}
138 @uref{build.html,,Building}
140 @uref{test.html,,Testing} (optional)
142 @uref{finalinstall.html,,Final install}
146 Please note that GCC does not support @samp{make uninstall} and probably
147 won't do so in the near future as this would open a can of worms. Instead,
148 we suggest that you install GCC into a directory of its own and simply
149 remove that directory when you do not need that specific version of GCC
150 any longer, and, if shared libraries are installed there as well, no
151 more binaries exist that use them.
158 @uref{./index.html,,Return to the GCC Installation page}
162 @c ***Downloading the source**************************************************
164 @comment node-name, next, previous, up
165 @node Downloading the source, Configuration, , Installing GCC
169 <h1 align="center">Downloading GCC</h1>
172 @chapter Downloading GCC
174 @cindex Downloading GCC
175 @cindex Downloading the Source
177 GCC is distributed via @uref{http://gcc.gnu.org/cvs.html,,CVS} and FTP
178 tarballs compressed with @command{gzip} or
179 @command{bzip2}. It is possible to download a full distribution or specific
182 Please refer to our @uref{http://gcc.gnu.org/releases.html,,releases web page}
183 for information on how to obtain GCC@.
185 The full distribution includes the C, C++, Objective-C, Fortran, Java,
186 and CHILL compilers. The full distribution also includes runtime libraries
187 for C++, Objective-C, Fortran, Java and CHILL. (GCC 3.0 does not
188 include CHILL.) In GCC 3.0 and later versions, GNU compiler testsuites
189 are also included in the full distribution.
191 If you choose to download specific components, you must download the core
192 GCC distribution plus any language specific distributions you wish to
193 use. The core distribution includes the C language front end as well as the
194 shared components. Each language has a tarball which includes the language
195 front end as well as the language runtime (when appropriate).
197 Unpack the core distribution as well as any language specific
198 distributions in the same directory.
200 If you also intend to build binutils (either to upgrade an existing
201 installation or for use in place of the corresponding tools of your
202 OS), unpack the binutils distribution either in the same directory or
203 a separate one. In the latter case, add symbolic links to any
204 components of the binutils you intend to build alongside the compiler
205 (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
206 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
213 @uref{./index.html,,Return to the GCC Installation page}
217 @c ***Configuration***********************************************************
219 @comment node-name, next, previous, up
220 @node Configuration, Building, Downloading the source, Installing GCC
224 <h1 align="center">Installing GCC: Configuration</h1>
227 @chapter Installing GCC: Configuration
229 @cindex Configuration
230 @cindex Installing GCC: Configuration
232 Like most GNU software, GCC must be configured before it can be built.
233 This document describes the recommended configuration procedure
234 for both native and cross targets.
236 We use @var{srcdir} to refer to the toplevel source directory for
237 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
239 If you obtained the sources via CVS, @var{srcdir} must refer to the top
240 @file{gcc} directory, the one where the @file{MAINTAINERS} can be found,
241 and not its @file{gcc} subdirectory, otherwise the build will fail.
243 First, we @strong{highly} recommend that GCC be built into a
244 separate directory than the sources which does @strong{not} reside
245 within the source tree. This is how we generally build GCC; building
246 where @var{srcdir} == @var{objdir} should still work, but doesn't
247 get extensive testing; building where @var{objdir} is a subdirectory
248 of @var{srcdir} is unsupported.
250 If you have previously built GCC in the same directory for a
251 different target machine, do @samp{make distclean} to delete all files
252 that might be invalid. One of the files this deletes is
253 @file{Makefile}; if @samp{make distclean} complains that @file{Makefile}
254 does not exist, it probably means that the directory is already suitably
255 clean. However, with the recommended method of building in a separate
256 @var{objdir}, you should simply use a different @var{objdir} for each
259 Second, when configuring a native system, either @command{cc} or
260 @command{gcc} must be in your path or you must set @env{CC} in
261 your environment before running configure. Otherwise the configuration
264 Note that the bootstrap compiler and the resulting GCC must be link
265 compatible, else the bootstrap will fail with linker errors about
266 incompatible object file formats. Several multilibed targets are
267 affected by this requirement, see @ref{Specific, host/target specific
268 installation notes} for details.
275 % @var{srcdir}/configure [@var{options}] [@var{target}]
279 @heading Target specification
282 GCC has code to correctly determine the correct value for @var{target}
283 for nearly all native systems. Therefore, we highly recommend you not
284 provide a configure target when configuring a native compiler.
287 @var{target} must be specified as @option{--target=@var{target}}
288 when configuring a cross compiler; examples of valid targets would be
289 i960-rtems, m68k-coff, sh-elf, etc.
292 Specifying just @var{target} instead of @option{--target=@var{target}}
293 implies that the host defaults to @var{target}.
297 @heading Options specification
299 Use @var{options} to override several configure time options for
300 GCC@. A partial list of supported @var{options}:
303 @item --prefix=@var{dirname}
304 Specify the toplevel installation
305 directory. This is the recommended way to install the tools into a directory
306 other than the default. The toplevel installation directory defaults to
309 We @strong{highly} recommend against @var{dirname} being the same or a
310 subdirectory of @var{objdir} or vice versa.
312 These additional options control where certain parts of the distribution
313 are installed. Normally you should not need to use these options.
316 @item --exec-prefix=@var{dirname}
317 Specify the toplevel installation directory for architecture-dependent
318 files. The default is @file{@var{prefix}}.
320 @item --bindir=@var{dirname}
321 Specify the installation directory for the executables called by users
322 (such as @command{gcc} and @command{g++}). The default is
323 @file{@var{exec-prefix}/bin}.
325 @item --libdir=@var{dirname}
326 Specify the installation directory for object code libraries and
327 internal parts of GCC@. The default is @file{@var{exec-prefix}/lib}.
329 @item --with-slibdir=@var{dirname}
330 Specify the installation directory for the shared libgcc library. The
331 default is @file{@var{libdir}}.
333 @item --infodir=@var{dirname}
334 Specify the installation directory for documentation in info format.
335 The default is @file{@var{prefix}/info}.
337 @item --mandir=@var{dirname}
338 Specify the installation directory for manual pages. The default is
339 @file{@var{prefix}/man}. (Note that the manual pages are only extracts from
340 the full GCC manuals, which are provided in Texinfo format. The
341 @command{g77} manpage is unmaintained and may be out of date; the others
342 are derived by an automatic conversion process from parts of the full
345 @item --with-gxx-include-dir=@var{dirname}
347 the installation directory for G++ header files. The default is
348 @file{@var{prefix}/include/g++-v3}.
352 @item --with-local-prefix=@var{dirname}
354 installation directory for local include files. The default is
355 @file{/usr/local}. Specify this option if you want the compiler to
356 search directory @file{@var{dirname}/include} for locally installed
357 header files @emph{instead} of @file{/usr/local/include}.
359 You should specify @option{--with-local-prefix} @strong{only} if your
360 site has a different convention (not @file{/usr/local}) for where to put
363 The default value for @option{--with-local-prefix} is @file{/usr/local}
364 regardless of the value of @option{--prefix}. Specifying
365 @option{--prefix} has no effect on which directory GCC searches for
366 local header files. This may seem counterintuitive, but actually it is
369 The purpose of @option{--prefix} is to specify where to @emph{install
370 GCC}. The local header files in @file{/usr/local/include}---if you put
371 any in that directory---are not part of GCC@. They are part of other
372 programs---perhaps many others. (GCC installs its own header files in
373 another directory which is based on the @option{--prefix} value.)
375 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
376 The directory you use for @option{--with-local-prefix} @strong{must not}
377 contain any of the system's standard header files. If it did contain
378 them, certain programs would be miscompiled (including GNU Emacs, on
379 certain targets), because this would override and nullify the header
380 file corrections made by the @code{fixincludes} script.
382 Indications are that people who use this option use it based on mistaken
383 ideas of what it is for. People use it as if it specified where to
384 install part of GCC@. Perhaps they make this assumption because
385 installing GCC creates the directory.
387 @item --enable-shared[=@var{package}[,@dots{}]]
388 Build shared versions of libraries, if shared libraries are supported on
389 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
390 are enabled by default on all platforms that support shared libraries,
391 except for @samp{libobjc} which is built as a static library only by
394 If a list of packages is given as an argument, build shared libraries
395 only for the listed packages. For other packages, only static libraries
396 will be built. Package names currently recognized in the GCC tree are
397 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
398 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc} and
399 @samp{libjava}. Note that @samp{libobjc} does not recognize itself by
400 any name, so, if you list package names in @option{--enable-shared},
401 you will only get static Objective-C libraries. @samp{libf2c} and
402 @samp{libiberty} do not support shared libraries at all.
404 Use @option{--disable-shared} to build only static libraries. Note that
405 @option{--disable-shared} does not accept a list of package names as
406 argument, only @option{--enable-shared} does.
408 @item @anchor{with-gnu-as}--with-gnu-as
409 Specify that the compiler should assume that the
410 assembler it finds is the GNU assembler. However, this does not modify
411 the rules to find an assembler and will result in confusion if found
412 assembler is not actually the GNU assembler. (Confusion will also
413 result if the compiler finds the GNU assembler but has not been
414 configured with @option{--with-gnu-as}.) If you have more than one
415 assembler installed on your system, you may want to use this option in
416 connection with @option{--with-as=@var{pathname}}.
418 The systems where it makes a difference whether you use the GNU assembler are
419 @samp{hppa1.0-@var{any}-@var{any}}, @samp{hppa1.1-@var{any}-@var{any}},
420 @samp{i386-@var{any}-sysv}, @samp{i386-@var{any}-isc},
421 @samp{i860-@var{any}-bsd}, @samp{m68k-bull-sysv},
422 @samp{m68k-hp-hpux}, @samp{m68k-sony-bsd},
423 @samp{m68k-altos-sysv}, @samp{m68000-hp-hpux},
424 @samp{m68000-att-sysv}, @samp{@var{any}-lynx-lynxos},
425 and @samp{mips-@var{any}}.
426 On any other system, @option{--with-gnu-as} has no effect.
428 On the systems listed above (except for the HP-PA, for ISC on the
429 386, and for @samp{mips-sgi-irix5.*}), if you use the GNU assembler,
430 you should also use the GNU linker (and specify @option{--with-gnu-ld}).
432 @item --with-as=@var{pathname}
434 compiler should use the assembler pointed to by @var{pathname}, rather
435 than the one found by the standard rules to find an assembler, which
440 @file{@var{exec_prefix}/lib/gcc-lib/@var{target}/@var{version}}
441 directory, where @var{exec_prefix} defaults to @var{prefix} which
442 defaults to @file{/usr/local} unless overridden by the
443 @option{--prefix=@var{pathname}} switch described above. @var{target} is the
444 target system triple, such as @var{sparc-sun-solaris2.7}, and
445 @var{version} denotes the GCC version, such as 3.0.
447 Check operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
450 Note that these rules do not check for the value of @env{PATH}. You may
451 want to use @option{--with-as} if no assembler is installed in the
452 directories listed above, or if you have multiple assemblers installed
453 and want to choose one that is not found by the above rules.
455 @item @anchor{with-gnu-ld}--with-gnu-ld
456 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
460 @item --with-ld=@var{pathname}
462 @option{--with-as}, but for the linker.
465 Specify that stabs debugging
466 information should be used instead of whatever format the host normally
467 uses. Normally GCC uses the same debug format as the host system.
469 On MIPS based systems and on Alphas, you must specify whether you want
470 GCC to create the normal ECOFF debugging format, or to use BSD-style
471 stabs passed through the ECOFF symbol table. The normal ECOFF debug
472 format cannot fully handle languages other than C@. BSD stabs format can
473 handle other languages, but it only works with the GNU debugger GDB@.
475 Normally, GCC uses the ECOFF debugging format by default; if you
476 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
478 No matter which default you choose when you configure GCC, the user
479 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
480 the debug format for a particular compilation.
482 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
483 @option{--with-gas} is used. It selects use of stabs debugging
484 information embedded in COFF output. This kind of debugging information
485 supports C++ well; ordinary COFF debugging information does not.
487 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
488 selects use of stabs debugging information embedded in ELF output. The
489 C++ compiler currently (2.6.0) does not support the DWARF debugging
490 information normally used on 386 SVR4 platforms; stabs provide a
491 workable alternative. This requires gas and gdb, as the normal SVR4
492 tools can not generate or interpret stabs.
494 @item --disable-multilib
495 Specify that multiple target
496 libraries to support different target variants, calling
497 conventions, etc should not be built. The default is to build a
498 predefined set of them.
500 @item --enable-threads
501 Specify that the target
502 supports threads. This affects the Objective-C compiler and runtime
503 library, and exception handling for other languages like C++ and Java.
504 On some systems, this is the default.
506 In general, the best (and, in many cases, the only known) threading
507 model available will be configured for use. Beware that on some
508 systems, gcc has not been taught what threading models are generally
509 available for the system. In this case, @option{--enable-threads} is an
510 alias for @option{--enable-threads=single}.
512 @item --disable-threads
513 Specify that threading support should be disabled for the system.
514 This is an alias for @option{--enable-threads=single}.
516 @item --enable-threads=@var{lib}
518 @var{lib} is the thread support library. This affects the Objective-C
519 compiler and runtime library, and exception handling for other languages
520 like C++ and Java. The possibilities for @var{lib} are:
528 Generic MACH thread support, known to work on NeXTSTEP@. (Please note
529 that the file needed to support this configuration, @file{gthr-mach.h}, is
530 missing and thus this setting will cause a known bootstrap failure.)
532 This is an alias for @samp{single}.
534 Generic POSIX thread support.
536 Same as @samp{posix} on arm*-*-linux*, *-*-chorusos* and *-*-freebsd*
537 only. A future release of gcc might remove this alias or extend it
540 RTEMS thread support.
542 Disable thread support, should work for all platforms.
544 Sun Solaris 2 thread support.
546 VxWorks thread support.
548 Microsoft Win32 API thread support.
551 @item --with-cpu=@var{cpu}
552 Specify which cpu variant the
553 compiler should generate code for by default. This is currently
554 only supported on the some ports, specifically arm, powerpc, and
555 SPARC@. If configure does not recognize the model name (e.g.@: arm700,
556 603e, or ultrasparc) you provide, please check the configure script
557 for a complete list of supported models.
559 @item --enable-target-optspace
561 libraries should be optimized for code space instead of code speed.
562 This is the default for the m32r platform.
565 Specify that a user visible @command{cpp} program should not be installed.
567 @item --with-cpp-install-dir=@var{dirname}
568 Specify that the user visible @command{cpp} program should be installed
569 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
571 @item --enable-maintainer-mode
573 regenerate the GCC master message catalog @file{gcc.pot} are normally
574 disabled. This is because it can only be rebuilt if the complete source
575 tree is present. If you have changed the sources and want to rebuild the
576 catalog, configuring with @option{--enable-maintainer-mode} will enable
577 this. Note that you need a recent version of the @code{gettext} tools
580 @item --enable-version-specific-runtime-libs
582 that runtime libraries should be installed in the compiler specific
583 subdirectory (@file{@var{libsubdir}}) rather than the usual places. In
584 addition, @samp{libstdc++}'s include files will be installed in
585 @file{@var{libsubdir}/include/g++} unless you overruled it by using
586 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
587 particularly useful if you intend to use several versions of GCC in
588 parallel. This is currently supported by @samp{libf2c} and
589 @samp{libstdc++}, and is the default for @samp{libobjc} which cannot be
590 changed in this case.
592 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
593 Specify that only a particular subset of compilers and
594 their runtime libraries should be built. For a list of valid values for
595 @var{langN} you can issue the following command in the
596 @file{gcc} directory of your GCC source tree:@*
598 grep language= */config-lang.in
600 Currently, you can use any of the following:
601 @code{c}, @code{c++}, @code{f77}, @code{java} and @code{objc}.
602 @code{CHILL} is not currently maintained, and will almost
603 certainly fail to compile.@*
604 If you do not pass this flag, all languages available in the @file{gcc}
605 sub-tree will be configured. Re-defining @code{LANGUAGES} when calling
606 @samp{make bootstrap} @strong{does not} work anymore, as those
607 language sub-directories might not have been configured!
609 @item --disable-libgcj
610 Specify that the run-time libraries
611 used by GCJ should not be built. This is useful in case you intend
612 to use GCJ with some other run-time, or you're going to install it
613 separately, or it just happens not to build on your particular
614 machine. In general, if the Java front end is enabled, the GCJ
615 libraries will be enabled too, unless they're known to not work on
616 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
617 may need to port it; in this case, before modifying the top-level
618 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
619 you may use @option{--enable-libgcj} to override the default.
622 Specify that the compiler should
623 use DWARF 2 debugging information as the default.
625 @item --enable-win32-registry
626 @itemx --enable-win32-registry=@var{key}
627 @itemx --disable-win32-registry
628 The @option{--enable-win32-registry} option enables Windows-hosted GCC
629 to look up installations paths in the registry using the following key:
632 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
635 @var{key} defaults to GCC version number, and can be overridden by the
636 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
637 who use custom installers are encouraged to provide a different key,
638 perhaps one comprised of vendor name and GCC version number, to
639 avoid conflict with existing installations. This feature is enabled
640 by default, and can be disabled by @option{--disable-win32-registry}
641 option. This option has no effect on the other hosts.
644 Specify that the machine does not have a floating point unit. This
645 option only applies to @samp{m68k-sun-sunos@var{n}} and
646 @samp{m68k-isi-bsd}. On any other system, @option{--nfp} has no effect.
648 @item --enable-checking
649 @itemx --enable-checking=@var{list}
650 When you specify this option, the compiler is built to perform checking
651 of tree node types when referencing fields of that node, and some other
652 internal consistency checks. This does not change the generated code,
653 but adds error checking within the compiler. This will slow down the
654 compiler and may only work properly if you are building the compiler
655 with GCC@. This is on by default when building from CVS or snapshots,
656 but off for releases. More control over the checks may be had by
657 specifying @var{list}; the categories of checks available are
658 @samp{misc}, @samp{tree}, @samp{gc}, @samp{rtl} and @samp{gcac}. The
659 default when @var{list} is not specified is @samp{misc,tree,gc}; the
660 checks @samp{rtl} and @samp{gcac} are very expensive.
664 The @option{--enable-nls} option enables Native Language Support (NLS),
665 which lets GCC output diagnostics in languages other than American
666 English. Native Language Support is enabled by default if not doing a
667 canadian cross build. The @option{--disable-nls} option disables NLS@.
669 @item --with-included-gettext
670 If NLS is enabled, the @option{--with-included-gettext} option causes the build
671 procedure to prefer its copy of GNU @code{gettext}.
674 If NLS is enabled, and if the host lacks @code{gettext} but has the
675 inferior @code{catgets} interface, the GCC build procedure normally
676 ignores @code{catgets} and instead uses GCC's copy of the GNU
677 @code{gettext} library. The @option{--with-catgets} option causes the
678 build procedure to use the host's @code{catgets} in this situation.
681 Some options which only apply to building cross compilers:
683 @item --with-headers=@var{dir}
684 Specifies a directory
685 which has target include files.
686 @emph{This options is required} when building a cross
687 compiler, if @file{@var{prefix}/@var{target}/sys-include} doesn't pre-exist.
688 These include files will be copied into the @file{gcc} install directory.
689 Fixincludes will be run on these files to make them compatible with
691 @item --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
692 Specifies a list of directories which contain the target runtime
693 libraries. These libraries will be copied into the @file{gcc} install
696 Specifies that @samp{newlib} is
697 being used as the target C library. This causes @code{__eprintf} to be
698 omitted from @file{libgcc.a} on the assumption that it will be provided by
702 Note that each @option{--enable} option has a corresponding
703 @option{--disable} option and that each @option{--with} option has a
704 corresponding @option{--without} option.
711 @uref{./index.html,,Return to the GCC Installation page}
715 @c ***Building****************************************************************
717 @comment node-name, next, previous, up
718 @node Building, Testing, Configuration, Installing GCC
722 <h1 align="center">Installing GCC: Building</h1>
727 @cindex Installing GCC: Building
729 Now that GCC is configured, you are ready to build the compiler and
732 We @strong{highly} recommend that GCC be built using GNU make;
733 other versions may work, then again they might not.
735 (For example, many broken versions of make will fail if you use the
736 recommended setup where @var{objdir} is different from @var{srcdir}.
737 Other broken versions may recompile parts of the compiler when
738 installing the compiler.)
740 Some commands executed when making the compiler may fail (return a
741 non-zero status) and be ignored by @code{make}. These failures, which
742 are often due to files that were not found, are expected, and can safely
745 It is normal to have compiler warnings when compiling certain files.
746 Unless you are a GCC developer, you can generally ignore these warnings
747 unless they cause compilation to fail.
749 On certain old systems, defining certain environment variables such as
750 @env{CC} can interfere with the functioning of @command{make}.
752 If you encounter seemingly strange errors when trying to build the
753 compiler in a directory other than the source directory, it could be
754 because you have previously configured the compiler in the source
755 directory. Make sure you have done all the necessary preparations.
757 If you build GCC on a BSD system using a directory stored in an old System
758 V file system, problems may occur in running @code{fixincludes} if the
759 System V file system doesn't support symbolic links. These problems
760 result in a failure to fix the declaration of @code{size_t} in
761 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
762 that type mismatches occur, this could be the cause.
764 The solution is not to use such a directory for building GCC@.
766 When building from CVS or snapshots, or if you modify parser sources,
767 you need the Bison parser generator installed. Any version 1.25 or
768 later should work; older versions may also work. If you do not modify
769 parser sources, releases contain the Bison-generated files and you do
770 not need Bison installed to build them.
772 When building from CVS or snapshots, or if you modify Texinfo
773 documentation, you need version 4.0 or later of Texinfo installed if you
774 want Info documentation to be regenerated. Releases contain Info
775 documentation pre-built for the unmodified documentation in the release.
777 @section Building a native compiler
779 For a native build issue the command @samp{make bootstrap}. This
780 will build the entire GCC system, which includes the following steps:
784 Build host tools necessary to build the compiler such as texinfo, bison,
788 Build target tools for use by the compiler such as binutils (bfd,
789 binutils, gas, gprof, ld, and opcodes)
790 if they have been individually linked
791 or moved into the top level GCC source tree before configuring.
794 Perform a 3-stage bootstrap of the compiler.
797 Perform a comparison test of the stage2 and stage3 compilers.
800 Build runtime libraries using the stage3 compiler from the previous step.
804 If you are short on disk space you might consider @samp{make
805 bootstrap-lean} instead. This is identical to @samp{make
806 bootstrap} except that object files from the stage1 and
807 stage2 of the 3-stage bootstrap of the compiler are deleted as
808 soon as they are no longer needed.
811 If you want to save additional space during the bootstrap and in
812 the final installation as well, you can build the compiler binaries
813 without debugging information with @samp{make CFLAGS='-O' LIBCFLAGS='-g
814 -O2' LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap}. This will save
815 roughly 40% of disk space both for the bootstrap and the final installation.
816 (Libraries will still contain debugging information.)
818 If you wish to use non-default GCC flags when compiling the stage2 and
819 stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing
820 @samp{make bootstrap}. Non-default optimization flags are less well
821 tested here than the default of @samp{-g -O2}, but should still work.
822 In a few cases, you may find that you need to specify special flags such
823 as @option{-msoft-float} here to complete the bootstrap; or, if the
824 native compiler miscompiles the stage1 compiler, you may need to work
825 around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the
826 stage1 compiler that were miscompiled, or by using @samp{make
827 bootstrap4} to increase the number of stages of bootstrap.
829 If you used the flag @option{--enable-languages=@dots{}} to restrict
830 the compilers to be built, only those you've actually enabled will be
831 built. This will of course only build those runtime libraries, for
832 which the particular compiler has been built. Please note,
833 that re-defining @env{LANGUAGES} when calling @samp{make bootstrap}
834 @strong{does not} work anymore!
836 If the comparison of stage2 and stage3 fails, this normally indicates
837 that the stage2 compiler has compiled GCC incorrectly, and is therefore
838 a potentially serious bug which you should investigate and report. (On
839 a few systems, meaningful comparison of object files is impossible; they
840 always appear ``different''. If you encounter this problem, you will
841 need to disable comparison in the @file{Makefile}.)
843 @section Building a cross compiler
845 We recommend reading the
846 @uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ}
847 for information about building cross compilers.
849 When building a cross compiler, it is not generally possible to do a
850 3-stage bootstrap of the compiler. This makes for an interesting problem
851 as parts of GCC can only be built with GCC@.
853 To build a cross compiler, we first recommend building and installing a
854 native compiler. You can then use the native GCC compiler to build the
857 Assuming you have already installed a native copy of GCC and configured
858 your cross compiler, issue the command @command{make}, which performs the
863 Build host tools necessary to build the compiler such as texinfo, bison,
867 Build target tools for use by the compiler such as binutils (bfd,
868 binutils, gas, gprof, ld, and opcodes)
869 if they have been individually linked or moved into the top level GCC source
870 tree before configuring.
873 Build the compiler (single stage only).
876 Build runtime libraries using the compiler from the previous step.
879 Note that if an error occurs in any step the make process will exit.
881 @section Building in parallel
883 If you have a multiprocessor system you can use @samp{make bootstrap
884 MAKE="make -j 2" -j 2} or just @samp{make -j 2 bootstrap}
885 for GNU Make 3.79 and above instead of just @samp{make bootstrap}
886 when building GCC@. You can use a bigger number instead of two if
887 you like. In most cases, it won't help to use a number bigger than
888 the number of processors in your machine.
895 @uref{./index.html,,Return to the GCC Installation page}
899 @c ***Testing*****************************************************************
901 @comment node-name, next, previous, up
902 @node Testing, Final install, Building, Installing GCC
906 <h1 align="center">Installing GCC: Testing</h1>
909 @chapter Installing GCC: Testing
912 @cindex Installing GCC: Testing
915 Before you install GCC, you might wish to run the testsuite. This
916 step is optional and may require you to download additional software.
918 First, you must have @uref{download.html,,downloaded the testsuites}.
919 The full distribution contains testsuites; only if you downloaded the
920 ``core'' compiler plus any front ends, you do not have the testsuites.
922 Second, you must have a @uref{http://www.gnu.org/software/dejagnu/,,current version of DejaGnu} installed;
923 dejagnu 1.3 is not sufficient.
925 Now you may need specific preparations:
930 The following environment variables may need to be set appropriately, as in
931 the following example (which assumes that DejaGnu has been installed
932 under @file{/usr/local}):
935 TCL_LIBRARY = /usr/local/share/tcl8.0
936 DEJAGNULIBS = /usr/local/share/dejagnu
939 On systems such as Cygwin, these paths are required to be actual
940 paths, not mounts or links; presumably this is due to some lack of
941 portability in the DejaGnu code.
943 If the directories where @command{runtest} and @command{expect} were
944 installed are in the @env{PATH}, it should not be necessary to set these
945 environment variables.
949 Finally, you can run the testsuite (which may take a long time):
951 cd @var{objdir}; make -k check
954 The testing process will try to test as many components in the GCC
955 distribution as possible, including the C, C++, Objective-C and Fortran
956 compilers as well as the C++ and Java runtime libraries.
958 @section How can I run the test suite on selected tests?
960 As a first possibility to cut down the number of tests that are run it is
961 possible to use @samp{make check-gcc} or @samp{make check-g++}
962 in the @file{gcc} subdirectory of the object directory. To further cut down the
963 tests the following is possible:
966 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
969 This will run all @command{gcc} execute tests in the testsuite.
972 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
975 This will run the @command{g++} ``old-deja'' tests in the testsuite where the filename
976 matches @samp{9805*}.
978 The @file{*.exp} files are located in the testsuite directories of the GCC
979 source, the most important ones being @file{compile.exp},
980 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
981 To get a list of the possible @file{*.exp} files, pipe the
982 output of @samp{make check} into a file and look at the
983 @samp{Running @dots{} .exp} lines.
985 @section How to interpret test results
987 After the testsuite has run you'll find various @file{*.sum} and @file{*.log}
988 files in the testsuite subdirectories. The @file{*.log} files contain a
989 detailed log of the compiler invocations and the corresponding
990 results, the @file{*.sum} files summarize the results. These summaries list
991 all the tests that have been run with a corresponding status code:
995 PASS: the test passed as expected
997 XPASS: the test unexpectedly passed
999 FAIL: the test unexpectedly failed
1001 XFAIL: the test failed as expected
1003 UNSUPPORTED: the test is not supported on this platform
1005 ERROR: the testsuite detected an error
1007 WARNING: the testsuite detected a possible problem
1010 It is normal for some tests to report unexpected failures. At the
1011 current time our testing harness does not allow fine grained control
1012 over whether or not a test is expected to fail. We expect to fix this
1013 problem in future releases.
1016 @section Submitting test results
1018 If you want to report the results to the GCC project, use the
1019 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
1022 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
1023 -m gcc-testresults@@gcc.gnu.org |sh
1026 This script uses the @command{Mail} program to send the results, so
1027 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
1028 prepended to the testsuite summary and should contain any special
1029 remarks you have on your results or your build environment. Please
1030 do not edit the testsuite result block or the subject line, as these
1031 messages are automatically parsed and presented at the
1032 @uref{http://gcc.gnu.org/testresults/,,GCC testresults} web
1033 page. Here you can also gather information on how specific tests
1034 behave on different platforms and compare them with your results. A
1035 few failing testcases are possible even on released versions and you
1036 should look here first if you think your results are unreasonable.
1040 @c ***Final install***********************************************************
1042 @comment node-name, next, previous, up
1043 @node Final install, , Testing, Installing GCC
1045 @ifset finalinstallhtml
1047 <h1 align="center">Installing GCC: Final installation</h1>
1050 @chapter Installing GCC: Final installation
1053 Now that GCC has been built (and optionally tested), you can install it with
1055 cd @var{objdir}; make install
1058 That step completes the installation of GCC; user level binaries can
1059 be found in @file{@var{prefix}/bin} where @var{prefix} is the value you
1060 specified with the @option{--prefix} to configure (or @file{/usr/local}
1061 by default). (If you specified @option{--bindir}, that directory will
1062 be used instead; otherwise, if you specified @option{--exec-prefix},
1063 @file{@var{exec-prefix}/bin} will be used.) Headers for the C++ and
1064 Java libraries are installed in @file{@var{prefix}/include}; libraries
1065 in @file{@var{libdir}} (normally @file{@var{prefix}/lib}); internal
1066 parts of the compiler in @file{@var{libdir}/gcc-lib}; documentation in
1067 info format in @file{@var{infodir}} (normally @file{@var{prefix}/info}).
1069 If you don't mind, please quickly review the
1070 @uref{http://gcc.gnu.org/gcc-3.0/buildstat.html,,build status page}.
1071 If your system is not listed, send a note to
1072 @email{gcc@@gcc.gnu.org} indicating
1073 that you successfully built and installed GCC.
1075 Include the output from running @file{@var{srcdir}/config.guess}. (Do
1076 not send us the @file{config.guess} file itself, just the one-line output from
1079 If you find a bug, please report it following our
1080 @uref{../bugs.html,,bug reporting guidelines}.
1082 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
1083 dvi}. You will need to have @command{texi2dvi} (version at least 4.0)
1084 and @TeX{} installed. This creates a number of @file{.dvi} files in
1085 subdirectories of @file{@var{objdir}}; these may be converted for
1086 printing with programs such as @command{dvips}. You can also
1087 @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the
1088 Free Software Foundation}, though such manuals may not be for the most
1089 recent version of GCC@.
1096 @uref{./index.html,,Return to the GCC Installation page}
1100 @c ***Binaries****************************************************************
1102 @comment node-name, next, previous, up
1103 @node Binaries, Specific, Installing GCC, Top
1107 <h1 align="center">Installing GCC: Binaries</h1>
1110 @chapter Installing GCC: Binaries
1113 @cindex Installing GCC: Binaries
1115 We are often asked about pre-compiled versions of GCC@. While we cannot
1116 provide these for all platforms, below you'll find links to binaries for
1117 various platforms where creating them by yourself is not easy due to various
1120 Please note that we did not create these binaries, nor do we
1121 support them. If you have any problems installing them, please
1122 contact their makers.
1129 @uref{http://www-frec.bull.com/docs/download.htm,,Bull's Freeware and
1130 Shareware Archive for AIX};
1133 @uref{http://aixpdlib.seas.ucla.edu,,UCLA Software Library for AIX};
1137 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP};
1140 @uref{http://hpux.cae.wisc.edu/,,HP-UX Porting Center};
1143 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
1144 OpenServer/Unixware};
1147 Solaris (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware};
1150 SGI---@uref{http://freeware.sgi.com/,,SGI Freeware};
1153 Windows 95, 98, and NT:
1156 The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project;
1158 @uref{http://www.xraylith.wisc.edu/~khan/software/gnu-win32/,,GNU Win32}
1159 related projects by Mumit Khan.
1163 @uref{ftp://ftp.thewrittenword.com/packages/free/by-name/gcc-2.95.2/,,The
1164 Written Word} offers binaries for Solaris 2.5.1, 2.6, 2.7/SPARC, 2.7/Intel,
1165 IRIX 6.2, 6.5, Digital UNIX 4.0D, HP-UX 10.20, and HP-UX 11.00.
1168 Hitachi H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
1169 Development Tools for the Hitachi H8/300[HS] Series}
1173 In addition to those specific offerings, you can get a binary
1174 distribution CD-ROM from the
1175 @uref{http://www.fsf.org/order/order.html,,Free Software Foundation}.
1176 It contains binaries for a number of platforms, and
1177 includes not only GCC, but other stuff as well. The current CD does
1178 not contain the latest version of GCC, but it should allow
1179 bootstrapping the compiler. An updated version of that disk is in the
1187 @uref{./index.html,,Return to the GCC Installation page}
1191 @c ***Specific****************************************************************
1193 @comment node-name, next, previous, up
1194 @node Specific, Concept Index, Binaries, Top
1198 <h1 align="center">Host/target specific installation notes for GCC</h1>
1201 @chapter Host/target specific installation notes for GCC
1204 @cindex Specific installation notes
1205 @cindex Target specific installation
1206 @cindex Host specific installation
1207 @cindex Target specific installation notes
1209 Please read this document carefully @emph{before} installing the
1210 GNU Compiler Collection on your machine.
1215 @uref{#1750a-*-*,,1750a-*-*}
1219 @uref{#a29k-*-bsd,,a29k-*-bsd}
1221 @uref{#alpha*-*-*,,alpha*-*-*}
1223 @uref{#alpha*-dec-osf*,,alpha*-dec-osf*}
1225 @uref{#arc-*-elf,,arc-*-elf}
1227 @uref{#arm-*-aout,,arm-*-aout}
1229 @uref{#arm-*-elf,,arm-*-elf}
1231 @uref{#arm*-*-linux-gnu,,arm*-*-linux-gnu}
1233 @uref{#arm-*-riscix,,arm-*-riscix}
1239 @uref{#decstation-*,,decstation-*}
1243 @uref{#dsp16xx,,dsp16xx}
1245 @uref{#elxsi-elxsi-bsd,,elxsi-elxsi-bsd}
1247 @uref{#h8300-hms,,h8300-hms}
1249 @uref{#hppa*-hp-hpux*,,hppa*-hp-hpux*}
1251 @uref{#hppa*-hp-hpux9,,hppa*-hp-hpux9}
1253 @uref{#hppa*-hp-hpux10,,hppa*-hp-hpux10}
1255 @uref{#hppa*-hp-hpux11,,hppa*-hp-hpux11}
1257 @uref{#*-*-freebsd*,,*-*-freebsd*}
1259 @uref{#i370-*-*,,i370-*-*}
1261 @uref{#*-*-linux-gnu,,*-*-linux-gnu}
1263 @uref{#ix86-*-linux*oldld,,i?86-*-linux*oldld}
1265 @uref{#ix86-*-linux*aout,,i?86-*-linux*aout}
1267 @uref{#ix86-*-linux*,,i?86-*-linux*}
1269 @uref{#ix86-*-sco,,i?86-*-sco}
1271 @uref{#ix86-*-sco3.2v4,,i?86-*-sco3.2v4}
1273 @uref{#ix86-*-sco3.2v5*,,i?86-*-sco3.2v5*}
1275 @uref{#ix86-*-udk,,i?86-*-udk}
1277 @uref{#ix86-*-isc,,i?86-*-isc}
1279 @uref{#ix86-*-esix,,i?86-*-esix}
1281 @uref{#ix86-ibm-aix,,i?86-ibm-aix}
1283 @uref{#ix86-sequent-bsd,,i?86-sequent-bsd}
1285 @uref{#ix86-sequent-ptx1*,,i?86-sequent-ptx1*, i?86-sequent-ptx2*}
1287 @uref{#ix86-*-sysv3*,,i?86-*-sysv3*}
1289 @uref{#i860-intel-osf*,,i860-intel-osf*}
1291 @uref{#*-lynx-lynxos,,*-lynx-lynxos}
1293 @uref{#*-ibm-aix*,,*-ibm-aix*}
1295 @uref{#m32r-*-elf,,m32r-*-elf}
1297 @uref{#m68000-hp-bsd,,m68000-hp-bsd}
1299 @uref{#m6811-elf,,m6811-elf}
1301 @uref{#m6812-elf,,m6812-elf}
1303 @uref{#m68k-altos,,m68k-altos}
1305 @uref{#m68k-apple-aux,,m68k-apple-aux}
1307 @uref{#m68k-att-sysv,,m68k-att-sysv}
1309 @uref{#m68k-bull-sysv,,m68k-bull-sysv}
1311 @uref{#m68k-crds-unox,,m68k-crds-unox}
1313 @uref{#m68k-hp-hpux,,m68k-hp-hpux}
1315 @uref{#m68k-*-nextstep*,,m68k-*-nextstep*}
1317 @uref{#m68k-ncr-*,,m68k-ncr-*}
1319 @uref{#m68k-sun,,m68k-sun}
1321 @uref{#m68k-sun-sunos4.1.1,,m68k-sun-sunos4.1.1}
1323 @uref{#m88k-*-svr3,,m88k-*-svr3}
1325 @uref{#m88k-*-dgux,,m88k-*-dgux}
1327 @uref{#m88k-tektronix-sysv3,,m88k-tektronix-sysv3}
1329 @uref{#mips-*-*,,mips-*-*}
1331 @uref{#mips-mips-bsd,,mips-mips-bsd}
1333 @uref{#mips-mips-riscos*,,mips-mips-riscos*}
1335 @uref{#mips*-sgi-irix4,,mips*-sgi-irix4}
1337 @uref{#mips*-sgi-irix5,,mips*-sgi-irix5}
1339 @uref{#mips*-sgi-irix6,,mips*-sgi-irix6}
1341 @uref{#mips-sony-sysv,,mips-sony-sysv}
1343 @uref{#ns32k-encore,,ns32k-encore}
1345 @uref{#ns32k-*-genix,,ns32k-*-genix}
1347 @uref{#ns32k-sequent,,ns32k-sequent}
1349 @uref{#ns32k-utek,,ns32k-utek}
1351 @uref{#powerpc-*-elf,,powerpc-*-elf, powerpc-*-sysv4}
1353 @uref{#powerpc-*-linux-gnu*,,powerpc-*-linux-gnu*}
1355 @uref{#powerpc-*-eabiaix,,powerpc-*-eabiaix}
1357 @uref{#powerpc-*-eabisim,,powerpc-*-eabisim}
1359 @uref{#powerpc-*-eabi,,powerpc-*-eabi}
1361 @uref{#powerpcle-*-elf,,powerpcle-*-elf, powerpcle-*-sysv4}
1363 @uref{#powerpcle-*-eabisim,,powerpcle-*-eabisim}
1365 @uref{#powerpcle-*-eabi,,powerpcle-*-eabi}
1367 @uref{#powerpcle-*-winnt,,powerpcle-*-winnt, powerpcle-*-pe}
1369 @uref{#romp-*-aos,,romp-*-aos, romp-*-mach}
1371 @uref{#*-*-solaris*,,*-*-solaris*}
1373 @uref{#sparc-sun-*,,sparc-sun-*}
1375 @uref{#sparc-sun-solaris*,,sparc-sun-solaris*}
1377 @uref{#sparc-sun-solaris2.7,,sparc-sun-solaris2.7}
1379 @uref{#*-sun-solaris2.8,,*-sun-solaris2.8}
1381 @uref{#sunv5,,Sun V5.0 Compiler Bugs}
1383 @uref{#sparc-sun-sunos*,,sparc-sun-sunos*}
1385 @uref{#sparc-unknown-linux-gnulibc1,,sparc-unknown-linux-gnulibc1}
1387 @uref{#sparc64-*-*,,sparc64-*-*}
1389 @uref{#*-*-sysv*,,*-*-sysv*}
1391 @uref{#vax-dec-ultrix,,vax-dec-ultrix}
1393 @uref{#we32k-*-*,,we32k-*-*}
1395 @uref{#windows,,Microsoft Windows}
1399 @uref{#older,,Older systems}
1404 @uref{#elf_targets,,all ELF targets} (SVR4, Solaris, etc.)
1410 <!-- -------- host/target specific issues start here ---------------- -->
1413 @heading @anchor{1750a-*-*}1750a-*-*
1414 MIL-STD-1750A processors.
1416 The MIL-STD-1750A cross configuration produces output for
1417 @code{as1750}, an assembler/linker available under the GNU Public
1418 License for the 1750A@. @code{as1750} can be obtained at
1419 @uref{ftp://ftp.fta-berlin.de/pub/crossgcc/1750gals/}.
1420 A similarly licensed simulator for
1421 the 1750A is available from same address.
1423 You should ignore a fatal error during the building of libgcc (libgcc is
1424 not yet implemented for the 1750A@.)
1426 The @code{as1750} assembler requires the file @file{ms1750.inc}, which is
1427 found in the directory @file{config/1750a}.
1429 GCC produced the same sections as the Fairchild F9450 C Compiler,
1434 The program code section.
1437 The read/write (RAM) data section.
1440 The read-only (ROM) constants section.
1443 Initialization section (code to copy KREL to SREL)@.
1446 The smallest addressable unit is 16 bits (BITS_PER_UNIT is 16). This
1447 means that type @code{char} is represented with a 16-bit word per character.
1448 The 1750A's ``Load/Store Upper/Lower Byte'' instructions are not used by
1455 @heading @anchor{a29k}a29k
1456 AMD Am29k-family processors. These are normally used in embedded
1457 applications. There are no standard Unix configurations.
1459 corresponds to AMD's standard calling sequence and binary interface
1460 and is compatible with other 29k tools.
1462 You may need to make a variant of the file @file{a29k.h} for your
1463 particular configuration.
1469 @heading @anchor{a29k-*-bsd}a29k-*-bsd
1470 AMD Am29050 used in a system running a variant of BSD Unix.
1476 @heading @anchor{alpha*-*-*}alpha*-*-*
1478 This section contains general configuration information for all
1479 alpha-based platforms using ELF (in particular, ignore this section for
1480 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
1481 section, please read all other sections that match your target.
1483 We require binutils 2.11.1 (as of yet unreleased), binutils with
1484 @samp{binutils-2_11-branch} tag after May 31, 2001 (as taken below), or newer.
1485 Previous binutils releases had a number of problems with DWARF2
1486 debugging information, not the least of which is incorrect linking of
1489 Until binutils 2.11.1 is released, these sample commands may be useful:
1492 mkdir binutils-2.11.X; cd binutils-2.11.X
1493 cvs -d :pserver:anoncvs@@anoncvs.cygnus.com:/cvs/src \
1494 co -rbinutils-2_11-branch -P binutils
1496 ../src/configure --prefix=@emph{an-absolute-path}
1497 make all check install
1500 When configuring gcc, provide explicit @option{--with-gnu-as}
1501 @option{--with-as=@emph{an-absolute-path/bin/as}} and
1502 @option{--with-gnu-ld} @option{--with-ld=@emph{an-absolute-path/bin/ld}}
1503 options to point into the prefix used above.
1509 @heading @anchor{alpha*-dec-osf*}alpha*-dec-osf*
1510 Systems using processors that implement the DEC Alpha architecture and
1511 are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
1512 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
1514 In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
1515 currently (2001-06-13) work with @command{mips-tfile}. As a workaround,
1516 we need to use the old assembler, invoked via the barely documented
1517 @option{-oldas} option. To bootstrap GCC, you either need to use the
1521 % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
1524 or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
1527 % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
1530 GCC writes a @samp{.verstamp} directive to the assembler output file
1531 unless it is built as a cross-compiler. It gets the version to use from
1532 the system header file @file{/usr/include/stamp.h}. If you install a
1533 new version of DEC Unix, you should rebuild GCC to pick up the new version
1536 Note that since the Alpha is a 64-bit architecture, cross-compilers from
1537 32-bit machines will not generate code as efficient as that generated
1538 when the compiler is running on a 64-bit machine because many
1539 optimizations that depend on being able to represent a word on the
1540 target in an integral value on the host cannot be performed. Building
1541 cross-compilers on the Alpha for 32-bit machines has only been tested in
1542 a few cases and may not work properly.
1544 @code{make compare} may fail on old versions of DEC Unix unless you add
1545 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
1546 assembler input file is stored in the object file, and that makes
1547 comparison fail if it differs between the @code{stage1} and
1548 @code{stage2} compilations. The option @option{-save-temps} forces a
1549 fixed name to be used for the assembler input file, instead of a
1550 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
1551 unless the comparisons fail without that option. If you add
1552 @option{-save-temps}, you will have to manually delete the @samp{.i} and
1553 @samp{.s} files after each series of compilations.
1555 GCC now supports both the native (ECOFF) debugging format used by DBX
1556 and GDB and an encapsulated STABS format for use only with GDB@. See the
1557 discussion of the @option{--with-stabs} option of @file{configure} above
1558 for more information on these formats and how to select them.
1560 There is a bug in DEC's assembler that produces incorrect line numbers
1561 for ECOFF format when the @samp{.align} directive is used. To work
1562 around this problem, GCC will not emit such alignment directives
1563 while writing ECOFF format debugging information even if optimization is
1564 being performed. Unfortunately, this has the very undesirable
1565 side-effect that code addresses when @option{-O} is specified are
1566 different depending on whether or not @option{-g} is also specified.
1568 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
1569 DBX@. DEC is now aware of this problem with the assembler and hopes to
1570 provide a fix shortly.
1576 @heading @anchor{arc-*-elf}arc-*-elf
1577 Argonaut ARC processor.
1578 This configuration is intended for embedded systems.
1584 @heading @anchor{arm-*-aout}arm-*-aout
1585 Advanced RISC Machines ARM-family processors. These are often used in
1586 embedded applications. There are no standard Unix configurations.
1587 This configuration corresponds to the basic instruction sequences and will
1588 produce @file{a.out} format object modules.
1590 You may need to make a variant of the file @file{arm.h} for your particular
1597 @heading @anchor{arm-*-elf}arm-*-elf
1598 This configuration is intended for embedded systems.
1604 @heading @anchor{arm*-*-linux-gnu}arm*-*-linux-gnu
1606 We require GNU binutils 2.10 or newer.
1612 @heading @anchor{arm-*-riscix}arm-*-riscix
1613 The ARM2 or ARM3 processor running RISC iX, Acorn's port of BSD Unix.
1614 If you are running a version of RISC iX prior to 1.2 then you must
1615 specify the version number during configuration. Note that the
1616 assembler shipped with RISC iX does not support stabs debugging
1617 information; a new version of the assembler, with stabs support
1618 included, is now available from Acorn and via ftp
1619 @uref{ftp://ftp.acorn.com/pub/riscix/as+xterm.tar.Z}. To enable stabs
1620 debugging, pass @option{--with-gnu-as} to configure.
1622 You will need to install GNU @command{sed} before you can run configure.
1628 @heading @anchor{avr}avr
1630 ATMEL AVR-family micro controllers. These are used in embedded
1631 applications. There are no standard Unix configurations. @xref{AVR
1632 Options,, AVR Options, gcc, Using and Porting the GNU Compiler
1633 Collection (GCC)}, for the list of supported MCU types.
1635 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
1637 Further installation notes and other useful information about AVR tools
1638 can also be obtained from:
1642 @uref{http://home.overta.ru/users/denisc,,http://home.overta.ru/users/denisc}
1644 @uref{http://www.itnet.pl/amelektr/avr,,http://www.itnet.pl/amelektr/avr}
1647 We @emph{strongly} recommend using binutils 2.11 or newer.
1649 The following error:
1651 Error: register required
1654 indicates that you should upgrade to a newer version of the binutils.
1660 @heading @anchor{c4x}c4x
1662 Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal
1663 Processors. These are used in embedded applications. There are no
1664 standard Unix configurations. @xref{C4x Options,, C4x Options, gcc,
1665 Using and Porting the GNU Compiler Collection (GCC)}, for the list of
1666 supported MCU types.
1668 GCC can be configured as a cross compiler for both the C3x and C4x
1669 architectures on the same system. Use @samp{configure --target=c4x
1670 --enable-languages="c,c++"} to configure.
1673 Further installation notes and other useful information about C4x tools
1674 can also be obtained from:
1678 @uref{http://www.elec.canterbury.ac.nz/c4x,,http://www.elec.canterbury.ac.nz/c4x}
1685 @heading @anchor{decstation-*}decstation-*
1686 MIPS-based DECstations can support three different personalities:
1687 Ultrix, DEC OSF/1, and OSF/rose. (Alpha-based DECstation products have
1688 a configuration name beginning with @samp{alpha-dec}.) To configure GCC
1689 for these platforms use the following configurations:
1692 @item decstation-ultrix
1693 Ultrix configuration.
1695 @item decstation-osf1
1696 Dec's version of OSF/1.
1698 @item decstation-osfrose
1699 Open Software Foundation reference port of OSF/1 which uses the
1700 OSF/rose object file format instead of ECOFF@. Normally, you
1701 would not select this configuration.
1704 The MIPS C compiler needs to be told to increase its table size
1705 for switch statements with the @option{-Wf,-XNg1500} option in
1706 order to compile @file{cp/parse.c}. If you use the @option{-O2}
1707 optimization option, you also need to use @option{-Olimit 3000}.
1708 Both of these options are automatically generated in the
1709 @file{Makefile} that the shell script @file{configure} builds.
1710 If you override the @code{CC} make variable and use the MIPS
1711 compilers, you may need to add @option{-Wf,-XNg1500 -Olimit 3000}.
1717 @heading @anchor{dos}DOS
1719 Please have a look at our @uref{binaries.html,,binaries page}.
1721 You cannot install GCC by itself on MSDOS; it will not compile under
1722 any MSDOS compiler except itself. You need to get the complete
1723 compilation package DJGPP, which includes binaries as well as sources,
1724 and includes all the necessary compilation tools and libraries.
1730 @heading @anchor{dsp16xx}dsp16xx
1731 A port to the AT&T DSP1610 family of processors.
1737 @heading @anchor{elxsi-elxsi-bsd}elxsi-elxsi-bsd
1738 The Elxsi's C compiler has known limitations that prevent it from
1739 compiling GCC@. Please contact @email{mrs@@cygnus.com} for more details.
1745 @heading @anchor{h8300-hms}h8300-hms
1746 Hitachi H8/300 series of processors.
1748 Please have a look at our @uref{binaries.html,,binaries page}.
1750 The calling convention and structure layout has changed in release 2.6.
1751 All code must be recompiled. The calling convention now passes the
1752 first three arguments in function calls in registers. Structures are no
1753 longer a multiple of 2 bytes.
1759 @heading @anchor{hppa*-hp-hpux*}hppa*-hp-hpux*
1761 We @emph{highly} recommend using gas/binutils-2.8 or newer on all hppa
1762 platforms; you may encounter a variety of problems when using the HP
1765 Specifically, @option{-g} does not work on HP-UX (since that system
1766 uses a peculiar debugging format which GCC does not know about), unless you
1767 use GAS and GDB and configure GCC with the
1768 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
1769 @option{--with-as=@dots{}} options.
1771 If you wish to use pa-risc 2.0 architecture support, you must use either
1772 the HP assembler, gas/binutils-2.11 or a recent
1773 @uref{ftp://sources.redhat.com/pub/binutils/snapshots,,snapshot of gas}.
1775 More specific information to hppa*-hp-hpux* targets follows.
1781 @heading @anchor{hppa*-hp-hpux9}hppa*-hp-hpux9
1783 The HP assembler has major problems on this platform. We've tried to work
1784 around the worst of the problems. However, those workarounds may be causing
1785 linker crashes in some circumstances; the workarounds also probably prevent
1786 shared libraries from working. Use the GNU assembler to avoid these problems.
1789 The configuration scripts for GCC will also trigger a bug in the hpux9
1790 shell. To avoid this problem set @env{CONFIG_SHELL} to @file{/bin/ksh}
1791 and @env{SHELL} to @file{/bin/ksh} in your environment.
1798 @heading @anchor{hppa*-hp-hpux10}hppa*-hp-hpux10
1800 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
1801 @code{PHCO_19798} from HP@. HP has two sites which provide patches free of
1807 <a href="http://us-support.external.hp.com">US, Canada, Asia-Pacific, and
1811 @uref{http://us-support.external.hp.com,,}US, Canada, Asia-Pacific, and
1815 @uref{http://europe-support.external.hp.com,,Europe}
1818 The HP assembler on these systems is much better than the hpux9 assembler,
1819 but still has some problems. Most notably the assembler inserts timestamps
1820 into each object file it creates, causing the 3-stage comparison test to fail
1821 during a @samp{make bootstrap}. You should be able to continue by
1822 saying @samp{make all} after getting the failure from @samp{make
1830 @heading @anchor{hppa*-hp-hpux11}hppa*-hp-hpux11
1832 GCC 3.0 supports HP-UX 11. You must use GNU binutils 2.11 or above on
1839 @heading @anchor{*-*-freebsd*}*-*-freebsd*
1841 The version of binutils installed in @file{/usr/bin} is known to work unless
1842 otherwise specified in any per-architecture notes. However, binutils
1843 2.11 is known to improve overall testsuite results.
1845 For FreeBSD 1, FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
1846 configuration support and files as shipped with gcc 2.95 are still in
1847 place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
1848 it is unknown which version of binutils was used (it is assumed that it
1849 was the system copy in @file{/usr/bin}) and C++ EH failures were noted.
1851 For FreeBSD using the ELF file format: DWARF2 debugging is now the
1852 default for all CPU architectures. It had been the default on
1853 FreeBSD/alpha since its inception. You may use @option{-gstabs} instead
1854 of @option{-g}, if you really want the old debugging format. There are
1855 no known issues with mixing object files and libraries with different
1856 debugging formats. Otherwise, this release of gcc should now match more
1857 of the configuration used in the stock FreeBSD configuration of gcc. In
1858 particular, @option{--enable-threads} is now configured by default.
1859 However, as a general user, do not attempt to replace the system
1860 compiler with this release. Known to bootstrap and check with good
1861 results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3 and 5-CURRENT@.
1863 At this time, @option{--enable-threads} is not compatible with
1864 @option{--enable-libgcj} on FreeBSD@.
1870 @heading @anchor{i370-*-*}i370-*-*
1871 This port is very preliminary and has many known bugs. We hope to
1872 have a higher-quality port for this machine soon.
1878 @heading @anchor{*-*-linux-gnu}*-*-linux-gnu
1880 If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install
1881 out-of-the-box. You'll get compile errors while building libstdc++.
1882 The patch @uref{glibc-2.2.patch,,glibc-2.2.patch}, that is to be
1883 applied in the GCC source tree, fixes the compatibility problems.
1893 Currently Glibc 2.2.3 (and older releases) and GCC 3.0 are out of sync
1894 since the latest exception handling changes for GCC@. Compiling glibc
1895 with GCC 3.0 will give a binary incompatible glibc and therefore cause
1896 lots of problems and might make your system completly unusable. This
1897 will definitly need fixes in glibc but might also need fixes in GCC@. We
1898 strongly advise to wait for glibc 2.2.4 and to read the release notes of
1899 glibc 2.2.4 whether patches for GCC 3.0 are needed. You can use glibc
1900 2.2.3 with GCC 3.0, just do not try to recompile it.
1906 @heading @anchor{ix86-*-linux*oldld}i?86-*-linux*oldld
1907 Use this configuration to generate @file{a.out} binaries on Linux-based
1908 GNU systems if you do not have gas/binutils version 2.5.2 or later
1909 installed. This is an obsolete configuration.
1915 @heading @anchor{ix86-*-linux*aout}i?86-*-linux*aout
1916 Use this configuration to generate @file{a.out} binaries on Linux-based
1917 GNU systems. This configuration is being superseded. You must use
1918 gas/binutils version 2.5.2 or later.
1924 @heading @anchor{ix86-*-linux*}i?86-*-linux*
1926 You will need binutils-2.9.1.0.15 or newer for exception handling to work.
1928 If you receive Signal 11 errors when building on GNU/Linux, then it is
1929 possible you have a hardware problem. Further information on this can be
1930 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
1936 @heading @anchor{ix86-*-sco}i?86-*-sco
1937 Compilation with RCC is recommended. Also, it may be a good idea to
1938 link with GNU malloc instead of the malloc that comes with the system.
1944 @heading @anchor{ix86-*-sco3.2v4}i?86-*-sco3.2v4
1945 Use this configuration for SCO release 3.2 version 4.
1951 @heading @anchor{ix86-*-sco3.2v5*}i?86-*-sco3.2v5*
1952 Use this for the SCO OpenServer Release 5 family of operating systems.
1954 Unlike earlier versions of GCC, the ability to generate COFF with this
1955 target is no longer provided.
1957 Earlier versions of GCC emitted Dwarf-1 when generating ELF to allow
1958 the system debugger to be used. That support was too burdensome to
1959 maintain. GCC now emits only dwarf-2 for this target. This means you
1960 may use either the UDK debugger or GDB to debug programs built by this
1963 If you are building languages other than C, you must follow the instructions
1964 about invoking @samp{make bootstrap} because the native OpenServer
1965 compiler will build a @command{cc1plus} that will not correctly parse many
1966 valid C++ programs including those in @file{libgcc.a}.
1967 @strong{You must do a @samp{make bootstrap} if you are building with the
1970 Use of the @option{-march-pentiumpro} flag can result in
1971 unrecognized opcodes when using the native assembler on OS versions before
1972 5.0.6. (Support for P6 opcodes was added to the native ELF assembler in
1973 that version.) While it's rather rare to see these emitted by GCC yet,
1974 errors of the basic form:
1977 /usr/tmp/ccaNlqBc.s:22:unknown instruction: fcomip
1978 /usr/tmp/ccaNlqBc.s:50:unknown instruction: fucomip
1981 are symptoms of this problem. You may work around this by not
1982 building affected files with that flag, by using the GNU assembler, or
1983 by using the assembler provided with the current version of the OS@.
1984 Users of GNU assembler should see the note below for hazards on doing
1987 The native SCO assembler that is provided with the OS at no
1988 charge is normally required. If, however, you must be able to use
1989 the GNU assembler (perhaps you're compiling code with asms that
1990 require GAS syntax) you may configure this package using the flags
1991 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You must
1992 use a recent version of GNU binutils; versions past 2.9.1 seem to work
1995 In general, the @option{--with-gnu-as} option isn't as well tested
1996 as the native assembler.
1998 Look in @file{gcc/config/i386/sco5.h} (search for ``messy'') for
1999 additional OpenServer-specific flags.
2001 Systems based on OpenServer before 5.0.4 (@samp{uname -X}
2002 will tell you what you're running) require TLS597 from ftp.sco.com/TLS
2003 for C++ constructors and destructors to work right.
2005 The system linker in (at least) 5.0.4 and 5.0.5 will sometimes
2006 do the wrong thing for a construct that GCC will emit for PIC
2007 code. This can be seen as execution testsuite failures when using
2008 @option{-fPIC} on @file{921215-1.c}, @file{931002-1.c}, @file{nestfunc-1.c}, and @file{gcov-1.c}.
2009 For 5.0.5, an updated linker that will cure this problem is
2010 available. You must install both
2011 @uref{ftp://ftp.sco.com/Supplements/rs505a/,,ftp://ftp.sco.com/Supplements/rs505a/}
2012 and @uref{ftp://ftp.sco.com/SLS/,,OSS499A}.
2014 The dynamic linker in OpenServer 5.0.5 (earlier versions may show
2015 the same problem) aborts on certain g77-compiled programs. It's particularly
2016 likely to be triggered by building Fortran code with the @option{-fPIC} flag.
2017 Although it's conceivable that the error could be triggered by other
2018 code, only G77-compiled code has been observed to cause this abort.
2019 If you are getting core dumps immediately upon execution of your
2020 g77 program---and especially if it's compiled with @option{-fPIC}---try applying
2021 @uref{sco_osr5_g77.patch,,@file{sco_osr5_g77.patch}} to your libf2c and
2023 Affected faults, when analyzed in a debugger, will show a stack
2024 backtrace with a fault occurring in @code{rtld()} and the program
2025 running as @file{/usr/lib/ld.so.1}. This problem has been reported to SCO
2026 engineering and will hopefully be addressed in later releases.
2033 @heading @anchor{ix86-*-udk}i?86-*-udk
2035 This target emulates the SCO Universal Development Kit and requires that
2036 package be installed. (If it is installed, you will have a
2037 @file{/udk/usr/ccs/bin/cc} file present.) It's very much like the
2038 @code{i?86-*-unixware7*} target
2039 but is meant to be used when hosting on a system where UDK isn't the
2040 default compiler such as OpenServer 5 or Unixware 2. This target will
2041 generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
2042 with the same warnings and caveats as the SCO UDK@.
2044 You can stage1 with either your native compiler or with UDK@. If you
2045 don't do a full bootstrap when initially building with your native compiler
2046 you will have an utterly unusable pile of bits as your reward.
2048 This target is a little tricky to build because we have to distinguish
2049 it from the native tools (so it gets headers, startups, and libraries
2050 from the right place) while making the tools not think we're actually
2051 building a cross compiler. The easiest way to do this is with a configure
2054 @samp{CC=/udk/usr/ccs/bin/cc @var{/your/path/to}/gcc/configure
2055 --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-}
2057 @emph{You should substitute @samp{i686} in the above command with the appropriate
2058 processor for your host.}
2060 You should follow this with a @samp{make bootstrap} then
2061 @samp{make install}. You can then access the UDK-targeted GCC
2062 tools by adding @command{udk-} before the commonly known name. For
2063 example, to invoke the C compiler, you would use @command{udk-gcc}.
2064 They will coexist peacefully with any native-target GCC tools you may
2072 @heading @anchor{ix86-*-isc}i?86-*-isc
2073 It may be a good idea to link with GNU malloc instead of the malloc that
2074 comes with the system.
2076 In ISC version 4.1, @command{sed} core dumps when building
2077 @file{deduced.h}. Use the version of @command{sed} from version 4.0.
2083 @heading @anchor{ix86-*-esix}i?86-*-esix
2084 It may be good idea to link with GNU malloc instead of the malloc that
2085 comes with the system.
2091 @heading @anchor{ix86-ibm-aix}i?86-ibm-aix
2092 You need to use GAS version 2.1 or later, and LD from
2093 GNU binutils version 2.2 or later.
2099 @heading @anchor{ix86-sequent-bsd}i?86-sequent-bsd
2100 Go to the Berkeley universe before compiling.
2106 @heading @anchor{ix86-sequent-ptx1*}i?86-sequent-ptx1*, i?86-sequent-ptx2*
2107 You must install GNU @file{sed} before running @file{configure}.
2113 @heading @anchor{#ix86-*-sysv3*}i?86-*-sysv3*
2114 The @code{fixproto} shell script may trigger a bug in the system shell.
2115 If you encounter this problem, upgrade your operating system or
2116 use BASH (the GNU shell) to run @code{fixproto}.
2123 @heading @anchor{i860-intel-osf*}i860-intel-osf*
2124 On the Intel Paragon (an i860 machine), if you are using operating
2125 system version 1.0, you will get warnings or errors about redefinition
2126 of @code{va_arg} when you build GCC@.
2128 If this happens, then you need to link most programs with the library
2129 @file{iclib.a}. You must also modify @file{stdio.h} as follows: before
2133 #if defined(__i860__) && !defined(_VA_LIST)
2134 #include <va_list.h>
2148 extern int vprintf(const char *, va_list );
2149 extern int vsprintf(char *, const char *, va_list );
2157 #endif /* __PGC__ */
2160 These problems don't exist in operating system version 1.1.
2166 @heading @anchor{*-lynx-lynxos}*-lynx-lynxos
2167 LynxOS 2.2 and earlier comes with GCC 1.x already installed as
2168 @file{/bin/gcc}. You should compile with this instead of @file{/bin/cc}.
2169 You can tell GCC to use the GNU assembler and linker, by specifying
2170 @samp{--with-gnu-as --with-gnu-ld} when configuring. These will produce
2171 COFF format object files and executables; otherwise GCC will use the
2172 installed tools, which produce @file{a.out} format executables.
2177 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
2179 @heading @anchor{*-ibm-aix*}*-ibm-aix*
2181 AIX Make frequently has problems with GCC makefiles. GNU Make 3.76 or
2182 newer is recommended to build on this platform.
2184 Errors involving @code{alloca} when building GCC generally are due
2185 to an incorrect definition of @var{CC} in the Makefile or mixing files
2186 compiled with the native C compiler and GCC@. During the stage1 phase of
2187 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
2188 (not @command{xlc}). Once @command{configure} has been informed of
2189 @command{xlc}, one needs to use @samp{make distclean} to remove the
2190 configure cache files and ensure that @env{CC} environment variable
2191 does not provide a definition that will confuse @command{configure}.
2192 If this error occurs during stage2 or later, then the problem most likely
2193 is the version of Make (see above).
2195 Binutils 2.10 does not support AIX 4.3. Binutils available from the
2196 @uref{http://www-1.ibm.com/servers/aix/products/aixos/linux/,,AIX
2197 Toolbox for Linux: GNU and Open Source tools for AIX};
2198 website does work. Binutils 2.11 is expected to include AIX 4.3
2199 support. The GNU Assembler is necessary for libstdc++ to build. The
2200 AIX native ld still is recommended. The native AIX tools do
2201 interoperate with GCC@.
2203 Linking executables and shared libraries may produce warnings of
2204 duplicate symbols. The assembly files generated by GCC for AIX always
2205 have included multiple symbol definitions for certain global variable
2206 and function declarations in the original program. The warnings should
2207 not prevent the linker from producing a correct library or runnable
2210 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
2211 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
2212 to parse archive libraries did not handle the new format correctly.
2213 These routines are used by GCC and result in error messages during
2214 linking such as ``not a COFF file''. The version of the routines shipped
2215 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
2216 option of the archive command may be used to create archives of 32-bit
2217 objects using the original ``small format''. A correct version of the
2218 routines is shipped with AIX 4.3.2.
2220 Some versions of the AIX binder (linker) can fail with a relocation
2221 overflow severe error when the @option{-bbigtoc} option is used to link
2222 GCC-produced object files into an executable that overflows the TOC@. A fix
2223 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
2224 available from IBM Customer Support and from its
2225 @uref{http://service.boulder.ibm.com/,,service.boulder.ibm.com}
2226 website as PTF U455193.
2228 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
2229 with a segmentation fault when invoked by any version of GCC@. A fix for
2230 APAR IX87327 is available from IBM Customer Support and from its
2231 @uref{http://service.boulder.ibm.com/,,service.boulder.ibm.com}
2232 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
2234 The initial assembler shipped with AIX 4.3.0 generates incorrect object
2235 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
2236 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
2237 @uref{http://service.boulder.ibm.com/,,service.boulder.ibm.com}
2238 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
2240 AIX provides National Language Support (NLS)@. Compilers and assemblers
2241 use NLS to support locale-specific representations of various data
2242 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
2243 separating decimal fractions). There have been problems reported where
2244 GCC does not produce the same floating-point formats that the assembler
2245 expects. If one encounters this problem, set the @env{LANG}
2246 environment variable to @samp{C} or @samp{En_US}.
2248 By default, GCC for AIX 4.1 and above produces code that can be used on
2249 both Power or PowerPC processors.
2251 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
2252 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
2258 @heading @anchor{m32r-*-elf}m32r-*-elf
2259 Mitsubishi M32R processor.
2260 This configuration is intended for embedded systems.
2266 @heading @anchor{m68000-hp-bsd}m68000-hp-bsd
2267 HP 9000 series 200 running BSD@. Note that the C compiler that comes
2268 with this system cannot compile GCC; contact @email{law@@cygnus.com}
2269 to get binaries of GCC for bootstrapping.
2275 @heading @anchor{m6811-elf}m6811-elf
2276 Motorola 68HC11 family micro controllers. These are used in embedded
2277 applications. There are no standard Unix configurations.
2283 @heading @anchor{m6812-elf}m6812-elf
2284 Motorola 68HC12 family micro controllers. These are used in embedded
2285 applications. There are no standard Unix configurations.
2291 @heading @anchor{m68k-altos}m68k-altos
2292 Altos 3068. You must use the GNU assembler, linker and debugger.
2293 Also, you must fix a kernel bug. Details in the file @file{README.ALTOS}.
2299 @heading @anchor{m68k-apple-aux}m68k-apple-aux
2300 Apple Macintosh running A/UX@.
2301 You may configure GCC to use either the system assembler and
2302 linker or the GNU assembler and linker. You should use the GNU configuration
2303 if you can, especially if you also want to use G++. You enabled
2304 that configuration with + the @option{--with-gnu-as} and @option{--with-gnu-ld}
2305 options to @code{configure}.
2307 Note the C compiler that comes
2308 with this system cannot compile GCC@. You can find binaries of GCC
2309 for bootstrapping on @code{jagubox.gsfc.nasa.gov}.
2310 You will also a patched version of @file{/bin/ld} there that
2311 raises some of the arbitrary limits found in the original.
2317 @heading @anchor{m68k-att-sysv}m68k-att-sysv
2318 AT&T 3b1, a.k.a.@: 7300 PC@. This version of GCC cannot
2319 be compiled with the system C compiler, which is too buggy.
2320 You will need to get a previous version of GCC and use it to
2321 bootstrap. Binaries are available from the OSU-CIS archive, at
2322 @uref{ftp://archive.cis.ohio-state.edu/pub/att7300/}.
2328 @heading @anchor{m68k-bull-sysv}m68k-bull-sysv
2329 Bull DPX/2 series 200 and 300 with BOS-2.00.45 up to BOS-2.01. GCC works
2330 either with native assembler or GNU assembler. You can use
2331 GNU assembler with native coff generation by providing @option{--with-gnu-as} to
2332 the configure script or use GNU assembler with dbx-in-coff encapsulation
2333 by providing @samp{--with-gnu-as --stabs}. For any problem with native
2334 assembler or for availability of the DPX/2 port of GAS, contact
2335 @email{F.Pierresteguy@@frcl.bull.fr}.
2341 @heading @anchor{m68k-crds-unox}m68k-crds-unox
2342 Use @samp{configure unos} for building on Unos.
2344 The Unos assembler is named @code{casm} instead of @code{as}. For some
2345 strange reason linking @file{/bin/as} to @file{/bin/casm} changes the
2346 behavior, and does not work. So, when installing GCC, you should
2347 install the following script as @file{as} in the subdirectory where
2348 the passes of GCC are installed:
2355 The default Unos library is named @file{libunos.a} instead of
2356 @file{libc.a}. To allow GCC to function, either change all
2357 references to @option{-lc} in @file{gcc.c} to @option{-lunos} or link
2358 @file{/lib/libc.a} to @file{/lib/libunos.a}.
2360 @cindex @code{alloca}, for Unos
2361 When compiling GCC with the standard compiler, to overcome bugs in
2362 the support of @code{alloca}, do not use @option{-O} when making stage 2.
2363 Then use the stage 2 compiler with @option{-O} to make the stage 3
2364 compiler. This compiler will have the same characteristics as the usual
2365 stage 2 compiler on other systems. Use it to make a stage 4 compiler
2366 and compare that with stage 3 to verify proper compilation.
2368 (Perhaps simply defining @code{ALLOCA} in @file{x-crds} as described in
2369 the comments there will make the above paragraph superfluous. Please
2370 inform us of whether this works.)
2372 Unos uses memory segmentation instead of demand paging, so you will need
2373 a lot of memory. 5 Mb is barely enough if no other tasks are running.
2374 If linking @file{cc1} fails, try putting the object files into a library
2375 and linking from that library.
2381 @heading @anchor{m68k-hp-hpux}m68k-hp-hpux
2382 HP 9000 series 300 or 400 running HP-UX@. HP-UX version 8.0 has a bug in
2383 the assembler that prevents compilation of GCC@. This
2384 bug manifests itself during the first stage of compilation, while
2385 building @file{libgcc2.a}:
2389 cc1: warning: `-g' option not supported on this version of GCC
2390 cc1: warning: `-g1' option not supported on this version of GCC
2391 ./xgcc: Internal compiler error: program as got fatal signal 11
2394 A patched version of the assembler is available as the file
2395 @uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you
2396 have HP software support, the patch can also be obtained directly from
2397 HP, as described in the following note:
2400 This is the patched assembler, to patch SR#1653-010439, where the
2401 assembler aborts on floating point constants.
2403 The bug is not really in the assembler, but in the shared library
2404 version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is
2405 SR#4701-078451. Anyway, the attached assembler uses the archive
2406 library version of ``cvtnum(3c)'' and thus does not exhibit the bug.
2409 This patch is also known as PHCO_4484.
2411 In addition, if you wish to use gas @option{--with-gnu-as} you must use
2412 gas version 2.1 or later, and you must use the GNU linker version 2.1 or
2413 later. Earlier versions of gas relied upon a program which converted the
2414 gas output into the native HP-UX format, but that program has not been
2415 kept up to date. gdb does not understand that native HP-UX format, so
2416 you must use gas if you wish to use gdb.
2418 On HP-UX version 8.05, but not on 8.07 or more recent versions, the
2419 @code{fixproto} shell script triggers a bug in the system shell. If you
2420 encounter this problem, upgrade your operating system or use BASH (the
2421 GNU shell) to run @code{fixproto}. This bug will cause the fixproto
2422 program to report an error of the form:
2425 ./fixproto: sh internal 1K buffer overflow
2428 To fix this, you can also change the first line of the fixproto script
2440 @heading @anchor{m68k-*-nextstep*}m68k-*-nextstep*
2442 Current GCC versions probably do not work on version 2 of the NeXT
2445 On NeXTStep 3.0, the Objective-C compiler does not work, due,
2446 apparently, to a kernel bug that it happens to trigger. This problem
2447 does not happen on 3.1.
2449 You absolutely @strong{must} use GNU sed and GNU make on this platform.
2452 On NeXTSTEP 3.x where x < 3 the build of GCC will abort during
2453 stage1 with an error message like this:
2457 /usr/tmp/ccbbsZ0U.s:987:Unknown pseudo-op: .section
2458 /usr/tmp/ccbbsZ0U.s:987:Rest of line ignored. 1st junk character
2462 The reason for this is the fact that NeXT's assembler for these
2463 versions of the operating system does not support the @samp{.section}
2464 pseudo op that's needed for full C++ exception functionality.
2466 As NeXT's assembler is a derived work from GNU as, a free
2467 replacement that does can be obtained at
2468 @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}.
2470 If you try to build the integrated C++ & C++ runtime libraries on this system
2471 you will run into trouble with include files. The way to get around this is
2472 to use the following sequence. Note you must have write permission to
2473 the directory @var{prefix} you specified in the configuration process of GCC
2474 for this sequence to work.
2478 make all-texinfo all-bison all-byacc all-binutils all-gas all-ld
2481 make install-headers-tar
2490 @heading @anchor{m68k-ncr-*}m68k-ncr-*
2491 On the Tower models 4@var{n}0 and 6@var{n}0, by default a process is not
2492 allowed to have more than one megabyte of memory. GCC cannot compile
2493 itself (or many other programs) with @option{-O} in that much memory.
2495 To solve this problem, reconfigure the kernel adding the following line
2496 to the configuration file:
2507 @heading @anchor{m68k-sun}m68k-sun
2508 Sun 3. We do not provide a configuration file to use the Sun FPA by
2509 default, because programs that establish signal handlers for floating
2510 point traps inherently cannot work with the FPA@.
2516 @heading @anchor{m68k-sun-sunos4.1.1}m68k-sun-sunos4.1.1
2518 It is reported that you may need the GNU assembler on this platform.
2525 @heading @anchor{m88k-*-svr3}m88k-*-svr3
2526 Motorola m88k running the AT&T/Unisoft/Motorola V.3 reference port.
2527 These systems tend to use the Green Hills C, revision 1.8.5, as the
2528 standard C compiler. There are apparently bugs in this compiler that
2529 result in object files differences between stage 2 and stage 3. If this
2530 happens, make the stage 4 compiler and compare it to the stage 3
2531 compiler. If the stage 3 and stage 4 object files are identical, this
2532 suggests you encountered a problem with the standard C compiler; the
2533 stage 3 and 4 compilers may be usable.
2535 It is best, however, to use an older version of GCC for bootstrapping
2542 @heading @anchor{m88k-*-dgux}m88k-*-dgux
2543 Motorola m88k running DG/UX@. To build 88open BCS native or cross
2544 compilers on DG/UX, specify the configuration name as
2545 @samp{m88k-*-dguxbcs} and build in the 88open BCS software development
2546 environment. To build ELF native or cross compilers on DG/UX, specify
2547 @samp{m88k-*-dgux} and build in the DG/UX ELF development environment.
2548 You set the software development environment by issuing
2549 @samp{sde-target} command and specifying either @samp{m88kbcs} or
2550 @samp{m88kdguxelf} as the operand.
2552 If you do not specify a configuration name, @file{configure} guesses the
2553 configuration based on the current software development environment.
2559 @heading @anchor{m88k-tektronix-sysv3}m88k-tektronix-sysv3
2560 Tektronix XD88 running UTekV 3.2e. Do not turn on
2561 optimization while building stage1 if you bootstrap with
2562 the buggy Green Hills compiler. Also, The bundled LAI
2563 System V NFS is buggy so if you build in an NFS mounted
2564 directory, start from a fresh reboot, or avoid NFS all together.
2565 Otherwise you may have trouble getting clean comparisons
2572 @heading @anchor{mips-*-*}mips-*-*
2573 If you use the 1.31 version of the MIPS assembler (such as was shipped
2574 with Ultrix 3.1), you will need to use the @option{-fno-delayed-branch} switch
2575 when optimizing floating point code. Otherwise, the assembler will
2576 complain when the GCC compiler fills a branch delay slot with a
2577 floating point instruction, such as @code{add.d}.
2579 If on a MIPS system you get an error message saying ``does not have gp
2580 sections for all it's [sic] sectons [sic]'', don't worry about it. This
2581 happens whenever you use GAS with the MIPS linker, but there is not
2582 really anything wrong, and it is okay to use the output file. You can
2583 stop such warnings by installing the GNU linker.
2585 It would be nice to extend GAS to produce the gp tables, but they are
2586 optional, and there should not be a warning about their absence.
2588 Users have reported some problems with version 2.0 of the MIPS
2589 compiler tools that were shipped with Ultrix 4.1. Version 2.10
2590 which came with Ultrix 4.2 seems to work fine.
2592 Users have also reported some problems with version 2.20 of the
2593 MIPS compiler tools that were shipped with RISC/os 4.x. The earlier
2594 version 2.11 seems to work fine.
2596 Some versions of the MIPS linker will issue an assertion failure
2597 when linking code that uses @code{alloca} against shared
2598 libraries on RISC-OS 5.0, and DEC's OSF/1 systems. This is a bug
2599 in the linker, that is supposed to be fixed in future revisions.
2600 To protect against this, GCC passes @option{-non_shared} to the
2601 linker unless you pass an explicit @option{-shared} or
2602 @option{-call_shared} switch.
2604 @heading @anchor{mips-mips-bsd}mips-mips-bsd
2605 MIPS machines running the MIPS operating system in BSD mode. It's
2606 possible that some old versions of the system lack the functions
2607 @code{memcpy}, @code{memmove}, @code{memcmp}, and @code{memset}. If your
2608 system lacks these, you must remove or undo the definition of
2609 @code{TARGET_MEM_FUNCTIONS} in @file{mips-bsd.h}.
2611 The MIPS C compiler needs to be told to increase its table size
2612 for switch statements with the @option{-Wf,-XNg1500} option in
2613 order to compile @file{cp/parse.c}. If you use the @option{-O2}
2614 optimization option, you also need to use @option{-Olimit 3000}.
2615 Both of these options are automatically generated in the
2616 @file{Makefile} that the shell script @file{configure} builds.
2617 If you override the @code{CC} make variable and use the MIPS
2618 compilers, you may need to add @option{-Wf,-XNg1500 -Olimit 3000}.
2624 @heading @anchor{mips-mips-riscos*}mips-mips-riscos*
2625 The MIPS C compiler needs to be told to increase its table size
2626 for switch statements with the @option{-Wf,-XNg1500} option in
2627 order to compile @file{cp/parse.c}. If you use the @option{-O2}
2628 optimization option, you also need to use @option{-Olimit 3000}.
2629 Both of these options are automatically generated in the
2630 @file{Makefile} that the shell script @file{configure} builds.
2631 If you override the @code{CC} make variable and use the MIPS
2632 compilers, you may need to add @samp{-Wf,-XNg1500 -Olimit 3000}.
2634 MIPS computers running RISC-OS can support four different
2635 personalities: default, BSD 4.3, System V.3, and System V.4
2636 (older versions of RISC-OS don't support V.4). To configure GCC
2637 for these platforms use the following configurations:
2640 @item mips-mips-riscos@code{rev}
2641 Default configuration for RISC-OS, revision @code{rev}.
2643 @item mips-mips-riscos@code{rev}bsd
2644 BSD 4.3 configuration for RISC-OS, revision @code{rev}.
2646 @item mips-mips-riscos@code{rev}sysv4
2647 System V.4 configuration for RISC-OS, revision @code{rev}.
2653 @item mips-mips-riscos@code{rev}sysv
2654 System V.3 configuration for RISC-OS, revision @code{rev}.
2657 The revision @code{rev} mentioned above is the revision of
2658 RISC-OS to use. You must reconfigure GCC when going from a
2659 RISC-OS revision 4 to RISC-OS revision 5. This has the effect of
2660 avoiding a linker bug.
2666 @heading @anchor{mips*-sgi-irix4*}mips*-sgi-irix4*
2668 In order to compile GCC on an SGI running IRIX 4, the ``c.hdr.lib''
2669 option must be installed from the CD-ROM supplied from Silicon Graphics.
2670 This is found on the 2nd CD in release 4.0.1.
2672 On IRIX version 4.0.5F, and perhaps on some other versions as well,
2673 there is an assembler bug that reorders instructions incorrectly. To
2674 work around it, specify the target configuration
2675 @samp{mips-sgi-irix4loser}. This configuration inhibits assembler
2678 In a compiler configured with target @samp{mips-sgi-irix4}, you can turn
2679 off assembler optimization by using the @option{-noasmopt} option. This
2680 compiler option passes the option @option{-O0} to the assembler, to
2683 The @option{-noasmopt} option can be useful for testing whether a problem
2684 is due to erroneous assembler reordering. Even if a problem does not go
2685 away with @option{-noasmopt}, it may still be due to assembler
2686 reordering---perhaps GCC itself was miscompiled as a result.
2688 You may get the following warning on IRIX 4 platforms, it can be safely
2691 warning: foo.o does not have gp tables for all its sections.
2698 @heading @anchor{mips*-sgi-irix5*}mips*-sgi-irix5*
2700 In order to compile GCC on an SGI running IRIX 5, the ``compiler_dev.hdr''
2701 subsystem must be installed from the IDO CD-ROM supplied by Silicon
2702 Graphics. It is also available for download from
2703 @uref{http://www.sgi.com/developers/devtools/apis/ido.html,,http://www.sgi.com/developers/devtools/apis/ido.html}.
2705 @code{make compare} may fail on version 5 of IRIX unless you add
2706 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
2707 assembler input file is stored in the object file, and that makes
2708 comparison fail if it differs between the @code{stage1} and
2709 @code{stage2} compilations. The option @option{-save-temps} forces a
2710 fixed name to be used for the assembler input file, instead of a
2711 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
2712 unless the comparisons fail without that option. If you do you
2713 @option{-save-temps}, you will have to manually delete the @samp{.i} and
2714 @samp{.s} files after each series of compilations.
2716 If you use the MIPS C compiler to bootstrap, it may be necessary
2717 to increase its table size for switch statements with the
2718 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
2719 optimization option, you also need to use @option{-Olimit 3000}.
2721 To enable debugging under IRIX 5, you must use GNU @command{as} 2.5 or later,
2722 and use the @option{--with-gnu-as} configure option when configuring GCC.
2723 GNU @command{as} is distributed as part of the binutils package.
2725 You must use GNU @command{as} on these platforms, as the native
2726 assembler can not handle the code for exception handling support. Either
2727 of these messages indicates that you are using the MIPS assembler when
2728 instead you should be using GNU @command{as}:
2731 as0: Error: ./libgcc2.c, line 1:Badly delimited numeric literal
2732 .4byte $LECIE1-$LSCIE1
2733 as0: Error: ./libgcc2.c, line 1:malformed statement
2739 as0: Error: ./libgcc2.c, line 1:undefined symbol in expression
2740 .word $LECIE1-$LSCIE1
2743 When building GCC, the build process loops rebuilding @command{cc1} over
2744 and over again. This happens on @samp{mips-sgi-irix5.2}, and possibly
2745 other platforms. It has been reported that this is a known bug in the
2746 @command{make} shipped with IRIX 5.2. We recommend you use GNU
2747 @command{make} instead of the vendor supplied @command{make} program;
2748 however, you may have success with @command{smake} on IRIX 5.2 if you do
2749 not have GNU @command{make} available.
2755 @heading @anchor{mips*-sgi-irix6}mips*-sgi-irix6
2757 If you are using IRIX @command{cc} as your bootstrap compiler, you must
2758 ensure that the N32 ABI is in use. To test this, compile a simple C
2759 file with @command{cc} and then run @command{file} on the
2760 resulting object file. The output should look like:
2763 test.o: ELF N32 MSB @dots{}
2769 test.o: ELF 32-bit MSB @dots{}
2775 test.o: ELF 64-bit MSB @dots{}
2778 then your version of @command{cc} uses the O32 or N64 ABI by default. You
2779 should set the environment variable @env{CC} to @samp{cc -n32}
2780 before configuring GCC@.
2782 GCC on IRIX 6 is usually built to support both the N32 and N64 ABIs. If
2783 you build GCC on a system that doesn't have the N64 libraries installed,
2784 you need to configure with @option{--disable-multilib} so GCC doesn't
2785 try to use them. Look for @file{/usr/lib64/libc.so.1} to see if you
2786 have the 64-bit libraries installed.
2788 You must @emph{not} use GNU @command{as} (which isn't built anyway as of
2789 binutils 2.11.2) on IRIX 6 platforms; doing so will only cause problems.
2791 GCC does not currently support generating O32 ABI binaries in the
2792 @samp{mips-sgi-irix6} configurations. It used to be possible to create a GCC
2793 with O32 ABI only support by configuring it for the @samp{mips-sgi-irix5}
2794 target, which doesn't currently (2001-06-13) work itself. It is
2795 expected that O32 ABI support will be available again in a future release.
2797 GCC does not correctly pass/return structures which are
2798 smaller than 16 bytes and which are not 8 bytes. The problem is very
2799 involved and difficult to fix. It affects a number of other targets also,
2800 but IRIX 6 is affected the most, because it is a 64 bit target, and 4 byte
2801 structures are common. The exact problem is that structures are being padded
2802 at the wrong end, e.g.@: a 4 byte structure is loaded into the lower 4 bytes
2803 of the register when it should be loaded into the upper 4 bytes of the
2806 GCC is consistent with itself, but not consistent with the SGI C compiler
2807 (and the SGI supplied runtime libraries), so the only failures that can
2808 happen are when there are library functions that take/return such
2809 structures. There are very few such library functions. Currently this
2810 is known to affect @code{inet_ntoa}, @code{inet_lnaof},
2811 @code{inet_netof}, @code{inet_makeaddr}, and @code{semctl}.
2813 See @uref{http://freeware.sgi.com/,,http://freeware.sgi.com/} for more
2814 information about using GCC on IRIX platforms.
2820 @heading @anchor{mips-sony-sysv}mips-sony-sysv
2821 Sony MIPS NEWS@. This works in NEWSOS 5.0.1, but not in 5.0.2 (which
2822 uses ELF instead of COFF)@. Support for 5.0.2 will probably be provided
2823 soon by volunteers. In particular, the linker does not like the
2824 code generated by GCC when shared libraries are linked in.
2831 @heading @anchor{ns32k-encore}ns32k-encore
2832 Encore ns32000 system. Encore systems are supported only under BSD@.
2838 @heading @anchor{ns32k-*-genix}ns32k-*-genix
2839 National Semiconductor ns32000 system. Genix has bugs in @code{alloca}
2840 and @code{malloc}; you must get the compiled versions of these from GNU
2847 @heading @anchor{ns32k-sequent}ns32k-sequent
2848 Go to the Berkeley universe before compiling.
2854 @heading @anchor{ns32k-utek}ns32k-utek
2855 UTEK ns32000 system (``merlin''). The C compiler that comes with this
2856 system cannot compile GCC; contact @samp{tektronix!reed!mason} to get
2857 binaries of GCC for bootstrapping.
2864 @heading @anchor{powerpc-*-elf}powerpc-*-elf, powerpc-*-sysv4
2865 PowerPC system in big endian mode, running System V.4.
2867 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
2868 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
2874 @heading @anchor{powerpc-*-linux-gnu*}powerpc-*-linux-gnu*
2877 @uref{ftp://ftp.varesearch.com/pub/support/hjl/binutils,,binutils-2.9.4.0.8}
2878 or newer for a working GCC@. It is strongly recommended to recompile binutils
2879 if you initially built it with gcc-2.7.2.x.
2881 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
2882 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
2888 @heading @anchor{powerpc-*-eabiaix}powerpc-*-eabiaix
2889 Embedded PowerPC system in big endian mode with @option{-mcall-aix} selected as
2892 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
2893 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
2899 @heading @anchor{powerpc-*-eabisim}powerpc-*-eabisim
2900 Embedded PowerPC system in big endian mode for use in running under the
2903 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
2904 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
2910 @heading @anchor{powerpc-*-eabi}powerpc-*-eabi
2911 Embedded PowerPC system in big endian mode.
2913 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
2914 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
2920 @heading @anchor{powerpcle-*-elf}powerpcle-*-elf, powerpcle-*-sysv4
2921 PowerPC system in little endian mode, running System V.4.
2923 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
2924 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
2930 @heading @anchor{powerpcle-*-eabisim}powerpcle-*-eabisim
2931 Embedded PowerPC system in little endian mode for use in running under
2938 @heading @anchor{powerpcle-*-eabi}powerpcle-*-eabi
2939 Embedded PowerPC system in little endian mode.
2941 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
2942 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
2948 @heading @anchor{powerpcle-*-winnt}powerpcle-*-winnt, powerpcle-*-pe
2949 PowerPC system in little endian mode running Windows NT@.
2951 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
2952 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
2958 @heading @anchor{romp-*-aos}romp-*-aos, romp-*-mach
2959 The only operating systems supported for the IBM RT PC are AOS and
2960 MACH@. GCC does not support AIX running on the RT@. We recommend you
2961 compile GCC with an earlier version of itself; if you compile GCC
2962 with @code{hc}, the Metaware compiler, it will work, but you will get
2963 mismatches between the stage 2 and stage 3 compilers in various files.
2964 These errors are minor differences in some floating-point constants and
2965 can be safely ignored; the stage 3 compiler is correct.
2971 @heading @anchor{*-*-solaris*}*-*-solaris*
2973 Starting with Solaris, Sun does not ship a C compiler any more. To
2974 bootstrap and install GCC you first have to install a pre-built
2975 compiler, see our @uref{binaries.html,,binaries page} for
2978 You must use GNU Make to build GCC on Solaris 2. If you don't have GNU
2979 Make installed, you can use the prebuilt compiler mentioned above to
2982 Sun as 4.X is broken in that it cannot cope with long symbol names.
2983 A typical error message might look similar to the following:
2985 @samp{/usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041:
2986 error: can't compute value of an expression involving an external symbol.}
2988 This is Sun bug 4237974. This is fixed with patch 108908-02 and has
2989 been fixed in later (5.x) versions of the assembler.
2991 Solaris' @file{/bin/sh} will often fail to configure libstdc++-v3, boehm-gc or
2992 libjava. If you encounter this problem, set @var{CONFIG_SHELL} to
2993 @file{/bin/ksh} in your environment and run @samp{make bootstrap} again.
2994 Another possibility that sometimes helps is to remove
2995 @file{*-*-solaris*/config.cache}.
3001 @heading @anchor{sparc-sun-*}sparc-sun-*
3002 Sometimes on a Sun 4 you may observe a crash in the program
3003 @code{genflags} or @code{genoutput} while building GCC@. This is said to
3004 be due to a bug in @code{sh}. You can probably get around it by running
3005 @code{genflags} or @code{genoutput} manually and then retrying the
3012 @heading @anchor{sparc-sun-solaris*}sparc-sun-solaris*
3013 On Solaris 2, executables of GCC version 2.0.2 are commonly
3014 available, but they have a bug that shows up when compiling current
3015 versions of GCC: undefined symbol errors occur during assembly if you
3018 The solution is to compile the current version of GCC without
3019 @option{-g}. That makes a working compiler which you can use to recompile
3022 Solaris 2 comes with a number of optional OS packages. Some of these
3023 packages are needed to use GCC fully. If you did not install all
3024 optional packages when installing Solaris, you will need to verify that
3025 the packages that GCC needs are installed.
3027 To check whether an optional package is installed, use
3028 the @code{pkginfo} command. To add an optional package, use the
3029 @code{pkgadd} command. For further details, see the Solaris
3032 For Solaris 2.0 and 2.1, GCC needs six packages: @samp{SUNWarc},
3033 @samp{SUNWbtool}, @samp{SUNWesu}, @samp{SUNWhea}, @samp{SUNWlibm}, and
3036 For Solaris 2.2, GCC needs an additional seventh package: @samp{SUNWsprot}.
3038 On Solaris 2, trying to use the linker and other tools in
3039 @file{/usr/ucb} to install GCC has been observed to cause trouble.
3040 For example, the linker may hang indefinitely. The fix is to remove
3041 @file{/usr/ucb} from your @code{PATH}.
3043 All releases of GNU binutils prior to 2.11.1 have known bugs on this
3044 platform. We recommend the use of GNU binutils 2.11.1 or the vendor
3045 tools (Sun as, Sun ld).
3047 Unfortunately, C++ shared libraries, including libstdc++, won't work
3048 properly if assembled with Sun as: the linker will complain about
3049 relocations in read-only sections, in the definition of virtual
3050 tables. Also, Sun as fails to process long symbols resulting from
3051 mangling template-heavy C++ function names.
3057 @heading @anchor{sparc-sun-solaris2.7}sparc-sun-solaris2.7
3059 Sun patch 107058-01 (1999-01-13) for SPARC Solaris 7 triggers a bug in
3060 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
3061 and later, including all EGCS releases. Sun formerly recommended
3062 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
3063 recommend it only for people who use Sun's compilers.
3065 Here are some workarounds to this problem:
3068 Do not install Sun patch 107058-01 until after Sun releases a
3069 complete patch for bug 4210064. This is the simplest course to take,
3070 unless you must also use Sun's C compiler. Unfortunately 107058-01
3071 is preinstalled on some new Solaris-based hosts, so you may have to
3075 Copy the original, unpatched Solaris 7
3076 @command{/usr/ccs/bin/as} into
3077 @command{/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/2.95.1/as},
3078 adjusting the latter name to fit your local conventions and software
3082 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
3083 both 107058-01 and 106950-03 installed has reported the bug with GCC
3084 and Sun's dynamic linker. This last course of action is riskiest,
3085 for two reasons. First, you must install 106950 on all hosts that
3086 run code generated by GCC; it doesn't suffice to install it only on
3087 the hosts that run GCC itself. Second, Sun says that 106950-03 is
3088 only a partial fix for bug 4210064, but Sun doesn't know whether the
3089 partial fix is adequate for GCC@. Revision -08 or later should fix
3090 the bug, but (as of 1999-10-06) it is still being tested.
3097 <!-- ripped from the same FAQ that I answered -->
3099 @heading @anchor{*-sun-solaris2.8}*-sun-solaris2.8
3101 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3102 newer: @command{g++} will complain that types are missing. These headers assume
3103 that omitting the type means @code{int}; this assumption worked for C89 but
3104 is wrong for C++, and is now wrong for C99 also.
3106 @command{g++} accepts such (illegal) constructs with the option @option{-fpermissive}; it
3107 will assume that any missing type is @code{int} (as defined by C89).
3109 For Solaris 8, this is fixed by revision 24 or later of patch 108652
3110 (for SPARCs) or 108653 (for Intels).
3112 Solaris 8's linker fails to link some libjava programs if
3113 previously-installed GCC java libraries already exist in the configured
3114 prefix. For this reason, libgcj is disabled by default on Solaris 8.
3115 If you use GNU ld, or if you don't have a previously-installed libgcj in
3116 the same prefix, use @option{--enable-libgcj} to build and install the
3123 @heading @anchor{sunv5}Sun V5.0 Compiler Bugs
3125 The Sun V5.0 compilers are known to mis-compile GCC 2.95 and GCC 2.95.1,
3126 which in turn causes GCC to fail its bootstrap comparison test.
3127 GCC 2.95.2 has a workaround.
3134 @heading @anchor{sparc-sun-sunos*}sparc-sun-sunos*
3136 A bug in the SunOS4 linker will cause it to crash when linking
3137 @option{-fPIC} compiled objects (and will therefore not allow you to build
3140 To fix this problem you can either use the most recent version of
3141 binutils or get the latest SunOS4 linker patch (patch ID 100170-10)
3142 from Sun's patch site.
3149 @heading @anchor{sparc-unknown-linux-gnulibc1}sparc-unknown-linux-gnulibc1
3151 It has been reported that you might need
3152 @uref{ftp://ftp.yggdrasil.com/private/hjl,,binutils-2.8.1.0.23}
3153 for this platform, too.
3160 @heading @anchor{sparc64-*-*}sparc64-*-*
3162 GCC version 2.95 is not able to compile code correctly for
3163 @code{sparc64} targets. Users of the Linux kernel, at least,
3164 12~can use the @code{sparc32} program to start up a new shell
3165 invocation with an environment that causes @command{configure} to
3166 recognize (via @samp{uname -a}) the system as @var{sparc-*-*} instead.
3173 @heading @anchor{#*-*-sysv*}*-*-sysv*
3174 On System V release 3, you may get this error message
3178 ld fatal: failed to write symbol name @var{something}
3179 in strings table for file @var{whatever}
3182 This probably indicates that the disk is full or your ULIMIT won't allow
3183 the file to be as large as it needs to be.
3185 This problem can also result because the kernel parameter @code{MAXUMEM}
3186 is too small. If so, you must regenerate the kernel and make the value
3187 much larger. The default value is reported to be 1024; a value of 32768
3188 is said to work. Smaller values may also work.
3190 On System V, if you get an error like this,
3193 /usr/local/lib/bison.simple: In function `yyparse':
3194 /usr/local/lib/bison.simple:625: virtual memory exhausted
3198 that too indicates a problem with disk space, ULIMIT, or @code{MAXUMEM}.
3200 On a System V release 4 system, make sure @file{/usr/bin} precedes
3201 @file{/usr/ucb} in @code{PATH}. The @code{cc} command in
3202 @file{/usr/ucb} uses libraries which have bugs.
3208 @heading @anchor{vax-dec-ultrix}vax-dec-ultrix
3209 Don't try compiling with Vax C (@code{vcc}). It produces incorrect code
3210 in some cases (for example, when @code{alloca} is used).
3212 Meanwhile, compiling @file{cp/parse.c} with pcc does not work because of
3213 an internal table size limitation in that compiler. To avoid this
3214 problem, compile just the GNU C compiler first, and use it to recompile
3215 building all the languages that you want to run.
3221 @heading @anchor{we32k-*-*}we32k-*-*
3222 These computers are also known as the 3b2, 3b5, 3b20 and other similar
3223 names. (However, the 3b1 is actually a 68000.)
3225 Don't use @option{-g} when compiling with the system's compiler. The
3226 system's linker seems to be unable to handle such a large program with
3227 debugging information.
3229 The system's compiler runs out of capacity when compiling @file{stmt.c}
3230 in GCC@. You can work around this by building @file{cpp} in GCC
3231 first, then use that instead of the system's preprocessor with the
3232 system's C compiler to compile @file{stmt.c}. Here is how:
3235 mv /lib/cpp /lib/cpp.att
3237 echo '/lib/cpp.gnu -traditional $@{1+"$@@"@}' > /lib/cpp
3241 The system's compiler produces bad code for some of the GCC
3242 optimization files. So you must build the stage 2 compiler without
3243 optimization. Then build a stage 3 compiler with optimization.
3244 That executable should work. Here are the necessary commands:
3247 make LANGUAGES=c CC=stage1/xgcc CFLAGS="-Bstage1/ -g"
3249 make CC=stage2/xgcc CFLAGS="-Bstage2/ -g -O"
3252 You may need to raise the ULIMIT setting to build a C++ compiler,
3253 as the file @file{cc1plus} is larger than one megabyte.
3259 @heading @anchor{windows}Microsoft Windows (32 bit)
3261 A port of GCC 2.95.x is included with the
3262 @uref{http://www.cygwin.com/,,Cygwin environment}.
3264 Current (as of early 2001) snapshots of GCC will build under Cygwin
3265 without modification.
3271 @heading @anchor{os2}OS/2
3273 GCC does not currently support OS/2. However, Andrew Zabolotny has been
3274 working on a generic OS/2 port with pgcc. The current code code can be found
3275 at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
3277 An older copy of GCC 2.8.1 is included with the EMX tools available at
3278 @uref{ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/,,
3279 ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/}.
3285 @heading @anchor{older}Older systems
3287 GCC contains support files for many older (1980s and early
3288 1990s) Unix variants. For the most part, support for these systems
3289 has not been deliberately removed, but it has not been maintained for
3290 several years and may suffer from bitrot. Support from some systems
3291 has been removed from GCC 3: fx80, ns32-ns-genix, pyramid, tahoe,
3292 gmicro, spur; most of these targets had not been updated since GCC
3295 Support for older systems as targets for cross-compilation is less
3296 problematic than support for them as hosts for GCC; if an enthusiast
3297 wishes to make such a target work again (including resurrecting any
3298 of the targets that never worked with GCC 2, starting from the last
3299 CVS version before they were removed), patches
3300 @uref{../contribute.html,,following the usual requirements}
3301 would be likely to be accepted, since they should not affect the
3302 support for more modern targets.
3304 Support for old systems as hosts for GCC can cause problems if the
3305 workarounds for compiler, library and operating system bugs affect the
3306 cleanliness or maintainability of the rest of GCC@. In some cases, to
3307 bring GCC up on such a system, if still possible with current GCC, may
3308 require first installing an old version of GCC which did work on that
3309 system, and using it to compile a more recent GCC, to avoid bugs in
3310 the vendor compiler. Old releases of GCC 1 and GCC 2 are available in
3311 the old-releases directory on the
3312 @uref{../mirrors.html,,GCC mirror sites}. Header bugs may generally
3313 be avoided using @command{fixincludes}, but bugs or deficiencies in
3314 libraries and the operating system may still cause problems.
3316 For some systems, old versions of GNU binutils may also be useful,
3317 and are available from pub/binutils/old-releases on
3318 @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}.
3320 Some of the information on specific systems above relates to
3321 such older systems, but much of the information
3322 about GCC on such systems (which may no longer be applicable to
3323 current GCC) is to be found in the GCC texinfo manual.
3329 @heading @anchor{elf_targets}all ELF targets (SVR4, Solaris, etc.)
3331 C++ support is significantly better on ELF targets if you use the
3332 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
3333 inlines, vtables and template instantiations will be discarded
3343 @uref{./index.html,,Return to the GCC Installation page}
3347 @c ***************************************************************************
3348 @c Part 6 The End of the Document
3350 @comment node-name, next, previous, up
3351 @node Concept Index, , Specific, Top
3355 @unnumbered Concept Index