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
269 @ref{Specific, host/target specific installation notes}.
272 @uref{specific.html,,host/target specific installation notes}.
280 % @var{srcdir}/configure [@var{options}] [@var{target}]
284 @heading Target specification
287 GCC has code to correctly determine the correct value for @var{target}
288 for nearly all native systems. Therefore, we highly recommend you not
289 provide a configure target when configuring a native compiler.
292 @var{target} must be specified as @option{--target=@var{target}}
293 when configuring a cross compiler; examples of valid targets would be
294 i960-rtems, m68k-coff, sh-elf, etc.
297 Specifying just @var{target} instead of @option{--target=@var{target}}
298 implies that the host defaults to @var{target}.
302 @heading Options specification
304 Use @var{options} to override several configure time options for
305 GCC@. A partial list of supported @var{options}:
308 @item --prefix=@var{dirname}
309 Specify the toplevel installation
310 directory. This is the recommended way to install the tools into a directory
311 other than the default. The toplevel installation directory defaults to
314 We @strong{highly} recommend against @var{dirname} being the same or a
315 subdirectory of @var{objdir} or vice versa.
317 These additional options control where certain parts of the distribution
318 are installed. Normally you should not need to use these options.
321 @item --exec-prefix=@var{dirname}
322 Specify the toplevel installation directory for architecture-dependent
323 files. The default is @file{@var{prefix}}.
325 @item --bindir=@var{dirname}
326 Specify the installation directory for the executables called by users
327 (such as @command{gcc} and @command{g++}). The default is
328 @file{@var{exec-prefix}/bin}.
330 @item --libdir=@var{dirname}
331 Specify the installation directory for object code libraries and
332 internal parts of GCC@. The default is @file{@var{exec-prefix}/lib}.
334 @item --with-slibdir=@var{dirname}
335 Specify the installation directory for the shared libgcc library. The
336 default is @file{@var{libdir}}.
338 @item --infodir=@var{dirname}
339 Specify the installation directory for documentation in info format.
340 The default is @file{@var{prefix}/info}.
342 @item --mandir=@var{dirname}
343 Specify the installation directory for manual pages. The default is
344 @file{@var{prefix}/man}. (Note that the manual pages are only extracts from
345 the full GCC manuals, which are provided in Texinfo format. The
346 @command{g77} manpage is unmaintained and may be out of date; the others
347 are derived by an automatic conversion process from parts of the full
350 @item --with-gxx-include-dir=@var{dirname}
352 the installation directory for G++ header files. The default is
353 @file{@var{prefix}/include/g++-v3}.
357 @item --with-local-prefix=@var{dirname}
359 installation directory for local include files. The default is
360 @file{/usr/local}. Specify this option if you want the compiler to
361 search directory @file{@var{dirname}/include} for locally installed
362 header files @emph{instead} of @file{/usr/local/include}.
364 You should specify @option{--with-local-prefix} @strong{only} if your
365 site has a different convention (not @file{/usr/local}) for where to put
368 The default value for @option{--with-local-prefix} is @file{/usr/local}
369 regardless of the value of @option{--prefix}. Specifying
370 @option{--prefix} has no effect on which directory GCC searches for
371 local header files. This may seem counterintuitive, but actually it is
374 The purpose of @option{--prefix} is to specify where to @emph{install
375 GCC}. The local header files in @file{/usr/local/include}---if you put
376 any in that directory---are not part of GCC@. They are part of other
377 programs---perhaps many others. (GCC installs its own header files in
378 another directory which is based on the @option{--prefix} value.)
380 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
381 The directory you use for @option{--with-local-prefix} @strong{must not}
382 contain any of the system's standard header files. If it did contain
383 them, certain programs would be miscompiled (including GNU Emacs, on
384 certain targets), because this would override and nullify the header
385 file corrections made by the @code{fixincludes} script.
387 Indications are that people who use this option use it based on mistaken
388 ideas of what it is for. People use it as if it specified where to
389 install part of GCC@. Perhaps they make this assumption because
390 installing GCC creates the directory.
392 @item --enable-shared[=@var{package}[,@dots{}]]
393 Build shared versions of libraries, if shared libraries are supported on
394 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
395 are enabled by default on all platforms that support shared libraries,
396 except for @samp{libobjc} which is built as a static library only by
399 If a list of packages is given as an argument, build shared libraries
400 only for the listed packages. For other packages, only static libraries
401 will be built. Package names currently recognized in the GCC tree are
402 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
403 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc} and
404 @samp{libjava}. Note that @samp{libobjc} does not recognize itself by
405 any name, so, if you list package names in @option{--enable-shared},
406 you will only get static Objective-C libraries. @samp{libf2c} and
407 @samp{libiberty} do not support shared libraries at all.
409 Use @option{--disable-shared} to build only static libraries. Note that
410 @option{--disable-shared} does not accept a list of package names as
411 argument, only @option{--enable-shared} does.
413 @item @anchor{with-gnu-as}--with-gnu-as
414 Specify that the compiler should assume that the
415 assembler it finds is the GNU assembler. However, this does not modify
416 the rules to find an assembler and will result in confusion if found
417 assembler is not actually the GNU assembler. (Confusion will also
418 result if the compiler finds the GNU assembler but has not been
419 configured with @option{--with-gnu-as}.) If you have more than one
420 assembler installed on your system, you may want to use this option in
421 connection with @option{--with-as=@var{pathname}}.
423 The systems where it makes a difference whether you use the GNU assembler are
424 @samp{hppa1.0-@var{any}-@var{any}}, @samp{hppa1.1-@var{any}-@var{any}},
425 @samp{i386-@var{any}-sysv}, @samp{i386-@var{any}-isc},
426 @samp{i860-@var{any}-bsd}, @samp{m68k-bull-sysv},
427 @samp{m68k-hp-hpux}, @samp{m68k-sony-bsd},
428 @samp{m68k-altos-sysv}, @samp{m68000-hp-hpux},
429 @samp{m68000-att-sysv}, @samp{@var{any}-lynx-lynxos},
430 and @samp{mips-@var{any}}.
431 On any other system, @option{--with-gnu-as} has no effect.
433 On the systems listed above (except for the HP-PA, for ISC on the
434 386, and for @samp{mips-sgi-irix5.*}), if you use the GNU assembler,
435 you should also use the GNU linker (and specify @option{--with-gnu-ld}).
437 @item --with-as=@var{pathname}
439 compiler should use the assembler pointed to by @var{pathname}, rather
440 than the one found by the standard rules to find an assembler, which
445 @file{@var{exec_prefix}/lib/gcc-lib/@var{target}/@var{version}}
446 directory, where @var{exec_prefix} defaults to @var{prefix} which
447 defaults to @file{/usr/local} unless overridden by the
448 @option{--prefix=@var{pathname}} switch described above. @var{target} is the
449 target system triple, such as @samp{sparc-sun-solaris2.7}, and
450 @var{version} denotes the GCC version, such as 3.0.
452 Check operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
455 Note that these rules do not check for the value of @env{PATH}. You may
456 want to use @option{--with-as} if no assembler is installed in the
457 directories listed above, or if you have multiple assemblers installed
458 and want to choose one that is not found by the above rules.
460 @item @anchor{with-gnu-ld}--with-gnu-ld
461 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
465 @item --with-ld=@var{pathname}
467 @option{--with-as}, but for the linker.
470 Specify that stabs debugging
471 information should be used instead of whatever format the host normally
472 uses. Normally GCC uses the same debug format as the host system.
474 On MIPS based systems and on Alphas, you must specify whether you want
475 GCC to create the normal ECOFF debugging format, or to use BSD-style
476 stabs passed through the ECOFF symbol table. The normal ECOFF debug
477 format cannot fully handle languages other than C@. BSD stabs format can
478 handle other languages, but it only works with the GNU debugger GDB@.
480 Normally, GCC uses the ECOFF debugging format by default; if you
481 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
483 No matter which default you choose when you configure GCC, the user
484 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
485 the debug format for a particular compilation.
487 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
488 @option{--with-gas} is used. It selects use of stabs debugging
489 information embedded in COFF output. This kind of debugging information
490 supports C++ well; ordinary COFF debugging information does not.
492 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
493 selects use of stabs debugging information embedded in ELF output. The
494 C++ compiler currently (2.6.0) does not support the DWARF debugging
495 information normally used on 386 SVR4 platforms; stabs provide a
496 workable alternative. This requires gas and gdb, as the normal SVR4
497 tools can not generate or interpret stabs.
499 @item --disable-multilib
500 Specify that multiple target
501 libraries to support different target variants, calling
502 conventions, etc should not be built. The default is to build a
503 predefined set of them.
505 @item --enable-threads
506 Specify that the target
507 supports threads. This affects the Objective-C compiler and runtime
508 library, and exception handling for other languages like C++ and Java.
509 On some systems, this is the default.
511 In general, the best (and, in many cases, the only known) threading
512 model available will be configured for use. Beware that on some
513 systems, gcc has not been taught what threading models are generally
514 available for the system. In this case, @option{--enable-threads} is an
515 alias for @option{--enable-threads=single}.
517 @item --disable-threads
518 Specify that threading support should be disabled for the system.
519 This is an alias for @option{--enable-threads=single}.
521 @item --enable-threads=@var{lib}
523 @var{lib} is the thread support library. This affects the Objective-C
524 compiler and runtime library, and exception handling for other languages
525 like C++ and Java. The possibilities for @var{lib} are:
533 Generic MACH thread support, known to work on NeXTSTEP@. (Please note
534 that the file needed to support this configuration, @file{gthr-mach.h}, is
535 missing and thus this setting will cause a known bootstrap failure.)
537 This is an alias for @samp{single}.
539 Generic POSIX thread support.
541 Same as @samp{posix} on arm*-*-linux*, *-*-chorusos* and *-*-freebsd*
542 only. A future release of gcc might remove this alias or extend it
545 RTEMS thread support.
547 Disable thread support, should work for all platforms.
549 Sun Solaris 2 thread support.
551 VxWorks thread support.
553 Microsoft Win32 API thread support.
556 @item --with-cpu=@var{cpu}
557 Specify which cpu variant the
558 compiler should generate code for by default. This is currently
559 only supported on the some ports, specifically arm, powerpc, and
560 SPARC@. If configure does not recognize the model name (e.g.@: arm700,
561 603e, or ultrasparc) you provide, please check the configure script
562 for a complete list of supported models.
564 @item --enable-target-optspace
566 libraries should be optimized for code space instead of code speed.
567 This is the default for the m32r platform.
570 Specify that a user visible @command{cpp} program should not be installed.
572 @item --with-cpp-install-dir=@var{dirname}
573 Specify that the user visible @command{cpp} program should be installed
574 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
576 @item --enable-maintainer-mode
578 regenerate the GCC master message catalog @file{gcc.pot} are normally
579 disabled. This is because it can only be rebuilt if the complete source
580 tree is present. If you have changed the sources and want to rebuild the
581 catalog, configuring with @option{--enable-maintainer-mode} will enable
582 this. Note that you need a recent version of the @code{gettext} tools
585 @item --enable-version-specific-runtime-libs
587 that runtime libraries should be installed in the compiler specific
588 subdirectory (@file{@var{libsubdir}}) rather than the usual places. In
589 addition, @samp{libstdc++}'s include files will be installed in
590 @file{@var{libsubdir}/include/g++} unless you overruled it by using
591 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
592 particularly useful if you intend to use several versions of GCC in
593 parallel. This is currently supported by @samp{libf2c} and
594 @samp{libstdc++}, and is the default for @samp{libobjc} which cannot be
595 changed in this case.
597 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
598 Specify that only a particular subset of compilers and
599 their runtime libraries should be built. For a list of valid values for
600 @var{langN} you can issue the following command in the
601 @file{gcc} directory of your GCC source tree:@*
603 grep language= */config-lang.in
605 Currently, you can use any of the following:
606 @code{c}, @code{c++}, @code{f77}, @code{java} and @code{objc}.
607 @code{CHILL} is not currently maintained, and will almost
608 certainly fail to compile.@*
609 If you do not pass this flag, all languages available in the @file{gcc}
610 sub-tree will be configured. Re-defining @code{LANGUAGES} when calling
611 @samp{make bootstrap} @strong{does not} work anymore, as those
612 language sub-directories might not have been configured!
614 @item --disable-libgcj
615 Specify that the run-time libraries
616 used by GCJ should not be built. This is useful in case you intend
617 to use GCJ with some other run-time, or you're going to install it
618 separately, or it just happens not to build on your particular
619 machine. In general, if the Java front end is enabled, the GCJ
620 libraries will be enabled too, unless they're known to not work on
621 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
622 may need to port it; in this case, before modifying the top-level
623 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
624 you may use @option{--enable-libgcj} to override the default.
627 Specify that the compiler should
628 use DWARF 2 debugging information as the default.
630 @item --enable-win32-registry
631 @itemx --enable-win32-registry=@var{key}
632 @itemx --disable-win32-registry
633 The @option{--enable-win32-registry} option enables Windows-hosted GCC
634 to look up installations paths in the registry using the following key:
637 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
640 @var{key} defaults to GCC version number, and can be overridden by the
641 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
642 who use custom installers are encouraged to provide a different key,
643 perhaps one comprised of vendor name and GCC version number, to
644 avoid conflict with existing installations. This feature is enabled
645 by default, and can be disabled by @option{--disable-win32-registry}
646 option. This option has no effect on the other hosts.
649 Specify that the machine does not have a floating point unit. This
650 option only applies to @samp{m68k-sun-sunos@var{n}} and
651 @samp{m68k-isi-bsd}. On any other system, @option{--nfp} has no effect.
653 @item --enable-checking
654 @itemx --enable-checking=@var{list}
655 When you specify this option, the compiler is built to perform checking
656 of tree node types when referencing fields of that node, and some other
657 internal consistency checks. This does not change the generated code,
658 but adds error checking within the compiler. This will slow down the
659 compiler and may only work properly if you are building the compiler
660 with GCC@. This is on by default when building from CVS or snapshots,
661 but off for releases. More control over the checks may be had by
662 specifying @var{list}; the categories of checks available are
663 @samp{misc}, @samp{tree}, @samp{gc}, @samp{rtl} and @samp{gcac}. The
664 default when @var{list} is not specified is @samp{misc,tree,gc}; the
665 checks @samp{rtl} and @samp{gcac} are very expensive.
669 The @option{--enable-nls} option enables Native Language Support (NLS),
670 which lets GCC output diagnostics in languages other than American
671 English. Native Language Support is enabled by default if not doing a
672 canadian cross build. The @option{--disable-nls} option disables NLS@.
674 @item --with-included-gettext
675 If NLS is enabled, the @option{--with-included-gettext} option causes the build
676 procedure to prefer its copy of GNU @command{gettext}.
679 If NLS is enabled, and if the host lacks @code{gettext} but has the
680 inferior @code{catgets} interface, the GCC build procedure normally
681 ignores @code{catgets} and instead uses GCC's copy of the GNU
682 @code{gettext} library. The @option{--with-catgets} option causes the
683 build procedure to use the host's @code{catgets} in this situation.
686 Some options which only apply to building cross compilers:
688 @item --with-headers=@var{dir}
689 Specifies a directory
690 which has target include files.
691 @emph{This options is required} when building a cross
692 compiler, if @file{@var{prefix}/@var{target}/sys-include} doesn't pre-exist.
693 These include files will be copied into the @file{gcc} install directory.
694 Fixincludes will be run on these files to make them compatible with
696 @item --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
697 Specifies a list of directories which contain the target runtime
698 libraries. These libraries will be copied into the @file{gcc} install
701 Specifies that @samp{newlib} is
702 being used as the target C library. This causes @code{__eprintf} to be
703 omitted from @file{libgcc.a} on the assumption that it will be provided by
707 Note that each @option{--enable} option has a corresponding
708 @option{--disable} option and that each @option{--with} option has a
709 corresponding @option{--without} option.
716 @uref{./index.html,,Return to the GCC Installation page}
720 @c ***Building****************************************************************
722 @comment node-name, next, previous, up
723 @node Building, Testing, Configuration, Installing GCC
727 <h1 align="center">Installing GCC: Building</h1>
732 @cindex Installing GCC: Building
734 Now that GCC is configured, you are ready to build the compiler and
737 We @strong{highly} recommend that GCC be built using GNU make;
738 other versions may work, then again they might not.
740 (For example, many broken versions of make will fail if you use the
741 recommended setup where @var{objdir} is different from @var{srcdir}.
742 Other broken versions may recompile parts of the compiler when
743 installing the compiler.)
745 Some commands executed when making the compiler may fail (return a
746 non-zero status) and be ignored by @code{make}. These failures, which
747 are often due to files that were not found, are expected, and can safely
750 It is normal to have compiler warnings when compiling certain files.
751 Unless you are a GCC developer, you can generally ignore these warnings
752 unless they cause compilation to fail.
754 On certain old systems, defining certain environment variables such as
755 @env{CC} can interfere with the functioning of @command{make}.
757 If you encounter seemingly strange errors when trying to build the
758 compiler in a directory other than the source directory, it could be
759 because you have previously configured the compiler in the source
760 directory. Make sure you have done all the necessary preparations.
762 If you build GCC on a BSD system using a directory stored in an old System
763 V file system, problems may occur in running @code{fixincludes} if the
764 System V file system doesn't support symbolic links. These problems
765 result in a failure to fix the declaration of @code{size_t} in
766 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
767 that type mismatches occur, this could be the cause.
769 The solution is not to use such a directory for building GCC@.
771 When building from CVS or snapshots, or if you modify parser sources,
772 you need the Bison parser generator installed. Any version 1.25 or
773 later should work; older versions may also work. If you do not modify
774 parser sources, releases contain the Bison-generated files and you do
775 not need Bison installed to build them.
777 When building from CVS or snapshots, or if you modify Texinfo
778 documentation, you need version 4.0 or later of Texinfo installed if you
779 want Info documentation to be regenerated. Releases contain Info
780 documentation pre-built for the unmodified documentation in the release.
782 @section Building a native compiler
784 For a native build issue the command @samp{make bootstrap}. This
785 will build the entire GCC system, which includes the following steps:
789 Build host tools necessary to build the compiler such as texinfo, bison,
793 Build target tools for use by the compiler such as binutils (bfd,
794 binutils, gas, gprof, ld, and opcodes)
795 if they have been individually linked
796 or moved into the top level GCC source tree before configuring.
799 Perform a 3-stage bootstrap of the compiler.
802 Perform a comparison test of the stage2 and stage3 compilers.
805 Build runtime libraries using the stage3 compiler from the previous step.
809 If you are short on disk space you might consider @samp{make
810 bootstrap-lean} instead. This is identical to @samp{make
811 bootstrap} except that object files from the stage1 and
812 stage2 of the 3-stage bootstrap of the compiler are deleted as
813 soon as they are no longer needed.
816 If you want to save additional space during the bootstrap and in
817 the final installation as well, you can build the compiler binaries
818 without debugging information with @samp{make CFLAGS='-O' LIBCFLAGS='-g
819 -O2' LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap}. This will save
820 roughly 40% of disk space both for the bootstrap and the final installation.
821 (Libraries will still contain debugging information.)
823 If you wish to use non-default GCC flags when compiling the stage2 and
824 stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing
825 @samp{make bootstrap}. Non-default optimization flags are less well
826 tested here than the default of @samp{-g -O2}, but should still work.
827 In a few cases, you may find that you need to specify special flags such
828 as @option{-msoft-float} here to complete the bootstrap; or, if the
829 native compiler miscompiles the stage1 compiler, you may need to work
830 around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the
831 stage1 compiler that were miscompiled, or by using @samp{make
832 bootstrap4} to increase the number of stages of bootstrap.
834 If you used the flag @option{--enable-languages=@dots{}} to restrict
835 the compilers to be built, only those you've actually enabled will be
836 built. This will of course only build those runtime libraries, for
837 which the particular compiler has been built. Please note,
838 that re-defining @env{LANGUAGES} when calling @samp{make bootstrap}
839 @strong{does not} work anymore!
841 If the comparison of stage2 and stage3 fails, this normally indicates
842 that the stage2 compiler has compiled GCC incorrectly, and is therefore
843 a potentially serious bug which you should investigate and report. (On
844 a few systems, meaningful comparison of object files is impossible; they
845 always appear ``different''. If you encounter this problem, you will
846 need to disable comparison in the @file{Makefile}.)
848 @section Building a cross compiler
850 We recommend reading the
851 @uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ}
852 for information about building cross compilers.
854 When building a cross compiler, it is not generally possible to do a
855 3-stage bootstrap of the compiler. This makes for an interesting problem
856 as parts of GCC can only be built with GCC@.
858 To build a cross compiler, we first recommend building and installing a
859 native compiler. You can then use the native GCC compiler to build the
862 Assuming you have already installed a native copy of GCC and configured
863 your cross compiler, issue the command @command{make}, which performs the
868 Build host tools necessary to build the compiler such as texinfo, bison,
872 Build target tools for use by the compiler such as binutils (bfd,
873 binutils, gas, gprof, ld, and opcodes)
874 if they have been individually linked or moved into the top level GCC source
875 tree before configuring.
878 Build the compiler (single stage only).
881 Build runtime libraries using the compiler from the previous step.
884 Note that if an error occurs in any step the make process will exit.
886 @section Building in parallel
888 If you have a multiprocessor system you can use @samp{make bootstrap
889 MAKE="make -j 2" -j 2} or just @samp{make -j 2 bootstrap}
890 for GNU Make 3.79 and above instead of just @samp{make bootstrap}
891 when building GCC@. You can use a bigger number instead of two if
892 you like. In most cases, it won't help to use a number bigger than
893 the number of processors in your machine.
900 @uref{./index.html,,Return to the GCC Installation page}
904 @c ***Testing*****************************************************************
906 @comment node-name, next, previous, up
907 @node Testing, Final install, Building, Installing GCC
911 <h1 align="center">Installing GCC: Testing</h1>
914 @chapter Installing GCC: Testing
917 @cindex Installing GCC: Testing
920 Before you install GCC, you might wish to run the testsuite. This
921 step is optional and may require you to download additional software.
923 First, you must have @uref{download.html,,downloaded the testsuites}.
924 The full distribution contains testsuites; only if you downloaded the
925 ``core'' compiler plus any front ends, you do not have the testsuites.
927 Second, you must have a @uref{http://www.gnu.org/software/dejagnu/,,current version of DejaGnu} installed;
928 dejagnu 1.3 is not sufficient.
930 Now you may need specific preparations:
935 The following environment variables may need to be set appropriately, as in
936 the following example (which assumes that DejaGnu has been installed
937 under @file{/usr/local}):
940 TCL_LIBRARY = /usr/local/share/tcl8.0
941 DEJAGNULIBS = /usr/local/share/dejagnu
944 On systems such as Cygwin, these paths are required to be actual
945 paths, not mounts or links; presumably this is due to some lack of
946 portability in the DejaGnu code.
948 If the directories where @command{runtest} and @command{expect} were
949 installed are in the @env{PATH}, it should not be necessary to set these
950 environment variables.
954 Finally, you can run the testsuite (which may take a long time):
956 cd @var{objdir}; make -k check
959 The testing process will try to test as many components in the GCC
960 distribution as possible, including the C, C++, Objective-C and Fortran
961 compilers as well as the C++ and Java runtime libraries.
963 @section How can I run the test suite on selected tests?
965 As a first possibility to cut down the number of tests that are run it is
966 possible to use @samp{make check-gcc} or @samp{make check-g++}
967 in the @file{gcc} subdirectory of the object directory. To further cut down the
968 tests the following is possible:
971 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
974 This will run all @command{gcc} execute tests in the testsuite.
977 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
980 This will run the @command{g++} ``old-deja'' tests in the testsuite where the filename
981 matches @samp{9805*}.
983 The @file{*.exp} files are located in the testsuite directories of the GCC
984 source, the most important ones being @file{compile.exp},
985 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
986 To get a list of the possible @file{*.exp} files, pipe the
987 output of @samp{make check} into a file and look at the
988 @samp{Running @dots{} .exp} lines.
990 @section How to interpret test results
992 After the testsuite has run you'll find various @file{*.sum} and @file{*.log}
993 files in the testsuite subdirectories. The @file{*.log} files contain a
994 detailed log of the compiler invocations and the corresponding
995 results, the @file{*.sum} files summarize the results. These summaries list
996 all the tests that have been run with a corresponding status code:
1000 PASS: the test passed as expected
1002 XPASS: the test unexpectedly passed
1004 FAIL: the test unexpectedly failed
1006 XFAIL: the test failed as expected
1008 UNSUPPORTED: the test is not supported on this platform
1010 ERROR: the testsuite detected an error
1012 WARNING: the testsuite detected a possible problem
1015 It is normal for some tests to report unexpected failures. At the
1016 current time our testing harness does not allow fine grained control
1017 over whether or not a test is expected to fail. We expect to fix this
1018 problem in future releases.
1021 @section Submitting test results
1023 If you want to report the results to the GCC project, use the
1024 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
1027 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
1028 -m gcc-testresults@@gcc.gnu.org |sh
1031 This script uses the @command{Mail} program to send the results, so
1032 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
1033 prepended to the testsuite summary and should contain any special
1034 remarks you have on your results or your build environment. Please
1035 do not edit the testsuite result block or the subject line, as these
1036 messages are automatically parsed and presented at the
1037 @uref{http://gcc.gnu.org/testresults/,,GCC testresults} web
1038 page. Here you can also gather information on how specific tests
1039 behave on different platforms and compare them with your results. A
1040 few failing testcases are possible even on released versions and you
1041 should look here first if you think your results are unreasonable.
1045 @c ***Final install***********************************************************
1047 @comment node-name, next, previous, up
1048 @node Final install, , Testing, Installing GCC
1050 @ifset finalinstallhtml
1052 <h1 align="center">Installing GCC: Final installation</h1>
1055 @chapter Installing GCC: Final installation
1058 Now that GCC has been built (and optionally tested), you can install it with
1060 cd @var{objdir}; make install
1063 That step completes the installation of GCC; user level binaries can
1064 be found in @file{@var{prefix}/bin} where @var{prefix} is the value you
1065 specified with the @option{--prefix} to configure (or @file{/usr/local}
1066 by default). (If you specified @option{--bindir}, that directory will
1067 be used instead; otherwise, if you specified @option{--exec-prefix},
1068 @file{@var{exec-prefix}/bin} will be used.) Headers for the C++ and
1069 Java libraries are installed in @file{@var{prefix}/include}; libraries
1070 in @file{@var{libdir}} (normally @file{@var{prefix}/lib}); internal
1071 parts of the compiler in @file{@var{libdir}/gcc-lib}; documentation in
1072 info format in @file{@var{infodir}} (normally @file{@var{prefix}/info}).
1074 If you don't mind, please quickly review the
1075 @uref{http://gcc.gnu.org/gcc-3.0/buildstat.html,,build status page}.
1076 If your system is not listed, send a note to
1077 @email{gcc@@gcc.gnu.org} indicating
1078 that you successfully built and installed GCC.
1080 Include the output from running @file{@var{srcdir}/config.guess}. (Do
1081 not send us the @file{config.guess} file itself, just the one-line output from
1084 If you find a bug, please report it following our
1085 @uref{../bugs.html,,bug reporting guidelines}.
1087 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
1088 dvi}. You will need to have @command{texi2dvi} (version at least 4.0)
1089 and @TeX{} installed. This creates a number of @file{.dvi} files in
1090 subdirectories of @file{@var{objdir}}; these may be converted for
1091 printing with programs such as @command{dvips}. You can also
1092 @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the
1093 Free Software Foundation}, though such manuals may not be for the most
1094 recent version of GCC@.
1101 @uref{./index.html,,Return to the GCC Installation page}
1105 @c ***Binaries****************************************************************
1107 @comment node-name, next, previous, up
1108 @node Binaries, Specific, Installing GCC, Top
1112 <h1 align="center">Installing GCC: Binaries</h1>
1115 @chapter Installing GCC: Binaries
1118 @cindex Installing GCC: Binaries
1120 We are often asked about pre-compiled versions of GCC@. While we cannot
1121 provide these for all platforms, below you'll find links to binaries for
1122 various platforms where creating them by yourself is not easy due to various
1125 Please note that we did not create these binaries, nor do we
1126 support them. If you have any problems installing them, please
1127 contact their makers.
1134 @uref{http://freeware.bull.net,,Bull's Freeware and Shareware Archive for AIX};
1137 @uref{http://aixpdslib.seas.ucla.edu,,UCLA Software Library for AIX};
1141 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP};
1144 @uref{http://hpux.cae.wisc.edu/,,HP-UX Porting Center};
1147 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
1148 OpenServer/Unixware};
1151 Solaris (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware};
1154 SGI---@uref{http://freeware.sgi.com/,,SGI Freeware};
1157 Windows 95, 98, and NT:
1160 The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project;
1162 @uref{http://www.xraylith.wisc.edu/~khan/software/gnu-win32/,,GNU Win32}
1163 related projects by Mumit Khan.
1167 @uref{ftp://ftp.thewrittenword.com/packages/free/by-name/gcc-2.95.2/,,The
1168 Written Word} offers binaries for Solaris 2.5.1, 2.6, 2.7/SPARC, 2.7/Intel,
1169 IRIX 6.2, 6.5, Digital UNIX 4.0D, HP-UX 10.20, and HP-UX 11.00.
1172 Hitachi H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
1173 Development Tools for the Hitachi H8/300[HS] Series}
1177 In addition to those specific offerings, you can get a binary
1178 distribution CD-ROM from the
1179 @uref{http://www.fsf.org/order/order.html,,Free Software Foundation}.
1180 It contains binaries for a number of platforms, and
1181 includes not only GCC, but other stuff as well. The current CD does
1182 not contain the latest version of GCC, but it should allow
1183 bootstrapping the compiler. An updated version of that disk is in the
1191 @uref{./index.html,,Return to the GCC Installation page}
1195 @c ***Specific****************************************************************
1197 @comment node-name, next, previous, up
1198 @node Specific, Concept Index, Binaries, Top
1202 <h1 align="center">Host/target specific installation notes for GCC</h1>
1205 @chapter Host/target specific installation notes for GCC
1208 @cindex Specific installation notes
1209 @cindex Target specific installation
1210 @cindex Host specific installation
1211 @cindex Target specific installation notes
1213 Please read this document carefully @emph{before} installing the
1214 GNU Compiler Collection on your machine.
1219 @uref{#1750a-*-*,,1750a-*-*}
1223 @uref{#a29k-*-bsd,,a29k-*-bsd}
1225 @uref{#alpha*-*-*,,alpha*-*-*}
1227 @uref{#alpha*-dec-osf*,,alpha*-dec-osf*}
1229 @uref{#arc-*-elf,,arc-*-elf}
1231 @uref{#arm-*-aout,,arm-*-aout}
1233 @uref{#arm-*-elf,,arm-*-elf}
1235 @uref{#arm*-*-linux-gnu,,arm*-*-linux-gnu}
1237 @uref{#arm-*-riscix,,arm-*-riscix}
1245 @uref{#dsp16xx,,dsp16xx}
1247 @uref{#elxsi-elxsi-bsd,,elxsi-elxsi-bsd}
1249 @uref{#*-*-freebsd*,,*-*-freebsd*}
1251 @uref{#h8300-hms,,h8300-hms}
1253 @uref{#hppa*-hp-hpux*,,hppa*-hp-hpux*}
1255 @uref{#hppa*-hp-hpux9,,hppa*-hp-hpux9}
1257 @uref{#hppa*-hp-hpux10,,hppa*-hp-hpux10}
1259 @uref{#hppa*-hp-hpux11,,hppa*-hp-hpux11}
1261 @uref{#i370-*-*,,i370-*-*}
1263 @uref{#*-*-linux-gnu,,*-*-linux-gnu}
1265 @uref{#ix86-*-linux*oldld,,i?86-*-linux*oldld}
1267 @uref{#ix86-*-linux*aout,,i?86-*-linux*aout}
1269 @uref{#ix86-*-linux*,,i?86-*-linux*}
1271 @uref{#ix86-*-sco,,i?86-*-sco}
1273 @uref{#ix86-*-sco3.2v4,,i?86-*-sco3.2v4}
1275 @uref{#ix86-*-sco3.2v5*,,i?86-*-sco3.2v5*}
1277 @uref{#ix86-*-udk,,i?86-*-udk}
1279 @uref{#ix86-*-isc,,i?86-*-isc}
1281 @uref{#ix86-*-esix,,i?86-*-esix}
1283 @uref{#ix86-ibm-aix,,i?86-ibm-aix}
1285 @uref{#ix86-sequent-bsd,,i?86-sequent-bsd}
1287 @uref{#ix86-sequent-ptx1*,,i?86-sequent-ptx1*, i?86-sequent-ptx2*}
1289 @uref{#ix86-*-sysv3*,,i?86-*-sysv3*}
1291 @uref{#i860-intel-osf*,,i860-intel-osf*}
1293 @uref{#*-lynx-lynxos,,*-lynx-lynxos}
1295 @uref{#*-ibm-aix*,,*-ibm-aix*}
1297 @uref{#m32r-*-elf,,m32r-*-elf}
1299 @uref{#m68000-hp-bsd,,m68000-hp-bsd}
1301 @uref{#m6811-elf,,m6811-elf}
1303 @uref{#m6812-elf,,m6812-elf}
1305 @uref{#m68k-altos,,m68k-altos}
1307 @uref{#m68k-apple-aux,,m68k-apple-aux}
1309 @uref{#m68k-att-sysv,,m68k-att-sysv}
1311 @uref{#m68k-bull-sysv,,m68k-bull-sysv}
1313 @uref{#m68k-crds-unox,,m68k-crds-unox}
1315 @uref{#m68k-hp-hpux,,m68k-hp-hpux}
1317 @uref{#m68k-*-nextstep*,,m68k-*-nextstep*}
1319 @uref{#m68k-ncr-*,,m68k-ncr-*}
1321 @uref{#m68k-sun,,m68k-sun}
1323 @uref{#m68k-sun-sunos4.1.1,,m68k-sun-sunos4.1.1}
1325 @uref{#m88k-*-svr3,,m88k-*-svr3}
1327 @uref{#m88k-*-dgux,,m88k-*-dgux}
1329 @uref{#m88k-tektronix-sysv3,,m88k-tektronix-sysv3}
1331 @uref{#mips-*-*,,mips-*-*}
1333 @uref{#mips-dec-*,,mips-dec-*}
1335 @uref{#mips-mips-bsd,,mips-mips-bsd}
1337 @uref{#mips-mips-riscos*,,mips-mips-riscos*}
1339 @uref{#mips-sgi-irix4,,mips-sgi-irix4}
1341 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
1343 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
1345 @uref{#mips-sony-sysv,,mips-sony-sysv}
1347 @uref{#ns32k-encore,,ns32k-encore}
1349 @uref{#ns32k-*-genix,,ns32k-*-genix}
1351 @uref{#ns32k-sequent,,ns32k-sequent}
1353 @uref{#ns32k-utek,,ns32k-utek}
1355 @uref{#powerpc*-*-*,,powerpc*-*-*, powerpc-*-sysv4}
1357 @uref{#powerpc-*-darwin*,,powerpc-*-darwin*}
1359 @uref{#powerpc-*-elf,,powerpc-*-elf, powerpc-*-sysv4}
1361 @uref{#powerpc-*-linux-gnu*,,powerpc-*-linux-gnu*}
1363 @uref{#powerpc-*-netbsd*,,powerpc-*-netbsd*}
1365 @uref{#powerpc-*-eabiaix,,powerpc-*-eabiaix}
1367 @uref{#powerpc-*-eabisim,,powerpc-*-eabisim}
1369 @uref{#powerpc-*-eabi,,powerpc-*-eabi}
1371 @uref{#powerpcle-*-elf,,powerpcle-*-elf, powerpcle-*-sysv4}
1373 @uref{#powerpcle-*-eabisim,,powerpcle-*-eabisim}
1375 @uref{#powerpcle-*-eabi,,powerpcle-*-eabi}
1377 @uref{#powerpcle-*-winnt,,powerpcle-*-winnt, powerpcle-*-pe}
1379 @uref{#romp-*-aos,,romp-*-aos, romp-*-mach}
1381 @uref{#s390-*-linux*}
1383 @uref{#s390x-*-linux*}
1385 @uref{#*-*-solaris*,,*-*-solaris*}
1387 @uref{#sparc-sun-solaris*,,sparc-sun-solaris*}
1389 @uref{#sparc-sun-solaris2.7,,sparc-sun-solaris2.7}
1391 @uref{#*-sun-solaris2.8,,*-sun-solaris2.8}
1393 @uref{#sparc-sun-sunos*,,sparc-sun-sunos*}
1395 @uref{#sparc-unknown-linux-gnulibc1,,sparc-unknown-linux-gnulibc1}
1397 @uref{#sparc64-*-*,,sparc64-*-*}
1399 @uref{#*-*-sysv*,,*-*-sysv*}
1401 @uref{#vax-dec-ultrix,,vax-dec-ultrix}
1403 @uref{#we32k-*-*,,we32k-*-*}
1405 @uref{#windows,,Microsoft Windows}
1409 @uref{#older,,Older systems}
1414 @uref{#elf_targets,,all ELF targets} (SVR4, Solaris, etc.)
1420 <!-- -------- host/target specific issues start here ---------------- -->
1423 @heading @anchor{1750a-*-*}1750a-*-*
1424 MIL-STD-1750A processors.
1426 The MIL-STD-1750A cross configuration produces output for
1427 @code{as1750}, an assembler/linker available under the GNU General Public
1428 License for the 1750A@. @code{as1750} can be obtained at
1429 @uref{ftp://ftp.fta-berlin.de/pub/crossgcc/1750gals/}.
1430 A similarly licensed simulator for
1431 the 1750A is available from same address.
1433 You should ignore a fatal error during the building of @samp{libgcc}
1434 (@samp{libgcc} is not yet implemented for the 1750A@.)
1436 The @code{as1750} assembler requires the file @file{ms1750.inc}, which is
1437 found in the directory @file{gcc/config/1750a}.
1439 GCC produced the same sections as the Fairchild F9450 C Compiler,
1444 The program code section.
1447 The read/write (RAM) data section.
1450 The read-only (ROM) constants section.
1453 Initialization section (code to copy KREL to SREL)@.
1456 The smallest addressable unit is 16 bits (@code{BITS_PER_UNIT} is 16). This
1457 means that type @code{char} is represented with a 16-bit word per character.
1458 The 1750A's ``Load/Store Upper/Lower Byte'' instructions are not used by
1465 @heading @anchor{a29k}a29k
1466 AMD Am29k-family processors. These are normally used in embedded
1467 applications. There are no standard Unix configurations.
1469 corresponds to AMD's standard calling sequence and binary interface
1470 and is compatible with other 29k tools.
1472 You may need to make a variant of the file @file{a29k.h} for your
1473 particular configuration.
1479 @heading @anchor{a29k-*-bsd}a29k-*-bsd
1480 AMD Am29050 used in a system running a variant of BSD Unix.
1486 @heading @anchor{alpha*-*-*}alpha*-*-*
1488 This section contains general configuration information for all
1489 alpha-based platforms using ELF (in particular, ignore this section for
1490 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
1491 section, please read all other sections that match your target.
1493 We require binutils 2.11.2 or newer.
1494 Previous binutils releases had a number of problems with DWARF 2
1495 debugging information, not the least of which is incorrect linking of
1502 @heading @anchor{alpha*-dec-osf*}alpha*-dec-osf*
1503 Systems using processors that implement the DEC Alpha architecture and
1504 are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
1505 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
1507 In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
1508 currently (2001-06-13) work with @command{mips-tfile}. As a workaround,
1509 we need to use the old assembler, invoked via the barely documented
1510 @option{-oldas} option. To bootstrap GCC, you either need to use the
1514 % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
1517 or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
1520 % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
1523 As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld}
1524 are supported on Tru64 UNIX, so you must not configure GCC with
1525 @option{--with-gnu-as} or @option{--with-gnu-ld}.
1527 The @option{--enable-threads} options isn't supported yet. A patch is
1528 in preparation for a future release. The Java runtime library has been
1529 reported to work on Tru64 UNIX V4.0F, V5.0, and V5.1, so you may try
1530 @option{--enable-libgcj} and report your results.
1532 GCC writes a @samp{.verstamp} directive to the assembler output file
1533 unless it is built as a cross-compiler. It gets the version to use from
1534 the system header file @file{/usr/include/stamp.h}. If you install a
1535 new version of DEC Unix, you should rebuild GCC to pick up the new version
1538 Note that since the Alpha is a 64-bit architecture, cross-compilers from
1539 32-bit machines will not generate code as efficient as that generated
1540 when the compiler is running on a 64-bit machine because many
1541 optimizations that depend on being able to represent a word on the
1542 target in an integral value on the host cannot be performed. Building
1543 cross-compilers on the Alpha for 32-bit machines has only been tested in
1544 a few cases and may not work properly.
1546 @code{make compare} may fail on old versions of DEC Unix unless you add
1547 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
1548 assembler input file is stored in the object file, and that makes
1549 comparison fail if it differs between the @code{stage1} and
1550 @code{stage2} compilations. The option @option{-save-temps} forces a
1551 fixed name to be used for the assembler input file, instead of a
1552 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
1553 unless the comparisons fail without that option. If you add
1554 @option{-save-temps}, you will have to manually delete the @samp{.i} and
1555 @samp{.s} files after each series of compilations.
1557 GCC now supports both the native (ECOFF) debugging format used by DBX
1558 and GDB and an encapsulated STABS format for use only with GDB@. See the
1559 discussion of the @option{--with-stabs} option of @file{configure} above
1560 for more information on these formats and how to select them.
1562 There is a bug in DEC's assembler that produces incorrect line numbers
1563 for ECOFF format when the @samp{.align} directive is used. To work
1564 around this problem, GCC will not emit such alignment directives
1565 while writing ECOFF format debugging information even if optimization is
1566 being performed. Unfortunately, this has the very undesirable
1567 side-effect that code addresses when @option{-O} is specified are
1568 different depending on whether or not @option{-g} is also specified.
1570 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
1571 DBX@. DEC is now aware of this problem with the assembler and hopes to
1572 provide a fix shortly.
1578 @heading @anchor{arc-*-elf}arc-*-elf
1579 Argonaut ARC processor.
1580 This configuration is intended for embedded systems.
1586 @heading @anchor{arm-*-aout}arm-*-aout
1587 Advanced RISC Machines ARM-family processors. These are often used in
1588 embedded applications. There are no standard Unix configurations.
1589 This configuration corresponds to the basic instruction sequences and will
1590 produce @file{a.out} format object modules.
1592 You may need to make a variant of the file @file{arm.h} for your particular
1599 @heading @anchor{arm-*-elf}arm-*-elf
1600 This configuration is intended for embedded systems.
1606 @heading @anchor{arm*-*-linux-gnu}arm*-*-linux-gnu
1608 We require GNU binutils 2.10 or newer.
1614 @heading @anchor{arm-*-riscix}arm-*-riscix
1615 The ARM2 or ARM3 processor running RISC iX, Acorn's port of BSD Unix.
1616 If you are running a version of RISC iX prior to 1.2 then you must
1617 specify the version number during configuration. Note that the
1618 assembler shipped with RISC iX does not support stabs debugging
1619 information; a new version of the assembler, with stabs support
1620 included, is now available from Acorn and via ftp
1621 @uref{ftp://ftp.acorn.com/pub/riscix/as+xterm.tar.Z}. To enable stabs
1622 debugging, pass @option{--with-gnu-as} to configure.
1624 You will need to install GNU @command{sed} before you can run configure.
1630 @heading @anchor{avr}avr
1632 ATMEL AVR-family micro controllers. These are used in embedded
1633 applications. There are no standard Unix configurations. @xref{AVR
1634 Options,, AVR Options, gcc, Using and Porting the GNU Compiler
1635 Collection (GCC)}, for the list of supported MCU types.
1637 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
1639 Further installation notes and other useful information about AVR tools
1640 can also be obtained from:
1644 @uref{http://home.overta.ru/users/denisc,,http://home.overta.ru/users/denisc}
1646 @uref{http://www.itnet.pl/amelektr/avr,,http://www.itnet.pl/amelektr/avr}
1649 We @emph{strongly} recommend using binutils 2.11 or newer.
1651 The following error:
1653 Error: register required
1656 indicates that you should upgrade to a newer version of the binutils.
1662 @heading @anchor{c4x}c4x
1664 Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal
1665 Processors. These are used in embedded applications. There are no
1666 standard Unix configurations. @xref{C4x Options,, C4x Options, gcc,
1667 Using and Porting the GNU Compiler Collection (GCC)}, for the list of
1668 supported MCU types.
1670 GCC can be configured as a cross compiler for both the C3x and C4x
1671 architectures on the same system. Use @samp{configure --target=c4x
1672 --enable-languages="c,c++"} to configure.
1675 Further installation notes and other useful information about C4x tools
1676 can also be obtained from:
1680 @uref{http://www.elec.canterbury.ac.nz/c4x,,http://www.elec.canterbury.ac.nz/c4x}
1687 @heading @anchor{dos}DOS
1689 Please have a look at our @uref{binaries.html,,binaries page}.
1691 You cannot install GCC by itself on MSDOS; it will not compile under
1692 any MSDOS compiler except itself. You need to get the complete
1693 compilation package DJGPP, which includes binaries as well as sources,
1694 and includes all the necessary compilation tools and libraries.
1700 @heading @anchor{dsp16xx}dsp16xx
1701 A port to the AT&T DSP1610 family of processors.
1707 @heading @anchor{*-*-freebsd*}*-*-freebsd*
1709 The version of binutils installed in @file{/usr/bin} is known to work unless
1710 otherwise specified in any per-architecture notes. However, binutils
1711 2.11 is known to improve overall testsuite results.
1713 For FreeBSD 1, FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
1714 configuration support and files as shipped with GCC 2.95 are still in
1715 place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
1716 it is unknown which version of binutils was used (it is assumed that it
1717 was the system copy in @file{/usr/bin}) and C++ EH failures were noted.
1719 For FreeBSD using the ELF file format: DWARF 2 debugging is now the
1720 default for all CPU architectures. It had been the default on
1721 FreeBSD/alpha since its inception. You may use @option{-gstabs} instead
1722 of @option{-g}, if you really want the old debugging format. There are
1723 no known issues with mixing object files and libraries with different
1724 debugging formats. Otherwise, this release of GCC should now match more
1725 of the configuration used in the stock FreeBSD configuration of GCC. In
1726 particular, @option{--enable-threads} is now configured by default.
1727 However, as a general user, do not attempt to replace the system
1728 compiler with this release. Known to bootstrap and check with good
1729 results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3 and 5-CURRENT@.
1731 At this time, @option{--enable-threads} is not compatible with
1732 @option{--enable-libgcj} on FreeBSD@.
1738 @heading @anchor{elxsi-elxsi-bsd}elxsi-elxsi-bsd
1739 The Elxsi's C compiler has known limitations that prevent it from
1740 compiling GCC@. Please contact @email{mrs@@wrs.com} for more details.
1746 @heading @anchor{h8300-hms}h8300-hms
1747 Hitachi H8/300 series of processors.
1749 Please have a look at our @uref{binaries.html,,binaries page}.
1751 The calling convention and structure layout has changed in release 2.6.
1752 All code must be recompiled. The calling convention now passes the
1753 first three arguments in function calls in registers. Structures are no
1754 longer a multiple of 2 bytes.
1760 @heading @anchor{hppa*-hp-hpux*}hppa*-hp-hpux*
1762 We @emph{highly} recommend using gas/binutils 2.8 or newer on all hppa
1763 platforms; you may encounter a variety of problems when using the HP
1766 Specifically, @option{-g} does not work on HP-UX (since that system
1767 uses a peculiar debugging format which GCC does not know about), unless you
1768 use GAS and GDB and configure GCC with the
1769 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
1770 @option{--with-as=@dots{}} options.
1772 If you wish to use pa-risc 2.0 architecture support, you must use either
1773 the HP assembler, gas/binutils 2.11 or a recent
1774 @uref{ftp://sources.redhat.com/pub/binutils/snapshots,,snapshot of gas}.
1776 More specific information to @samp{hppa*-hp-hpux*} targets follows.
1782 @heading @anchor{hppa*-hp-hpux9}hppa*-hp-hpux9
1784 The HP assembler has major problems on this platform. We've tried to work
1785 around the worst of the problems. However, those workarounds may be causing
1786 linker crashes in some circumstances; the workarounds also probably prevent
1787 shared libraries from working. Use the GNU assembler to avoid these problems.
1790 The configuration scripts for GCC will also trigger a bug in the hpux9
1791 shell. To avoid this problem set @env{CONFIG_SHELL} to @file{/bin/ksh}
1792 and @env{SHELL} to @file{/bin/ksh} in your environment.
1799 @heading @anchor{hppa*-hp-hpux10}hppa*-hp-hpux10
1801 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
1802 @code{PHCO_19798} from HP@. HP has two sites which provide patches free of
1808 <a href="http://us-support.external.hp.com">US, Canada, Asia-Pacific, and
1812 @uref{http://us-support.external.hp.com,,}US, Canada, Asia-Pacific, and
1816 @uref{http://europe-support.external.hp.com,,Europe}
1819 The HP assembler on these systems is much better than the hpux9 assembler,
1820 but still has some problems. Most notably the assembler inserts timestamps
1821 into each object file it creates, causing the 3-stage comparison test to fail
1822 during a @samp{make bootstrap}. You should be able to continue by
1823 saying @samp{make all} after getting the failure from @samp{make
1831 @heading @anchor{hppa*-hp-hpux11}hppa*-hp-hpux11
1833 GCC 3.0 supports HP-UX 11. You must use GNU binutils 2.11 or above on
1840 @heading @anchor{i370-*-*}i370-*-*
1841 This port is very preliminary and has many known bugs. We hope to
1842 have a higher-quality port for this machine soon.
1848 @heading @anchor{*-*-linux-gnu}*-*-linux-gnu
1850 If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install
1851 out-of-the-box. You'll get compile errors while building @samp{libstdc++}.
1852 The patch @uref{glibc-2.2.patch,,glibc-2.2.patch}, that is to be
1853 applied in the GCC source tree, fixes the compatibility problems.
1863 Currently Glibc 2.2.3 (and older releases) and GCC 3.0 are out of sync
1864 since the latest exception handling changes for GCC@. Compiling glibc
1865 with GCC 3.0 will give a binary incompatible glibc and therefore cause
1866 lots of problems and might make your system completly unusable. This
1867 will definitly need fixes in glibc but might also need fixes in GCC@. We
1868 strongly advise to wait for glibc 2.2.4 and to read the release notes of
1869 glibc 2.2.4 whether patches for GCC 3.0 are needed. You can use glibc
1870 2.2.3 with GCC 3.0, just do not try to recompile it.
1876 @heading @anchor{ix86-*-linux*oldld}i?86-*-linux*oldld
1877 Use this configuration to generate @file{a.out} binaries on Linux-based
1878 GNU systems if you do not have gas/binutils version 2.5.2 or later
1879 installed. This is an obsolete configuration.
1885 @heading @anchor{ix86-*-linux*aout}i?86-*-linux*aout
1886 Use this configuration to generate @file{a.out} binaries on Linux-based
1887 GNU systems. This configuration is being superseded. You must use
1888 gas/binutils version 2.5.2 or later.
1894 @heading @anchor{ix86-*-linux*}i?86-*-linux*
1896 You will need binutils 2.9.1.0.15 or newer for exception handling to work.
1898 If you receive Signal 11 errors when building on GNU/Linux, then it is
1899 possible you have a hardware problem. Further information on this can be
1900 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
1906 @heading @anchor{ix86-*-sco}i?86-*-sco
1907 Compilation with RCC is recommended. Also, it may be a good idea to
1908 link with GNU malloc instead of the malloc that comes with the system.
1914 @heading @anchor{ix86-*-sco3.2v4}i?86-*-sco3.2v4
1915 Use this configuration for SCO release 3.2 version 4.
1921 @heading @anchor{ix86-*-sco3.2v5*}i?86-*-sco3.2v5*
1922 Use this for the SCO OpenServer Release 5 family of operating systems.
1924 Unlike earlier versions of GCC, the ability to generate COFF with this
1925 target is no longer provided.
1927 Earlier versions of GCC emitted DWARF 1 when generating ELF to allow
1928 the system debugger to be used. That support was too burdensome to
1929 maintain. GCC now emits only DWARF 2 for this target. This means you
1930 may use either the UDK debugger or GDB to debug programs built by this
1933 Use of the @option{-march=pentiumpro} flag can result in
1934 unrecognized opcodes when using the native assembler on OS versions before
1935 5.0.6. (Support for P6 opcodes was added to the native ELF assembler in
1936 that version.) While it's rather rare to see these emitted by GCC yet,
1937 errors of the basic form:
1940 /usr/tmp/ccaNlqBc.s:22:unknown instruction: fcomip
1941 /usr/tmp/ccaNlqBc.s:50:unknown instruction: fucomip
1944 are symptoms of this problem. You may work around this by not
1945 building affected files with that flag, by using the GNU assembler, or
1946 by using the assembler provided with the current version of the OS@.
1947 Users of GNU assembler should see the note below for hazards on doing
1950 The native SCO assembler that is provided with the OS at no
1951 charge is normally required. If, however, you must be able to use
1952 the GNU assembler (perhaps you're compiling code with asms that
1953 require GAS syntax) you may configure this package using the flags
1954 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You must
1955 use a recent version of GNU binutils; versions past 2.9.1 seem to work
1958 In general, the @option{--with-gnu-as} option isn't as well tested
1959 as the native assembler.
1961 Look in @file{gcc/config/i386/sco5.h} (search for ``messy'') for
1962 additional OpenServer-specific flags.
1964 Systems based on OpenServer before 5.0.4 (@samp{uname -X}
1965 will tell you what you're running) require TLS597 from
1966 @uref{ftp://ftp.sco.com/TLS/,,ftp://ftp.sco.com/TLS/}
1967 for C++ constructors and destructors to work right.
1969 The system linker in (at least) 5.0.4 and 5.0.5 will sometimes
1970 do the wrong thing for a construct that GCC will emit for PIC
1971 code. This can be seen as execution testsuite failures when using
1972 @option{-fPIC} on @file{921215-1.c}, @file{931002-1.c}, @file{nestfunc-1.c}, and @file{gcov-1.c}.
1973 For 5.0.5, an updated linker that will cure this problem is
1974 available. You must install both
1975 @uref{ftp://ftp.sco.com/Supplements/rs505a/,,ftp://ftp.sco.com/Supplements/rs505a/}
1976 and @uref{ftp://ftp.sco.com/SLS/,,OSS499A}.
1978 The dynamic linker in OpenServer 5.0.5 (earlier versions may show
1979 the same problem) aborts on certain G77-compiled programs. It's particularly
1980 likely to be triggered by building Fortran code with the @option{-fPIC} flag.
1981 Although it's conceivable that the error could be triggered by other
1982 code, only G77-compiled code has been observed to cause this abort.
1983 If you are getting core dumps immediately upon execution of your
1984 G77 program---and especially if it's compiled with @option{-fPIC}---try applying
1985 @uref{sco_osr5_g77.patch,,@file{sco_osr5_g77.patch}} to your @samp{libf2c} and
1987 Affected faults, when analyzed in a debugger, will show a stack
1988 backtrace with a fault occurring in @code{rtld()} and the program
1989 running as @file{/usr/lib/ld.so.1}. This problem has been reported to SCO
1990 engineering and will hopefully be addressed in later releases.
1997 @heading @anchor{ix86-*-udk}i?86-*-udk
1999 This target emulates the SCO Universal Development Kit and requires that
2000 package be installed. (If it is installed, you will have a
2001 @file{/udk/usr/ccs/bin/cc} file present.) It's very much like the
2002 @samp{i?86-*-unixware7*} target
2003 but is meant to be used when hosting on a system where UDK isn't the
2004 default compiler such as OpenServer 5 or Unixware 2. This target will
2005 generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
2006 with the same warnings and caveats as the SCO UDK@.
2008 This target is a little tricky to build because we have to distinguish
2009 it from the native tools (so it gets headers, startups, and libraries
2010 from the right place) while making the tools not think we're actually
2011 building a cross compiler. The easiest way to do this is with a configure
2014 @samp{CC=/udk/usr/ccs/bin/cc @var{/your/path/to}/gcc/configure
2015 --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-}
2017 @emph{You should substitute @samp{i686} in the above command with the appropriate
2018 processor for your host.}
2020 After the usual @samp{make bootstrap} and
2021 @samp{make install}, you can then access the UDK-targeted GCC
2022 tools by adding @command{udk-} before the commonly known name. For
2023 example, to invoke the C compiler, you would use @command{udk-gcc}.
2024 They will coexist peacefully with any native-target GCC tools you may
2032 @heading @anchor{ix86-*-isc}i?86-*-isc
2033 It may be a good idea to link with GNU malloc instead of the malloc that
2034 comes with the system.
2036 In ISC version 4.1, @command{sed} core dumps when building
2037 @file{deduced.h}. Use the version of @command{sed} from version 4.0.
2043 @heading @anchor{ix86-*-esix}i?86-*-esix
2044 It may be good idea to link with GNU malloc instead of the malloc that
2045 comes with the system.
2051 @heading @anchor{ix86-ibm-aix}i?86-ibm-aix
2052 You need to use GAS version 2.1 or later, and LD from
2053 GNU binutils version 2.2 or later.
2059 @heading @anchor{ix86-sequent-bsd}i?86-sequent-bsd
2060 Go to the Berkeley universe before compiling.
2066 @heading @anchor{ix86-sequent-ptx1*}i?86-sequent-ptx1*, i?86-sequent-ptx2*
2067 You must install GNU @command{sed} before running @command{configure}.
2073 @heading @anchor{#ix86-*-sysv3*}i?86-*-sysv3*
2074 The @code{fixproto} shell script may trigger a bug in the system shell.
2075 If you encounter this problem, upgrade your operating system or
2076 use @command{bash} (the GNU shell) to run @code{fixproto}.
2083 @heading @anchor{i860-intel-osf*}i860-intel-osf*
2084 On the Intel Paragon (an i860 machine), if you are using operating
2085 system version 1.0, you will get warnings or errors about redefinition
2086 of @code{va_arg} when you build GCC@.
2088 If this happens, then you need to link most programs with the library
2089 @file{iclib.a}. You must also modify @file{stdio.h} as follows: before
2093 #if defined(__i860__) && !defined(_VA_LIST)
2094 #include <va_list.h>
2108 extern int vprintf(const char *, va_list );
2109 extern int vsprintf(char *, const char *, va_list );
2117 #endif /* __PGC__ */
2120 These problems don't exist in operating system version 1.1.
2126 @heading @anchor{*-lynx-lynxos}*-lynx-lynxos
2127 LynxOS 2.2 and earlier comes with GCC 1.x already installed as
2128 @file{/bin/gcc}. You should compile with this instead of @file{/bin/cc}.
2129 You can tell GCC to use the GNU assembler and linker, by specifying
2130 @samp{--with-gnu-as --with-gnu-ld} when configuring. These will produce
2131 COFF format object files and executables; otherwise GCC will use the
2132 installed tools, which produce @file{a.out} format executables.
2137 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
2139 @heading @anchor{*-ibm-aix*}*-ibm-aix*
2141 AIX Make frequently has problems with GCC makefiles. GNU Make 3.76 or
2142 newer is recommended to build on this platform.
2144 Errors involving @code{alloca} when building GCC generally are due
2145 to an incorrect definition of @code{CC} in the Makefile or mixing files
2146 compiled with the native C compiler and GCC@. During the stage1 phase of
2147 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
2148 (not @command{xlc}). Once @command{configure} has been informed of
2149 @command{xlc}, one needs to use @samp{make distclean} to remove the
2150 configure cache files and ensure that @env{CC} environment variable
2151 does not provide a definition that will confuse @command{configure}.
2152 If this error occurs during stage2 or later, then the problem most likely
2153 is the version of Make (see above).
2155 Binutils 2.10 does not support AIX 4.3. Binutils available from the
2156 @uref{http://www-1.ibm.com/servers/aix/products/aixos/linux/,,AIX
2157 Toolbox for Linux: GNU and Open Source tools for AIX};
2158 website does work. Binutils 2.11 is expected to include AIX 4.3
2159 support. The GNU Assembler is necessary for @samp{libstdc++} to build. The
2160 AIX native @command{ld} still is recommended. The native AIX tools do
2161 interoperate with GCC@.
2163 Linking executables and shared libraries may produce warnings of
2164 duplicate symbols. The assembly files generated by GCC for AIX always
2165 have included multiple symbol definitions for certain global variable
2166 and function declarations in the original program. The warnings should
2167 not prevent the linker from producing a correct library or runnable
2170 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
2171 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
2172 to parse archive libraries did not handle the new format correctly.
2173 These routines are used by GCC and result in error messages during
2174 linking such as ``not a COFF file''. The version of the routines shipped
2175 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
2176 option of the archive command may be used to create archives of 32-bit
2177 objects using the original ``small format''. A correct version of the
2178 routines is shipped with AIX 4.3.2.
2180 Some versions of the AIX binder (linker) can fail with a relocation
2181 overflow severe error when the @option{-bbigtoc} option is used to link
2182 GCC-produced object files into an executable that overflows the TOC@. A fix
2183 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
2184 available from IBM Customer Support and from its
2185 @uref{http://service.boulder.ibm.com/,,service.boulder.ibm.com}
2186 website as PTF U455193.
2188 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
2189 with a segmentation fault when invoked by any version of GCC@. A fix for
2190 APAR IX87327 is available from IBM Customer Support and from its
2191 @uref{http://service.boulder.ibm.com/,,service.boulder.ibm.com}
2192 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
2194 The initial assembler shipped with AIX 4.3.0 generates incorrect object
2195 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
2196 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
2197 @uref{http://service.boulder.ibm.com/,,service.boulder.ibm.com}
2198 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
2200 AIX provides National Language Support (NLS)@. Compilers and assemblers
2201 use NLS to support locale-specific representations of various data
2202 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
2203 separating decimal fractions). There have been problems reported where
2204 GCC does not produce the same floating-point formats that the assembler
2205 expects. If one encounters this problem, set the @env{LANG}
2206 environment variable to @samp{C} or @samp{En_US}.
2208 By default, GCC for AIX 4.1 and above produces code that can be used on
2209 both Power or PowerPC processors.
2211 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
2212 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
2218 @heading @anchor{m32r-*-elf}m32r-*-elf
2219 Mitsubishi M32R processor.
2220 This configuration is intended for embedded systems.
2226 @heading @anchor{m68000-hp-bsd}m68000-hp-bsd
2227 HP 9000 series 200 running BSD@. Note that the C compiler that comes
2228 with this system cannot compile GCC; contact @email{law@@cygnus.com}
2229 to get binaries of GCC for bootstrapping.
2235 @heading @anchor{m6811-elf}m6811-elf
2236 Motorola 68HC11 family micro controllers. These are used in embedded
2237 applications. There are no standard Unix configurations.
2243 @heading @anchor{m6812-elf}m6812-elf
2244 Motorola 68HC12 family micro controllers. These are used in embedded
2245 applications. There are no standard Unix configurations.
2251 @heading @anchor{m68k-altos}m68k-altos
2252 Altos 3068. You must use the GNU assembler, linker and debugger.
2253 Also, you must fix a kernel bug.
2259 @heading @anchor{m68k-apple-aux}m68k-apple-aux
2260 Apple Macintosh running A/UX@.
2261 You may configure GCC to use either the system assembler and
2262 linker or the GNU assembler and linker. You should use the GNU configuration
2263 if you can, especially if you also want to use G++. You enable
2264 that configuration with the @option{--with-gnu-as} and @option{--with-gnu-ld}
2265 options to @code{configure}.
2267 Note the C compiler that comes
2268 with this system cannot compile GCC@. You can find binaries of GCC
2269 for bootstrapping on @code{jagubox.gsfc.nasa.gov}.
2270 You will also a patched version of @file{/bin/ld} there that
2271 raises some of the arbitrary limits found in the original.
2277 @heading @anchor{m68k-att-sysv}m68k-att-sysv
2278 AT&T 3b1, a.k.a.@: 7300 PC@. This version of GCC cannot
2279 be compiled with the system C compiler, which is too buggy.
2280 You will need to get a previous version of GCC and use it to
2281 bootstrap. Binaries are available from the OSU-CIS archive, at
2282 @uref{ftp://archive.cis.ohio-state.edu/pub/att7300/}.
2288 @heading @anchor{m68k-bull-sysv}m68k-bull-sysv
2289 Bull DPX/2 series 200 and 300 with BOS-2.00.45 up to BOS-2.01. GCC works
2290 either with native assembler or GNU assembler. You can use
2291 GNU assembler with native COFF generation by providing @option{--with-gnu-as} to
2292 the configure script or use GNU assembler with stabs-in-COFF encapsulation
2293 by providing @samp{--with-gnu-as --stabs}. For any problem with the native
2294 assembler or for availability of the DPX/2 port of GAS, contact
2295 @email{F.Pierresteguy@@frcl.bull.fr}.
2301 @heading @anchor{m68k-crds-unox}m68k-crds-unox
2302 Use @samp{configure unos} for building on Unos.
2304 The Unos assembler is named @code{casm} instead of @code{as}. For some
2305 strange reason linking @file{/bin/as} to @file{/bin/casm} changes the
2306 behavior, and does not work. So, when installing GCC, you should
2307 install the following script as @file{as} in the subdirectory where
2308 the passes of GCC are installed:
2315 The default Unos library is named @file{libunos.a} instead of
2316 @file{libc.a}. To allow GCC to function, either change all
2317 references to @option{-lc} in @file{gcc.c} to @option{-lunos} or link
2318 @file{/lib/libc.a} to @file{/lib/libunos.a}.
2320 @cindex @code{alloca}, for Unos
2321 When compiling GCC with the standard compiler, to overcome bugs in
2322 the support of @code{alloca}, do not use @option{-O} when making stage 2.
2323 Then use the stage 2 compiler with @option{-O} to make the stage 3
2324 compiler. This compiler will have the same characteristics as the usual
2325 stage 2 compiler on other systems. Use it to make a stage 4 compiler
2326 and compare that with stage 3 to verify proper compilation.
2328 (Perhaps simply defining @code{ALLOCA} in @file{x-crds} as described in
2329 the comments there will make the above paragraph superfluous. Please
2330 inform us of whether this works.)
2332 Unos uses memory segmentation instead of demand paging, so you will need
2333 a lot of memory. 5 Mb is barely enough if no other tasks are running.
2334 If linking @file{cc1} fails, try putting the object files into a library
2335 and linking from that library.
2341 @heading @anchor{m68k-hp-hpux}m68k-hp-hpux
2342 HP 9000 series 300 or 400 running HP-UX@. HP-UX version 8.0 has a bug in
2343 the assembler that prevents compilation of GCC@. This
2344 bug manifests itself during the first stage of compilation, while
2345 building @file{libgcc2.a}:
2349 cc1: warning: `-g' option not supported on this version of GCC
2350 cc1: warning: `-g1' option not supported on this version of GCC
2351 ./xgcc: Internal compiler error: program as got fatal signal 11
2354 A patched version of the assembler is available as the file
2355 @uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you
2356 have HP software support, the patch can also be obtained directly from
2357 HP, as described in the following note:
2360 This is the patched assembler, to patch SR#1653-010439, where the
2361 assembler aborts on floating point constants.
2363 The bug is not really in the assembler, but in the shared library
2364 version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is
2365 SR#4701-078451. Anyway, the attached assembler uses the archive
2366 library version of ``cvtnum(3c)'' and thus does not exhibit the bug.
2369 This patch is also known as PHCO_4484.
2371 In addition, if you wish to use gas, you must use
2372 gas version 2.1 or later, and you must use the GNU linker version 2.1 or
2373 later. Earlier versions of gas relied upon a program which converted the
2374 gas output into the native HP-UX format, but that program has not been
2375 kept up to date. gdb does not understand that native HP-UX format, so
2376 you must use gas if you wish to use gdb.
2378 On HP-UX version 8.05, but not on 8.07 or more recent versions, the
2379 @code{fixproto} shell script triggers a bug in the system shell. If you
2380 encounter this problem, upgrade your operating system or use BASH (the
2381 GNU shell) to run @code{fixproto}. This bug will cause the fixproto
2382 program to report an error of the form:
2385 ./fixproto: sh internal 1K buffer overflow
2388 To fix this, you can also change the first line of the fixproto script
2400 @heading @anchor{m68k-*-nextstep*}m68k-*-nextstep*
2402 Current GCC versions probably do not work on version 2 of the NeXT
2405 On NeXTStep 3.0, the Objective-C compiler does not work, due,
2406 apparently, to a kernel bug that it happens to trigger. This problem
2407 does not happen on 3.1.
2409 You absolutely @strong{must} use GNU sed and GNU make on this platform.
2412 On NeXTSTEP 3.x where x < 3 the build of GCC will abort during
2413 stage1 with an error message like this:
2417 /usr/tmp/ccbbsZ0U.s:987:Unknown pseudo-op: .section
2418 /usr/tmp/ccbbsZ0U.s:987:Rest of line ignored. 1st junk character
2422 The reason for this is the fact that NeXT's assembler for these
2423 versions of the operating system does not support the @samp{.section}
2424 pseudo op that's needed for full C++ exception functionality.
2426 As NeXT's assembler is a derived work from GNU as, a free
2427 replacement that does can be obtained at
2428 @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}.
2430 If you try to build the integrated C++ & C++ runtime libraries on this system
2431 you will run into trouble with include files. The way to get around this is
2432 to use the following sequence. Note you must have write permission to
2433 the directory @var{prefix} you specified in the configuration process of GCC
2434 for this sequence to work.
2438 make all-texinfo all-bison all-byacc all-binutils all-gas all-ld
2441 make install-headers-tar
2450 @heading @anchor{m68k-ncr-*}m68k-ncr-*
2451 On the Tower models 4@var{n}0 and 6@var{n}0, by default a process is not
2452 allowed to have more than one megabyte of memory. GCC cannot compile
2453 itself (or many other programs) with @option{-O} in that much memory.
2455 To solve this problem, reconfigure the kernel adding the following line
2456 to the configuration file:
2467 @heading @anchor{m68k-sun}m68k-sun
2468 Sun 3. We do not provide a configuration file to use the Sun FPA by
2469 default, because programs that establish signal handlers for floating
2470 point traps inherently cannot work with the FPA@.
2476 @heading @anchor{m68k-sun-sunos4.1.1}m68k-sun-sunos4.1.1
2478 It is reported that you may need the GNU assembler on this platform.
2485 @heading @anchor{m88k-*-svr3}m88k-*-svr3
2486 Motorola m88k running the AT&T/Unisoft/Motorola V.3 reference port.
2487 These systems tend to use the Green Hills C, revision 1.8.5, as the
2488 standard C compiler. There are apparently bugs in this compiler that
2489 result in object files differences between stage 2 and stage 3. If this
2490 happens, make the stage 4 compiler and compare it to the stage 3
2491 compiler. If the stage 3 and stage 4 object files are identical, this
2492 suggests you encountered a problem with the standard C compiler; the
2493 stage 3 and 4 compilers may be usable.
2495 It is best, however, to use an older version of GCC for bootstrapping
2502 @heading @anchor{m88k-*-dgux}m88k-*-dgux
2503 Motorola m88k running DG/UX@. To build 88open BCS native or cross
2504 compilers on DG/UX, specify the configuration name as
2505 @samp{m88k-*-dguxbcs} and build in the 88open BCS software development
2506 environment. To build ELF native or cross compilers on DG/UX, specify
2507 @samp{m88k-*-dgux} and build in the DG/UX ELF development environment.
2508 You set the software development environment by issuing
2509 @samp{sde-target} command and specifying either @samp{m88kbcs} or
2510 @samp{m88kdguxelf} as the operand.
2512 If you do not specify a configuration name, @file{configure} guesses the
2513 configuration based on the current software development environment.
2519 @heading @anchor{m88k-tektronix-sysv3}m88k-tektronix-sysv3
2520 Tektronix XD88 running UTekV 3.2e. Do not turn on
2521 optimization while building stage1 if you bootstrap with
2522 the buggy Green Hills compiler. Also, the bundled LAI
2523 System V NFS is buggy so if you build in an NFS mounted
2524 directory, start from a fresh reboot, or avoid NFS all together.
2525 Otherwise you may have trouble getting clean comparisons
2532 @heading @anchor{mips-*-*}mips-*-*
2533 If you use the 1.31 version of the MIPS assembler (such as was shipped
2534 with Ultrix 3.1), you will need to use the @option{-fno-delayed-branch} switch
2535 when optimizing floating point code. Otherwise, the assembler will
2536 complain when the GCC compiler fills a branch delay slot with a
2537 floating point instruction, such as @code{add.d}.
2539 If on a MIPS system you get an error message saying ``does not have gp
2540 sections for all it's [sic] sectons [sic]'', don't worry about it. This
2541 happens whenever you use GAS with the MIPS linker, but there is not
2542 really anything wrong, and it is okay to use the output file. You can
2543 stop such warnings by installing the GNU linker.
2545 It would be nice to extend GAS to produce the gp tables, but they are
2546 optional, and there should not be a warning about their absence.
2548 Users have reported some problems with version 2.0 of the MIPS
2549 compiler tools that were shipped with Ultrix 4.1. Version 2.10
2550 which came with Ultrix 4.2 seems to work fine.
2552 Users have also reported some problems with version 2.20 of the
2553 MIPS compiler tools that were shipped with RISC/os 4.x. The earlier
2554 version 2.11 seems to work fine.
2556 Some versions of the MIPS linker will issue an assertion failure
2557 when linking code that uses @code{alloca} against shared
2558 libraries on RISC-OS 5.0, and DEC's OSF/1 systems. This is a bug
2559 in the linker, that is supposed to be fixed in future revisions.
2560 To protect against this, GCC passes @option{-non_shared} to the
2561 linker unless you pass an explicit @option{-shared} or
2562 @option{-call_shared} switch.
2564 @heading @anchor{mips-mips-bsd}mips-mips-bsd
2565 MIPS machines running the MIPS operating system in BSD mode. It's
2566 possible that some old versions of the system lack the functions
2567 @code{memcpy}, @code{memmove}, @code{memcmp}, and @code{memset}. If your
2568 system lacks these, you must remove or undo the definition of
2569 @code{TARGET_MEM_FUNCTIONS} in @file{mips-bsd.h}.
2571 If you use the MIPS C compiler to bootstrap, it may be necessary
2572 to increase its table size for switch statements with the
2573 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
2574 optimization option, you also need to use @option{-Olimit 3000}.
2575 Both of these options are automatically generated in the
2576 @file{Makefile} that the shell script @file{configure} builds.
2577 If you override the @code{CC} make variable and use the MIPS
2578 compilers, you may need to add @option{-Wf,-XNg1500 -Olimit 3000}.
2584 @heading @anchor{mips-dec-*}mips-dec-*
2585 MIPS-based DECstations can support three different personalities:
2586 Ultrix, DEC OSF/1, and OSF/rose. (Alpha-based DECstation products have
2587 a configuration name beginning with @samp{alpha*-dec}.) To configure GCC
2588 for these platforms use the following configurations:
2591 @item mips-dec-ultrix
2592 Ultrix configuration.
2595 DEC's version of OSF/1.
2597 @item mips-dec-osfrose
2598 Open Software Foundation reference port of OSF/1 which uses the
2599 OSF/rose object file format instead of ECOFF@. Normally, you
2600 would not select this configuration.
2603 If you use the MIPS C compiler to bootstrap, it may be necessary
2604 to increase its table size for switch statements with the
2605 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
2606 optimization option, you also need to use @option{-Olimit 3000}.
2607 Both of these options are automatically generated in the
2608 @file{Makefile} that the shell script @file{configure} builds.
2609 If you override the @code{CC} make variable and use the MIPS
2610 compilers, you may need to add @option{-Wf,-XNg1500 -Olimit 3000}.
2616 @heading @anchor{mips-mips-riscos*}mips-mips-riscos*
2617 If you use the MIPS C compiler to bootstrap, it may be necessary
2618 to increase its table size for switch statements with the
2619 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
2620 optimization option, you also need to use @option{-Olimit 3000}.
2621 Both of these options are automatically generated in the
2622 @file{Makefile} that the shell script @file{configure} builds.
2623 If you override the @code{CC} make variable and use the MIPS
2624 compilers, you may need to add @samp{-Wf,-XNg1500 -Olimit 3000}.
2626 MIPS computers running RISC-OS can support four different
2627 personalities: default, BSD 4.3, System V.3, and System V.4
2628 (older versions of RISC-OS don't support V.4). To configure GCC
2629 for these platforms use the following configurations:
2632 @item mips-mips-riscos@var{rev}
2633 Default configuration for RISC-OS, revision @var{rev}.
2635 @item mips-mips-riscos@var{rev}bsd
2636 BSD 4.3 configuration for RISC-OS, revision @var{rev}.
2638 @item mips-mips-riscos@var{rev}sysv4
2639 System V.4 configuration for RISC-OS, revision @var{rev}.
2645 @item mips-mips-riscos@var{rev}sysv
2646 System V.3 configuration for RISC-OS, revision @var{rev}.
2649 The revision @code{rev} mentioned above is the revision of
2650 RISC-OS to use. You must reconfigure GCC when going from a
2651 RISC-OS revision 4 to RISC-OS revision 5. This has the effect of
2652 avoiding a linker bug.
2658 @heading @anchor{mips-sgi-irix4}mips-sgi-irix4
2660 In order to compile GCC on an SGI running IRIX 4, the ``c.hdr.lib''
2661 option must be installed from the CD-ROM supplied from Silicon Graphics.
2662 This is found on the 2nd CD in release 4.0.1.
2664 On IRIX version 4.0.5F, and perhaps on some other versions as well,
2665 there is an assembler bug that reorders instructions incorrectly. To
2666 work around it, specify the target configuration
2667 @samp{mips-sgi-irix4loser}. This configuration inhibits assembler
2670 In a compiler configured with target @samp{mips-sgi-irix4}, you can turn
2671 off assembler optimization by using the @option{-noasmopt} option. This
2672 compiler option passes the option @option{-O0} to the assembler, to
2675 The @option{-noasmopt} option can be useful for testing whether a problem
2676 is due to erroneous assembler reordering. Even if a problem does not go
2677 away with @option{-noasmopt}, it may still be due to assembler
2678 reordering---perhaps GCC itself was miscompiled as a result.
2680 You may get the following warning on IRIX 4 platforms, it can be safely
2683 warning: foo.o does not have gp tables for all its sections.
2690 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
2692 This configuration has considerable problems, which will be fixed in a
2695 In order to compile GCC on an SGI running IRIX 5, the ``compiler_dev.hdr''
2696 subsystem must be installed from the IDO CD-ROM supplied by Silicon
2697 Graphics. It is also available for download from
2698 @uref{http://www.sgi.com/developers/devtools/apis/ido.html,,http://www.sgi.com/developers/devtools/apis/ido.html}.
2700 @code{make compare} may fail on version 5 of IRIX unless you add
2701 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
2702 assembler input file is stored in the object file, and that makes
2703 comparison fail if it differs between the @code{stage1} and
2704 @code{stage2} compilations. The option @option{-save-temps} forces a
2705 fixed name to be used for the assembler input file, instead of a
2706 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
2707 unless the comparisons fail without that option. If you do you
2708 @option{-save-temps}, you will have to manually delete the @samp{.i} and
2709 @samp{.s} files after each series of compilations.
2711 If you use the MIPS C compiler to bootstrap, it may be necessary
2712 to increase its table size for switch statements with the
2713 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
2714 optimization option, you also need to use @option{-Olimit 3000}.
2716 To enable debugging under IRIX 5, you must use GNU @command{as} 2.11.2
2718 and use the @option{--with-gnu-as} configure option when configuring GCC.
2719 GNU @command{as} is distributed as part of the binutils package.
2720 When using release 2.11.2, you need to apply a patch
2721 @uref{http://sources.redhat.com/ml/binutils/2001-07/msg00352.html,,http://sources.redhat.com/ml/binutils/2001-07/msg00352.html}
2722 which will be included in the next release of binutils.
2724 When building GCC, the build process loops rebuilding @command{cc1} over
2725 and over again. This happens on @samp{mips-sgi-irix5.2}, and possibly
2726 other platforms. It has been reported that this is a known bug in the
2727 @command{make} shipped with IRIX 5.2. We recommend you use GNU
2728 @command{make} instead of the vendor supplied @command{make} program;
2729 however, you may have success with @command{smake} on IRIX 5.2 if you do
2730 not have GNU @command{make} available.
2736 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
2738 If you are using IRIX @command{cc} as your bootstrap compiler, you must
2739 ensure that the N32 ABI is in use. To test this, compile a simple C
2740 file with @command{cc} and then run @command{file} on the
2741 resulting object file. The output should look like:
2744 test.o: ELF N32 MSB @dots{}
2750 test.o: ELF 32-bit MSB @dots{}
2756 test.o: ELF 64-bit MSB @dots{}
2759 then your version of @command{cc} uses the O32 or N64 ABI by default. You
2760 should set the environment variable @env{CC} to @samp{cc -n32}
2761 before configuring GCC@.
2763 GCC on IRIX 6 is usually built to support both the N32 and N64 ABIs. If
2764 you build GCC on a system that doesn't have the N64 libraries installed,
2765 you need to configure with @option{--disable-multilib} so GCC doesn't
2766 try to use them. Look for @file{/usr/lib64/libc.so.1} to see if you
2767 have the 64-bit libraries installed.
2769 You must @emph{not} use GNU @command{as} (which isn't built anyway as of
2770 binutils 2.11.2) on IRIX 6 platforms; doing so will only cause problems.
2772 GCC does not currently support generating O32 ABI binaries in the
2773 @samp{mips-sgi-irix6} configurations. It is possible to create a GCC
2774 with O32 ABI only support by configuring it for the @samp{mips-sgi-irix5}
2775 target and using a patched GNU @command{as} 2.11.2 as documented in the
2776 @uref{#mips-sgi-irix5,,@samp{mips-sgi-irix5}} section above. Using the
2777 native assembler requires patches to GCC which will be included in a
2778 future release. It is
2779 expected that O32 ABI support will be available again in a future release.
2781 The @option{--enable-threads} option doesn't currently work, a patch is
2782 in preparation for a future release. The @option{--enable-libgcj}
2783 option is disabled by default: IRIX 6 uses a very low default limit
2784 (20480) for the command line length. Although libtool contains a
2785 workaround for this problem, at least the N64 @samp{libgcj} is known not
2786 to build despite this, running into an internal error of the native
2787 @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
2788 its maximum of 262144 bytes. If you have root access, you can use the
2789 @command{systune} command to do this.
2791 GCC does not correctly pass/return structures which are
2792 smaller than 16 bytes and which are not 8 bytes. The problem is very
2793 involved and difficult to fix. It affects a number of other targets also,
2794 but IRIX 6 is affected the most, because it is a 64 bit target, and 4 byte
2795 structures are common. The exact problem is that structures are being padded
2796 at the wrong end, e.g.@: a 4 byte structure is loaded into the lower 4 bytes
2797 of the register when it should be loaded into the upper 4 bytes of the
2800 GCC is consistent with itself, but not consistent with the SGI C compiler
2801 (and the SGI supplied runtime libraries), so the only failures that can
2802 happen are when there are library functions that take/return such
2803 structures. There are very few such library functions. Currently this
2804 is known to affect @code{inet_ntoa}, @code{inet_lnaof},
2805 @code{inet_netof}, @code{inet_makeaddr}, and @code{semctl}. Until the
2806 bug is fixed, GCC contains workarounds for the known affected functions.
2808 See @uref{http://freeware.sgi.com/,,http://freeware.sgi.com/} for more
2809 information about using GCC on IRIX platforms.
2815 @heading @anchor{mips-sony-sysv}mips-sony-sysv
2816 Sony MIPS NEWS@. This works in NEWSOS 5.0.1, but not in 5.0.2 (which
2817 uses ELF instead of COFF)@. Support for 5.0.2 will probably be provided
2818 soon by volunteers. In particular, the linker does not like the
2819 code generated by GCC when shared libraries are linked in.
2826 @heading @anchor{ns32k-encore}ns32k-encore
2827 Encore ns32000 system. Encore systems are supported only under BSD@.
2833 @heading @anchor{ns32k-*-genix}ns32k-*-genix
2834 National Semiconductor ns32000 system. Genix has bugs in @code{alloca}
2835 and @code{malloc}; you must get the compiled versions of these from GNU
2842 @heading @anchor{ns32k-sequent}ns32k-sequent
2843 Go to the Berkeley universe before compiling.
2849 @heading @anchor{ns32k-utek}ns32k-utek
2850 UTEK ns32000 system (``merlin''). The C compiler that comes with this
2851 system cannot compile GCC; contact @samp{tektronix!reed!mason} to get
2852 binaries of GCC for bootstrapping.
2859 @heading @anchor{powerpc*-*-*}powerpc-*-*
2861 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
2862 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
2868 @heading @anchor{powerpc-*-darwin*}powerpc-*-darwin*
2869 PowerPC running Darwin (Mac OS X kernel).
2871 GCC 3.0 does not support Darwin, but 3.1 and later releases will work.
2873 Pre-installed versions of Mac OS X may not include any developer tools,
2874 meaning that you will not be able to build GCC from source. Tool
2875 binaries are available at
2876 @uref{http://www.opensource.apple.com/projects/darwin} (free
2877 registration required).
2879 Versions of the assembler prior to ``cctools-364'' cannot handle the
2880 4-argument form of rlwinm and related mask-using instructions. Darwin
2881 1.3 (Mac OS X 10.0) uses cctools-353 for instance. To get cctools-364,
2882 check out @file{cctools} with tag @samp{Apple-364}, build it, and
2883 install the assembler as @file{usr/bin/as}. See
2884 @uref{http://www.opensource.apple.com/tools/cvs/docs.html} for details.
2886 Also, the default stack limit of 512K is too small, and a bootstrap will
2887 typically fail when self-compiling @file{expr.c}. Set the stack to 800K
2888 or more, for instance by doing @samp{limit stack 800}. It's also
2889 convenient to use the GNU preprocessor instead of Apple's during the
2890 first stage of bootstrapping; this is automatic when doing @samp{make
2891 bootstrap}, but to do it from the toplevel objdir you will need to say
2892 @samp{make CC='cc -no-cpp-precomp' bootstrap}.
2894 Note that the version of GCC shipped by Apple typically includes a
2895 number of extensions not available in a standard GCC release. These
2896 extensions are generally specific to Mac programming.
2902 @heading @anchor{powerpc-*-elf}powerpc-*-elf, powerpc-*-sysv4
2903 PowerPC system in big endian mode, running System V.4.
2909 @heading @anchor{powerpc-*-linux-gnu*}powerpc-*-linux-gnu*
2912 @uref{ftp://ftp.varesearch.com/pub/support/hjl/binutils,,binutils 2.9.4.0.8}
2913 or newer for a working GCC@. It is strongly recommended to recompile binutils
2914 if you initially built it with gcc-2.7.2.x.
2920 @heading @anchor{powerpc-*-netbsd*}powerpc-*-netbsd*
2921 PowerPC system in big endian mode running NetBSD@. To build the
2922 documentation you will need Texinfo version 4.0 (NetBSD 1.5.1 included
2923 Texinfo version 3.12).
2929 @heading @anchor{powerpc-*-eabiaix}powerpc-*-eabiaix
2930 Embedded PowerPC system in big endian mode with @option{-mcall-aix} selected as
2937 @heading @anchor{powerpc-*-eabisim}powerpc-*-eabisim
2938 Embedded PowerPC system in big endian mode for use in running under the
2945 @heading @anchor{powerpc-*-eabi}powerpc-*-eabi
2946 Embedded PowerPC system in big endian mode.
2952 @heading @anchor{powerpcle-*-elf}powerpcle-*-elf, powerpcle-*-sysv4
2953 PowerPC system in little endian mode, running System V.4.
2959 @heading @anchor{powerpcle-*-eabisim}powerpcle-*-eabisim
2960 Embedded PowerPC system in little endian mode for use in running under
2967 @heading @anchor{powerpcle-*-eabi}powerpcle-*-eabi
2968 Embedded PowerPC system in little endian mode.
2974 @heading @anchor{powerpcle-*-winnt}powerpcle-*-winnt, powerpcle-*-pe
2975 PowerPC system in little endian mode running Windows NT@.
2981 @heading @anchor{romp-*-aos}romp-*-aos, romp-*-mach
2982 The only operating systems supported for the IBM RT PC are AOS and
2983 MACH@. GCC does not support AIX running on the RT@. We recommend you
2984 compile GCC with an earlier version of itself; if you compile GCC
2985 with @command{hc}, the Metaware compiler, it will work, but you will get
2986 mismatches between the stage 2 and stage 3 compilers in various files.
2987 These errors are minor differences in some floating-point constants and
2988 can be safely ignored; the stage 3 compiler is correct.
2994 @heading @anchor{s390-*-linux*}s390-*-linux*
2995 S/390 system running Linux for S/390@.
3001 @heading @anchor{s390x-*-linux*}s390x-*-linux*
3002 zSeries system (64 Bit) running Linux for zSeries@.
3008 @heading @anchor{*-*-solaris*}*-*-solaris*
3010 Sun does not ship a C compiler with Solaris. To bootstrap and install
3011 GCC you first have to install a pre-built compiler, see our
3012 @uref{binaries.html,,binaries page} for details.
3014 Solaris' @file{/bin/sh} will often fail to configure @file{libstdc++-v3}, @file{boehm-gc} or
3015 @file{libjava}. If you encounter this problem, set @env{CONFIG_SHELL} to
3016 @file{/bin/ksh} in your environment and run @command{make bootstrap} again.
3017 Another possibility that sometimes helps is to remove
3018 @file{*-*-solaris*/config.cache}.
3020 Solaris 2 comes with a number of optional OS packages. Some of these
3021 packages are needed to use GCC fully, namely @code{SUNWarc},
3022 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
3023 @code{SUNWsprot}, and @code{SUNWtoo}. 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 @command{pkginfo} command. To add an optional package, use the
3029 @command{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
3037 On some versions of Solaris, trying to use the linker and other tools in
3038 @file{/usr/ucb} to install GCC has been observed to cause trouble.
3039 For example, the linker may hang indefinitely. The fix is to remove
3040 @file{/usr/ucb} from your @code{PATH}.
3042 All releases of GNU binutils prior to 2.11.2 have known bugs on this
3043 platform. We recommend the use of GNU binutils 2.11.2 or the vendor
3044 tools (Sun @command{as}, Sun @command{ld}).
3046 Unfortunately, C++ shared libraries, including @samp{libstdc++}, won't work
3047 properly if assembled with Sun @command{as}: the linker will complain about
3048 relocations in read-only sections, in the definition of virtual
3049 tables. Also, Sun @command{as} fails to process long symbols resulting from
3050 mangling template-heavy C++ function names.
3056 @heading @anchor{sparc-sun-solaris*}sparc-sun-solaris*
3058 Sun @command{as} 4.X is broken in that it cannot cope with long symbol names.
3059 A typical error message might look similar to the following:
3061 @samp{/usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041:
3062 error: can't compute value of an expression involving an external symbol.}
3064 This is Sun bug 4237974. This is fixed with patch 108908-02 and has
3065 been fixed in later (5.x) versions of the assembler.
3071 @heading @anchor{sparc-sun-solaris2.7}sparc-sun-solaris2.7
3073 Sun patch 107058-01 (1999-01-13) for SPARC Solaris 7 triggers a bug in
3074 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
3075 and later, including all EGCS releases. Sun formerly recommended
3076 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
3077 recommend it only for people who use Sun's compilers.
3079 Here are some workarounds to this problem:
3082 Do not install Sun patch 107058-01 until after Sun releases a
3083 complete patch for bug 4210064. This is the simplest course to take,
3084 unless you must also use Sun's C compiler. Unfortunately 107058-01
3085 is preinstalled on some new Solaris-based hosts, so you may have to
3089 Copy the original, unpatched Solaris 7
3090 @command{/usr/ccs/bin/as} into
3091 @command{/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/3.0/as},
3092 adjusting the latter name to fit your local conventions and software
3096 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
3097 both 107058-01 and 106950-03 installed has reported the bug with GCC
3098 and Sun's dynamic linker. This last course of action is riskiest,
3099 for two reasons. First, you must install 106950 on all hosts that
3100 run code generated by GCC; it doesn't suffice to install it only on
3101 the hosts that run GCC itself. Second, Sun says that 106950-03 is
3102 only a partial fix for bug 4210064, but Sun doesn't know whether the
3103 partial fix is adequate for GCC@. Revision -08 or later should fix
3104 the bug, but (as of 1999-10-06) it is still being tested.
3111 <!-- ripped from the same FAQ that I answered -->
3113 @heading @anchor{*-sun-solaris2.8}*-sun-solaris2.8
3115 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3116 newer: @command{g++} will complain that types are missing. These headers assume
3117 that omitting the type means @code{int}; this assumption worked for C89 but
3118 is wrong for C++, and is now wrong for C99 also.
3120 @command{g++} accepts such (illegal) constructs with the option @option{-fpermissive}; it
3121 will assume that any missing type is @code{int} (as defined by C89).
3123 For Solaris 8, this is fixed by revision 24 or later of patch 108652
3124 (for SPARCs) or 108653 (for Intels).
3126 Solaris 8's linker fails to link some @samp{libjava} programs if
3127 previously-installed GCC java libraries already exist in the configured
3128 prefix. For this reason, @samp{libgcj} is disabled by default on Solaris 8.
3129 If you use GNU ld, or if you don't have a previously-installed @samp{libgcj} in
3130 the same prefix, use @option{--enable-libgcj} to build and install the
3137 @heading @anchor{sparc-sun-sunos*}sparc-sun-sunos*
3139 A bug in the SunOS 4 linker will cause it to crash when linking
3140 @option{-fPIC} compiled objects (and will therefore not allow you to build
3143 To fix this problem you can either use the most recent version of
3144 binutils or get the latest SunOS 4 linker patch (patch ID 100170-10)
3145 from Sun's patch site.
3147 Sometimes on a Sun 4 you may observe a crash in the program
3148 @command{genflags} or @command{genoutput} while building GCC. This is said to
3149 be due to a bug in @command{sh}. You can probably get around it by running
3150 @command{genflags} or @command{genoutput} manually and then retrying the
3157 @heading @anchor{sparc-unknown-linux-gnulibc1}sparc-unknown-linux-gnulibc1
3159 It has been reported that you might need
3160 @uref{ftp://ftp.yggdrasil.com/private/hjl,,binutils 2.8.1.0.23}
3161 for this platform, too.
3168 @heading @anchor{sparc64-*-*}sparc64-*-*
3170 GCC version 2.95 is not able to compile code correctly for
3171 @code{sparc64} targets. Users of the Linux kernel, at least,
3172 can use the @code{sparc32} program to start up a new shell
3173 invocation with an environment that causes @command{configure} to
3174 recognize (via @samp{uname -a}) the system as @samp{sparc-*-*} instead.
3181 @heading @anchor{#*-*-sysv*}*-*-sysv*
3182 On System V release 3, you may get this error message
3186 ld fatal: failed to write symbol name @var{something}
3187 in strings table for file @var{whatever}
3190 This probably indicates that the disk is full or your ulimit won't allow
3191 the file to be as large as it needs to be.
3193 This problem can also result because the kernel parameter @code{MAXUMEM}
3194 is too small. If so, you must regenerate the kernel and make the value
3195 much larger. The default value is reported to be 1024; a value of 32768
3196 is said to work. Smaller values may also work.
3198 On System V, if you get an error like this,
3201 /usr/local/lib/bison.simple: In function `yyparse':
3202 /usr/local/lib/bison.simple:625: virtual memory exhausted
3206 that too indicates a problem with disk space, ulimit, or @code{MAXUMEM}.
3208 On a System V release 4 system, make sure @file{/usr/bin} precedes
3209 @file{/usr/ucb} in @code{PATH}. The @code{cc} command in
3210 @file{/usr/ucb} uses libraries which have bugs.
3216 @heading @anchor{vax-dec-ultrix}vax-dec-ultrix
3217 Don't try compiling with VAX C (@code{vcc}). It produces incorrect code
3218 in some cases (for example, when @code{alloca} is used).
3224 @heading @anchor{we32k-*-*}we32k-*-*
3225 These computers are also known as the 3b2, 3b5, 3b20 and other similar
3226 names. (However, the 3b1 is actually a 68000.)
3228 Don't use @option{-g} when compiling with the system's compiler. The
3229 system's linker seems to be unable to handle such a large program with
3230 debugging information.
3232 The system's compiler runs out of capacity when compiling @file{stmt.c}
3233 in GCC@. You can work around this by building @file{cpp} in GCC
3234 first, then use that instead of the system's preprocessor with the
3235 system's C compiler to compile @file{stmt.c}. Here is how:
3238 mv /lib/cpp /lib/cpp.att
3240 echo '/lib/cpp.gnu -traditional $@{1+"$@@"@}' > /lib/cpp
3244 The system's compiler produces bad code for some of the GCC
3245 optimization files. So you must build the stage 2 compiler without
3246 optimization. Then build a stage 3 compiler with optimization.
3247 That executable should work. Here are the necessary commands:
3250 make LANGUAGES=c CC=stage1/xgcc CFLAGS="-Bstage1/ -g"
3252 make CC=stage2/xgcc CFLAGS="-Bstage2/ -g -O"
3255 You may need to raise the ULIMIT setting to build a C++ compiler,
3256 as the file @file{cc1plus} is larger than one megabyte.
3262 @heading @anchor{windows}Microsoft Windows (32 bit)
3264 A port of GCC 2.95.x is included with the
3265 @uref{http://www.cygwin.com/,,Cygwin environment}.
3267 Current (as of early 2001) snapshots of GCC will build under Cygwin
3268 without modification.
3274 @heading @anchor{os2}OS/2
3276 GCC does not currently support OS/2. However, Andrew Zabolotny has been
3277 working on a generic OS/2 port with pgcc. The current code code can be found
3278 at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
3280 An older copy of GCC 2.8.1 is included with the EMX tools available at
3281 @uref{ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/,,
3282 ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/}.
3288 @heading @anchor{older}Older systems
3290 GCC contains support files for many older (1980s and early
3291 1990s) Unix variants. For the most part, support for these systems
3292 has not been deliberately removed, but it has not been maintained for
3293 several years and may suffer from bitrot. Support from some systems
3294 has been removed from GCC 3: fx80, ns32-ns-genix, pyramid, tahoe,
3295 gmicro, spur; most of these targets had not been updated since GCC
3298 Support for older systems as targets for cross-compilation is less
3299 problematic than support for them as hosts for GCC; if an enthusiast
3300 wishes to make such a target work again (including resurrecting any
3301 of the targets that never worked with GCC 2, starting from the last
3302 CVS version before they were removed), patches
3303 @uref{../contribute.html,,following the usual requirements}
3304 would be likely to be accepted, since they should not affect the
3305 support for more modern targets.
3307 Support for old systems as hosts for GCC can cause problems if the
3308 workarounds for compiler, library and operating system bugs affect the
3309 cleanliness or maintainability of the rest of GCC@. In some cases, to
3310 bring GCC up on such a system, if still possible with current GCC, may
3311 require first installing an old version of GCC which did work on that
3312 system, and using it to compile a more recent GCC, to avoid bugs in
3313 the vendor compiler. Old releases of GCC 1 and GCC 2 are available in
3314 the @file{old-releases} directory on the
3315 @uref{../mirrors.html,,GCC mirror sites}. Header bugs may generally
3316 be avoided using @command{fixincludes}, but bugs or deficiencies in
3317 libraries and the operating system may still cause problems.
3319 For some systems, old versions of GNU binutils may also be useful,
3320 and are available from @file{pub/binutils/old-releases} on
3321 @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}.
3323 Some of the information on specific systems above relates to
3324 such older systems, but much of the information
3325 about GCC on such systems (which may no longer be applicable to
3326 current GCC) is to be found in the GCC texinfo manual.
3332 @heading @anchor{elf_targets}all ELF targets (SVR4, Solaris, etc.)
3334 C++ support is significantly better on ELF targets if you use the
3335 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
3336 inlines, vtables and template instantiations will be discarded
3346 @uref{./index.html,,Return to the GCC Installation page}
3350 @c ***************************************************************************
3351 @c Part 6 The End of the Document
3353 @comment node-name, next, previous, up
3354 @node Concept Index, , Specific, Top
3358 @unnumbered Concept Index