1 \input texinfo.tex @c -*-texinfo-*-
4 @setfilename gccinstall.info
5 @settitle Installing GCC
10 @c Specify title for specific html page
12 @settitle Installing GCC
15 @settitle Host/Target specific installation notes for GCC
18 @settitle Downloading GCC
21 @settitle Installing GCC: Configuration
24 @settitle Installing GCC: Building
27 @settitle Installing GCC: Testing
29 @ifset finalinstallhtml
30 @settitle Installing GCC: Final installation
33 @settitle Installing GCC: Binaries
36 @settitle Installing GCC: Old documentation
39 @settitle Installing GCC: GNU Free Documentation License
42 @c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
43 @c 1999, 2000, 2001, 2002 Free Software Foundation, Inc.
44 @c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com
46 @c Include everything if we're not making html
60 @c Part 2 Summary Description and Copyright
62 Copyright @copyright{} 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
63 1999, 2000, 2001, 2002, 2003 Free Software Foundation, Inc.
65 Permission is granted to copy, distribute and/or modify this document
66 under the terms of the GNU Free Documentation License, Version 1.2 or
67 any later version published by the Free Software Foundation; with no
68 Invariant Sections, the Front-Cover texts being (a) (see below), and
69 with the Back-Cover Texts being (b) (see below). A copy of the
70 license is included in the section entitled ``@uref{./gfdl.html,,GNU
71 Free Documentation License}''.
73 (a) The FSF's Front-Cover Text is:
77 (b) The FSF's Back-Cover Text is:
79 You have freedom to copy and modify this GNU Manual, like GNU
80 software. Copies published by the Free Software Foundation raise
81 funds for GNU development.
87 @c Part 3 Titlepage and Copyright
90 @comment The title is printed in a large font.
91 @center @titlefont{Installing GCC}
93 @c The following two commands start the copyright page.
95 @vskip 0pt plus 1filll
99 @c Part 4 Top node and Master Menu
102 @comment node-name, next, Previous, up
105 * Installing GCC:: This document describes the generic installation
106 procedure for GCC as well as detailing some target
107 specific installation instructions.
109 * Specific:: Host/target specific installation notes for GCC.
110 * Binaries:: Where to get pre-compiled binaries.
112 * Old:: Old installation documentation.
114 * GNU Free Documentation License:: How you can copy and share this manual.
115 * Concept Index:: This index has two entries.
119 @c Part 5 The Body of the Document
120 @c ***Installing GCC**********************************************************
122 @comment node-name, next, previous, up
123 @node Installing GCC, Binaries, , Top
127 @chapter Installing GCC
130 The latest version of this document is always available at
131 @uref{http://gcc.gnu.org/install/,,http://gcc.gnu.org/install/}.
133 This document describes the generic installation procedure for GCC as well
134 as detailing some target specific installation instructions.
136 GCC includes several components that previously were separate distributions
137 with their own installation instructions. This document supersedes all
138 package specific installation instructions.
140 @emph{Before} starting the build/install procedure please check the
142 @ref{Specific, host/target specific installation notes}.
145 @uref{specific.html,,host/target specific installation notes}.
147 We recommend you browse the entire generic installation instructions before
150 Lists of successful builds for released versions of GCC are
151 available at @uref{http://gcc.gnu.org/buildstat.html}.
152 These lists are updated as new information becomes available.
154 The installation procedure itself is broken into five steps.
158 * Downloading the source::
161 * Testing:: (optional)
168 @uref{download.html,,Downloading the source}
170 @uref{configure.html,,Configuration}
172 @uref{build.html,,Building}
174 @uref{test.html,,Testing} (optional)
176 @uref{finalinstall.html,,Final install}
180 Please note that GCC does not support @samp{make uninstall} and probably
181 won't do so in the near future as this would open a can of worms. Instead,
182 we suggest that you install GCC into a directory of its own and simply
183 remove that directory when you do not need that specific version of GCC
184 any longer, and, if shared libraries are installed there as well, no
185 more binaries exist that use them.
188 There are also some @uref{old.html,,old installation instructions},
189 which are mostly obsolete but still contain some information which has
190 not yet been merged into the main part of this manual.
198 @uref{./index.html,,Return to the GCC Installation page}
204 @c ***Downloading the source**************************************************
206 @comment node-name, next, previous, up
207 @node Downloading the source, Configuration, , Installing GCC
211 @chapter Downloading GCC
213 @cindex Downloading GCC
214 @cindex Downloading the Source
216 GCC is distributed via @uref{http://gcc.gnu.org/cvs.html,,CVS} and FTP
217 tarballs compressed with @command{gzip} or
218 @command{bzip2}. It is possible to download a full distribution or specific
221 Please refer to our @uref{http://gcc.gnu.org/releases.html,,releases web page}
222 for information on how to obtain GCC@.
224 The full distribution includes the C, C++, Objective-C, Fortran, Java,
225 and Ada (in case of GCC 3.1 and later) compilers. The full distribution
226 also includes runtime libraries for C++, Objective-C, Fortran, and Java.
227 In GCC 3.0 and later versions, GNU compiler testsuites are also included
228 in the full distribution.
230 If you choose to download specific components, you must download the core
231 GCC distribution plus any language specific distributions you wish to
232 use. The core distribution includes the C language front end as well as the
233 shared components. Each language has a tarball which includes the language
234 front end as well as the language runtime (when appropriate).
236 Unpack the core distribution as well as any language specific
237 distributions in the same directory.
239 If you also intend to build binutils (either to upgrade an existing
240 installation or for use in place of the corresponding tools of your
241 OS), unpack the binutils distribution either in the same directory or
242 a separate one. In the latter case, add symbolic links to any
243 components of the binutils you intend to build alongside the compiler
244 (@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
245 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
252 @uref{./index.html,,Return to the GCC Installation page}
256 @c ***Configuration***********************************************************
258 @comment node-name, next, previous, up
259 @node Configuration, Building, Downloading the source, Installing GCC
263 @chapter Installing GCC: Configuration
265 @cindex Configuration
266 @cindex Installing GCC: Configuration
268 Like most GNU software, GCC must be configured before it can be built.
269 This document describes the recommended configuration procedure
270 for both native and cross targets.
272 We use @var{srcdir} to refer to the toplevel source directory for
273 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
275 If you obtained the sources via CVS, @var{srcdir} must refer to the top
276 @file{gcc} directory, the one where the @file{MAINTAINERS} can be found,
277 and not its @file{gcc} subdirectory, otherwise the build will fail.
279 If either @var{srcdir} or @var{objdir} is located on an automounted NFS
280 file system, the shell's built-in @command{pwd} command will return
281 temporary pathnames. Using these can lead to various sorts of build
282 problems. To avoid this issue, set the @env{PWDCMD} environment
283 variable to an automounter-aware @command{pwd} command, e.g.,
284 @command{pawd} or @samp{amq -w}, during the configuration and build
287 First, we @strong{highly} recommend that GCC be built into a
288 separate directory than the sources which does @strong{not} reside
289 within the source tree. This is how we generally build GCC; building
290 where @var{srcdir} == @var{objdir} should still work, but doesn't
291 get extensive testing; building where @var{objdir} is a subdirectory
292 of @var{srcdir} is unsupported.
294 If you have previously built GCC in the same directory for a
295 different target machine, do @samp{make distclean} to delete all files
296 that might be invalid. One of the files this deletes is @file{Makefile};
297 if @samp{make distclean} complains that @file{Makefile} does not exist
298 or issues a message like ``don't know how to make distclean'' it probably
299 means that the directory is already suitably clean. However, with the
300 recommended method of building in a separate @var{objdir}, you should
301 simply use a different @var{objdir} for each target.
303 Second, when configuring a native system, either @command{cc} or
304 @command{gcc} must be in your path or you must set @env{CC} in
305 your environment before running configure. Otherwise the configuration
308 Note that the bootstrap compiler and the resulting GCC must be link
309 compatible, else the bootstrap will fail with linker errors about
310 incompatible object file formats. Several multilibed targets are
311 affected by this requirement, see
313 @ref{Specific, host/target specific installation notes}.
316 @uref{specific.html,,host/target specific installation notes}.
324 % @var{srcdir}/configure [@var{options}] [@var{target}]
328 @heading Target specification
331 GCC has code to correctly determine the correct value for @var{target}
332 for nearly all native systems. Therefore, we highly recommend you not
333 provide a configure target when configuring a native compiler.
336 @var{target} must be specified as @option{--target=@var{target}}
337 when configuring a cross compiler; examples of valid targets would be
338 i960-rtems, m68k-coff, sh-elf, etc.
341 Specifying just @var{target} instead of @option{--target=@var{target}}
342 implies that the host defaults to @var{target}.
346 @heading Options specification
348 Use @var{options} to override several configure time options for
349 GCC@. A list of supported @var{options} follows; @samp{configure
350 --help} may list other options, but those not listed below may not
351 work and should not normally be used.
354 @item --prefix=@var{dirname}
355 Specify the toplevel installation
356 directory. This is the recommended way to install the tools into a directory
357 other than the default. The toplevel installation directory defaults to
360 We @strong{highly} recommend against @var{dirname} being the same or a
361 subdirectory of @var{objdir} or vice versa. If specifying a directory
362 beneath a user's home directory tree, some shells will not expand
363 @var{dirname} correctly if it contains the @samp{~} metacharacter; use
366 These additional options control where certain parts of the distribution
367 are installed. Normally you should not need to use these options.
369 @item --exec-prefix=@var{dirname}
370 Specify the toplevel installation directory for architecture-dependent
371 files. The default is @file{@var{prefix}}.
373 @item --bindir=@var{dirname}
374 Specify the installation directory for the executables called by users
375 (such as @command{gcc} and @command{g++}). The default is
376 @file{@var{exec-prefix}/bin}.
378 @item --libdir=@var{dirname}
379 Specify the installation directory for object code libraries and
380 internal parts of GCC@. The default is @file{@var{exec-prefix}/lib}.
382 @item --with-slibdir=@var{dirname}
383 Specify the installation directory for the shared libgcc library. The
384 default is @file{@var{libdir}}.
386 @item --infodir=@var{dirname}
387 Specify the installation directory for documentation in info format.
388 The default is @file{@var{prefix}/info}.
390 @item --datadir=@var{dirname}
391 Specify the installation directory for some architecture-independent
392 data files referenced by GCC@. The default is @file{@var{prefix}/share}.
394 @item --mandir=@var{dirname}
395 Specify the installation directory for manual pages. The default is
396 @file{@var{prefix}/man}. (Note that the manual pages are only extracts from
397 the full GCC manuals, which are provided in Texinfo format. The
398 @command{g77} manpage is unmaintained and may be out of date; the others
399 are derived by an automatic conversion process from parts of the full
402 @item --with-gxx-include-dir=@var{dirname}
404 the installation directory for G++ header files. The default is
405 @file{@var{prefix}/include/g++-v3}.
409 @item --program-prefix=@var{prefix}
410 GCC supports some transformations of the names of its programs when
411 installing them. This option prepends @var{prefix} to the names of
412 programs to install in @var{bindir} (see above). For example, specifying
413 @option{--program-prefix=foo-} would result in @samp{gcc}
414 being installed as @file{/usr/local/bin/foo-gcc}.
416 @item --program-suffix=@var{suffix}
417 Appends @var{suffix} to the names of programs to install in @var{bindir}
418 (see above). For example, specifying @option{--program-suffix=-3.1}
419 would result in @samp{gcc} being installed as
420 @file{/usr/local/bin/gcc-3.1}.
422 @item --program-transform-name=@var{pattern}
423 Applies the @samp{sed} script @var{pattern} to be applied to the names
424 of programs to install in @var{bindir} (see above). @var{pattern} has to
425 consist of one or more basic @samp{sed} editing commands, separated by
426 semicolons. For example, if you want the @samp{gcc} program name to be
427 transformed to the installed program @file{/usr/local/bin/myowngcc} and
428 the @samp{g++} program name to be transformed to
429 @file{/usr/local/bin/gspecial++} without changing other program names,
430 you could use the pattern
431 @option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}
432 to achieve this effect.
434 All three options can be combined and used together, resulting in more
435 complex conversion patterns. As a basic rule, @var{prefix} (and
436 @var{suffix}) are prepended (appended) before further transformations
437 can happen with a special transformation script @var{pattern}.
439 As currently implemented, this option only takes effect for native
440 builds; cross compiler binaries' names are not transformed even when a
441 transformation is explicitly asked for by one of these options.
443 For native builds, some of the installed programs are also installed
444 with the target alias in front of their name, as in
445 @samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
446 before the target alias is prepended to the name - so, specifying
447 @option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
448 resulting binary would be installed as
449 @file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.
451 As a last shortcoming, none of the installed Ada programs are
452 transformed yet, which will be fixed in some time.
454 @item --with-local-prefix=@var{dirname}
456 installation directory for local include files. The default is
457 @file{/usr/local}. Specify this option if you want the compiler to
458 search directory @file{@var{dirname}/include} for locally installed
459 header files @emph{instead} of @file{/usr/local/include}.
461 You should specify @option{--with-local-prefix} @strong{only} if your
462 site has a different convention (not @file{/usr/local}) for where to put
465 The default value for @option{--with-local-prefix} is @file{/usr/local}
466 regardless of the value of @option{--prefix}. Specifying
467 @option{--prefix} has no effect on which directory GCC searches for
468 local header files. This may seem counterintuitive, but actually it is
471 The purpose of @option{--prefix} is to specify where to @emph{install
472 GCC}. The local header files in @file{/usr/local/include}---if you put
473 any in that directory---are not part of GCC@. They are part of other
474 programs---perhaps many others. (GCC installs its own header files in
475 another directory which is based on the @option{--prefix} value.)
477 Both the local-prefix include directory and the GCC-prefix include
478 directory are part of GCC's "system include" directories. Although these
479 two directories are not fixed, they need to be searched in the proper
480 order for the correct processing of the include_next directive. The
481 local-prefix include directory is searched before the GCC-prefix
482 include directory. Another characteristic of system include directories
483 is that pedantic warnings are turned off for headers in these directories.
485 Some autoconf macros add @option{-I @var{directory}} options to the
486 compiler command line, to ensure that directories containing installed
487 packages' headers are searched. When @var{directory} is one of GCC's
488 system include directories, GCC will ignore the option so that system
489 directories continue to be processed in the correct order. This
490 may result in a search order different from what was specified but the
491 directory will still be searched.
493 GCC automatically searches for ordinary libraries using
494 @env{GCC_EXEC_PREFIX}. Thus, when the same installation prefix is
495 used for both GCC and packages, GCC will automatically search for
496 both headers and libraries. This provides a configuration that is
497 easy to use. GCC behaves in a manner similar to that when it is
498 installed as a system compiler in @file{/usr}.
500 Sites that need to install multiple versions of GCC may not want to
501 use the above simple configuration. It is possible to use the
502 @option{--program-prefix}, @option{--program-suffix} and
503 @option{--program-transform-name} options to install multiple versions
504 into a single directory, but it may be simpler to use different prefixes
505 and the @option{--with-local-prefix} option to specify the location of the
506 site-specific files for each version. It will then be necessary for
507 users to specify explicitly the location of local site libraries
508 (e.g., with @env{LIBRARY_PATH}).
510 The same value can be used for both @option{--with-local-prefix} and
511 @option{--prefix} provided it is not @file{/usr}. This can be used
512 to avoid the default search of @file{/usr/local/include}.
514 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
515 The directory you use for @option{--with-local-prefix} @strong{must not}
516 contain any of the system's standard header files. If it did contain
517 them, certain programs would be miscompiled (including GNU Emacs, on
518 certain targets), because this would override and nullify the header
519 file corrections made by the @command{fixincludes} script.
521 Indications are that people who use this option use it based on mistaken
522 ideas of what it is for. People use it as if it specified where to
523 install part of GCC@. Perhaps they make this assumption because
524 installing GCC creates the directory.
526 @item --enable-shared[=@var{package}[,@dots{}]]
527 Build shared versions of libraries, if shared libraries are supported on
528 the target platform. Unlike GCC 2.95.x and earlier, shared libraries
529 are enabled by default on all platforms that support shared libraries,
530 except for @samp{libobjc} which is built as a static library only by
533 If a list of packages is given as an argument, build shared libraries
534 only for the listed packages. For other packages, only static libraries
535 will be built. Package names currently recognized in the GCC tree are
536 @samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
537 @samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc} and
538 @samp{libjava}. Note that @samp{libobjc} does not recognize itself by
539 any name, so, if you list package names in @option{--enable-shared},
540 you will only get static Objective-C libraries. @samp{libf2c} and
541 @samp{libiberty} do not support shared libraries at all.
543 Use @option{--disable-shared} to build only static libraries. Note that
544 @option{--disable-shared} does not accept a list of package names as
545 argument, only @option{--enable-shared} does.
547 @item @anchor{with-gnu-as}--with-gnu-as
548 Specify that the compiler should assume that the
549 assembler it finds is the GNU assembler. However, this does not modify
550 the rules to find an assembler and will result in confusion if the
551 assembler found is not actually the GNU assembler. (Confusion may also
552 result if the compiler finds the GNU assembler but has not been
553 configured with @option{--with-gnu-as}.) If you have more than one
554 assembler installed on your system, you may want to use this option in
555 connection with @option{--with-as=@var{pathname}}.
557 The following systems are the only ones where it makes a difference
558 whether you use the GNU assembler. On any other system,
559 @option{--with-gnu-as} has no effect.
562 @item @samp{hppa1.0-@var{any}-@var{any}}
563 @item @samp{hppa1.1-@var{any}-@var{any}}
564 @item @samp{i386-@var{any}-sysv}
565 @item @samp{m68k-bull-sysv}
566 @item @samp{m68k-hp-hpux}
567 @item @samp{m68000-hp-hpux}
568 @item @samp{m68000-att-sysv}
569 @item @samp{@var{any}-lynx-lynxos}
570 @item @samp{mips-@var{any}}
573 On the systems listed above (except for the HP-PA, for ISC on the
574 386, and for @samp{mips-sgi-irix5.*}), if you use the GNU assembler,
575 you should also use the GNU linker (and specify @option{--with-gnu-ld}).
577 @item --with-as=@var{pathname}
579 compiler should use the assembler pointed to by @var{pathname}, rather
580 than the one found by the standard rules to find an assembler, which
585 @file{@var{exec_prefix}/lib/gcc-lib/@var{target}/@var{version}}
586 directory, where @var{exec_prefix} defaults to @var{prefix} which
587 defaults to @file{/usr/local} unless overridden by the
588 @option{--prefix=@var{pathname}} switch described above. @var{target} is the
589 target system triple, such as @samp{sparc-sun-solaris2.7}, and
590 @var{version} denotes the GCC version, such as 3.0.
592 Check operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
595 Note that these rules do not check for the value of @env{PATH}. You may
596 want to use @option{--with-as} if no assembler is installed in the
597 directories listed above, or if you have multiple assemblers installed
598 and want to choose one that is not found by the above rules.
600 @item @anchor{with-gnu-ld}--with-gnu-ld
601 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
605 @item --with-ld=@var{pathname}
607 @option{--with-as}, but for the linker.
610 Specify that stabs debugging
611 information should be used instead of whatever format the host normally
612 uses. Normally GCC uses the same debug format as the host system.
614 On MIPS based systems and on Alphas, you must specify whether you want
615 GCC to create the normal ECOFF debugging format, or to use BSD-style
616 stabs passed through the ECOFF symbol table. The normal ECOFF debug
617 format cannot fully handle languages other than C@. BSD stabs format can
618 handle other languages, but it only works with the GNU debugger GDB@.
620 Normally, GCC uses the ECOFF debugging format by default; if you
621 prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
623 No matter which default you choose when you configure GCC, the user
624 can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
625 the debug format for a particular compilation.
627 @option{--with-stabs} is meaningful on the ISC system on the 386, also, if
628 @option{--with-gas} is used. It selects use of stabs debugging
629 information embedded in COFF output. This kind of debugging information
630 supports C++ well; ordinary COFF debugging information does not.
632 @option{--with-stabs} is also meaningful on 386 systems running SVR4. It
633 selects use of stabs debugging information embedded in ELF output. The
634 C++ compiler currently (2.6.0) does not support the DWARF debugging
635 information normally used on 386 SVR4 platforms; stabs provide a
636 workable alternative. This requires gas and gdb, as the normal SVR4
637 tools can not generate or interpret stabs.
639 @item --disable-multilib
640 Specify that multiple target
641 libraries to support different target variants, calling
642 conventions, etc should not be built. The default is to build a
643 predefined set of them.
645 Some targets provide finer-grained control over which multilibs are built
646 (e.g., @option{--disable-softfloat}):
652 fpu, 26bit, underscore, interwork, biendian, nofmult.
655 softfloat, m68881, m68000, m68020.
658 single-float, biendian, softfloat.
660 @item powerpc*-*-*, rs6000*-*-*
661 aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
666 @item --enable-threads
667 Specify that the target
668 supports threads. This affects the Objective-C compiler and runtime
669 library, and exception handling for other languages like C++ and Java.
670 On some systems, this is the default.
672 In general, the best (and, in many cases, the only known) threading
673 model available will be configured for use. Beware that on some
674 systems, gcc has not been taught what threading models are generally
675 available for the system. In this case, @option{--enable-threads} is an
676 alias for @option{--enable-threads=single}.
678 @item --disable-threads
679 Specify that threading support should be disabled for the system.
680 This is an alias for @option{--enable-threads=single}.
682 @item --enable-threads=@var{lib}
684 @var{lib} is the thread support library. This affects the Objective-C
685 compiler and runtime library, and exception handling for other languages
686 like C++ and Java. The possibilities for @var{lib} are:
694 Ada tasking support. For non-Ada programs, this setting is equivalent
695 to @samp{single}. When used in conjunction with the Ada run time, it
696 causes GCC to use the same thread primitives as Ada uses. This option
697 is necessary when using both Ada and the back end exception handling,
698 which is the default for most Ada targets.
700 Generic MACH thread support, known to work on NeXTSTEP@. (Please note
701 that the file needed to support this configuration, @file{gthr-mach.h}, is
702 missing and thus this setting will cause a known bootstrap failure.)
704 This is an alias for @samp{single}.
706 Generic POSIX thread support.
708 Same as @samp{posix} on arm*-*-linux*, *-*-chorusos* and *-*-freebsd*
709 only. A future release of gcc might remove this alias or extend it
712 RTEMS thread support.
714 Disable thread support, should work for all platforms.
716 Sun Solaris 2 thread support.
718 VxWorks thread support.
720 Microsoft Win32 API thread support.
723 @item --with-cpu=@var{cpu}
724 Specify which cpu variant the compiler should generate code for by default.
725 @var{cpu} will be used as the default value of the @option{-mcpu=} switch.
726 This option is only supported on some targets, including ARM, i386, PowerPC,
729 @item --with-schedule=@var{cpu}
730 @itemx --with-arch=@var{cpu}
731 @itemx --with-tune=@var{cpu}
732 @itemx --with-abi=@var{abi}
733 @itemx --with-float=@var{type}
734 These configure options provide default values for the @option{-mschedule=},
735 @option{-march=}, @option{-mtune=}, and @option{-mabi=} options and for
736 @option{-mhard-float} or @option{-msoft-float}. As with @option{--with-cpu},
737 which switches will be accepted and acceptable values of the arguments depend
740 @item --enable-altivec
741 Specify that the target supports AltiVec vector enhancements. This
742 option will adjust the ABI for AltiVec enhancements, as well as generate
743 AltiVec code when appropriate. This option is only available for
746 @item --enable-target-optspace
748 libraries should be optimized for code space instead of code speed.
749 This is the default for the m32r platform.
752 Specify that a user visible @command{cpp} program should not be installed.
754 @item --with-cpp-install-dir=@var{dirname}
755 Specify that the user visible @command{cpp} program should be installed
756 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
758 @item --enable-initfini-array
759 Force the use of sections @code{.init_array} and @code{.fini_array}
760 (instead of @code{.init} and @code{.fini}) for constructors and
761 destructors. Option @option{--disable-initfini-array} has the
762 opposite effect. If neither option is specified, the configure script
763 will try to guess whether the @code{.init_array} and
764 @code{.fini_array} sections are supported and, if they are, use them.
766 @item --enable-maintainer-mode
768 regenerate the GCC master message catalog @file{gcc.pot} are normally
769 disabled. This is because it can only be rebuilt if the complete source
770 tree is present. If you have changed the sources and want to rebuild the
771 catalog, configuring with @option{--enable-maintainer-mode} will enable
772 this. Note that you need a recent version of the @code{gettext} tools
775 @item --enable-version-specific-runtime-libs
777 that runtime libraries should be installed in the compiler specific
778 subdirectory (@file{@var{libsubdir}}) rather than the usual places. In
779 addition, @samp{libstdc++}'s include files will be installed in
780 @file{@var{libsubdir}/include/g++} unless you overruled it by using
781 @option{--with-gxx-include-dir=@var{dirname}}. Using this option is
782 particularly useful if you intend to use several versions of GCC in
783 parallel. This is currently supported by @samp{libf2c} and
784 @samp{libstdc++}, and is the default for @samp{libobjc} which cannot be
785 changed in this case.
787 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
788 Specify that only a particular subset of compilers and
789 their runtime libraries should be built. For a list of valid values for
790 @var{langN} you can issue the following command in the
791 @file{gcc} directory of your GCC source tree:@*
793 grep language= */config-lang.in
795 Currently, you can use any of the following:
796 @code{ada}, @code{c}, @code{c++}, @code{f77}, @code{java}, @code{objc}.
797 Building the Ada compiler has special requirements, see below.@*
798 If you do not pass this flag, all languages available in the @file{gcc}
799 sub-tree will be configured. Re-defining @code{LANGUAGES} when calling
800 @samp{make bootstrap} @strong{does not} work anymore, as those
801 language sub-directories might not have been configured!
803 @item --disable-libgcj
804 Specify that the run-time libraries
805 used by GCJ should not be built. This is useful in case you intend
806 to use GCJ with some other run-time, or you're going to install it
807 separately, or it just happens not to build on your particular
808 machine. In general, if the Java front end is enabled, the GCJ
809 libraries will be enabled too, unless they're known to not work on
810 the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
811 may need to port it; in this case, before modifying the top-level
812 @file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
813 you may use @option{--enable-libgcj} to override the default.
816 Specify that the compiler should
817 use DWARF 2 debugging information as the default.
819 @item --enable-win32-registry
820 @itemx --enable-win32-registry=@var{key}
821 @itemx --disable-win32-registry
822 The @option{--enable-win32-registry} option enables Windows-hosted GCC
823 to look up installations paths in the registry using the following key:
826 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
829 @var{key} defaults to GCC version number, and can be overridden by the
830 @option{--enable-win32-registry=@var{key}} option. Vendors and distributors
831 who use custom installers are encouraged to provide a different key,
832 perhaps one comprised of vendor name and GCC version number, to
833 avoid conflict with existing installations. This feature is enabled
834 by default, and can be disabled by @option{--disable-win32-registry}
835 option. This option has no effect on the other hosts.
838 Specify that the machine does not have a floating point unit. This
839 option only applies to @samp{m68k-sun-sunos@var{n}}. On any other
840 system, @option{--nfp} has no effect.
842 @item --enable-werror
843 @itemx --disable-werror
844 @itemx --enable-werror=yes
845 @itemx --enable-werror=no
846 When you specify this option, it controls whether certain files in the
847 compiler are built with @option{-Werror} in bootstrap stage2 and later.
848 If you don't specify it, @option{-Werror} is turned on for the main
849 development trunk. However it defaults to off for release branches and
850 final releases. The specific files which get @option{-Werror} are
851 controlled by the Makefiles.
853 @item --enable-checking
854 @itemx --enable-checking=@var{list}
855 When you specify this option, the compiler is built to perform checking
856 of tree node types when referencing fields of that node, and some other
857 internal consistency checks. This does not change the generated code,
858 but adds error checking within the compiler. This will slow down the
859 compiler and may only work properly if you are building the compiler
860 with GCC@. This is on by default when building from CVS or snapshots,
861 but off for releases. More control over the checks may be had by
862 specifying @var{list}; the categories of checks available are
863 @samp{misc}, @samp{tree}, @samp{gc}, @samp{rtl}, @samp{rtlflag} and
865 default when @var{list} is not specified is @samp{misc,tree,gc,rtlflag}; the
866 checks @samp{rtl} and @samp{gcac} are very expensive.
868 @item --enable-coverage
869 @item --enable-coverage=@var{level}
870 With this option, the compiler is built to collect self coverage
871 information, every time it is run. This is for internal development
872 purposes, and only works when the compiler is being built with gcc. The
873 @var{level} argument controls whether the compiler is built optimized or
874 not, values are @samp{opt} and @samp{noopt}. For coverage analysis you
875 want to disable optimization, for performance analysis you want to
876 enable optimization. When coverage is enabled, the default level is
877 without optimization.
881 The @option{--enable-nls} option enables Native Language Support (NLS),
882 which lets GCC output diagnostics in languages other than American
883 English. Native Language Support is enabled by default if not doing a
884 canadian cross build. The @option{--disable-nls} option disables NLS@.
886 @item --with-included-gettext
887 If NLS is enabled, the @option{--with-included-gettext} option causes the build
888 procedure to prefer its copy of GNU @command{gettext}.
891 If NLS is enabled, and if the host lacks @code{gettext} but has the
892 inferior @code{catgets} interface, the GCC build procedure normally
893 ignores @code{catgets} and instead uses GCC's copy of the GNU
894 @code{gettext} library. The @option{--with-catgets} option causes the
895 build procedure to use the host's @code{catgets} in this situation.
897 @item --with-libiconv-prefix=@var{dir}
898 Search for libiconv header files in @file{@var{dir}/include} and
899 libiconv library files in @file{@var{dir}/lib}.
901 @item --with-system-zlib
902 Use installed zlib rather than that included with GCC@. This option
903 only applies if the Java front end is being built.
905 @item --enable-obsolete
906 Enable configuration for an obsoleted system. If you attempt to
907 configure GCC for a system (build, host, or target) which has been
908 obsoleted, and you do not specify this flag, configure will halt with an
911 All support for systems which have been obsoleted in one release of GCC
912 is removed entirely in the next major release, unless someone steps
913 forward to maintain the port.
916 Some options which only apply to building cross compilers:
919 @itemx --with-sysroot=@var{dir}
920 Tells GCC to consider @var{dir} as the root of a tree that contains a
921 (subset of) the root filesystem of the target operating system.
922 Target system headers, libraries and run-time object files will be
923 searched in there. The specified directory is not copied into the
924 install tree, unlike the options @option{--with-headers} and
925 @option{--with-libs} that this option obsoletes. The default value,
926 in case @option{--with-sysroot} is not given an argument, is
927 @option{$@{gcc_tooldir@}/sys-root}. If the specified directory is a
928 subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to
929 the GCC binaries if the installation tree is moved.
932 @itemx --with-headers=@var{dir}
933 Deprecated in favor of @option{--with-sysroot}.
934 Specifies that target headers are available when building a cross compiler.
935 The @var{dir} argument specifies a directory which has the target include
936 files. These include files will be copied into the @file{gcc} install
937 directory. @emph{This option with the @var{dir} argument is required} when
938 building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include}
939 doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does
940 pre-exist, the @var{dir} argument may be omitted. @command{fixincludes}
941 will be run on these files to make them compatible with GCC.
943 @itemx --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
944 Deprecated in favor of @option{--with-sysroot}.
945 Specifies a list of directories which contain the target runtime
946 libraries. These libraries will be copied into the @file{gcc} install
947 directory. If the directory list is omitted, this option has no
950 Specifies that @samp{newlib} is
951 being used as the target C library. This causes @code{__eprintf} to be
952 omitted from @file{libgcc.a} on the assumption that it will be provided by
956 Note that each @option{--enable} option has a corresponding
957 @option{--disable} option and that each @option{--with} option has a
958 corresponding @option{--without} option.
965 @uref{./index.html,,Return to the GCC Installation page}
969 @c ***Building****************************************************************
971 @comment node-name, next, previous, up
972 @node Building, Testing, Configuration, Installing GCC
978 @cindex Installing GCC: Building
980 Now that GCC is configured, you are ready to build the compiler and
983 We @strong{highly} recommend that GCC be built using GNU make;
984 other versions may work, then again they might not.
985 GNU make is required for compiling GNAT (the Ada compiler) and the Java
988 (For example, many broken versions of make will fail if you use the
989 recommended setup where @var{objdir} is different from @var{srcdir}.
990 Other broken versions may recompile parts of the compiler when
991 installing the compiler.)
993 Some commands executed when making the compiler may fail (return a
994 nonzero status) and be ignored by @command{make}. These failures, which
995 are often due to files that were not found, are expected, and can safely
998 It is normal to have compiler warnings when compiling certain files.
999 Unless you are a GCC developer, you can generally ignore these warnings
1000 unless they cause compilation to fail. Developers should attempt to fix
1001 any warnings encountered, however they can temporarily continue past
1002 warnings-as-errors by specifying the configure flag
1003 @option{--disable-werror}.
1005 On certain old systems, defining certain environment variables such as
1006 @env{CC} can interfere with the functioning of @command{make}.
1008 If you encounter seemingly strange errors when trying to build the
1009 compiler in a directory other than the source directory, it could be
1010 because you have previously configured the compiler in the source
1011 directory. Make sure you have done all the necessary preparations.
1013 If you build GCC on a BSD system using a directory stored in an old System
1014 V file system, problems may occur in running @command{fixincludes} if the
1015 System V file system doesn't support symbolic links. These problems
1016 result in a failure to fix the declaration of @code{size_t} in
1017 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
1018 that type mismatches occur, this could be the cause.
1020 The solution is not to use such a directory for building GCC@.
1022 When building from CVS or snapshots, or if you modify parser sources,
1023 you need the Bison parser generator installed. Any version 1.25 or
1024 later should work; older versions may also work. If you do not modify
1025 parser sources, releases contain the Bison-generated files and you do
1026 not need Bison installed to build them.
1028 When building from CVS or snapshots, or if you modify Texinfo
1029 documentation, you need version 4.2 or later of Texinfo installed if you
1030 want Info documentation to be regenerated. Releases contain Info
1031 documentation pre-built for the unmodified documentation in the release.
1033 @section Building a native compiler
1035 For a native build issue the command @samp{make bootstrap}. This
1036 will build the entire GCC system, which includes the following steps:
1040 Build host tools necessary to build the compiler such as texinfo, bison,
1044 Build target tools for use by the compiler such as binutils (bfd,
1045 binutils, gas, gprof, ld, and opcodes)
1046 if they have been individually linked
1047 or moved into the top level GCC source tree before configuring.
1050 Perform a 3-stage bootstrap of the compiler.
1053 Perform a comparison test of the stage2 and stage3 compilers.
1056 Build runtime libraries using the stage3 compiler from the previous step.
1060 If you are short on disk space you might consider @samp{make
1061 bootstrap-lean} instead. This is identical to @samp{make
1062 bootstrap} except that object files from the stage1 and
1063 stage2 of the 3-stage bootstrap of the compiler are deleted as
1064 soon as they are no longer needed.
1066 If you want to save additional space during the bootstrap and in
1067 the final installation as well, you can build the compiler binaries
1068 without debugging information as in the following example. This will save
1069 roughly 40% of disk space both for the bootstrap and the final installation.
1070 (Libraries will still contain debugging information.)
1073 make CFLAGS='-O' LIBCFLAGS='-g -O2' \
1074 LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap
1077 If you wish to use non-default GCC flags when compiling the stage2 and
1078 stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing
1079 @samp{make bootstrap}. Non-default optimization flags are less well
1080 tested here than the default of @samp{-g -O2}, but should still work.
1081 In a few cases, you may find that you need to specify special flags such
1082 as @option{-msoft-float} here to complete the bootstrap; or, if the
1083 native compiler miscompiles the stage1 compiler, you may need to work
1084 around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the
1085 stage1 compiler that were miscompiled, or by using @samp{make
1086 bootstrap4} to increase the number of stages of bootstrap.
1088 If you used the flag @option{--enable-languages=@dots{}} to restrict
1089 the compilers to be built, only those you've actually enabled will be
1090 built. This will of course only build those runtime libraries, for
1091 which the particular compiler has been built. Please note,
1092 that re-defining @env{LANGUAGES} when calling @samp{make bootstrap}
1093 @strong{does not} work anymore!
1095 If the comparison of stage2 and stage3 fails, this normally indicates
1096 that the stage2 compiler has compiled GCC incorrectly, and is therefore
1097 a potentially serious bug which you should investigate and report. (On
1098 a few systems, meaningful comparison of object files is impossible; they
1099 always appear ``different''. If you encounter this problem, you will
1100 need to disable comparison in the @file{Makefile}.)
1102 @section Building a cross compiler
1104 We recommend reading the
1105 @uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ}
1106 for information about building cross compilers.
1108 When building a cross compiler, it is not generally possible to do a
1109 3-stage bootstrap of the compiler. This makes for an interesting problem
1110 as parts of GCC can only be built with GCC@.
1112 To build a cross compiler, we first recommend building and installing a
1113 native compiler. You can then use the native GCC compiler to build the
1114 cross compiler. The installed native compiler needs to be GCC version
1117 Assuming you have already installed a native copy of GCC and configured
1118 your cross compiler, issue the command @command{make}, which performs the
1123 Build host tools necessary to build the compiler such as texinfo, bison,
1127 Build target tools for use by the compiler such as binutils (bfd,
1128 binutils, gas, gprof, ld, and opcodes)
1129 if they have been individually linked or moved into the top level GCC source
1130 tree before configuring.
1133 Build the compiler (single stage only).
1136 Build runtime libraries using the compiler from the previous step.
1139 Note that if an error occurs in any step the make process will exit.
1141 @section Building in parallel
1143 If you have a multiprocessor system you can use @samp{make bootstrap
1144 MAKE="make -j 2" -j 2} or just @samp{make -j 2 bootstrap}
1145 for GNU Make 3.79 and above instead of just @samp{make bootstrap}
1146 when building GCC@. You can use a bigger number instead of two if
1147 you like. In most cases, it won't help to use a number bigger than
1148 the number of processors in your machine.
1150 @section Building the Ada compiler
1152 In order to build GNAT, the Ada compiler, you need a working GNAT
1153 compiler (GNAT version 3.14 or later, or GCC version 3.1 or later),
1154 since the Ada front end is written in Ada (with some
1155 GNAT-specific extensions), and GNU make.
1157 However, you do not need a full installation of GNAT, just the GNAT
1158 binary @file{gnat1}, a copy of @file{gnatbind}, and a compiler driver
1159 which can deal with Ada input (by invoking the @file{gnat1} binary).
1160 You can specify this compiler driver by setting the @env{ADAC}
1161 environment variable at the configure step. @command{configure} can
1162 detect the driver automatically if it has got a common name such as
1163 @command{gcc} or @command{gnatgcc}. Of course, you still need a working
1164 C compiler (the compiler driver can be different or not).
1165 @command{configure} does not test whether the GNAT installation works
1166 and has a sufficiently recent version; if too old a GNAT version is
1167 installed, the build will fail unless @option{--enable-languages} is
1168 used to disable building the Ada front end.
1170 Additional build tools (such as @command{gnatmake}) or a working GNAT
1171 run-time library installation are usually @emph{not} required. However,
1172 if you want to bootstrap the compiler using a minimal version of GNAT,
1173 you have to issue the following commands before invoking @samp{make
1174 bootstrap} (this assumes that you start with an unmodified and consistent
1175 source distribution):
1178 cd @var{srcdir}/gcc/ada
1179 touch treeprs.ads [es]info.h nmake.ad[bs]
1182 At the moment, the GNAT library and several tools for GNAT are not built
1183 by @samp{make bootstrap}. You have to invoke
1184 @samp{make gnatlib_and_tools} in the @file{@var{objdir}/gcc}
1185 subdirectory before proceeding with the next steps.
1187 For example, you can build a native Ada compiler by issuing the
1188 following commands (assuming @command{make} is GNU make):
1192 @var{srcdir}/configure --enable-languages=c,ada
1193 cd @var{srcdir}/gcc/ada
1194 touch treeprs.ads [es]info.h nmake.ad[bs]
1198 make gnatlib_and_tools
1202 Currently, when compiling the Ada front end, you cannot use the parallel
1203 build feature described in the previous section.
1205 @section Building with profile feedback
1207 It is possible to use profile feedback to optimize the compiler itself. This
1208 should result in a faster compiler binary. Experiments done on x86 using gcc
1209 3.3 showed approximately 7 percent speedup on compiling C programs. To
1210 bootstrap compiler with profile feedback, use @code{make profiledbootstrap}.
1212 When @samp{make profiledbootstrap} is run, it will first build a @code{stage1}
1213 compiler. This compiler is used to build a @code{stageprofile} compiler
1214 instrumented to collect execution counts of instruction and branch
1215 probabilities. Then runtime libraries are compiled with profile collected.
1216 Finally a @code{stagefeedback} compiler is built using the information collected.
1218 Unlike @samp{make bootstrap} several additional restrictions apply. The
1219 compiler used to build @code{stage1} needs to support a 64-bit integral type.
1220 It is recommended to only use GCC for this. Also parallel make is currently
1221 not supported since collisions in profile collecting may occur.
1228 @uref{./index.html,,Return to the GCC Installation page}
1232 @c ***Testing*****************************************************************
1234 @comment node-name, next, previous, up
1235 @node Testing, Final install, Building, Installing GCC
1239 @chapter Installing GCC: Testing
1242 @cindex Installing GCC: Testing
1245 Before you install GCC, we encourage you to run the testsuites and to
1246 compare your results with results from a similar configuration that have
1247 been submitted to the
1248 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
1249 Some of these archived results are linked from the build status lists
1250 at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who
1251 reports a successful build runs the testsuites and submits the results.
1252 This step is optional and may require you to download additional software,
1253 but it can give you confidence in your new GCC installation or point out
1254 problems before you install and start using your new GCC.
1256 First, you must have @uref{download.html,,downloaded the testsuites}.
1257 These are part of the full distribution, but if you downloaded the
1258 ``core'' compiler plus any front ends, you must download the testsuites
1261 Second, you must have the testing tools installed. This includes
1262 @uref{http://www.gnu.org/software/dejagnu/,,DejaGnu} 1.4.2 (or later),
1263 Tcl, and Expect; the DejaGnu site has links to these.
1265 If the directories where @command{runtest} and @command{expect} were
1266 installed are not in the @env{PATH}, you may need to set the following
1267 environment variables appropriately, as in the following example (which
1268 assumes that DejaGnu has been installed under @file{/usr/local}):
1271 TCL_LIBRARY = /usr/local/share/tcl8.0
1272 DEJAGNULIBS = /usr/local/share/dejagnu
1275 (On systems such as Cygwin, these paths are required to be actual
1276 paths, not mounts or links; presumably this is due to some lack of
1277 portability in the DejaGnu code.)
1280 Finally, you can run the testsuite (which may take a long time):
1282 cd @var{objdir}; make -k check
1285 This will test various components of GCC, such as compiler
1286 front ends and runtime libraries. While running the testsuite, DejaGnu
1287 might emit some harmless messages resembling
1288 @samp{WARNING: Couldn't find the global config file.} or
1289 @samp{WARNING: Couldn't find tool init file} that can be ignored.
1291 @section How can I run the test suite on selected tests?
1293 In order to run sets of tests selectively, there are targets
1294 @samp{make check-gcc} and @samp{make check-g++}
1295 in the @file{gcc} subdirectory of the object directory. You can also
1296 just run @samp{make check} in a subdirectory of the object directory.
1299 A more selective way to just run all @command{gcc} execute tests in the
1303 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
1306 Likewise, in order to run only the @command{g++} ``old-deja'' tests in
1307 the testsuite with filenames matching @samp{9805*}, you would use
1310 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
1313 The @file{*.exp} files are located in the testsuite directories of the GCC
1314 source, the most important ones being @file{compile.exp},
1315 @file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
1316 To get a list of the possible @file{*.exp} files, pipe the
1317 output of @samp{make check} into a file and look at the
1318 @samp{Running @dots{} .exp} lines.
1321 @section Additional testing for Java Class Libraries
1323 The @uref{http://sources.redhat.com/mauve/,,Mauve Project} provides
1324 a suite of tests for the Java Class Libraries. This suite can be run
1325 as part of libgcj testing by placing the Mauve tree within the libjava
1326 testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by
1327 specifying the location of that tree when invoking @samp{make}, as in
1328 @samp{make MAUVEDIR=~/mauve check}.
1330 @uref{http://www-124.ibm.com/developerworks/oss/cvs/jikes/~checkout~/jacks/jacks.html,,Jacks}
1331 is a free test suite that tests Java compiler front ends. This suite
1332 can be run as part of libgcj testing by placing the Jacks tree within
1333 the libjava testsuite at @file{libjava/testsuite/libjava.jacks/jacks}.
1335 @section How to interpret test results
1337 The result of running the testsuite are various @file{*.sum} and @file{*.log}
1338 files in the testsuite subdirectories. The @file{*.log} files contain a
1339 detailed log of the compiler invocations and the corresponding
1340 results, the @file{*.sum} files summarize the results. These summaries
1341 contain status codes for all tests:
1345 PASS: the test passed as expected
1347 XPASS: the test unexpectedly passed
1349 FAIL: the test unexpectedly failed
1351 XFAIL: the test failed as expected
1353 UNSUPPORTED: the test is not supported on this platform
1355 ERROR: the testsuite detected an error
1357 WARNING: the testsuite detected a possible problem
1360 It is normal for some tests to report unexpected failures. At the
1361 current time our testing harness does not allow fine grained control
1362 over whether or not a test is expected to fail. We expect to fix this
1363 problem in future releases.
1366 @section Submitting test results
1368 If you want to report the results to the GCC project, use the
1369 @file{contrib/test_summary} shell script. Start it in the @var{objdir} with
1372 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
1373 -m gcc-testresults@@gcc.gnu.org |sh
1376 This script uses the @command{Mail} program to send the results, so
1377 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
1378 prepended to the testsuite summary and should contain any special
1379 remarks you have on your results or your build environment. Please
1380 do not edit the testsuite result block or the subject line, as these
1381 messages may be automatically processed.
1388 @uref{./index.html,,Return to the GCC Installation page}
1392 @c ***Final install***********************************************************
1394 @comment node-name, next, previous, up
1395 @node Final install, , Testing, Installing GCC
1397 @ifset finalinstallhtml
1399 @chapter Installing GCC: Final installation
1402 Now that GCC has been built (and optionally tested), you can install it with
1404 cd @var{objdir}; make install
1407 We strongly recommend to install into a target directory where there is
1408 no previous version of GCC present.
1410 That step completes the installation of GCC; user level binaries can
1411 be found in @file{@var{prefix}/bin} where @var{prefix} is the value you
1412 specified with the @option{--prefix} to configure (or @file{/usr/local}
1413 by default). (If you specified @option{--bindir}, that directory will
1414 be used instead; otherwise, if you specified @option{--exec-prefix},
1415 @file{@var{exec-prefix}/bin} will be used.) Headers for the C++ and
1416 Java libraries are installed in @file{@var{prefix}/include}; libraries
1417 in @file{@var{libdir}} (normally @file{@var{prefix}/lib}); internal
1418 parts of the compiler in @file{@var{libdir}/gcc-lib}; documentation in
1419 info format in @file{@var{infodir}} (normally @file{@var{prefix}/info}).
1421 When installing cross-compilers, GCC's executables
1422 are not only installed into @file{@var{bindir}}, that
1423 is, @file{@var{exec-prefix}/bin}, but additionally into
1424 @file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory
1425 exists. Typically, such @dfn{tooldirs} hold target-specific
1426 binutils, including assembler and linker.
1428 Installation into a temporary staging area or into a @command{chroot}
1429 jail can be achieved with the command
1432 make DESTDIR=@var{path-to-rootdir} install
1435 @noindent where @var{path-to-rootdir} is the absolute path of
1436 a directory relative to which all installation paths will be
1437 interpreted. Note that the directory specified by @code{DESTDIR}
1438 need not exist yet; it will be created if necessary.
1440 There is a subtle point with tooldirs and @code{DESTDIR}:
1441 If you relocate a cross-compiler installation with
1442 e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory
1443 @file{@var{rootdir}/@var{exec-prefix}/@var{target-alias}/bin} will
1444 be filled with duplicated GCC executables only if it already exists,
1445 it will not be created otherwise. This is regarded as a feature,
1446 not as a bug, because it gives slightly more control to the packagers
1447 using the @code{DESTDIR} feature.
1449 If you built a released version of GCC using @samp{make bootstrap} then please
1450 quickly review the build status page for your release, available from
1451 @uref{http://gcc.gnu.org/buildstat.html}.
1452 If your system is not listed for the version of GCC that you built,
1454 @email{gcc@@gcc.gnu.org} indicating
1455 that you successfully built and installed GCC.
1456 Include the following information:
1460 Output from running @file{@var{srcdir}/config.guess}. Do not send us
1461 that file itself, just the one-line output from running it.
1464 The output of @samp{gcc -v} for your newly installed gcc.
1465 This tells us which version of GCC you built and the options you passed to
1469 Whether you enabled all languages or a subset of them. If you used a
1470 full distribution then this information is part of the configure
1471 options in the output of @samp{gcc -v}, but if you downloaded the
1472 ``core'' compiler plus additional front ends then it isn't apparent
1473 which ones you built unless you tell us about it.
1476 If the build was for GNU/Linux, also include:
1479 The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
1480 this information should be available from @file{/etc/issue}.
1483 The version of the Linux kernel, available from @samp{uname --version}
1487 The version of glibc you used; for RPM-based systems like Red Hat,
1488 Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
1489 and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
1491 For other systems, you can include similar information if you think it is
1495 Any other information that you think would be useful to people building
1496 GCC on the same configuration. The new entry in the build status list
1497 will include a link to the archived copy of your message.
1500 We'd also like to know if the
1502 @ref{Specific, host/target specific installation notes}
1505 @uref{specific.html,,host/target specific installation notes}
1507 didn't include your host/target information or if that information is
1508 incomplete or out of date. Send a note to
1509 @email{gcc@@gcc.gnu.org} telling us how the information should be changed.
1511 If you find a bug, please report it following our
1512 @uref{../bugs.html,,bug reporting guidelines}.
1514 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
1515 dvi}. You will need to have @command{texi2dvi} (version at least 4.2)
1516 and @TeX{} installed. This creates a number of @file{.dvi} files in
1517 subdirectories of @file{@var{objdir}}; these may be converted for
1518 printing with programs such as @command{dvips}. You can also
1519 @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the
1520 Free Software Foundation}, though such manuals may not be for the most
1521 recent version of GCC@.
1528 @uref{./index.html,,Return to the GCC Installation page}
1532 @c ***Binaries****************************************************************
1534 @comment node-name, next, previous, up
1535 @node Binaries, Specific, Installing GCC, Top
1539 @chapter Installing GCC: Binaries
1542 @cindex Installing GCC: Binaries
1544 We are often asked about pre-compiled versions of GCC@. While we cannot
1545 provide these for all platforms, below you'll find links to binaries for
1546 various platforms where creating them by yourself is not easy due to various
1549 Please note that we did not create these binaries, nor do we
1550 support them. If you have any problems installing them, please
1551 contact their makers.
1558 @uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX};
1561 @uref{http://aixpdslib.seas.ucla.edu,,UCLA Software Library for AIX}.
1565 DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}.
1568 Hitachi H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
1569 Development Tools for the Hitachi H8/300[HS] Series}.
1575 @uref{http://hpux.cae.wisc.edu/,,HP-UX Porting Center};
1578 @uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
1582 Motorola 68HC11/68HC12---@uref{http://www.gnu-m68hc11.org,,GNU
1583 Development Tools for the Motorola 68HC11/68HC12}.
1586 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
1587 OpenServer/Unixware}.
1590 Sinix/Reliant Unix---@uref{ftp://ftp.fujitsu-siemens.com/pub/pd/gnu/gcc/,,Siemens}.
1593 Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware}.
1596 SGI---@uref{http://freeware.sgi.com/,,SGI Freeware}.
1602 The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project;
1604 The @uref{http://www.mingw.org/,,MinGW} project.
1608 @uref{ftp://ftp.thewrittenword.com/packages/by-name/,,The
1609 Written Word} offers binaries for
1612 Digital UNIX 4.0D and 5.1,
1614 HP-UX 10.20, 11.00, and 11.11, and
1615 Solaris/SPARC 2.5.1, 2.6, 2.7, 8, and 9,
1618 In addition to those specific offerings, you can get a binary
1619 distribution CD-ROM from the
1620 @uref{http://www.fsf.org/order/order.html,,Free Software Foundation}.
1621 It contains binaries for a number of platforms, and
1622 includes not only GCC, but other stuff as well. The current CD does
1623 not contain the latest version of GCC, but it should allow
1624 bootstrapping the compiler. An updated version of that disk is in the
1632 @uref{./index.html,,Return to the GCC Installation page}
1636 @c ***Specific****************************************************************
1638 @comment node-name, next, previous, up
1639 @node Specific, Old, Binaries, Top
1643 @chapter Host/target specific installation notes for GCC
1646 @cindex Specific installation notes
1647 @cindex Target specific installation
1648 @cindex Host specific installation
1649 @cindex Target specific installation notes
1651 Please read this document carefully @emph{before} installing the
1652 GNU Compiler Collection on your machine.
1657 @uref{#alpha*-*-*,,alpha*-*-*}
1659 @uref{#alpha*-dec-osf*,,alpha*-dec-osf*}
1661 @uref{#alphaev5-cray-unicosmk*,,alphaev5-cray-unicosmk*}
1663 @uref{#arc-*-elf,,arc-*-elf}
1665 @uref{#arm-*-*,,arm-*-*}
1667 @uref{#xscale-*-*,,xscale-*-*}
1675 @uref{#dsp16xx,,dsp16xx}
1677 @uref{#*-*-freebsd*,,*-*-freebsd*}
1679 @uref{#h8300-hms,,h8300-hms}
1681 @uref{#hppa*-hp-hpux*,,hppa*-hp-hpux*}
1683 @uref{#hppa*-hp-hpux10,,hppa*-hp-hpux10}
1685 @uref{#hppa*-hp-hpux11,,hppa*-hp-hpux11}
1687 @uref{#i370-*-*,,i370-*-*}
1689 @uref{#*-*-linux-gnu,,*-*-linux-gnu}
1691 @uref{#ix86-*-linux*aout,,i?86-*-linux*aout}
1693 @uref{#ix86-*-linux*,,i?86-*-linux*}
1695 @uref{#ix86-*-sco,,i?86-*-sco}
1697 @uref{#ix86-*-sco3.2v4,,i?86-*-sco3.2v4}
1699 @uref{#ix86-*-sco3.2v5*,,i?86-*-sco3.2v5*}
1701 @uref{#ix86-*-udk,,i?86-*-udk}
1703 @uref{#ix86-*-esix,,i?86-*-esix}
1705 @uref{#ia64-*-linux,,ia64-*-linux}
1707 @uref{#*-ibm-aix*,,*-ibm-aix*}
1709 @uref{#ip2k-*-elf,,ip2k-*-elf}
1711 @uref{#m32r-*-elf,,m32r-*-elf}
1713 @uref{#m6811-elf,,m6811-elf}
1715 @uref{#m6812-elf,,m6812-elf}
1717 @uref{#m68k-hp-hpux,,m68k-hp-hpux}
1719 @uref{#mips-*-*,,mips-*-*}
1721 @uref{#mips-sgi-irix5,,mips-sgi-irix5}
1723 @uref{#mips-sgi-irix6,,mips-sgi-irix6}
1725 @uref{#powerpc*-*-*,,powerpc*-*-*, powerpc-*-sysv4}
1727 @uref{#powerpc-*-darwin*,,powerpc-*-darwin*}
1729 @uref{#powerpc-*-elf,,powerpc-*-elf, powerpc-*-sysv4}
1731 @uref{#powerpc-*-linux-gnu*,,powerpc-*-linux-gnu*}
1733 @uref{#powerpc-*-netbsd*,,powerpc-*-netbsd*}
1735 @uref{#powerpc-*-eabiaix,,powerpc-*-eabiaix}
1737 @uref{#powerpc-*-eabisim,,powerpc-*-eabisim}
1739 @uref{#powerpc-*-eabi,,powerpc-*-eabi}
1741 @uref{#powerpcle-*-elf,,powerpcle-*-elf, powerpcle-*-sysv4}
1743 @uref{#powerpcle-*-eabisim,,powerpcle-*-eabisim}
1745 @uref{#powerpcle-*-eabi,,powerpcle-*-eabi}
1747 @uref{#powerpcle-*-winnt,,powerpcle-*-winnt, powerpcle-*-pe}
1749 @uref{#s390-*-linux*,,s390-*-linux*}
1751 @uref{#s390x-*-linux*,,s390x-*-linux*}
1753 @uref{#*-*-solaris2*,,*-*-solaris2*}
1755 @uref{#sparc-sun-solaris2*,,sparc-sun-solaris2*}
1757 @uref{#sparc-sun-solaris2.7,,sparc-sun-solaris2.7}
1759 @uref{#sparc-*-linux*,,sparc-*-linux*}
1761 @uref{#sparc64-*-solaris2*,,sparc64-*-solaris2*}
1763 @uref{#sparcv9-*-solaris2*,,sparcv9-*-solaris2*}
1765 @uref{#*-*-sysv*,,*-*-sysv*}
1767 @uref{#vax-dec-ultrix,,vax-dec-ultrix}
1769 @uref{#*-*-vxworks*,,*-*-vxworks*}
1771 @uref{#xtensa-*-elf,,xtensa-*-elf}
1773 @uref{#xtensa-*-linux*,,xtensa-*-linux*}
1775 @uref{#windows,,Microsoft Windows}
1779 @uref{#older,,Older systems}
1784 @uref{#elf_targets,,all ELF targets} (SVR4, Solaris 2, etc.)
1790 <!-- -------- host/target specific issues start here ---------------- -->
1793 @heading @anchor{alpha*-*-*}alpha*-*-*
1795 This section contains general configuration information for all
1796 alpha-based platforms using ELF (in particular, ignore this section for
1797 DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
1798 section, please read all other sections that match your target.
1800 We require binutils 2.11.2 or newer.
1801 Previous binutils releases had a number of problems with DWARF 2
1802 debugging information, not the least of which is incorrect linking of
1808 @heading @anchor{alpha*-dec-osf*}alpha*-dec-osf*
1809 Systems using processors that implement the DEC Alpha architecture and
1810 are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
1811 Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
1813 As of GCC 3.2, versions before @code{alpha*-dec-osf4} are no longer
1814 supported. (These are the versions which identify themselves as DEC
1817 In Digital Unix V4.0, virtual memory exhausted bootstrap failures
1818 may be fixed by configuring with @option{--with-gc=simple},
1819 reconfiguring Kernel Virtual Memory and Swap parameters
1820 per the @command{/usr/sbin/sys_check} Tuning Suggestions,
1821 or applying the patch in
1822 @uref{http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html}.
1824 In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
1825 currently (2001-06-13) work with @command{mips-tfile}. As a workaround,
1826 we need to use the old assembler, invoked via the barely documented
1827 @option{-oldas} option. To bootstrap GCC, you either need to use the
1831 % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
1834 or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
1837 % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
1840 As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld}
1841 are supported on Tru64 UNIX, so you must not configure GCC with
1842 @option{--with-gnu-as} or @option{--with-gnu-ld}.
1844 The @option{--enable-threads} options isn't supported yet. A patch is
1845 in preparation for a future release.
1847 GCC writes a @samp{.verstamp} directive to the assembler output file
1848 unless it is built as a cross-compiler. It gets the version to use from
1849 the system header file @file{/usr/include/stamp.h}. If you install a
1850 new version of DEC Unix, you should rebuild GCC to pick up the new version
1853 Note that since the Alpha is a 64-bit architecture, cross-compilers from
1854 32-bit machines will not generate code as efficient as that generated
1855 when the compiler is running on a 64-bit machine because many
1856 optimizations that depend on being able to represent a word on the
1857 target in an integral value on the host cannot be performed. Building
1858 cross-compilers on the Alpha for 32-bit machines has only been tested in
1859 a few cases and may not work properly.
1861 @samp{make compare} may fail on old versions of DEC Unix unless you add
1862 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
1863 assembler input file is stored in the object file, and that makes
1864 comparison fail if it differs between the @code{stage1} and
1865 @code{stage2} compilations. The option @option{-save-temps} forces a
1866 fixed name to be used for the assembler input file, instead of a
1867 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
1868 unless the comparisons fail without that option. If you add
1869 @option{-save-temps}, you will have to manually delete the @samp{.i} and
1870 @samp{.s} files after each series of compilations.
1872 GCC now supports both the native (ECOFF) debugging format used by DBX
1873 and GDB and an encapsulated STABS format for use only with GDB@. See the
1874 discussion of the @option{--with-stabs} option of @file{configure} above
1875 for more information on these formats and how to select them.
1877 There is a bug in DEC's assembler that produces incorrect line numbers
1878 for ECOFF format when the @samp{.align} directive is used. To work
1879 around this problem, GCC will not emit such alignment directives
1880 while writing ECOFF format debugging information even if optimization is
1881 being performed. Unfortunately, this has the very undesirable
1882 side-effect that code addresses when @option{-O} is specified are
1883 different depending on whether or not @option{-g} is also specified.
1885 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
1886 DBX@. DEC is now aware of this problem with the assembler and hopes to
1887 provide a fix shortly.
1892 @heading @anchor{alphaev5-cray-unicosmk*}alphaev5-cray-unicosmk*
1893 Cray T3E systems running Unicos/Mk.
1895 This port is incomplete and has many known bugs. We hope to improve the
1896 support for this target soon. Currently, only the C front end is supported,
1897 and it is not possible to build parallel applications. Cray modules are not
1898 supported; in particular, Craylibs are assumed to be in
1899 @file{/opt/ctl/craylibs/craylibs}.
1901 You absolutely @strong{must} use GNU make on this platform. Also, you
1902 need to tell GCC where to find the assembler and the linker. The
1903 simplest way to do so is by providing @option{--with-as} and
1904 @option{--with-ld} to @file{configure}, e.g.@:
1907 configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld \
1908 --enable-languages=c
1911 The comparison test during @samp{make bootstrap} fails on Unicos/Mk
1912 because the assembler inserts timestamps into object files. You should
1913 be able to work around this by doing @samp{make all} after getting this
1919 @heading @anchor{arc-*-elf}arc-*-elf
1920 Argonaut ARC processor.
1921 This configuration is intended for embedded systems.
1926 @heading @anchor{arm-*-*}arm-*-*
1927 @heading @anchor{xscale-*-*}xscale-*-*
1928 Advanced RISC Machines ARM-family processors. Subtargets that use the
1929 ELF object format require GNU binutils 2.13 or newer.
1934 @heading @anchor{avr}avr
1936 ATMEL AVR-family micro controllers. These are used in embedded
1937 applications. There are no standard Unix configurations.
1939 @xref{AVR Options,, AVR Options, gcc, Using and Porting the GNU Compiler
1943 See ``AVR Options'' in the main manual
1945 for the list of supported MCU types.
1947 Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
1949 Further installation notes and other useful information about AVR tools
1950 can also be obtained from:
1954 @uref{http://www.openavr.org,,http://www.openavr.org}
1956 @uref{http://home.overta.ru/users/denisc/,,http://home.overta.ru/users/denisc/}
1958 @uref{http://www.amelek.gda.pl/avr/,,http://www.amelek.gda.pl/avr/}
1961 We @emph{strongly} recommend using binutils 2.13 or newer.
1963 The following error:
1965 Error: register required
1968 indicates that you should upgrade to a newer version of the binutils.
1973 @heading @anchor{c4x}c4x
1975 Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal
1976 Processors. These are used in embedded applications. There are no
1977 standard Unix configurations.
1979 @xref{TMS320C3x/C4x Options,, TMS320C3x/C4x Options, gcc, Using and
1980 Porting the GNU Compiler Collection (GCC)},
1983 See ``TMS320C3x/C4x Options'' in the main manual
1985 for the list of supported MCU types.
1987 GCC can be configured as a cross compiler for both the C3x and C4x
1988 architectures on the same system. Use @samp{configure --target=c4x
1989 --enable-languages="c,c++"} to configure.
1992 Further installation notes and other useful information about C4x tools
1993 can also be obtained from:
1997 @uref{http://www.elec.canterbury.ac.nz/c4x/,,http://www.elec.canterbury.ac.nz/c4x/}
2003 @heading @anchor{cris}CRIS
2005 CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
2006 series. These are used in embedded applications.
2009 @xref{CRIS Options,, CRIS Options, gcc, Using and Porting the GNU Compiler
2013 See ``CRIS Options'' in the main manual
2015 for a list of CRIS-specific options.
2017 There are a few different CRIS targets:
2019 @item cris-axis-aout
2020 Old target. Includes a multilib for the @samp{elinux} a.out-based
2021 target. No multilibs for newer architecture variants.
2023 Mainly for monolithic embedded systems. Includes a multilib for the
2024 @samp{v10} core used in @samp{ETRAX 100 LX}.
2025 @item cris-axis-linux-gnu
2026 A GNU/Linux port for the CRIS architecture, currently targeting
2027 @samp{ETRAX 100 LX} by default.
2030 For @code{cris-axis-aout} and @code{cris-axis-elf} you need binutils 2.11
2031 or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
2033 Pre-packaged tools can be obtained from
2034 @uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More
2035 information about this platform is available at
2036 @uref{http://developer.axis.com/}.
2041 @heading @anchor{dos}DOS
2043 Please have a look at our @uref{binaries.html,,binaries page}.
2045 You cannot install GCC by itself on MSDOS; it will not compile under
2046 any MSDOS compiler except itself. You need to get the complete
2047 compilation package DJGPP, which includes binaries as well as sources,
2048 and includes all the necessary compilation tools and libraries.
2053 @heading @anchor{dsp16xx}dsp16xx
2054 A port to the AT&T DSP1610 family of processors.
2059 @heading @anchor{*-*-freebsd*}*-*-freebsd*
2061 The version of binutils installed in @file{/usr/bin} is known to work unless
2062 otherwise specified in any per-architecture notes. However, binutils
2063 2.12.1 or greater is known to improve overall testsuite results.
2065 FreeBSD 1 is no longer supported.
2067 For FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
2068 configuration support and files as shipped with GCC 2.95 are still in
2069 place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
2070 it is unknown which version of binutils was used (it is assumed that it
2071 was the system copy in @file{/usr/bin}) and C++ EH failures were noted.
2073 For FreeBSD using the ELF file format: DWARF 2 debugging is now the
2074 default for all CPU architectures. It had been the default on
2075 FreeBSD/alpha since its inception. You may use @option{-gstabs} instead
2076 of @option{-g}, if you really want the old debugging format. There are
2077 no known issues with mixing object files and libraries with different
2078 debugging formats. Otherwise, this release of GCC should now match more
2079 of the configuration used in the stock FreeBSD configuration of GCC. In
2080 particular, @option{--enable-threads} is now configured by default.
2081 However, as a general user, do not attempt to replace the system
2082 compiler with this release. Known to bootstrap and check with good
2083 results on FreeBSD 4.8-STABLE and 5-CURRENT@. In the past, known to
2084 bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2,
2085 4.3, 4.4, 4.5-STABLE@.
2087 In principle, @option{--enable-threads} is now compatible with
2088 @option{--enable-libgcj} on FreeBSD@. However, it has only been built
2089 and tested on @samp{i386-*-freebsd[45]} and @samp{alpha-*-freebsd[45]}.
2091 library may be incorrectly built (symbols are missing at link time).
2092 There is a rare timing-based startup hang (probably involves an
2093 assumption about the thread library). Multi-threaded boehm-gc (required for
2094 libjava) exposes severe threaded signal-handling bugs on FreeBSD before
2095 4.5-RELEASE@. Other CPU architectures
2096 supported by FreeBSD will require additional configuration tuning in, at
2097 the very least, both boehm-gc and libffi.
2099 Shared @file{libgcc_s.so} is now built and installed by default.
2104 @heading @anchor{h8300-hms}h8300-hms
2105 Hitachi H8/300 series of processors.
2107 Please have a look at our @uref{binaries.html,,binaries page}.
2109 The calling convention and structure layout has changed in release 2.6.
2110 All code must be recompiled. The calling convention now passes the
2111 first three arguments in function calls in registers. Structures are no
2112 longer a multiple of 2 bytes.
2117 @heading @anchor{hppa*-hp-hpux*}hppa*-hp-hpux*
2118 HP-UX version 9 or older is no longer supported.
2120 We @emph{highly} recommend using gas/binutils 2.8 or newer on all hppa
2121 platforms; you may encounter a variety of problems when using the HP
2124 Specifically, @option{-g} does not work on HP-UX (since that system
2125 uses a peculiar debugging format which GCC does not know about), unless you
2126 use GAS and GDB and configure GCC with the
2127 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
2128 @option{--with-as=@dots{}} options.
2130 If you wish to use the pa-risc 2.0 architecture support with a 32-bit
2131 runtime, you must use either the HP assembler, gas/binutils 2.11 or newer,
2133 @uref{ftp://sources.redhat.com/pub/binutils/snapshots,,snapshot of gas}.
2135 There are two default scheduling models for instructions. These are
2136 PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
2137 architecture specified for the target machine when configuring.
2138 PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
2139 the target is a @samp{hppa1*} machine.
2141 The PROCESSOR_8000 model is not well suited to older processors. Thus,
2142 it is important to completely specify the machine architecture when
2143 configuring if you want a model other than PROCESSOR_8000. The macro
2144 TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
2145 default scheduling model is desired.
2147 More specific information to @samp{hppa*-hp-hpux*} targets follows.
2152 @heading @anchor{hppa*-hp-hpux10}hppa*-hp-hpux10
2154 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
2155 @code{PHCO_19798} from HP@. HP has two sites which provide patches free of
2161 <a href="http://us.itrc.hp.com/service/home/home.do">US, Canada, Asia-Pacific, and
2165 @uref{http://us.itrc.hp.com/service/home/home.do,,} US, Canada, Asia-Pacific,
2169 @uref{http://europe.itrc.hp.com/service/home/home.do,,} Europe.
2172 The HP assembler on these systems has some problems. Most notably the
2173 assembler inserts timestamps into each object file it creates, causing
2174 the 3-stage comparison test to fail during a @samp{make bootstrap}.
2175 You should be able to continue by saying @samp{make all} after getting
2176 the failure from @samp{make bootstrap}.
2182 @heading @anchor{hppa*-hp-hpux11}hppa*-hp-hpux11
2184 GCC 3.0 and up support HP-UX 11. On 64-bit capable systems, there
2185 are two distinct ports. The @samp{hppa2.0w-hp-hpux11*} port generates
2186 code for the 32-bit pa-risc runtime architecture. It uses the HP
2187 linker. The @samp{hppa64-hp-hpux11*} port generates 64-bit code for the
2188 pa-risc 2.0 architecture. The script config.guess now selects the port
2189 type based on the type compiler detected during configuration. You must
2190 set your @env{PATH} or define @env{CC} so that configure finds an appropriate
2191 compiler for the initial bootstrap. Different prefixes must be used if
2192 both ports are to be installed on the same system.
2194 It is best to explicitly configure the @samp{hppa64-hp-hpux11*} target
2195 with the @option{--with-ld=@dots{}} option. We support both the HP
2196 and GNU linkers for this target. The two linkers require different
2197 link commands. Thus, it's not possible to switch linkers during a
2198 GCC build. This has been been reported to occur in a unified build
2199 of binutils and GCC.
2201 GCC 2.95.x is not supported under HP-UX 11 and cannot be used to
2202 compile GCC 3.0 and up. Refer to @uref{binaries.html,,binaries} for
2203 information about obtaining precompiled GCC binaries for HP-UX.
2205 You must use GNU binutils 2.11 or above with the 32-bit port. Thread
2206 support is not currently implemented, so @option{--enable-threads} does
2210 @item @uref{http://gcc.gnu.org/ml/gcc-prs/2002-01/msg00551.html}
2211 @item @uref{http://gcc.gnu.org/ml/gcc-bugs/2002-01/msg00663.html}
2214 GCC 3.3 and later support weak symbols on the 32-bit port using SOM
2215 secondary definition symbols. This feature is not enabled for earlier
2216 versions of HP-UX since there have been bugs in the linker support for
2217 secondary symbols. The HP linker patches @code{PHSS_26559} and
2218 @code{PHSS_24304} for HP-UX 11.00 and 11.11, respectively, correct the
2219 problem of linker core dumps creating C++ libraries. Earlier patches
2220 may work but they have not been tested.
2222 GCC 3.3 nows uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capability
2223 to run initializers and finalizers on the 64-bit port. The feature
2224 requires CVS binutils as of January 2, 2003, or a subsequent release
2225 to correct a problem arising from HP's non-standard use of the .init
2226 and .fini sections. The 32-bit port uses the linker @option{+init}
2227 and @option{+fini} options. As with the support for secondary symbols,
2228 there have been bugs in the order in which these options are executed
2229 by the HP linker. So, again a recent linker patch is recommended.
2231 The HP assembler has many limitations and is not recommended for either
2232 the 32 or 64-bit ports. For example, it does not support weak symbols
2233 or alias definitions. As a result, explicit template instantiations
2234 are required when using C++. This will make it difficult if not
2235 impossible to build many C++ applications. You also can't generate
2236 debugging information when using the HP assembler with GCC.
2238 There are a number of issues to consider in selecting which linker to
2239 use with the 64-bit port. The GNU 64-bit linker can only create dynamic
2240 binaries. The @option{-static} option causes linking with archive
2241 libraries but doesn't produce a truly static binary. Dynamic binaries
2242 still require final binding by the dynamic loader to resolve a set of
2243 dynamic-loader-defined symbols. The default behavior of the HP linker
2244 is the same as the GNU linker. However, it can generate true 64-bit
2245 static binaries using the @option{+compat} option.
2247 The HP 64-bit linker doesn't support linkonce semantics. As a
2248 result, C++ programs have many more sections than they should.
2250 The GNU 64-bit linker has some issues with shared library support
2251 and exceptions. As a result, we only support libgcc in archive
2252 format. For similar reasons, dwarf2 unwind and exception support
2253 are disabled. The GNU linker also has problems creating binaries
2254 with @option{-static}. It doesn't provide stubs for internal
2255 calls to global functions in shared libraries, so these calls
2256 can't be overloaded.
2258 There are several possible approaches to building the distribution.
2259 Binutils can be built first using the HP tools. Then, the GCC
2260 distribution can be built. The second approach is to build GCC
2261 first using the HP tools, then build binutils, then rebuild GCC.
2262 There have been problems with various binary distributions, so
2263 it is best not to start from a binary distribution.
2265 Starting with GCC 3.4 an ISO C compiler is required to bootstrap.
2266 The bundled compiler supports only traditional C; you will need
2267 either HP's unbundled compiler, or a binary distribution of GCC@.
2269 This port still is undergoing significant development.
2274 @heading @anchor{i370-*-*}i370-*-*
2275 This port is very preliminary and has many known bugs. We hope to
2276 have a higher-quality port for this machine soon.
2281 @heading @anchor{*-*-linux-gnu}*-*-linux-gnu
2283 Versions of libstdc++-v3 starting with 3.2.1 require bugfixes present
2284 in glibc 2.2.5 and later. More information is available in the
2285 libstdc++-v3 documentation.
2287 If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install
2288 out-of-the-box. You'll get compile errors while building @samp{libstdc++}.
2289 The patch @uref{glibc-2.2.patch,,glibc-2.2.patch}, that is to be
2290 applied in the GCC source tree, fixes the compatibility problems.
2292 Currently Glibc 2.2.3 (and older releases) and GCC 3.0 are out of sync
2293 since the latest exception handling changes for GCC@. Compiling glibc
2294 with GCC 3.0 will give a binary incompatible glibc and therefore cause
2295 lots of problems and might make your system completely unusable. This
2296 will definitely need fixes in glibc but might also need fixes in GCC@. We
2297 strongly advise to wait for glibc 2.2.4 and to read the release notes of
2298 glibc 2.2.4 whether patches for GCC 3.0 are needed. You can use glibc
2299 2.2.3 with GCC 3.0, just do not try to recompile it.
2304 @heading @anchor{ix86-*-linux*aout}i?86-*-linux*aout
2305 Use this configuration to generate @file{a.out} binaries on Linux-based
2306 GNU systems. This configuration is being superseded. You must use
2307 gas/binutils version 2.5.2 or later.
2312 @heading @anchor{ix86-*-linux*}i?86-*-linux*
2314 You will need binutils 2.9.1.0.15 or newer for exception handling to work.
2316 If you receive Signal 11 errors when building on GNU/Linux, then it is
2317 possible you have a hardware problem. Further information on this can be
2318 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
2323 @heading @anchor{ix86-*-sco}i?86-*-sco
2324 Compilation with RCC is recommended. Also, it may be a good idea to
2325 link with GNU malloc instead of the malloc that comes with the system.
2330 @heading @anchor{ix86-*-sco3.2v4}i?86-*-sco3.2v4
2331 Use this configuration for SCO release 3.2 version 4.
2336 @heading @anchor{ix86-*-sco3.2v5*}i?86-*-sco3.2v5*
2337 Use this for the SCO OpenServer Release 5 family of operating systems.
2339 Unlike earlier versions of GCC, the ability to generate COFF with this
2340 target is no longer provided.
2342 Earlier versions of GCC emitted DWARF 1 when generating ELF to allow
2343 the system debugger to be used. That support was too burdensome to
2344 maintain. GCC now emits only DWARF 2 for this target. This means you
2345 may use either the UDK debugger or GDB to debug programs built by this
2348 GCC is now only supported on releases 5.0.4 and later, and requires that
2349 you install Support Level Supplement OSS646B or later, and Support Level
2350 Supplement OSS631C or later. If you are using release 5.0.7 of
2351 OpenServer, you must have at least the first maintenance pack installed
2352 (this includes the relevant portions of OSS646). OSS646, also known as
2353 the "Execution Environment Update", provides updated link editors and
2354 assemblers, as well as updated standard C and math libraries. The C
2355 startup modules are also updated to support the System V gABI draft, and
2356 GCC relies on that behaviour. OSS631 provides a collection of commonly
2357 used open source libraries, some of which GCC depends on (such as GNU
2358 gettext and zlib). SCO OpenServer Release 5.0.7 has all of this built
2359 in by default, but OSS631C and later also apply to that release. Please
2361 @uref{ftp://ftp.sco.com/pub/openserver5,,ftp://ftp.sco.com/pub/openserver5}
2362 for the latest versions of these (and other potentially useful)
2365 Although there is support for using the native assembler, it is
2366 recommended that you configure GCC to use the GNU assembler. You do
2367 this by using the flags
2368 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You should
2369 use a modern version of GNU binutils. Version 2.13.2.1 was used for all
2370 testing. In general, only the @option{--with-gnu-as} option is tested.
2371 A modern bintuils (as well as a plethora of other development related
2372 GNU utilities) can be found in Support Level Supplement OSS658A, the
2373 "GNU Development Tools" package. See the SCO web and ftp sites for details.
2374 That package also contains the currently "officially supported" version of
2375 GCC, version 2.95.3. It is useful for bootstrapping this version.
2380 @heading @anchor{ix86-*-udk}i?86-*-udk
2382 This target emulates the SCO Universal Development Kit and requires that
2383 package be installed. (If it is installed, you will have a
2384 @file{/udk/usr/ccs/bin/cc} file present.) It's very much like the
2385 @samp{i?86-*-unixware7*} target
2386 but is meant to be used when hosting on a system where UDK isn't the
2387 default compiler such as OpenServer 5 or Unixware 2. This target will
2388 generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
2389 with the same warnings and caveats as the SCO UDK@.
2391 This target is a little tricky to build because we have to distinguish
2392 it from the native tools (so it gets headers, startups, and libraries
2393 from the right place) while making the tools not think we're actually
2394 building a cross compiler. The easiest way to do this is with a configure
2398 CC=/udk/usr/ccs/bin/cc @var{/your/path/to}/gcc/configure \
2399 --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-
2402 @emph{You should substitute @samp{i686} in the above command with the appropriate
2403 processor for your host.}
2405 After the usual @samp{make bootstrap} and
2406 @samp{make install}, you can then access the UDK-targeted GCC
2407 tools by adding @command{udk-} before the commonly known name. For
2408 example, to invoke the C compiler, you would use @command{udk-gcc}.
2409 They will coexist peacefully with any native-target GCC tools you may
2416 @heading @anchor{ia64-*-linux}ia64-*-linux
2417 IA-64 processor (also known as IPF, or Itanium Processor Family)
2420 The toolchain is not completely finished, so requirements will continue
2422 GCC 3.0.1 and later require glibc 2.2.4.
2423 GCC 3.0.2 requires binutils from 2001-09-05 or later.
2424 GCC 3.0.1 requires binutils 2.11.1 or later.
2426 None of the following versions of GCC has an ABI that is compatible
2427 with any of the other versions in this list, with the exception that
2428 Red Hat 2.96 and Trillian 000171 are compatible with each other:
2429 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
2430 This primarily affects C++ programs and programs that create shared libraries.
2431 Because of these ABI incompatibilities, GCC 3.0.2 is not recommended for
2432 user programs on GNU/Linux systems built using earlier compiler releases.
2433 GCC 3.0.2 is recommended for compiling linux, the kernel.
2434 GCC 3.0.2 is believed to be fully ABI compliant, and hence no more major
2435 ABI changes are expected.
2439 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
2441 @heading @anchor{*-ibm-aix*}*-ibm-aix*
2442 AIX version 3 or older is no longer supported.
2444 AIX Make frequently has problems with GCC makefiles. GNU Make 3.76 or
2445 newer is recommended to build on this platform.
2447 Errors involving @code{alloca} when building GCC generally are due
2448 to an incorrect definition of @code{CC} in the Makefile or mixing files
2449 compiled with the native C compiler and GCC@. During the stage1 phase of
2450 the build, the native AIX compiler @strong{must} be invoked as @command{cc}
2451 (not @command{xlc}). Once @command{configure} has been informed of
2452 @command{xlc}, one needs to use @samp{make distclean} to remove the
2453 configure cache files and ensure that @env{CC} environment variable
2454 does not provide a definition that will confuse @command{configure}.
2455 If this error occurs during stage2 or later, then the problem most likely
2456 is the version of Make (see above).
2458 The native @command{as} and @command{ld} are recommended for bootstrapping
2459 on AIX 4 and required for bootstrapping on AIX 5L. The GNU Assembler
2460 reports that it supports WEAK symbols on AIX 4, which causes GCC to try to
2461 utilize weak symbol functionality although it is not supported. The GNU
2462 Assembler and Linker do not support AIX 5L sufficiently to bootstrap GCC.
2463 The native AIX tools do interoperate with GCC@.
2465 Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
2466 APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1).
2468 @samp{libstdc++} in GCC 3.2 increments the major version number of the
2469 shared object and GCC installation places the @file{libstdc++.a}
2470 shared library in a common location which will overwrite the GCC 3.1
2471 version of the shared library. Applications either need to be
2472 re-linked against the new shared library or the GCC 3.1 version of the
2473 @samp{libstdc++} shared object needs to be available to the AIX
2474 runtime loader. The GCC 3.1 @samp{libstdc++.so.4} shared object can
2475 be installed for runtime dynamic loading using the following steps to
2476 set the @samp{F_LOADONLY} flag in the shared object for @emph{each}
2477 multilib @file{libstdc++.a} installed:
2479 Extract the shared object from each the GCC 3.1 @file{libstdc++.a}
2482 % ar -x libstdc++.a libstdc++.so.4
2485 Enable the @samp{F_LOADONLY} flag so that the shared object will be
2486 available for runtime dynamic loading, but not linking:
2488 % strip -e libstdc++.so.4
2491 Archive the runtime-only shared object in the GCC 3.2
2492 @file{libstdc++.a} archive:
2494 % ar -q libstdc++.a libstdc++.so.4
2497 Linking executables and shared libraries may produce warnings of
2498 duplicate symbols. The assembly files generated by GCC for AIX always
2499 have included multiple symbol definitions for certain global variable
2500 and function declarations in the original program. The warnings should
2501 not prevent the linker from producing a correct library or runnable
2504 AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
2505 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
2506 to parse archive libraries did not handle the new format correctly.
2507 These routines are used by GCC and result in error messages during
2508 linking such as ``not a COFF file''. The version of the routines shipped
2509 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
2510 option of the archive command may be used to create archives of 32-bit
2511 objects using the original ``small format''. A correct version of the
2512 routines is shipped with AIX 4.3.2 and above.
2514 Some versions of the AIX binder (linker) can fail with a relocation
2515 overflow severe error when the @option{-bbigtoc} option is used to link
2516 GCC-produced object files into an executable that overflows the TOC@. A fix
2517 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
2518 available from IBM Customer Support and from its
2519 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2520 website as PTF U455193.
2522 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
2523 with a segmentation fault when invoked by any version of GCC@. A fix for
2524 APAR IX87327 is available from IBM Customer Support and from its
2525 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2526 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
2528 The initial assembler shipped with AIX 4.3.0 generates incorrect object
2529 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
2530 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
2531 @uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
2532 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
2534 AIX provides National Language Support (NLS)@. Compilers and assemblers
2535 use NLS to support locale-specific representations of various data
2536 formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
2537 separating decimal fractions). There have been problems reported where
2538 GCC does not produce the same floating-point formats that the assembler
2539 expects. If one encounters this problem, set the @env{LANG}
2540 environment variable to @samp{C} or @samp{En_US}.
2542 By default, GCC for AIX 4.1 and above produces code that can be used on
2543 both Power or PowerPC processors.
2545 A default can be specified with the @option{-mcpu=@var{cpu_type}}
2546 switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
2551 @heading @anchor{ip2k-*-elf}ip2k-*-elf
2552 Ubicom IP2022 micro controller.
2553 This configuration is intended for embedded systems.
2554 There are no standard Unix configurations.
2556 Use @samp{configure --target=ip2k-elf --enable-languages=c} to configure GCC@.
2561 @heading @anchor{m32r-*-elf}m32r-*-elf
2562 Mitsubishi M32R processor.
2563 This configuration is intended for embedded systems.
2568 @heading @anchor{m6811-elf}m6811-elf
2569 Motorola 68HC11 family micro controllers. These are used in embedded
2570 applications. There are no standard Unix configurations.
2575 @heading @anchor{m6812-elf}m6812-elf
2576 Motorola 68HC12 family micro controllers. These are used in embedded
2577 applications. There are no standard Unix configurations.
2582 @heading @anchor{m68k-hp-hpux}m68k-hp-hpux
2583 HP 9000 series 300 or 400 running HP-UX@. HP-UX version 8.0 has a bug in
2584 the assembler that prevents compilation of GCC@. This
2585 bug manifests itself during the first stage of compilation, while
2586 building @file{libgcc2.a}:
2590 cc1: warning: `-g' option not supported on this version of GCC
2591 cc1: warning: `-g1' option not supported on this version of GCC
2592 ./xgcc: Internal compiler error: program as got fatal signal 11
2595 A patched version of the assembler is available as the file
2596 @uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you
2597 have HP software support, the patch can also be obtained directly from
2598 HP, as described in the following note:
2601 This is the patched assembler, to patch SR#1653-010439, where the
2602 assembler aborts on floating point constants.
2604 The bug is not really in the assembler, but in the shared library
2605 version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is
2606 SR#4701-078451. Anyway, the attached assembler uses the archive
2607 library version of ``cvtnum(3c)'' and thus does not exhibit the bug.
2610 This patch is also known as PHCO_4484.
2612 In addition, if you wish to use gas, you must use
2613 gas version 2.1 or later, and you must use the GNU linker version 2.1 or
2614 later. Earlier versions of gas relied upon a program which converted the
2615 gas output into the native HP-UX format, but that program has not been
2616 kept up to date. gdb does not understand that native HP-UX format, so
2617 you must use gas if you wish to use gdb.
2619 On HP-UX version 8.05, but not on 8.07 or more recent versions, the
2620 @command{fixproto} shell script triggers a bug in the system shell. If you
2621 encounter this problem, upgrade your operating system or use BASH (the
2622 GNU shell) to run @command{fixproto}. This bug will cause the fixproto
2623 program to report an error of the form:
2626 ./fixproto: sh internal 1K buffer overflow
2629 To fix this, you can also change the first line of the fixproto script
2639 @heading @anchor{mips-*-*}mips-*-*
2640 If on a MIPS system you get an error message saying ``does not have gp
2641 sections for all it's [sic] sectons [sic]'', don't worry about it. This
2642 happens whenever you use GAS with the MIPS linker, but there is not
2643 really anything wrong, and it is okay to use the output file. You can
2644 stop such warnings by installing the GNU linker.
2646 It would be nice to extend GAS to produce the gp tables, but they are
2647 optional, and there should not be a warning about their absence.
2649 The libstdc++ atomic locking routines for MIPS targets requires MIPS II
2650 and later. A patch went in just after the GCC 3.3 release to
2651 make @samp{mips*-*-*} use the generic implementation instead. You can also
2652 configure for @samp{mipsel-elf} as a workaround. The
2653 @samp{mips*-*-linux*} target continues to use the MIPS II routines. More
2654 work on this is expected in future releases.
2659 @heading @anchor{mips-sgi-irix5}mips-sgi-irix5
2661 This configuration has considerable problems, which will be fixed in a
2664 In order to compile GCC on an SGI running IRIX 5, the ``compiler_dev.hdr''
2665 subsystem must be installed from the IDO CD-ROM supplied by Silicon
2666 Graphics. It is also available for download from
2667 @uref{http://www.sgi.com/developers/devtools/apis/ido.html,,http://www.sgi.com/developers/devtools/apis/ido.html}.
2669 @samp{make compare} may fail on version 5 of IRIX unless you add
2670 @option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
2671 assembler input file is stored in the object file, and that makes
2672 comparison fail if it differs between the @code{stage1} and
2673 @code{stage2} compilations. The option @option{-save-temps} forces a
2674 fixed name to be used for the assembler input file, instead of a
2675 randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
2676 unless the comparisons fail without that option. If you do you
2677 @option{-save-temps}, you will have to manually delete the @samp{.i} and
2678 @samp{.s} files after each series of compilations.
2680 If you use the MIPS C compiler to bootstrap, it may be necessary
2681 to increase its table size for switch statements with the
2682 @option{-Wf,-XNg1500} option. If you use the @option{-O2}
2683 optimization option, you also need to use @option{-Olimit 3000}.
2685 To enable debugging under IRIX 5, you must use GNU @command{as} 2.11.2
2687 and use the @option{--with-gnu-as} configure option when configuring GCC.
2688 GNU @command{as} is distributed as part of the binutils package.
2689 When using release 2.11.2, you need to apply a patch
2690 @uref{http://sources.redhat.com/ml/binutils/2001-07/msg00352.html,,http://sources.redhat.com/ml/binutils/2001-07/msg00352.html}
2691 which will be included in the next release of binutils.
2693 When building GCC, the build process loops rebuilding @command{cc1} over
2694 and over again. This happens on @samp{mips-sgi-irix5.2}, and possibly
2695 other platforms. It has been reported that this is a known bug in the
2696 @command{make} shipped with IRIX 5.2. We recommend you use GNU
2697 @command{make} instead of the vendor supplied @command{make} program;
2698 however, you may have success with @command{smake} on IRIX 5.2 if you do
2699 not have GNU @command{make} available.
2704 @heading @anchor{mips-sgi-irix6}mips-sgi-irix6
2706 If you are using IRIX @command{cc} as your bootstrap compiler, you must
2707 ensure that the N32 ABI is in use. To test this, compile a simple C
2708 file with @command{cc} and then run @command{file} on the
2709 resulting object file. The output should look like:
2712 test.o: ELF N32 MSB @dots{}
2718 test.o: ELF 32-bit MSB @dots{}
2724 test.o: ELF 64-bit MSB @dots{}
2727 then your version of @command{cc} uses the O32 or N64 ABI by default. You
2728 should set the environment variable @env{CC} to @samp{cc -n32}
2729 before configuring GCC@.
2731 If you want the resulting @command{gcc} to run on old 32-bit systems
2732 with the MIPS R4400 CPU, you need to ensure that only code for the mips3
2733 instruction set architecture (ISA) is generated. While GCC 3.x does
2734 this correctly, both GCC 2.95 and SGI's MIPSpro @command{cc} may change
2735 the ISA depending on the machine where GCC is built. Using one of them
2736 as the bootstrap compiler may result in mips4 code, which won't run at
2737 all on mips3-only systems. For the test program above, you should see:
2740 test.o: ELF N32 MSB mips-3 @dots{}
2746 test.o: ELF N32 MSB mips-4 @dots{}
2749 instead, you should set the environment variable @env{CC} to @samp{cc
2750 -n32 -mips3} or @samp{gcc -mips3} respectively before configuring GCC@.
2752 GCC on IRIX 6 is usually built to support both the N32 and N64 ABIs. If
2753 you build GCC on a system that doesn't have the N64 libraries installed,
2754 you need to configure with @option{--disable-multilib} so GCC doesn't
2755 try to use them. Look for @file{/usr/lib64/libc.so.1} to see if you
2756 have the 64-bit libraries installed.
2758 You must @emph{not} use GNU @command{as} (which isn't built anyway as of
2759 binutils 2.11.2) on IRIX 6 platforms; doing so will only cause problems.
2761 GCC does not currently support generating O32 ABI binaries in the
2762 @samp{mips-sgi-irix6} configurations. It is possible to create a GCC
2763 with O32 ABI only support by configuring it for the @samp{mips-sgi-irix5}
2764 target and using a patched GNU @command{as} 2.11.2 as documented in the
2765 @uref{#mips-sgi-irix5,,@samp{mips-sgi-irix5}} section above. Using the
2766 native assembler requires patches to GCC which will be included in a
2767 future release. It is
2768 expected that O32 ABI support will be available again in a future release.
2770 The @option{--enable-threads} option doesn't currently work, a patch is
2771 in preparation for a future release. The @option{--enable-libgcj}
2772 option is disabled by default: IRIX 6 uses a very low default limit
2773 (20480) for the command line length. Although libtool contains a
2774 workaround for this problem, at least the N64 @samp{libgcj} is known not
2775 to build despite this, running into an internal error of the native
2776 @command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
2777 its maximum of 262144 bytes. If you have root access, you can use the
2778 @command{systune} command to do this.
2780 GCC does not correctly pass/return structures which are
2781 smaller than 16 bytes and which are not 8 bytes. The problem is very
2782 involved and difficult to fix. It affects a number of other targets also,
2783 but IRIX 6 is affected the most, because it is a 64-bit target, and 4 byte
2784 structures are common. The exact problem is that structures are being padded
2785 at the wrong end, e.g.@: a 4 byte structure is loaded into the lower 4 bytes
2786 of the register when it should be loaded into the upper 4 bytes of the
2789 GCC is consistent with itself, but not consistent with the SGI C compiler
2790 (and the SGI supplied runtime libraries), so the only failures that can
2791 happen are when there are library functions that take/return such
2792 structures. There are very few such library functions. Currently this
2793 is known to affect @code{inet_ntoa}, @code{inet_lnaof},
2794 @code{inet_netof}, @code{inet_makeaddr}, and @code{semctl}. Until the
2795 bug is fixed, GCC contains workarounds for the known affected functions.
2797 See @uref{http://freeware.sgi.com/,,http://freeware.sgi.com/} for more
2798 information about using GCC on IRIX platforms.
2803 @heading @anchor{powerpc*-*-*}powerpc-*-*
2805 You can specify a default version for the @option{-mcpu=@var{cpu_type}}
2806 switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
2811 @heading @anchor{powerpc-*-darwin*}powerpc-*-darwin*
2812 PowerPC running Darwin (Mac OS X kernel).
2814 Pre-installed versions of Mac OS X may not include any developer tools,
2815 meaning that you will not be able to build GCC from source. Tool
2816 binaries are available at
2817 @uref{http://developer.apple.com/tools/compilers.html} (free
2818 registration required).
2820 The default stack limit of 512K is too small, which may cause compiles
2821 to fail with 'Bus error'. Set the stack larger, for instance
2822 by doing @samp{limit stack 800}. It's a good idea to use the GNU
2823 preprocessor instead of Apple's @file{cpp-precomp} during the first stage of
2824 bootstrapping; this is automatic when doing @samp{make bootstrap}, but
2825 to do it from the toplevel objdir you will need to say @samp{make
2826 CC='cc -no-cpp-precomp' bootstrap}.
2828 The version of GCC shipped by Apple typically includes a number of
2829 extensions not available in a standard GCC release. These extensions
2830 are generally specific to Mac programming.
2835 @heading @anchor{powerpc-*-elf}powerpc-*-elf, powerpc-*-sysv4
2836 PowerPC system in big endian mode, running System V.4.
2841 @heading @anchor{powerpc-*-linux-gnu*}powerpc-*-linux-gnu*
2844 @uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.13.90.0.10}
2845 or newer for a working GCC@.
2850 @heading @anchor{powerpc-*-netbsd*}powerpc-*-netbsd*
2851 PowerPC system in big endian mode running NetBSD@. To build the
2852 documentation you will need Texinfo version 4.2 (NetBSD 1.5.1 included
2853 Texinfo version 3.12).
2858 @heading @anchor{powerpc-*-eabisim}powerpc-*-eabisim
2859 Embedded PowerPC system in big endian mode for use in running under the
2865 @heading @anchor{powerpc-*-eabi}powerpc-*-eabi
2866 Embedded PowerPC system in big endian mode.
2871 @heading @anchor{powerpcle-*-elf}powerpcle-*-elf, powerpcle-*-sysv4
2872 PowerPC system in little endian mode, running System V.4.
2877 @heading @anchor{powerpcle-*-eabisim}powerpcle-*-eabisim
2878 Embedded PowerPC system in little endian mode for use in running under
2884 @heading @anchor{powerpcle-*-eabi}powerpcle-*-eabi
2885 Embedded PowerPC system in little endian mode.
2890 @heading @anchor{powerpcle-*-winnt}powerpcle-*-winnt, powerpcle-*-pe
2891 PowerPC system in little endian mode running Windows NT@.
2896 @heading @anchor{s390-*-linux*}s390-*-linux*
2897 S/390 system running Linux for S/390@.
2902 @heading @anchor{s390x-*-linux*}s390x-*-linux*
2903 zSeries system (64-bit) running Linux for zSeries@.
2908 @c Please use Solaris 2 to refer to all release of Solaris, starting
2909 @c with 2.0 until 2.6, 7, and 8. Solaris 1 was a marketing name for
2910 @c SunOS 4 releases which we don't use to avoid confusion. Solaris
2911 @c alone is too unspecific and must be avoided.
2912 @heading @anchor{*-*-solaris2*}*-*-solaris2*
2914 Sun does not ship a C compiler with Solaris 2. To bootstrap and install
2915 GCC you first have to install a pre-built compiler, see our
2916 @uref{binaries.html,,binaries page} for details.
2918 The Solaris 2 @command{/bin/sh} will often fail to configure
2919 @file{libstdc++-v3}, @file{boehm-gc} or @file{libjava}. We therefore
2920 recommend to set @env{CONFIG_SHELL} to @command{/bin/ksh} in your
2923 Solaris 2 comes with a number of optional OS packages. Some of these
2924 are needed to use GCC fully, namely @code{SUNWarc},
2925 @code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
2926 @code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
2927 optional packages when installing Solaris 2, you will need to verify that
2928 the packages that GCC needs are installed.
2930 To check whether an optional package is installed, use
2931 the @command{pkginfo} command. To add an optional package, use the
2932 @command{pkgadd} command. For further details, see the Solaris 2
2935 Trying to use the linker and other tools in
2936 @file{/usr/ucb} to install GCC has been observed to cause trouble.
2937 For example, the linker may hang indefinitely. The fix is to remove
2938 @file{/usr/ucb} from your @env{PATH}.
2940 All releases of GNU binutils prior to 2.11.2 have known bugs on this
2941 platform. We recommend the use of GNU binutils 2.11.2 or the vendor
2942 tools (Sun @command{as}, Sun @command{ld}).
2944 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
2945 newer: @command{g++} will complain that types are missing. These headers assume
2946 that omitting the type means @code{int}; this assumption worked for C89 but
2947 is wrong for C++, and is now wrong for C99 also.
2949 @command{g++} accepts such (invalid) constructs with the option
2950 @option{-fpermissive}; it
2951 will assume that any missing type is @code{int} (as defined by C89).
2953 There are patches for Solaris 2.6 (105633-56 or newer for SPARC,
2954 106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC,
2955 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
2956 108653-22 for Intel) that fix this bug.
2961 @heading @anchor{sparc-sun-solaris2*}sparc-sun-solaris2*
2963 When GCC is configured to use binutils 2.11.2 or later the binaries
2964 produced are smaller than the ones produced using Sun's native tools;
2965 this difference is quite significant for binaries containing debugging
2968 Sun @command{as} 4.x is broken in that it cannot cope with long symbol names.
2969 A typical error message might look similar to the following:
2972 /usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error:
2973 can't compute value of an expression involving an external symbol.
2976 This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris
2977 2.6 and has been fixed in later (5.x) versions of the assembler,
2978 starting with Solaris 7.
2980 Starting with Solaris 7, the operating system is capable of executing
2981 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
2982 this; the @option{-m64} option enables 64-bit code generation.
2983 However, if all you want is code tuned for the UltraSPARC CPU, you
2984 should try the @option{-mtune=ultrasparc} option instead, which produces
2985 code that, unlike full 64-bit code, can still run on non-UltraSPARC
2988 When configuring on a Solaris 7 or later system that is running a kernel
2989 that supports only 32-bit binaries, one must configure with
2990 @option{--disable-multilib}, since we will not be able to build the
2991 64-bit target libraries.
2996 @heading @anchor{sparc-sun-solaris2.7}sparc-sun-solaris2.7
2998 Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
2999 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
3000 and later, including all EGCS releases. Sun formerly recommended
3001 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
3002 recommend it only for people who use Sun's compilers.
3004 Here are some workarounds to this problem:
3007 Do not install Sun patch 107058-01 until after Sun releases a
3008 complete patch for bug 4210064. This is the simplest course to take,
3009 unless you must also use Sun's C compiler. Unfortunately 107058-01
3010 is preinstalled on some new Solaris 7-based hosts, so you may have to
3014 Copy the original, unpatched Solaris 7
3015 @command{/usr/ccs/bin/as} into
3016 @command{/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/3.1/as},
3017 adjusting the latter name to fit your local conventions and software
3021 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
3022 both 107058-01 and 106950-03 installed has reported the bug with GCC
3023 and Sun's dynamic linker. This last course of action is riskiest,
3024 for two reasons. First, you must install 106950 on all hosts that
3025 run code generated by GCC; it doesn't suffice to install it only on
3026 the hosts that run GCC itself. Second, Sun says that 106950-03 is
3027 only a partial fix for bug 4210064, but Sun doesn't know whether the
3028 partial fix is adequate for GCC@. Revision -08 or later should fix
3029 the bug. The current (as of 2001-09-24) revision is -14, and is included in
3030 the Solaris 7 Recommended Patch Cluster.
3033 GCC 3.3 triggers a bug in version 5.0 Alpha 03/27/98 of the Sun assembler,
3034 which causes a bootstrap failure when linking the 64-bit shared version of
3035 libgcc. A typical error message is:
3038 ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o:
3039 symbol <unknown>: offset 0xffffffff7ec133e7 is non-aligned.
3042 This bug has been fixed in the final 5.0 version of the assembler.
3047 @heading @anchor{sparc-*-linux*}sparc-*-linux*
3049 GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
3050 or newer on this platform. All earlier binutils and glibc
3051 releases mishandled unaligned relocations on @code{sparc-*-*} targets.
3057 @heading @anchor{sparc64-*-solaris2*}sparc64-*-solaris2*
3059 The following compiler flags must be specified in the configure
3060 step in order to bootstrap this target with the Sun compiler:
3063 % CC="cc -xildoff -xarch=v9" @var{srcdir}/configure [@var{options}] [@var{target}]
3066 @option{-xildoff} turns off the incremental linker, and @option{-xarch=v9}
3067 specifies the SPARC-V9 architecture to the Sun linker and assembler.
3072 @heading @anchor{sparcv9-*-solaris2*}sparcv9-*-solaris2*
3074 This is a synonym for sparc64-*-solaris2*.
3079 @heading @anchor{#*-*-sysv*}*-*-sysv*
3080 On System V release 3, you may get this error message
3084 ld fatal: failed to write symbol name @var{something}
3085 in strings table for file @var{whatever}
3088 This probably indicates that the disk is full or your ulimit won't allow
3089 the file to be as large as it needs to be.
3091 This problem can also result because the kernel parameter @code{MAXUMEM}
3092 is too small. If so, you must regenerate the kernel and make the value
3093 much larger. The default value is reported to be 1024; a value of 32768
3094 is said to work. Smaller values may also work.
3096 On System V, if you get an error like this,
3099 /usr/local/lib/bison.simple: In function `yyparse':
3100 /usr/local/lib/bison.simple:625: virtual memory exhausted
3104 that too indicates a problem with disk space, ulimit, or @code{MAXUMEM}.
3106 On a System V release 4 system, make sure @file{/usr/bin} precedes
3107 @file{/usr/ucb} in @code{PATH}. The @command{cc} command in
3108 @file{/usr/ucb} uses libraries which have bugs.
3113 @heading @anchor{vax-dec-ultrix}vax-dec-ultrix
3114 Don't try compiling with VAX C (@command{vcc}). It produces incorrect code
3115 in some cases (for example, when @code{alloca} is used).
3120 @heading @anchor{*-*-vxworks*}*-*-vxworks*
3121 Support for VxWorks is in flux. At present GCC supports @emph{only} the
3122 very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC.
3123 We welcome patches for other architectures supported by VxWorks 5.5.
3124 Support for VxWorks AE would also be welcome; we believe this is merely
3125 a matter of writing an appropriate ``configlette'' (see below). We are
3126 not interested in supporting older, a.out or COFF-based, versions of
3129 VxWorks comes with an older version of GCC installed in
3130 @file{@var{$WIND_BASE}/host}; we recommend you do not overwrite it.
3131 Choose an installation @var{prefix} entirely outside @var{$WIND_BASE}.
3132 Before running @command{configure}, create the directories @file{@var{prefix}}
3133 and @file{@var{prefix}/bin}. Link or copy the appropriate assembler,
3134 linker, etc. into @file{@var{prefix}/bin}, and set your @var{PATH} to
3135 include that directory while running both @command{configure} and
3138 You must give @command{configure} the
3139 @option{--with-headers=@var{$WIND_BASE}/target/h} switch so that it can
3140 find the VxWorks system headers. Since VxWorks is a cross compilation
3141 target only, you must also specify @option{--target=@var{target}}.
3142 @command{configure} will attempt to create the directory
3143 @file{@var{prefix}/@var{target}/sys-include} and copy files into it;
3144 make sure the user running @command{configure} has sufficient privilege
3147 GCC's exception handling runtime requires a special ``configlette''
3148 module, @file{contrib/gthr_supp_vxw_5x.c}. Follow the instructions in
3149 that file to add the module to your kernel build. (Future versions of
3150 VxWorks will incorporate this module.)
3155 @heading @anchor{xtensa-*-elf}xtensa-*-elf
3157 This target is intended for embedded Xtensa systems using the
3158 @samp{newlib} C library. It uses ELF but does not support shared
3159 objects. Designed-defined instructions specified via the
3160 Tensilica Instruction Extension (TIE) language are only supported
3161 through inline assembly.
3163 The Xtensa configuration information must be specified prior to
3164 building GCC@. The @file{gcc/config/xtensa/xtensa-config.h} header
3165 file contains the configuration information. If you created your
3166 own Xtensa configuration with the Xtensa Processor Generator, the
3167 downloaded files include a customized copy of this header file,
3168 which you can use to replace the default header file.
3173 @heading @anchor{xtensa-*-linux*}xtensa-*-linux*
3175 This target is for Xtensa systems running GNU/Linux. It supports ELF
3176 shared objects and the GNU C library (glibc). It also generates
3177 position-independent code (PIC) regardless of whether the
3178 @option{-fpic} or @option{-fPIC} options are used. In other
3179 respects, this target is the same as the
3180 @uref{#xtensa-*-elf,,@samp{xtensa-*-elf}} target.
3185 @heading @anchor{windows}Microsoft Windows (32-bit)
3187 A port of GCC 2.95.2 and 3.x is included with the
3188 @uref{http://www.cygwin.com/,,Cygwin environment}.
3190 Current (as of early 2001) snapshots of GCC will build under Cygwin
3191 without modification.
3193 GCC does not currently build with Microsoft's C++ compiler and there
3194 are no plans to make it do so.
3199 @heading @anchor{os2}OS/2
3201 GCC does not currently support OS/2. However, Andrew Zabolotny has been
3202 working on a generic OS/2 port with pgcc. The current code can be found
3203 at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
3205 An older copy of GCC 2.8.1 is included with the EMX tools available at
3206 @uref{ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/,,
3207 ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/}.
3212 @heading @anchor{older}Older systems
3214 GCC contains support files for many older (1980s and early
3215 1990s) Unix variants. For the most part, support for these systems
3216 has not been deliberately removed, but it has not been maintained for
3217 several years and may suffer from bitrot.
3219 Starting with GCC 3.1, each release has a list of ``obsoleted'' systems.
3220 Support for these systems is still present in that release, but
3221 @command{configure} will fail unless the @option{--enable-obsolete}
3222 option is given. Unless a maintainer steps forward, support for these
3223 systems will be removed from the next release of GCC@.
3225 Support for old systems as hosts for GCC can cause problems if the
3226 workarounds for compiler, library and operating system bugs affect the
3227 cleanliness or maintainability of the rest of GCC@. In some cases, to
3228 bring GCC up on such a system, if still possible with current GCC, may
3229 require first installing an old version of GCC which did work on that
3230 system, and using it to compile a more recent GCC, to avoid bugs in the
3231 vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
3232 @file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror
3233 sites}. Header bugs may generally be avoided using
3234 @command{fixincludes}, but bugs or deficiencies in libraries and the
3235 operating system may still cause problems.
3237 Support for older systems as targets for cross-compilation is less
3238 problematic than support for them as hosts for GCC; if an enthusiast
3239 wishes to make such a target work again (including resurrecting any of
3240 the targets that never worked with GCC 2, starting from the last CVS
3241 version before they were removed), patches
3242 @uref{../contribute.html,,following the usual requirements} would be
3243 likely to be accepted, since they should not affect the support for more
3246 For some systems, old versions of GNU binutils may also be useful,
3247 and are available from @file{pub/binutils/old-releases} on
3248 @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}.
3250 Some of the information on specific systems above relates to
3251 such older systems, but much of the information
3252 about GCC on such systems (which may no longer be applicable to
3253 current GCC) is to be found in the GCC texinfo manual.
3258 @heading @anchor{elf_targets}all ELF targets (SVR4, Solaris 2, etc.)
3260 C++ support is significantly better on ELF targets if you use the
3261 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
3262 inlines, vtables and template instantiations will be discarded
3271 @uref{./index.html,,Return to the GCC Installation page}
3275 @c ***Old documentation******************************************************
3277 @include install-old.texi
3283 @uref{./index.html,,Return to the GCC Installation page}
3287 @c ***GFDL********************************************************************
3295 @uref{./index.html,,Return to the GCC Installation page}
3299 @c ***************************************************************************
3300 @c Part 6 The End of the Document
3302 @comment node-name, next, previous, up
3303 @node Concept Index, , GNU Free Documentation License, Top
3307 @unnumbered Concept Index