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.2 2001/05/16 14:57:06 dje 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{Sample Title}
64 @c The following two commands start the copyright page.
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 `@code{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 any longer.
159 @uref{./index.html,,Return to the GCC Installation page}
163 @c ***Downloading the source**************************************************
165 @comment node-name, next, previous, up
166 @node Downloading the source, Configuration, , Installing GCC
170 <h1 align="center">Downloading GCC</h1>
173 @chapter Downloading GCC
175 @cindex Downloading GCC
176 @cindex Downloading the Source
178 GCC is distributed via CVS and FTP tarballs compressed with gzip or
179 bzip2. It is possible to download a full distribution or specific
182 Please refer to our @uref{http://gcc.gnu.org/releases.html,,releases web page}
183 for information on how to obtain GCC.
185 The full distribution includes the C, C++, Objective-C, Fortran, Java,
186 and Chill compilers. The full distribution also includes runtime libraries
187 for C++, Objective-C and Fortran. In the future the GNU compiler testsuites
188 will be included in the full distribution.
190 If you choose to download specific components, you must download the core
191 gcc distribution plus any language specific distributions you wish to
192 use. The core distribution includes the C language front-end as well as the
193 shared components. Each language has a tarball which includes the language
194 front-end as well as the language runtime (when appropriate).
196 Unpack the core distribution as well as any language specific
197 distributions in the same directory.
199 If you also intend to build binutils (either to upgrade an existing
200 installation or for use in place of the corresponding tools of your
201 OS), unpack the binutils distribution either in the same directory or
202 a separate one. In the latter case, add symbolic links to any
203 components of the binutils you intend to build alongside the compiler
204 (bfd, binutils, gas, gprof, ld, opcodes,...) to the directory containing
212 @uref{./index.html,,Return to the GCC Installation page}
216 @c ***Configuration***********************************************************
218 @comment node-name, next, previous, up
219 @node Configuration, Building, Downloading the source, Installing GCC
223 <h1 align="center">Installing GCC: Configuration</h1>
226 @chapter Installing GCC: Configuration
228 @cindex Configuration
229 @cindex Installing GCC: Configuration
231 Like most GNU software, GCC must be configured before it can be built.
232 This document describes the recommended configuration procedure
233 for both native and cross targets.
235 We use @emph{srcdir} to refer to the toplevel source directory for
236 GCC; we use @emph{objdir} to refer to the toplevel build/object directory.
238 First, we @strong{highly} recommend that GCC be built into a
239 separate directory than the sources which does @strong{not} reside
240 within the source tree. This is how we generally build GCC; building
241 where @emph{srcdir} == @emph{objdir} should still work, but doesn't
242 get extensive testing; building where @emph{objdir} is a subdirectory
243 of @emph{srcdir} is unsupported.
245 Second, when configuring a native system, either ``@command{cc}'' or
246 ``@command{gcc}'' must be in your path or you must set @command{CC} in
247 your environment before running configure. Otherwise the configuration
253 % mkdir @emph{objdir}
255 % @emph{srcdir}/configure @strong{[target] [options]}
259 @strong{target specification}
262 GCC has code to correctly determine the correct value for @strong{target}
263 for nearly all native systems. Therefore, we highly recommend you not
264 provide a configure target when configuring a native compiler.
267 @strong{target} must be specified as @option{--target=}@emph{target}
268 when configuring a cross compiler; examples of valid targets would be
269 i960-rtems, m68k-coff, sh-elf, etc.
272 Specifying just @strong{target} instead of @option{--target=}@emph{target}
273 implies that the host defaults to @strong{target}.
277 @strong{options specification}
279 Use @strong{options} to override several configure time options for
280 GCC. A partial list of supported @option{options}:
284 @option{--prefix=}@emph{dirname} @minus{}@minus{} Specify the toplevel installation
285 directory. This is the recommended way to install the tools into a directory
286 other than the default. The toplevel installation directory defaults to
289 We @strong{highly} recommend against @emph{dirname} being the same or a
290 subdirectory of @emph{objdir} or vice versa.
292 These additional options control where certain parts of the distribution
293 are installed. Normally you should not need to use these options.
296 @option{--with-local-prefix=}@emph{dirname} @minus{}@minus{} Specify the installation
297 directory for local include files. The default is @code{/usr/local}.
300 @option{--with-gxx-include-dir=}@emph{dirname} @minus{}@minus{} Specify the installation
301 directory for g++ header files. The default is @command{/usr/local/include/g++}.
306 @option{--enable-shared} @minus{}@minus{} Build shared versions of the C++ runtime
307 libraries if supported. This is the default on most systems. Use @option{--disable-shared}
308 for static libraries. Note that up to the gcc version 2.95.x series, static
309 libraries were the default on all systems.
312 @option{--with-gnu-as} @minus{}@minus{} Specify that the compiler should assume that the
313 assembler it finds is the GNU assembler. However, this does not modify the rules to find an
314 assembler and will result in confusion if found assembler is not actually the GNU assembler.
315 If you have more than one assembler installed on your system, you may want to use this option
316 in connection with @option{--with-as=/path/to/gas}.
319 @option{--with-as=@emph{/path/to/as}} @minus{}@minus{} Specify that the compiler should use the
320 assembler pointed to by @emph{pathname}, rather than the one found by the standard rules to
321 find an assembler, which are:
324 Check the @emph{$exec_prefix/lib/gcc-lib/$target/$version} directory, where @emph{$exec_prefix}
325 defaults to @emph{$prefix} which defaults to @file{/usr/local} unless overridden by the
326 @option{--prefix=/pathname} switch described above. @emph{$target} is the target system triple,
327 such as @emph{sparc-sun-solaris2.7}, and @emph{$version} denotes the GCC version, such as 2.95.2.
329 Check operating system specific directories (e.g. @file{/usr/ccs/bin} on Sun Solaris).
331 Note that these rules do not check for the value of @emph{$PATH}. You may want to use
332 @option{--with-as} if no assembler is installed in the directories listed above, or if you have
333 multiple assemblers installed and want to choose one that is not found by the above rules.
336 @option{--with-gnu-ld} @minus{}@minus{} Same as @option{--with-gnu-as} but for linker.
339 @option{--with-ld=@emph{/path/to/ld}} @minus{}@minus{} Same as @option{--with-as}, but for the
343 @option{--with-stabs} @minus{}@minus{} Specify that stabs debugging information should be used
344 instead of whatever format the host normally uses. Normally GCC uses the
345 same debug format as the host system.
348 @option{--enable-multilib} @minus{}@minus{} Specify that multiple target libraries
349 should be built to support different target variants, calling conventions,
350 etc. This is the default.
353 @option{--enable-threads} @minus{}@minus{} Specify that the target supports threads.
354 This affects the Objective-C compiler and runtime library, and exception
355 handling for other languages like C++ and Java.
358 @option{--enable-threads=}@emph{lib} @minus{}@minus{} Specify that @emph{lib} is the thread
359 support library. This affects the Objective-C compiler and runtime library,
360 and exception handling for other languages like C++ and Java.
363 @option{--with-cpu=}@emph{cpu} @minus{}@minus{} Specify which cpu variant the
364 compiler should generate code for by default. This is currently
365 only supported on the some ports, specifically arm, powerpc, and
366 SPARC. If configure does not recognize the model name (e.g. arm700,
367 603e, or ultrasparc) you provide, please check the configure script
368 for a complete list of supported models.
371 @option{--enable-target-optspace} @minus{}@minus{} Specify that target libraries
372 should be optimized for code space instead of code speed. This is the
373 default for the m32r platform.
376 @option{--enable-cpp} @minus{}@minus{} Specify that a shell script which emulates
377 traditional cpp functionality should be installed.
380 @option{--enable-cpplib} @minus{}@minus{} Specify that the functionality of
381 CPP should be integrated into the compiler itself. This option is
382 not supported by snapshots since November 2000. In snapshots where
383 it is supported, it is not enabled by default, except for snapshots
384 very close to November 2000.
387 @option{--without-fast-fixincludes} @minus{}@minus{} Specify that the old, slower
388 method of fixing the system header files should be used.
389 EGCS 1.1.x and older releases default to the slow version. GCC 2.95 and
390 newer releases will default to the fast version.
393 @option{--enable-version-specific-runtime-libs} @minus{}@minus{} Specify that runtime
394 libraries should be installed in the compiler specific subdirectory
395 (@option{$@{libsubdir@}}) rather than the usual places.
396 In addition, libstdc++'s include files will be installed in
397 @option{$@{libsubdir@}/include/g++} unless you overruled it by using
398 @option{--with-gxx-include-dir=}@emph{dirname}.
399 Using this option is particularly useful if you intend to use several
400 versions of GCC in parallel. This is currently supported by @option{libf2c}
401 and @option{libstdc++}.
404 @option{--enable-languages=}@emph{lang1}@option{,}@emph{lang2}@option{,...}
405 @minus{}@minus{} Specify that only a particular subset of compilers and their runtime libraries
406 should be built. For a list of valid values for @emph{lang}@option{x} you can issue
407 the following command in the @option{gcc} directory of your GCC source tree:@*
408 @command{grep language= */config-lang.in}@*
409 Currently, you can use any of the following: @code{c++}, @code{f77}, @code{java} and @code{objc}.
410 @code{CHILL} is not currently maintained, and will almost
411 certainly fail to compile. Note that this switch does not work with
412 EGCS 1.1.2 or older versions of egcs. It is supported in GCC 2.95
413 and newer versions.@*
414 If you do not pass this flag, all languages available in the @code{gcc} sub-tree
415 will be configured. Re-defining LANGUAGES when calling @command{make bootstrap}
416 @strong{*does not*} work anymore, as those language sub-directories might not have been
420 @option{--disable-libgcj} @minus{}@minus{} Specify that the run-time libraries
421 used by GCJ should not be built. This is useful in case you intend
422 to use GCJ with some other run-time, or you're going to install it
423 separately, or it just happens not to build on your particular
424 machine. In general, if the Java front-end is enabled, the GCJ
425 libraries will be enabled too, unless they're known to not work on
426 the target platform. If GCJ is enabled but libgcj isn't built, you
427 may need to port it; in this case, before modifying the top-level
428 configure.in so that libgcj is enabled by default on this platform,
429 you may use @option{--enable-libgcj} to override the default.
432 @option{--with-dwarf2} @minus{}@minus{} Specify that the compiler should use DWARF2
433 debugging information as the default.
436 Some options which only apply to building cross compilers:
439 @option{--with-headers=}@emph{dir} @minus{}@minus{} Specifies a directory which has
440 target include files.
441 @emph{This options is required} when building a cross
442 compiler, if @code{$@{prefix@}/$@{target@}/sys-include} doesn't pre-exist.
443 These include files will be copied into the @code{gcc} install directory.
444 Fixincludes will be run on these files to make them compatible with @command{gcc}.
446 @option{--with-libs=}@emph{``dir1 dir2 ... dirN''} @minus{}@minus{} Specifies a list of
447 directories which contain the target runtime libraries. These libraries will
448 be copied into the @code{gcc} install directory.
450 @option{--with-newlib} @minus{}@minus{} Specifies that ``newlib'' is being used as the target
451 C library. This causes @code{__eprintf} to be omitted from libgcc.a on the
452 assumption that it will be provided by newlib.
455 Note that each @option{--enable} option has a corresponding @option{--disable} option and
456 that each @option{--with} option has a corresponding @option{--without} option.
463 @uref{./index.html,,Return to the GCC Installation page}
467 @c ***Building****************************************************************
469 @comment node-name, next, previous, up
470 @node Building, Testing, Configuration, Installing GCC
474 <h1 align="center">Installing GCC: Building</h1>
479 @cindex Installing GCC: Building
481 Now that GCC is configured, you are ready to build the compiler and
484 We @strong{highly} recommend that GCC be built using GNU make;
485 other versions may work, then again they might not.
487 (For example, many broken versions of make will fail if you use the
488 recommended setup where @emph{objdir} is different from @emph{srcdir}.)
491 @section Building a native compiler
493 For a native build issue the command `@code{make bootstrap}'. This
494 will build the entire GCC system, which includes the following steps:
498 Build host tools necessary to build the compiler such as texinfo, bison,
502 Build target tools for use by the compiler such as binutils (bfd,
503 binutils, gas, gprof, ld, and opcodes)@*
504 if they have been individually linked
505 or moved into the top level GCC source tree before configuring.
508 Perform a 3-stage bootstrap of the compiler.
511 Perform a comparison test of the stage2 and stage3 compilers.
514 Build runtime libraries using the stage3 compiler from the previous step.
518 If you are short on disk space you might consider `@code{make
519 bootstrap-lean}' instead. This is identical to `@code{make
520 bootstrap}' except that object files from the stage1 and
521 stage2 of the 3-stage bootstrap of the compiler are deleted as
522 soon as they are no longer needed.
525 If you want to save additional space during the bootstrap and in
526 the final installation as well, you can build the compiler binaries
527 without debugging information with ``@code{make CFLAGS='-O' LIBCFLAGS='-g
528 -O2' LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap}''. This will save
529 roughly 40% of disk space both for the bootstrap and the final installation.
530 (Libraries will still contain debugging information.)
532 If you used the flag @code{--enable-languages=...} to restrict
533 the compilers to be built, only those you've actually enabled will be
534 built. This will of course only build those runtime libraries, for
535 which the particular compiler has been built. Please note,
536 that re-defining LANGUAGES when calling `@code{make bootstrap}'
537 @strong{*does not*} work anymore!
540 @section Building a cross compiler
542 We recommend reading the
543 @uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ}
544 for information about building cross compilers.
546 When building a cross compiler, it is not generally possible to do a
547 3-stage bootstrap of the compiler. This makes for an interesting problem
548 as parts of GCC can only be built with GCC.
550 To build a cross compiler, we first recommend building and installing a
551 native compiler. You can then use the native GCC compiler to build the
554 Assuming you have already installed a native copy of GCC and configured
555 your cross compiler, issue the command `@code{make}', which performs the
560 Build host tools necessary to build the compiler such as texinfo, bison,
564 Build target tools for use by the compiler such as binutils (bfd,
565 binutils, gas, gprof, ld, and opcodes)
566 if they have been individually linked or moved into the top level GCC source
567 tree before configuring.
570 Build the compiler (single stage only).
573 Build runtime libraries using the compiler from the previous step.
576 Note that if an error occurs in any step the make process will exit.
578 @section Building in parallel
580 If you have a multiprocessor system you can use `@code{make bootstrap
581 MAKE="make -j 2" -j 2}' or just `@code{make -j 2 bootstrap}'
582 for GNU Make 3.79 and above instead of just `@code{make bootstrap}'
583 when building GCC. You can use a bigger number instead of two if
584 you like. In most cases, it won't help to use a number bigger than
585 the number of processors in your machine.
592 @uref{./index.html,,Return to the GCC Installation page}
596 @c ***Testing*****************************************************************
598 @comment node-name, next, previous, up
599 @node Testing, Final install, Building, Installing GCC
603 <h1 align="center">Installing GCC: Testing</h1>
606 @chapter Installing GCC: Testing
609 @cindex Installing GCC: Testing
612 @strong{Please note that this is only applicable
613 to current development versions of GCC and GCC 3.0 or later.
614 GCC 2.95.x does not come with a testsuite.}
616 Before you install GCC, you might wish to run the testsuite. This
617 step is optional and may require you to download additional software.
619 First, you must have @uref{download.html,,downloaded the testsuites}.
620 The full distribution contains testsuites; only if you downloaded the
621 ``core'' compiler plus any front ends, you do not have the testsuites.
623 Second, you must have a @uref{http://www.gnu.org/software/dejagnu/,,current version of DejaGnu} installed;
624 dejagnu 1.3 is not sufficient.
626 Now you may need specific preparations:
630 In order to run the libio tests on targets which do not fully
631 support Unix/POSIX commands (e.g. Cygwin), the references to the dbz
632 directory have to be deleted from @code{libio/configure.in}.
635 The following environment variables must be set appropriately, as in
636 the following example (which assumes that DejaGnu has been installed
637 under @code{/usr/local}):
640 TCL_LIBRARY = /usr/local/share/tcl8.0
641 DEJAGNULIBS = /usr/local/share/dejagnu
644 On systems such as Cygwin, these paths are required to be actual
645 paths, not mounts or links; presumably this is due to some lack of
646 portability in the DejaGnu code.
650 Finally, you can run the testsuite (which may take a long time):
652 cd @emph{objdir}; make -k check
655 The testing process will try to test as many components in the GCC
656 distribution as possible, including the C, C++ and Fortran compilers as
657 well as the C++ runtime libraries.
659 @section How can I run the test suite on selected tests?
661 As a first possibility to cut down the number of tests that are run it is
662 possible to use `@code{make check-gcc}' or `@code{make check-g++}'
663 in the gcc subdirectory of the object directory. To further cut down the
664 tests the following is possible:
667 make check-gcc RUNTESTFLAGS="execute.exp <other options>"
670 This will run all gcc execute tests in the testsuite.
673 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* <other options>"
676 This will run the g++ "old-deja" tests in the testsuite where the filename
679 The *.exp files are located in the testsuite directories of the GCC
680 source, the most important ones being compile.exp, execute.exp, dg.exp
681 and old-deja.exp. To get a list of the possible *.exp files, pipe the
682 output of `@code{make check}' into a file and look at the
683 "@code{Running ... .exp}" lines.
685 @section How to interpret test results
687 After the testsuite has run you'll find various *.sum and *.log
688 files in the testsuite subdirectories. The *.log files contain a
689 detailed log of the compiler invocations and the corresponding
690 results, the *.sum files summarize the results. These summaries list
691 all the tests that have been run with a corresponding status code:
695 PASS: the test passed as expected
697 XPASS: the test unexpectedly passed
699 FAIL: the test unexpectedly failed
701 XFAIL: the test failed as expected
703 UNSUPPORTED: the test is not supported on this platform
705 ERROR: the testsuite detected an error
707 WARNING: the testsuite detected a possible problem
710 It is normal for some tests to report unexpected failures. At the current time
711 our testing harness does not allow fine grained control over whether or not a
712 test is expected to fail. We expect to fix this problem in future releases.
715 @section Submitting test results
717 If you want to report the results to the GCC project, use the
718 @code{contrib/test_summary} shell script. Start it in the @emph{objdir} with
721 @emph{srcdir}/contrib/test_summary -p your_commentary.txt -m gcc-testresults@@gcc.gnu.org |sh
724 This script uses the @code{Mail} program to send the results, so
725 make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
726 prepended to the testsuite summary and should contain any special
727 remarks you have on your results or your build environment. Please
728 do not edit the testsuite result block or the subject line, as these
729 messages are automatically parsed and presented at the
730 @uref{http://gcc.gnu.org/testresults/,,GCC testresults} web
731 page. Here you can also gather information on how specific tests
732 behave on different platforms and compare them with your results. A
733 few failing testcases are possible even on released versions and you
734 should look here first if you think your results are unreasonable.
738 @c ***Final install***********************************************************
740 @comment node-name, next, previous, up
741 @node Final install, , Testing, Installing GCC
743 @ifset finalinstallhtml
745 <h1 align="center">Installing GCC: Final installation</h1>
748 @chapter Installing GCC: Final installation
751 Now that GCC has been built and tested, you can install it with
752 `@command{cd @emph{objdir}; make install}' for a native compiler or
753 `@command{cd @emph{objdir}; make install LANGUAGES="c c++"}' for
754 a cross compiler (note installing cross compilers will be easier in the
757 That step completes the installation of GCC; user level binaries can
758 be found in @code{@emph{prefix}/bin} where @code{@emph{prefix}} is the value you specified
759 with the @option{--prefix} to configure (or @file{/usr/local} by default).
761 If you don't mind, please quickly review the
762 @uref{http://gcc.gnu.org/gcc-2.95/buildstat.html,,build status page}.
763 If your system is not listed, send a note to
764 @uref{mailto:gcc@@gcc.gnu.org,,gcc@@gcc.gnu.org} indicating
765 that you successfully built and installed GCC.
767 Include the output from running @code{@emph{srcdir}/config.guess}. (Do not
768 send us the config.guess file itself, just the output from running
771 If you find a bug, please report it following our
772 @uref{../bugs.html,,bug reporting guidelines}.
779 @uref{./index.html,,Return to the GCC Installation page}
783 @c ***Binaries****************************************************************
785 @comment node-name, next, previous, up
786 @node Binaries, Specific, Installing GCC, Top
790 <h1 align="center">Installing GCC: Binaries</h1>
793 @chapter Installing GCC: Binaries
796 @cindex Installing GCC: Binaries
798 We are often asked about pre-compiled versions of GCC. While we cannot
799 provide these for all platforms, below you'll find links to binaries for
800 various platforms where creating them by yourself is not easy due to various
803 Please note that we did not create these binaries, nor do we
804 support them. If you have any problems installing them, please
805 contact their makers.
812 @uref{http://www-frec.bull.com/docs/download.htm,,Bull's Freeware and Shareware Archive for AIX};
815 @uref{http://aixpdlib.seas.ucla.edu,,UCLA Software Library for AIX};
819 DOS - @uref{http://www.delorie.com/djgpp/,,DJGPP};
822 @uref{http://hpux.cae.wisc.edu/,,HP-UX Porting Center};
825 @uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO OpenServer/Unixware};
828 Solaris (SPARC, Intel) - @uref{http://www.sunfreeware.com/,,Sunfreeware};
831 SGI - @uref{http://freeware.sgi.com/,,SGI Freeware};
834 Windows 95, 98, and NT:
837 The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project;
839 @uref{http://www.xraylith.wisc.edu/~khan/software/gnu-win32/,,GNU Win32}
840 related projects by Mumit Khan.
844 @uref{ftp://ftp.thewrittenword.com/packages/free/by-name/gcc-2.95.2/,,The
845 Written Word} offers binaries for Solaris 2.5.1, 2.6, 2.7/SPARC, 2.7/Intel,
846 IRIX 6.2, 6.5, Digital UNIX 4.0D, HP-UX 10.20, and HP-UX 11.00.
850 @uref{http://h8300-hms.sourceforge.net/,,GNU Development Tools for the
851 Hitachi H8/300[HS] Series}
855 In addition to those specific offerings, you can get a binary
856 distribution CD-ROM from the
857 @uref{http://www.fsf.org/order/order.html,,Free Software Foundation}.
858 It contains binaries for a number of platforms, and
859 includes not only GCC, but other stuff as well. The current CD does
860 not contain the latest version of GCC, but it should allow
861 bootstrapping the compiler. An updated version of that disk is in the
869 @uref{./index.html,,Return to the GCC Installation page}
873 @c ***Specific****************************************************************
875 @comment node-name, next, previous, up
876 @node Specific, Concept Index, Binaries, Top
880 <h1 align="center">Host/target specific installation notes for GCC</h1>
883 @chapter Host/target specific installation notes for GCC
886 @cindex Specific installation notes
887 @cindex Target specific installation
888 @cindex Host specific installation
889 @cindex Target specific installation notes
891 Please read this document carefully @emph{before} installing the
892 GNU Compiler Collection on your machine.
896 @uref{#alpha*-dec-linux*,,alpha*-dec-linux*}
898 @uref{#alpha*-dec-osf*,,alpha*-dec-osf*}
904 @uref{#h8300-hms,,h8300-hms}
906 @uref{#hppa*-hp-hpux*,,hppa*-hp-hpux*}
908 @uref{#hppa*-hp-hpux9,,hppa*-hp-hpux9}
910 @uref{#hppa*-hp-hpux10,,hppa*-hp-hpux10}
912 @uref{#hppa*-hp-hpux11,,hppa*-hp-hpux11}
914 @uref{#*-*-linux-gnu,,*-*-linux-gnu}
916 @uref{#ix86-*-linux*,,i?86-*-linux*}
918 @uref{#ix86-*-sco3.2v5*,,i?86-*-sco3.2v5*}
920 @uref{#ix86-*-solaris*,,i?86-*-solaris*}
922 @uref{#ix86-*-udk,,i?86-*-udk}
924 @uref{#*-ibm-aix*,,*-ibm-aix*}
926 @uref{#m68k-*-nextstep*,,m68k-*-nextstep*}
928 @uref{#m68k-sun-sunos4.1.1,,m68k-sun-sunos4.1.1}
930 @uref{#mips*-sgi-irix[45],,mips*-sgi-irix[45]}
932 @uref{#mips*-sgi-irix6,,mips*-sgi-irix6}
934 @uref{#powerpc-*-linux-gnu*,,powerpc-*-linux-gnu*}
936 @uref{#*-*-solaris*,,*-*-solaris*}
938 @uref{#sparc-sun-solaris*,,sparc-sun-solaris*}
940 @uref{#sparc-sun-solaris2.7,,sparc-sun-solaris2.7}
942 @uref{#*-sun-solaris2.8,,*-sun-solaris2.8}
944 @uref{#sunv5,,Sun V5.0 Compiler Bugs}
946 @uref{#sparc-sun-sunos*,,sparc-sun-sunos*}
948 @uref{#sparc-unknown-linux-gnulibc1,,sparc-unknown-linux-gnulibc1}
950 @uref{#sparc64-*-*,,sparc64-*-*}
952 @uref{#windows,,Microsoft Windows}
956 @uref{#older,,Older systems}
961 @uref{#elf_targets,,all ELF targets} (SVR4, Solaris, etc.)
966 <!-- -------- host/target specific issues start here ---------------- -->
968 <h3><a name="alpha*-dec-linux*">alpha*-dec-linux*</a></h3>
971 We strongly recommend to upgrade to binutils 2.10 (or newer).
975 Error: macro requires $at register while noat in effect
978 indicates that you should upgrade to a newer version of
979 the assembler, 2.9 or later. If you can not upgrade the assembler, the
980 compiler option "-Wa,-m21164a" may work around this problem.
985 <h3><a name="alpha*-dec-osf*">alpha*-dec-osf*</a></h3>
988 If you install a shared libstdc++ and, when you link a non-trivial C++
989 program (for example, @code{gcc/testsuite/g++.other/delete3.C}),
990 the linker reports a couple of errors about multiply-defined symbols
991 (for example, @code{nothrow}, @code{__throw} and
992 @code{terminate(void)}), you've probably got a linker bug, for
993 which there's no known fix. The officially recommended work-around is
994 to remove the shared libstdc++.
996 An alternative solution is to arrange that all symbols from
997 @code{libgcc} get copied to the shared @code{libstdc++};
998 see detailed solution below. (Surprising as it may seem, this does
999 indeed fix the problem!) @emph{Beware} that this may bring you
1000 binary-compatibility problems in the future, if you don't use the same
1001 work-around next time you build @code{libstdc++}: if programs
1002 start to depend on @code{libstdc++} to provide symbols that used
1003 to be only in @code{libgcc}, you must arrange that
1004 @code{libstdc++} keeps providing them, otherwise the programs
1005 will have to be relinked.
1007 The magic spell is to add @code{-Wl,-all,-lgcc,-none} to the
1008 definition of macro @code{SHDEPS} in
1009 @code{libstdc++/config/dec-osf.ml} @emph{before}
1010 @code{alpha*-dec-osf*/libstdc++/Makefile} is created (a
1011 @uref{dec-osf-shlibstdc++.patch,,patch}
1012 that does just that is available). If the Makefile already exists, run
1013 @code{./config.status} within directory
1014 @code{alpha*-dec-osf*/libstdc++} (and
1015 @code{alpha*-dec-osf*/ieee/libstdc++}, if it also exists).
1016 Remove any existing @code{libstdc++.so*} from such directories,
1017 and run @code{make all-target-libstdc++} in the top-level
1018 directory, then @code{make install-target-libstdc++}.
1020 If you have already removed the build tree, you may just remove
1021 @code{libstdc++.so.2.10.0} from the install tree and re-create
1023 @code{gcc -shared -o libstdc++.so.2.10.0 -Wl,-all,-lstdc++,-lgcc,-none -lm}.
1025 sub-directory exists, repeat this command in it, with the additional
1031 <h3><a name="avr">avr</a></h3>
1034 Use `@command{configure} @option{--target=avr}
1035 @option{--enable-languages="c"}' to configure GCC.
1037 Further installation notes and other useful information about AVR tools
1038 can also be obtained from:
1042 @uref{http://home.overta.ru/users/denisc,,http://home.overta.ru/users/denisc}
1044 @uref{http://www.itnet.pl/amelektr/avr,,http://www.itnet.pl/amelektr/avr}
1047 We strongly recommend to upgrade to binutils 2.11
1048 (or a current snapshot until 2.11 has been released).
1050 The following error:
1052 Error: register required
1055 indicates that you should upgrade to a newer version of the binutils.
1060 <h3><a name="dos">DOS</a></h3>
1063 Please have a look at our @uref{binaries.html,,binaries page}.
1068 <h3><a name="h8300-hms">h8300-hms</a></h3>
1071 Please have a look at our @uref{binaries.html,,binaries page}.
1076 <h3><a name="hppa*-hp-hpux*">hppa*-hp-hpux*</a></h3>
1079 We @emph{highly} recommend using gas/binutils-2.8 or newer on all hppa
1080 platforms; you may encounter a variety of problems when using the HP
1083 Specifically, @option{-g} does not work on HP-UX (since that system
1084 uses a peculiar debugging format which GCC does not know about), unless you
1085 use GAS and GDB and configure GCC with the @option{--with-gnu-as}
1088 If you wish to use pa-risc 2.0 architecture support, you must use either
1089 the HP assembler or a recent
1090 @uref{ftp://sources.redhat.com/pub/binutils/snapshots,,snapshot of gas}.
1092 More specific information to hppa*-hp-hpux* targets follows.
1097 <h3><a name="hppa*-hp-hpux9">hppa*-hp-hpux9</a></h3>
1100 The HP assembler has major problems on this platform. We've tried to work
1101 around the worst of the problems. However, those workarounds may be causing
1102 linker crashes in some circumstances; the workarounds also probably prevent
1103 shared libraries from working. Use the GNU assembler to avoid these problems.
1106 The configuration scripts for GCC will also trigger a bug in the hpux9
1107 shell. To avoid this problem set CONFIG_SHELL to @file{/bin/ksh} and SHELL
1108 to @file{/bin/ksh} in your environment.
1114 <h3><a name="hppa*-hp-hpux10">hppa*-hp-hpux10</a></h3>
1117 For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
1118 @code{PHCO_19798} from HP. HP has two sites which provide patches free of
1124 <a href="http://us-support.external.hp.com">US, Canada, Asia-Pacific, and
1128 @uref{http://us-support.external.hp.com,,}US, Canada, Asia-Pacific, and
1132 @uref{http://europe-support.external.hp.com,,Europe}
1135 The HP assembler on these systems is much better than the hpux9 assembler,
1136 but still has some problems. Most notably the assembler inserts timestamps
1137 into each object file it creates, causing the 3-stage comparison test to fail
1138 during a `@code{make bootstrap}'. You should be able to continue by
1139 saying `@code{make all}' after getting the failure from `@code{make
1146 <h3><a name="hppa*-hp-hpux11">hppa*-hp-hpux11</a></h3>
1149 GCC 2.95.2 does not support HP-UX 11, and it cannot generate 64-bit
1150 object files. Current (as of late 2000) snapshots and GCC 3.0 do support
1157 <h3><a name="*-*-linux-gnu">*-*-linux-gnu</a></h3>
1160 If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install
1161 out-of-the-box. You'll get compile errors while building libstdc++.
1162 The patch @uref{glibc-2.2.patch,,glibc-2.2.patch}, that is to be
1163 applied in the GCC source tree, fixes the compatibility problems.
1168 <h3><a name="ix86-*-linux*">i?86-*-linux*</a></h3>
1171 You will need binutils-2.9.1.0.15 or newer for exception handling to work.
1173 If you receive Signal 11 errors when building on GNU/Linux, then it is
1174 possible you have a hardware problem. Further information on this can be
1175 found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
1180 <h3><a name="ix86-*-sco3.2v5*">i?86-*-sco3.2v5*</a></h3>
1183 Unlike earlier versions of GCC, the ability to generate COFF with this
1184 target is no longer provided.
1186 Earlier versions of GCC emitted Dwarf-1 when generating ELF to allow
1187 the system debugger to be used. That support was too burdensome to
1188 maintain. GCC now emits only dwarf-2 for this target. This means you
1189 may use either the UDK debugger or GDB to debug programs built by this
1192 If you are building languages other than C, you must follow the instructions
1193 about invoking `@code{make bootstrap}' because the native OpenServer
1194 compiler will build a @code{cc1plus} that will not correctly parse many
1195 valid C++ programs including those in @code{libgcc.a}.
1196 @strong{You must do a `@code{make bootstrap}' if you are building with the
1199 Use of the `@option{-march-pentiumpro}' flag can result in
1200 unrecognized opcodes when using the native assembler on OS versions before
1201 5.0.6. (Support for P6 opcodes was added to the native ELF assembler in
1202 that version.) While it's rather rare to see these emitted by GCC yet,
1203 errors of the basic form:
1206 /usr/tmp/ccaNlqBc.s:22:unknown instruction: fcomip
1207 /usr/tmp/ccaNlqBc.s:50:unknown instruction: fucomip
1210 are symptoms of this problem. You may work around this by not
1211 building affected files with that flag, by using the GNU assembler, or
1212 by using the assembler provided with the current version of the OS.
1213 Users of GNU assembler should see the note below for hazards on doing
1216 The native SCO assembler that is provided with the OS at no
1217 charge is normally required. If, however, you must be able to use
1218 the GNU assembler (perhaps you're compiling code with asms that
1219 require GAS syntax) you may configure this package using the flags
1220 @option{--with-gnu-as}. You must use a recent version of GNU
1221 binutils; versions past 2.9.1 seem to work well.
1223 In general, the @option{--with-gnu-as} option isn't as well tested
1224 as the native assembler.
1226 Look in @file{gcc/config/i386/sco5.h} (search for "messy") for
1227 additional OpenServer-specific flags.
1229 Systems based on OpenServer before 5.0.4 (`@code{uname -X}'
1230 will tell you what you're running) require TLS597 from ftp.sco.com/TLS
1231 for C++ constructors and destructors to work right.
1233 The system linker in (at least) 5.0.4 and 5.0.5 will sometimes
1234 do the wrong thing for a construct that GCC will emit for PIC
1235 code. This can be seen as execution testsuite failures when using
1236 -fPIC on 921215-1.c, 931002-1.c, nestfunc-1.c, and gcov-1.c.
1237 For 5.0.5, an updated linker that will cure this problem is
1238 available. You must install both
1239 @uref{ftp://ftp.sco.com/Supplements/rs505a/,,ftp://ftp.sco.com/Supplements/rs505a/}
1240 and @uref{ftp://ftp.sco.com/SLS/,,OSS499A}.
1242 The dynamic linker in OpenServer 5.0.5 (earlier versions may show
1243 the same problem) aborts on certain g77-compiled programs. It's particularly
1244 likely to be triggered by building Fortran code with the @option{-fPIC} flag.
1245 Although it's conceivable that the error could be triggered by other
1246 code, only G77-compiled code has been observed to cause this abort.
1247 If you are getting core dumps immediately upon execution of your
1248 g77 program - and especially if it's compiled with -fPIC - try applying
1249 @uref{sco_osr5_g77.patch,,@code{`sco_osr5_g77.patch'}} to your libf2c and
1251 Affected faults, when analyzed in a debugger, will show a stack
1252 backtrace with a fault occurring in @code{rtld()} and the program
1253 running as @code{/usr/lib/ld.so.1}. This problem has been reported to SCO
1254 engineering and will hopefully be addressed in later releases.
1260 <h3><a name="ix86-*-solaris*">i?86-*-solaris*</a></h3>
1263 GCC 2.95.2, when configured to use the GNU assembler, would invoke
1264 it with the @code{-s} switch, that GNU as up to 2.9.5.0.12 does
1265 not support. If you'd rather not use a newer GNU as nor the native
1266 assembler, you'll need the patch
1267 @uref{x86-sol2-gas.patch,,@code{`x86-sol2-gas.patch'}}.
1273 <h3><a name="ix86-*-udk">i?86-*-udk</a></h3>
1276 This target emulates the SCO Universal Development Kit and requires that
1277 package be installed. (If it is installed, you will have a
1278 @file{/udk/usr/ccs/bin/cc } file present.) It's very much like the
1279 @code{i?86-*-unixware7*} target
1280 but is meant to be used when hosting on a system where UDK isn't the
1281 default compiler such as OpenServer 5 or Unixware 2. This target will
1282 generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
1283 with the same warnings and caveats as the SCO UDK.
1285 You can stage1 with either your native compiler or with UDK. If you
1286 don't do a full bootstrap when initially building with your native compiler
1287 you will have an utterly unusable pile of bits as your reward.
1289 This target is a little tricky to build because we have to distinguish
1290 it from the native tools (so it gets headers, startups, and libraries
1291 from the right place) while making the tools not think we're actually
1292 building a cross compiler. The easiest way to do this is with a configure
1295 @command{ CC=/udk/usr/ccs/bin/cc <i>/your/path/to/</i>gcc/configure
1296 --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-}
1298 @emph{You should substitute 'i686' in the above command with the appropriate
1299 processor for your host.}
1301 You should follow this with a `@command{make bootstrap}' then
1302 `@command{make install}'. You can then access the UDK-targeted GCC
1303 tools by adding @code{udk-} before the commonly known name. For example, to
1304 invoke the C compiler, you would use `@code{udk-gcc}'. They will coexist
1305 peacefully with any native-target GCC tools you may have installed.
1311 <h3><a name="*-ibm-aix*">*-ibm-aix*</a></h3>
1312 <!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
1315 AIX Make frequently has problems with GCC makefiles. GNU Make 3.76 or
1316 newer is recommended to build on this platform.
1318 Errors involving "alloca" when building GCC generally are due
1319 to an incorrect definition of @command{CC} in the Makefile or mixing files
1320 compiled with the native C compiler and GCC. During the stage1 phase of
1321 the build, the native AIX compiler @strong{must} be invoked as "cc"
1322 (not "xlc"). Once @command{configure} has been informed of
1323 "xlc", one needs to use "make distclean" to remove the
1324 configure cache files and ensure that @command{CC} environment variable
1325 does not provide a definition that will confuse @command{configure}.
1326 If this error occurs during stage2 or later, then the problem most likely
1327 is the version of Make (see above).
1329 Binutils 2.10 does not support AIX 4.3. Binutils available from the
1330 @uref{http://www-1.ibm.com/servers/aix/products/aixos/linux/,,AIX Toolbox for Linux: GNU and Open Source tools for AIX};
1331 website does work. Binutils 2.11 is expected to include AIX 4.3
1332 support. The GNU Assembler is necessary for libstdc++ to build. The
1333 AIX native ld still is recommended. The native AIX tools do
1334 interoperate with GCC.
1336 Linking executables and shared libraries may produce warnings of
1337 duplicate symbols. The assembly files generated by GCC for AIX always
1338 have included multiple symbol definitions for certain global variable
1339 and function declarations in the original program. The warnings should
1340 not prevent the linker from producing a correct library or runnable
1343 AIX 4.3 utilizes a "large format" archive to support both 32-bit and
1344 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
1345 to parse archive libraries did not handle the new format correctly.
1346 These routines are used by GCC and result in error messages during
1347 linking such as "not a COFF file". The version of the routines shipped
1348 with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
1349 option of the archive command may be used to create archives of 32-bit
1350 objects using the original "small format". A correct version of the
1351 routines is shipped with AIX 4.3.2.
1353 Some versions of the AIX binder (linker) can fail with a relocation
1354 overflow severe error when the @option{-bbigtoc} option is used to link
1355 GCC-produced object files into an executable that overflows the TOC. A fix
1356 for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
1357 available from IBM Customer Support and from its
1358 @uref{http://service.boulder.ibm.com/,,service.boulder.ibm.com}
1359 website as PTF U455193.
1361 The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
1362 with a segmentation fault when invoked by any version of GCC. A fix for
1363 APAR IX87327 is available from IBM Customer Support and from its
1364 @uref{http://service.boulder.ibm.com/,,service.boulder.ibm.com}
1365 website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
1367 The initial assembler shipped with AIX 4.3.0 generates incorrect object
1368 files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
1369 TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
1370 @uref{http://service.boulder.ibm.com/,,service.boulder.ibm.com}
1371 website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
1373 AIX provides National Language Support (NLS). Compilers and assemblers
1374 use NLS to support locale-specific representations of various data
1375 formats including floating-point numbers (e.g., "." vs "," for
1376 separating decimal fractions). There have been problems reported where
1377 GCC does not produce the same floating-point formats that the assembler
1378 expects. If one encouters this problem, set the @command{LANG}
1379 environment variable to "C" or "En_US".
1385 <h3><a name="m68k-*-nextstep*">m68k-*-nextstep*</a></h3>
1388 You absolutely @strong{must} use GNU sed and GNU make on this platform.
1391 On NEXTSTEP 3.x where x < 3 the build of GCC will abort during
1392 stage1 with an error message like this:
1396 /usr/tmp/ccbbsZ0U.s:987:Unknown pseudo-op: .section
1397 /usr/tmp/ccbbsZ0U.s:987:Rest of line ignored. 1st junk character
1401 The reason for this is the fact that NeXT's assembler for these
1402 versions of the operating system does not support the .section
1403 pseudo op that's needed for full C++ exception functionality.
1405 As NeXT's assembler is a derived work from GNU as, a free
1406 replacement that does can be obtained at
1407 @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}.
1409 If you try to build the integrated C++ & C++ runtime libraries on this system
1410 you will run into trouble with include files. The way to get around this is
1411 to use the following sequence. Note you must have write permission to
1412 the directory @emph{prefix} you specified in the configuration process of GCC
1413 for this sequence to work.
1417 make all-texinfo all-bison all-byacc all-binutils all-gas all-ld
1420 make install-headers-tar
1429 <h3><a name="m68k-sun-sunos4.1.1">m68k-sun-sunos4.1.1</a></h3>
1432 It is reported that you may need the GNU assembler on this platform.
1438 <h3><a name="mips*-sgi-irix[45]">mips*-sgi-irix[45]</a></h3>
1441 You must use GAS on these platforms, as the native assembler can not handle
1442 the code for exception handling support. Either of these messages indicates
1443 that you are using the MIPS assembler when instead you should be using GAS:
1445 @samp{ as0: Error: ./libgcc2.c, line 1:Badly delimited numeric literal
1446 .4byte $LECIE1-$LSCIE1
1447 as0: Error: ./libgcc2.c, line 1:malformed statement}
1451 @samp{ as0: Error: /src/bld-gcc/gcc/libgcc2.c, line 1:undefined symbol in expression
1452 .word $LECIE1-$LSCIE1}
1454 These systems don't have ranlib, which various components in GCC need; you
1455 should be able to avoid this problem by installing GNU binutils, which includes
1456 a functional ranlib for this system.
1458 You may get the following warning on irix4 platforms, it can be safely
1461 warning: foo.o does not have gp tables for all its sections.
1464 When building GCC, the build process loops rebuilding cc1 over and
1465 over again. This happens on mips-sgi-irix5.2, and possibly other platforms.@*
1466 It has been reported that this is a known bug in the make shipped with
1467 IRIX 5.2. We recommend you use GNU make instead of the vendor supplied
1468 make program; however, you may have success with "smake" on IRIX 5.2 if
1469 you do not have GNU make available.
1471 See @uref{http://reality.sgi.com/ariel/freeware/,,http://reality.sgi.com/ariel/freeware} for more information about
1472 using GCC on IRIX platforms.
1478 <h3><a name="mips*-sgi-irix6">mips*-sgi-irix6</a></h3>
1481 You must @emph{not} use GAS on irix6 platforms; doing so will only
1484 These systems don't have ranlib, which various components in GCC need; you
1485 should be able to avoid this problem by making a dummy script called ranlib
1486 which just exits with zero status and placing it in your path.
1488 If you are using Irix cc as your bootstrap compiler, you must
1489 ensure that the N32 ABI is in use. To test this, compile a simple C
1490 file with @command{cc} and then run @command{file} on the
1491 resulting object file. The output should look like:
1494 @code{ test.o: ELF N32 MSB ...}
1499 @code{ test.o: ELF 32-bit MSB}
1502 then your version of @command{cc} uses the O32 ABI default. You
1503 should set the environment variable @command{CC} to 'cc -n32'
1504 before configuring GCC.
1506 GCC does not currently support generating O32 ABI binaries in the
1507 mips-sgi-irix6 configurations. It used to be possible to create a GCC
1508 with O32 ABI only support by configuring it for the mips-sgi-irix5
1509 target. See the link below for details.
1511 GCC does not correctly pass/return structures which are
1512 smaller than 16 bytes and which are not 8 bytes. The problem is very
1513 involved and difficult to fix. It affects a number of other targets also,
1514 but IRIX 6 is affected the most, because it is a 64 bit target, and 4 byte
1515 structures are common. The exact problem is that structures are being padded
1516 at the wrong end, e.g. a 4 byte structure is loaded into the lower 4 bytes
1517 of the register when it should be loaded into the upper 4 bytes of the
1520 GCC is consistent with itself, but not consistent with the SGI C compiler
1521 (and the SGI supplied runtime libraries), so the only failures that can
1522 happen are when there are library functions that take/return such
1523 structures. There are very few such library functions. I can only recall
1524 seeing two of them: inet_ntoa, and semctl.
1526 See @uref{http://reality.sgi.com/ariel/freeware/,,http://reality.sgi.com/ariel/freeware} for more information about
1527 using GCC on IRIX platforms.
1533 <h3><a name="powerpc-*-linux-gnu*">powerpc-*-linux-gnu*</a></h3>
1537 @uref{ftp://ftp.varesearch.com/pub/support/hjl/binutils,,binutils-2.9.4.0.8}
1538 or newer for a working GCC. It is strongly recommended to recompile binutils
1539 if you initially built it with gcc-2.7.2.x.
1545 <h3><a name="*-*-solaris*">*-*-solaris*</a></h3>
1548 Starting with Solaris, Sun does not ship a C compiler any more. To
1549 bootstrap and install GCC you first have to install a pre-built
1550 compiler, see our @uref{binaries.html,,binaries page} for
1553 You must use GNU Make to build GCC on Solaris 2. If you don't have GNU
1554 Make installed, you can use the prebuilt compiler mentioned above to
1557 Sun as 4.X is broken in that it cannot cope with long symbol names.
1558 A typical error message might look similar to the following:
1560 @samp{/usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041:
1561 error: can't compute value of an expression involving an external symbol.}
1563 This is Sun bug 4237974. This is fixed with patch 108908-02 and has
1564 been fixed in later (5.x) versions of the assembler.
1568 <h3><a name="sparc-sun-solaris*">sparc-sun-solaris*</a></h3>
1571 binutils 2.9.1 has known bugs on this platform. We recommend to use
1572 binutils 2.10 or the vendor tools (Sun as, Sun ld).
1574 Unfortunately, C++ shared libraries, including libstdc++, won't work
1575 properly if assembled with Sun as: the linker will complain about
1576 relocations in read-only sections, in the definition of virtual
1577 tables. Also, Sun as fails to process long symbols resulting from
1578 mangling template-heavy C++ function names.
1584 <h3><a name="sparc-sun-solaris2.7">sparc-sun-solaris2.7</a></h3>
1587 Sun patch 107058-01 (1999-01-13) for SPARC Solaris 7 triggers a bug in
1588 the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8
1589 and later, including all EGCS releases. Sun formerly recommended
1590 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
1591 recommend it only for people who use Sun's compilers.
1593 Here are some workarounds to this problem:
1596 Do not install Sun patch 107058-01 until after Sun releases a
1597 complete patch for bug 4210064. This is the simplest course to take,
1598 unless you must also use Sun's C compiler. Unfortunately 107058-01
1599 is preinstalled on some new Solaris-based hosts, so you may have to
1603 Copy the original, unpatched Solaris 7
1604 @command{/usr/ccs/bin/as} into
1605 @command{/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/2.95.1/as},
1606 adjusting the latter name to fit your local conventions and software
1610 Install Sun patch 106950-03 (1999-05-25) or later. Nobody with
1611 both 107058-01 and 106950-03 installed has reported the bug with GCC
1612 and Sun's dynamic linker. This last course of action is riskiest,
1613 for two reasons. First, you must install 106950 on all hosts that
1614 run code generated by GCC; it doesn't suffice to install it only on
1615 the hosts that run GCC itself. Second, Sun says that 106950-03 is
1616 only a partial fix for bug 4210064, but Sun doesn't know whether the
1617 partial fix is adequate for GCC. Revision -08 or later should fix
1618 the bug, but (as of 1999-10-06) it is still being tested.
1625 <h3><a name="*-sun-solaris2.8">*-sun-solaris2.8</a></h3>
1626 <!-- ripped from the same FAQ that I answered -->
1629 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
1630 newer: g++ will complain that types are missing. These headers assume
1631 that omitting the type means 'int'; this assumption worked for C89 but
1632 is wrong for C++, and is now wrong for C99 also.
1634 g++ accepts such (illegal) constructs with the option @option{-fpermissive}; it
1635 will assume that any missing type is 'int' (as defined by C89).
1637 For Solaris 8, t<h3><a name="older"></a>Older systems</h3>
1639 <p>GCC contains support files for many older (1980s and early
1640 1990s) Unix variants. For the most part, support for these systems
1641 has not been deliberately removed, but it has not been maintained for
1642 several years and may suffer from bitrot. Support from some systems
1643 has been removed from GCC 3: fx80, ns32-ns-genix, pyramid, tahoe,
1644 gmicro, spur; most of these targets had not been updated since GCC
1647 <p>Support for older systems as targets for cross-compilation is less
1648 problematic than support for them as hosts for GCC; if an
1649 enthusiast wishes to make such a target work again
1650 (including resurrecting any of the targets that never worked with GCC
1651 2, starting from the last CVS version before they were removed),
1652 patches <a href="../contribute.html">following the usual
1653 requirements</a> would be likely to be accepted, since they should not
1654 affect the support for more modern targets.</p>
1656 <p>Support for old systems as hosts for GCC can cause problems if the
1657 workarounds for compiler, library and operating system bugs affect the
1658 cleanliness or maintainability of the rest of GCC. In some cases, to
1659 bring GCC up on such a system, if still possible with current GCC, may
1660 require first installing an old version of GCC which did work on that
1661 system, and using it to compile a more recent GCC, to avoid bugs in
1662 the vendor compiler. Old releases of GCC 1 and GCC 2 are available in
1663 the old-releases directory on the <a href="../mirrors.html">GCC mirror
1664 sites</a>. Header bugs may generally be avoided using
1665 <code>fixincludes</code>, but bugs or deficiencies in libraries and
1666 the operating system may still cause problems.</p>
1668 <p>For some systems, old versions of GNU binutils may also be useful,
1669 and are available from pub/binutils/old-releases on <a
1670 href="http://sources.redhat.com/mirrors.html">sources.redhat.com
1671 mirror sites</a>.</p>
1673 <p>Some of the information on specific systems above relates to
1674 such older systems, but much of the information
1675 about GCC on such systems (which may no longer be applicable to
1676 current GCC) is to be found in the GCC texinfo manual.</p>
1679 his is fixed by revision 24 or later of patch 108652
1680 (for SPARCs) or 108653 (for Intels).
1686 <h3><a name="sunv5">Sun V5.0 Compiler Bugs</a></h3>
1689 The Sun V5.0 compilers are known to mis-compile GCC 2.95 and GCC 2.95.1,
1690 which in turn causes GCC to fail its bootstrap comparison test.
1691 GCC 2.95.2 has a workaround.
1697 <h3><a name="sparc-sun-sunos*">sparc-sun-sunos*</a></h3>
1700 A bug in the SunOS4 linker will cause it to crash when linking
1701 -fPIC compiled objects (and will therefore not allow you to build
1704 To fix this problem you can either use the most recent version of
1705 binutils or get the latest SunOS4 linker patch (patch ID 100170-10)
1706 from Sun's patch site.
1712 <h3><a name="sparc-unknown-linux-gnulibc1">sparc-unknown-linux-gnulibc1</a></h3>
1715 It has been reported that you might need
1716 @uref{ftp://ftp.yggdrasil.com/private/hjl,,binutils-2.8.1.0.23}
1717 for this platform, too.
1723 <h3><a name="sparc64-*-*">sparc64-*-*</a></h3>
1726 GCC version 2.95 is not able to compile code correctly for
1727 @code{sparc64} targets. Users of the Linux kernel, at least,
1728 12~can use the @code{sparc32} program to start up a new shell
1729 invocation with an environment that causes @command{configure} to
1730 recognize (via @command{uname -a}) the system as @command{sparc-*-*} instead.
1736 <h3><a name="windows"></a>Microsoft Windows (32 bit)</h3>
1739 A port of GCC 2.95.x is included with the
1740 @uref{http://www.cygwin.com/,,Cygwin environment}.
1742 Current (as of early 2001) snapshots of GCC will build under Cygwin
1743 without modification.
1748 <h3><a name="os2"></a>OS/2</h3>
1751 GCC does not currently support OS/2. However, Andrew Zabolotny has been
1752 working on a generic OS/2 port with pgcc. The current code code can be found
1753 at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
1755 An older copy of GCC 2.8.1 is included with the EMX tools available at
1756 @uref{ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/,,
1757 ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/}.
1762 <h3><a name="older"></a>Older systems</h3>
1765 GCC contains support files for many older (1980s and early
1766 1990s) Unix variants. For the most part, support for these systems
1767 has not been deliberately removed, but it has not been maintained for
1768 several years and may suffer from bitrot. Support from some systems
1769 has been removed from GCC 3: fx80, ns32-ns-genix, pyramid, tahoe,
1770 gmicro, spur; most of these targets had not been updated since GCC
1773 Support for older systems as targets for cross-compilation is less
1774 problematic than support for them as hosts for GCC; if an enthusiast
1775 wishes to make such a target work again (including resurrecting any
1776 of the targets that never worked with GCC 2, starting from the last
1777 CVS version before they were removed), patches
1778 @uref{../contribute.html,,following the usual requirements}
1779 would be likely to be accepted, since they should not affect the
1780 support for more modern targets.
1782 Support for old systems as hosts for GCC can cause problems if the
1783 workarounds for compiler, library and operating system bugs affect the
1784 cleanliness or maintainability of the rest of GCC. In some cases, to
1785 bring GCC up on such a system, if still possible with current GCC, may
1786 require first installing an old version of GCC which did work on that
1787 system, and using it to compile a more recent GCC, to avoid bugs in
1788 the vendor compiler. Old releases of GCC 1 and GCC 2 are available in
1789 the old-releases directory on the
1790 @uref{../mirrors.html,,GCC mirror sites}. Header bugs may generally
1791 be avoided using @code{fixincludes}, but bugs or deficiencies in libraries and
1792 the operating system may still cause problems.
1794 For some systems, old versions of GNU binutils may also be useful,
1795 and are available from pub/binutils/old-releases on
1796 @uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}.
1798 Some of the information on specific systems above relates to
1799 such older systems, but much of the information
1800 about GCC on such systems (which may no longer be applicable to
1801 current GCC) is to be found in the GCC texinfo manual.
1806 <h3><a name="elf_targets">all ELF targets (SVR4, Solaris, etc.)</a></h3>
1809 C++ support is significantly better on ELF targets if you use the GNU
1810 linker; duplicate copies of inlines, vtables and template instantiations
1811 will be discarded automatically.
1820 @uref{./index.html,,Return to the GCC Installation page}
1824 @c ***************************************************************************
1825 @c Part 6 The End of the Document
1827 @comment node-name, next, previous, up
1828 @node Concept Index, , Specific, Top
1832 @unnumbered Concept Index