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.13 2001/06/02 22:33:30 jsm28 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 and Fortran. In the future the GNU compiler testsuites
189 will be included in the full distribution.
191 If you choose to download specific components, you must download the core
192 gcc distribution plus any language specific distributions you wish to
193 use. The core distribution includes the C language front-end as well as the
194 shared components. Each language has a tarball which includes the language
195 front-end as well as the language runtime (when appropriate).
197 Unpack the core distribution as well as any language specific
198 distributions in the same directory.
200 If you also intend to build binutils (either to upgrade an existing
201 installation or for use in place of the corresponding tools of your
202 OS), unpack the binutils distribution either in the same directory or
203 a separate one. In the latter case, add symbolic links to any
204 components of the binutils you intend to build alongside the compiler
205 (bfd, binutils, gas, gprof, ld, opcodes,...) to the directory containing
213 @uref{./index.html,,Return to the GCC Installation page}
217 @c ***Configuration***********************************************************
219 @comment node-name, next, previous, up
220 @node Configuration, Building, Downloading the source, Installing GCC
224 <h1 align="center">Installing GCC: Configuration</h1>
227 @chapter Installing GCC: Configuration
229 @cindex Configuration
230 @cindex Installing GCC: Configuration
232 Like most GNU software, GCC must be configured before it can be built.
233 This document describes the recommended configuration procedure
234 for both native and cross targets.
236 We use @var{srcdir} to refer to the toplevel source directory for
237 GCC; we use @var{objdir} to refer to the toplevel build/object directory.
239 If you obtained the sources via CVS, @var{srcdir} must refer to the top
240 @file{gcc} directory, the one where the @file{MAINTAINERS} can be found,
241 and not its @file{gcc} subdirectory, otherwise the build will fail.
243 First, we @strong{highly} recommend that GCC be built into a
244 separate directory than the sources which does @strong{not} reside
245 within the source tree. This is how we generally build GCC; building
246 where @var{srcdir} == @var{objdir} should still work, but doesn't
247 get extensive testing; building where @var{objdir} is a subdirectory
248 of @var{srcdir} is unsupported.
250 Second, when configuring a native system, either @command{cc} or
251 @command{gcc} must be in your path or you must set @env{CC} in
252 your environment before running configure. Otherwise the configuration
260 % @var{srcdir}/configure [@var{target}] [@var{options}]
264 @heading Target specification
267 GCC has code to correctly determine the correct value for @var{target}
268 for nearly all native systems. Therefore, we highly recommend you not
269 provide a configure target when configuring a native compiler.
272 @var{target} must be specified as @option{--target=}@var{target}
273 when configuring a cross compiler; examples of valid targets would be
274 i960-rtems, m68k-coff, sh-elf, etc.
277 Specifying just @var{target} instead of @option{--target=}@var{target}
278 implies that the host defaults to @var{target}.
282 @heading Options specification
284 Use @var{options} to override several configure time options for
285 GCC. A partial list of supported @var{options}:
288 @item --prefix=@var{dirname}
289 Specify the toplevel installation
290 directory. This is the recommended way to install the tools into a directory
291 other than the default. The toplevel installation directory defaults to
294 We @strong{highly} recommend against @var{dirname} being the same or a
295 subdirectory of @var{objdir} or vice versa.
297 These additional options control where certain parts of the distribution
298 are installed. Normally you should not need to use these options.
301 @item --with-gxx-include-dir=@var{dirname}
303 the installation directory for g++ header files. The default is
304 @file{/usr/local/include/g++}.
308 @item --with-local-prefix=@var{dirname}
310 installation directory for local include files. The default is
311 @file{/usr/local}. Specify this option if you want the compiler to
312 search directory @file{@var{dirname}/include} for locally installed
313 header files @emph{instead} of @file{/usr/local/include}.
315 You should specify @option{--with-local-prefix} @strong{only} if your
316 site has a different convention (not @file{/usr/local}) for where to put
319 The default value for @option{--with-local-prefix} is @file{/usr/local}
320 regardless of the value of @option{--prefix}. Specifying
321 @option{--prefix} has no effect on which directory GCC searches for
322 local header files. This may seem counterintuitive, but actually it is
325 The purpose of @option{--prefix} is to specify where to @emph{install
326 GCC}. The local header files in @file{/usr/local/include}---if you put
327 any in that directory---are not part of GCC. They are part of other
328 programs---perhaps many others. (GCC installs its own header files in
329 another directory which is based on the @option{--prefix} value.)
331 @strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
332 The directory you use for @option{--with-local-prefix} @strong{must not}
333 contain any of the system's standard header files. If it did contain
334 them, certain programs would be miscompiled (including GNU Emacs, on
335 certain targets), because this would override and nullify the header
336 file corrections made by the @code{fixincludes} script.
338 Indications are that people who use this option use it based on mistaken
339 ideas of what it is for. People use it as if it specified where to
340 install part of GCC. Perhaps they make this assumption because
341 installing GCC creates the directory.
343 @item --enable-shared
344 Build shared versions of the
345 C++ runtime libraries if supported. This is the default on most
346 systems. Use @option{--disable-shared} for static libraries. Note that
347 up to the gcc version 2.95.x series, static libraries were the default
350 @item @anchor{with-gnu-as}--with-gnu-as
351 Specify that the compiler should assume that the
352 assembler it finds is the GNU assembler. However, this does not modify
353 the rules to find an assembler and will result in confusion if found
354 assembler is not actually the GNU assembler. If you have more than one
355 assembler installed on your system, you may want to use this option in
356 connection with @option{--with-as=@file{/path/to/gas}}.
358 @item --with-as=@file{/path/to/as}
360 compiler should use the assembler pointed to by @var{pathname}, rather
361 than the one found by the standard rules to find an assembler, which
366 @file{@var{exec_prefix}/lib/gcc-lib/@var{target}/@var{version}}
367 directory, where @var{exec_prefix} defaults to @var{prefix} which
368 defaults to @file{/usr/local} unless overridden by the
369 @option{--prefix=/pathname} switch described above. @var{target} is the
370 target system triple, such as @var{sparc-sun-solaris2.7}, and
371 @var{version} denotes the GCC version, such as 2.95.2.
373 Check operating system specific directories (e.g. @file{/usr/ccs/bin} on
376 Note that these rules do not check for the value of @env{PATH}. You may
377 want to use @option{--with-as} if no assembler is installed in the
378 directories listed above, or if you have multiple assemblers installed
379 and want to choose one that is not found by the above rules.
381 @item @anchor{with-gnu-ld}--with-gnu-ld
382 Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
386 @item --with-ld=@file{/path/to/ld}
388 @option{--with-as}, but for the linker.
391 Specify that stabs debugging
392 information should be used instead of whatever format the host normally
393 uses. Normally GCC uses the same debug format as the host system.
395 @item --enable-multilib
396 Specify that multiple target
397 libraries should be built to support different target variants, calling
398 conventions, etc. This is the default.
400 @item --enable-threads
401 Specify that the target
402 supports threads. This affects the Objective-C compiler and runtime
403 library, and exception handling for other languages like C++ and Java.
404 On some systems, this is the default.
406 @item --enable-threads=@var{lib}
408 @var{lib} is the thread support library. This affects the Objective-C
409 compiler and runtime library, and exception handling for other languages
410 like C++ and Java. The possibilities for @var{lib} are @samp{aix},
411 @samp{dce}, @samp{decosf1}, @samp{irix}, @samp{mach}, @samp{os2},
412 @samp{posix}, @samp{pthreads}, @samp{single}, @samp{solaris},
413 @samp{vxworks} and @samp{win32}.
415 @item --with-cpu=@var{cpu}
416 Specify which cpu variant the
417 compiler should generate code for by default. This is currently
418 only supported on the some ports, specifically arm, powerpc, and
419 SPARC. If configure does not recognize the model name (e.g. arm700,
420 603e, or ultrasparc) you provide, please check the configure script
421 for a complete list of supported models.
423 @item --enable-target-optspace
425 libraries should be optimized for code space instead of code speed.
426 This is the default for the m32r platform.
429 Specify that a shell script which
430 emulates traditional cpp functionality should be installed.
432 @item --enable-cpplib
433 Specify that the functionality of
434 CPP should be integrated into the compiler itself. This option is
435 not supported by snapshots since November 2000. In snapshots where
436 it is supported, it is not enabled by default, except for snapshots
437 very close to November 2000.
439 @item --enable-maintainer-mode
441 regenerate the GCC master message catalog @code{gcc.pot} are normally
442 disabled. This is because it can only be rebuilt if the complete source
443 tree is present. If you have changed the sources and want to rebuild the
444 catalog, configuring with @option{--enable-maintainer-mode} will enable
445 this. Note that you need a recent version of the @code{gettext} tools
448 @item --without-fast-fixincludes
450 old, slower method of fixing the system header files should be used.
451 EGCS 1.1.x and older releases default to the slow version. GCC 2.95 and
452 newer releases will default to the fast version.
454 @item --enable-version-specific-runtime-libs
456 that runtime libraries should be installed in the compiler specific
457 subdirectory (@file{@var{libsubdir}}) rather than the usual places. In
458 addition, libstdc++'s include files will be installed in
459 @file{@var{libsubdir}/include/g++} unless you overruled it by using
460 @option{--with-gxx-include-dir=}@var{dirname}. Using this option is
461 particularly useful if you intend to use several versions of GCC in
462 parallel. This is currently supported by @option{libf2c} and
465 @item --enable-languages=@var{lang1},@var{lang2},@dots{}
466 Specify that only a particular subset of compilers and
467 their runtime libraries should be built. For a list of valid values for
468 @var{lang}@option{x} you can issue the following command in the
469 @file{gcc} directory of your GCC source tree:@* @samp{grep language=
470 */config-lang.in}@* Currently, you can use any of the following:
471 @code{c++}, @code{f77}, @code{java} and @code{objc}.
472 @code{CHILL} is not currently maintained, and will almost
473 certainly fail to compile. Note that this switch does not work with
474 EGCS 1.1.2 or older versions of egcs. It is supported in GCC 2.95
475 and newer versions.@*
476 If you do not pass this flag, all languages available in the @file{gcc}
477 sub-tree will be configured. Re-defining LANGUAGES when calling
478 @samp{make bootstrap} @strong{does not} work anymore, as those
479 language sub-directories might not have been configured!
481 @item --disable-libgcj
482 Specify that the run-time libraries
483 used by GCJ should not be built. This is useful in case you intend
484 to use GCJ with some other run-time, or you're going to install it
485 separately, or it just happens not to build on your particular
486 machine. In general, if the Java front-end is enabled, the GCJ
487 libraries will be enabled too, unless they're known to not work on
488 the target platform. If GCJ is enabled but libgcj isn't built, you
489 may need to port it; in this case, before modifying the top-level
490 configure.in so that libgcj is enabled by default on this platform,
491 you may use @option{--enable-libgcj} to override the default.
494 Specify that the compiler should
495 use DWARF2 debugging information as the default.
498 Some options which only apply to building cross compilers:
500 @item --with-headers=@var{dir}
501 Specifies a directory
502 which has target include files.
503 @emph{This options is required} when building a cross
504 compiler, if @file{@var{prefix}/@var{target}/sys-include} doesn't pre-exist.
505 These include files will be copied into the @file{gcc} install directory.
506 Fixincludes will be run on these files to make them compatible with
508 @item --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
509 Specifies a list of directories which contain the target runtime
510 libraries. These libraries will be copied into the @file{gcc} install
513 Specifies that ``newlib'' is
514 being used as the target C library. This causes @code{__eprintf} to be
515 omitted from libgcc.a on the assumption that it will be provided by
519 Note that each @option{--enable} option has a corresponding
520 @option{--disable} option and that each @option{--with} option has a
521 corresponding @option{--without} option.
528 @uref{./index.html,,Return to the GCC Installation page}
532 @c ***Building****************************************************************
534 @comment node-name, next, previous, up
535 @node Building, Testing, Configuration, Installing GCC
539 <h1 align="center">Installing GCC: Building</h1>
544 @cindex Installing GCC: Building
546 Now that GCC is configured, you are ready to build the compiler and
549 We @strong{highly} recommend that GCC be built using GNU make;
550 other versions may work, then again they might not.
552 (For example, many broken versions of make will fail if you use the
553 recommended setup where @var{objdir} is different from @var{srcdir}.
554 Other broken versions may recompile parts of the compiler when
555 installing the compiler.)
557 Some commands executed when making the compiler may fail (return a
558 non-zero status) and be ignored by @code{make}. These failures, which
559 are often due to files that were not found, are expected, and can safely
562 It is normal to have compiler warnings when compiling certain files.
563 Unless you are a GCC developer, you can generally ignore these warnings
564 unless they cause compilation to fail.
566 On certain old systems, defining certain environment variables such as
567 @code{CC} can interfere with the functioning of @code{make}.
569 If you encounter seemingly strange errors when trying to build the
570 compiler in a directory other than the source directory, it could be
571 because you have previously configured the compiler in the source
572 directory. Make sure you have done all the necessary preparations.
574 If you build GCC on a BSD system using a directory stored in an old System
575 V file system, problems may occur in running @code{fixincludes} if the
576 System V file system doesn't support symbolic links. These problems
577 result in a failure to fix the declaration of @code{size_t} in
578 @file{sys/types.h}. If you find that @code{size_t} is a signed type and
579 that type mismatches occur, this could be the cause.
581 The solution is not to use such a directory for building GCC.
583 @section Building a native compiler
585 For a native build issue the command @samp{make bootstrap}. This
586 will build the entire GCC system, which includes the following steps:
590 Build host tools necessary to build the compiler such as texinfo, bison,
594 Build target tools for use by the compiler such as binutils (bfd,
595 binutils, gas, gprof, ld, and opcodes)@*
596 if they have been individually linked
597 or moved into the top level GCC source tree before configuring.
600 Perform a 3-stage bootstrap of the compiler.
603 Perform a comparison test of the stage2 and stage3 compilers.
606 Build runtime libraries using the stage3 compiler from the previous step.
610 If you are short on disk space you might consider @samp{make
611 bootstrap-lean} instead. This is identical to @samp{make
612 bootstrap} except that object files from the stage1 and
613 stage2 of the 3-stage bootstrap of the compiler are deleted as
614 soon as they are no longer needed.
617 If you want to save additional space during the bootstrap and in
618 the final installation as well, you can build the compiler binaries
619 without debugging information with @samp{make CFLAGS='-O' LIBCFLAGS='-g
620 -O2' LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap}. This will save
621 roughly 40% of disk space both for the bootstrap and the final installation.
622 (Libraries will still contain debugging information.)
624 If you used the flag @option{--enable-languages=...} to restrict
625 the compilers to be built, only those you've actually enabled will be
626 built. This will of course only build those runtime libraries, for
627 which the particular compiler has been built. Please note,
628 that re-defining LANGUAGES when calling @samp{make bootstrap}
629 @strong{does not} work anymore!
632 @section Building a cross compiler
634 We recommend reading the
635 @uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ}
636 for information about building cross compilers.
638 When building a cross compiler, it is not generally possible to do a
639 3-stage bootstrap of the compiler. This makes for an interesting problem
640 as parts of GCC can only be built with GCC.
642 To build a cross compiler, we first recommend building and installing a
643 native compiler. You can then use the native GCC compiler to build the
646 Assuming you have already installed a native copy of GCC and configured
647 your cross compiler, issue the command @samp{make}, which performs the
652 Build host tools necessary to build the compiler such as texinfo, bison,
656 Build target tools for use by the compiler such as binutils (bfd,
657 binutils, gas, gprof, ld, and opcodes)
658 if they have been individually linked or moved into the top level GCC source
659 tree before configuring.
662 Build the compiler (single stage only).
665 Build runtime libraries using the compiler from the previous step.
668 Note that if an error occurs in any step the make process will exit.
670 @section Building in parallel
672 If you have a multiprocessor system you can use @samp{make bootstrap
673 MAKE="make -j 2" -j 2} or just @samp{make -j 2 bootstrap}
674 for GNU Make 3.79 and above instead of just @samp{make bootstrap}
675 when building GCC. You can use a bigger number instead of two if
676 you like. In most cases, it won't help to use a number bigger than
677 the number of processors in your machine.
684 @uref{./index.html,,Return to the GCC Installation page}
688 @c ***Testing*****************************************************************
690 @comment node-name, next, previous, up
691 @node Testing, Final install, Building, Installing GCC
695 <h1 align="center">Installing GCC: Testing</h1>
698 @chapter Installing GCC: Testing
701 @cindex Installing GCC: Testing
704 @strong{Please note that this is only applicable
705 to current development versions of GCC and GCC 3.0 or later.
706 GCC 2.95.x does not come with a testsuite.}
708 Before you install GCC, you might wish to run the testsuite. This
709 step is optional and may require you to download additional software.
711 First, you must have @uref{download.html,,downloaded the testsuites}.
712 The full distribution contains testsuites; only if you downloaded the
713 ``core'' compiler plus any front ends, you do not have the testsuites.
715 Second, you must have a @uref{http://www.gnu.org/software/dejagnu/,,current version of DejaGnu} installed;
716 dejagnu 1.3 is not sufficient.
718 Now you may need specific preparations:
722 In order to run the libio tests on targets which do not fully
723 support Unix/POSIX commands (e.g. Cygwin), the references to the dbz
724 directory have to be deleted from @code{libio/configure.in}.
727 The following environment variables must be set appropriately, as in
728 the following example (which assumes that DejaGnu has been installed
729 under @code{/usr/local}):
732 TCL_LIBRARY = /usr/local/share/tcl8.0
733 DEJAGNULIBS = /usr/local/share/dejagnu
736 On systems such as Cygwin, these paths are required to be actual
737 paths, not mounts or links; presumably this is due to some lack of
738 portability in the DejaGnu code.
742 Finally, you can run the testsuite (which may take a long time):
744 cd @var{objdir}; make -k check
747 The testing process will try to test as many components in the GCC
748 distribution as possible, including the C, C++ and Fortran compilers as
749 well as the C++ runtime libraries.
751 @section How can I run the test suite on selected tests?
753 As a first possibility to cut down the number of tests that are run it is
754 possible to use @samp{make check-gcc} or @samp{make check-g++}
755 in the gcc subdirectory of the object directory. To further cut down the
756 tests the following is possible:
759 make check-gcc RUNTESTFLAGS="execute.exp <other options>"
762 This will run all gcc execute tests in the testsuite.
765 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* <other options>"
768 This will run the g++ "old-deja" tests in the testsuite where the filename
771 The *.exp files are located in the testsuite directories of the GCC
772 source, the most important ones being compile.exp, execute.exp, dg.exp
773 and old-deja.exp. To get a list of the possible *.exp files, pipe the
774 output of @samp{make check} into a file and look at the
775 @samp{Running ... .exp} lines.
777 @section How to interpret test results
779 After the testsuite has run you'll find various *.sum and *.log
780 files in the testsuite subdirectories. The *.log files contain a
781 detailed log of the compiler invocations and the corresponding
782 results, the *.sum files summarize the results. These summaries list
783 all the tests that have been run with a corresponding status code:
787 PASS: the test passed as expected
789 XPASS: the test unexpectedly passed
791 FAIL: the test unexpectedly failed
793 XFAIL: the test failed as expected
795 UNSUPPORTED: the test is not supported on this platform
797 ERROR: the testsuite detected an error
799 WARNING: the testsuite detected a possible problem
802 It is normal for some tests to report unexpected failures. At the
803 current time our testing harness does not allow fine grained control
804 over whether or not a test is expected to fail. We expect to fix this
805 problem in future releases.
808 @section Submitting test results
810 If you want to report the results to the GCC project, use the
811 @code{contrib/test_summary} shell script. Start it in the @var{objdir} with
814 @var{srcdir}/contrib/test_summary -p your_commentary.txt -m gcc-testresults@@gcc.gnu.org |sh
817 This script uses the @code{Mail} program to send the results, so
818 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
819 prepended to the testsuite summary and should contain any special
820 remarks you have on your results or your build environment. Please
821 do not edit the testsuite result block or the subject line, as these
822 messages are automatically parsed and presented at the
823 @uref{http://gcc.gnu.org/testresults/,,GCC testresults} web
824 page. Here you can also gather information on how specific tests
825 behave on different platforms and compare them with your results. A
826 few failing testcases are possible even on released versions and you
827 should look here first if you think your results are unreasonable.
831 @c ***Final install***********************************************************
833 @comment node-name, next, previous, up
834 @node Final install, , Testing, Installing GCC
836 @ifset finalinstallhtml
838 <h1 align="center">Installing GCC: Final installation</h1>
841 @chapter Installing GCC: Final installation
844 Now that GCC has been built and tested, you can install it with
845 @samp{cd @var{objdir}; make install} for a native compiler or
846 @samp{cd @var{objdir}; make install LANGUAGES="c c++"} for
847 a cross compiler (note installing cross compilers will be easier in the
850 That step completes the installation of GCC; user level binaries can
851 be found in @file{@var{prefix}/bin} where @var{prefix} is the value you
852 specified with the @option{--prefix} to configure (or @file{/usr/local}
855 If you don't mind, please quickly review the
856 @uref{http://gcc.gnu.org/gcc-2.95/buildstat.html,,build status page}.
857 If your system is not listed, send a note to
858 @uref{mailto:gcc@@gcc.gnu.org,,gcc@@gcc.gnu.org} indicating
859 that you successfully built and installed GCC.
861 Include the output from running @file{@var{srcdir}/config.guess}. (Do not
862 send us the config.guess file itself, just the output from running
865 If you find a bug, please report it following our
866 @uref{../bugs.html,,bug reporting guidelines}.
873 @uref{./index.html,,Return to the GCC Installation page}
877 @c ***Binaries****************************************************************
879 @comment node-name, next, previous, up
880 @node Binaries, Specific, Installing GCC, Top
884 <h1 align="center">Installing GCC: Binaries</h1>
887 @chapter Installing GCC: Binaries
890 @cindex Installing GCC: Binaries
892 We are often asked about pre-compiled versions of GCC. While we cannot
893 provide these for all platforms, below you'll find links to binaries for
894 various platforms where creating them by yourself is not easy due to various
897 Please note that we did not create these binaries, nor do we
898 support them. If you have any problems installing them, please
899 contact their makers.
906 @uref{http://www-frec.bull.com/docs/download.htm,,Bull's Freeware and
907 Shareware Archive for AIX};
910 @uref{http://aixpdlib.seas.ucla.edu,,UCLA Software Library for AIX};
914 DOS - @uref{http://www.delorie.com/djgpp/,,DJGPP};
917 @uref{http://hpux.cae.wisc.edu/,,HP-UX Porting Center};
920 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
921 OpenServer/Unixware};
924 Solaris (SPARC, Intel) - @uref{http://www.sunfreeware.com/,,Sunfreeware};
927 SGI - @uref{http://freeware.sgi.com/,,SGI Freeware};
930 Windows 95, 98, and NT:
933 The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project;
935 @uref{http://www.xraylith.wisc.edu/~khan/software/gnu-win32/,,GNU Win32}
936 related projects by Mumit Khan.
940 @uref{ftp://ftp.thewrittenword.com/packages/free/by-name/gcc-2.95.2/,,The
941 Written Word} offers binaries for Solaris 2.5.1, 2.6, 2.7/SPARC, 2.7/Intel,
942 IRIX 6.2, 6.5, Digital UNIX 4.0D, HP-UX 10.20, and HP-UX 11.00.
946 @uref{http://h8300-hms.sourceforge.net/,,GNU Development Tools for the
947 Hitachi H8/300[HS] Series}
951 In addition to those specific offerings, you can get a binary
952 distribution CD-ROM from the
953 @uref{http://www.fsf.org/order/order.html,,Free Software Foundation}.
954 It contains binaries for a number of platforms, and
955 includes not only GCC, but other stuff as well. The current CD does
956 not contain the latest version of GCC, but it should allow
957 bootstrapping the compiler. An updated version of that disk is in the
965 @uref{./index.html,,Return to the GCC Installation page}
969 @c ***Specific****************************************************************
971 @comment node-name, next, previous, up
972 @node Specific, Concept Index, Binaries, Top
976 <h1 align="center">Host/target specific installation notes for GCC</h1>
979 @chapter Host/target specific installation notes for GCC
982 @cindex Specific installation notes
983 @cindex Target specific installation
984 @cindex Host specific installation
985 @cindex Target specific installation notes
987 Please read this document carefully @emph{before} installing the
988 GNU Compiler Collection on your machine.
993 @uref{#1750a-*-*,,1750a-*-*}
997 @uref{#a29k-*-bsd,,a29k-*-bsd}
999 @uref{#alpha*-dec-linux*,,alpha*-dec-linux*}
1001 @uref{#alpha-*-osf1,,alpha-*-osf1}
1003 @uref{#alpha*-dec-osf*,,alpha*-dec-osf*}
1005 @uref{#arc-*-elf,,arc-*-elf}
1007 @uref{#arm-*-aout,,arm-*-aout}
1009 @uref{#arm-*-elf,,arm-*-elf}
1011 @uref{#arm*-*-linux-gnu,,arm*-*-linux-gnu}
1013 @uref{#arm-*-riscix,,arm-*-riscix}
1017 @uref{#decstation-*,,decstation-*}
1021 @uref{#dsp16xx,,dsp16xx}
1023 @uref{#elxsi-elxsi-bsd,,elxsi-elxsi-bsd}
1025 @uref{#h8300-hms,,h8300-hms}
1027 @uref{#hppa*-hp-hpux*,,hppa*-hp-hpux*}
1029 @uref{#hppa*-hp-hpux9,,hppa*-hp-hpux9}
1031 @uref{#hppa*-hp-hpux10,,hppa*-hp-hpux10}
1033 @uref{#hppa*-hp-hpux11,,hppa*-hp-hpux11}
1035 @uref{#i370-*-*,,i370-*-*}
1037 @uref{#*-*-linux-gnu,,*-*-linux-gnu}
1039 @uref{#ix86-*-linux*oldld,,i?86-*-linux*oldld}
1041 @uref{#ix86-*-linux*aout,,i?86-*-linux*aout}
1043 @uref{#ix86-*-linux*,,i?86-*-linux*}
1045 @uref{#ix86-*-sco,,i?86-*-sco}
1047 @uref{#ix86-*-sco3.2v4,,i?86-*-sco3.2v4}
1049 @uref{#ix86-*-sco3.2v5*,,i?86-*-sco3.2v5*}
1051 @uref{#ix86-*-solaris*,,i?86-*-solaris*}
1053 @uref{#ix86-*-udk,,i?86-*-udk}
1055 @uref{#ix86-*-isc,,i?86-*-isc}
1057 @uref{#ix86-*-esix,,i?86-*-esix}
1059 @uref{#ix86-ibm-aix,,i?86-ibm-aix}
1061 @uref{#ix86-sequent-bsd,,i?86-sequent-bsd}
1063 @uref{#ix86-sequent-ptx1*,,i?86-sequent-ptx1*, i?86-sequent-ptx2*}
1065 @uref{#ix86-*-sysv3*,,i?86-*-sysv3*}
1067 @uref{#i860-intel-osf*,,i860-intel-osf*}
1069 @uref{#*-lynx-lynxos,,*-lynx-lynxos}
1071 @uref{#*-ibm-aix*,,*-ibm-aix*}
1073 @uref{#m32r-*-elf,,m32r-*-elf}
1075 @uref{#m68000-hp-bsd,,m68000-hp-bsd}
1077 @uref{#m6811-elf,,m6811-elf}
1079 @uref{#m6812-elf,,m6812-elf}
1081 @uref{#m68k-altos,,m68k-altos}
1083 @uref{#m68k-apple-aux,,m68k-apple-aux}
1085 @uref{#m68k-att-sysv,,m68k-att-sysv}
1087 @uref{#m68k-bull-sysv,,m68k-bull-sysv}
1089 @uref{#m68k-crds-unox,,m68k-crds-unox}
1091 @uref{#m68k-hp-hpux,,m68k-hp-hpux}
1093 @uref{#m68k-*-nextstep*,,m68k-*-nextstep*}
1095 @uref{#m68k-ncr-*,,m68k-ncr-*}
1097 @uref{#m68k-sun,,m68k-sun}
1099 @uref{#m68k-sun-sunos4.1.1,,m68k-sun-sunos4.1.1}
1101 @uref{#m88k-*-svr3,,m88k-*-svr3}
1103 @uref{#m88k-*-dgux,,m88k-*-dgux}
1105 @uref{#m88k-tektronix-sysv3,,m88k-tektronix-sysv3}
1107 @uref{#mips-*-*,,mips-*-*}
1109 @uref{#mips-mips-bsd,,mips-mips-bsd}
1111 @uref{#mips-mips-riscos*,,mips-mips-riscos*}
1113 @uref{#mips*-sgi-irix[45],,mips*-sgi-irix[45]}
1115 @uref{#mips*-sgi-irix6,,mips*-sgi-irix6}
1117 @uref{#mips-sony-sysv,,mips-sony-sysv}
1119 @uref{#ns32k-encore,,ns32k-encore}
1121 @uref{#ns32k-*-genix,,ns32k-*-genix}
1123 @uref{#ns32k-sequent,,ns32k-sequent}
1125 @uref{#ns32k-utek,,ns32k-utek}
1127 @uref{#powerpc-*-elf,,powerpc-*-elf, powerpc-*-sysv4}
1129 @uref{#powerpc-*-linux-gnu*,,powerpc-*-linux-gnu*}
1131 @uref{#powerpc-*-eabiaix,,powerpc-*-eabiaix}
1133 @uref{#powerpc-*-eabisim,,powerpc-*-eabisim}
1135 @uref{#powerpc-*-eabi,,powerpc-*-eabi}
1137 @uref{#powerpcle-*-elf,,powerpcle-*-elf, powerpcle-*-sysv4}
1139 @uref{#powerpcle-*-eabisim,,powerpcle-*-eabisim}
1141 @uref{#powerpcle-*-eabi,,powerpcle-*-eabi}
1143 @uref{#powerpcle-*-winnt,,powerpcle-*-winnt, powerpcle-*-pe}
1145 @uref{#romp-*-aos,,romp-*-aos, romp-*-mach}
1147 @uref{#*-*-solaris*,,*-*-solaris*}
1149 @uref{#sparc-sun-*,,sparc-sun-*}
1151 @uref{#sparc-sun-solaris*,,sparc-sun-solaris*}
1153 @uref{#sparc-sun-solaris2.7,,sparc-sun-solaris2.7}
1155 @uref{#*-sun-solaris2.8,,*-sun-solaris2.8}
1157 @uref{#sunv5,,Sun V5.0 Compiler Bugs}
1159 @uref{#sparc-sun-sunos*,,sparc-sun-sunos*}
1161 @uref{#sparc-unknown-linux-gnulibc1,,sparc-unknown-linux-gnulibc1}
1163 @uref{#sparc64-*-*,,sparc64-*-*}
1165 @uref{#*-*-sysv*,,*-*-sysv*}
1167 @uref{#vax-dec-ultrix,,vax-dec-ultrix}
1169 @uref{#we32k-*-*,,we32k-*-*}
1171 @uref{#windows,,Microsoft Windows}
1175 @uref{#older,,Older systems}
1180 @uref{#elf_targets,,all ELF targets} (SVR4, Solaris, etc.)
1186 <!-- -------- host/target specific issues start here ---------------- -->
1189 @heading @anchor{1750a-*-*}1750a-*-*
1190 MIL-STD-1750A processors.
1192 The MIL-STD-1750A cross configuration produces output for
1193 @code{as1750}, an assembler/linker available under the GNU Public
1194 License for the 1750A. @code{as1750} can be obtained at
1195 @uref{ftp://ftp.fta-berlin.de/pub/crossgcc/1750gals/}.
1196 A similarly licensed simulator for
1197 the 1750A is available from same address.
1199 You should ignore a fatal error during the building of libgcc (libgcc is
1200 not yet implemented for the 1750A.)
1202 The @code{as1750} assembler requires the file @file{ms1750.inc}, which is
1203 found in the directory @file{config/1750a}.
1205 GNU CC produced the same sections as the Fairchild F9450 C Compiler,
1210 The program code section.
1213 The read/write (RAM) data section.
1216 The read-only (ROM) constants section.
1219 Initialization section (code to copy KREL to SREL).
1222 The smallest addressable unit is 16 bits (BITS_PER_UNIT is 16). This
1223 means that type `char' is represented with a 16-bit word per character.
1224 The 1750A's "Load/Store Upper/Lower Byte" instructions are not used by
1231 @heading @anchor{a29k}a29k
1232 AMD Am29k-family processors. These are normally used in embedded
1233 applications. There are no standard Unix configurations.
1235 corresponds to AMD's standard calling sequence and binary interface
1236 and is compatible with other 29k tools.
1238 You may need to make a variant of the file @file{a29k.h} for your
1239 particular configuration.
1245 @heading @anchor{a29k-*-bsd}a29k-*-bsd
1246 AMD Am29050 used in a system running a variant of BSD Unix.
1252 @heading @anchor{alpha*-dec-linux*}alpha*-dec-linux*
1254 We require binutils 2.11 or newer. Previous binutils releases
1255 had a number of problems with DWARF2 debugging information, not
1256 the least of which is incorrect linking of shared libraries.
1262 @heading @anchor{alpha-*-osf1}alpha-*-osf1
1263 Systems using processors that implement the DEC Alpha architecture and
1264 are running the DEC Unix (OSF/1) operating system, for example the DEC
1265 Alpha AXP systems.CC.)
1267 GNU CC writes a @samp{.verstamp} directive to the assembler output file
1268 unless it is built as a cross-compiler. It gets the version to use from
1269 the system header file @file{/usr/include/stamp.h}. If you install a
1270 new version of DEC Unix, you should rebuild GCC to pick up the new version
1273 Note that since the Alpha is a 64-bit architecture, cross-compilers from
1274 32-bit machines will not generate code as efficient as that generated
1275 when the compiler is running on a 64-bit machine because many
1276 optimizations that depend on being able to represent a word on the
1277 target in an integral value on the host cannot be performed. Building
1278 cross-compilers on the Alpha for 32-bit machines has only been tested in
1279 a few cases and may not work properly.
1281 @code{make compare} may fail on old versions of DEC Unix unless you add
1282 @samp{-save-temps} to @code{CFLAGS}. On these systems, the name of the
1283 assembler input file is stored in the object file, and that makes
1284 comparison fail if it differs between the @code{stage1} and
1285 @code{stage2} compilations. The option @samp{-save-temps} forces a
1286 fixed name to be used for the assembler input file, instead of a
1287 randomly chosen name in @file{/tmp}. Do not add @samp{-save-temps}
1288 unless the comparisons fail without that option. If you add
1289 @samp{-save-temps}, you will have to manually delete the @samp{.i} and
1290 @samp{.s} files after each series of compilations.
1292 GNU CC now supports both the native (ECOFF) debugging format used by DBX
1293 and GDB and an encapsulated STABS format for use only with GDB. See the
1294 discussion of the @samp{--with-stabs} option of @file{configure} above
1295 for more information on these formats and how to select them.
1297 There is a bug in DEC's assembler that produces incorrect line numbers
1298 for ECOFF format when the @samp{.align} directive is used. To work
1299 around this problem, GNU CC will not emit such alignment directives
1300 while writing ECOFF format debugging information even if optimization is
1301 being performed. Unfortunately, this has the very undesirable
1302 side-effect that code addresses when @samp{-O} is specified are
1303 different depending on whether or not @samp{-g} is also specified.
1305 To avoid this behavior, specify @samp{-gstabs+} and use GDB instead of
1306 DBX. DEC is now aware of this problem with the assembler and hopes to
1307 provide a fix shortly.
1313 @heading @anchor{alpha*-dec-osf*}alpha*-dec-osf*
1315 If you install a shared libstdc++ and, when you link a non-trivial C++
1316 program (for example, @file{gcc/testsuite/g++.other/delete3.C}),
1317 the linker reports a couple of errors about multiply-defined symbols
1318 (for example, @code{nothrow}, @code{__throw} and
1319 @code{terminate(void)}), you've probably got a linker bug, for
1320 which there's no known fix. The officially recommended work-around is
1321 to remove the shared libstdc++.
1323 An alternative solution is to arrange that all symbols from
1324 @code{libgcc} get copied to the shared @code{libstdc++};
1325 see detailed solution below. (Surprising as it may seem, this does
1326 indeed fix the problem!) @emph{Beware} that this may bring you
1327 binary-compatibility problems in the future, if you don't use the same
1328 work-around next time you build @code{libstdc++}: if programs
1329 start to depend on @code{libstdc++} to provide symbols that used
1330 to be only in @code{libgcc}, you must arrange that
1331 @code{libstdc++} keeps providing them, otherwise the programs
1332 will have to be relinked.
1334 The magic spell is to add @code{-Wl,-all,-lgcc,-none} to the
1335 definition of macro @code{SHDEPS} in
1336 @file{libstdc++/config/dec-osf.ml} @emph{before}
1337 @file{alpha*-dec-osf*/libstdc++/Makefile} is created (a
1338 @uref{dec-osf-shlibstdc++.patch,,patch}
1339 that does just that is available). If the Makefile already exists, run
1340 @file{./config.status} within directory
1341 @file{alpha*-dec-osf*/libstdc++} (and
1342 @file{alpha*-dec-osf*/ieee/libstdc++}, if it also exists).
1343 Remove any existing @file{libstdc++.so*} from such directories,
1344 and run @samp{make all-target-libstdc++} in the top-level
1345 directory, then @samp{make install-target-libstdc++}.
1347 If you have already removed the build tree, you may just remove
1348 @file{libstdc++.so.2.10.0} from the install tree and re-create
1350 @samp{gcc -shared -o libstdc++.so.2.10.0 -Wl,-all,-lstdc++,-lgcc,-none -lm}.
1352 sub-directory exists, repeat this command in it, with the additional
1353 flag @option{-mieee}.
1359 @heading @anchor{arc-*-elf}arc-*-elf
1360 Argonaut ARC processor.
1361 This configuration is intended for embedded systems.
1367 @heading @anchor{arm-*-aout}arm-*-aout
1368 Advanced RISC Machines ARM-family processors. These are often used in
1369 embedded applications. There are no standard Unix configurations.
1370 This configuration corresponds to the basic instruction sequences and will
1371 produce @file{a.out} format object modules.
1373 You may need to make a variant of the file @file{arm.h} for your particular
1380 @heading @anchor{arm-*-elf}arm-*-elf
1381 This configuration is intended for embedded systems.
1387 @heading @anchor{arm*-*-linux-gnu}arm*-*-linux-gnu
1389 We require GNU binutils 2.10 or newer.
1395 @heading @anchor{arm-*-riscix}arm-*-riscix
1396 The ARM2 or ARM3 processor running RISC iX, Acorn's port of BSD Unix.
1397 If you are running a version of RISC iX prior to 1.2 then you must
1398 specify the version number during configuration. Note that the
1399 assembler shipped with RISC iX does not support stabs debugging
1400 information; a new version of the assembler, with stabs support
1401 included, is now available from Acorn and via ftp
1402 @uref{ftp://ftp.acorn.com/pub/riscix/as+xterm.tar.Z}. To enable stabs
1403 debugging, pass @samp{--with-gnu-as} to configure.
1405 You will need to install GNU @file{sed} before you can run configure.
1411 @heading @anchor{avr}avr
1413 ATMEL AVR-family micro controllers. These are used in embedded
1414 applications. There are no standard Unix configurations. @xref{AVR
1415 Options,, AVR Options, gcc, Using and Porting the GNU Compiler
1416 Collection (GCC)}, for the list of supported MCU types.
1418 Use @samp{configure --target=avr}
1419 @option{--enable-languages="c"}' to configure GCC.
1421 Further installation notes and other useful information about AVR tools
1422 can also be obtained from:
1426 @uref{http://home.overta.ru/users/denisc,,http://home.overta.ru/users/denisc}
1428 @uref{http://www.itnet.pl/amelektr/avr,,http://www.itnet.pl/amelektr/avr}
1431 We @emph{strongly} recommend using binutils 2.11 or newer.
1433 The following error:
1435 Error: register required
1438 indicates that you should upgrade to a newer version of the binutils.
1444 @heading @anchor{decstation-*}decstation-*
1445 MIPS-based DECstations can support three different personalities:
1446 Ultrix, DEC OSF/1, and OSF/rose. (Alpha-based DECstation products have
1447 a configuration name beginning with @samp{alpha-dec}.) To configure GCC
1448 for these platforms use the following configurations:
1451 @item decstation-ultrix
1452 Ultrix configuration.
1454 @item decstation-osf1
1455 Dec's version of OSF/1.
1457 @item decstation-osfrose
1458 Open Software Foundation reference port of OSF/1 which uses the
1459 OSF/rose object file format instead of ECOFF. Normally, you
1460 would not select this configuration.
1463 The MIPS C compiler needs to be told to increase its table size
1464 for switch statements with the @samp{-Wf,-XNg1500} option in
1465 order to compile @file{cp/parse.c}. If you use the @samp{-O2}
1466 optimization option, you also need to use @samp{-Olimit 3000}.
1467 Both of these options are automatically generated in the
1468 @file{Makefile} that the shell script @file{configure} builds.
1469 If you override the @code{CC} make variable and use the MIPS
1470 compilers, you may need to add @samp{-Wf,-XNg1500 -Olimit 3000}.
1476 @heading @anchor{dos}DOS
1478 Please have a look at our @uref{binaries.html,,binaries page}.
1484 @heading @anchor{dsp16xx}dsp16xx
1485 A port to the AT&T DSP1610 family of processors.
1491 @heading @anchor{elxsi-elxsi-bsd}elxsi-elxsi-bsd
1492 The Elxsi's C compiler has known limitations that prevent it from
1493 compiling GNU C. Please contact @email{mrs@@cygnus.com} for more details.
1499 @heading @anchor{h8300-hms}h8300-hms
1500 Hitachi H8/300 series of processors.
1502 Please have a look at our @uref{binaries.html,,binaries page}.
1504 The calling convention and structure layout has changed in release 2.6.
1505 All code must be recompiled. The calling convention now passes the
1506 first three arguments in function calls in registers. Structures are no
1507 longer a multiple of 2 bytes.
1513 @heading @anchor{hppa*-hp-hpux*}hppa*-hp-hpux*
1515 We @emph{highly} recommend using gas/binutils-2.8 or newer on all hppa
1516 platforms; you may encounter a variety of problems when using the HP
1519 Specifically, @option{-g} does not work on HP-UX (since that system
1520 uses a peculiar debugging format which GCC does not know about), unless you
1521 use GAS and GDB and configure GCC with the
1522 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
1523 @option{--with-as=...} options.
1525 If you wish to use pa-risc 2.0 architecture support, you must use either
1526 the HP assembler, gas/binutils-2.11 or a recent
1527 @uref{ftp://sources.redhat.com/pub/binutils/snapshots,,snapshot of gas}.
1529 More specific information to hppa*-hp-hpux* targets follows.
1535 @heading @anchor{hppa*-hp-hpux9}hppa*-hp-hpux9
1537 The HP assembler has major problems on this platform. We've tried to work
1538 around the worst of the problems. However, those workarounds may be causing
1539 linker crashes in some circumstances; the workarounds also probably prevent
1540 shared libraries from working. Use the GNU assembler to avoid these problems.
1543 The configuration scripts for GCC will also trigger a bug in the hpux9
1544 shell. To avoid this problem set @env{CONFIG_SHELL} to @file{/bin/ksh}
1545 and @env{SHELL} to @file{/bin/ksh} in your environment.
1552 @heading @anchor{hppa*-hp-hpux10}hppa*-hp-hpux10
1554 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
1555 @code{PHCO_19798} from HP. HP has two sites which provide patches free of
1561 <a href="http://us-support.external.hp.com">US, Canada, Asia-Pacific, and
1565 @uref{http://us-support.external.hp.com,,}US, Canada, Asia-Pacific, and
1569 @uref{http://europe-support.external.hp.com,,Europe}
1572 The HP assembler on these systems is much better than the hpux9 assembler,
1573 but still has some problems. Most notably the assembler inserts timestamps
1574 into each object file it creates, causing the 3-stage comparison test to fail
1575 during a @samp{make bootstrap}. You should be able to continue by
1576 saying @samp{make all} after getting the failure from @samp{make
1584 @heading @anchor{hppa*-hp-hpux11}hppa*-hp-hpux11
1586 GCC 2.95.2 does not support HP-UX 11, and it cannot generate 64-bit
1587 object files. Current (as of late 2000) snapshots and GCC 3.0 do support
1595 @heading @anchor{i370-*-*}i370-*-*
1596 This port is very preliminary and has many known bugs. We hope to
1597 have a higher-quality port for this machine soon.
1603 @heading @anchor{*-*-linux-gnu}*-*-linux-gnu
1605 If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install
1606 out-of-the-box. You'll get compile errors while building libstdc++.
1607 The patch @uref{glibc-2.2.patch,,glibc-2.2.patch}, that is to be
1608 applied in the GCC source tree, fixes the compatibility problems.
1614 @heading @anchor{ix86-*-linux*oldld}i?86-*-linux*oldld
1615 Use this configuration to generate @file{a.out} binaries on Linux-based
1616 GNU systems if you do not have gas/binutils version 2.5.2 or later
1617 installed. This is an obsolete configuration.
1623 @heading @anchor{ix86-*-linux*aout}i?86-*-linux*aout
1624 Use this configuration to generate @file{a.out} binaries on Linux-based
1625 GNU systems. This configuration is being superseded. You must use
1626 gas/binutils version 2.5.2 or later.
1632 @heading @anchor{ix86-*-linux*}i?86-*-linux*
1634 You will need binutils-2.9.1.0.15 or newer for exception handling to work.
1636 If you receive Signal 11 errors when building on GNU/Linux, then it is
1637 possible you have a hardware problem. Further information on this can be
1638 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
1644 @heading @anchor{ix86-*-sco}i?86-*-sco
1645 Compilation with RCC is recommended. Also, it may be a good idea to
1646 link with GNU malloc instead of the malloc that comes with the system.
1652 @heading @anchor{ix86-*-sco3.2v4}i?86-*-sco3.2v4
1653 Use this configuration for SCO release 3.2 version 4.
1659 @heading @anchor{ix86-*-sco3.2v5*}i?86-*-sco3.2v5*
1660 Use this for the SCO OpenServer Release 5 family of operating systems.
1662 Unlike earlier versions of GCC, the ability to generate COFF with this
1663 target is no longer provided.
1665 Earlier versions of GCC emitted Dwarf-1 when generating ELF to allow
1666 the system debugger to be used. That support was too burdensome to
1667 maintain. GCC now emits only dwarf-2 for this target. This means you
1668 may use either the UDK debugger or GDB to debug programs built by this
1671 If you are building languages other than C, you must follow the instructions
1672 about invoking @samp{make bootstrap} because the native OpenServer
1673 compiler will build a @command{cc1plus} that will not correctly parse many
1674 valid C++ programs including those in @file{libgcc.a}.
1675 @strong{You must do a @samp{make bootstrap} if you are building with the
1678 Use of the @option{-march-pentiumpro} flag can result in
1679 unrecognized opcodes when using the native assembler on OS versions before
1680 5.0.6. (Support for P6 opcodes was added to the native ELF assembler in
1681 that version.) While it's rather rare to see these emitted by GCC yet,
1682 errors of the basic form:
1685 /usr/tmp/ccaNlqBc.s:22:unknown instruction: fcomip
1686 /usr/tmp/ccaNlqBc.s:50:unknown instruction: fucomip
1689 are symptoms of this problem. You may work around this by not
1690 building affected files with that flag, by using the GNU assembler, or
1691 by using the assembler provided with the current version of the OS.
1692 Users of GNU assembler should see the note below for hazards on doing
1695 The native SCO assembler that is provided with the OS at no
1696 charge is normally required. If, however, you must be able to use
1697 the GNU assembler (perhaps you're compiling code with asms that
1698 require GAS syntax) you may configure this package using the flags
1699 @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You must
1700 use a recent version of GNU binutils; versions past 2.9.1 seem to work
1703 In general, the @option{--with-gnu-as} option isn't as well tested
1704 as the native assembler.
1706 Look in @file{gcc/config/i386/sco5.h} (search for "messy") for
1707 additional OpenServer-specific flags.
1709 Systems based on OpenServer before 5.0.4 (@samp{uname -X}
1710 will tell you what you're running) require TLS597 from ftp.sco.com/TLS
1711 for C++ constructors and destructors to work right.
1713 The system linker in (at least) 5.0.4 and 5.0.5 will sometimes
1714 do the wrong thing for a construct that GCC will emit for PIC
1715 code. This can be seen as execution testsuite failures when using
1716 -fPIC on 921215-1.c, 931002-1.c, nestfunc-1.c, and gcov-1.c.
1717 For 5.0.5, an updated linker that will cure this problem is
1718 available. You must install both
1719 @uref{ftp://ftp.sco.com/Supplements/rs505a/,,ftp://ftp.sco.com/Supplements/rs505a/}
1720 and @uref{ftp://ftp.sco.com/SLS/,,OSS499A}.
1722 The dynamic linker in OpenServer 5.0.5 (earlier versions may show
1723 the same problem) aborts on certain g77-compiled programs. It's particularly
1724 likely to be triggered by building Fortran code with the @option{-fPIC} flag.
1725 Although it's conceivable that the error could be triggered by other
1726 code, only G77-compiled code has been observed to cause this abort.
1727 If you are getting core dumps immediately upon execution of your
1728 g77 program - and especially if it's compiled with -fPIC - try applying
1729 @uref{sco_osr5_g77.patch,,@file{sco_osr5_g77.patch}} to your libf2c and
1731 Affected faults, when analyzed in a debugger, will show a stack
1732 backtrace with a fault occurring in @code{rtld()} and the program
1733 running as @file{/usr/lib/ld.so.1}. This problem has been reported to SCO
1734 engineering and will hopefully be addressed in later releases.
1741 @heading @anchor{ix86-*-solaris*}i?86-*-solaris*
1743 GCC 2.95.2, when configured to use the GNU assembler, would invoke
1744 it with the @code{-s} switch, that GNU as up to 2.9.5.0.12 does
1745 not support. If you'd rather not use a newer GNU as nor the native
1746 assembler, you'll need the patch
1747 @uref{x86-sol2-gas.patch,,@file{x86-sol2-gas.patch}}.
1754 @heading @anchor{ix86-*-udk}i?86-*-udk
1756 This target emulates the SCO Universal Development Kit and requires that
1757 package be installed. (If it is installed, you will have a
1758 @file{/udk/usr/ccs/bin/cc } file present.) It's very much like the
1759 @code{i?86-*-unixware7*} target
1760 but is meant to be used when hosting on a system where UDK isn't the
1761 default compiler such as OpenServer 5 or Unixware 2. This target will
1762 generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
1763 with the same warnings and caveats as the SCO UDK.
1765 You can stage1 with either your native compiler or with UDK. If you
1766 don't do a full bootstrap when initially building with your native compiler
1767 you will have an utterly unusable pile of bits as your reward.
1769 This target is a little tricky to build because we have to distinguish
1770 it from the native tools (so it gets headers, startups, and libraries
1771 from the right place) while making the tools not think we're actually
1772 building a cross compiler. The easiest way to do this is with a configure
1775 @samp{CC=/udk/usr/ccs/bin/cc <i>/your/path/to/</i>gcc/configure
1776 --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-}
1778 @emph{You should substitute 'i686' in the above command with the appropriate
1779 processor for your host.}
1781 You should follow this with a @samp{make bootstrap} then
1782 @samp{make install}. You can then access the UDK-targeted GCC
1783 tools by adding @command{udk-} before the commonly known name. For
1784 example, to invoke the C compiler, you would use @command{udk-gcc}.
1785 They will coexist peacefully with any native-target GCC tools you may
1793 @heading @anchor{ix86-*-isc}i?86-*-isc
1794 It may be a good idea to link with GNU malloc instead of the malloc that
1795 comes with the system.
1797 In ISC version 4.1, @file{sed} core dumps when building
1798 @file{deduced.h}. Use the version of @file{sed} from version 4.0.
1804 @heading @anchor{ix86-*-esix}i?86-*-esix
1805 It may be good idea to link with GNU malloc instead of the malloc that
1806 comes with the system.
1812 @heading @anchor{ix86-ibm-aix}i?86-ibm-aix
1813 You need to use GAS version 2.1 or later, and LD from
1814 GNU binutils version 2.2 or later.
1820 @heading @anchor{ix86-sequent-bsd}i?86-sequent-bsd
1821 Go to the Berkeley universe before compiling.
1827 @heading @anchor{ix86-sequent-ptx1*}i?86-sequent-ptx1*, i?86-sequent-ptx2*
1828 You must install GNU @file{sed} before running @file{configure}.
1834 @heading @anchor{#ix86-*-sysv3*}i?86-*-sysv3*
1835 The @code{fixproto} shell script may trigger a bug in the system shell.
1836 If you encounter this problem, upgrade your operating system or
1837 use BASH (the GNU shell) to run @code{fixproto}.
1844 @heading @anchor{i860-intel-osf*}i860-intel-osf*
1845 On the Intel Paragon (an i860 machine), if you are using operating
1846 system version 1.0, you will get warnings or errors about redefinition
1847 of @code{va_arg} when you build GCC.
1849 If this happens, then you need to link most programs with the library
1850 @file{iclib.a}. You must also modify @file{stdio.h} as follows: before
1854 #if defined(__i860__) && !defined(_VA_LIST)
1855 #include <va_list.h>
1869 extern int vprintf(const char *, va_list );
1870 extern int vsprintf(char *, const char *, va_list );
1878 #endif /* __PGC__ */
1881 These problems don't exist in operating system version 1.1.
1887 @heading @anchor{*-lynx-lynxos}*-lynx-lynxos
1888 LynxOS 2.2 and earlier comes with GNU CC 1.x already installed as
1889 @file{/bin/gcc}. You should compile with this instead of @file{/bin/cc}.
1890 You can tell GNU CC to use the GNU assembler and linker, by specifying
1891 @samp{--with-gnu-as --with-gnu-ld} when configuring. These will produce
1892 COFF format object files and executables; otherwise GNU CC will use the
1893 installed tools, which produce @file{a.out} format executables.
1898 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
1900 @heading @anchor{*-ibm-aix*}*-ibm-aix*
1902 AIX Make frequently has problems with GCC makefiles. GNU Make 3.76 or
1903 newer is recommended to build on this platform.
1905 Errors involving "alloca" when building GCC generally are due
1906 to an incorrect definition of @var{CC} in the Makefile or mixing files
1907 compiled with the native C compiler and GCC. During the stage1 phase of
1908 the build, the native AIX compiler @strong{must} be invoked as "cc"
1909 (not "xlc"). Once @command{configure} has been informed of
1910 "xlc", one needs to use @samp{make distclean} to remove the
1911 configure cache files and ensure that @env{CC} environment variable
1912 does not provide a definition that will confuse @command{configure}.
1913 If this error occurs during stage2 or later, then the problem most likely
1914 is the version of Make (see above).
1916 Binutils 2.10 does not support AIX 4.3. Binutils available from the
1917 @uref{http://www-1.ibm.com/servers/aix/products/aixos/linux/,,AIX
1918 Toolbox for Linux: GNU and Open Source tools for AIX};
1919 website does work. Binutils 2.11 is expected to include AIX 4.3
1920 support. The GNU Assembler is necessary for libstdc++ to build. The
1921 AIX native ld still is recommended. The native AIX tools do
1922 interoperate with GCC.
1924 Linking executables and shared libraries may produce warnings of
1925 duplicate symbols. The assembly files generated by GCC for AIX always
1926 have included multiple symbol definitions for certain global variable
1927 and function declarations in the original program. The warnings should
1928 not prevent the linker from producing a correct library or runnable
1931 AIX 4.3 utilizes a "large format" archive to support both 32-bit and
1932 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
1933 to parse archive libraries did not handle the new format correctly.
1934 These routines are used by GCC and result in error messages during
1935 linking such as "not a COFF file". The version of the routines shipped
1936 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
1937 option of the archive command may be used to create archives of 32-bit
1938 objects using the original "small format". A correct version of the
1939 routines is shipped with AIX 4.3.2.
1941 Some versions of the AIX binder (linker) can fail with a relocation
1942 overflow severe error when the @option{-bbigtoc} option is used to link
1943 GCC-produced object files into an executable that overflows the TOC. A fix
1944 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
1945 available from IBM Customer Support and from its
1946 @uref{http://service.boulder.ibm.com/,,service.boulder.ibm.com}
1947 website as PTF U455193.
1949 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
1950 with a segmentation fault when invoked by any version of GCC. A fix for
1951 APAR IX87327 is available from IBM Customer Support and from its
1952 @uref{http://service.boulder.ibm.com/,,service.boulder.ibm.com}
1953 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
1955 The initial assembler shipped with AIX 4.3.0 generates incorrect object
1956 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
1957 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
1958 @uref{http://service.boulder.ibm.com/,,service.boulder.ibm.com}
1959 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
1961 AIX provides National Language Support (NLS). Compilers and assemblers
1962 use NLS to support locale-specific representations of various data
1963 formats including floating-point numbers (e.g., "." vs "," for
1964 separating decimal fractions). There have been problems reported where
1965 GCC does not produce the same floating-point formats that the assembler
1966 expects. If one encouters this problem, set the @env{LANG}
1967 environment variable to "C" or "En_US".
1969 By default, GCC for AIX 4.1 and above produces code that can be used on
1970 both Power or PowerPC processors.
1972 You can specify a default version for the @samp{-mcpu=}@var{cpu_type}
1973 switch by using the configure option @samp{--with-cpu-}@var{cpu_type}.
1979 @heading @anchor{m32r-*-elf}m32r-*-elf
1980 Mitsubishi M32R processor.
1981 This configuration is intended for embedded systems.
1987 @heading @anchor{m68000-hp-bsd}m68000-hp-bsd
1988 HP 9000 series 200 running BSD. Note that the C compiler that comes
1989 with this system cannot compile GNU CC; contact @email{law@@cygnus.com}
1990 to get binaries of GNU CC for bootstrapping.
1996 @heading @anchor{m6811-elf}m6811-elf
1997 Motorola 68HC11 family micro controllers. These are used in embedded
1998 applications. There are no standard Unix configurations.
2004 @heading @anchor{m6812-elf}m6812-elf
2005 Motorola 68HC12 family micro controllers. These are used in embedded
2006 applications. There are no standard Unix configurations.
2012 @heading @anchor{m68k-altos}m68k-altos
2013 Altos 3068. You must use the GNU assembler, linker and debugger.
2014 Also, you must fix a kernel bug. Details in the file @file{README.ALTOS}.
2020 @heading @anchor{m68k-apple-aux}m68k-apple-aux
2021 Apple Macintosh running A/UX.
2022 You may configure GCC to use either the system assembler and
2023 linker or the GNU assembler and linker. You should use the GNU configuration
2024 if you can, especially if you also want to use GNU C++. You enabled
2025 that configuration with + the @samp{--with-gnu-as} and @samp{--with-gnu-ld}
2026 options to @code{configure}.
2028 Note the C compiler that comes
2029 with this system cannot compile GNU CC. You can find binaries of GNU CC
2030 for bootstrapping on @code{jagubox.gsfc.nasa.gov}.
2031 You will also a patched version of @file{/bin/ld} there that
2032 raises some of the arbitrary limits found in the original.
2038 @heading @anchor{m68k-att-sysv}m68k-att-sysv
2039 AT&T 3b1, a.k.a. 7300 PC. This version of GNU CC cannot
2040 be compiled with the system C compiler, which is too buggy.
2041 You will need to get a previous version of GCC and use it to
2042 bootstrap. Binaries are available from the OSU-CIS archive, at
2043 @uref{ftp://archive.cis.ohio-state.edu/pub/att7300/}.
2049 @heading @anchor{m68k-bull-sysv}m68k-bull-sysv
2050 Bull DPX/2 series 200 and 300 with BOS-2.00.45 up to BOS-2.01. GNU CC works
2051 either with native assembler or GNU assembler. You can use
2052 GNU assembler with native coff generation by providing @samp{--with-gnu-as} to
2053 the configure script or use GNU assembler with dbx-in-coff encapsulation
2054 by providing @samp{--with-gnu-as --stabs}. For any problem with native
2055 assembler or for availability of the DPX/2 port of GAS, contact
2056 @email{F.Pierresteguy@@frcl.bull.fr}.
2062 @heading @anchor{m68k-crds-unox}m68k-crds-unox
2063 Use @samp{configure unos} for building on Unos.
2065 The Unos assembler is named @code{casm} instead of @code{as}. For some
2066 strange reason linking @file{/bin/as} to @file{/bin/casm} changes the
2067 behavior, and does not work. So, when installing GNU CC, you should
2068 install the following script as @file{as} in the subdirectory where
2069 the passes of GCC are installed:
2076 The default Unos library is named @file{libunos.a} instead of
2077 @file{libc.a}. To allow GNU CC to function, either change all
2078 references to @samp{-lc} in @file{gcc.c} to @samp{-lunos} or link
2079 @file{/lib/libc.a} to @file{/lib/libunos.a}.
2081 @cindex @code{alloca}, for Unos
2082 When compiling GNU CC with the standard compiler, to overcome bugs in
2083 the support of @code{alloca}, do not use @samp{-O} when making stage 2.
2084 Then use the stage 2 compiler with @samp{-O} to make the stage 3
2085 compiler. This compiler will have the same characteristics as the usual
2086 stage 2 compiler on other systems. Use it to make a stage 4 compiler
2087 and compare that with stage 3 to verify proper compilation.
2089 (Perhaps simply defining @code{ALLOCA} in @file{x-crds} as described in
2090 the comments there will make the above paragraph superfluous. Please
2091 inform us of whether this works.)
2093 Unos uses memory segmentation instead of demand paging, so you will need
2094 a lot of memory. 5 Mb is barely enough if no other tasks are running.
2095 If linking @file{cc1} fails, try putting the object files into a library
2096 and linking from that library.
2102 @heading @anchor{m68k-hp-hpux}m68k-hp-hpux
2103 HP 9000 series 300 or 400 running HP-UX. HP-UX version 8.0 has a bug in
2104 the assembler that prevents compilation of GNU CC. This
2105 bug manifests itself during the first stage of compilation, while
2106 building @file{libgcc2.a}:
2110 cc1: warning: `-g' option not supported on this version of GCC
2111 cc1: warning: `-g1' option not supported on this version of GCC
2112 ./xgcc: Internal compiler error: program as got fatal signal 11
2115 A patched version of the assembler is available as the file
2116 @uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you
2117 have HP software support, the patch can also be obtained directly from
2118 HP, as described in the following note:
2121 This is the patched assembler, to patch SR#1653-010439, where the
2122 assembler aborts on floating point constants.
2124 The bug is not really in the assembler, but in the shared library
2125 version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is
2126 SR#4701-078451. Anyway, the attached assembler uses the archive
2127 library version of ``cvtnum(3c)'' and thus does not exhibit the bug.
2130 This patch is also known as PHCO_4484.
2132 In addition, if you wish to use gas @samp{--with-gnu-as} you must use
2133 gas version 2.1 or later, and you must use the GNU linker version 2.1 or
2134 later. Earlier versions of gas relied upon a program which converted the
2135 gas output into the native HP-UX format, but that program has not been
2136 kept up to date. gdb does not understand that native HP-UX format, so
2137 you must use gas if you wish to use gdb.
2139 On HP-UX version 8.05, but not on 8.07 or more recent versions, the
2140 @code{fixproto} shell script triggers a bug in the system shell. If you
2141 encounter this problem, upgrade your operating system or use BASH (the
2142 GNU shell) to run @code{fixproto}. This bug will cause the fixproto
2143 program to report an error of the form:
2146 ./fixproto: sh internal 1K buffer overflow
2149 To fix this, you can also change the first line of the fixproto script
2161 @heading @anchor{m68k-*-nextstep*}m68k-*-nextstep*
2163 Current GCC versions probably do not work on version 2 of the NeXT
2166 On NeXTStep 3.0, the Objective C compiler does not work, due,
2167 apparently, to a kernel bug that it happens to trigger. This problem
2168 does not happen on 3.1.
2170 You absolutely @strong{must} use GNU sed and GNU make on this platform.
2173 On NEXTSTEP 3.x where x < 3 the build of GCC will abort during
2174 stage1 with an error message like this:
2178 /usr/tmp/ccbbsZ0U.s:987:Unknown pseudo-op: .section
2179 /usr/tmp/ccbbsZ0U.s:987:Rest of line ignored. 1st junk character
2183 The reason for this is the fact that NeXT's assembler for these
2184 versions of the operating system does not support the .section
2185 pseudo op that's needed for full C++ exception functionality.
2187 As NeXT's assembler is a derived work from GNU as, a free
2188 replacement that does can be obtained at
2189 @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}.
2191 If you try to build the integrated C++ & C++ runtime libraries on this system
2192 you will run into trouble with include files. The way to get around this is
2193 to use the following sequence. Note you must have write permission to
2194 the directory @var{prefix} you specified in the configuration process of GCC
2195 for this sequence to work.
2199 make all-texinfo all-bison all-byacc all-binutils all-gas all-ld
2202 make install-headers-tar
2211 @heading @anchor{m68k-ncr-*}m68k-ncr-*
2212 On the Tower models 4@var{n}0 and 6@var{n}0, by default a process is not
2213 allowed to have more than one megabyte of memory. GCC cannot compile
2214 itself (or many other programs) with @samp{-O} in that much memory.
2216 To solve this problem, reconfigure the kernel adding the following line
2217 to the configuration file:
2228 @heading @anchor{m68k-sun}m68k-sun
2229 Sun 3. We do not provide a configuration file to use the Sun FPA by
2230 default, because programs that establish signal handlers for floating
2231 point traps inherently cannot work with the FPA.
2237 @heading @anchor{m68k-sun-sunos4.1.1}m68k-sun-sunos4.1.1
2239 It is reported that you may need the GNU assembler on this platform.
2246 @heading @anchor{m88k-*-svr3}m88k-*-svr3
2247 Motorola m88k running the AT&T/Unisoft/Motorola V.3 reference port.
2248 These systems tend to use the Green Hills C, revision 1.8.5, as the
2249 standard C compiler. There are apparently bugs in this compiler that
2250 result in object files differences between stage 2 and stage 3. If this
2251 happens, make the stage 4 compiler and compare it to the stage 3
2252 compiler. If the stage 3 and stage 4 object files are identical, this
2253 suggests you encountered a problem with the standard C compiler; the
2254 stage 3 and 4 compilers may be usable.
2256 It is best, however, to use an older version of GNU CC for bootstrapping
2263 @heading @anchor{m88k-*-dgux}m88k-*-dgux
2264 Motorola m88k running DG/UX. To build 88open BCS native or cross
2265 compilers on DG/UX, specify the configuration name as
2266 @samp{m88k-*-dguxbcs} and build in the 88open BCS software development
2267 environment. To build ELF native or cross compilers on DG/UX, specify
2268 @samp{m88k-*-dgux} and build in the DG/UX ELF development environment.
2269 You set the software development environment by issuing
2270 @samp{sde-target} command and specifying either @samp{m88kbcs} or
2271 @samp{m88kdguxelf} as the operand.
2273 If you do not specify a configuration name, @file{configure} guesses the
2274 configuration based on the current software development environment.
2280 @heading @anchor{m88k-tektronix-sysv3}m88k-tektronix-sysv3
2281 Tektronix XD88 running UTekV 3.2e. Do not turn on
2282 optimization while building stage1 if you bootstrap with
2283 the buggy Green Hills compiler. Also, The bundled LAI
2284 System V NFS is buggy so if you build in an NFS mounted
2285 directory, start from a fresh reboot, or avoid NFS all together.
2286 Otherwise you may have trouble getting clean comparisons
2293 @heading @anchor{mips-*-*}mips-*-*
2294 If you use the 1.31 version of the MIPS assembler (such as was shipped
2295 with Ultrix 3.1), you will need to use the -fno-delayed-branch switch
2296 when optimizing floating point code. Otherwise, the assembler will
2297 complain when the GCC compiler fills a branch delay slot with a
2298 floating point instruction, such as @code{add.d}.
2300 If on a MIPS system you get an error message saying ``does not have gp
2301 sections for all it's [sic] sectons [sic]'', don't worry about it. This
2302 happens whenever you use GAS with the MIPS linker, but there is not
2303 really anything wrong, and it is okay to use the output file. You can
2304 stop such warnings by installing the GNU linker.
2306 It would be nice to extend GAS to produce the gp tables, but they are
2307 optional, and there should not be a warning about their absence.
2309 Users have reported some problems with version 2.0 of the MIPS
2310 compiler tools that were shipped with Ultrix 4.1. Version 2.10
2311 which came with Ultrix 4.2 seems to work fine.
2313 Users have also reported some problems with version 2.20 of the
2314 MIPS compiler tools that were shipped with RISC/os 4.x. The earlier
2315 version 2.11 seems to work fine.
2317 Some versions of the MIPS linker will issue an assertion failure
2318 when linking code that uses @code{alloca} against shared
2319 libraries on RISC-OS 5.0, and DEC's OSF/1 systems. This is a bug
2320 in the linker, that is supposed to be fixed in future revisions.
2321 To protect against this, GCC passes @samp{-non_shared} to the
2322 linker unless you pass an explicit @samp{-shared} or
2323 @samp{-call_shared} switch.
2325 @heading @anchor{mips-mips-bsd}mips-mips-bsd
2326 MIPS machines running the MIPS operating system in BSD mode. It's
2327 possible that some old versions of the system lack the functions
2328 @code{memcpy}, @code{memmove}, @code{memcmp}, and @code{memset}. If your
2329 system lacks these, you must remove or undo the definition of
2330 @code{TARGET_MEM_FUNCTIONS} in @file{mips-bsd.h}.
2332 The MIPS C compiler needs to be told to increase its table size
2333 for switch statements with the @samp{-Wf,-XNg1500} option in
2334 order to compile @file{cp/parse.c}. If you use the @samp{-O2}
2335 optimization option, you also need to use @samp{-Olimit 3000}.
2336 Both of these options are automatically generated in the
2337 @file{Makefile} that the shell script @file{configure} builds.
2338 If you override the @code{CC} make variable and use the MIPS
2339 compilers, you may need to add @samp{-Wf,-XNg1500 -Olimit 3000}.
2345 @heading @anchor{mips-mips-riscos*}mips-mips-riscos*
2346 The MIPS C compiler needs to be told to increase its table size
2347 for switch statements with the @samp{-Wf,-XNg1500} option in
2348 order to compile @file{cp/parse.c}. If you use the @samp{-O2}
2349 optimization option, you also need to use @samp{-Olimit 3000}.
2350 Both of these options are automatically generated in the
2351 @file{Makefile} that the shell script @file{configure} builds.
2352 If you override the @code{CC} make variable and use the MIPS
2353 compilers, you may need to add @samp{-Wf,-XNg1500 -Olimit 3000}.
2355 MIPS computers running RISC-OS can support four different
2356 personalities: default, BSD 4.3, System V.3, and System V.4
2357 (older versions of RISC-OS don't support V.4). To configure GCC
2358 for these platforms use the following configurations:
2361 @item mips-mips-riscos@code{rev}
2362 Default configuration for RISC-OS, revision @code{rev}.
2364 @item mips-mips-riscos@code{rev}bsd
2365 BSD 4.3 configuration for RISC-OS, revision @code{rev}.
2367 @item mips-mips-riscos@code{rev}sysv4
2368 System V.4 configuration for RISC-OS, revision @code{rev}.
2374 @item mips-mips-riscos@code{rev}sysv
2375 System V.3 configuration for RISC-OS, revision @code{rev}.
2378 The revision @code{rev} mentioned above is the revision of
2379 RISC-OS to use. You must reconfigure GCC when going from a
2380 RISC-OS revision 4 to RISC-OS revision 5. This has the effect of
2381 avoiding a linker bug.
2387 @heading @anchor{mips*-sgi-irix[45]}mips*-sgi-irix[45]
2389 In order to compile GCC on an SGI running IRIX 4, the "c.hdr.lib"
2390 option must be installed from the CD-ROM supplied from Silicon Graphics.
2391 This is found on the 2nd CD in release 4.0.1.
2393 In order to compile GCC on an SGI running IRIX 5, the "compiler_dev.hdr"
2394 subsystem must be installed from the IDO CD-ROM supplied by Silicon
2397 @code{make compare} may fail on version 5 of IRIX unless you add
2398 @samp{-save-temps} to @code{CFLAGS}. On these systems, the name of the
2399 assembler input file is stored in the object file, and that makes
2400 comparison fail if it differs between the @code{stage1} and
2401 @code{stage2} compilations. The option @samp{-save-temps} forces a
2402 fixed name to be used for the assembler input file, instead of a
2403 randomly chosen name in @file{/tmp}. Do not add @samp{-save-temps}
2404 unless the comparisons fail without that option. If you do you
2405 @samp{-save-temps}, you will have to manually delete the @samp{.i} and
2406 @samp{.s} files after each series of compilations.
2408 The MIPS C compiler needs to be told to increase its table size
2409 for switch statements with the @samp{-Wf,-XNg1500} option in
2410 order to compile @file{cp/parse.c}. If you use the @samp{-O2}
2411 optimization option, you also need to use @samp{-Olimit 3000}.
2412 Both of these options are automatically generated in the
2413 @file{Makefile} that the shell script @file{configure} builds.
2414 If you override the @code{CC} make variable and use the MIPS
2415 compilers, you may need to add @samp{-Wf,-XNg1500 -Olimit 3000}.
2417 On Irix version 4.0.5F, and perhaps on some other versions as well,
2418 there is an assembler bug that reorders instructions incorrectly. To
2419 work around it, specify the target configuration
2420 @samp{mips-sgi-irix4loser}. This configuration inhibits assembler
2423 In a compiler configured with target @samp{mips-sgi-irix4}, you can turn
2424 off assembler optimization by using the @samp{-noasmopt} option. This
2425 compiler option passes the option @samp{-O0} to the assembler, to
2428 The @samp{-noasmopt} option can be useful for testing whether a problem
2429 is due to erroneous assembler reordering. Even if a problem does not go
2430 away with @samp{-noasmopt}, it may still be due to assembler
2431 reordering---perhaps GNU CC itself was miscompiled as a result.
2433 To enable debugging under Irix 5, you must use GNU as 2.5 or later,
2434 and use the @samp{--with-gnu-as} configure option when configuring gcc.
2435 GNU as is distributed as part of the binutils package.
2437 You must use GAS on these platforms, as the native assembler can not handle
2438 the code for exception handling support. Either of these messages indicates
2439 that you are using the MIPS assembler when instead you should be using GAS:
2441 @samp{ as0: Error: ./libgcc2.c, line 1:Badly delimited numeric literal
2442 .4byte $LECIE1-$LSCIE1
2443 as0: Error: ./libgcc2.c, line 1:malformed statement}
2447 @samp{ as0: Error: /src/bld-gcc/gcc/libgcc2.c, line 1:undefined symbol in expression
2448 .word $LECIE1-$LSCIE1}
2450 These systems don't have ranlib, which various components in GCC need; you
2451 should be able to avoid this problem by installing GNU binutils, which includes
2452 a functional ranlib for this system.
2454 You may get the following warning on irix4 platforms, it can be safely
2457 warning: foo.o does not have gp tables for all its sections.
2460 When building GCC, the build process loops rebuilding cc1 over and
2461 over again. This happens on mips-sgi-irix5.2, and possibly other platforms.@*
2462 It has been reported that this is a known bug in the make shipped with
2463 IRIX 5.2. We recommend you use GNU make instead of the vendor supplied
2464 make program; however, you may have success with "smake" on IRIX 5.2 if
2465 you do not have GNU make available.
2467 See @uref{http://freeware.sgi.com/,,http://freeware.sgi.com/} for more
2468 information about using GCC on IRIX platforms.
2475 @heading @anchor{mips*-sgi-irix6}mips*-sgi-irix6
2477 You must @emph{not} use GAS on irix6 platforms; doing so will only
2480 These systems don't have ranlib, which various components in GCC need; you
2481 should be able to avoid this problem by making a dummy script called ranlib
2482 which just exits with zero status and placing it in your path.
2484 If you are using Irix cc as your bootstrap compiler, you must
2485 ensure that the N32 ABI is in use. To test this, compile a simple C
2486 file with @command{cc} and then run @command{file} on the
2487 resulting object file. The output should look like:
2490 @code{ test.o: ELF N32 MSB ...}
2495 @code{ test.o: ELF 32-bit MSB}
2498 then your version of @command{cc} uses the O32 ABI default. You
2499 should set the environment variable @env{CC} to @samp{cc -n32}
2500 before configuring GCC.
2502 GCC does not currently support generating O32 ABI binaries in the
2503 mips-sgi-irix6 configurations. It used to be possible to create a GCC
2504 with O32 ABI only support by configuring it for the mips-sgi-irix5
2505 target. See the link below for details.
2507 GCC does not correctly pass/return structures which are
2508 smaller than 16 bytes and which are not 8 bytes. The problem is very
2509 involved and difficult to fix. It affects a number of other targets also,
2510 but IRIX 6 is affected the most, because it is a 64 bit target, and 4 byte
2511 structures are common. The exact problem is that structures are being padded
2512 at the wrong end, e.g. a 4 byte structure is loaded into the lower 4 bytes
2513 of the register when it should be loaded into the upper 4 bytes of the
2516 GCC is consistent with itself, but not consistent with the SGI C compiler
2517 (and the SGI supplied runtime libraries), so the only failures that can
2518 happen are when there are library functions that take/return such
2519 structures. There are very few such library functions. I can only recall
2520 seeing two of them: inet_ntoa, and semctl.
2522 See @uref{http://freeware.sgi.com/,,http://freeware.sgi.com/} for more
2523 information about using GCC on IRIX platforms.
2530 @heading @anchor{mips-sony-sysv}mips-sony-sysv
2531 Sony MIPS NEWS. This works in NEWSOS 5.0.1, but not in 5.0.2 (which
2532 uses ELF instead of COFF). Support for 5.0.2 will probably be provided
2533 soon by volunteers. In particular, the linker does not like the
2534 code generated by GCC when shared libraries are linked in.
2541 @heading @anchor{ns32k-encore}ns32k-encore
2542 Encore ns32000 system. Encore systems are supported only under BSD.
2548 @heading @anchor{ns32k-*-genix}ns32k-*-genix
2549 National Semiconductor ns32000 system. Genix has bugs in @code{alloca}
2550 and @code{malloc}; you must get the compiled versions of these from GNU
2557 @heading @anchor{ns32k-sequent}ns32k-sequent
2558 Go to the Berkeley universe before compiling.
2564 @heading @anchor{ns32k-utek}ns32k-utek
2565 UTEK ns32000 system (``merlin''). The C compiler that comes with this
2566 system cannot compile GNU CC; contact @samp{tektronix!reed!mason} to get
2567 binaries of GNU CC for bootstrapping.
2574 @heading @anchor{powerpc-*-elf}powerpc-*-elf, powerpc-*-sysv4
2575 PowerPC system in big endian mode, running System V.4.
2577 You can specify a default version for the @samp{-mcpu=}@var{cpu_type}
2578 switch by using the configure option @samp{--with-cpu-}@var{cpu_type}.
2584 @heading @anchor{powerpc-*-linux-gnu*}powerpc-*-linux-gnu*
2587 @uref{ftp://ftp.varesearch.com/pub/support/hjl/binutils,,binutils-2.9.4.0.8}
2588 or newer for a working GCC. It is strongly recommended to recompile binutils
2589 if you initially built it with gcc-2.7.2.x.
2591 You can specify a default version for the @samp{-mcpu=}@var{cpu_type}
2592 switch by using the configure option @samp{--with-cpu-}@var{cpu_type}.
2598 @heading @anchor{powerpc-*-eabiaix}powerpc-*-eabiaix
2599 Embedded PowerPC system in big endian mode with -mcall-aix selected as
2602 You can specify a default version for the @samp{-mcpu=}@var{cpu_type}
2603 switch by using the configure option @samp{--with-cpu-}@var{cpu_type}.
2609 @heading @anchor{powerpc-*-eabisim}powerpc-*-eabisim
2610 Embedded PowerPC system in big endian mode for use in running under the
2613 You can specify a default version for the @samp{-mcpu=}@var{cpu_type}
2614 switch by using the configure option @samp{--with-cpu-}@var{cpu_type}.
2620 @heading @anchor{powerpc-*-eabi}powerpc-*-eabi
2621 Embedded PowerPC system in big endian mode.
2623 You can specify a default version for the @samp{-mcpu=}@var{cpu_type}
2624 switch by using the configure option @samp{--with-cpu-}@var{cpu_type}.
2630 @heading @anchor{powerpcle-*-elf}powerpcle-*-elf, powerpcle-*-sysv4
2631 PowerPC system in little endian mode, running System V.4.
2633 You can specify a default version for the @samp{-mcpu=}@var{cpu_type}
2634 switch by using the configure option @samp{--with-cpu-}@var{cpu_type}.
2640 @heading @anchor{powerpcle-*-eabisim}powerpcle-*-eabisim
2641 Embedded PowerPC system in little endian mode for use in running under
2648 @heading @anchor{powerpcle-*-eabi}powerpcle-*-eabi
2649 Embedded PowerPC system in little endian mode.
2651 You can specify a default version for the @samp{-mcpu=}@var{cpu_type}
2652 switch by using the configure option @samp{--with-cpu-}@var{cpu_type}.
2658 @heading @anchor{powerpcle-*-winnt}powerpcle-*-winnt, powerpcle-*-pe
2659 PowerPC system in little endian mode running Windows NT.
2661 You can specify a default version for the @samp{-mcpu=}@var{cpu_type}
2662 switch by using the configure option @samp{--with-cpu-}@var{cpu_type}.
2668 @heading @anchor{romp-*-aos}romp-*-aos, romp-*-mach
2669 The only operating systems supported for the IBM RT PC are AOS and
2670 MACH. GNU CC does not support AIX running on the RT. We recommend you
2671 compile GNU CC with an earlier version of itself; if you compile GNU CC
2672 with @code{hc}, the Metaware compiler, it will work, but you will get
2673 mismatches between the stage 2 and stage 3 compilers in various files.
2674 These errors are minor differences in some floating-point constants and
2675 can be safely ignored; the stage 3 compiler is correct.
2681 @heading @anchor{*-*-solaris*}*-*-solaris*
2683 Starting with Solaris, Sun does not ship a C compiler any more. To
2684 bootstrap and install GCC you first have to install a pre-built
2685 compiler, see our @uref{binaries.html,,binaries page} for
2688 You must use GNU Make to build GCC on Solaris 2. If you don't have GNU
2689 Make installed, you can use the prebuilt compiler mentioned above to
2692 Sun as 4.X is broken in that it cannot cope with long symbol names.
2693 A typical error message might look similar to the following:
2695 @samp{/usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041:
2696 error: can't compute value of an expression involving an external symbol.}
2698 This is Sun bug 4237974. This is fixed with patch 108908-02 and has
2699 been fixed in later (5.x) versions of the assembler.
2705 @heading @anchor{sparc-sun-*}sparc-sun-*
2706 Sometimes on a Sun 4 you may observe a crash in the program
2707 @code{genflags} or @code{genoutput} while building GCC. This is said to
2708 be due to a bug in @code{sh}. You can probably get around it by running
2709 @code{genflags} or @code{genoutput} manually and then retrying the
2716 @heading @anchor{sparc-sun-solaris*}sparc-sun-solaris*
2717 On Solaris 2, executables of GCC version 2.0.2 are commonly
2718 available, but they have a bug that shows up when compiling current
2719 versions of GCC: undefined symbol errors occur during assembly if you
2722 The solution is to compile the current version of GCC without
2723 @samp{-g}. That makes a working compiler which you can use to recompile
2726 Solaris 2 comes with a number of optional OS packages. Some of these
2727 packages are needed to use GCC fully. If you did not install all
2728 optional packages when installing Solaris, you will need to verify that
2729 the packages that GCC needs are installed.
2731 To check whether an optional package is installed, use
2732 the @code{pkginfo} command. To add an optional package, use the
2733 @code{pkgadd} command. For further details, see the Solaris
2736 For Solaris 2.0 and 2.1, GCC needs six packages: @samp{SUNWarc},
2737 @samp{SUNWbtool}, @samp{SUNWesu}, @samp{SUNWhea}, @samp{SUNWlibm}, and
2740 For Solaris 2.2, GCC needs an additional seventh package: @samp{SUNWsprot}.
2742 On Solaris 2, trying to use the linker and other tools in
2743 @file{/usr/ucb} to install GCC has been observed to cause trouble.
2744 For example, the linker may hang indefinitely. The fix is to remove
2745 @file{/usr/ucb} from your @code{PATH}.
2747 binutils 2.9.1 has known bugs on this platform. We recommend to use
2748 binutils 2.10 or the vendor tools (Sun as, Sun ld).
2750 Unfortunately, C++ shared libraries, including libstdc++, won't work
2751 properly if assembled with Sun as: the linker will complain about
2752 relocations in read-only sections, in the definition of virtual
2753 tables. Also, Sun as fails to process long symbols resulting from
2754 mangling template-heavy C++ function names.
2761 @heading @anchor{sparc-sun-solaris2.7}sparc-sun-solaris2.7
2763 Sun patch 107058-01 (1999-01-13) for SPARC Solaris 7 triggers a bug in
2764 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
2765 and later, including all EGCS releases. Sun formerly recommended
2766 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
2767 recommend it only for people who use Sun's compilers.
2769 Here are some workarounds to this problem:
2772 Do not install Sun patch 107058-01 until after Sun releases a
2773 complete patch for bug 4210064. This is the simplest course to take,
2774 unless you must also use Sun's C compiler. Unfortunately 107058-01
2775 is preinstalled on some new Solaris-based hosts, so you may have to
2779 Copy the original, unpatched Solaris 7
2780 @command{/usr/ccs/bin/as} into
2781 @command{/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/2.95.1/as},
2782 adjusting the latter name to fit your local conventions and software
2786 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
2787 both 107058-01 and 106950-03 installed has reported the bug with GCC
2788 and Sun's dynamic linker. This last course of action is riskiest,
2789 for two reasons. First, you must install 106950 on all hosts that
2790 run code generated by GCC; it doesn't suffice to install it only on
2791 the hosts that run GCC itself. Second, Sun says that 106950-03 is
2792 only a partial fix for bug 4210064, but Sun doesn't know whether the
2793 partial fix is adequate for GCC. Revision -08 or later should fix
2794 the bug, but (as of 1999-10-06) it is still being tested.
2801 <!-- ripped from the same FAQ that I answered -->
2803 @heading @anchor{*-sun-solaris2.8}*-sun-solaris2.8
2805 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
2806 newer: g++ will complain that types are missing. These headers assume
2807 that omitting the type means 'int'; this assumption worked for C89 but
2808 is wrong for C++, and is now wrong for C99 also.
2810 g++ accepts such (illegal) constructs with the option @option{-fpermissive}; it
2811 will assume that any missing type is 'int' (as defined by C89).
2813 For Solaris 8, this is fixed by revision 24 or later of patch 108652
2814 (for SPARCs) or 108653 (for Intels).
2821 @heading @anchor{sunv5}Sun V5.0 Compiler Bugs
2823 The Sun V5.0 compilers are known to mis-compile GCC 2.95 and GCC 2.95.1,
2824 which in turn causes GCC to fail its bootstrap comparison test.
2825 GCC 2.95.2 has a workaround.
2832 @heading @anchor{sparc-sun-sunos*}sparc-sun-sunos*
2834 A bug in the SunOS4 linker will cause it to crash when linking
2835 -fPIC compiled objects (and will therefore not allow you to build
2838 To fix this problem you can either use the most recent version of
2839 binutils or get the latest SunOS4 linker patch (patch ID 100170-10)
2840 from Sun's patch site.
2847 @heading @anchor{sparc-unknown-linux-gnulibc1}sparc-unknown-linux-gnulibc1
2849 It has been reported that you might need
2850 @uref{ftp://ftp.yggdrasil.com/private/hjl,,binutils-2.8.1.0.23}
2851 for this platform, too.
2858 @heading @anchor{sparc64-*-*}sparc64-*-*
2860 GCC version 2.95 is not able to compile code correctly for
2861 @code{sparc64} targets. Users of the Linux kernel, at least,
2862 12~can use the @code{sparc32} program to start up a new shell
2863 invocation with an environment that causes @command{configure} to
2864 recognize (via @samp{uname -a}) the system as @var{sparc-*-*} instead.
2871 @heading @anchor{#*-*-sysv*}*-*-sysv*
2872 On System V release 3, you may get this error message
2876 ld fatal: failed to write symbol name @var{something}
2877 in strings table for file @var{whatever}
2880 This probably indicates that the disk is full or your ULIMIT won't allow
2881 the file to be as large as it needs to be.
2883 This problem can also result because the kernel parameter @code{MAXUMEM}
2884 is too small. If so, you must regenerate the kernel and make the value
2885 much larger. The default value is reported to be 1024; a value of 32768
2886 is said to work. Smaller values may also work.
2888 On System V, if you get an error like this,
2891 /usr/local/lib/bison.simple: In function `yyparse':
2892 /usr/local/lib/bison.simple:625: virtual memory exhausted
2896 that too indicates a problem with disk space, ULIMIT, or @code{MAXUMEM}.
2903 @heading @anchor{vax-dec-ultrix}vax-dec-ultrix
2904 Don't try compiling with Vax C (@code{vcc}). It produces incorrect code
2905 in some cases (for example, when @code{alloca} is used).
2907 Meanwhile, compiling @file{cp/parse.c} with pcc does not work because of
2908 an internal table size limitation in that compiler. To avoid this
2909 problem, compile just the GNU C compiler first, and use it to recompile
2910 building all the languages that you want to run.
2916 @heading @anchor{we32k-*-*}we32k-*-*
2917 These computers are also known as the 3b2, 3b5, 3b20 and other similar
2918 names. (However, the 3b1 is actually a 68000.)
2920 Don't use @samp{-g} when compiling with the system's compiler. The
2921 system's linker seems to be unable to handle such a large program with
2922 debugging information.
2924 The system's compiler runs out of capacity when compiling @file{stmt.c}
2925 in GNU CC. You can work around this by building @file{cpp} in GNU CC
2926 first, then use that instead of the system's preprocessor with the
2927 system's C compiler to compile @file{stmt.c}. Here is how:
2930 mv /lib/cpp /lib/cpp.att
2932 echo '/lib/cpp.gnu -traditional $@{1+"$@@"@}' > /lib/cpp
2936 The system's compiler produces bad code for some of the GNU CC
2937 optimization files. So you must build the stage 2 compiler without
2938 optimization. Then build a stage 3 compiler with optimization.
2939 That executable should work. Here are the necessary commands:
2942 make LANGUAGES=c CC=stage1/xgcc CFLAGS="-Bstage1/ -g"
2944 make CC=stage2/xgcc CFLAGS="-Bstage2/ -g -O"
2947 You may need to raise the ULIMIT setting to build a C++ compiler,
2948 as the file @file{cc1plus} is larger than one megabyte.
2954 @heading @anchor{windows}Microsoft Windows (32 bit)
2956 A port of GCC 2.95.x is included with the
2957 @uref{http://www.cygwin.com/,,Cygwin environment}.
2959 Current (as of early 2001) snapshots of GCC will build under Cygwin
2960 without modification.
2966 @heading @anchor{os2}OS/2
2968 GCC does not currently support OS/2. However, Andrew Zabolotny has been
2969 working on a generic OS/2 port with pgcc. The current code code can be found
2970 at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
2972 An older copy of GCC 2.8.1 is included with the EMX tools available at
2973 @uref{ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/,,
2974 ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/}.
2980 @heading @anchor{older}Older systems
2982 GCC contains support files for many older (1980s and early
2983 1990s) Unix variants. For the most part, support for these systems
2984 has not been deliberately removed, but it has not been maintained for
2985 several years and may suffer from bitrot. Support from some systems
2986 has been removed from GCC 3: fx80, ns32-ns-genix, pyramid, tahoe,
2987 gmicro, spur; most of these targets had not been updated since GCC
2990 Support for older systems as targets for cross-compilation is less
2991 problematic than support for them as hosts for GCC; if an enthusiast
2992 wishes to make such a target work again (including resurrecting any
2993 of the targets that never worked with GCC 2, starting from the last
2994 CVS version before they were removed), patches
2995 @uref{../contribute.html,,following the usual requirements}
2996 would be likely to be accepted, since they should not affect the
2997 support for more modern targets.
2999 Support for old systems as hosts for GCC can cause problems if the
3000 workarounds for compiler, library and operating system bugs affect the
3001 cleanliness or maintainability of the rest of GCC. In some cases, to
3002 bring GCC up on such a system, if still possible with current GCC, may
3003 require first installing an old version of GCC which did work on that
3004 system, and using it to compile a more recent GCC, to avoid bugs in
3005 the vendor compiler. Old releases of GCC 1 and GCC 2 are available in
3006 the old-releases directory on the
3007 @uref{../mirrors.html,,GCC mirror sites}. Header bugs may generally
3008 be avoided using @command{fixincludes}, but bugs or deficiencies in
3009 libraries and the operating system may still cause problems.
3011 For some systems, old versions of GNU binutils may also be useful,
3012 and are available from pub/binutils/old-releases on
3013 @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}.
3015 Some of the information on specific systems above relates to
3016 such older systems, but much of the information
3017 about GCC on such systems (which may no longer be applicable to
3018 current GCC) is to be found in the GCC texinfo manual.
3024 @heading @anchor{elf_targets}all ELF targets (SVR4, Solaris, etc.)
3026 C++ support is significantly better on ELF targets if you use the
3027 @uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
3028 inlines, vtables and template instantiations will be discarded
3038 @uref{./index.html,,Return to the GCC Installation page}
3042 @c ***************************************************************************
3043 @c Part 6 The End of the Document
3045 @comment node-name, next, previous, up
3046 @node Concept Index, , Specific, Top
3050 @unnumbered Concept Index