1 \input texinfo.tex @c -*-texinfo-*-
4 @setfilename install.info
5 @settitle Installing GCC
10 @c Specify title for specific html page
12 @settitle Installing GCC
15 @settitle Host/Target specific installation notes for GCC
18 @settitle Downloading GCC
21 @settitle Installing GCC: Configuration
24 @settitle Installing GCC: Building
27 @settitle Installing GCC: Testing
29 @ifset finalinstallhtml
30 @settitle Installing GCC: Final installation
33 @settitle Installing GCC: Binaries
36 @comment $Id: install.texi,v 1.19 2001/06/11 21:29:37 mmitchel Exp $
37 @c Copyright (C) 2001 Free Software Foundation, Inc.
38 @c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com
40 @c Include everything if we're not making html
52 @c Part 2 Summary Description and Copyright
55 Copyright @copyright{} 2001 Free Software Foundation, Inc.
58 @c Part 3 Titlepage and Copyright
61 @comment The title is printed in a large font.
62 @center @titlefont{Installing GCC}
64 @c The following two commands start the copyright page.
66 @vskip 0pt plus 1filll
67 Copyright @copyright{} 2001 Free Software Foundation, Inc.
70 @c Part 4 Top node and Master Menu
73 @comment node-name, next, Previous, up
76 * Installing GCC:: This document describes the generic installation
77 procedure for GCC as well as detailing some target
78 specific installation instructions.
80 * Specific:: Host/target specific installation notes for GCC.
81 * Binaries:: Where to get pre-compiled binaries.
83 * Concept Index:: This index has two entries.
87 @c Part 5 The Body of the Document
88 @c ***Installing GCC**********************************************************
90 @comment node-name, next, previous, up
91 @node Installing GCC, Binaries, , Top
95 <h1 align="center">Installing GCC</h1>
98 @chapter Installing GCC
101 The latest version of this document is always available at
102 @uref{http://gcc.gnu.org/install/,,http://gcc.gnu.org/install/}.
104 This document describes the generic installation procedure for GCC as well
105 as detailing some target specific installation instructions.
107 GCC includes several components that previously were separate distributions
108 with their own installation instructions. This document supersedes all
109 package specific installation instructions. We provide the component
110 specific installation information in the source distribution for historical
111 reference purposes only.
113 @emph{Before} starting the build/install procedure please check the
115 @xref{Specific, host/target specific installation notes}.
118 @uref{specific.html,,host/target specific installation notes}.
120 We recommend you browse the entire generic installation instructions before
123 The installation procedure itself is broken into five steps.
127 * Downloading the source::
130 * Testing:: (optional)
137 @uref{download.html,,Downloading the source}
139 @uref{configure.html,,Configuration}
141 @uref{build.html,,Building}
143 @uref{test.html,,Testing} (optional)
145 @uref{finalinstall.html,,Final install}
149 Please note that GCC does not support @samp{make uninstall} and probably
150 won't do so in the near future as this would open a can of worms. Instead,
151 we suggest that you install GCC into a directory of its own and simply
152 remove that directory when you do not need that specific version of GCC
160 @uref{./index.html,,Return to the GCC Installation page}
164 @c ***Downloading the source**************************************************
166 @comment node-name, next, previous, up
167 @node Downloading the source, Configuration, , Installing GCC
171 <h1 align="center">Downloading GCC</h1>
174 @chapter Downloading GCC
176 @cindex Downloading GCC
177 @cindex Downloading the Source
179 GCC is distributed via CVS and FTP tarballs compressed with gzip or
180 bzip2. It is possible to download a full distribution or specific
183 Please refer to our @uref{http://gcc.gnu.org/releases.html,,releases web page}
184 for information on how to obtain GCC.
186 The full distribution includes the C, C++, Objective-C, Fortran, Java,
187 and Chill compilers. The full distribution also includes runtime libraries
188 for C++, Objective-C, Fortran, Java and Chill. (GCC 3.0 does not
189 include Chill. Releases before 3.0 do not include the Java runtime
190 library.) In GCC 3.0 and later versions, GNU compiler testsuites
191 are also included in the full distribution.
193 If you choose to download specific components, you must download the core
194 gcc distribution plus any language specific distributions you wish to
195 use. The core distribution includes the C language front-end as well as the
196 shared components. Each language has a tarball which includes the language
197 front-end as well as the language runtime (when appropriate).
199 Unpack the core distribution as well as any language specific
200 distributions in the same directory.
202 If you also intend to build binutils (either to upgrade an existing
203 installation or for use in place of the corresponding tools of your
204 OS), unpack the binutils distribution either in the same directory or
205 a separate one. In the latter case, add symbolic links to any
206 components of the binutils you intend to build alongside the compiler
207 (bfd, binutils, gas, gprof, ld, opcodes,...) to the directory containing
215 @uref{./index.html,,Return to the GCC Installation page}
219 @c ***Configuration***********************************************************
221 @comment node-name, next, previous, up
222 @node Configuration, Building, Downloading the source, Installing GCC
226 <h1 align="center">Installing GCC: Configuration</h1>
229 @chapter Installing GCC: Configuration
231 @cindex Configuration
232 @cindex Installing GCC: Configuration
234 Like most GNU software, GCC must be configured before it can be built.
235 This document describes the recommended configuration procedure
236 for both native and cross targets.
238 We use @var{srcdir} to refer to the toplevel source directory for
239 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
241 If you obtained the sources via CVS, @var{srcdir} must refer to the top
242 @file{gcc} directory, the one where the @file{MAINTAINERS} can be found,
243 and not its @file{gcc} subdirectory, otherwise the build will fail.
245 First, we @strong{highly} recommend that GCC be built into a
246 separate directory than the sources which does @strong{not} reside
247 within the source tree. This is how we generally build GCC; building
248 where @var{srcdir} == @var{objdir} should still work, but doesn't
249 get extensive testing; building where @var{objdir} is a subdirectory
250 of @var{srcdir} is unsupported.
252 If you have built GNU CC previously in the same directory for a
253 different target machine, do @samp{make distclean} to delete all files
254 that might be invalid. One of the files this deletes is
255 @file{Makefile}; if @samp{make distclean} complains that @file{Makefile}
256 does not exist, it probably means that the directory is already suitably
257 clean. However, with the recommended method of building in a separate
258 @var{objdir}, you should simply use a different @var{objdir} for each
261 Second, when configuring a native system, either @command{cc} or
262 @command{gcc} must be in your path or you must set @env{CC} in
263 your environment before running configure. Otherwise the configuration
271 % @var{srcdir}/configure [@var{target}] [@var{options}]
275 @heading Target specification
278 GCC has code to correctly determine the correct value for @var{target}
279 for nearly all native systems. Therefore, we highly recommend you not
280 provide a configure target when configuring a native compiler.
283 @var{target} must be specified as @option{--target=}@var{target}
284 when configuring a cross compiler; examples of valid targets would be
285 i960-rtems, m68k-coff, sh-elf, etc.
288 Specifying just @var{target} instead of @option{--target=}@var{target}
289 implies that the host defaults to @var{target}.
293 @heading Options specification
295 Use @var{options} to override several configure time options for
296 GCC. A partial list of supported @var{options}:
299 @item --prefix=@var{dirname}
300 Specify the toplevel installation
301 directory. This is the recommended way to install the tools into a directory
302 other than the default. The toplevel installation directory defaults to
305 We @strong{highly} recommend against @var{dirname} being the same or a
306 subdirectory of @var{objdir} or vice versa.
308 These additional options control where certain parts of the distribution
309 are installed. Normally you should not need to use these options.
312 @item --exec-prefix=@var{dirname}
313 Specify the toplevel installation directory for architecture-dependent
314 files. The default is @file{@var{prefix}}.
316 @item --bindir=@var{dirname}
317 Specify the installation directory for the executables called by users
318 (such as @command{gcc} and @command{g++}). The default is
319 @file{@var{exec-prefix}/bin}.
321 @item --libdir=@var{dirname}
322 Specify the installation directory for object code libraries and
323 internal parts of GCC. The default is @file{@var{exec-prefix}/lib}.
325 @item --with-slibdir=@var{dirname}
326 Specify the installation directory for the shared libgcc library. The
327 default is @file{@var{libdir}}.
329 @item --infodir=@var{dirname}
330 Specify the installation directory for documentation in info format.
331 The default is @file{@var{prefix}/info}.
333 @item --mandir=@var{dirname}
334 Specify the installation directory for manual pages. The default is
335 @file{@var{prefix}/man}. (Note that the manual pages are only extracts from
336 the full GCC manuals, which are provided in Texinfo format. The
337 @command{g77} manpage is unmaintained and may be out of date; the others
338 are derived by an automatic conversion process from parts of the full
341 @item --with-gxx-include-dir=@var{dirname}
343 the installation directory for g++ header files. The default is
344 @file{@var{prefix}/include/g++-v3}.
348 @item --with-local-prefix=@var{dirname}
350 installation directory for local include files. The default is
351 @file{/usr/local}. Specify this option if you want the compiler to
352 search directory @file{@var{dirname}/include} for locally installed
353 header files @emph{instead} of @file{/usr/local/include}.
355 You should specify @option{--with-local-prefix} @strong{only} if your
356 site has a different convention (not @file{/usr/local}) for where to put
359 The default value for @option{--with-local-prefix} is @file{/usr/local}
360 regardless of the value of @option{--prefix}. Specifying
361 @option{--prefix} has no effect on which directory GCC searches for
362 local header files. This may seem counterintuitive, but actually it is
365 The purpose of @option{--prefix} is to specify where to @emph{install
366 GCC}. The local header files in @file{/usr/local/include}---if you put
367 any in that directory---are not part of GCC. They are part of other
368 programs---perhaps many others. (GCC installs its own header files in
369 another directory which is based on the @option{--prefix} value.)
371 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
372 The directory you use for @option{--with-local-prefix} @strong{must not}
373 contain any of the system's standard header files. If it did contain
374 them, certain programs would be miscompiled (including GNU Emacs, on
375 certain targets), because this would override and nullify the header
376 file corrections made by the @code{fixincludes} script.
378 Indications are that people who use this option use it based on mistaken
379 ideas of what it is for. People use it as if it specified where to
380 install part of GCC. Perhaps they make this assumption because
381 installing GCC creates the directory.
383 @item --enable-shared
384 Build shared versions of the
385 C++ runtime libraries if supported. This is the default on most
386 systems. Use @option{--disable-shared} for static libraries. Note that
387 up to the gcc version 2.95.x series, static libraries were the default
390 @item @anchor{with-gnu-as}--with-gnu-as
391 Specify that the compiler should assume that the
392 assembler it finds is the GNU assembler. However, this does not modify
393 the rules to find an assembler and will result in confusion if found
394 assembler is not actually the GNU assembler. If you have more than one
395 assembler installed on your system, you may want to use this option in
396 connection with @option{--with-as=@file{/path/to/gas}}.
398 @item --with-as=@file{/path/to/as}
400 compiler should use the assembler pointed to by @var{pathname}, rather
401 than the one found by the standard rules to find an assembler, which
406 @file{@var{exec_prefix}/lib/gcc-lib/@var{target}/@var{version}}
407 directory, where @var{exec_prefix} defaults to @var{prefix} which
408 defaults to @file{/usr/local} unless overridden by the
409 @option{--prefix=/pathname} switch described above. @var{target} is the
410 target system triple, such as @var{sparc-sun-solaris2.7}, and
411 @var{version} denotes the GCC version, such as 2.95.2.
413 Check operating system specific directories (e.g. @file{/usr/ccs/bin} on
416 Note that these rules do not check for the value of @env{PATH}. You may
417 want to use @option{--with-as} if no assembler is installed in the
418 directories listed above, or if you have multiple assemblers installed
419 and want to choose one that is not found by the above rules.
421 @item @anchor{with-gnu-ld}--with-gnu-ld
422 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
426 @item --with-ld=@file{/path/to/ld}
428 @option{--with-as}, but for the linker.
431 Specify that stabs debugging
432 information should be used instead of whatever format the host normally
433 uses. Normally GCC uses the same debug format as the host system.
435 @item --enable-multilib
436 Specify that multiple target
437 libraries should be built to support different target variants, calling
438 conventions, etc. This is the default.
440 @item --enable-threads
441 Specify that the target
442 supports threads. This affects the Objective-C compiler and runtime
443 library, and exception handling for other languages like C++ and Java.
444 On some systems, this is the default.
446 @item --enable-threads=@var{lib}
448 @var{lib} is the thread support library. This affects the Objective-C
449 compiler and runtime library, and exception handling for other languages
450 like C++ and Java. The possibilities for @var{lib} are:
458 DEC OSF/1 thread support.
460 SGI IRIX thread support.
462 Generic MACH thread support, known to work on NEXTSTEP.
464 IBM OS/2 thread support.
466 Generix POSIX thread support.
468 Same as @samp{posix}.
470 Disable thread support, should work for all platforms.
472 SUN Solaris thread support.
474 VxWorks thread support.
476 Microsoft Win32 API thread support.
479 @item --with-cpu=@var{cpu}
480 Specify which cpu variant the
481 compiler should generate code for by default. This is currently
482 only supported on the some ports, specifically arm, powerpc, and
483 SPARC. If configure does not recognize the model name (e.g. arm700,
484 603e, or ultrasparc) you provide, please check the configure script
485 for a complete list of supported models.
487 @item --enable-target-optspace
489 libraries should be optimized for code space instead of code speed.
490 This is the default for the m32r platform.
493 Specify that a user visible @command{cpp} program should not be installed.
495 @item --with-cpp-install-dir=@var{dirname}
496 Specify that the user visible @command{cpp} program should be installed
497 in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
499 @item --enable-maintainer-mode
501 regenerate the GCC master message catalog @code{gcc.pot} are normally
502 disabled. This is because it can only be rebuilt if the complete source
503 tree is present. If you have changed the sources and want to rebuild the
504 catalog, configuring with @option{--enable-maintainer-mode} will enable
505 this. Note that you need a recent version of the @code{gettext} tools
508 @item --enable-version-specific-runtime-libs
510 that runtime libraries should be installed in the compiler specific
511 subdirectory (@file{@var{libsubdir}}) rather than the usual places. In
512 addition, libstdc++'s include files will be installed in
513 @file{@var{libsubdir}/include/g++} unless you overruled it by using
514 @option{--with-gxx-include-dir=}@var{dirname}. Using this option is
515 particularly useful if you intend to use several versions of GCC in
516 parallel. This is currently supported by @option{libf2c} and
519 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
520 Specify that only a particular subset of compilers and
521 their runtime libraries should be built. For a list of valid values for
522 @var{lang}@option{x} you can issue the following command in the
523 @file{gcc} directory of your GCC source tree:@* @samp{grep language=
524 */config-lang.in}@* Currently, you can use any of the following:
525 @code{c++}, @code{f77}, @code{java} and @code{objc}.
526 @code{CHILL} is not currently maintained, and will almost
527 certainly fail to compile. Note that this switch does not work with
528 EGCS 1.1.2 or older versions of egcs. It is supported in GCC 2.95
529 and newer versions.@*
530 If you do not pass this flag, all languages available in the @file{gcc}
531 sub-tree will be configured. Re-defining LANGUAGES when calling
532 @samp{make bootstrap} @strong{does not} work anymore, as those
533 language sub-directories might not have been configured!
535 @item --disable-libgcj
536 Specify that the run-time libraries
537 used by GCJ should not be built. This is useful in case you intend
538 to use GCJ with some other run-time, or you're going to install it
539 separately, or it just happens not to build on your particular
540 machine. In general, if the Java front-end is enabled, the GCJ
541 libraries will be enabled too, unless they're known to not work on
542 the target platform. If GCJ is enabled but libgcj isn't built, you
543 may need to port it; in this case, before modifying the top-level
544 configure.in so that libgcj is enabled by default on this platform,
545 you may use @option{--enable-libgcj} to override the default.
548 Specify that the compiler should
549 use DWARF2 debugging information as the default.
551 @item --enable-win32-registry
552 @itemx --enable-win32-registry=@var{KEY}
553 @itemx --disable-win32-registry
554 The @samp{--enable-win32-registry} option enables Windows-hosted GCC
555 to look up installations paths in the registry using the following key:
558 @code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\<KEY>}
561 <KEY> defaults to GCC version number, and can be overridden by the
562 @code{--enable-win32-registry=KEY} option. Vendors and distributors
563 who use custom installers are encouraged to provide a different key,
564 perhaps one comprised of vendor name and GCC version number, to
565 avoid conflict with existing installations. This feature is enabled
566 by default, and can be disabled by @code{--disable-win32-registry}
567 option. This option has no effect on the other hosts.
570 Specify that the machine does not have a floating point unit. This
571 option only applies to @samp{m68k-sun-sunos@var{n}} and
572 @samp{m68k-isi-bsd}. On any other system, @samp{--nfp} has no effect.
574 @item --enable-checking
575 @itemx --enable-checking=@var{list}
576 When you specify this option, the compiler is built to perform checking
577 of tree node types when referencing fields of that node, and some other
578 internal consistency checks. This does not change the generated code,
579 but adds error checking within the compiler. This will slow down the
580 compiler and may only work properly if you are building the compiler
581 with GNU C. This is on by default when building from CVS or snapshots,
582 but off for releases. More control over the checks may be had by
583 specifying @var{list}; the categories of checks available are
584 @samp{misc}, @samp{tree}, @samp{gc}, @samp{rtl} and @samp{gcac}. The
585 default when @var{list} is not specified is @samp{misc,tree,gc}; the
586 checks @samp{rtl} and @samp{gcac} are very expensive.
590 The @samp{--enable-nls} option enables Native Language Support (NLS),
591 which lets GCC output diagnostics in languages other than American
592 English. Native Language Support is enabled by default if not doing a
593 canadian cross build. The @samp{--disable-nls} option disables NLS.
595 @item --with-included-gettext
596 If NLS is enbled, the @samp{--with-included-gettext} option causes the build
597 procedure to prefer its copy of GNU @code{gettext}.
600 If NLS is enabled, and if the host lacks @code{gettext} but has the
601 inferior @code{catgets} interface, the GCC build procedure normally
602 ignores @code{catgets} and instead uses GCC's copy of the GNU
603 @code{gettext} library. The @samp{--with-catgets} option causes the
604 build procedure to use the host's @code{catgets} in this situation.
607 Some options which only apply to building cross compilers:
609 @item --with-headers=@var{dir}
610 Specifies a directory
611 which has target include files.
612 @emph{This options is required} when building a cross
613 compiler, if @file{@var{prefix}/@var{target}/sys-include} doesn't pre-exist.
614 These include files will be copied into the @file{gcc} install directory.
615 Fixincludes will be run on these files to make them compatible with
617 @item --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
618 Specifies a list of directories which contain the target runtime
619 libraries. These libraries will be copied into the @file{gcc} install
622 Specifies that ``newlib'' is
623 being used as the target C library. This causes @code{__eprintf} to be
624 omitted from libgcc.a on the assumption that it will be provided by
628 Note that each @option{--enable} option has a corresponding
629 @option{--disable} option and that each @option{--with} option has a
630 corresponding @option{--without} option.
637 @uref{./index.html,,Return to the GCC Installation page}
641 @c ***Building****************************************************************
643 @comment node-name, next, previous, up
644 @node Building, Testing, Configuration, Installing GCC
648 <h1 align="center">Installing GCC: Building</h1>
653 @cindex Installing GCC: Building
655 Now that GCC is configured, you are ready to build the compiler and
658 We @strong{highly} recommend that GCC be built using GNU make;
659 other versions may work, then again they might not.
661 (For example, many broken versions of make will fail if you use the
662 recommended setup where @var{objdir} is different from @var{srcdir}.
663 Other broken versions may recompile parts of the compiler when
664 installing the compiler.)
666 Some commands executed when making the compiler may fail (return a
667 non-zero status) and be ignored by @code{make}. These failures, which
668 are often due to files that were not found, are expected, and can safely
671 It is normal to have compiler warnings when compiling certain files.
672 Unless you are a GCC developer, you can generally ignore these warnings
673 unless they cause compilation to fail.
675 On certain old systems, defining certain environment variables such as
676 @code{CC} can interfere with the functioning of @code{make}.
678 If you encounter seemingly strange errors when trying to build the
679 compiler in a directory other than the source directory, it could be
680 because you have previously configured the compiler in the source
681 directory. Make sure you have done all the necessary preparations.
683 If you build GCC on a BSD system using a directory stored in an old System
684 V file system, problems may occur in running @code{fixincludes} if the
685 System V file system doesn't support symbolic links. These problems
686 result in a failure to fix the declaration of @code{size_t} in
687 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
688 that type mismatches occur, this could be the cause.
690 The solution is not to use such a directory for building GCC.
692 When building from CVS or snapshots, or if you modify parser sources,
693 you need the Bison parser generator installed. Any version 1.25 or
694 later should work; older versions may also work. If you do not modify
695 parser sources, releases contain the Bison-generated files and you do
696 not need Bison installed to build them.
698 When building from CVS or snapshots, or if you modify Texinfo
699 documentation, you need version 4.0 or later of Texinfo installed if you
700 want Info documentation to be regenerated. Releases contain Info
701 documentation pre-built for the unmodified documentation in the release.
703 @section Building a native compiler
705 For a native build issue the command @samp{make bootstrap}. This
706 will build the entire GCC system, which includes the following steps:
710 Build host tools necessary to build the compiler such as texinfo, bison,
714 Build target tools for use by the compiler such as binutils (bfd,
715 binutils, gas, gprof, ld, and opcodes)@*
716 if they have been individually linked
717 or moved into the top level GCC source tree before configuring.
720 Perform a 3-stage bootstrap of the compiler.
723 Perform a comparison test of the stage2 and stage3 compilers.
726 Build runtime libraries using the stage3 compiler from the previous step.
730 If you are short on disk space you might consider @samp{make
731 bootstrap-lean} instead. This is identical to @samp{make
732 bootstrap} except that object files from the stage1 and
733 stage2 of the 3-stage bootstrap of the compiler are deleted as
734 soon as they are no longer needed.
737 If you want to save additional space during the bootstrap and in
738 the final installation as well, you can build the compiler binaries
739 without debugging information with @samp{make CFLAGS='-O' LIBCFLAGS='-g
740 -O2' LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap}. This will save
741 roughly 40% of disk space both for the bootstrap and the final installation.
742 (Libraries will still contain debugging information.)
744 If you wish to use non-default flags when compiling the stage2 and
745 stage3 compile, set @code{BOOT_CFLAGS} on the command line when doing
746 @samp{make bootstrap}. Non-default optimization flags are less well
747 tested here than the default of @samp{-g -O2}, but should still work.
748 In a few cases, you may find that you need to specify special flags such
749 as @option{-msoft-float} here to complete the bootstrap; or, if the
750 native compiler miscompiles the stage1 compiler, you may need to work
751 around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the
752 stage1 compiler that were miscompiled, or by using @samp{make
753 bootstrap4} to increase the number of stages of bootstrap.
755 If you used the flag @option{--enable-languages=...} to restrict
756 the compilers to be built, only those you've actually enabled will be
757 built. This will of course only build those runtime libraries, for
758 which the particular compiler has been built. Please note,
759 that re-defining LANGUAGES when calling @samp{make bootstrap}
760 @strong{does not} work anymore!
762 If the comparison of stage2 and stage3 fails, this normally indicates
763 that the stage 2 compiler has compiled GCC incorrectly, and is therefore
764 a potentially serious bug which you should investigate and report. (On
765 a few systems, meaningful comparison of object files is impossible; they
766 always appear ``different''. If you encounter this problem, you will
767 need to disable comparison in the @file{Makefile}.)
769 @section Building a cross compiler
771 We recommend reading the
772 @uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ}
773 for information about building cross compilers.
775 When building a cross compiler, it is not generally possible to do a
776 3-stage bootstrap of the compiler. This makes for an interesting problem
777 as parts of GCC can only be built with GCC.
779 To build a cross compiler, we first recommend building and installing a
780 native compiler. You can then use the native GCC compiler to build the
783 Assuming you have already installed a native copy of GCC and configured
784 your cross compiler, issue the command @samp{make}, which performs the
789 Build host tools necessary to build the compiler such as texinfo, bison,
793 Build target tools for use by the compiler such as binutils (bfd,
794 binutils, gas, gprof, ld, and opcodes)
795 if they have been individually linked or moved into the top level GCC source
796 tree before configuring.
799 Build the compiler (single stage only).
802 Build runtime libraries using the compiler from the previous step.
805 Note that if an error occurs in any step the make process will exit.
807 @section Building in parallel
809 If you have a multiprocessor system you can use @samp{make bootstrap
810 MAKE="make -j 2" -j 2} or just @samp{make -j 2 bootstrap}
811 for GNU Make 3.79 and above instead of just @samp{make bootstrap}
812 when building GCC. You can use a bigger number instead of two if
813 you like. In most cases, it won't help to use a number bigger than
814 the number of processors in your machine.
821 @uref{./index.html,,Return to the GCC Installation page}
825 @c ***Testing*****************************************************************
827 @comment node-name, next, previous, up
828 @node Testing, Final install, Building, Installing GCC
832 <h1 align="center">Installing GCC: Testing</h1>
835 @chapter Installing GCC: Testing
838 @cindex Installing GCC: Testing
841 @strong{Please note that this is only applicable
842 to current development versions of GCC and GCC 3.0 or later.
843 GCC 2.95.x does not come with a testsuite.}
845 Before you install GCC, you might wish to run the testsuite. This
846 step is optional and may require you to download additional software.
848 First, you must have @uref{download.html,,downloaded the testsuites}.
849 The full distribution contains testsuites; only if you downloaded the
850 ``core'' compiler plus any front ends, you do not have the testsuites.
852 Second, you must have a @uref{http://www.gnu.org/software/dejagnu/,,current version of DejaGnu} installed;
853 dejagnu 1.3 is not sufficient.
855 Now you may need specific preparations:
859 In order to run the libio tests in GCC 2.95 and earlier versions of GCC
860 on targets which do not fully
861 support Unix/POSIX commands (e.g. Cygwin), the references to the dbz
862 directory have to be deleted from @code{libio/configure.in}.
865 The following environment variables may need to be set appropriately, as in
866 the following example (which assumes that DejaGnu has been installed
867 under @code{/usr/local}):
870 TCL_LIBRARY = /usr/local/share/tcl8.0
871 DEJAGNULIBS = /usr/local/share/dejagnu
874 On systems such as Cygwin, these paths are required to be actual
875 paths, not mounts or links; presumably this is due to some lack of
876 portability in the DejaGnu code.
878 If the directories where @command{runtest} and @command{expect} were
879 installed are in the @env{PATH}, it should not be necessary to set these
880 environment variables.
884 Finally, you can run the testsuite (which may take a long time):
886 cd @var{objdir}; make -k check
889 The testing process will try to test as many components in the GCC
890 distribution as possible, including the C, C++, Objective C and Fortran
891 compilers as well as the C++ and Java runtime libraries.
893 @section How can I run the test suite on selected tests?
895 As a first possibility to cut down the number of tests that are run it is
896 possible to use @samp{make check-gcc} or @samp{make check-g++}
897 in the gcc subdirectory of the object directory. To further cut down the
898 tests the following is possible:
901 make check-gcc RUNTESTFLAGS="execute.exp <other options>"
904 This will run all gcc execute tests in the testsuite.
907 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* <other options>"
910 This will run the g++ "old-deja" tests in the testsuite where the filename
913 The *.exp files are located in the testsuite directories of the GCC
914 source, the most important ones being compile.exp, execute.exp, dg.exp
915 and old-deja.exp. To get a list of the possible *.exp files, pipe the
916 output of @samp{make check} into a file and look at the
917 @samp{Running ... .exp} lines.
919 @section How to interpret test results
921 After the testsuite has run you'll find various *.sum and *.log
922 files in the testsuite subdirectories. The *.log files contain a
923 detailed log of the compiler invocations and the corresponding
924 results, the *.sum files summarize the results. These summaries list
925 all the tests that have been run with a corresponding status code:
929 PASS: the test passed as expected
931 XPASS: the test unexpectedly passed
933 FAIL: the test unexpectedly failed
935 XFAIL: the test failed as expected
937 UNSUPPORTED: the test is not supported on this platform
939 ERROR: the testsuite detected an error
941 WARNING: the testsuite detected a possible problem
944 It is normal for some tests to report unexpected failures. At the
945 current time our testing harness does not allow fine grained control
946 over whether or not a test is expected to fail. We expect to fix this
947 problem in future releases.
950 @section Submitting test results
952 If you want to report the results to the GCC project, use the
953 @code{contrib/test_summary} shell script. Start it in the @var{objdir} with
956 @var{srcdir}/contrib/test_summary -p your_commentary.txt -m gcc-testresults@@gcc.gnu.org |sh
959 This script uses the @code{Mail} program to send the results, so
960 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
961 prepended to the testsuite summary and should contain any special
962 remarks you have on your results or your build environment. Please
963 do not edit the testsuite result block or the subject line, as these
964 messages are automatically parsed and presented at the
965 @uref{http://gcc.gnu.org/testresults/,,GCC testresults} web
966 page. Here you can also gather information on how specific tests
967 behave on different platforms and compare them with your results. A
968 few failing testcases are possible even on released versions and you
969 should look here first if you think your results are unreasonable.
973 @c ***Final install***********************************************************
975 @comment node-name, next, previous, up
976 @node Final install, , Testing, Installing GCC
978 @ifset finalinstallhtml
980 <h1 align="center">Installing GCC: Final installation</h1>
983 @chapter Installing GCC: Final installation
986 Now that GCC has been built and tested, you can install it with
987 @samp{cd @var{objdir}; make install}.
989 That step completes the installation of GCC; user level binaries can
990 be found in @file{@var{prefix}/bin} where @var{prefix} is the value you
991 specified with the @option{--prefix} to configure (or @file{/usr/local}
992 by default). (If you specified @option{--bindir}, that directory will
993 be used instead; otherwise, if you specified @option{--exec-prefix},
994 @file{@var{exec-prefix}/bin} will be used.) Headers for the C++ and
995 Java libraries are installed in @file{@var{prefix}/include}; libraries
996 in @file{@var{libdir}} (normally @file{@var{prefix}/lib}); internal
997 parts of the compiler in @file{@var{libdir}/gcc-lib}; documentation in
998 info format in @file{@var{infodir}} (normally @file{@var{prefix}/info}).
1000 If you don't mind, please quickly review the
1001 @uref{http://gcc.gnu.org/gcc-3.0/buildstat.html,,build status page}.
1002 If your system is not listed, send a note to
1003 @uref{mailto:gcc@@gcc.gnu.org,,gcc@@gcc.gnu.org} indicating
1004 that you successfully built and installed GCC.
1006 Include the output from running @file{@var{srcdir}/config.guess}. (Do
1007 not send us the config.guess file itself, just the one-line output from
1010 If you find a bug, please report it following our
1011 @uref{../bugs.html,,bug reporting guidelines}.
1013 If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
1014 dvi}. You will need to have @command{texi2dvi} (version at least 4.0)
1015 and @TeX{} installed. This creates a number of @file{.dvi} files in
1016 subdirectories of @file{@var{objdir}}; these may be converted for
1017 printing with programs such as @command{dvips}. You can also
1018 @uref{http://www.gnu.org/order/order.html,,buy printed manuals from the
1019 Free Software Foundation}, though such manuals may not be for the most
1020 recent version of GCC.
1027 @uref{./index.html,,Return to the GCC Installation page}
1031 @c ***Binaries****************************************************************
1033 @comment node-name, next, previous, up
1034 @node Binaries, Specific, Installing GCC, Top
1038 <h1 align="center">Installing GCC: Binaries</h1>
1041 @chapter Installing GCC: Binaries
1044 @cindex Installing GCC: Binaries
1046 We are often asked about pre-compiled versions of GCC. While we cannot
1047 provide these for all platforms, below you'll find links to binaries for
1048 various platforms where creating them by yourself is not easy due to various
1051 Please note that we did not create these binaries, nor do we
1052 support them. If you have any problems installing them, please
1053 contact their makers.
1060 @uref{http://www-frec.bull.com/docs/download.htm,,Bull's Freeware and
1061 Shareware Archive for AIX};
1064 @uref{http://aixpdlib.seas.ucla.edu,,UCLA Software Library for AIX};
1068 DOS - @uref{http://www.delorie.com/djgpp/,,DJGPP};
1071 @uref{http://hpux.cae.wisc.edu/,,HP-UX Porting Center};
1074 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
1075 OpenServer/Unixware};
1078 Solaris (SPARC, Intel) - @uref{http://www.sunfreeware.com/,,Sunfreeware};
1081 SGI - @uref{http://freeware.sgi.com/,,SGI Freeware};
1084 Windows 95, 98, and NT:
1087 The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project;
1089 @uref{http://www.xraylith.wisc.edu/~khan/software/gnu-win32/,,GNU Win32}
1090 related projects by Mumit Khan.
1094 @uref{ftp://ftp.thewrittenword.com/packages/free/by-name/gcc-2.95.2/,,The
1095 Written Word} offers binaries for Solaris 2.5.1, 2.6, 2.7/SPARC, 2.7/Intel,
1096 IRIX 6.2, 6.5, Digital UNIX 4.0D, HP-UX 10.20, and HP-UX 11.00.
1099 Hitachi H8/300[HS] -
1100 @uref{http://h8300-hms.sourceforge.net/,,GNU Development Tools for the
1101 Hitachi H8/300[HS] Series}
1105 In addition to those specific offerings, you can get a binary
1106 distribution CD-ROM from the
1107 @uref{http://www.fsf.org/order/order.html,,Free Software Foundation}.
1108 It contains binaries for a number of platforms, and
1109 includes not only GCC, but other stuff as well. The current CD does
1110 not contain the latest version of GCC, but it should allow
1111 bootstrapping the compiler. An updated version of that disk is in the
1119 @uref{./index.html,,Return to the GCC Installation page}
1123 @c ***Specific****************************************************************
1125 @comment node-name, next, previous, up
1126 @node Specific, Concept Index, Binaries, Top
1130 <h1 align="center">Host/target specific installation notes for GCC</h1>
1133 @chapter Host/target specific installation notes for GCC
1136 @cindex Specific installation notes
1137 @cindex Target specific installation
1138 @cindex Host specific installation
1139 @cindex Target specific installation notes
1141 Please read this document carefully @emph{before} installing the
1142 GNU Compiler Collection on your machine.
1147 @uref{#1750a-*-*,,1750a-*-*}
1151 @uref{#a29k-*-bsd,,a29k-*-bsd}
1153 @uref{#alpha*-*-*,,alpha*-*-*}
1155 @uref{#alpha-*-osf1,,alpha-*-osf1}
1157 @uref{#alpha*-dec-osf*,,alpha*-dec-osf*}
1159 @uref{#arc-*-elf,,arc-*-elf}
1161 @uref{#arm-*-aout,,arm-*-aout}
1163 @uref{#arm-*-elf,,arm-*-elf}
1165 @uref{#arm*-*-linux-gnu,,arm*-*-linux-gnu}
1167 @uref{#arm-*-riscix,,arm-*-riscix}
1171 @uref{#decstation-*,,decstation-*}
1175 @uref{#dsp16xx,,dsp16xx}
1177 @uref{#elxsi-elxsi-bsd,,elxsi-elxsi-bsd}
1179 @uref{#h8300-hms,,h8300-hms}
1181 @uref{#hppa*-hp-hpux*,,hppa*-hp-hpux*}
1183 @uref{#hppa*-hp-hpux9,,hppa*-hp-hpux9}
1185 @uref{#hppa*-hp-hpux10,,hppa*-hp-hpux10}
1187 @uref{#hppa*-hp-hpux11,,hppa*-hp-hpux11}
1189 @uref{#*-*-freebsd*,,*-*-freebsd*}
1191 @uref{#i370-*-*,,i370-*-*}
1193 @uref{#*-*-linux-gnu,,*-*-linux-gnu}
1195 @uref{#ix86-*-linux*oldld,,i?86-*-linux*oldld}
1197 @uref{#ix86-*-linux*aout,,i?86-*-linux*aout}
1199 @uref{#ix86-*-linux*,,i?86-*-linux*}
1201 @uref{#ix86-*-sco,,i?86-*-sco}
1203 @uref{#ix86-*-sco3.2v4,,i?86-*-sco3.2v4}
1205 @uref{#ix86-*-sco3.2v5*,,i?86-*-sco3.2v5*}
1207 @uref{#ix86-*-solaris*,,i?86-*-solaris*}
1209 @uref{#ix86-*-udk,,i?86-*-udk}
1211 @uref{#ix86-*-isc,,i?86-*-isc}
1213 @uref{#ix86-*-esix,,i?86-*-esix}
1215 @uref{#ix86-ibm-aix,,i?86-ibm-aix}
1217 @uref{#ix86-sequent-bsd,,i?86-sequent-bsd}
1219 @uref{#ix86-sequent-ptx1*,,i?86-sequent-ptx1*, i?86-sequent-ptx2*}
1221 @uref{#ix86-*-sysv3*,,i?86-*-sysv3*}
1223 @uref{#i860-intel-osf*,,i860-intel-osf*}
1225 @uref{#*-lynx-lynxos,,*-lynx-lynxos}
1227 @uref{#*-ibm-aix*,,*-ibm-aix*}
1229 @uref{#m32r-*-elf,,m32r-*-elf}
1231 @uref{#m68000-hp-bsd,,m68000-hp-bsd}
1233 @uref{#m6811-elf,,m6811-elf}
1235 @uref{#m6812-elf,,m6812-elf}
1237 @uref{#m68k-altos,,m68k-altos}
1239 @uref{#m68k-apple-aux,,m68k-apple-aux}
1241 @uref{#m68k-att-sysv,,m68k-att-sysv}
1243 @uref{#m68k-bull-sysv,,m68k-bull-sysv}
1245 @uref{#m68k-crds-unox,,m68k-crds-unox}
1247 @uref{#m68k-hp-hpux,,m68k-hp-hpux}
1249 @uref{#m68k-*-nextstep*,,m68k-*-nextstep*}
1251 @uref{#m68k-ncr-*,,m68k-ncr-*}
1253 @uref{#m68k-sun,,m68k-sun}
1255 @uref{#m68k-sun-sunos4.1.1,,m68k-sun-sunos4.1.1}
1257 @uref{#m88k-*-svr3,,m88k-*-svr3}
1259 @uref{#m88k-*-dgux,,m88k-*-dgux}
1261 @uref{#m88k-tektronix-sysv3,,m88k-tektronix-sysv3}
1263 @uref{#mips-*-*,,mips-*-*}
1265 @uref{#mips-mips-bsd,,mips-mips-bsd}
1267 @uref{#mips-mips-riscos*,,mips-mips-riscos*}
1269 @uref{#mips*-sgi-irix[45],,mips*-sgi-irix[45]}
1271 @uref{#mips*-sgi-irix6,,mips*-sgi-irix6}
1273 @uref{#mips-sony-sysv,,mips-sony-sysv}
1275 @uref{#ns32k-encore,,ns32k-encore}
1277 @uref{#ns32k-*-genix,,ns32k-*-genix}
1279 @uref{#ns32k-sequent,,ns32k-sequent}
1281 @uref{#ns32k-utek,,ns32k-utek}
1283 @uref{#powerpc-*-elf,,powerpc-*-elf, powerpc-*-sysv4}
1285 @uref{#powerpc-*-linux-gnu*,,powerpc-*-linux-gnu*}
1287 @uref{#powerpc-*-eabiaix,,powerpc-*-eabiaix}
1289 @uref{#powerpc-*-eabisim,,powerpc-*-eabisim}
1291 @uref{#powerpc-*-eabi,,powerpc-*-eabi}
1293 @uref{#powerpcle-*-elf,,powerpcle-*-elf, powerpcle-*-sysv4}
1295 @uref{#powerpcle-*-eabisim,,powerpcle-*-eabisim}
1297 @uref{#powerpcle-*-eabi,,powerpcle-*-eabi}
1299 @uref{#powerpcle-*-winnt,,powerpcle-*-winnt, powerpcle-*-pe}
1301 @uref{#romp-*-aos,,romp-*-aos, romp-*-mach}
1303 @uref{#*-*-solaris*,,*-*-solaris*}
1305 @uref{#sparc-sun-*,,sparc-sun-*}
1307 @uref{#sparc-sun-solaris*,,sparc-sun-solaris*}
1309 @uref{#sparc-sun-solaris2.7,,sparc-sun-solaris2.7}
1311 @uref{#*-sun-solaris2.8,,*-sun-solaris2.8}
1313 @uref{#sunv5,,Sun V5.0 Compiler Bugs}
1315 @uref{#sparc-sun-sunos*,,sparc-sun-sunos*}
1317 @uref{#sparc-unknown-linux-gnulibc1,,sparc-unknown-linux-gnulibc1}
1319 @uref{#sparc64-*-*,,sparc64-*-*}
1321 @uref{#*-*-sysv*,,*-*-sysv*}
1323 @uref{#vax-dec-ultrix,,vax-dec-ultrix}
1325 @uref{#we32k-*-*,,we32k-*-*}
1327 @uref{#windows,,Microsoft Windows}
1331 @uref{#older,,Older systems}
1336 @uref{#elf_targets,,all ELF targets} (SVR4, Solaris, etc.)
1342 <!-- -------- host/target specific issues start here ---------------- -->
1345 @heading @anchor{1750a-*-*}1750a-*-*
1346 MIL-STD-1750A processors.
1348 The MIL-STD-1750A cross configuration produces output for
1349 @code{as1750}, an assembler/linker available under the GNU Public
1350 License for the 1750A. @code{as1750} can be obtained at
1351 @uref{ftp://ftp.fta-berlin.de/pub/crossgcc/1750gals/}.
1352 A similarly licensed simulator for
1353 the 1750A is available from same address.
1355 You should ignore a fatal error during the building of libgcc (libgcc is
1356 not yet implemented for the 1750A.)
1358 The @code{as1750} assembler requires the file @file{ms1750.inc}, which is
1359 found in the directory @file{config/1750a}.
1361 GNU CC produced the same sections as the Fairchild F9450 C Compiler,
1366 The program code section.
1369 The read/write (RAM) data section.
1372 The read-only (ROM) constants section.
1375 Initialization section (code to copy KREL to SREL).
1378 The smallest addressable unit is 16 bits (BITS_PER_UNIT is 16). This
1379 means that type `char' is represented with a 16-bit word per character.
1380 The 1750A's "Load/Store Upper/Lower Byte" instructions are not used by
1387 @heading @anchor{a29k}a29k
1388 AMD Am29k-family processors. These are normally used in embedded
1389 applications. There are no standard Unix configurations.
1391 corresponds to AMD's standard calling sequence and binary interface
1392 and is compatible with other 29k tools.
1394 You may need to make a variant of the file @file{a29k.h} for your
1395 particular configuration.
1401 @heading @anchor{a29k-*-bsd}a29k-*-bsd
1402 AMD Am29050 used in a system running a variant of BSD Unix.
1408 @heading @anchor{alpha*-*-*}alpha*-*-*
1410 This section contains general configuration information for all
1411 alpha-based platforms using ELF (in particular, ignore this section for
1412 OSF and tru64). In addition to reading this section, please read all
1413 other sections that match your target.
1415 We require binutils 2.11.1 (as of yet unreleased), binutils with
1416 binutils-2_11-branch tag after May 31, 2001 (as taken below), or newer.
1417 Previous binutils releases had a number of problems with DWARF2
1418 debugging information, not the least of which is incorrect linking of
1421 Until binutils 2.11.1 is released, these sample commands may be useful:
1424 mkdir binutils-2.11.X; cd binutils-2.11.X
1425 cvs -d :pserver:anoncvs@@anoncvs.cygnus.com:/cvs/src \
1426 co -rbinutils-2_11-branch -P binutils
1428 ../src/configure --prefix=@emph{an-absolute-path}
1429 make all check install
1432 When configuring gcc, provide explicit @option{--with-gnu-as}
1433 @option{--with-as=}@emph{an-absolute-path/bin/as} and
1434 @option{--with-gnu-ld} @option{--with-ld=}@emph{an-absolute-path/bin/ld}
1435 options to point into the prefix used above.
1441 @heading @anchor{alpha-*-osf1}alpha-*-osf1
1442 Systems using processors that implement the DEC Alpha architecture and
1443 are running the DEC Unix (OSF/1) operating system, for example the DEC
1444 Alpha AXP systems.CC.)
1446 GNU CC writes a @samp{.verstamp} directive to the assembler output file
1447 unless it is built as a cross-compiler. It gets the version to use from
1448 the system header file @file{/usr/include/stamp.h}. If you install a
1449 new version of DEC Unix, you should rebuild GCC to pick up the new version
1452 Note that since the Alpha is a 64-bit architecture, cross-compilers from
1453 32-bit machines will not generate code as efficient as that generated
1454 when the compiler is running on a 64-bit machine because many
1455 optimizations that depend on being able to represent a word on the
1456 target in an integral value on the host cannot be performed. Building
1457 cross-compilers on the Alpha for 32-bit machines has only been tested in
1458 a few cases and may not work properly.
1460 @code{make compare} may fail on old versions of DEC Unix unless you add
1461 @samp{-save-temps} to @code{CFLAGS}. On these systems, the name of the
1462 assembler input file is stored in the object file, and that makes
1463 comparison fail if it differs between the @code{stage1} and
1464 @code{stage2} compilations. The option @samp{-save-temps} forces a
1465 fixed name to be used for the assembler input file, instead of a
1466 randomly chosen name in @file{/tmp}. Do not add @samp{-save-temps}
1467 unless the comparisons fail without that option. If you add
1468 @samp{-save-temps}, you will have to manually delete the @samp{.i} and
1469 @samp{.s} files after each series of compilations.
1471 GNU CC now supports both the native (ECOFF) debugging format used by DBX
1472 and GDB and an encapsulated STABS format for use only with GDB. See the
1473 discussion of the @samp{--with-stabs} option of @file{configure} above
1474 for more information on these formats and how to select them.
1476 There is a bug in DEC's assembler that produces incorrect line numbers
1477 for ECOFF format when the @samp{.align} directive is used. To work
1478 around this problem, GNU CC will not emit such alignment directives
1479 while writing ECOFF format debugging information even if optimization is
1480 being performed. Unfortunately, this has the very undesirable
1481 side-effect that code addresses when @samp{-O} is specified are
1482 different depending on whether or not @samp{-g} is also specified.
1484 To avoid this behavior, specify @samp{-gstabs+} and use GDB instead of
1485 DBX. DEC is now aware of this problem with the assembler and hopes to
1486 provide a fix shortly.
1492 @heading @anchor{alpha*-dec-osf*}alpha*-dec-osf*
1494 If you install a shared libstdc++ and, when you link a non-trivial C++
1495 program (for example, @file{gcc/testsuite/g++.other/delete3.C}),
1496 the linker reports a couple of errors about multiply-defined symbols
1497 (for example, @code{nothrow}, @code{__throw} and
1498 @code{terminate(void)}), you've probably got a linker bug, for
1499 which there's no known fix. The officially recommended work-around is
1500 to remove the shared libstdc++.
1502 An alternative solution is to arrange that all symbols from
1503 @code{libgcc} get copied to the shared @code{libstdc++};
1504 see detailed solution below. (Surprising as it may seem, this does
1505 indeed fix the problem!) @emph{Beware} that this may bring you
1506 binary-compatibility problems in the future, if you don't use the same
1507 work-around next time you build @code{libstdc++}: if programs
1508 start to depend on @code{libstdc++} to provide symbols that used
1509 to be only in @code{libgcc}, you must arrange that
1510 @code{libstdc++} keeps providing them, otherwise the programs
1511 will have to be relinked.
1513 The magic spell is to add @code{-Wl,-all,-lgcc,-none} to the
1514 definition of macro @code{SHDEPS} in
1515 @file{libstdc++/config/dec-osf.ml} @emph{before}
1516 @file{alpha*-dec-osf*/libstdc++/Makefile} is created (a
1517 @uref{dec-osf-shlibstdc++.patch,,patch}
1518 that does just that is available). If the Makefile already exists, run
1519 @file{./config.status} within directory
1520 @file{alpha*-dec-osf*/libstdc++} (and
1521 @file{alpha*-dec-osf*/ieee/libstdc++}, if it also exists).
1522 Remove any existing @file{libstdc++.so*} from such directories,
1523 and run @samp{make all-target-libstdc++} in the top-level
1524 directory, then @samp{make install-target-libstdc++}.
1526 If you have already removed the build tree, you may just remove
1527 @file{libstdc++.so.2.10.0} from the install tree and re-create
1529 @samp{gcc -shared -o libstdc++.so.2.10.0 -Wl,-all,-lstdc++,-lgcc,-none -lm}.
1531 sub-directory exists, repeat this command in it, with the additional
1532 flag @option{-mieee}.
1538 @heading @anchor{arc-*-elf}arc-*-elf
1539 Argonaut ARC processor.
1540 This configuration is intended for embedded systems.
1546 @heading @anchor{arm-*-aout}arm-*-aout
1547 Advanced RISC Machines ARM-family processors. These are often used in
1548 embedded applications. There are no standard Unix configurations.
1549 This configuration corresponds to the basic instruction sequences and will
1550 produce @file{a.out} format object modules.
1552 You may need to make a variant of the file @file{arm.h} for your particular
1559 @heading @anchor{arm-*-elf}arm-*-elf
1560 This configuration is intended for embedded systems.
1566 @heading @anchor{arm*-*-linux-gnu}arm*-*-linux-gnu
1568 We require GNU binutils 2.10 or newer.
1574 @heading @anchor{arm-*-riscix}arm-*-riscix
1575 The ARM2 or ARM3 processor running RISC iX, Acorn's port of BSD Unix.
1576 If you are running a version of RISC iX prior to 1.2 then you must
1577 specify the version number during configuration. Note that the
1578 assembler shipped with RISC iX does not support stabs debugging
1579 information; a new version of the assembler, with stabs support
1580 included, is now available from Acorn and via ftp
1581 @uref{ftp://ftp.acorn.com/pub/riscix/as+xterm.tar.Z}. To enable stabs
1582 debugging, pass @samp{--with-gnu-as} to configure.
1584 You will need to install GNU @file{sed} before you can run configure.
1590 @heading @anchor{avr}avr
1592 ATMEL AVR-family micro controllers. These are used in embedded
1593 applications. There are no standard Unix configurations. @xref{AVR
1594 Options,, AVR Options, gcc, Using and Porting the GNU Compiler
1595 Collection (GCC)}, for the list of supported MCU types.
1597 Use @samp{configure --target=avr}
1598 @option{--enable-languages="c"}' to configure GCC.
1600 Further installation notes and other useful information about AVR tools
1601 can also be obtained from:
1605 @uref{http://home.overta.ru/users/denisc,,http://home.overta.ru/users/denisc}
1607 @uref{http://www.itnet.pl/amelektr/avr,,http://www.itnet.pl/amelektr/avr}
1610 We @emph{strongly} recommend using binutils 2.11 or newer.
1612 The following error:
1614 Error: register required
1617 indicates that you should upgrade to a newer version of the binutils.
1623 @heading @anchor{decstation-*}decstation-*
1624 MIPS-based DECstations can support three different personalities:
1625 Ultrix, DEC OSF/1, and OSF/rose. (Alpha-based DECstation products have
1626 a configuration name beginning with @samp{alpha-dec}.) To configure GCC
1627 for these platforms use the following configurations:
1630 @item decstation-ultrix
1631 Ultrix configuration.
1633 @item decstation-osf1
1634 Dec's version of OSF/1.
1636 @item decstation-osfrose
1637 Open Software Foundation reference port of OSF/1 which uses the
1638 OSF/rose object file format instead of ECOFF. Normally, you
1639 would not select this configuration.
1642 The MIPS C compiler needs to be told to increase its table size
1643 for switch statements with the @samp{-Wf,-XNg1500} option in
1644 order to compile @file{cp/parse.c}. If you use the @samp{-O2}
1645 optimization option, you also need to use @samp{-Olimit 3000}.
1646 Both of these options are automatically generated in the
1647 @file{Makefile} that the shell script @file{configure} builds.
1648 If you override the @code{CC} make variable and use the MIPS
1649 compilers, you may need to add @samp{-Wf,-XNg1500 -Olimit 3000}.
1655 @heading @anchor{dos}DOS
1657 Please have a look at our @uref{binaries.html,,binaries page}.
1659 You cannot install GNU C by itself on MSDOS; it will not compile under
1660 any MSDOS compiler except itself. You need to get the complete
1661 compilation package DJGPP, which includes binaries as well as sources,
1662 and includes all the necessary compilation tools and libraries.
1668 @heading @anchor{dsp16xx}dsp16xx
1669 A port to the AT&T DSP1610 family of processors.
1675 @heading @anchor{elxsi-elxsi-bsd}elxsi-elxsi-bsd
1676 The Elxsi's C compiler has known limitations that prevent it from
1677 compiling GNU C. Please contact @email{mrs@@cygnus.com} for more details.
1683 @heading @anchor{h8300-hms}h8300-hms
1684 Hitachi H8/300 series of processors.
1686 Please have a look at our @uref{binaries.html,,binaries page}.
1688 The calling convention and structure layout has changed in release 2.6.
1689 All code must be recompiled. The calling convention now passes the
1690 first three arguments in function calls in registers. Structures are no
1691 longer a multiple of 2 bytes.
1697 @heading @anchor{hppa*-hp-hpux*}hppa*-hp-hpux*
1699 We @emph{highly} recommend using gas/binutils-2.8 or newer on all hppa
1700 platforms; you may encounter a variety of problems when using the HP
1703 Specifically, @option{-g} does not work on HP-UX (since that system
1704 uses a peculiar debugging format which GCC does not know about), unless you
1705 use GAS and GDB and configure GCC with the
1706 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
1707 @option{--with-as=...} options.
1709 If you wish to use pa-risc 2.0 architecture support, you must use either
1710 the HP assembler, gas/binutils-2.11 or a recent
1711 @uref{ftp://sources.redhat.com/pub/binutils/snapshots,,snapshot of gas}.
1713 More specific information to hppa*-hp-hpux* targets follows.
1719 @heading @anchor{hppa*-hp-hpux9}hppa*-hp-hpux9
1721 The HP assembler has major problems on this platform. We've tried to work
1722 around the worst of the problems. However, those workarounds may be causing
1723 linker crashes in some circumstances; the workarounds also probably prevent
1724 shared libraries from working. Use the GNU assembler to avoid these problems.
1727 The configuration scripts for GCC will also trigger a bug in the hpux9
1728 shell. To avoid this problem set @env{CONFIG_SHELL} to @file{/bin/ksh}
1729 and @env{SHELL} to @file{/bin/ksh} in your environment.
1736 @heading @anchor{hppa*-hp-hpux10}hppa*-hp-hpux10
1738 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
1739 @code{PHCO_19798} from HP. HP has two sites which provide patches free of
1745 <a href="http://us-support.external.hp.com">US, Canada, Asia-Pacific, and
1749 @uref{http://us-support.external.hp.com,,}US, Canada, Asia-Pacific, and
1753 @uref{http://europe-support.external.hp.com,,Europe}
1756 The HP assembler on these systems is much better than the hpux9 assembler,
1757 but still has some problems. Most notably the assembler inserts timestamps
1758 into each object file it creates, causing the 3-stage comparison test to fail
1759 during a @samp{make bootstrap}. You should be able to continue by
1760 saying @samp{make all} after getting the failure from @samp{make
1768 @heading @anchor{hppa*-hp-hpux11}hppa*-hp-hpux11
1770 GCC 3.0 supports HP-UX 11. You must use GNU binutils 2.11 or above on
1777 @heading @anchor{*-*-freebsd*}*-*-freebsd*
1779 The version of binutils installed in /usr/bin is known to work unless
1780 otherwise specified in any per-architecture notes. However, binutils
1781 2.11 is known to improve overall testsuite results.
1783 For FreeBSD 1, FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
1784 configuration support and files as shipped with gcc 2.95 are still in
1785 place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
1786 it is unknown which version of binutils was used (it is assumed that it
1787 was the system copy in /usr/bin) and C++ EH failures were noted.
1789 For FreeBSD using the ELF file format: DWARF2 debugging is now the
1790 default for all CPU architectures. It had been the default on
1791 FreeBSD/alpha since its inception. You may use @option{-gstabs} instead
1792 of @option{-g}, if you really want the old debugging format. There are
1793 no known issues with mixing object files and libraries with different
1794 debugging formats. Otherwise, this release of gcc should now match more
1795 of the configuration used in the stock FreeBSD configuration of gcc. In
1796 particular, @option{--enable-threads} is now configured by default.
1797 However, as a general user, do not attempt to replace the system
1798 compiler with this release. Known to bootstrap and check with good
1799 results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3 and 5-CURRENT.
1801 At this time, @option{--enable-threads} is not compatible with
1802 @option{--enable-libgcj} on FreeBSD.
1808 @heading @anchor{i370-*-*}i370-*-*
1809 This port is very preliminary and has many known bugs. We hope to
1810 have a higher-quality port for this machine soon.
1816 @heading @anchor{*-*-linux-gnu}*-*-linux-gnu
1818 If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install
1819 out-of-the-box. You'll get compile errors while building libstdc++.
1820 The patch @uref{glibc-2.2.patch,,glibc-2.2.patch}, that is to be
1821 applied in the GCC source tree, fixes the compatibility problems.
1827 @heading @anchor{ix86-*-linux*oldld}i?86-*-linux*oldld
1828 Use this configuration to generate @file{a.out} binaries on Linux-based
1829 GNU systems if you do not have gas/binutils version 2.5.2 or later
1830 installed. This is an obsolete configuration.
1836 @heading @anchor{ix86-*-linux*aout}i?86-*-linux*aout
1837 Use this configuration to generate @file{a.out} binaries on Linux-based
1838 GNU systems. This configuration is being superseded. You must use
1839 gas/binutils version 2.5.2 or later.
1845 @heading @anchor{ix86-*-linux*}i?86-*-linux*
1847 You will need binutils-2.9.1.0.15 or newer for exception handling to work.
1849 If you receive Signal 11 errors when building on GNU/Linux, then it is
1850 possible you have a hardware problem. Further information on this can be
1851 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
1857 @heading @anchor{ix86-*-sco}i?86-*-sco
1858 Compilation with RCC is recommended. Also, it may be a good idea to
1859 link with GNU malloc instead of the malloc that comes with the system.
1865 @heading @anchor{ix86-*-sco3.2v4}i?86-*-sco3.2v4
1866 Use this configuration for SCO release 3.2 version 4.
1872 @heading @anchor{ix86-*-sco3.2v5*}i?86-*-sco3.2v5*
1873 Use this for the SCO OpenServer Release 5 family of operating systems.
1875 Unlike earlier versions of GCC, the ability to generate COFF with this
1876 target is no longer provided.
1878 Earlier versions of GCC emitted Dwarf-1 when generating ELF to allow
1879 the system debugger to be used. That support was too burdensome to
1880 maintain. GCC now emits only dwarf-2 for this target. This means you
1881 may use either the UDK debugger or GDB to debug programs built by this
1884 If you are building languages other than C, you must follow the instructions
1885 about invoking @samp{make bootstrap} because the native OpenServer
1886 compiler will build a @command{cc1plus} that will not correctly parse many
1887 valid C++ programs including those in @file{libgcc.a}.
1888 @strong{You must do a @samp{make bootstrap} if you are building with the
1891 Use of the @option{-march-pentiumpro} flag can result in
1892 unrecognized opcodes when using the native assembler on OS versions before
1893 5.0.6. (Support for P6 opcodes was added to the native ELF assembler in
1894 that version.) While it's rather rare to see these emitted by GCC yet,
1895 errors of the basic form:
1898 /usr/tmp/ccaNlqBc.s:22:unknown instruction: fcomip
1899 /usr/tmp/ccaNlqBc.s:50:unknown instruction: fucomip
1902 are symptoms of this problem. You may work around this by not
1903 building affected files with that flag, by using the GNU assembler, or
1904 by using the assembler provided with the current version of the OS.
1905 Users of GNU assembler should see the note below for hazards on doing
1908 The native SCO assembler that is provided with the OS at no
1909 charge is normally required. If, however, you must be able to use
1910 the GNU assembler (perhaps you're compiling code with asms that
1911 require GAS syntax) you may configure this package using the flags
1912 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You must
1913 use a recent version of GNU binutils; versions past 2.9.1 seem to work
1916 In general, the @option{--with-gnu-as} option isn't as well tested
1917 as the native assembler.
1919 Look in @file{gcc/config/i386/sco5.h} (search for "messy") for
1920 additional OpenServer-specific flags.
1922 Systems based on OpenServer before 5.0.4 (@samp{uname -X}
1923 will tell you what you're running) require TLS597 from ftp.sco.com/TLS
1924 for C++ constructors and destructors to work right.
1926 The system linker in (at least) 5.0.4 and 5.0.5 will sometimes
1927 do the wrong thing for a construct that GCC will emit for PIC
1928 code. This can be seen as execution testsuite failures when using
1929 -fPIC on 921215-1.c, 931002-1.c, nestfunc-1.c, and gcov-1.c.
1930 For 5.0.5, an updated linker that will cure this problem is
1931 available. You must install both
1932 @uref{ftp://ftp.sco.com/Supplements/rs505a/,,ftp://ftp.sco.com/Supplements/rs505a/}
1933 and @uref{ftp://ftp.sco.com/SLS/,,OSS499A}.
1935 The dynamic linker in OpenServer 5.0.5 (earlier versions may show
1936 the same problem) aborts on certain g77-compiled programs. It's particularly
1937 likely to be triggered by building Fortran code with the @option{-fPIC} flag.
1938 Although it's conceivable that the error could be triggered by other
1939 code, only G77-compiled code has been observed to cause this abort.
1940 If you are getting core dumps immediately upon execution of your
1941 g77 program - and especially if it's compiled with -fPIC - try applying
1942 @uref{sco_osr5_g77.patch,,@file{sco_osr5_g77.patch}} to your libf2c and
1944 Affected faults, when analyzed in a debugger, will show a stack
1945 backtrace with a fault occurring in @code{rtld()} and the program
1946 running as @file{/usr/lib/ld.so.1}. This problem has been reported to SCO
1947 engineering and will hopefully be addressed in later releases.
1954 @heading @anchor{ix86-*-solaris*}i?86-*-solaris*
1956 GCC 2.95.2, when configured to use the GNU assembler, would invoke
1957 it with the @code{-s} switch, that GNU as up to 2.9.5.0.12 does
1958 not support. If you'd rather not use a newer GNU as nor the native
1959 assembler, you'll need the patch
1960 @uref{x86-sol2-gas.patch,,@file{x86-sol2-gas.patch}}.
1967 @heading @anchor{ix86-*-udk}i?86-*-udk
1969 This target emulates the SCO Universal Development Kit and requires that
1970 package be installed. (If it is installed, you will have a
1971 @file{/udk/usr/ccs/bin/cc } file present.) It's very much like the
1972 @code{i?86-*-unixware7*} target
1973 but is meant to be used when hosting on a system where UDK isn't the
1974 default compiler such as OpenServer 5 or Unixware 2. This target will
1975 generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
1976 with the same warnings and caveats as the SCO UDK.
1978 You can stage1 with either your native compiler or with UDK. If you
1979 don't do a full bootstrap when initially building with your native compiler
1980 you will have an utterly unusable pile of bits as your reward.
1982 This target is a little tricky to build because we have to distinguish
1983 it from the native tools (so it gets headers, startups, and libraries
1984 from the right place) while making the tools not think we're actually
1985 building a cross compiler. The easiest way to do this is with a configure
1988 @samp{CC=/udk/usr/ccs/bin/cc <i>/your/path/to/</i>gcc/configure
1989 --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-}
1991 @emph{You should substitute 'i686' in the above command with the appropriate
1992 processor for your host.}
1994 You should follow this with a @samp{make bootstrap} then
1995 @samp{make install}. You can then access the UDK-targeted GCC
1996 tools by adding @command{udk-} before the commonly known name. For
1997 example, to invoke the C compiler, you would use @command{udk-gcc}.
1998 They will coexist peacefully with any native-target GCC tools you may
2006 @heading @anchor{ix86-*-isc}i?86-*-isc
2007 It may be a good idea to link with GNU malloc instead of the malloc that
2008 comes with the system.
2010 In ISC version 4.1, @file{sed} core dumps when building
2011 @file{deduced.h}. Use the version of @file{sed} from version 4.0.
2017 @heading @anchor{ix86-*-esix}i?86-*-esix
2018 It may be good idea to link with GNU malloc instead of the malloc that
2019 comes with the system.
2025 @heading @anchor{ix86-ibm-aix}i?86-ibm-aix
2026 You need to use GAS version 2.1 or later, and LD from
2027 GNU binutils version 2.2 or later.
2033 @heading @anchor{ix86-sequent-bsd}i?86-sequent-bsd
2034 Go to the Berkeley universe before compiling.
2040 @heading @anchor{ix86-sequent-ptx1*}i?86-sequent-ptx1*, i?86-sequent-ptx2*
2041 You must install GNU @file{sed} before running @file{configure}.
2047 @heading @anchor{#ix86-*-sysv3*}i?86-*-sysv3*
2048 The @code{fixproto} shell script may trigger a bug in the system shell.
2049 If you encounter this problem, upgrade your operating system or
2050 use BASH (the GNU shell) to run @code{fixproto}.
2057 @heading @anchor{i860-intel-osf*}i860-intel-osf*
2058 On the Intel Paragon (an i860 machine), if you are using operating
2059 system version 1.0, you will get warnings or errors about redefinition
2060 of @code{va_arg} when you build GCC.
2062 If this happens, then you need to link most programs with the library
2063 @file{iclib.a}. You must also modify @file{stdio.h} as follows: before
2067 #if defined(__i860__) && !defined(_VA_LIST)
2068 #include <va_list.h>
2082 extern int vprintf(const char *, va_list );
2083 extern int vsprintf(char *, const char *, va_list );
2091 #endif /* __PGC__ */
2094 These problems don't exist in operating system version 1.1.
2100 @heading @anchor{*-lynx-lynxos}*-lynx-lynxos
2101 LynxOS 2.2 and earlier comes with GNU CC 1.x already installed as
2102 @file{/bin/gcc}. You should compile with this instead of @file{/bin/cc}.
2103 You can tell GNU CC to use the GNU assembler and linker, by specifying
2104 @samp{--with-gnu-as --with-gnu-ld} when configuring. These will produce
2105 COFF format object files and executables; otherwise GNU CC will use the
2106 installed tools, which produce @file{a.out} format executables.
2111 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
2113 @heading @anchor{*-ibm-aix*}*-ibm-aix*
2115 AIX Make frequently has problems with GCC makefiles. GNU Make 3.76 or
2116 newer is recommended to build on this platform.
2118 Errors involving "alloca" when building GCC generally are due
2119 to an incorrect definition of @var{CC} in the Makefile or mixing files
2120 compiled with the native C compiler and GCC. During the stage1 phase of
2121 the build, the native AIX compiler @strong{must} be invoked as "cc"
2122 (not "xlc"). Once @command{configure} has been informed of
2123 "xlc", one needs to use @samp{make distclean} to remove the
2124 configure cache files and ensure that @env{CC} environment variable
2125 does not provide a definition that will confuse @command{configure}.
2126 If this error occurs during stage2 or later, then the problem most likely
2127 is the version of Make (see above).
2129 Binutils 2.10 does not support AIX 4.3. Binutils available from the
2130 @uref{http://www-1.ibm.com/servers/aix/products/aixos/linux/,,AIX
2131 Toolbox for Linux: GNU and Open Source tools for AIX};
2132 website does work. Binutils 2.11 is expected to include AIX 4.3
2133 support. The GNU Assembler is necessary for libstdc++ to build. The
2134 AIX native ld still is recommended. The native AIX tools do
2135 interoperate with GCC.
2137 Linking executables and shared libraries may produce warnings of
2138 duplicate symbols. The assembly files generated by GCC for AIX always
2139 have included multiple symbol definitions for certain global variable
2140 and function declarations in the original program. The warnings should
2141 not prevent the linker from producing a correct library or runnable
2144 AIX 4.3 utilizes a "large format" archive to support both 32-bit and
2145 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
2146 to parse archive libraries did not handle the new format correctly.
2147 These routines are used by GCC and result in error messages during
2148 linking such as "not a COFF file". The version of the routines shipped
2149 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
2150 option of the archive command may be used to create archives of 32-bit
2151 objects using the original "small format". A correct version of the
2152 routines is shipped with AIX 4.3.2.
2154 Some versions of the AIX binder (linker) can fail with a relocation
2155 overflow severe error when the @option{-bbigtoc} option is used to link
2156 GCC-produced object files into an executable that overflows the TOC. A fix
2157 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
2158 available from IBM Customer Support and from its
2159 @uref{http://service.boulder.ibm.com/,,service.boulder.ibm.com}
2160 website as PTF U455193.
2162 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
2163 with a segmentation fault when invoked by any version of GCC. A fix for
2164 APAR IX87327 is available from IBM Customer Support and from its
2165 @uref{http://service.boulder.ibm.com/,,service.boulder.ibm.com}
2166 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
2168 The initial assembler shipped with AIX 4.3.0 generates incorrect object
2169 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
2170 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
2171 @uref{http://service.boulder.ibm.com/,,service.boulder.ibm.com}
2172 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
2174 AIX provides National Language Support (NLS). Compilers and assemblers
2175 use NLS to support locale-specific representations of various data
2176 formats including floating-point numbers (e.g., "." vs "," for
2177 separating decimal fractions). There have been problems reported where
2178 GCC does not produce the same floating-point formats that the assembler
2179 expects. If one encouters this problem, set the @env{LANG}
2180 environment variable to "C" or "En_US".
2182 By default, GCC for AIX 4.1 and above produces code that can be used on
2183 both Power or PowerPC processors.
2185 You can specify a default version for the @samp{-mcpu=}@var{cpu_type}
2186 switch by using the configure option @samp{--with-cpu-}@var{cpu_type}.
2192 @heading @anchor{m32r-*-elf}m32r-*-elf
2193 Mitsubishi M32R processor.
2194 This configuration is intended for embedded systems.
2200 @heading @anchor{m68000-hp-bsd}m68000-hp-bsd
2201 HP 9000 series 200 running BSD. Note that the C compiler that comes
2202 with this system cannot compile GNU CC; contact @email{law@@cygnus.com}
2203 to get binaries of GNU CC for bootstrapping.
2209 @heading @anchor{m6811-elf}m6811-elf
2210 Motorola 68HC11 family micro controllers. These are used in embedded
2211 applications. There are no standard Unix configurations.
2217 @heading @anchor{m6812-elf}m6812-elf
2218 Motorola 68HC12 family micro controllers. These are used in embedded
2219 applications. There are no standard Unix configurations.
2225 @heading @anchor{m68k-altos}m68k-altos
2226 Altos 3068. You must use the GNU assembler, linker and debugger.
2227 Also, you must fix a kernel bug. Details in the file @file{README.ALTOS}.
2233 @heading @anchor{m68k-apple-aux}m68k-apple-aux
2234 Apple Macintosh running A/UX.
2235 You may configure GCC to use either the system assembler and
2236 linker or the GNU assembler and linker. You should use the GNU configuration
2237 if you can, especially if you also want to use GNU C++. You enabled
2238 that configuration with + the @samp{--with-gnu-as} and @samp{--with-gnu-ld}
2239 options to @code{configure}.
2241 Note the C compiler that comes
2242 with this system cannot compile GNU CC. You can find binaries of GNU CC
2243 for bootstrapping on @code{jagubox.gsfc.nasa.gov}.
2244 You will also a patched version of @file{/bin/ld} there that
2245 raises some of the arbitrary limits found in the original.
2251 @heading @anchor{m68k-att-sysv}m68k-att-sysv
2252 AT&T 3b1, a.k.a. 7300 PC. This version of GNU CC cannot
2253 be compiled with the system C compiler, which is too buggy.
2254 You will need to get a previous version of GCC and use it to
2255 bootstrap. Binaries are available from the OSU-CIS archive, at
2256 @uref{ftp://archive.cis.ohio-state.edu/pub/att7300/}.
2262 @heading @anchor{m68k-bull-sysv}m68k-bull-sysv
2263 Bull DPX/2 series 200 and 300 with BOS-2.00.45 up to BOS-2.01. GNU CC works
2264 either with native assembler or GNU assembler. You can use
2265 GNU assembler with native coff generation by providing @samp{--with-gnu-as} to
2266 the configure script or use GNU assembler with dbx-in-coff encapsulation
2267 by providing @samp{--with-gnu-as --stabs}. For any problem with native
2268 assembler or for availability of the DPX/2 port of GAS, contact
2269 @email{F.Pierresteguy@@frcl.bull.fr}.
2275 @heading @anchor{m68k-crds-unox}m68k-crds-unox
2276 Use @samp{configure unos} for building on Unos.
2278 The Unos assembler is named @code{casm} instead of @code{as}. For some
2279 strange reason linking @file{/bin/as} to @file{/bin/casm} changes the
2280 behavior, and does not work. So, when installing GNU CC, you should
2281 install the following script as @file{as} in the subdirectory where
2282 the passes of GCC are installed:
2289 The default Unos library is named @file{libunos.a} instead of
2290 @file{libc.a}. To allow GNU CC to function, either change all
2291 references to @samp{-lc} in @file{gcc.c} to @samp{-lunos} or link
2292 @file{/lib/libc.a} to @file{/lib/libunos.a}.
2294 @cindex @code{alloca}, for Unos
2295 When compiling GNU CC with the standard compiler, to overcome bugs in
2296 the support of @code{alloca}, do not use @samp{-O} when making stage 2.
2297 Then use the stage 2 compiler with @samp{-O} to make the stage 3
2298 compiler. This compiler will have the same characteristics as the usual
2299 stage 2 compiler on other systems. Use it to make a stage 4 compiler
2300 and compare that with stage 3 to verify proper compilation.
2302 (Perhaps simply defining @code{ALLOCA} in @file{x-crds} as described in
2303 the comments there will make the above paragraph superfluous. Please
2304 inform us of whether this works.)
2306 Unos uses memory segmentation instead of demand paging, so you will need
2307 a lot of memory. 5 Mb is barely enough if no other tasks are running.
2308 If linking @file{cc1} fails, try putting the object files into a library
2309 and linking from that library.
2315 @heading @anchor{m68k-hp-hpux}m68k-hp-hpux
2316 HP 9000 series 300 or 400 running HP-UX. HP-UX version 8.0 has a bug in
2317 the assembler that prevents compilation of GNU CC. This
2318 bug manifests itself during the first stage of compilation, while
2319 building @file{libgcc2.a}:
2323 cc1: warning: `-g' option not supported on this version of GCC
2324 cc1: warning: `-g1' option not supported on this version of GCC
2325 ./xgcc: Internal compiler error: program as got fatal signal 11
2328 A patched version of the assembler is available as the file
2329 @uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you
2330 have HP software support, the patch can also be obtained directly from
2331 HP, as described in the following note:
2334 This is the patched assembler, to patch SR#1653-010439, where the
2335 assembler aborts on floating point constants.
2337 The bug is not really in the assembler, but in the shared library
2338 version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is
2339 SR#4701-078451. Anyway, the attached assembler uses the archive
2340 library version of ``cvtnum(3c)'' and thus does not exhibit the bug.
2343 This patch is also known as PHCO_4484.
2345 In addition, if you wish to use gas @samp{--with-gnu-as} you must use
2346 gas version 2.1 or later, and you must use the GNU linker version 2.1 or
2347 later. Earlier versions of gas relied upon a program which converted the
2348 gas output into the native HP-UX format, but that program has not been
2349 kept up to date. gdb does not understand that native HP-UX format, so
2350 you must use gas if you wish to use gdb.
2352 On HP-UX version 8.05, but not on 8.07 or more recent versions, the
2353 @code{fixproto} shell script triggers a bug in the system shell. If you
2354 encounter this problem, upgrade your operating system or use BASH (the
2355 GNU shell) to run @code{fixproto}. This bug will cause the fixproto
2356 program to report an error of the form:
2359 ./fixproto: sh internal 1K buffer overflow
2362 To fix this, you can also change the first line of the fixproto script
2374 @heading @anchor{m68k-*-nextstep*}m68k-*-nextstep*
2376 Current GCC versions probably do not work on version 2 of the NeXT
2379 On NeXTStep 3.0, the Objective C compiler does not work, due,
2380 apparently, to a kernel bug that it happens to trigger. This problem
2381 does not happen on 3.1.
2383 You absolutely @strong{must} use GNU sed and GNU make on this platform.
2386 On NEXTSTEP 3.x where x < 3 the build of GCC will abort during
2387 stage1 with an error message like this:
2391 /usr/tmp/ccbbsZ0U.s:987:Unknown pseudo-op: .section
2392 /usr/tmp/ccbbsZ0U.s:987:Rest of line ignored. 1st junk character
2396 The reason for this is the fact that NeXT's assembler for these
2397 versions of the operating system does not support the .section
2398 pseudo op that's needed for full C++ exception functionality.
2400 As NeXT's assembler is a derived work from GNU as, a free
2401 replacement that does can be obtained at
2402 @uref{ftp://ftp.next.peak.org:/next-ftp/next/apps/devtools/as.3.3.NIHS.s.tar.gz,,ftp://ftp.next.peak.org:/next-ftp/next/apps/devtools/as.3.3.NIHS.s.tar.gz}.
2404 If you try to build the integrated C++ & C++ runtime libraries on this system
2405 you will run into trouble with include files. The way to get around this is
2406 to use the following sequence. Note you must have write permission to
2407 the directory @var{prefix} you specified in the configuration process of GCC
2408 for this sequence to work.
2412 make all-texinfo all-bison all-byacc all-binutils all-gas all-ld
2415 make install-headers-tar
2424 @heading @anchor{m68k-ncr-*}m68k-ncr-*
2425 On the Tower models 4@var{n}0 and 6@var{n}0, by default a process is not
2426 allowed to have more than one megabyte of memory. GCC cannot compile
2427 itself (or many other programs) with @samp{-O} in that much memory.
2429 To solve this problem, reconfigure the kernel adding the following line
2430 to the configuration file:
2441 @heading @anchor{m68k-sun}m68k-sun
2442 Sun 3. We do not provide a configuration file to use the Sun FPA by
2443 default, because programs that establish signal handlers for floating
2444 point traps inherently cannot work with the FPA.
2450 @heading @anchor{m68k-sun-sunos4.1.1}m68k-sun-sunos4.1.1
2452 It is reported that you may need the GNU assembler on this platform.
2459 @heading @anchor{m88k-*-svr3}m88k-*-svr3
2460 Motorola m88k running the AT&T/Unisoft/Motorola V.3 reference port.
2461 These systems tend to use the Green Hills C, revision 1.8.5, as the
2462 standard C compiler. There are apparently bugs in this compiler that
2463 result in object files differences between stage 2 and stage 3. If this
2464 happens, make the stage 4 compiler and compare it to the stage 3
2465 compiler. If the stage 3 and stage 4 object files are identical, this
2466 suggests you encountered a problem with the standard C compiler; the
2467 stage 3 and 4 compilers may be usable.
2469 It is best, however, to use an older version of GNU CC for bootstrapping
2476 @heading @anchor{m88k-*-dgux}m88k-*-dgux
2477 Motorola m88k running DG/UX. To build 88open BCS native or cross
2478 compilers on DG/UX, specify the configuration name as
2479 @samp{m88k-*-dguxbcs} and build in the 88open BCS software development
2480 environment. To build ELF native or cross compilers on DG/UX, specify
2481 @samp{m88k-*-dgux} and build in the DG/UX ELF development environment.
2482 You set the software development environment by issuing
2483 @samp{sde-target} command and specifying either @samp{m88kbcs} or
2484 @samp{m88kdguxelf} as the operand.
2486 If you do not specify a configuration name, @file{configure} guesses the
2487 configuration based on the current software development environment.
2493 @heading @anchor{m88k-tektronix-sysv3}m88k-tektronix-sysv3
2494 Tektronix XD88 running UTekV 3.2e. Do not turn on
2495 optimization while building stage1 if you bootstrap with
2496 the buggy Green Hills compiler. Also, The bundled LAI
2497 System V NFS is buggy so if you build in an NFS mounted
2498 directory, start from a fresh reboot, or avoid NFS all together.
2499 Otherwise you may have trouble getting clean comparisons
2506 @heading @anchor{mips-*-*}mips-*-*
2507 If you use the 1.31 version of the MIPS assembler (such as was shipped
2508 with Ultrix 3.1), you will need to use the -fno-delayed-branch switch
2509 when optimizing floating point code. Otherwise, the assembler will
2510 complain when the GCC compiler fills a branch delay slot with a
2511 floating point instruction, such as @code{add.d}.
2513 If on a MIPS system you get an error message saying ``does not have gp
2514 sections for all it's [sic] sectons [sic]'', don't worry about it. This
2515 happens whenever you use GAS with the MIPS linker, but there is not
2516 really anything wrong, and it is okay to use the output file. You can
2517 stop such warnings by installing the GNU linker.
2519 It would be nice to extend GAS to produce the gp tables, but they are
2520 optional, and there should not be a warning about their absence.
2522 Users have reported some problems with version 2.0 of the MIPS
2523 compiler tools that were shipped with Ultrix 4.1. Version 2.10
2524 which came with Ultrix 4.2 seems to work fine.
2526 Users have also reported some problems with version 2.20 of the
2527 MIPS compiler tools that were shipped with RISC/os 4.x. The earlier
2528 version 2.11 seems to work fine.
2530 Some versions of the MIPS linker will issue an assertion failure
2531 when linking code that uses @code{alloca} against shared
2532 libraries on RISC-OS 5.0, and DEC's OSF/1 systems. This is a bug
2533 in the linker, that is supposed to be fixed in future revisions.
2534 To protect against this, GCC passes @samp{-non_shared} to the
2535 linker unless you pass an explicit @samp{-shared} or
2536 @samp{-call_shared} switch.
2538 @heading @anchor{mips-mips-bsd}mips-mips-bsd
2539 MIPS machines running the MIPS operating system in BSD mode. It's
2540 possible that some old versions of the system lack the functions
2541 @code{memcpy}, @code{memmove}, @code{memcmp}, and @code{memset}. If your
2542 system lacks these, you must remove or undo the definition of
2543 @code{TARGET_MEM_FUNCTIONS} in @file{mips-bsd.h}.
2545 The MIPS C compiler needs to be told to increase its table size
2546 for switch statements with the @samp{-Wf,-XNg1500} option in
2547 order to compile @file{cp/parse.c}. If you use the @samp{-O2}
2548 optimization option, you also need to use @samp{-Olimit 3000}.
2549 Both of these options are automatically generated in the
2550 @file{Makefile} that the shell script @file{configure} builds.
2551 If you override the @code{CC} make variable and use the MIPS
2552 compilers, you may need to add @samp{-Wf,-XNg1500 -Olimit 3000}.
2558 @heading @anchor{mips-mips-riscos*}mips-mips-riscos*
2559 The MIPS C compiler needs to be told to increase its table size
2560 for switch statements with the @samp{-Wf,-XNg1500} option in
2561 order to compile @file{cp/parse.c}. If you use the @samp{-O2}
2562 optimization option, you also need to use @samp{-Olimit 3000}.
2563 Both of these options are automatically generated in the
2564 @file{Makefile} that the shell script @file{configure} builds.
2565 If you override the @code{CC} make variable and use the MIPS
2566 compilers, you may need to add @samp{-Wf,-XNg1500 -Olimit 3000}.
2568 MIPS computers running RISC-OS can support four different
2569 personalities: default, BSD 4.3, System V.3, and System V.4
2570 (older versions of RISC-OS don't support V.4). To configure GCC
2571 for these platforms use the following configurations:
2574 @item mips-mips-riscos@code{rev}
2575 Default configuration for RISC-OS, revision @code{rev}.
2577 @item mips-mips-riscos@code{rev}bsd
2578 BSD 4.3 configuration for RISC-OS, revision @code{rev}.
2580 @item mips-mips-riscos@code{rev}sysv4
2581 System V.4 configuration for RISC-OS, revision @code{rev}.
2587 @item mips-mips-riscos@code{rev}sysv
2588 System V.3 configuration for RISC-OS, revision @code{rev}.
2591 The revision @code{rev} mentioned above is the revision of
2592 RISC-OS to use. You must reconfigure GCC when going from a
2593 RISC-OS revision 4 to RISC-OS revision 5. This has the effect of
2594 avoiding a linker bug.
2600 @heading @anchor{mips*-sgi-irix[45]}mips*-sgi-irix[45]
2602 In order to compile GCC on an SGI running IRIX 4, the "c.hdr.lib"
2603 option must be installed from the CD-ROM supplied from Silicon Graphics.
2604 This is found on the 2nd CD in release 4.0.1.
2606 In order to compile GCC on an SGI running IRIX 5, the "compiler_dev.hdr"
2607 subsystem must be installed from the IDO CD-ROM supplied by Silicon
2610 @code{make compare} may fail on version 5 of IRIX unless you add
2611 @samp{-save-temps} to @code{CFLAGS}. On these systems, the name of the
2612 assembler input file is stored in the object file, and that makes
2613 comparison fail if it differs between the @code{stage1} and
2614 @code{stage2} compilations. The option @samp{-save-temps} forces a
2615 fixed name to be used for the assembler input file, instead of a
2616 randomly chosen name in @file{/tmp}. Do not add @samp{-save-temps}
2617 unless the comparisons fail without that option. If you do you
2618 @samp{-save-temps}, you will have to manually delete the @samp{.i} and
2619 @samp{.s} files after each series of compilations.
2621 The MIPS C compiler needs to be told to increase its table size
2622 for switch statements with the @samp{-Wf,-XNg1500} option in
2623 order to compile @file{cp/parse.c}. If you use the @samp{-O2}
2624 optimization option, you also need to use @samp{-Olimit 3000}.
2625 Both of these options are automatically generated in the
2626 @file{Makefile} that the shell script @file{configure} builds.
2627 If you override the @code{CC} make variable and use the MIPS
2628 compilers, you may need to add @samp{-Wf,-XNg1500 -Olimit 3000}.
2630 On Irix version 4.0.5F, and perhaps on some other versions as well,
2631 there is an assembler bug that reorders instructions incorrectly. To
2632 work around it, specify the target configuration
2633 @samp{mips-sgi-irix4loser}. This configuration inhibits assembler
2636 In a compiler configured with target @samp{mips-sgi-irix4}, you can turn
2637 off assembler optimization by using the @samp{-noasmopt} option. This
2638 compiler option passes the option @samp{-O0} to the assembler, to
2641 The @samp{-noasmopt} option can be useful for testing whether a problem
2642 is due to erroneous assembler reordering. Even if a problem does not go
2643 away with @samp{-noasmopt}, it may still be due to assembler
2644 reordering---perhaps GNU CC itself was miscompiled as a result.
2646 To enable debugging under Irix 5, you must use GNU as 2.5 or later,
2647 and use the @samp{--with-gnu-as} configure option when configuring gcc.
2648 GNU as is distributed as part of the binutils package.
2650 You must use GAS on these platforms, as the native assembler can not handle
2651 the code for exception handling support. Either of these messages indicates
2652 that you are using the MIPS assembler when instead you should be using GAS:
2654 @samp{ as0: Error: ./libgcc2.c, line 1:Badly delimited numeric literal
2655 .4byte $LECIE1-$LSCIE1
2656 as0: Error: ./libgcc2.c, line 1:malformed statement}
2660 @samp{ as0: Error: /src/bld-gcc/gcc/libgcc2.c, line 1:undefined symbol in expression
2661 .word $LECIE1-$LSCIE1}
2663 These systems don't have ranlib, which various components in GCC need; you
2664 should be able to avoid this problem by installing GNU binutils, which includes
2665 a functional ranlib for this system.
2667 You may get the following warning on irix4 platforms, it can be safely
2670 warning: foo.o does not have gp tables for all its sections.
2673 When building GCC, the build process loops rebuilding cc1 over and
2674 over again. This happens on mips-sgi-irix5.2, and possibly other platforms.@*
2675 It has been reported that this is a known bug in the make shipped with
2676 IRIX 5.2. We recommend you use GNU make instead of the vendor supplied
2677 make program; however, you may have success with "smake" on IRIX 5.2 if
2678 you do not have GNU make available.
2680 See @uref{http://freeware.sgi.com/,,http://freeware.sgi.com/} for more
2681 information about using GCC on IRIX platforms.
2688 @heading @anchor{mips*-sgi-irix6}mips*-sgi-irix6
2690 You must @emph{not} use GAS on irix6 platforms; doing so will only
2693 These systems don't have ranlib, which various components in GCC need; you
2694 should be able to avoid this problem by making a dummy script called ranlib
2695 which just exits with zero status and placing it in your path.
2697 If you are using Irix cc as your bootstrap compiler, you must
2698 ensure that the N32 ABI is in use. To test this, compile a simple C
2699 file with @command{cc} and then run @command{file} on the
2700 resulting object file. The output should look like:
2703 @code{ test.o: ELF N32 MSB ...}
2708 @code{ test.o: ELF 32-bit MSB}
2711 then your version of @command{cc} uses the O32 ABI default. You
2712 should set the environment variable @env{CC} to @samp{cc -n32}
2713 before configuring GCC.
2715 GCC does not currently support generating O32 ABI binaries in the
2716 mips-sgi-irix6 configurations. It used to be possible to create a GCC
2717 with O32 ABI only support by configuring it for the mips-sgi-irix5
2718 target. See the link below for details.
2720 GCC does not correctly pass/return structures which are
2721 smaller than 16 bytes and which are not 8 bytes. The problem is very
2722 involved and difficult to fix. It affects a number of other targets also,
2723 but IRIX 6 is affected the most, because it is a 64 bit target, and 4 byte
2724 structures are common. The exact problem is that structures are being padded
2725 at the wrong end, e.g. a 4 byte structure is loaded into the lower 4 bytes
2726 of the register when it should be loaded into the upper 4 bytes of the
2729 GCC is consistent with itself, but not consistent with the SGI C compiler
2730 (and the SGI supplied runtime libraries), so the only failures that can
2731 happen are when there are library functions that take/return such
2732 structures. There are very few such library functions. I can only recall
2733 seeing two of them: inet_ntoa, and semctl.
2735 See @uref{http://freeware.sgi.com/,,http://freeware.sgi.com/} for more
2736 information about using GCC on IRIX platforms.
2743 @heading @anchor{mips-sony-sysv}mips-sony-sysv
2744 Sony MIPS NEWS. This works in NEWSOS 5.0.1, but not in 5.0.2 (which
2745 uses ELF instead of COFF). Support for 5.0.2 will probably be provided
2746 soon by volunteers. In particular, the linker does not like the
2747 code generated by GCC when shared libraries are linked in.
2754 @heading @anchor{ns32k-encore}ns32k-encore
2755 Encore ns32000 system. Encore systems are supported only under BSD.
2761 @heading @anchor{ns32k-*-genix}ns32k-*-genix
2762 National Semiconductor ns32000 system. Genix has bugs in @code{alloca}
2763 and @code{malloc}; you must get the compiled versions of these from GNU
2770 @heading @anchor{ns32k-sequent}ns32k-sequent
2771 Go to the Berkeley universe before compiling.
2777 @heading @anchor{ns32k-utek}ns32k-utek
2778 UTEK ns32000 system (``merlin''). The C compiler that comes with this
2779 system cannot compile GNU CC; contact @samp{tektronix!reed!mason} to get
2780 binaries of GNU CC for bootstrapping.
2787 @heading @anchor{powerpc-*-elf}powerpc-*-elf, powerpc-*-sysv4
2788 PowerPC system in big endian mode, running System V.4.
2790 You can specify a default version for the @samp{-mcpu=}@var{cpu_type}
2791 switch by using the configure option @samp{--with-cpu-}@var{cpu_type}.
2797 @heading @anchor{powerpc-*-linux-gnu*}powerpc-*-linux-gnu*
2800 @uref{ftp://ftp.varesearch.com/pub/support/hjl/binutils,,binutils-2.9.4.0.8}
2801 or newer for a working GCC. It is strongly recommended to recompile binutils
2802 if you initially built it with gcc-2.7.2.x.
2804 You can specify a default version for the @samp{-mcpu=}@var{cpu_type}
2805 switch by using the configure option @samp{--with-cpu-}@var{cpu_type}.
2811 @heading @anchor{powerpc-*-eabiaix}powerpc-*-eabiaix
2812 Embedded PowerPC system in big endian mode with -mcall-aix selected as
2815 You can specify a default version for the @samp{-mcpu=}@var{cpu_type}
2816 switch by using the configure option @samp{--with-cpu-}@var{cpu_type}.
2822 @heading @anchor{powerpc-*-eabisim}powerpc-*-eabisim
2823 Embedded PowerPC system in big endian mode for use in running under the
2826 You can specify a default version for the @samp{-mcpu=}@var{cpu_type}
2827 switch by using the configure option @samp{--with-cpu-}@var{cpu_type}.
2833 @heading @anchor{powerpc-*-eabi}powerpc-*-eabi
2834 Embedded PowerPC system in big endian mode.
2836 You can specify a default version for the @samp{-mcpu=}@var{cpu_type}
2837 switch by using the configure option @samp{--with-cpu-}@var{cpu_type}.
2843 @heading @anchor{powerpcle-*-elf}powerpcle-*-elf, powerpcle-*-sysv4
2844 PowerPC system in little endian mode, running System V.4.
2846 You can specify a default version for the @samp{-mcpu=}@var{cpu_type}
2847 switch by using the configure option @samp{--with-cpu-}@var{cpu_type}.
2853 @heading @anchor{powerpcle-*-eabisim}powerpcle-*-eabisim
2854 Embedded PowerPC system in little endian mode for use in running under
2861 @heading @anchor{powerpcle-*-eabi}powerpcle-*-eabi
2862 Embedded PowerPC system in little endian mode.
2864 You can specify a default version for the @samp{-mcpu=}@var{cpu_type}
2865 switch by using the configure option @samp{--with-cpu-}@var{cpu_type}.
2871 @heading @anchor{powerpcle-*-winnt}powerpcle-*-winnt, powerpcle-*-pe
2872 PowerPC system in little endian mode running Windows NT.
2874 You can specify a default version for the @samp{-mcpu=}@var{cpu_type}
2875 switch by using the configure option @samp{--with-cpu-}@var{cpu_type}.
2881 @heading @anchor{romp-*-aos}romp-*-aos, romp-*-mach
2882 The only operating systems supported for the IBM RT PC are AOS and
2883 MACH. GNU CC does not support AIX running on the RT. We recommend you
2884 compile GNU CC with an earlier version of itself; if you compile GNU CC
2885 with @code{hc}, the Metaware compiler, it will work, but you will get
2886 mismatches between the stage 2 and stage 3 compilers in various files.
2887 These errors are minor differences in some floating-point constants and
2888 can be safely ignored; the stage 3 compiler is correct.
2894 @heading @anchor{*-*-solaris*}*-*-solaris*
2896 Starting with Solaris, Sun does not ship a C compiler any more. To
2897 bootstrap and install GCC you first have to install a pre-built
2898 compiler, see our @uref{binaries.html,,binaries page} for
2901 You must use GNU Make to build GCC on Solaris 2. If you don't have GNU
2902 Make installed, you can use the prebuilt compiler mentioned above to
2905 Sun as 4.X is broken in that it cannot cope with long symbol names.
2906 A typical error message might look similar to the following:
2908 @samp{/usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041:
2909 error: can't compute value of an expression involving an external symbol.}
2911 This is Sun bug 4237974. This is fixed with patch 108908-02 and has
2912 been fixed in later (5.x) versions of the assembler.
2918 @heading @anchor{sparc-sun-*}sparc-sun-*
2919 Sometimes on a Sun 4 you may observe a crash in the program
2920 @code{genflags} or @code{genoutput} while building GCC. This is said to
2921 be due to a bug in @code{sh}. You can probably get around it by running
2922 @code{genflags} or @code{genoutput} manually and then retrying the
2929 @heading @anchor{sparc-sun-solaris*}sparc-sun-solaris*
2930 On Solaris 2, executables of GCC version 2.0.2 are commonly
2931 available, but they have a bug that shows up when compiling current
2932 versions of GCC: undefined symbol errors occur during assembly if you
2935 The solution is to compile the current version of GCC without
2936 @samp{-g}. That makes a working compiler which you can use to recompile
2939 Solaris 2 comes with a number of optional OS packages. Some of these
2940 packages are needed to use GCC fully. If you did not install all
2941 optional packages when installing Solaris, you will need to verify that
2942 the packages that GCC needs are installed.
2944 To check whether an optional package is installed, use
2945 the @code{pkginfo} command. To add an optional package, use the
2946 @code{pkgadd} command. For further details, see the Solaris
2949 For Solaris 2.0 and 2.1, GCC needs six packages: @samp{SUNWarc},
2950 @samp{SUNWbtool}, @samp{SUNWesu}, @samp{SUNWhea}, @samp{SUNWlibm}, and
2953 For Solaris 2.2, GCC needs an additional seventh package: @samp{SUNWsprot}.
2955 On Solaris 2, trying to use the linker and other tools in
2956 @file{/usr/ucb} to install GCC has been observed to cause trouble.
2957 For example, the linker may hang indefinitely. The fix is to remove
2958 @file{/usr/ucb} from your @code{PATH}.
2960 binutils 2.9.1 has known bugs on this platform. We recommend to use
2961 binutils 2.10 or the vendor tools (Sun as, Sun ld).
2963 Unfortunately, C++ shared libraries, including libstdc++, won't work
2964 properly if assembled with Sun as: the linker will complain about
2965 relocations in read-only sections, in the definition of virtual
2966 tables. Also, Sun as fails to process long symbols resulting from
2967 mangling template-heavy C++ function names.
2974 @heading @anchor{sparc-sun-solaris2.7}sparc-sun-solaris2.7
2976 Sun patch 107058-01 (1999-01-13) for SPARC Solaris 7 triggers a bug in
2977 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
2978 and later, including all EGCS releases. Sun formerly recommended
2979 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
2980 recommend it only for people who use Sun's compilers.
2982 Here are some workarounds to this problem:
2985 Do not install Sun patch 107058-01 until after Sun releases a
2986 complete patch for bug 4210064. This is the simplest course to take,
2987 unless you must also use Sun's C compiler. Unfortunately 107058-01
2988 is preinstalled on some new Solaris-based hosts, so you may have to
2992 Copy the original, unpatched Solaris 7
2993 @command{/usr/ccs/bin/as} into
2994 @command{/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/2.95.1/as},
2995 adjusting the latter name to fit your local conventions and software
2999 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
3000 both 107058-01 and 106950-03 installed has reported the bug with GCC
3001 and Sun's dynamic linker. This last course of action is riskiest,
3002 for two reasons. First, you must install 106950 on all hosts that
3003 run code generated by GCC; it doesn't suffice to install it only on
3004 the hosts that run GCC itself. Second, Sun says that 106950-03 is
3005 only a partial fix for bug 4210064, but Sun doesn't know whether the
3006 partial fix is adequate for GCC. Revision -08 or later should fix
3007 the bug, but (as of 1999-10-06) it is still being tested.
3014 <!-- ripped from the same FAQ that I answered -->
3016 @heading @anchor{*-sun-solaris2.8}*-sun-solaris2.8
3018 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3019 newer: g++ will complain that types are missing. These headers assume
3020 that omitting the type means 'int'; this assumption worked for C89 but
3021 is wrong for C++, and is now wrong for C99 also.
3023 g++ accepts such (illegal) constructs with the option @option{-fpermissive}; it
3024 will assume that any missing type is 'int' (as defined by C89).
3026 For Solaris 8, this is fixed by revision 24 or later of patch 108652
3027 (for SPARCs) or 108653 (for Intels).
3034 @heading @anchor{sunv5}Sun V5.0 Compiler Bugs
3036 The Sun V5.0 compilers are known to mis-compile GCC 2.95 and GCC 2.95.1,
3037 which in turn causes GCC to fail its bootstrap comparison test.
3038 GCC 2.95.2 has a workaround.
3045 @heading @anchor{sparc-sun-sunos*}sparc-sun-sunos*
3047 A bug in the SunOS4 linker will cause it to crash when linking
3048 -fPIC compiled objects (and will therefore not allow you to build
3051 To fix this problem you can either use the most recent version of
3052 binutils or get the latest SunOS4 linker patch (patch ID 100170-10)
3053 from Sun's patch site.
3060 @heading @anchor{sparc-unknown-linux-gnulibc1}sparc-unknown-linux-gnulibc1
3062 It has been reported that you might need
3063 @uref{ftp://ftp.yggdrasil.com/private/hjl,,binutils-2.8.1.0.23}
3064 for this platform, too.
3071 @heading @anchor{sparc64-*-*}sparc64-*-*
3073 GCC version 2.95 is not able to compile code correctly for
3074 @code{sparc64} targets. Users of the Linux kernel, at least,
3075 12~can use the @code{sparc32} program to start up a new shell
3076 invocation with an environment that causes @command{configure} to
3077 recognize (via @samp{uname -a}) the system as @var{sparc-*-*} instead.
3084 @heading @anchor{#*-*-sysv*}*-*-sysv*
3085 On System V release 3, you may get this error message
3089 ld fatal: failed to write symbol name @var{something}
3090 in strings table for file @var{whatever}
3093 This probably indicates that the disk is full or your ULIMIT won't allow
3094 the file to be as large as it needs to be.
3096 This problem can also result because the kernel parameter @code{MAXUMEM}
3097 is too small. If so, you must regenerate the kernel and make the value
3098 much larger. The default value is reported to be 1024; a value of 32768
3099 is said to work. Smaller values may also work.
3101 On System V, if you get an error like this,
3104 /usr/local/lib/bison.simple: In function `yyparse':
3105 /usr/local/lib/bison.simple:625: virtual memory exhausted
3109 that too indicates a problem with disk space, ULIMIT, or @code{MAXUMEM}.
3111 On a System V release 4 system, make sure @file{/usr/bin} precedes
3112 @file{/usr/ucb} in @code{PATH}. The @code{cc} command in
3113 @file{/usr/ucb} uses libraries which have bugs.
3119 @heading @anchor{vax-dec-ultrix}vax-dec-ultrix
3120 Don't try compiling with Vax C (@code{vcc}). It produces incorrect code
3121 in some cases (for example, when @code{alloca} is used).
3123 Meanwhile, compiling @file{cp/parse.c} with pcc does not work because of
3124 an internal table size limitation in that compiler. To avoid this
3125 problem, compile just the GNU C compiler first, and use it to recompile
3126 building all the languages that you want to run.
3132 @heading @anchor{we32k-*-*}we32k-*-*
3133 These computers are also known as the 3b2, 3b5, 3b20 and other similar
3134 names. (However, the 3b1 is actually a 68000.)
3136 Don't use @samp{-g} when compiling with the system's compiler. The
3137 system's linker seems to be unable to handle such a large program with
3138 debugging information.
3140 The system's compiler runs out of capacity when compiling @file{stmt.c}
3141 in GNU CC. You can work around this by building @file{cpp} in GNU CC
3142 first, then use that instead of the system's preprocessor with the
3143 system's C compiler to compile @file{stmt.c}. Here is how:
3146 mv /lib/cpp /lib/cpp.att
3148 echo '/lib/cpp.gnu -traditional $@{1+"$@@"@}' > /lib/cpp
3152 The system's compiler produces bad code for some of the GNU CC
3153 optimization files. So you must build the stage 2 compiler without
3154 optimization. Then build a stage 3 compiler with optimization.
3155 That executable should work. Here are the necessary commands:
3158 make LANGUAGES=c CC=stage1/xgcc CFLAGS="-Bstage1/ -g"
3160 make CC=stage2/xgcc CFLAGS="-Bstage2/ -g -O"
3163 You may need to raise the ULIMIT setting to build a C++ compiler,
3164 as the file @file{cc1plus} is larger than one megabyte.
3170 @heading @anchor{windows}Microsoft Windows (32 bit)
3172 A port of GCC 2.95.x is included with the
3173 @uref{http://www.cygwin.com/,,Cygwin environment}.
3175 Current (as of early 2001) snapshots of GCC will build under Cygwin
3176 without modification.
3182 @heading @anchor{os2}OS/2
3184 GCC does not currently support OS/2. However, Andrew Zabolotny has been
3185 working on a generic OS/2 port with pgcc. The current code code can be found
3186 at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
3188 An older copy of GCC 2.8.1 is included with the EMX tools available at
3189 @uref{ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/,,
3190 ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/}.
3196 @heading @anchor{older}Older systems
3198 GCC contains support files for many older (1980s and early
3199 1990s) Unix variants. For the most part, support for these systems
3200 has not been deliberately removed, but it has not been maintained for
3201 several years and may suffer from bitrot. Support from some systems
3202 has been removed from GCC 3: fx80, ns32-ns-genix, pyramid, tahoe,
3203 gmicro, spur; most of these targets had not been updated since GCC
3206 Support for older systems as targets for cross-compilation is less
3207 problematic than support for them as hosts for GCC; if an enthusiast
3208 wishes to make such a target work again (including resurrecting any
3209 of the targets that never worked with GCC 2, starting from the last
3210 CVS version before they were removed), patches
3211 @uref{../contribute.html,,following the usual requirements}
3212 would be likely to be accepted, since they should not affect the
3213 support for more modern targets.
3215 Support for old systems as hosts for GCC can cause problems if the
3216 workarounds for compiler, library and operating system bugs affect the
3217 cleanliness or maintainability of the rest of GCC. In some cases, to
3218 bring GCC up on such a system, if still possible with current GCC, may
3219 require first installing an old version of GCC which did work on that
3220 system, and using it to compile a more recent GCC, to avoid bugs in
3221 the vendor compiler. Old releases of GCC 1 and GCC 2 are available in
3222 the old-releases directory on the
3223 @uref{../mirrors.html,,GCC mirror sites}. Header bugs may generally
3224 be avoided using @command{fixincludes}, but bugs or deficiencies in
3225 libraries and the operating system may still cause problems.
3227 For some systems, old versions of GNU binutils may also be useful,
3228 and are available from pub/binutils/old-releases on
3229 @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}.
3231 Some of the information on specific systems above relates to
3232 such older systems, but much of the information
3233 about GCC on such systems (which may no longer be applicable to
3234 current GCC) is to be found in the GCC texinfo manual.
3240 @heading @anchor{elf_targets}all ELF targets (SVR4, Solaris, etc.)
3242 C++ support is significantly better on ELF targets if you use the
3243 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
3244 inlines, vtables and template instantiations will be discarded
3254 @uref{./index.html,,Return to the GCC Installation page}
3258 @c ***************************************************************************
3259 @c Part 6 The End of the Document
3261 @comment node-name, next, previous, up
3262 @node Concept Index, , Specific, Top
3266 @unnumbered Concept Index