Merge branch 'master' of ssh://crater.dragonflybsd.org/repository/git/dragonfly
[dragonfly.git] / contrib / gcc-3.4 / gcc / doc / install.texi
CommitLineData
003757ed
MD
1\input texinfo.tex @c -*-texinfo-*-
2@c @ifnothtml
3@c %**start of header
4@setfilename gccinstall.info
5@settitle Installing GCC
6@setchapternewpage odd
7@c %**end of header
8@c @end ifnothtml
9
10@c Specify title for specific html page
11@ifset indexhtml
12@settitle Installing GCC
13@end ifset
14@ifset specifichtml
15@settitle Host/Target specific installation notes for GCC
16@end ifset
17@ifset prerequisiteshtml
18@settitle Prerequisites for GCC
19@end ifset
20@ifset downloadhtml
21@settitle Downloading GCC
22@end ifset
23@ifset configurehtml
24@settitle Installing GCC: Configuration
25@end ifset
26@ifset buildhtml
27@settitle Installing GCC: Building
28@end ifset
29@ifset testhtml
30@settitle Installing GCC: Testing
31@end ifset
32@ifset finalinstallhtml
33@settitle Installing GCC: Final installation
34@end ifset
35@ifset binarieshtml
36@settitle Installing GCC: Binaries
37@end ifset
38@ifset oldhtml
39@settitle Installing GCC: Old documentation
40@end ifset
41@ifset gfdlhtml
42@settitle Installing GCC: GNU Free Documentation License
43@end ifset
44
45@c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
46@c 1999, 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc.
47@c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com
48
49@c Include everything if we're not making html
50@ifnothtml
51@set indexhtml
52@set specifichtml
53@set prerequisiteshtml
54@set downloadhtml
55@set configurehtml
56@set buildhtml
57@set testhtml
58@set finalinstallhtml
59@set binarieshtml
60@set oldhtml
61@set gfdlhtml
62@end ifnothtml
63
64@c Part 2 Summary Description and Copyright
65@copying
66Copyright @copyright{} 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
671999, 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc.
68@sp 1
69Permission is granted to copy, distribute and/or modify this document
70under the terms of the GNU Free Documentation License, Version 1.2 or
71any later version published by the Free Software Foundation; with no
72Invariant Sections, the Front-Cover texts being (a) (see below), and
73with the Back-Cover Texts being (b) (see below). A copy of the
74license is included in the section entitled ``@uref{./gfdl.html,,GNU
75Free Documentation License}''.
76
77(a) The FSF's Front-Cover Text is:
78
79 A GNU Manual
80
81(b) The FSF's Back-Cover Text is:
82
83 You have freedom to copy and modify this GNU Manual, like GNU
84 software. Copies published by the Free Software Foundation raise
85 funds for GNU development.
86@end copying
87@ifinfo
88@insertcopying
89@end ifinfo
90@dircategory Programming
91@direntry
92* gccinstall: (gccinstall). Installing the GNU Compiler Collection.
93@end direntry
94
95@c Part 3 Titlepage and Copyright
96@titlepage
97@sp 10
98@comment The title is printed in a large font.
99@center @titlefont{Installing GCC}
100
101@c The following two commands start the copyright page.
102@page
103@vskip 0pt plus 1filll
104@insertcopying
105@end titlepage
106
107@c Part 4 Top node and Master Menu
108@ifinfo
109@node Top, , , (dir)
110@comment node-name, next, Previous, up
111
112@menu
113* Installing GCC:: This document describes the generic installation
114 procedure for GCC as well as detailing some target
115 specific installation instructions.
116
117* Specific:: Host/target specific installation notes for GCC.
118* Binaries:: Where to get pre-compiled binaries.
119
120* Old:: Old installation documentation.
121
122* GNU Free Documentation License:: How you can copy and share this manual.
123* Concept Index:: This index has two entries.
124@end menu
125@end ifinfo
126
127@c Part 5 The Body of the Document
128@c ***Installing GCC**********************************************************
129@ifnothtml
130@comment node-name, next, previous, up
131@node Installing GCC, Binaries, , Top
132@end ifnothtml
133@ifset indexhtml
134@ifnothtml
135@chapter Installing GCC
136@end ifnothtml
137
138The latest version of this document is always available at
139@uref{http://gcc.gnu.org/install/,,http://gcc.gnu.org/install/}.
140
141This document describes the generic installation procedure for GCC as well
142as detailing some target specific installation instructions.
143
144GCC includes several components that previously were separate distributions
145with their own installation instructions. This document supersedes all
146package specific installation instructions.
147
148@emph{Before} starting the build/install procedure please check the
149@ifnothtml
150@ref{Specific, host/target specific installation notes}.
151@end ifnothtml
152@ifhtml
153@uref{specific.html,,host/target specific installation notes}.
154@end ifhtml
155We recommend you browse the entire generic installation instructions before
156you proceed.
157
158Lists of successful builds for released versions of GCC are
159available at @uref{http://gcc.gnu.org/buildstat.html}.
160These lists are updated as new information becomes available.
161
162The installation procedure itself is broken into five steps.
163
164@ifinfo
165@menu
166* Prerequisites::
167* Downloading the source::
168* Configuration::
169* Building::
170* Testing:: (optional)
171* Final install::
172@end menu
173@end ifinfo
174@ifhtml
175@enumerate
176@item
177@uref{prerequisites.html,,Prerequisites}
178@item
179@uref{download.html,,Downloading the source}
180@item
181@uref{configure.html,,Configuration}
182@item
183@uref{build.html,,Building}
184@item
185@uref{test.html,,Testing} (optional)
186@item
187@uref{finalinstall.html,,Final install}
188@end enumerate
189@end ifhtml
190
191Please note that GCC does not support @samp{make uninstall} and probably
192won't do so in the near future as this would open a can of worms. Instead,
193we suggest that you install GCC into a directory of its own and simply
194remove that directory when you do not need that specific version of GCC
195any longer, and, if shared libraries are installed there as well, no
196more binaries exist that use them.
197
198@ifhtml
199There are also some @uref{old.html,,old installation instructions},
200which are mostly obsolete but still contain some information which has
201not yet been merged into the main part of this manual.
202@end ifhtml
203
204@html
205<hr />
206<p>
207@end html
208@ifhtml
209@uref{./index.html,,Return to the GCC Installation page}
210
211@insertcopying
212@end ifhtml
213@end ifset
214
215@c ***Prerequisites**************************************************
216@ifnothtml
217@comment node-name, next, previous, up
218@node Prerequisites, Downloading the source, , Installing GCC
219@end ifnothtml
220@ifset prerequisiteshtml
221@ifnothtml
222@chapter Prerequisites
223@end ifnothtml
224@cindex Prerequisites
225
226GCC requires that various tools and packages be available for use in the
227build procedure. Modifying GCC sources requires additional tools
228described below.
229
230@heading Tools/packages necessary for building GCC
231@table @asis
232@item ISO C90 compiler
233Necessary to bootstrap the GCC package, although versions of GCC prior
234to 3.4 also allow bootstrapping with a traditional (K&R) C compiler.
235
236To make all languages in a cross-compiler or other configuration where
2373-stage bootstrap is not performed, you need to start with an existing
238GCC binary (version 2.95 or later) because source code for language
239frontends other than C might use GCC extensions.
240
241@item GNAT
242
243In order to build the Ada compiler (GNAT) you must already have GNAT
244installed because portions of the Ada frontend are written in Ada (with
245GNAT extensions.) Refer to the Ada installation instructions for more
246specific information.
247
248@item A ``working'' POSIX compatible shell, or GNU bash
249
250Necessary when running @command{configure} because some
251@command{/bin/sh} shells have bugs and may crash when configuring the
252target libraries. In other cases, @command{/bin/sh} or even some
253@command{ksh} have disastrous corner-case performance problems. This
254can cause target @command{configure} runs to literally take days to
255complete in some cases.
256
257So on some platforms @command{/bin/ksh} is sufficient, on others it
258isn't. See the host/target specific instructions for your platform, or
259use @command{bash} to be sure. Then set @env{CONFIG_SHELL} in your
260environment to your ``good'' shell prior to running
261@command{configure}/@command{make}.
262
263@command{zsh} is not a fully compliant POSIX shell and will not
264work when configuring GCC.
265
266@item GNU binutils
267
268Necessary in some circumstances, optional in others. See the
269host/target specific instructions for your platform for the exact
270requirements.
271
272@item gzip version 1.2.4 (or later) or
273@itemx bzip2 version 1.0.2 (or later)
274
275Necessary to uncompress GCC @command{tar} files when source code is
276obtained via FTP mirror sites.
277
278@item GNU make version 3.79.1 (or later)
279
280You must have GNU make installed to build GCC.
281
282@item GNU tar version 1.12 (or later)
283
284Necessary (only on some platforms) to untar the source code. Many
285systems' @command{tar} programs will also work, only try GNU
286@command{tar} if you have problems.
287
288@end table
289
290
291@heading Tools/packages necessary for modifying GCC
292@table @asis
293@item autoconf versions 2.13 and 2.57
294@itemx GNU m4 version 1.4 (or later)
295
296Necessary when modifying @file{configure.in}, @file{aclocal.m4}, etc.@:
297to regenerate @file{configure} and @file{config.in} files. Most
298directories require autoconf 2.13 (exactly), but @file{libiberty},
299@file{fastjar}, @file{libstdc++-v3}, @file{libjava/libltdl}, and @file{gcc}
300require autoconf 2.57 (exactly).
301
302@item automake versions 1.4-gcj and 1.7.9
303
304Necessary when modifying a @file{Makefile.am} file to regenerate its
305associated @file{Makefile.in}.
306
307Much of GCC does not use automake, so directly edit the @file{Makefile.in}
308file. Specifically this applies to the @file{gcc}, @file{intl},
309@file{libf2c}, @file{libiberty}, @file{libobjc} directories as well as any
310of their subdirectories.
311
312The @file{libstdc++-v3}, @file{libjava/libltdl}, and @file{fastjar}
313directories require automake 1.7.9. However, the Java directories, which
314include @file{boehm-gc}, @file{libffi}, @file{libjava}, and @file{zlib},
315require a modified version of automake 1.4 downloadable from
316@uref{ftp://gcc.gnu.org/pub/java/automake-gcj-1.4.tar.gz}.
317
318@item gettext version 0.12 (or later)
319
320Needed to regenerate @file{gcc.pot}.
321
322@item gperf version 2.7.2 (or later)
323
324Necessary when modifying @command{gperf} input files, e.g.@:
325@file{gcc/cp/cfns.gperf} to regenerate its associated header file, e.g.@:
326@file{gcc/cp/cfns.h}.
327
328@item expect version ???
329@itemx tcl version ???
330@itemx dejagnu version ???
331
332Necessary to run the GCC testsuite.
333
334@item autogen version 5.5.4 (or later) and
335@itemx guile version 1.4.1 (or later)
336
337Necessary to regenerate @file{fixinc/fixincl.x} from
338@file{fixinc/inclhack.def} and @file{fixinc/*.tpl}.
339
340Necessary to run the @file{fixinc} @command{make check}.
341
342Necessary to regenerate the top level @file{Makefile.in} file from
343@file{Makefile.tpl} and @file{Makefile.def}.
344
345@item GNU Bison version 1.28 (or later)
346Berkeley @command{yacc} (@command{byacc}) is also reported to work other
347than for java.
348
349Necessary when modifying @file{*.y} files.
350
351Necessary to build GCC during development because the generated output
352files are not included in the CVS repository. They are included in
353releases.
354
355@item Flex version 2.5.4 (or later)
356
357Necessary when modifying @file{*.l} files.
358
359Necessary to build GCC during development because the generated output
360files are not included in the CVS repository. They are included in
361releases.
362
363@item Texinfo version 4.2 (or later)
364
365Necessary for running @command{makeinfo} when modifying @file{*.texi}
366files to test your changes.
367
368Necessary to build GCC documentation during development because the
369generated output files are not included in the CVS repository. They are
370included in releases.
371
372@item @TeX{} (any working version)
373
374Necessary for running @command{texi2dvi}, used when running
375@command{make dvi} to create DVI files.
376
377@item cvs version 1.10 (or later)
378@itemx ssh (any version)
379
380Necessary to access the CVS repository. Public releases and weekly
381snapshots of the development sources are also available via FTP.
382
383@item perl version 5.6.1 (or later)
384
385Necessary when regenerating @file{Makefile} dependencies in libiberty.
386Necessary when regenerating @file{libiberty/functions.texi}.
387Necessary when generating manpages from Texinfo manuals.
388Used by various scripts to generate some files included in CVS (mainly
389Unicode-related and rarely changing) from source tables.
390
391@item GNU diffutils version 2.7 (or later)
392
393Necessary when creating changes to GCC source code to submit for review.
394
395@item patch version 2.5.4 (or later)
396
397Necessary when applying patches, created with @command{diff}, to one's
398own sources.
399
400@end table
401
402@html
403<hr />
404<p>
405@end html
406@ifhtml
407@uref{./index.html,,Return to the GCC Installation page}
408@end ifhtml
409@end ifset
410
411@c ***Downloading the source**************************************************
412@ifnothtml
413@comment node-name, next, previous, up
414@node Downloading the source, Configuration, Prerequisites, Installing GCC
415@end ifnothtml
416@ifset downloadhtml
417@ifnothtml
418@chapter Downloading GCC
419@end ifnothtml
420@cindex Downloading GCC
421@cindex Downloading the Source
422
423GCC is distributed via @uref{http://gcc.gnu.org/cvs.html,,CVS} and FTP
424tarballs compressed with @command{gzip} or
425@command{bzip2}. It is possible to download a full distribution or specific
426components.
427
3a327f56 428Please refer to the @uref{http://gcc.gnu.org/releases.html,,releases web page}
003757ed
MD
429for information on how to obtain GCC@.
430
431The full distribution includes the C, C++, Objective-C, Fortran, Java,
432and Ada (in case of GCC 3.1 and later) compilers. The full distribution
433also includes runtime libraries for C++, Objective-C, Fortran, and Java.
434In GCC 3.0 and later versions, GNU compiler testsuites are also included
435in the full distribution.
436
437If you choose to download specific components, you must download the core
438GCC distribution plus any language specific distributions you wish to
439use. The core distribution includes the C language front end as well as the
440shared components. Each language has a tarball which includes the language
441front end as well as the language runtime (when appropriate).
442
443Unpack the core distribution as well as any language specific
444distributions in the same directory.
445
446If you also intend to build binutils (either to upgrade an existing
447installation or for use in place of the corresponding tools of your
448OS), unpack the binutils distribution either in the same directory or
449a separate one. In the latter case, add symbolic links to any
450components of the binutils you intend to build alongside the compiler
451(@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
452@file{opcodes}, @dots{}) to the directory containing the GCC sources.
453
454@html
455<hr />
456<p>
457@end html
458@ifhtml
459@uref{./index.html,,Return to the GCC Installation page}
460@end ifhtml
461@end ifset
462
463@c ***Configuration***********************************************************
464@ifnothtml
465@comment node-name, next, previous, up
466@node Configuration, Building, Downloading the source, Installing GCC
467@end ifnothtml
468@ifset configurehtml
469@ifnothtml
470@chapter Installing GCC: Configuration
471@end ifnothtml
472@cindex Configuration
473@cindex Installing GCC: Configuration
474
475Like most GNU software, GCC must be configured before it can be built.
476This document describes the recommended configuration procedure
477for both native and cross targets.
478
479We use @var{srcdir} to refer to the toplevel source directory for
480GCC; we use @var{objdir} to refer to the toplevel build/object directory.
481
482If you obtained the sources via CVS, @var{srcdir} must refer to the top
483@file{gcc} directory, the one where the @file{MAINTAINERS} can be found,
484and not its @file{gcc} subdirectory, otherwise the build will fail.
485
486If either @var{srcdir} or @var{objdir} is located on an automounted NFS
487file system, the shell's built-in @command{pwd} command will return
488temporary pathnames. Using these can lead to various sorts of build
489problems. To avoid this issue, set the @env{PWDCMD} environment
490variable to an automounter-aware @command{pwd} command, e.g.,
491@command{pawd} or @samp{amq -w}, during the configuration and build
492phases.
493
494First, we @strong{highly} recommend that GCC be built into a
495separate directory than the sources which does @strong{not} reside
496within the source tree. This is how we generally build GCC; building
497where @var{srcdir} == @var{objdir} should still work, but doesn't
498get extensive testing; building where @var{objdir} is a subdirectory
499of @var{srcdir} is unsupported.
500
501If you have previously built GCC in the same directory for a
502different target machine, do @samp{make distclean} to delete all files
503that might be invalid. One of the files this deletes is @file{Makefile};
504if @samp{make distclean} complains that @file{Makefile} does not exist
505or issues a message like ``don't know how to make distclean'' it probably
506means that the directory is already suitably clean. However, with the
507recommended method of building in a separate @var{objdir}, you should
508simply use a different @var{objdir} for each target.
509
510Second, when configuring a native system, either @command{cc} or
511@command{gcc} must be in your path or you must set @env{CC} in
512your environment before running configure. Otherwise the configuration
513scripts may fail.
514
515Note that the bootstrap compiler and the resulting GCC must be link
516compatible, else the bootstrap will fail with linker errors about
517incompatible object file formats. Several multilibed targets are
518affected by this requirement, see
519@ifnothtml
520@ref{Specific, host/target specific installation notes}.
521@end ifnothtml
522@ifhtml
523@uref{specific.html,,host/target specific installation notes}.
524@end ifhtml
525
526To configure GCC:
527
528@smallexample
529 % mkdir @var{objdir}
530 % cd @var{objdir}
531 % @var{srcdir}/configure [@var{options}] [@var{target}]
532@end smallexample
533
534
535@heading Target specification
536@itemize @bullet
537@item
538GCC has code to correctly determine the correct value for @var{target}
539for nearly all native systems. Therefore, we highly recommend you not
540provide a configure target when configuring a native compiler.
541
542@item
543@var{target} must be specified as @option{--target=@var{target}}
544when configuring a cross compiler; examples of valid targets would be
545i960-rtems, m68k-coff, sh-elf, etc.
546
547@item
548Specifying just @var{target} instead of @option{--target=@var{target}}
549implies that the host defaults to @var{target}.
550@end itemize
551
552
553@heading Options specification
554
555Use @var{options} to override several configure time options for
556GCC@. A list of supported @var{options} follows; @samp{configure
557--help} may list other options, but those not listed below may not
558work and should not normally be used.
559
560Note that each @option{--enable} option has a corresponding
561@option{--disable} option and that each @option{--with} option has a
562corresponding @option{--without} option.
563
564@table @code
565@item --prefix=@var{dirname}
566Specify the toplevel installation
567directory. This is the recommended way to install the tools into a directory
568other than the default. The toplevel installation directory defaults to
569@file{/usr/local}.
570
571We @strong{highly} recommend against @var{dirname} being the same or a
572subdirectory of @var{objdir} or vice versa. If specifying a directory
573beneath a user's home directory tree, some shells will not expand
574@var{dirname} correctly if it contains the @samp{~} metacharacter; use
575@env{$HOME} instead.
576
577The following standard @command{autoconf} options are supported. Normally you
578should not need to use these options.
579@table @code
580@item --exec-prefix=@var{dirname}
581Specify the toplevel installation directory for architecture-dependent
582files. The default is @file{@var{prefix}}.
583
584@item --bindir=@var{dirname}
585Specify the installation directory for the executables called by users
586(such as @command{gcc} and @command{g++}). The default is
587@file{@var{exec-prefix}/bin}.
588
589@item --libdir=@var{dirname}
590Specify the installation directory for object code libraries and
591internal data files of GCC@. The default is @file{@var{exec-prefix}/lib}.
592
593@item --libexecdir=@var{dirname}
594Specify the installation directory for internal executables of GCC@.
595 The default is @file{@var{exec-prefix}/libexec}.
596
597@item --with-slibdir=@var{dirname}
598Specify the installation directory for the shared libgcc library. The
599default is @file{@var{libdir}}.
600
601@item --infodir=@var{dirname}
602Specify the installation directory for documentation in info format.
603The default is @file{@var{prefix}/info}.
604
605@item --datadir=@var{dirname}
606Specify the installation directory for some architecture-independent
607data files referenced by GCC@. The default is @file{@var{prefix}/share}.
608
609@item --mandir=@var{dirname}
610Specify the installation directory for manual pages. The default is
611@file{@var{prefix}/man}. (Note that the manual pages are only extracts from
612the full GCC manuals, which are provided in Texinfo format. The manpages
613are derived by an automatic conversion process from parts of the full
614manual.)
615
616@item --with-gxx-include-dir=@var{dirname}
617Specify
618the installation directory for G++ header files. The default is
619@file{@var{prefix}/include/c++/@var{version}}.
620
621@end table
622
623@item --program-prefix=@var{prefix}
624GCC supports some transformations of the names of its programs when
625installing them. This option prepends @var{prefix} to the names of
626programs to install in @var{bindir} (see above). For example, specifying
627@option{--program-prefix=foo-} would result in @samp{gcc}
628being installed as @file{/usr/local/bin/foo-gcc}.
629
630@item --program-suffix=@var{suffix}
631Appends @var{suffix} to the names of programs to install in @var{bindir}
632(see above). For example, specifying @option{--program-suffix=-3.1}
633would result in @samp{gcc} being installed as
634@file{/usr/local/bin/gcc-3.1}.
635
636@item --program-transform-name=@var{pattern}
637Applies the @samp{sed} script @var{pattern} to be applied to the names
638of programs to install in @var{bindir} (see above). @var{pattern} has to
639consist of one or more basic @samp{sed} editing commands, separated by
640semicolons. For example, if you want the @samp{gcc} program name to be
641transformed to the installed program @file{/usr/local/bin/myowngcc} and
642the @samp{g++} program name to be transformed to
643@file{/usr/local/bin/gspecial++} without changing other program names,
644you could use the pattern
645@option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'}
646to achieve this effect.
647
648All three options can be combined and used together, resulting in more
649complex conversion patterns. As a basic rule, @var{prefix} (and
650@var{suffix}) are prepended (appended) before further transformations
651can happen with a special transformation script @var{pattern}.
652
653As currently implemented, this option only takes effect for native
654builds; cross compiler binaries' names are not transformed even when a
655transformation is explicitly asked for by one of these options.
656
657For native builds, some of the installed programs are also installed
658with the target alias in front of their name, as in
659@samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
660before the target alias is prepended to the name - so, specifying
661@option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
662resulting binary would be installed as
663@file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}.
664
665As a last shortcoming, none of the installed Ada programs are
666transformed yet, which will be fixed in some time.
667
668@item --with-local-prefix=@var{dirname}
669Specify the
670installation directory for local include files. The default is
671@file{/usr/local}. Specify this option if you want the compiler to
672search directory @file{@var{dirname}/include} for locally installed
673header files @emph{instead} of @file{/usr/local/include}.
674
675You should specify @option{--with-local-prefix} @strong{only} if your
676site has a different convention (not @file{/usr/local}) for where to put
677site-specific files.
678
679The default value for @option{--with-local-prefix} is @file{/usr/local}
680regardless of the value of @option{--prefix}. Specifying
681@option{--prefix} has no effect on which directory GCC searches for
682local header files. This may seem counterintuitive, but actually it is
683logical.
684
685The purpose of @option{--prefix} is to specify where to @emph{install
686GCC}. The local header files in @file{/usr/local/include}---if you put
687any in that directory---are not part of GCC@. They are part of other
688programs---perhaps many others. (GCC installs its own header files in
689another directory which is based on the @option{--prefix} value.)
690
691Both the local-prefix include directory and the GCC-prefix include
692directory are part of GCC's "system include" directories. Although these
693two directories are not fixed, they need to be searched in the proper
694order for the correct processing of the include_next directive. The
695local-prefix include directory is searched before the GCC-prefix
696include directory. Another characteristic of system include directories
697is that pedantic warnings are turned off for headers in these directories.
698
699Some autoconf macros add @option{-I @var{directory}} options to the
700compiler command line, to ensure that directories containing installed
701packages' headers are searched. When @var{directory} is one of GCC's
702system include directories, GCC will ignore the option so that system
703directories continue to be processed in the correct order. This
704may result in a search order different from what was specified but the
705directory will still be searched.
706
707GCC automatically searches for ordinary libraries using
708@env{GCC_EXEC_PREFIX}. Thus, when the same installation prefix is
709used for both GCC and packages, GCC will automatically search for
710both headers and libraries. This provides a configuration that is
711easy to use. GCC behaves in a manner similar to that when it is
712installed as a system compiler in @file{/usr}.
713
714Sites that need to install multiple versions of GCC may not want to
715use the above simple configuration. It is possible to use the
716@option{--program-prefix}, @option{--program-suffix} and
717@option{--program-transform-name} options to install multiple versions
718into a single directory, but it may be simpler to use different prefixes
719and the @option{--with-local-prefix} option to specify the location of the
720site-specific files for each version. It will then be necessary for
721users to specify explicitly the location of local site libraries
722(e.g., with @env{LIBRARY_PATH}).
723
724The same value can be used for both @option{--with-local-prefix} and
725@option{--prefix} provided it is not @file{/usr}. This can be used
726to avoid the default search of @file{/usr/local/include}.
727
728@strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
729The directory you use for @option{--with-local-prefix} @strong{must not}
730contain any of the system's standard header files. If it did contain
731them, certain programs would be miscompiled (including GNU Emacs, on
732certain targets), because this would override and nullify the header
733file corrections made by the @command{fixincludes} script.
734
735Indications are that people who use this option use it based on mistaken
736ideas of what it is for. People use it as if it specified where to
737install part of GCC@. Perhaps they make this assumption because
738installing GCC creates the directory.
739
740@item --enable-shared[=@var{package}[,@dots{}]]
741Build shared versions of libraries, if shared libraries are supported on
742the target platform. Unlike GCC 2.95.x and earlier, shared libraries
743are enabled by default on all platforms that support shared libraries,
744except for @samp{libobjc} which is built as a static library only by
745default.
746
747If a list of packages is given as an argument, build shared libraries
748only for the listed packages. For other packages, only static libraries
749will be built. Package names currently recognized in the GCC tree are
750@samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
751@samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc} and
752@samp{libjava}. Note that @samp{libobjc} does not recognize itself by
753any name, so, if you list package names in @option{--enable-shared},
754you will only get static Objective-C libraries. @samp{libf2c} and
755@samp{libiberty} do not support shared libraries at all.
756
757Use @option{--disable-shared} to build only static libraries. Note that
758@option{--disable-shared} does not accept a list of package names as
759argument, only @option{--enable-shared} does.
760
761@item @anchor{with-gnu-as}--with-gnu-as
762Specify that the compiler should assume that the
763assembler it finds is the GNU assembler. However, this does not modify
764the rules to find an assembler and will result in confusion if the
765assembler found is not actually the GNU assembler. (Confusion may also
766result if the compiler finds the GNU assembler but has not been
767configured with @option{--with-gnu-as}.) If you have more than one
768assembler installed on your system, you may want to use this option in
769connection with @option{--with-as=@var{pathname}}.
770
771The following systems are the only ones where it makes a difference
772whether you use the GNU assembler. On any other system,
773@option{--with-gnu-as} has no effect.
774
775@itemize @bullet
776@item @samp{hppa1.0-@var{any}-@var{any}}
777@item @samp{hppa1.1-@var{any}-@var{any}}
778@item @samp{i386-@var{any}-sysv}
779@item @samp{m68k-bull-sysv}
780@item @samp{m68k-hp-hpux}
781@item @samp{m68000-hp-hpux}
782@item @samp{m68000-att-sysv}
783@item @samp{@var{any}-lynx-lynxos}
784@item @samp{mips-@var{any}}
785@item @samp{sparc-sun-solaris2.@var{any}}
786@item @samp{sparc64-@var{any}-solaris2.@var{any}}
787@end itemize
788
789On the systems listed above (except for the HP-PA, the SPARC, for ISC on
790the 386, and for @samp{mips-sgi-irix5.*}), if you use the GNU assembler,
791you should also use the GNU linker (and specify @option{--with-gnu-ld}).
792
793@item @anchor{with-as}--with-as=@var{pathname}
794Specify that the
795compiler should use the assembler pointed to by @var{pathname}, rather
796than the one found by the standard rules to find an assembler, which
797are:
798@itemize @bullet
799@item
800Check the @file{@var{libexec}/gcc/@var{target}/@var{version}}
801directory, where @var{libexec} defaults to
802@file{@var{exec-prefix}/libexec} and @var{exec-prefix} defaults to
803@var{prefix} which defaults to @file{/usr/local} unless overridden by
804the @option{--prefix=@var{pathname}} switch described
805above. @var{target} is the target system triple, such as
806@samp{sparc-sun-solaris2.7}, and @var{version} denotes the GCC
807version, such as 3.0.
808@item
809Check operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
810Sun Solaris 2).
811@end itemize
812Note that these rules do not check for the value of @env{PATH}. You may
813want to use @option{--with-as} if no assembler is installed in the
814directories listed above, or if you have multiple assemblers installed
815and want to choose one that is not found by the above rules.
816
817@item @anchor{with-gnu-ld}--with-gnu-ld
818Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
819but for the linker.
820
821@item --with-ld=@var{pathname}
822Same as @uref{#with-as,,@option{--with-as}}
823but for the linker.
824
825@item --with-stabs
826Specify that stabs debugging
827information should be used instead of whatever format the host normally
828uses. Normally GCC uses the same debug format as the host system.
829
830On MIPS based systems and on Alphas, you must specify whether you want
831GCC to create the normal ECOFF debugging format, or to use BSD-style
832stabs passed through the ECOFF symbol table. The normal ECOFF debug
833format cannot fully handle languages other than C@. BSD stabs format can
834handle other languages, but it only works with the GNU debugger GDB@.
835
836Normally, GCC uses the ECOFF debugging format by default; if you
837prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@.
838
839No matter which default you choose when you configure GCC, the user
840can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
841the debug format for a particular compilation.
842
843@option{--with-stabs} is meaningful on the ISC system on the 386, also, if
844@option{--with-gas} is used. It selects use of stabs debugging
845information embedded in COFF output. This kind of debugging information
846supports C++ well; ordinary COFF debugging information does not.
847
848@option{--with-stabs} is also meaningful on 386 systems running SVR4. It
849selects use of stabs debugging information embedded in ELF output. The
850C++ compiler currently (2.6.0) does not support the DWARF debugging
851information normally used on 386 SVR4 platforms; stabs provide a
852workable alternative. This requires gas and gdb, as the normal SVR4
853tools can not generate or interpret stabs.
854
855@item --disable-multilib
856Specify that multiple target
857libraries to support different target variants, calling
858conventions, etc should not be built. The default is to build a
859predefined set of them.
860
861Some targets provide finer-grained control over which multilibs are built
862(e.g., @option{--disable-softfloat}):
863@table @code
864@item arc-*-elf*
865biendian.
866
867@item arm-*-*
868fpu, 26bit, underscore, interwork, biendian, nofmult.
869
870@item m68*-*-*
871softfloat, m68881, m68000, m68020.
872
873@item mips*-*-*
874single-float, biendian, softfloat.
875
876@item powerpc*-*-*, rs6000*-*-*
877aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
878sysv, aix.
879
880@end table
881
882@item --enable-threads
883Specify that the target
884supports threads. This affects the Objective-C compiler and runtime
885library, and exception handling for other languages like C++ and Java.
886On some systems, this is the default.
887
888In general, the best (and, in many cases, the only known) threading
889model available will be configured for use. Beware that on some
890systems, GCC has not been taught what threading models are generally
891available for the system. In this case, @option{--enable-threads} is an
892alias for @option{--enable-threads=single}.
893
894@item --disable-threads
895Specify that threading support should be disabled for the system.
896This is an alias for @option{--enable-threads=single}.
897
898@item --enable-threads=@var{lib}
899Specify that
900@var{lib} is the thread support library. This affects the Objective-C
901compiler and runtime library, and exception handling for other languages
902like C++ and Java. The possibilities for @var{lib} are:
903
904@table @code
905@item aix
906AIX thread support.
907@item dce
908DCE thread support.
909@item gnat
910Ada tasking support. For non-Ada programs, this setting is equivalent
911to @samp{single}. When used in conjunction with the Ada run time, it
912causes GCC to use the same thread primitives as Ada uses. This option
913is necessary when using both Ada and the back end exception handling,
914which is the default for most Ada targets.
915@item mach
916Generic MACH thread support, known to work on NeXTSTEP@. (Please note
917that the file needed to support this configuration, @file{gthr-mach.h}, is
918missing and thus this setting will cause a known bootstrap failure.)
919@item no
920This is an alias for @samp{single}.
921@item posix
922Generic POSIX thread support.
923@item rtems
924RTEMS thread support.
925@item single
926Disable thread support, should work for all platforms.
927@item solaris
928Sun Solaris 2 thread support.
929@item vxworks
930VxWorks thread support.
931@item win32
932Microsoft Win32 API thread support.
933@end table
934
935@item --with-cpu=@var{cpu}
936Specify which cpu variant the compiler should generate code for by default.
937@var{cpu} will be used as the default value of the @option{-mcpu=} switch.
938This option is only supported on some targets, including ARM, i386, PowerPC,
939and SPARC@.
940
941@item --with-schedule=@var{cpu}
942@itemx --with-arch=@var{cpu}
943@itemx --with-tune=@var{cpu}
944@itemx --with-abi=@var{abi}
945@itemx --with-float=@var{type}
946These configure options provide default values for the @option{-mschedule=},
947@option{-march=}, @option{-mtune=}, and @option{-mabi=} options and for
948@option{-mhard-float} or @option{-msoft-float}. As with @option{--with-cpu},
949which switches will be accepted and acceptable values of the arguments depend
950on the target.
951
952@item --enable-altivec
953Specify that the target supports AltiVec vector enhancements. This
954option will adjust the ABI for AltiVec enhancements, as well as generate
955AltiVec code when appropriate. This option is only available for
956PowerPC systems.
957
958@item --enable-__cxa_atexit
959Define if you want to use __cxa_atexit, rather than atexit, to
960register C++ destructors for local statics and global objects.
961This is essential for fully standards-compliant handling of
962destructors, but requires __cxa_atexit in libc. This option is currently
963only available on systems with GNU libc. When enabled, this will cause
964@option{-fuse-cxa-exit} to be passed by default.
965
966@item --enable-target-optspace
967Specify that target
968libraries should be optimized for code space instead of code speed.
969This is the default for the m32r platform.
970
971@item --disable-cpp
972Specify that a user visible @command{cpp} program should not be installed.
973
974@item --with-cpp-install-dir=@var{dirname}
975Specify that the user visible @command{cpp} program should be installed
976in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
977
978@item --enable-initfini-array
979Force the use of sections @code{.init_array} and @code{.fini_array}
980(instead of @code{.init} and @code{.fini}) for constructors and
981destructors. Option @option{--disable-initfini-array} has the
982opposite effect. If neither option is specified, the configure script
983will try to guess whether the @code{.init_array} and
984@code{.fini_array} sections are supported and, if they are, use them.
985
986@item --enable-maintainer-mode
987The build rules that
988regenerate the GCC master message catalog @file{gcc.pot} are normally
989disabled. This is because it can only be rebuilt if the complete source
990tree is present. If you have changed the sources and want to rebuild the
991catalog, configuring with @option{--enable-maintainer-mode} will enable
992this. Note that you need a recent version of the @code{gettext} tools
993to do so.
994
995@item --enable-generated-files-in-srcdir
996Neither the .c and .h files that are generated from bison and flex nor the
997info manuals and man pages that are built from the .texi files are present
998in the CVS development tree. When building GCC from that development tree,
999or from a snapshot which are created from CVS, then those generated files
1000are placed in your build directory, which allows for the source to be in a
1001readonly directory.
1002
1003If you configure with @option{--enable-generated-files-in-srcdir} then those
1004generated files will go into the source directory. This is mainly intended
1005for generating release or prerelease tarballs of the GCC sources, since it
1006is not a requirement that the users of source releases to have flex, bison, or
1007makeinfo.
1008
1009@item --enable-version-specific-runtime-libs
1010Specify
1011that runtime libraries should be installed in the compiler specific
1012subdirectory (@file{@var{libdir}/gcc}) rather than the usual places. In
1013addition, @samp{libstdc++}'s include files will be installed into
1014@file{@var{libdir}} unless you overruled it by using
1015@option{--with-gxx-include-dir=@var{dirname}}. Using this option is
1016particularly useful if you intend to use several versions of GCC in
1017parallel. This is currently supported by @samp{libf2c} and
1018@samp{libstdc++}, and is the default for @samp{libobjc} which cannot be
1019changed in this case.
1020
1021@item --enable-languages=@var{lang1},@var{lang2},@dots{}
1022Specify that only a particular subset of compilers and
1023their runtime libraries should be built. For a list of valid values for
1024@var{langN} you can issue the following command in the
1025@file{gcc} directory of your GCC source tree:@*
1026@smallexample
1027grep language= */config-lang.in
1028@end smallexample
1029Currently, you can use any of the following:
1030@code{ada}, @code{c}, @code{c++}, @code{f77}, @code{java}, @code{objc}.
1031Building the Ada compiler has special requirements, see below.@*
1032If you do not pass this flag, all languages available in the @file{gcc}
1033sub-tree will be configured. Re-defining @code{LANGUAGES} when calling
1034@samp{make bootstrap} @strong{does not} work anymore, as those
1035language sub-directories might not have been configured!
1036
1037@item --with-dwarf2
1038Specify that the compiler should
1039use DWARF 2 debugging information as the default.
1040
1041@item --enable-win32-registry
1042@itemx --enable-win32-registry=@var{key}
1043@itemx --disable-win32-registry
1044The @option{--enable-win32-registry} option enables Microsoft Windows-hosted GCC
1045to look up installations paths in the registry using the following key:
1046
1047@smallexample
1048@code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
1049@end smallexample
1050
1051@var{key} defaults to GCC version number, and can be overridden by the
1052@option{--enable-win32-registry=@var{key}} option. Vendors and distributors
1053who use custom installers are encouraged to provide a different key,
1054perhaps one comprised of vendor name and GCC version number, to
1055avoid conflict with existing installations. This feature is enabled
1056by default, and can be disabled by @option{--disable-win32-registry}
1057option. This option has no effect on the other hosts.
1058
1059@item --nfp
1060Specify that the machine does not have a floating point unit. This
1061option only applies to @samp{m68k-sun-sunos@var{n}}. On any other
1062system, @option{--nfp} has no effect.
1063
1064@item --enable-werror
1065@itemx --disable-werror
1066@itemx --enable-werror=yes
1067@itemx --enable-werror=no
1068When you specify this option, it controls whether certain files in the
1069compiler are built with @option{-Werror} in bootstrap stage2 and later.
1070If you don't specify it, @option{-Werror} is turned on for the main
1071development trunk. However it defaults to off for release branches and
1072final releases. The specific files which get @option{-Werror} are
1073controlled by the Makefiles.
1074
1075@item --enable-checking
1076@itemx --enable-checking=@var{list}
1077When you specify this option, the compiler is built to perform checking
1078of tree node types when referencing fields of that node, and some other
1079internal consistency checks. This does not change the generated code,
1080but adds error checking within the compiler. This will slow down the
1081compiler and may only work properly if you are building the compiler
1082with GCC@. This is on by default when building from CVS or snapshots,
1083but off for releases. More control over the checks may be had by
1084specifying @var{list}; the categories of checks available are
1085@samp{misc}, @samp{tree}, @samp{gc}, @samp{rtl}, @samp{rtlflag},
1086@samp{fold}, @samp{gcac} and @samp{valgrind}. The check @samp{valgrind}
1087requires the external @command{valgrind} simulator, available from
eba42d60 1088@uref{http://valgrind.org/}. The default when @var{list} is
003757ed
MD
1089not specified is @samp{misc,tree,gc,rtlflag}; the checks @samp{rtl},
1090@samp{gcac} and @samp{valgrind} are very expensive.
1091
1092@item --enable-coverage
1093@itemx --enable-coverage=@var{level}
1094With this option, the compiler is built to collect self coverage
1095information, every time it is run. This is for internal development
1096purposes, and only works when the compiler is being built with gcc. The
1097@var{level} argument controls whether the compiler is built optimized or
1098not, values are @samp{opt} and @samp{noopt}. For coverage analysis you
1099want to disable optimization, for performance analysis you want to
1100enable optimization. When coverage is enabled, the default level is
1101without optimization.
1102
1103@item --enable-gather-detailed-mem-stats
1104When this option is specified more detailed information on memory
1105allocation is gathered. This information is printed when using
1106@option{-fmem-report}.
1107
1108@item --enable-nls
1109@itemx --disable-nls
1110The @option{--enable-nls} option enables Native Language Support (NLS),
1111which lets GCC output diagnostics in languages other than American
1112English. Native Language Support is enabled by default if not doing a
1113canadian cross build. The @option{--disable-nls} option disables NLS@.
1114
1115@item --with-included-gettext
1116If NLS is enabled, the @option{--with-included-gettext} option causes the build
1117procedure to prefer its copy of GNU @command{gettext}.
1118
1119@item --with-catgets
1120If NLS is enabled, and if the host lacks @code{gettext} but has the
1121inferior @code{catgets} interface, the GCC build procedure normally
1122ignores @code{catgets} and instead uses GCC's copy of the GNU
1123@code{gettext} library. The @option{--with-catgets} option causes the
1124build procedure to use the host's @code{catgets} in this situation.
1125
1126@item --with-libiconv-prefix=@var{dir}
1127Search for libiconv header files in @file{@var{dir}/include} and
1128libiconv library files in @file{@var{dir}/lib}.
1129
1130@item --enable-obsolete
1131Enable configuration for an obsoleted system. If you attempt to
1132configure GCC for a system (build, host, or target) which has been
1133obsoleted, and you do not specify this flag, configure will halt with an
1134error message.
1135
1136All support for systems which have been obsoleted in one release of GCC
1137is removed entirely in the next major release, unless someone steps
1138forward to maintain the port.
1139@end table
1140
1141@subheading Cross-Compiler-Specific Options
1142The following options only apply to building cross compilers.
1143@table @code
1144@item --with-sysroot
1145@itemx --with-sysroot=@var{dir}
1146Tells GCC to consider @var{dir} as the root of a tree that contains a
1147(subset of) the root filesystem of the target operating system.
1148Target system headers, libraries and run-time object files will be
1149searched in there. The specified directory is not copied into the
1150install tree, unlike the options @option{--with-headers} and
1151@option{--with-libs} that this option obsoletes. The default value,
1152in case @option{--with-sysroot} is not given an argument, is
1153@option{$@{gcc_tooldir@}/sys-root}. If the specified directory is a
1154subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to
1155the GCC binaries if the installation tree is moved.
1156
1157@item --with-headers
1158@itemx --with-headers=@var{dir}
1159Deprecated in favor of @option{--with-sysroot}.
1160Specifies that target headers are available when building a cross compiler.
1161The @var{dir} argument specifies a directory which has the target include
1162files. These include files will be copied into the @file{gcc} install
1163directory. @emph{This option with the @var{dir} argument is required} when
1164building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include}
1165doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does
1166pre-exist, the @var{dir} argument may be omitted. @command{fixincludes}
1167will be run on these files to make them compatible with GCC.
1168
1169@item --without-headers
1170Tells GCC not use any target headers from a libc when building a cross
1171compiler. When crossing to GNU/Linux, you need the headers so GCC
1172can build the exception handling for libgcc.
1173See @uref{http://www.objsw.com/CrossGCC/,,CrossGCC} for more information
1174on this option.
1175
1176@item --with-libs
1177@itemx --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
1178Deprecated in favor of @option{--with-sysroot}.
1179Specifies a list of directories which contain the target runtime
1180libraries. These libraries will be copied into the @file{gcc} install
1181directory. If the directory list is omitted, this option has no
1182effect.
1183@item --with-newlib
1184Specifies that @samp{newlib} is
1185being used as the target C library. This causes @code{__eprintf} to be
1186omitted from @file{libgcc.a} on the assumption that it will be provided by
1187@samp{newlib}.
1188@end table
1189
1190@subheading Java-Specific Options
1191
1192The following option applies to the build of the Java front end.
1193
1194@table @code
1195@item --disable-libgcj
1196Specify that the run-time libraries
1197used by GCJ should not be built. This is useful in case you intend
1198to use GCJ with some other run-time, or you're going to install it
1199separately, or it just happens not to build on your particular
1200machine. In general, if the Java front end is enabled, the GCJ
1201libraries will be enabled too, unless they're known to not work on
1202the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
1203may need to port it; in this case, before modifying the top-level
1204@file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
1205you may use @option{--enable-libgcj} to override the default.
1206
1207@end table
1208
1209The following options apply to building @samp{libgcj}.
1210
1211@subsubheading General Options
1212
1213@table @code
1214@item --disable-getenv-properties
1215Don't set system properties from @env{GCJ_PROPERTIES}.
1216
1217@item --enable-hash-synchronization
1218Use a global hash table for monitor locks. Ordinarily,
1219@samp{libgcj}'s @samp{configure} script automatically makes
1220the correct choice for this option for your platform. Only use
1221this if you know you need the library to be configured differently.
1222
1223@item --enable-interpreter
1224Enable the Java interpreter. The interpreter is automatically
1225enabled by default on all platforms that support it. This option
1226is really only useful if you want to disable the interpreter
1227(using @option{--disable-interpreter}).
1228
1229@item --disable-java-net
1230Disable java.net. This disables the native part of java.net only,
1231using non-functional stubs for native method implementations.
1232
1233@item --disable-jvmpi
1234Disable JVMPI support.
1235
1236@item --with-ecos
1237Enable runtime eCos target support.
1238
1239@item --without-libffi
1240Don't use @samp{libffi}. This will disable the interpreter and JNI
1241support as well, as these require @samp{libffi} to work.
1242
1243@item --enable-libgcj-debug
1244Enable runtime debugging code.
1245
1246@item --enable-libgcj-multifile
1247If specified, causes all @file{.java} source files to be
1248compiled into @file{.class} files in one invocation of
1249@samp{gcj}. This can speed up build time, but is more
1250resource-intensive. If this option is unspecified or
1251disabled, @samp{gcj} is invoked once for each @file{.java}
1252file to compile into a @file{.class} file.
1253
1254@item --with-libiconv-prefix=DIR
1255Search for libiconv in @file{DIR/include} and @file{DIR/lib}.
1256
1257@item --enable-sjlj-exceptions
1258Force use of @code{builtin_setjmp} for exceptions. @samp{configure}
1259ordinarily picks the correct value based on the platform. Only use
1260this option if you are sure you need a different setting.
1261
1262@item --with-system-zlib
1263Use installed @samp{zlib} rather than that included with GCC@.
1264
1265@item --with-win32-nlsapi=ansi, unicows or unicode
1266Indicates how MinGW @samp{libgcj} translates between UNICODE
1267characters and the Win32 API.
1268@table @code
1269@item ansi
1270Use the single-byte @code{char} and the Win32 A functions natively,
1271translating to and from UNICODE when using these functions. If
1272unspecified, this is the default.
1273
1274@item unicows
1275Use the @code{WCHAR} and Win32 W functions natively. Adds
1276@code{-lunicows} to @file{libgcj.spec} to link with @samp{libunicows}.
1277@file{unicows.dll} needs to be deployed on Microsoft Windows 9X machines
1278running built executables. @file{libunicows.a}, an open-source
1279import library around Microsoft's @code{unicows.dll}, is obtained from
1280@uref{http://libunicows.sourceforge.net/}, which also gives details
1281on getting @file{unicows.dll} from Microsoft.
1282
1283@item unicode
1284Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not}
1285add @code{-lunicows} to @file{libgcj.spec}. The built executables will
1286only run on Microsoft Windows NT and above.
1287@end table
1288@end table
1289
1290@subsubheading AWT-Specific Options
1291
1292@table @code
1293@item --with-x
1294Use the X Window System.
1295
1296@item --enable-java-awt=PEER(S)
1297Specifies the AWT peer library or libraries to build alongside
1298@samp{libgcj}. If this option is unspecified or disabled, AWT
1299will be non-functional. Current valid values are @option{gtk} and
1300@option{xlib}. Multiple libraries should be separated by a
1301comma (i.e. @option{--enable-java-awt=gtk,xlib}).
1302
1303@item --enable-gtk-cairo
1304Build the cairo Graphics2D implementation on GTK.
1305
1306@item --enable-java-gc=TYPE
1307Choose garbage collector. Defaults to @option{boehm} if unspecified.
1308
1309@item --disable-gtktest
1310Do not try to compile and run a test GTK+ program.
1311
1312@item --disable-glibtest
1313Do not try to compile and run a test GLIB program.
1314
1315@item --with-libart-prefix=PFX
1316Prefix where libart is installed (optional).
1317
1318@item --with-libart-exec-prefix=PFX
1319Exec prefix where libart is installed (optional).
1320
1321@item --disable-libarttest
1322Do not try to compile and run a test libart program.
1323
1324@end table
1325
1326@html
1327<hr />
1328<p>
1329@end html
1330@ifhtml
1331@uref{./index.html,,Return to the GCC Installation page}
1332@end ifhtml
1333@end ifset
1334
1335@c ***Building****************************************************************
1336@ifnothtml
1337@comment node-name, next, previous, up
1338@node Building, Testing, Configuration, Installing GCC
1339@end ifnothtml
1340@ifset buildhtml
1341@ifnothtml
1342@chapter Building
1343@end ifnothtml
1344@cindex Installing GCC: Building
1345
1346Now that GCC is configured, you are ready to build the compiler and
1347runtime libraries.
1348
003757ed
MD
1349Some commands executed when making the compiler may fail (return a
1350nonzero status) and be ignored by @command{make}. These failures, which
1351are often due to files that were not found, are expected, and can safely
1352be ignored.
1353
1354It is normal to have compiler warnings when compiling certain files.
1355Unless you are a GCC developer, you can generally ignore these warnings
1356unless they cause compilation to fail. Developers should attempt to fix
1357any warnings encountered, however they can temporarily continue past
1358warnings-as-errors by specifying the configure flag
1359@option{--disable-werror}.
1360
1361On certain old systems, defining certain environment variables such as
1362@env{CC} can interfere with the functioning of @command{make}.
1363
1364If you encounter seemingly strange errors when trying to build the
1365compiler in a directory other than the source directory, it could be
1366because you have previously configured the compiler in the source
1367directory. Make sure you have done all the necessary preparations.
1368
1369If you build GCC on a BSD system using a directory stored in an old System
1370V file system, problems may occur in running @command{fixincludes} if the
1371System V file system doesn't support symbolic links. These problems
1372result in a failure to fix the declaration of @code{size_t} in
1373@file{sys/types.h}. If you find that @code{size_t} is a signed type and
1374that type mismatches occur, this could be the cause.
1375
1376The solution is not to use such a directory for building GCC@.
1377
1378When building from CVS or snapshots, or if you modify parser sources,
1379you need the Bison parser generator installed. Any version 1.25 or
1380later should work; older versions may also work. If you do not modify
1381parser sources, releases contain the Bison-generated files and you do
1382not need Bison installed to build them.
1383
1384When building from CVS or snapshots, or if you modify Texinfo
1385documentation, you need version 4.2 or later of Texinfo installed if you
1386want Info documentation to be regenerated. Releases contain Info
1387documentation pre-built for the unmodified documentation in the release.
1388
1389@section Building a native compiler
1390
1391For a native build issue the command @samp{make bootstrap}. This
1392will build the entire GCC system, which includes the following steps:
1393
1394@itemize @bullet
1395@item
1396Build host tools necessary to build the compiler such as texinfo, bison,
1397gperf.
1398
1399@item
1400Build target tools for use by the compiler such as binutils (bfd,
1401binutils, gas, gprof, ld, and opcodes)
1402if they have been individually linked
1403or moved into the top level GCC source tree before configuring.
1404
1405@item
1406Perform a 3-stage bootstrap of the compiler.
1407
1408@item
1409Perform a comparison test of the stage2 and stage3 compilers.
1410
1411@item
1412Build runtime libraries using the stage3 compiler from the previous step.
1413
1414@end itemize
1415
1416If you are short on disk space you might consider @samp{make
1417bootstrap-lean} instead. This is identical to @samp{make
1418bootstrap} except that object files from the stage1 and
1419stage2 of the 3-stage bootstrap of the compiler are deleted as
1420soon as they are no longer needed.
1421
1422If you want to save additional space during the bootstrap and in
1423the final installation as well, you can build the compiler binaries
1424without debugging information as in the following example. This will save
1425roughly 40% of disk space both for the bootstrap and the final installation.
1426(Libraries will still contain debugging information.)
1427
1428@smallexample
1429 make CFLAGS='-O' LIBCFLAGS='-g -O2' \
1430 LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap
1431@end smallexample
1432
1433If you wish to use non-default GCC flags when compiling the stage2 and
1434stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing
1435@samp{make bootstrap}. Non-default optimization flags are less well
1436tested here than the default of @samp{-g -O2}, but should still work.
1437In a few cases, you may find that you need to specify special flags such
1438as @option{-msoft-float} here to complete the bootstrap; or, if the
1439native compiler miscompiles the stage1 compiler, you may need to work
1440around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the
1441stage1 compiler that were miscompiled, or by using @samp{make
1442bootstrap4} to increase the number of stages of bootstrap.
1443
1444If you used the flag @option{--enable-languages=@dots{}} to restrict
1445the compilers to be built, only those you've actually enabled will be
1446built. This will of course only build those runtime libraries, for
1447which the particular compiler has been built. Please note,
1448that re-defining @env{LANGUAGES} when calling @samp{make bootstrap}
1449@strong{does not} work anymore!
1450
1451If the comparison of stage2 and stage3 fails, this normally indicates
1452that the stage2 compiler has compiled GCC incorrectly, and is therefore
1453a potentially serious bug which you should investigate and report. (On
1454a few systems, meaningful comparison of object files is impossible; they
1455always appear ``different''. If you encounter this problem, you will
1456need to disable comparison in the @file{Makefile}.)
1457
1458@section Building a cross compiler
1459
1460We recommend reading the
1461@uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ}
1462for information about building cross compilers.
1463
1464When building a cross compiler, it is not generally possible to do a
14653-stage bootstrap of the compiler. This makes for an interesting problem
1466as parts of GCC can only be built with GCC@.
1467
1468To build a cross compiler, we first recommend building and installing a
1469native compiler. You can then use the native GCC compiler to build the
1470cross compiler. The installed native compiler needs to be GCC version
14712.95 or later.
1472
1473Assuming you have already installed a native copy of GCC and configured
1474your cross compiler, issue the command @command{make}, which performs the
1475following steps:
1476
1477@itemize @bullet
1478@item
1479Build host tools necessary to build the compiler such as texinfo, bison,
1480gperf.
1481
1482@item
1483Build target tools for use by the compiler such as binutils (bfd,
1484binutils, gas, gprof, ld, and opcodes)
1485if they have been individually linked or moved into the top level GCC source
1486tree before configuring.
1487
1488@item
1489Build the compiler (single stage only).
1490
1491@item
1492Build runtime libraries using the compiler from the previous step.
1493@end itemize
1494
1495Note that if an error occurs in any step the make process will exit.
1496
1497If you are not building GNU binutils in the same source tree as GCC,
1498you will need a cross-assembler and cross-linker installed before
1499configuring GCC@. Put them in the directory
1500@file{@var{prefix}/@var{target}/bin}. Here is a table of the tools
1501you should put in this directory:
1502
1503@table @file
1504@item as
1505This should be the cross-assembler.
1506
1507@item ld
1508This should be the cross-linker.
1509
1510@item ar
1511This should be the cross-archiver: a program which can manipulate
1512archive files (linker libraries) in the target machine's format.
1513
1514@item ranlib
1515This should be a program to construct a symbol table in an archive file.
1516@end table
1517
1518The installation of GCC will find these programs in that directory,
1519and copy or link them to the proper place to for the cross-compiler to
1520find them when run later.
1521
1522The easiest way to provide these files is to build the Binutils package.
1523Configure it with the same @option{--host} and @option{--target}
1524options that you use for configuring GCC, then build and install
1525them. They install their executables automatically into the proper
1526directory. Alas, they do not support all the targets that GCC
1527supports.
1528
1529If you are not building a C library in the same source tree as GCC,
1530you should also provide the target libraries and headers before
1531configuring GCC, specifying the directories with
1532@option{--with-sysroot} or @option{--with-headers} and
1533@option{--with-libs}. Many targets also require ``start files'' such
1534as @file{crt0.o} and
1535@file{crtn.o} which are linked into each executable. There may be several
1536alternatives for @file{crt0.o}, for use with profiling or other
1537compilation options. Check your target's definition of
1538@code{STARTFILE_SPEC} to find out what start files it uses.
1539
1540@section Building in parallel
1541
1542You can use @samp{make bootstrap MAKE="make -j 2" -j 2}, or just
1543@samp{make -j 2 bootstrap} for GNU Make 3.79 and above, instead of
1544@samp{make bootstrap} to build GCC in parallel.
1545You can also specify a bigger number, and in most cases using a value
1546greater than the number of processors in your machine will result in
1547fewer and shorter I/O latency hits, thus improving overall throughput;
1548this is especially true for slow drives and network filesystems.
1549
1550@section Building the Ada compiler
1551
1552In order to build GNAT, the Ada compiler, you need a working GNAT
1553compiler (GNAT version 3.14 or later, or GCC version 3.1 or later),
1554including GNAT tools such as @command{gnatmake} and @command{gnatlink},
1555since the Ada front end is written in Ada (with some
1556GNAT-specific extensions), and GNU make.
1557
1558@command{configure} does not test whether the GNAT installation works
1559and has a sufficiently recent version; if too old a GNAT version is
1560installed, the build will fail unless @option{--enable-languages} is
1561used to disable building the Ada front end.
1562
1563At the moment, the GNAT library and several tools for GNAT are not built
1564by @samp{make bootstrap}. For a native build, you have to invoke
1565@samp{make gnatlib_and_tools} in the @file{@var{objdir}/gcc}
1566subdirectory before proceeding with the next steps.
1567For a cross build, you need to invoke
1568@samp{make gnatlib cross-gnattools ada.all.cross}. For a canadian
1569cross you only need to invoke @samp{make cross-gnattools}; the GNAT
1570library would be the same as the one built for the cross compiler.
1571
1572For example, you can build a native Ada compiler by issuing the
1573following commands (assuming @command{make} is GNU make):
1574
1575@smallexample
1576 cd @var{objdir}
1577 @var{srcdir}/configure --enable-languages=c,ada
1578 cd @var{objdir}
1579 make bootstrap
1580 cd gcc
1581 make gnatlib_and_tools
1582 cd ..
1583@end smallexample
1584
1585Currently, when compiling the Ada front end, you cannot use the parallel
1586build feature described in the previous section.
1587
1588@section Building with profile feedback
1589
1590It is possible to use profile feedback to optimize the compiler itself. This
1591should result in a faster compiler binary. Experiments done on x86 using gcc
15923.3 showed approximately 7 percent speedup on compiling C programs. To
1593bootstrap compiler with profile feedback, use @code{make profiledbootstrap}.
1594
1595When @samp{make profiledbootstrap} is run, it will first build a @code{stage1}
1596compiler. This compiler is used to build a @code{stageprofile} compiler
1597instrumented to collect execution counts of instruction and branch
1598probabilities. Then runtime libraries are compiled with profile collected.
1599Finally a @code{stagefeedback} compiler is built using the information collected.
1600
1601Unlike @samp{make bootstrap} several additional restrictions apply. The
1602compiler used to build @code{stage1} needs to support a 64-bit integral type.
1603It is recommended to only use GCC for this. Also parallel make is currently
1604not supported since collisions in profile collecting may occur.
1605
1606@html
1607<hr />
1608<p>
1609@end html
1610@ifhtml
1611@uref{./index.html,,Return to the GCC Installation page}
1612@end ifhtml
1613@end ifset
1614
1615@c ***Testing*****************************************************************
1616@ifnothtml
1617@comment node-name, next, previous, up
1618@node Testing, Final install, Building, Installing GCC
1619@end ifnothtml
1620@ifset testhtml
1621@ifnothtml
1622@chapter Installing GCC: Testing
1623@end ifnothtml
1624@cindex Testing
1625@cindex Installing GCC: Testing
1626@cindex Testsuite
1627
1628Before you install GCC, we encourage you to run the testsuites and to
1629compare your results with results from a similar configuration that have
1630been submitted to the
1631@uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
1632Some of these archived results are linked from the build status lists
1633at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who
1634reports a successful build runs the testsuites and submits the results.
1635This step is optional and may require you to download additional software,
1636but it can give you confidence in your new GCC installation or point out
1637problems before you install and start using your new GCC.
1638
1639First, you must have @uref{download.html,,downloaded the testsuites}.
1640These are part of the full distribution, but if you downloaded the
1641``core'' compiler plus any front ends, you must download the testsuites
1642separately.
1643
1644Second, you must have the testing tools installed. This includes
1645@uref{http://www.gnu.org/software/dejagnu/,,DejaGnu} 1.4.1 or 1.4.3
1646and later, Tcl, and Expect; the DejaGnu site has links to these.
1647
1648If the directories where @command{runtest} and @command{expect} were
1649installed are not in the @env{PATH}, you may need to set the following
1650environment variables appropriately, as in the following example (which
1651assumes that DejaGnu has been installed under @file{/usr/local}):
1652
1653@smallexample
1654 TCL_LIBRARY = /usr/local/share/tcl8.0
1655 DEJAGNULIBS = /usr/local/share/dejagnu
1656@end smallexample
1657
1658(On systems such as Cygwin, these paths are required to be actual
1659paths, not mounts or links; presumably this is due to some lack of
1660portability in the DejaGnu code.)
1661
1662
1663Finally, you can run the testsuite (which may take a long time):
1664@smallexample
1665 cd @var{objdir}; make -k check
1666@end smallexample
1667
1668This will test various components of GCC, such as compiler
1669front ends and runtime libraries. While running the testsuite, DejaGnu
1670might emit some harmless messages resembling
1671@samp{WARNING: Couldn't find the global config file.} or
1672@samp{WARNING: Couldn't find tool init file} that can be ignored.
1673
3a327f56 1674@section How can you run the testsuite on selected tests?
003757ed
MD
1675
1676In order to run sets of tests selectively, there are targets
1677@samp{make check-gcc} and @samp{make check-g++}
1678in the @file{gcc} subdirectory of the object directory. You can also
1679just run @samp{make check} in a subdirectory of the object directory.
1680
1681
1682A more selective way to just run all @command{gcc} execute tests in the
1683testsuite is to use
1684
1685@smallexample
1686 make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
1687@end smallexample
1688
1689Likewise, in order to run only the @command{g++} ``old-deja'' tests in
1690the testsuite with filenames matching @samp{9805*}, you would use
1691
1692@smallexample
1693 make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
1694@end smallexample
1695
1696The @file{*.exp} files are located in the testsuite directories of the GCC
1697source, the most important ones being @file{compile.exp},
1698@file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
1699To get a list of the possible @file{*.exp} files, pipe the
1700output of @samp{make check} into a file and look at the
1701@samp{Running @dots{} .exp} lines.
1702
1703@section Passing options and running multiple testsuites
1704
1705You can pass multiple options to the testsuite using the
1706@samp{--target_board} option of DejaGNU, either passed as part of
1707@samp{RUNTESTFLAGS}, or directly to @command{runtest} if you prefer to
1708work outside the makefiles. For example,
1709
1710@smallexample
1711 make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fno-strength-reduce"
1712@end smallexample
1713
1714will run the standard @command{g++} testsuites (``unix'' is the target name
1715for a standard native testsuite situation), passing
1716@samp{-O3 -fno-strength-reduce} to the compiler on every test, i.e.,
1717slashes separate options.
1718
1719You can run the testsuites multiple times using combinations of options
1720with a syntax similar to the brace expansion of popular shells:
1721
1722@smallexample
1723 @dots{}"--target_board=arm-sim@{-mhard-float,-msoft-float@}@{-O1,-O2,-O3,@}"
1724@end smallexample
1725
1726(Note the empty option caused by the trailing comma in the final group.)
1727The following will run each testsuite eight times using the @samp{arm-sim}
1728target, as if you had specified all possible combinations yourself:
1729
1730@smallexample
1731 --target_board=arm-sim/-mhard-float/-O1
1732 --target_board=arm-sim/-mhard-float/-O2
1733 --target_board=arm-sim/-mhard-float/-O3
1734 --target_board=arm-sim/-mhard-float
1735 --target_board=arm-sim/-msoft-float/-O1
1736 --target_board=arm-sim/-msoft-float/-O2
1737 --target_board=arm-sim/-msoft-float/-O3
1738 --target_board=arm-sim/-msoft-float
1739@end smallexample
1740
1741They can be combined as many times as you wish, in arbitrary ways. This
1742list:
1743
1744@smallexample
1745 @dots{}"--target_board=unix/-Wextra@{-O3,-fno-strength-reduce@}@{-fomit-frame-pointer,@}"
1746@end smallexample
1747
1748will generate four combinations, all involving @samp{-Wextra}.
1749
1750The disadvantage to this method is that the testsuites are run in serial,
1751which is a waste on multiprocessor systems. For users with GNU Make and
1752a shell which performs brace expansion, you can run the testsuites in
1753parallel by having the shell perform the combinations and @command{make}
1754do the parallel runs. Instead of using @samp{--target_board}, use a
1755special makefile target:
1756
1757@smallexample
1758 make -j@var{N} check-@var{testsuite}//@var{test-target}/@var{option1}/@var{option2}/@dots{}
1759@end smallexample
1760
1761For example,
1762
1763@smallexample
1764 make -j3 check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@}
1765@end smallexample
1766
1767will run three concurrent ``make-gcc'' testsuites, eventually testing all
1768ten combinations as described above. Note that this is currently only
1769supported in the @file{gcc} subdirectory. (To see how this works, try
1770typing @command{echo} before the example given here.)
1771
1772
1773@section Additional testing for Java Class Libraries
1774
1775The Java runtime tests can be executed via @samp{make check}
1776in the @file{@var{target}/libjava/testsuite} directory in
1777the build tree.
1778
1779The @uref{http://sources.redhat.com/mauve/,,Mauve Project} provides
1780a suite of tests for the Java Class Libraries. This suite can be run
1781as part of libgcj testing by placing the Mauve tree within the libjava
1782testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by
1783specifying the location of that tree when invoking @samp{make}, as in
1784@samp{make MAUVEDIR=~/mauve check}.
1785
1786@uref{http://www-124.ibm.com/developerworks/oss/cvs/jikes/~checkout~/jacks/jacks.html,,Jacks}
3a327f56 1787is a free testsuite that tests Java compiler front ends. This suite
003757ed
MD
1788can be run as part of libgcj testing by placing the Jacks tree within
1789the libjava testsuite at @file{libjava/testsuite/libjava.jacks/jacks}.
1790
1791@section How to interpret test results
1792
1793The result of running the testsuite are various @file{*.sum} and @file{*.log}
1794files in the testsuite subdirectories. The @file{*.log} files contain a
1795detailed log of the compiler invocations and the corresponding
1796results, the @file{*.sum} files summarize the results. These summaries
1797contain status codes for all tests:
1798
1799@itemize @bullet
1800@item
1801PASS: the test passed as expected
1802@item
1803XPASS: the test unexpectedly passed
1804@item
1805FAIL: the test unexpectedly failed
1806@item
1807XFAIL: the test failed as expected
1808@item
1809UNSUPPORTED: the test is not supported on this platform
1810@item
1811ERROR: the testsuite detected an error
1812@item
1813WARNING: the testsuite detected a possible problem
1814@end itemize
1815
1816It is normal for some tests to report unexpected failures. At the
3a327f56
JS
1817current time the testing harness does not allow fine grained control
1818over whether or not a test is expected to fail. This problem should
1819be fixed in future releases.
003757ed
MD
1820
1821
1822@section Submitting test results
1823
1824If you want to report the results to the GCC project, use the
1825@file{contrib/test_summary} shell script. Start it in the @var{objdir} with
1826
1827@smallexample
1828 @var{srcdir}/contrib/test_summary -p your_commentary.txt \
1829 -m gcc-testresults@@gcc.gnu.org |sh
1830@end smallexample
1831
1832This script uses the @command{Mail} program to send the results, so
1833make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is
1834prepended to the testsuite summary and should contain any special
1835remarks you have on your results or your build environment. Please
1836do not edit the testsuite result block or the subject line, as these
1837messages may be automatically processed.
1838
1839@html
1840<hr />
1841<p>
1842@end html
1843@ifhtml
1844@uref{./index.html,,Return to the GCC Installation page}
1845@end ifhtml
1846@end ifset
1847
1848@c ***Final install***********************************************************
1849@ifnothtml
1850@comment node-name, next, previous, up
1851@node Final install, , Testing, Installing GCC
1852@end ifnothtml
1853@ifset finalinstallhtml
1854@ifnothtml
1855@chapter Installing GCC: Final installation
1856@end ifnothtml
1857
1858Now that GCC has been built (and optionally tested), you can install it with
1859@smallexample
1860cd @var{objdir}; make install
1861@end smallexample
1862
1863We strongly recommend to install into a target directory where there is
1864no previous version of GCC present.
1865
1866That step completes the installation of GCC; user level binaries can
1867be found in @file{@var{prefix}/bin} where @var{prefix} is the value
1868you specified with the @option{--prefix} to configure (or
1869@file{/usr/local} by default). (If you specified @option{--bindir},
1870that directory will be used instead; otherwise, if you specified
1871@option{--exec-prefix}, @file{@var{exec-prefix}/bin} will be used.)
1872Headers for the C++ and Java libraries are installed in
1873@file{@var{prefix}/include}; libraries in @file{@var{libdir}}
1874(normally @file{@var{prefix}/lib}); internal parts of the compiler in
1875@file{@var{libdir}/gcc} and @file{@var{libexecdir}/gcc}; documentation
1876in info format in @file{@var{infodir}} (normally
1877@file{@var{prefix}/info}).
1878
1879When installing cross-compilers, GCC's executables
1880are not only installed into @file{@var{bindir}}, that
1881is, @file{@var{exec-prefix}/bin}, but additionally into
1882@file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory
1883exists. Typically, such @dfn{tooldirs} hold target-specific
1884binutils, including assembler and linker.
1885
1886Installation into a temporary staging area or into a @command{chroot}
1887jail can be achieved with the command
1888
1889@smallexample
1890make DESTDIR=@var{path-to-rootdir} install
1891@end smallexample
1892
1893@noindent where @var{path-to-rootdir} is the absolute path of
1894a directory relative to which all installation paths will be
1895interpreted. Note that the directory specified by @code{DESTDIR}
1896need not exist yet; it will be created if necessary.
1897
1898There is a subtle point with tooldirs and @code{DESTDIR}:
1899If you relocate a cross-compiler installation with
1900e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory
1901@file{@var{rootdir}/@var{exec-prefix}/@var{target-alias}/bin} will
1902be filled with duplicated GCC executables only if it already exists,
1903it will not be created otherwise. This is regarded as a feature,
1904not as a bug, because it gives slightly more control to the packagers
1905using the @code{DESTDIR} feature.
1906
1907If you built a released version of GCC using @samp{make bootstrap} then please
1908quickly review the build status page for your release, available from
1909@uref{http://gcc.gnu.org/buildstat.html}.
1910If your system is not listed for the version of GCC that you built,
1911send a note to
1912@email{gcc@@gcc.gnu.org} indicating
1913that you successfully built and installed GCC.
1914Include the following information:
1915
1916@itemize @bullet
1917@item
3a327f56 1918Output from running @file{@var{srcdir}/config.guess}. Do not send
003757ed
MD
1919that file itself, just the one-line output from running it.
1920
1921@item
1922The output of @samp{gcc -v} for your newly installed @command{gcc}.
1923This tells us which version of GCC you built and the options you passed to
1924configure.
1925
1926@item
1927Whether you enabled all languages or a subset of them. If you used a
1928full distribution then this information is part of the configure
1929options in the output of @samp{gcc -v}, but if you downloaded the
1930``core'' compiler plus additional front ends then it isn't apparent
1931which ones you built unless you tell us about it.
1932
1933@item
1934If the build was for GNU/Linux, also include:
1935@itemize @bullet
1936@item
1937The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
1938this information should be available from @file{/etc/issue}.
1939
1940@item
1941The version of the Linux kernel, available from @samp{uname --version}
1942or @samp{uname -a}.
1943
1944@item
1945The version of glibc you used; for RPM-based systems like Red Hat,
1946Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
1947and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
1948@end itemize
1949For other systems, you can include similar information if you think it is
1950relevant.
1951
1952@item
1953Any other information that you think would be useful to people building
1954GCC on the same configuration. The new entry in the build status list
1955will include a link to the archived copy of your message.
1956@end itemize
1957
1958We'd also like to know if the
1959@ifnothtml
1960@ref{Specific, host/target specific installation notes}
1961@end ifnothtml
1962@ifhtml
1963@uref{specific.html,,host/target specific installation notes}
1964@end ifhtml
1965didn't include your host/target information or if that information is
1966incomplete or out of date. Send a note to
3a327f56 1967@email{gcc@@gcc.gnu.org} detailing how the information should be changed.
003757ed 1968
3a327f56 1969If you find a bug, please report it following the
003757ed
MD
1970@uref{../bugs.html,,bug reporting guidelines}.
1971
1972If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
1973dvi}. You will need to have @command{texi2dvi} (version at least 4.2)
1974and @TeX{} installed. This creates a number of @file{.dvi} files in
1975subdirectories of @file{@var{objdir}}; these may be converted for
1976printing with programs such as @command{dvips}. You can also
1977@uref{http://www.gnu.org/order/order.html,,buy printed manuals from the
1978Free Software Foundation}, though such manuals may not be for the most
1979recent version of GCC@.
1980
1981@html
1982<hr />
1983<p>
1984@end html
1985@ifhtml
1986@uref{./index.html,,Return to the GCC Installation page}
1987@end ifhtml
1988@end ifset
1989
1990@c ***Binaries****************************************************************
1991@ifnothtml
1992@comment node-name, next, previous, up
1993@node Binaries, Specific, Installing GCC, Top
1994@end ifnothtml
1995@ifset binarieshtml
1996@ifnothtml
1997@chapter Installing GCC: Binaries
1998@end ifnothtml
1999@cindex Binaries
2000@cindex Installing GCC: Binaries
2001
2002We are often asked about pre-compiled versions of GCC@. While we cannot
2003provide these for all platforms, below you'll find links to binaries for
2004various platforms where creating them by yourself is not easy due to various
2005reasons.
2006
2007Please note that we did not create these binaries, nor do we
2008support them. If you have any problems installing them, please
2009contact their makers.
2010
2011@itemize
2012@item
2013AIX:
2014@itemize
2015@item
2016@uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX};
2017
2018@item
2019@uref{http://aixpdslib.seas.ucla.edu,,UCLA Software Library for AIX}.
2020@end itemize
2021
2022@item
2023DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}.
2024
2025@item
2026Renesas H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
2027Development Tools for the Renesas H8/300[HS] Series}.
2028
2029@item
2030HP-UX:
2031@itemize
2032@item
eba42d60 2033@uref{http://hpux.cs.utah.edu/,,HP-UX Porting Center};
003757ed
MD
2034
2035@item
2036@uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
2037@end itemize
2038
2039@item
2040Motorola 68HC11/68HC12---@uref{http://www.gnu-m68hc11.org,,GNU
2041Development Tools for the Motorola 68HC11/68HC12}.
2042
2043@item
2044@uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
2045OpenServer/Unixware}.
2046
003757ed
MD
2047@item
2048Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware}.
2049
2050@item
2051SGI---@uref{http://freeware.sgi.com/,,SGI Freeware}.
2052
2053@item
2054Microsoft Windows:
2055@itemize
2056@item
2057The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project;
2058@item
2059The @uref{http://www.mingw.org/,,MinGW} project.
2060@end itemize
2061
2062@item
2063@uref{ftp://ftp.thewrittenword.com/packages/by-name/,,The
2064Written Word} offers binaries for
2065AIX 4.3.2.
2066IRIX 6.5,
2067Digital UNIX 4.0D and 5.1,
2068GNU/Linux (i386),
2069HP-UX 10.20, 11.00, and 11.11, and
2070Solaris/SPARC 2.5.1, 2.6, 2.7, 8, and 9,
3a327f56
JS
2071
2072@item
2073@uref{http://www.openpkg.org/,,OpenPKG} offers binaries for quite a
2074number of platforms.
003757ed
MD
2075@end itemize
2076
2077In addition to those specific offerings, you can get a binary
2078distribution CD-ROM from the
eba42d60 2079@uref{http://www.gnu.org/order/order.html,,Free Software Foundation}.
003757ed
MD
2080It contains binaries for a number of platforms, and
2081includes not only GCC, but other stuff as well. The current CD does
2082not contain the latest version of GCC, but it should allow
2083bootstrapping the compiler. An updated version of that disk is in the
2084works.
2085
2086@html
2087<hr />
2088<p>
2089@end html
2090@ifhtml
2091@uref{./index.html,,Return to the GCC Installation page}
2092@end ifhtml
2093@end ifset
2094
2095@c ***Specific****************************************************************
2096@ifnothtml
2097@comment node-name, next, previous, up
2098@node Specific, Old, Binaries, Top
2099@end ifnothtml
2100@ifset specifichtml
2101@ifnothtml
2102@chapter Host/target specific installation notes for GCC
2103@end ifnothtml
2104@cindex Specific
2105@cindex Specific installation notes
2106@cindex Target specific installation
2107@cindex Host specific installation
2108@cindex Target specific installation notes
2109
2110Please read this document carefully @emph{before} installing the
2111GNU Compiler Collection on your machine.
2112
2113@ifhtml
2114@itemize
2115@item
1c1138ce 2116@uref{#alpha-x-x,,alpha*-*-*}
003757ed 2117@item
1c1138ce 2118@uref{#alpha-dec-osf,,alpha*-dec-osf*}
003757ed 2119@item
1c1138ce 2120@uref{#alphaev5-cray-unicosmk,,alphaev5-cray-unicosmk*}
003757ed 2121@item
1c1138ce 2122@uref{#arc-x-elf,,arc-*-elf}
003757ed 2123@item
1c1138ce
JS
2124@uref{#arm-x-elf,,arm-*-elf}
2125@uref{#arm-x-coff,,arm-*-coff}
2126@uref{#arm-x-aout,,arm-*-aout}
003757ed 2127@item
1c1138ce 2128@uref{#xscale-x-x,,xscale-*-*}
003757ed
MD
2129@item
2130@uref{#avr,,avr}
2131@item
2132@uref{#c4x,,c4x}
2133@item
2134@uref{#dos,,DOS}
2135@item
2136@uref{#dsp16xx,,dsp16xx}
2137@item
1c1138ce 2138@uref{#x-x-freebsd,,*-*-freebsd*}
003757ed
MD
2139@item
2140@uref{#h8300-hms,,h8300-hms}
2141@item
1c1138ce 2142@uref{#hppa-hp-hpux,,hppa*-hp-hpux*}
003757ed 2143@item
1c1138ce 2144@uref{#hppa-hp-hpux10,,hppa*-hp-hpux10}
003757ed 2145@item
1c1138ce 2146@uref{#hppa-hp-hpux11,,hppa*-hp-hpux11}
003757ed 2147@item
1c1138ce 2148@uref{#i370-x-x,,i370-*-*}
003757ed 2149@item
1c1138ce 2150@uref{#x-x-linux-gnu,,*-*-linux-gnu}
003757ed 2151@item
1c1138ce 2152@uref{#ix86-x-linuxaout,,i?86-*-linux*aout}
003757ed 2153@item
1c1138ce 2154@uref{#ix86-x-linux,,i?86-*-linux*}
003757ed 2155@item
1c1138ce 2156@uref{#ix86-x-sco32v5,,i?86-*-sco3.2v5*}
003757ed 2157@item
1c1138ce 2158@uref{#ix86-x-udk,,i?86-*-udk}
003757ed 2159@item
1c1138ce 2160@uref{#ia64-x-linux,,ia64-*-linux}
003757ed 2161@item
1c1138ce 2162@uref{#ia64-x-hpux,,ia64-*-hpux*}
003757ed 2163@item
1c1138ce 2164@uref{#x-ibm-aix,,*-ibm-aix*}
003757ed 2165@item
1c1138ce 2166@uref{#ip2k-x-elf,,ip2k-*-elf}
003757ed 2167@item
1c1138ce 2168@uref{#iq2000-x-elf,,iq2000-*-elf}
003757ed 2169@item
1c1138ce 2170@uref{#m32r-x-elf,,m32r-*-elf}
003757ed
MD
2171@item
2172@uref{#m6811-elf,,m6811-elf}
2173@item
2174@uref{#m6812-elf,,m6812-elf}
2175@item
2176@uref{#m68k-hp-hpux,,m68k-hp-hpux}
2177@item
1c1138ce 2178@uref{#mips-x-x,,mips-*-*}
003757ed
MD
2179@item
2180@uref{#mips-sgi-irix5,,mips-sgi-irix5}
2181@item
2182@uref{#mips-sgi-irix6,,mips-sgi-irix6}
2183@item
1c1138ce 2184@uref{#powerpc-x-x,,powerpc*-*-*, powerpc-*-sysv4}
003757ed 2185@item
1c1138ce 2186@uref{#powerpc-x-darwin,,powerpc-*-darwin*}
003757ed 2187@item
1c1138ce 2188@uref{#powerpc-x-elf,,powerpc-*-elf, powerpc-*-sysv4}
003757ed 2189@item
1c1138ce 2190@uref{#powerpc-x-linux-gnu,,powerpc*-*-linux-gnu*}
003757ed 2191@item
1c1138ce 2192@uref{#powerpc-x-netbsd,,powerpc-*-netbsd*}
003757ed 2193@item
1c1138ce 2194@uref{#powerpc-x-eabisim,,powerpc-*-eabisim}
003757ed 2195@item
1c1138ce 2196@uref{#powerpc-x-eabi,,powerpc-*-eabi}
003757ed 2197@item
1c1138ce 2198@uref{#powerpcle-x-elf,,powerpcle-*-elf, powerpcle-*-sysv4}
003757ed 2199@item
1c1138ce 2200@uref{#powerpcle-x-eabisim,,powerpcle-*-eabisim}
003757ed 2201@item
1c1138ce 2202@uref{#powerpcle-x-eabi,,powerpcle-*-eabi}
003757ed 2203@item
1c1138ce 2204@uref{#s390-x-linux,,s390-*-linux*}
003757ed 2205@item
1c1138ce 2206@uref{#s390x-x-linux,,s390x-*-linux*}
003757ed 2207@item
1c1138ce 2208@uref{#s390x-ibm-tpf,,s390x-ibm-tpf*}
003757ed 2209@item
1c1138ce 2210@uref{#x-x-solaris2,,*-*-solaris2*}
003757ed 2211@item
1c1138ce 2212@uref{#sparc-sun-solaris2,,sparc-sun-solaris2*}
003757ed 2213@item
1c1138ce 2214@uref{#sparc-sun-solaris27,,sparc-sun-solaris2.7}
003757ed 2215@item
1c1138ce 2216@uref{#sparc-x-linux,,sparc-*-linux*}
003757ed 2217@item
1c1138ce 2218@uref{#sparc64-x-solaris2,,sparc64-*-solaris2*}
003757ed 2219@item
1c1138ce 2220@uref{#sparcv9-x-solaris2,,sparcv9-*-solaris2*}
003757ed 2221@item
1c1138ce 2222@uref{#x-x-sysv,,*-*-sysv*}
003757ed
MD
2223@item
2224@uref{#vax-dec-ultrix,,vax-dec-ultrix}
2225@item
1c1138ce 2226@uref{#x-x-vxworks,,*-*-vxworks*}
003757ed 2227@item
1c1138ce 2228@uref{#x86-64-x-x,,x86_64-*-*, amd64-*-*}
003757ed 2229@item
1c1138ce 2230@uref{#xtensa-x-elf,,xtensa-*-elf}
003757ed 2231@item
1c1138ce 2232@uref{#xtensa-x-linux,,xtensa-*-linux*}
003757ed
MD
2233@item
2234@uref{#windows,,Microsoft Windows}
2235@item
2236@uref{#os2,,OS/2}
2237@item
2238@uref{#older,,Older systems}
2239@end itemize
2240
2241@itemize
2242@item
1c1138ce 2243@uref{#elf,,all ELF targets} (SVR4, Solaris 2, etc.)
003757ed
MD
2244@end itemize
2245@end ifhtml
2246
2247
2248@html
2249<!-- -------- host/target specific issues start here ---------------- -->
2250<hr />
2251@end html
1c1138ce 2252@heading @anchor{alpha-x-x}alpha*-*-*
003757ed
MD
2253
2254This section contains general configuration information for all
2255alpha-based platforms using ELF (in particular, ignore this section for
2256DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this
2257section, please read all other sections that match your target.
2258
2259We require binutils 2.11.2 or newer.
2260Previous binutils releases had a number of problems with DWARF 2
2261debugging information, not the least of which is incorrect linking of
2262shared libraries.
2263
2264@html
2265<hr />
2266@end html
1c1138ce 2267@heading @anchor{alpha-dec-osf}alpha*-dec-osf*
003757ed
MD
2268Systems using processors that implement the DEC Alpha architecture and
2269are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
2270Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
2271
2272As of GCC 3.2, versions before @code{alpha*-dec-osf4} are no longer
2273supported. (These are the versions which identify themselves as DEC
2274OSF/1.)
2275
2276In Digital Unix V4.0, virtual memory exhausted bootstrap failures
2277may be fixed by configuring with @option{--with-gc=simple},
2278reconfiguring Kernel Virtual Memory and Swap parameters
2279per the @command{/usr/sbin/sys_check} Tuning Suggestions,
2280or applying the patch in
2281@uref{http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html}.
2282
2283In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
2284currently (2001-06-13) work with @command{mips-tfile}. As a workaround,
2285we need to use the old assembler, invoked via the barely documented
2286@option{-oldas} option. To bootstrap GCC, you either need to use the
2287Compaq C Compiler:
2288
2289@smallexample
2290 % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
2291@end smallexample
2292
2293or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
2294
2295@smallexample
2296 % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
2297@end smallexample
2298
2299As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld}
2300are supported on Tru64 UNIX, so you must not configure GCC with
2301@option{--with-gnu-as} or @option{--with-gnu-ld}.
2302
2303GCC writes a @samp{.verstamp} directive to the assembler output file
2304unless it is built as a cross-compiler. It gets the version to use from
2305the system header file @file{/usr/include/stamp.h}. If you install a
2306new version of DEC Unix, you should rebuild GCC to pick up the new version
2307stamp.
2308
2309Note that since the Alpha is a 64-bit architecture, cross-compilers from
231032-bit machines will not generate code as efficient as that generated
2311when the compiler is running on a 64-bit machine because many
2312optimizations that depend on being able to represent a word on the
2313target in an integral value on the host cannot be performed. Building
2314cross-compilers on the Alpha for 32-bit machines has only been tested in
2315a few cases and may not work properly.
2316
2317@samp{make compare} may fail on old versions of DEC Unix unless you add
2318@option{-save-temps} to @code{CFLAGS}. On these systems, the name of the
2319assembler input file is stored in the object file, and that makes
2320comparison fail if it differs between the @code{stage1} and
2321@code{stage2} compilations. The option @option{-save-temps} forces a
2322fixed name to be used for the assembler input file, instead of a
2323randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
2324unless the comparisons fail without that option. If you add
2325@option{-save-temps}, you will have to manually delete the @samp{.i} and
2326@samp{.s} files after each series of compilations.
2327
2328GCC now supports both the native (ECOFF) debugging format used by DBX
2329and GDB and an encapsulated STABS format for use only with GDB@. See the
2330discussion of the @option{--with-stabs} option of @file{configure} above
2331for more information on these formats and how to select them.
2332
2333There is a bug in DEC's assembler that produces incorrect line numbers
2334for ECOFF format when the @samp{.align} directive is used. To work
2335around this problem, GCC will not emit such alignment directives
2336while writing ECOFF format debugging information even if optimization is
2337being performed. Unfortunately, this has the very undesirable
2338side-effect that code addresses when @option{-O} is specified are
2339different depending on whether or not @option{-g} is also specified.
2340
2341To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
2342DBX@. DEC is now aware of this problem with the assembler and hopes to
2343provide a fix shortly.
2344
2345@html
2346<hr />
2347@end html
1c1138ce 2348@heading @anchor{alphaev5-cray-unicosmk}alphaev5-cray-unicosmk*
003757ed
MD
2349Cray T3E systems running Unicos/Mk.
2350
2351This port is incomplete and has many known bugs. We hope to improve the
2352support for this target soon. Currently, only the C front end is supported,
2353and it is not possible to build parallel applications. Cray modules are not
2354supported; in particular, Craylibs are assumed to be in
2355@file{/opt/ctl/craylibs/craylibs}.
2356
2357You absolutely @strong{must} use GNU make on this platform. Also, you
2358need to tell GCC where to find the assembler and the linker. The
2359simplest way to do so is by providing @option{--with-as} and
2360@option{--with-ld} to @file{configure}, e.g.@:
2361
2362@smallexample
2363 configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld \
2364 --enable-languages=c
2365@end smallexample
2366
2367The comparison test during @samp{make bootstrap} fails on Unicos/Mk
2368because the assembler inserts timestamps into object files. You should
2369be able to work around this by doing @samp{make all} after getting this
2370failure.
2371
2372@html
2373<hr />
2374@end html
1c1138ce 2375@heading @anchor{arc-x-elf}arc-*-elf
003757ed
MD
2376Argonaut ARC processor.
2377This configuration is intended for embedded systems.
2378
2379@html
2380<hr />
2381@end html
1c1138ce
JS
2382@heading @anchor{arm-x-elf}arm-*-elf
2383@heading @anchor{xscale-x-x}xscale-*-*
003757ed
MD
2384ARM-family processors. Subtargets that use the ELF object format
2385require GNU binutils 2.13 or newer. Such subtargets include:
2386@code{arm-*-freebsd}, @code{arm-*-netbsdelf}, @code{arm-*-*linux},
2387@code{arm-*-rtems} and @code{arm-*-kaos}.
2388
2389@html
2390<hr />
2391@end html
1c1138ce 2392@heading @anchor{arm-x-coff}arm-*-coff
003757ed
MD
2393ARM-family processors. Note that there are two different varieties
2394of PE format subtarget supported: @code{arm-wince-pe} and
2395@code{arm-pe} as well as a standard COFF target @code{arm-*-coff}.
2396
2397@html
2398<hr />
2399@end html
1c1138ce 2400@heading @anchor{arm-x-aout}arm-*-aout
003757ed
MD
2401ARM-family processors. These targets support the AOUT file format:
2402@code{arm-*-aout}, @code{arm-*-netbsd}.
2403
2404@html
2405<hr />
2406@end html
2407@heading @anchor{avr}avr
2408
2409ATMEL AVR-family micro controllers. These are used in embedded
2410applications. There are no standard Unix configurations.
2411@ifnothtml
2412@xref{AVR Options,, AVR Options, gcc, Using and Porting the GNU Compiler
2413Collection (GCC)},
2414@end ifnothtml
2415@ifhtml
2416See ``AVR Options'' in the main manual
2417@end ifhtml
2418for the list of supported MCU types.
2419
2420Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
2421
2422Further installation notes and other useful information about AVR tools
2423can also be obtained from:
2424
2425@itemize @bullet
2426@item
eba42d60 2427@uref{http://www.nongnu.org/avr/,,http://www.nongnu.org/avr/}
003757ed
MD
2428@item
2429@uref{http://home.overta.ru/users/denisc/,,http://home.overta.ru/users/denisc/}
2430@item
2431@uref{http://www.amelek.gda.pl/avr/,,http://www.amelek.gda.pl/avr/}
2432@end itemize
2433
2434We @emph{strongly} recommend using binutils 2.13 or newer.
2435
2436The following error:
2437@smallexample
2438 Error: register required
2439@end smallexample
2440
2441indicates that you should upgrade to a newer version of the binutils.
2442
2443@html
2444<hr />
2445@end html
2446@heading @anchor{c4x}c4x
2447
2448Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal
2449Processors. These are used in embedded applications. There are no
2450standard Unix configurations.
2451@ifnothtml
2452@xref{TMS320C3x/C4x Options,, TMS320C3x/C4x Options, gcc, Using and
2453Porting the GNU Compiler Collection (GCC)},
2454@end ifnothtml
2455@ifhtml
2456See ``TMS320C3x/C4x Options'' in the main manual
2457@end ifhtml
2458for the list of supported MCU types.
2459
2460GCC can be configured as a cross compiler for both the C3x and C4x
2461architectures on the same system. Use @samp{configure --target=c4x
2462--enable-languages="c,c++"} to configure.
2463
2464
2465Further installation notes and other useful information about C4x tools
2466can also be obtained from:
2467
2468@itemize @bullet
2469@item
2470@uref{http://www.elec.canterbury.ac.nz/c4x/,,http://www.elec.canterbury.ac.nz/c4x/}
2471@end itemize
2472
2473@html
2474<hr />
2475@end html
2476@heading @anchor{cris}CRIS
2477
2478CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
2479series. These are used in embedded applications.
2480
2481@ifnothtml
2482@xref{CRIS Options,, CRIS Options, gcc, Using and Porting the GNU Compiler
2483Collection (GCC)},
2484@end ifnothtml
2485@ifhtml
2486See ``CRIS Options'' in the main manual
2487@end ifhtml
2488for a list of CRIS-specific options.
2489
2490There are a few different CRIS targets:
2491@table @code
2492@item cris-axis-aout
2493Old target. Includes a multilib for the @samp{elinux} a.out-based
2494target. No multilibs for newer architecture variants.
2495@item cris-axis-elf
2496Mainly for monolithic embedded systems. Includes a multilib for the
2497@samp{v10} core used in @samp{ETRAX 100 LX}.
2498@item cris-axis-linux-gnu
2499A GNU/Linux port for the CRIS architecture, currently targeting
2500@samp{ETRAX 100 LX} by default.
2501@end table
2502
2503For @code{cris-axis-aout} and @code{cris-axis-elf} you need binutils 2.11
2504or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
2505
2506Pre-packaged tools can be obtained from
2507@uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More
2508information about this platform is available at
2509@uref{http://developer.axis.com/}.
2510
2511@html
2512<hr />
2513@end html
2514@heading @anchor{dos}DOS
2515
3a327f56 2516Please have a look at the @uref{binaries.html,,binaries page}.
003757ed
MD
2517
2518You cannot install GCC by itself on MSDOS; it will not compile under
2519any MSDOS compiler except itself. You need to get the complete
2520compilation package DJGPP, which includes binaries as well as sources,
2521and includes all the necessary compilation tools and libraries.
2522
2523@html
2524<hr />
2525@end html
2526@heading @anchor{dsp16xx}dsp16xx
2527A port to the AT&T DSP1610 family of processors.
2528
2529@html
2530<hr />
2531@end html
1c1138ce 2532@heading @anchor{x-x-freebsd}*-*-freebsd*
003757ed
MD
2533
2534The version of binutils installed in @file{/usr/bin} probably works with
2535this release of GCC. However, on FreeBSD 4, bootstrapping against the
2536latest FSF binutils is known to improve overall testsuite results; and,
2537on FreeBSD/alpha, using binutils 2.14 or later is required to build libjava.
2538
2539Support for FreeBSD 1 was discontinued in GCC 3.2.
2540
2541Support for FreeBSD 2 will be discontinued after GCC 3.4. The
2542following was true for GCC 3.1 but the current status is unknown.
2543For FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
2544configuration support and files as shipped with GCC 2.95 are still in
2545place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
2546it is unknown which version of binutils was used (it is assumed that it
2547was the system copy in @file{/usr/bin}) and C++ EH failures were noted.
2548
2549For FreeBSD using the ELF file format: DWARF 2 debugging is now the
2550default for all CPU architectures. It had been the default on
2551FreeBSD/alpha since its inception. You may use @option{-gstabs} instead
2552of @option{-g}, if you really want the old debugging format. There are
2553no known issues with mixing object files and libraries with different
2554debugging formats. Otherwise, this release of GCC should now match more
2555of the configuration used in the stock FreeBSD configuration of GCC. In
2556particular, @option{--enable-threads} is now configured by default.
2557However, as a general user, do not attempt to replace the system
2558compiler with this release. Known to bootstrap and check with good
2559results on FreeBSD 4.9-STABLE and 5-CURRENT@. In the past, known to
2560bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2,
25614.3, 4.4, 4.5, 4.8-STABLE@.
2562
2563In principle, @option{--enable-threads} is now compatible with
2564@option{--enable-libgcj} on FreeBSD@. However, it has only been built
2565and tested on @samp{i386-*-freebsd[45]} and @samp{alpha-*-freebsd[45]}.
2566The static
2567library may be incorrectly built (symbols are missing at link time).
2568There is a rare timing-based startup hang (probably involves an
2569assumption about the thread library). Multi-threaded boehm-gc (required for
2570libjava) exposes severe threaded signal-handling bugs on FreeBSD before
25714.5-RELEASE@. Other CPU architectures
2572supported by FreeBSD will require additional configuration tuning in, at
2573the very least, both boehm-gc and libffi.
2574
2575Shared @file{libgcc_s.so} is now built and installed by default.
2576
2577@html
2578<hr />
2579@end html
2580@heading @anchor{h8300-hms}h8300-hms
2581Renesas H8/300 series of processors.
2582
3a327f56 2583Please have a look at the @uref{binaries.html,,binaries page}.
003757ed
MD
2584
2585The calling convention and structure layout has changed in release 2.6.
2586All code must be recompiled. The calling convention now passes the
2587first three arguments in function calls in registers. Structures are no
2588longer a multiple of 2 bytes.
2589
2590@html
2591<hr />
2592@end html
1c1138ce 2593@heading @anchor{hppa-hp-hpux}hppa*-hp-hpux*
003757ed
MD
2594Support for HP-UX version 9 and older was discontinued in GCC 3.4.
2595
2596We @emph{highly} recommend using gas/binutils 2.8 or newer on all hppa
2597platforms; you may encounter a variety of problems when using the HP
2598assembler.
2599
2600Specifically, @option{-g} does not work on HP-UX (since that system
2601uses a peculiar debugging format which GCC does not know about), unless you
2602use GAS and GDB and configure GCC with the
2603@uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
2604@option{--with-as=@dots{}} options.
2605
2606If you wish to use the pa-risc 2.0 architecture support with a 32-bit
2607runtime, you must use either the HP assembler, or gas/binutils 2.11
2608or newer.
2609
2610There are two default scheduling models for instructions. These are
2611PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
2612architecture specified for the target machine when configuring.
2613PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
2614the target is a @samp{hppa1*} machine.
2615
2616The PROCESSOR_8000 model is not well suited to older processors. Thus,
2617it is important to completely specify the machine architecture when
2618configuring if you want a model other than PROCESSOR_8000. The macro
2619TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
2620default scheduling model is desired.
2621
2622More specific information to @samp{hppa*-hp-hpux*} targets follows.
2623
2624@html
2625<hr />
2626@end html
1c1138ce 2627@heading @anchor{hppa-hp-hpux10}hppa*-hp-hpux10
003757ed
MD
2628
2629For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
2630@code{PHCO_19798} from HP@. HP has two sites which provide patches free of
2631charge:
2632
2633@itemize @bullet
2634@item
2635@html
2636<a href="http://us.itrc.hp.com/service/home/home.do">US, Canada, Asia-Pacific, and
2637Latin-America</a>
2638@end html
2639@ifnothtml
2640@uref{http://us.itrc.hp.com/service/home/home.do,,} US, Canada, Asia-Pacific,
2641and Latin-America.
2642@end ifnothtml
2643@item
2644@uref{http://europe.itrc.hp.com/service/home/home.do,,} Europe.
2645@end itemize
2646
2647The HP assembler on these systems has some problems. Most notably the
2648assembler inserts timestamps into each object file it creates, causing
2649the 3-stage comparison test to fail during a @samp{make bootstrap}.
2650You should be able to continue by saying @samp{make all} after getting
2651the failure from @samp{make bootstrap}.
2652
2653
2654@html
2655<hr />
2656@end html
1c1138ce 2657@heading @anchor{hppa-hp-hpux11}hppa*-hp-hpux11
003757ed
MD
2658
2659GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
2660be used to compile GCC 3.0 and up.
2661
2662Refer to @uref{binaries.html,,binaries} for information about obtaining
2663precompiled GCC binaries for HP-UX. Precompiled binaries must be obtained
2664to build the Ada language as it can't be bootstrapped using C. Ada is
2665only available for the 32-bit PA-RISC runtime. The libffi and libjava
2666haven't been ported to HP-UX and don't build.
2667
2668It is possible to build GCC 3.3 starting with the bundled HP compiler,
2669but the process requires several steps. GCC 3.3 can then be used to
2670build later versions. The fastjar program contains ISO C code and
2671can't be built with the HP bundled compiler. This problem can be
2672avoided by not building the Java language. For example, use the
2673@option{--enable-languages="c,c++,f77,objc"} option in your configure
2674command.
2675
2676Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The
2677bundled compiler supports only traditional C; you will need either HP's
2678unbundled compiler, or a binary distribution of GCC@.
2679
2680There are several possible approaches to building the distribution.
2681Binutils can be built first using the HP tools. Then, the GCC
2682distribution can be built. The second approach is to build GCC
2683first using the HP tools, then build binutils, then rebuild GCC.
2684There have been problems with various binary distributions, so it
2685is best not to start from a binary distribution.
2686
2687On 64-bit capable systems, there are two distinct targets. Different
2688installation prefixes must be used if both are to be installed on
2689the same system. The @samp{hppa[1-2]*-hp-hpux11*} target generates code
2690for the 32-bit PA-RISC runtime architecture and uses the HP linker.
2691The @samp{hppa64-hp-hpux11*} target generates 64-bit code for the
2692PA-RISC 2.0 architecture. The HP and GNU linkers are both supported
2693for this target.
2694
2695The script config.guess now selects the target type based on the compiler
2696detected during configuration. You must define @env{PATH} or @env{CC} so
2697that configure finds an appropriate compiler for the initial bootstrap.
2698When @env{CC} is used, the definition should contain the options that are
2699needed whenever @env{CC} is used.
2700
2701Specifically, options that determine the runtime architecture must be
2702in @env{CC} to correctly select the target for the build. It is also
2703convenient to place many other compiler options in @env{CC}. For example,
2704@env{CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"}
2705can be used to bootstrap the GCC 3.3 branch with the HP compiler in
270664-bit K&R/bundled mode. The @option{+DA2.0W} option will result in
2707the automatic selection of the @samp{hppa64-hp-hpux11*} target. The
2708macro definition table of cpp needs to be increased for a successful
2709build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to
2710be defined when building with the bundled compiler, or when using the
2711@option{-Ac} option. These defines aren't necessary with @option{-Ae}.
2712
2713It is best to explicitly configure the @samp{hppa64-hp-hpux11*} target
2714with the @option{--with-ld=@dots{}} option. This overrides the standard
2715search for ld. The two linkers supported on this target require different
2716commands. The default linker is determined during configuration. As a
2717result, it's not possible to switch linkers in the middle of a GCC build.
2718This has been been reported to sometimes occur in unified builds of
2719binutils and GCC.
2720
2721With GCC 3.0 through 3.2, you must use binutils 2.11 or above. As of
2722GCC 3.3, binutils 2.14 or later is required.
2723
2724Although the HP assembler can be used for an initial build, it shouldn't
2725be used with any languages other than C and perhaps Fortran due to its
2726many limitations. For example, it does not support weak symbols or alias
2727definitions. As a result, explicit template instantiations are required
2728when using C++. This makes it difficult if not impossible to build many
2729C++ applications. You can't generate debugging information when using
2730the HP assembler. Finally, @samp{make bootstrap} fails in the final
2731comparison of object modules due to the time stamps that it inserts into
2732the modules. The bootstrap can be continued from this point with
2733@samp{make all}.
2734
2735A recent linker patch must be installed for the correct operation of
2736GCC 3.3 and later. @code{PHSS_26559} and @code{PHSS_24304} are the
2737oldest linker patches that are known to work. They are for HP-UX
273811.00 and 11.11, respectively. @code{PHSS_24303}, the companion to
2739@code{PHSS_24304}, might be usable but it hasn't been tested. These
2740patches have been superseded. Consult the HP patch database to obtain
2741the currently recommended linker patch for your system.
2742
2743The patches are necessary for the support of weak symbols on the
274432-bit port, and for the running of initializers and finalizers. Weak
2745symbols are implemented using SOM secondary definition symbols. Prior
2746to HP-UX 11, there are bugs in the linker support for secondary symbols.
2747The patches correct a problem of linker core dumps creating shared
2748libraries containing secondary symbols, as well as various other
2749linking issues involving secondary symbols.
2750
2751GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
2752run initializers and finalizers on the 64-bit port. The 32-bit port
2753uses the linker @option{+init} and @option{+fini} options for the same
2754purpose. The patches correct various problems with the +init/+fini
2755options, including program core dumps. Binutils 2.14 corrects a
2756problem on the 64-bit port resulting from HP's non-standard use of
2757the .init and .fini sections for array initializers and finalizers.
2758
2759There are a number of issues to consider in selecting which linker to
2760use with the 64-bit port. The GNU 64-bit linker can only create dynamic
2761binaries. The @option{-static} option causes linking with archive
2762libraries but doesn't produce a truly static binary. Dynamic binaries
2763still require final binding by the dynamic loader to resolve a set of
2764dynamic-loader-defined symbols. The default behavior of the HP linker
2765is the same as the GNU linker. However, it can generate true 64-bit
2766static binaries using the @option{+compat} option.
2767
2768The HP 64-bit linker doesn't support linkonce semantics. As a
2769result, C++ programs have many more sections than they should.
2770
2771The GNU 64-bit linker has some issues with shared library support
2772and exceptions. As a result, we only support libgcc in archive
2773format. For similar reasons, dwarf2 unwind and exception support
2774are disabled. The GNU linker also has problems creating binaries
2775with @option{-static}. It doesn't provide stubs for internal
2776calls to global functions in shared libraries, so these calls
2777can't be overloaded.
2778
2779Thread support is not implemented in GCC 3.0 through 3.2, so the
2780@option{--enable-threads} configure option does not work. In 3.3
2781and later, POSIX threads are supported. The optional DCE thread
2782library is not supported.
2783
2784This port still is undergoing significant development.
2785
2786@html
2787<hr />
2788@end html
1c1138ce 2789@heading @anchor{i370-x-x}i370-*-*
003757ed
MD
2790This port is very preliminary and has many known bugs. We hope to
2791have a higher-quality port for this machine soon.
2792
2793@html
2794<hr />
2795@end html
1c1138ce 2796@heading @anchor{x-x-linux-gnu}*-*-linux-gnu
003757ed
MD
2797
2798Versions of libstdc++-v3 starting with 3.2.1 require bugfixes present
2799in glibc 2.2.5 and later. More information is available in the
2800libstdc++-v3 documentation.
2801
2802@html
2803<hr />
2804@end html
1c1138ce 2805@heading @anchor{ix86-x-linuxaout}i?86-*-linux*aout
003757ed
MD
2806Use this configuration to generate @file{a.out} binaries on Linux-based
2807GNU systems. This configuration is being superseded.
2808
2809@html
2810<hr />
2811@end html
1c1138ce 2812@heading @anchor{ix86-x-linux}i?86-*-linux*
003757ed
MD
2813
2814As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
2815See @uref{http://gcc.gnu.org/PR10877,,bug 10877} for more information.
2816
2817If you receive Signal 11 errors when building on GNU/Linux, then it is
2818possible you have a hardware problem. Further information on this can be
2819found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
2820
2821Some recent versions of GNU/Linux, such as Fedora Core 1, support
2822exec-shield-randomize. Turning this on interferes with precompiled
2823headers. If you need to use precompiled headers,
2824exec-shield-randomize can be turned off for the entire system by
2825editing @file{/etc/sysctl.conf} and adding a line:
2826@smallexample
2827kernel.exec-shield-randomize = 0
2828@end smallexample
2829You may then need to run @samp{sysctl -p}.
2830
2831This will be fixed in future releases of GCC.
2832
2833@html
2834<hr />
2835@end html
1c1138ce 2836@heading @anchor{ix86-x-sco32v5}i?86-*-sco3.2v5*
003757ed
MD
2837Use this for the SCO OpenServer Release 5 family of operating systems.
2838
2839Unlike earlier versions of GCC, the ability to generate COFF with this
2840target is no longer provided.
2841
2842Earlier versions of GCC emitted DWARF 1 when generating ELF to allow
2843the system debugger to be used. That support was too burdensome to
2844maintain. GCC now emits only DWARF 2 for this target. This means you
2845may use either the UDK debugger or GDB to debug programs built by this
2846version of GCC@.
2847
2848GCC is now only supported on releases 5.0.4 and later, and requires that
2849you install Support Level Supplement OSS646B or later, and Support Level
2850Supplement OSS631C or later. If you are using release 5.0.7 of
2851OpenServer, you must have at least the first maintenance pack installed
2852(this includes the relevant portions of OSS646). OSS646, also known as
2853the "Execution Environment Update", provides updated link editors and
2854assemblers, as well as updated standard C and math libraries. The C
2855startup modules are also updated to support the System V gABI draft, and
2856GCC relies on that behavior. OSS631 provides a collection of commonly
2857used open source libraries, some of which GCC depends on (such as GNU
2858gettext and zlib). SCO OpenServer Release 5.0.7 has all of this built
2859in by default, but OSS631C and later also apply to that release. Please
2860visit
2861@uref{ftp://ftp.sco.com/pub/openserver5,,ftp://ftp.sco.com/pub/openserver5}
2862for the latest versions of these (and other potentially useful)
2863supplements.
2864
2865Although there is support for using the native assembler, it is
2866recommended that you configure GCC to use the GNU assembler. You do
2867this by using the flags
2868@uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You should
2869use a modern version of GNU binutils. Version 2.13.2.1 was used for all
2870testing. In general, only the @option{--with-gnu-as} option is tested.
2871A modern bintuils (as well as a plethora of other development related
2872GNU utilities) can be found in Support Level Supplement OSS658A, the
2873"GNU Development Tools" package. See the SCO web and ftp sites for details.
2874That package also contains the currently "officially supported" version of
2875GCC, version 2.95.3. It is useful for bootstrapping this version.
2876
2877@html
2878<hr />
2879@end html
1c1138ce 2880@heading @anchor{ix86-x-udk}i?86-*-udk
003757ed
MD
2881
2882This target emulates the SCO Universal Development Kit and requires that
2883package be installed. (If it is installed, you will have a
2884@file{/udk/usr/ccs/bin/cc} file present.) It's very much like the
2885@samp{i?86-*-unixware7*} target
2886but is meant to be used when hosting on a system where UDK isn't the
2887default compiler such as OpenServer 5 or Unixware 2. This target will
2888generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
2889with the same warnings and caveats as the SCO UDK@.
2890
2891This target is a little tricky to build because we have to distinguish
2892it from the native tools (so it gets headers, startups, and libraries
2893from the right place) while making the tools not think we're actually
2894building a cross compiler. The easiest way to do this is with a configure
2895command like this:
2896
2897@smallexample
2898 CC=/udk/usr/ccs/bin/cc @var{/your/path/to}/gcc/configure \
2899 --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-
2900@end smallexample
2901
2902@emph{You should substitute @samp{i686} in the above command with the appropriate
2903processor for your host.}
2904
2905After the usual @samp{make bootstrap} and
2906@samp{make install}, you can then access the UDK-targeted GCC
2907tools by adding @command{udk-} before the commonly known name. For
2908example, to invoke the C compiler, you would use @command{udk-gcc}.
2909They will coexist peacefully with any native-target GCC tools you may
2910have installed.
2911
2912
2913@html
2914<hr />
2915@end html
1c1138ce 2916@heading @anchor{ia64-x-linux}ia64-*-linux
003757ed
MD
2917IA-64 processor (also known as IPF, or Itanium Processor Family)
2918running GNU/Linux.
2919
3a327f56
JS
2920If you are using the installed system libunwind library with
2921@option{--with-system-libunwind}, then you must use libunwind 0.98 or
2922later.
003757ed
MD
2923
2924None of the following versions of GCC has an ABI that is compatible
2925with any of the other versions in this list, with the exception that
2926Red Hat 2.96 and Trillian 000171 are compatible with each other:
29273.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
2928This primarily affects C++ programs and programs that create shared libraries.
2929GCC 3.1 or later is recommended for compiling linux, the kernel.
2930As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
2931more major ABI changes are expected.
2932
2933@html
2934<hr />
2935@end html
1c1138ce 2936@heading @anchor{ia64-x-hpux}ia64-*-hpux*
003757ed
MD
2937Building GCC on this target requires the GNU Assembler. The bundled HP
2938assembler will not work. To prevent GCC from using the wrong assembler,
2939the option @option{--with-gnu-as} may be necessary.
2940
2941The GCC libunwind library has not been ported to HPUX. This means that for
2942GCC versions 3.2.3 and earlier, @option{--enable-libunwind-exceptions}
2943is required to build GCC. For GCC 3.3 and later, this is the default.
3a327f56
JS
2944For gcc 3.4.3 and later, @option{--enable-libunwind-exceptions} is
2945removed and the system libunwind library will always be used.
003757ed
MD
2946
2947@html
2948<hr />
2949<!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
2950@end html
1c1138ce 2951@heading @anchor{x-ibm-aix}*-ibm-aix*
003757ed
MD
2952Support for AIX version 3 and older was discontinued in GCC 3.4.
2953
2954AIX Make frequently has problems with GCC makefiles. GNU Make 3.79.1 or
2955newer is recommended to build on this platform.
2956
2957To speed up the configuration phases of bootstrapping and installing GCC,
2958one may use GNU Bash instead of AIX @command{/bin/sh}, e.g.,
2959
2960@smallexample
2961 % CONFIG_SHELL=/opt/freeware/bin/bash
2962 % export CONFIG_SHELL
2963@end smallexample
2964
2965and then proceed as described in @uref{build.html,,the build instructions},
2966where we strongly recommend using GNU make and specifying an absolute path
2967to invoke @var{srcdir}/configure.
2968
2969Errors involving @code{alloca} when building GCC generally are due
2970to an incorrect definition of @code{CC} in the Makefile or mixing files
2971compiled with the native C compiler and GCC@. During the stage1 phase of
2972the build, the native AIX compiler @strong{must} be invoked as @command{cc}
2973(not @command{xlc}). Once @command{configure} has been informed of
2974@command{xlc}, one needs to use @samp{make distclean} to remove the
2975configure cache files and ensure that @env{CC} environment variable
2976does not provide a definition that will confuse @command{configure}.
2977If this error occurs during stage2 or later, then the problem most likely
2978is the version of Make (see above).
2979
2980The native @command{as} and @command{ld} are recommended for bootstrapping
2981on AIX 4 and required for bootstrapping on AIX 5L. The GNU Assembler
2982reports that it supports WEAK symbols on AIX 4, which causes GCC to try to
2983utilize weak symbol functionality although it is not supported. The GNU
2984Assembler and Linker do not support AIX 5L sufficiently to bootstrap GCC.
2985The native AIX tools do interoperate with GCC@.
2986
2987Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
2988APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
2989fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
2990referenced as APAR IY53606 (AIX 5.2) or a APAR IY54774 (AIX 5.1)
2991
2992@samp{libstdc++} in GCC 3.4 increments the major version number of the
2993shared object and GCC installation places the @file{libstdc++.a}
2994shared library in a common location which will overwrite the and GCC
29953.3 version of the shared library. Applications either need to be
2996re-linked against the new shared library or the GCC 3.1 and GCC 3.3
2997versions of the @samp{libstdc++} shared object needs to be available
2998to the AIX runtime loader. The GCC 3.1 @samp{libstdc++.so.4}, if
2999present, and GCC 3.3 @samp{libstdc++.so.5} shared objects can be
3000installed for runtime dynamic loading using the following steps to set
3001the @samp{F_LOADONLY} flag in the shared object for @emph{each}
3002multilib @file{libstdc++.a} installed:
3003
3004Extract the shared objects from the currently installed
3005@file{libstdc++.a} archive:
3006@smallexample
3007 % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
3008@end smallexample
3009
3010Enable the @samp{F_LOADONLY} flag so that the shared object will be
3011available for runtime dynamic loading, but not linking:
3012@smallexample
3013 % strip -e libstdc++.so.4 libstdc++.so.5
3014@end smallexample
3015
3016Archive the runtime-only shared object in the GCC 3.4
3017@file{libstdc++.a} archive:
3018@smallexample
3019 % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
3020@end smallexample
3021
3022Linking executables and shared libraries may produce warnings of
3023duplicate symbols. The assembly files generated by GCC for AIX always
3024have included multiple symbol definitions for certain global variable
3025and function declarations in the original program. The warnings should
3026not prevent the linker from producing a correct library or runnable
3027executable.
3028
3029AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and
303064-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
3031to parse archive libraries did not handle the new format correctly.
3032These routines are used by GCC and result in error messages during
3033linking such as ``not a COFF file''. The version of the routines shipped
3034with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
3035option of the archive command may be used to create archives of 32-bit
3036objects using the original ``small format''. A correct version of the
3037routines is shipped with AIX 4.3.2 and above.
3038
3039Some versions of the AIX binder (linker) can fail with a relocation
3040overflow severe error when the @option{-bbigtoc} option is used to link
3041GCC-produced object files into an executable that overflows the TOC@. A fix
3042for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
3043available from IBM Customer Support and from its
3044@uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3045website as PTF U455193.
3046
3047The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
3048with a segmentation fault when invoked by any version of GCC@. A fix for
3049APAR IX87327 is available from IBM Customer Support and from its
3050@uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3051website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
3052
3053The initial assembler shipped with AIX 4.3.0 generates incorrect object
3054files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
3055TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
3056@uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
3057website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
3058
3059AIX provides National Language Support (NLS)@. Compilers and assemblers
3060use NLS to support locale-specific representations of various data
3061formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for
3062separating decimal fractions). There have been problems reported where
3063GCC does not produce the same floating-point formats that the assembler
3064expects. If one encounters this problem, set the @env{LANG}
3065environment variable to @samp{C} or @samp{En_US}.
3066
3067By default, GCC for AIX 4.1 and above produces code that can be used on
3068both Power or PowerPC processors.
3069
3070A default can be specified with the @option{-mcpu=@var{cpu_type}}
3071switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
3072
3073@html
3074<hr />
3075@end html
1c1138ce 3076@heading @anchor{ip2k-x-elf}ip2k-*-elf
003757ed
MD
3077Ubicom IP2022 micro controller.
3078This configuration is intended for embedded systems.
3079There are no standard Unix configurations.
3080
3081Use @samp{configure --target=ip2k-elf --enable-languages=c} to configure GCC@.
3082
3083@html
3084<hr />
3085@end html
1c1138ce 3086@heading @anchor{iq2000-x-elf}iq2000-*-elf
003757ed
MD
3087Vitesse IQ2000 processors. These are used in embedded
3088applications. There are no standard Unix configurations.
3089
3090@html
3091<hr />
3092@end html
1c1138ce 3093@heading @anchor{m32r-x-elf}m32r-*-elf
003757ed
MD
3094Renesas M32R processor.
3095This configuration is intended for embedded systems.
3096
3097@html
3098<hr />
3099@end html
3100@heading @anchor{m6811-elf}m6811-elf
3101Motorola 68HC11 family micro controllers. These are used in embedded
3102applications. There are no standard Unix configurations.
3103
3104@html
3105<hr />
3106@end html
3107@heading @anchor{m6812-elf}m6812-elf
3108Motorola 68HC12 family micro controllers. These are used in embedded
3109applications. There are no standard Unix configurations.
3110
3111@html
3112<hr />
3113@end html
3114@heading @anchor{m68k-hp-hpux}m68k-hp-hpux
3115HP 9000 series 300 or 400 running HP-UX@. HP-UX version 8.0 has a bug in
3116the assembler that prevents compilation of GCC@. This
3117bug manifests itself during the first stage of compilation, while
3118building @file{libgcc2.a}:
3119
3120@smallexample
3121_floatdisf
3122cc1: warning: `-g' option not supported on this version of GCC
3123cc1: warning: `-g1' option not supported on this version of GCC
3124./xgcc: Internal compiler error: program as got fatal signal 11
3125@end smallexample
3126
3127A patched version of the assembler is available as the file
3128@uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you
3129have HP software support, the patch can also be obtained directly from
3130HP, as described in the following note:
3131
3132@quotation
3133This is the patched assembler, to patch SR#1653-010439, where the
3134assembler aborts on floating point constants.
3135
3136The bug is not really in the assembler, but in the shared library
3137version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is
3138SR#4701-078451. Anyway, the attached assembler uses the archive
3139library version of ``cvtnum(3c)'' and thus does not exhibit the bug.
3140@end quotation
3141
3142This patch is also known as PHCO_4484.
3143
3144In addition gdb does not understand that native HP-UX format, so
3145you must use gas if you wish to use gdb.
3146
3147On HP-UX version 8.05, but not on 8.07 or more recent versions, the
3148@command{fixproto} shell script triggers a bug in the system shell. If you
3149encounter this problem, upgrade your operating system or use BASH (the
3150GNU shell) to run @command{fixproto}. This bug will cause the fixproto
3151program to report an error of the form:
3152
3153@smallexample
3154./fixproto: sh internal 1K buffer overflow
3155@end smallexample
3156
3157To fix this, you can also change the first line of the fixproto script
3158to look like:
3159
3160@smallexample
3161#!/bin/ksh
3162@end smallexample
3163
3164@html
3165<hr />
3166@end html
1c1138ce 3167@heading @anchor{mips-x-x}mips-*-*
003757ed
MD
3168If on a MIPS system you get an error message saying ``does not have gp
3169sections for all it's [sic] sectons [sic]'', don't worry about it. This
3170happens whenever you use GAS with the MIPS linker, but there is not
3171really anything wrong, and it is okay to use the output file. You can
3172stop such warnings by installing the GNU linker.
3173
3174It would be nice to extend GAS to produce the gp tables, but they are
3175optional, and there should not be a warning about their absence.
3176
3177The libstdc++ atomic locking routines for MIPS targets requires MIPS II
3178and later. A patch went in just after the GCC 3.3 release to
3179make @samp{mips*-*-*} use the generic implementation instead. You can also
3180configure for @samp{mipsel-elf} as a workaround. The
3181@samp{mips*-*-linux*} target continues to use the MIPS II routines. More
3182work on this is expected in future releases.
3183
3184Cross-compilers for the Mips as target using the Mips assembler
3185currently do not work, because the auxiliary programs
3186@file{mips-tdump.c} and @file{mips-tfile.c} can't be compiled on
3187anything but a Mips. It does work to cross compile for a Mips
3188if you use the GNU assembler and linker.
3189
3190@html
3191<hr />
3192@end html
3193@heading @anchor{mips-sgi-irix5}mips-sgi-irix5
3194
3195In order to compile GCC on an SGI running IRIX 5, the @samp{compiler_dev.hdr}
3196subsystem must be installed from the IDO CD-ROM supplied by SGI@.
3197It is also available for download from
3198@uref{ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist}.
3199
3200If you use the MIPS C compiler to bootstrap, it may be necessary
3201to increase its table size for switch statements with the
3202@option{-Wf,-XNg1500} option. If you use the @option{-O2}
3203optimization option, you also need to use @option{-Olimit 3000}.
3204
3205To enable debugging under IRIX 5, you must use GNU binutils 2.15 or
3206later, and use the @option{--with-gnu-as} and @option{--with-gnu-ld}
3207@command{configure} options when configuring GCC@. You need to use GNU
3208@command{ar} and @command{nm}, also distributed with GNU binutils.
3209
3a327f56
JS
3210Some users have reported that @command{/bin/sh} will hang during bootstrap.
3211This problem can be avoided by running the commands:
3212
3213@smallexample
3214 % CONFIG_SHELL=/bin/ksh
3215 % export CONFIG_SHELL
3216@end smallexample
3217
3218before starting the build.
3219
003757ed
MD
3220@html
3221<hr />
3222@end html
3223@heading @anchor{mips-sgi-irix6}mips-sgi-irix6
3224
3225If you are using SGI's MIPSpro @command{cc} as your bootstrap compiler, you must
3226ensure that the N32 ABI is in use. To test this, compile a simple C
3227file with @command{cc} and then run @command{file} on the
3228resulting object file. The output should look like:
3229
3230@smallexample
3231test.o: ELF N32 MSB @dots{}
3232@end smallexample
3233
3234If you see:
3235
3236@smallexample
3237test.o: ELF 32-bit MSB @dots{}
3238@end smallexample
3239
3240or
3241
3242@smallexample
3243test.o: ELF 64-bit MSB @dots{}
3244@end smallexample
3245
3246then your version of @command{cc} uses the O32 or N64 ABI by default. You
3247should set the environment variable @env{CC} to @samp{cc -n32}
3248before configuring GCC@. SGI's MIPSpro 7.2 assembler may misassemble
3249parts of the compiler, causing bootstrap failures. MIPSpro 7.3 is
3250known to work. MIPSpro C 7.4 may cause bootstrap failures, too, due
3251to a bug when inlining @code{memcmp}. Either add @code{-U__INLINE_INTRINSICS}
3252to the @env{CC} environment variable as a workaround or upgrade to
3253MIPSpro C 7.4.1m.
3254
3255If you want the resulting @command{gcc} to run on old 32-bit systems
3256with the MIPS R4400 CPU, you need to ensure that only code for the @samp{mips3}
3257instruction set architecture (ISA) is generated. While GCC 3.x does
3258this correctly, both GCC 2.95 and SGI's MIPSpro @command{cc} may change
3259the ISA depending on the machine where GCC is built. Using one of them
3260as the bootstrap compiler may result in @samp{mips4} code, which won't run at
3261all on @samp{mips3}-only systems. For the test program above, you should see:
3262
3263@smallexample
3264test.o: ELF N32 MSB mips-3 @dots{}
3265@end smallexample
3266
3267If you get:
3268
3269@smallexample
3270test.o: ELF N32 MSB mips-4 @dots{}
3271@end smallexample
3272
3273instead, you should set the environment variable @env{CC} to @samp{cc
3274-n32 -mips3} or @samp{gcc -mips3} respectively before configuring GCC@.
3275
3276GCC on IRIX 6 is usually built to support the N32, O32 and N64 ABIs. If
3277you build GCC on a system that doesn't have the N64 libraries installed
3278or cannot run 64-bit binaries,
3279you need to configure with @option{--disable-multilib} so GCC doesn't
3280try to use them. This will disable building the O32 libraries, too.
3281Look for @file{/usr/lib64/libc.so.1} to see if you
3282have the 64-bit libraries installed.
3283
3284To enable debugging for the O32 ABI, you must use GNU @command{as} from
3285GNU binutils 2.15 or later. You may also use GNU @command{ld}, but
3286this is not required and currently causes some problems with Ada.
3287
3288The @option{--enable-threads} option doesn't currently work, a patch is
3289in preparation for a future release. The @option{--enable-libgcj}
3290option is disabled by default: IRIX 6 uses a very low default limit
3291(20480) for the command line length. Although @command{libtool} contains a
3292workaround for this problem, at least the N64 @samp{libgcj} is known not
3293to build despite this, running into an internal error of the native
3294@command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
3295its maximum of 262144 bytes. If you have root access, you can use the
3296@command{systune} command to do this.
3297
3298See @uref{http://freeware.sgi.com/} for more
3299information about using GCC on IRIX platforms.
3300
3301@html
3302<hr />
3303@end html
1c1138ce 3304@heading @anchor{powerpc-x-x}powerpc-*-*
003757ed
MD
3305
3306You can specify a default version for the @option{-mcpu=@var{cpu_type}}
3307switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
3308
3309@html
3310<hr />
3311@end html
1c1138ce 3312@heading @anchor{powerpc-x-darwin}powerpc-*-darwin*
003757ed
MD
3313PowerPC running Darwin (Mac OS X kernel).
3314
3315Pre-installed versions of Mac OS X may not include any developer tools,
3316meaning that you will not be able to build GCC from source. Tool
3317binaries are available at
1c1138ce 3318@uref{http://developer.apple.com/darwin/projects/compiler/} (free
003757ed
MD
3319registration required).
3320
3321The default stack limit of 512K is too small, which may cause compiles
3322to fail with 'Bus error'. Set the stack larger, for instance
3323by doing @samp{limit stack 800}. It's a good idea to use the GNU
3324preprocessor instead of Apple's @file{cpp-precomp} during the first stage of
3325bootstrapping; this is automatic when doing @samp{make bootstrap}, but
3326to do it from the toplevel objdir you will need to say @samp{make
3327CC='cc -no-cpp-precomp' bootstrap}.
3328
3329The version of GCC shipped by Apple typically includes a number of
3330extensions not available in a standard GCC release. These extensions
3331are generally specific to Mac programming.
3332
3333@html
3334<hr />
3335@end html
1c1138ce 3336@heading @anchor{powerpc-x-elf}powerpc-*-elf, powerpc-*-sysv4
003757ed
MD
3337PowerPC system in big endian mode, running System V.4.
3338
3339@html
3340<hr />
3341@end html
1c1138ce 3342@heading @anchor{powerpc-x-linux-gnu}powerpc*-*-linux-gnu*
003757ed
MD
3343
3344You will need
1c1138ce 3345@uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.15}
003757ed
MD
3346or newer for a working GCC@.
3347
3348@html
3349<hr />
3350@end html
1c1138ce 3351@heading @anchor{powerpc-x-netbsd}powerpc-*-netbsd*
003757ed
MD
3352PowerPC system in big endian mode running NetBSD@. To build the
3353documentation you will need Texinfo version 4.2 (NetBSD 1.5.1 included
3354Texinfo version 3.12).
3355
3356@html
3357<hr />
3358@end html
1c1138ce 3359@heading @anchor{powerpc-x-eabisim}powerpc-*-eabisim
003757ed
MD
3360Embedded PowerPC system in big endian mode for use in running under the
3361PSIM simulator.
3362
3363@html
3364<hr />
3365@end html
1c1138ce 3366@heading @anchor{powerpc-x-eabi}powerpc-*-eabi
003757ed
MD
3367Embedded PowerPC system in big endian mode.
3368
3369@html
3370<hr />
3371@end html
1c1138ce 3372@heading @anchor{powerpcle-x-elf}powerpcle-*-elf, powerpcle-*-sysv4
003757ed
MD
3373PowerPC system in little endian mode, running System V.4.
3374
3375@html
3376<hr />
3377@end html
1c1138ce 3378@heading @anchor{powerpcle-x-eabisim}powerpcle-*-eabisim
003757ed
MD
3379Embedded PowerPC system in little endian mode for use in running under
3380the PSIM simulator.
3381
3382@html
3383<hr />
3384@end html
1c1138ce 3385@heading @anchor{powerpcle-x-eabi}powerpcle-*-eabi
003757ed
MD
3386Embedded PowerPC system in little endian mode.
3387
3388@html
3389<hr />
3390@end html
1c1138ce 3391@heading @anchor{s390-x-linux}s390-*-linux*
003757ed
MD
3392S/390 system running GNU/Linux for S/390@.
3393
3394@html
3395<hr />
3396@end html
1c1138ce 3397@heading @anchor{s390x-x-linux}s390x-*-linux*
003757ed
MD
3398zSeries system (64-bit) running GNU/Linux for zSeries@.
3399
3400@html
3401<hr />
3402@end html
1c1138ce 3403@heading @anchor{s390x-ibm-tpf}s390x-ibm-tpf*
003757ed
MD
3404zSeries system (64-bit) running TPF. This platform is
3405supported as cross-compilation target only.
3406
3407@html
3408<hr />
3409@end html
3410@c Please use Solaris 2 to refer to all release of Solaris, starting
3411@c with 2.0 until 2.6, 7, 8, etc. Solaris 1 was a marketing name for
3412@c SunOS 4 releases which we don't use to avoid confusion. Solaris
3413@c alone is too unspecific and must be avoided.
1c1138ce 3414@heading @anchor{x-x-solaris2}*-*-solaris2*
003757ed
MD
3415
3416Sun does not ship a C compiler with Solaris 2. To bootstrap and install
3a327f56 3417GCC you first have to install a pre-built compiler, see the
003757ed
MD
3418@uref{binaries.html,,binaries page} for details.
3419
3420The Solaris 2 @command{/bin/sh} will often fail to configure
3421@file{libstdc++-v3}, @file{boehm-gc} or @file{libjava}. We therefore
3422recommend to use the following sequence of commands to bootstrap and
3423install GCC:
3424
3425@smallexample
3426 % CONFIG_SHELL=/bin/ksh
3427 % export CONFIG_SHELL
3428@end smallexample
3429
3a327f56
JS
3430and then proceed as described in @uref{build.html,,the build instructions}.
3431In addition we strongly recommend specifying an absolute path to invoke
3432@var{srcdir}/configure.
003757ed
MD
3433
3434Solaris 2 comes with a number of optional OS packages. Some of these
3435are needed to use GCC fully, namely @code{SUNWarc},
3436@code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
3437@code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all
3438optional packages when installing Solaris 2, you will need to verify that
3439the packages that GCC needs are installed.
3440
3441To check whether an optional package is installed, use
3442the @command{pkginfo} command. To add an optional package, use the
3443@command{pkgadd} command. For further details, see the Solaris 2
3444documentation.
3445
3446Trying to use the linker and other tools in
3447@file{/usr/ucb} to install GCC has been observed to cause trouble.
3448For example, the linker may hang indefinitely. The fix is to remove
3449@file{/usr/ucb} from your @env{PATH}.
3450
3451The build process works more smoothly with the legacy Sun tools so, if you
3452have @file{/usr/xpg4/bin} in your @env{PATH}, we recommend that you place
3453@file{/usr/bin} before @file{/usr/xpg4/bin} for the duration of the build.
3454
3455All releases of GNU binutils prior to 2.11.2 have known bugs on this
3a327f56
JS
3456platform. We recommend the use of GNU binutils 2.11.2 or later, or the
3457vendor tools (Sun @command{as}, Sun @command{ld}). Note that your mileage
3458may vary if you use a combination of the GNU tools and the Sun tools: while
3459the combination GNU @command{as} + Sun @command{ld} should reasonably work,
3460the reverse combination Sun @command{as} + GNU @command{ld} is known to
3461cause memory corruption at runtime in some cases for C++ programs.
3462
3463The stock GNU binutils 2.15 release is broken on this platform because of a
3464single bug. It has been fixed on the 2.15 branch in the CVS repository.
3465You can obtain a working version by checking out the binutils-2_15-branch
3466from the CVS repository or applying the patch
3467@uref{http://sources.redhat.com/ml/binutils-cvs/2004-09/msg00036.html} to the
3468release.
003757ed
MD
3469
3470Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3471newer: @command{g++} will complain that types are missing. These headers assume
3472that omitting the type means @code{int}; this assumption worked for C89 but
3473is wrong for C++, and is now wrong for C99 also.
3474
3475@command{g++} accepts such (invalid) constructs with the option
3476@option{-fpermissive}; it
3477will assume that any missing type is @code{int} (as defined by C89).
3478
3479There are patches for Solaris 2.6 (105633-56 or newer for SPARC,
3480106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC,
3481108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
3482108653-22 for Intel) that fix this bug.
3483
3a327f56
JS
3484Sun bug 4927647 sometimes causes random spurious testsuite failures
3485related to missing diagnostic output. This bug doesn't affect GCC
3486itself, rather it is a kernel bug triggered by the @command{expect}
3487program which is used only by the GCC testsuite driver. When the bug
3488causes the @command{expect} program to miss anticipated output, extra
3489testsuite failures appear.
3490
3491There are patches for Solaris 8 (117350-12 or newer for SPARC,
3492117351-12 or newer for Intel) and Solaris 9 (117171-11 or newer for
3493SPARC, 117172-11 or newer for Intel) that address this problem.
3494
003757ed
MD
3495@html
3496<hr />
3497@end html
1c1138ce 3498@heading @anchor{sparc-sun-solaris2}sparc-sun-solaris2*
003757ed
MD
3499
3500When GCC is configured to use binutils 2.11.2 or later the binaries
3501produced are smaller than the ones produced using Sun's native tools;
3502this difference is quite significant for binaries containing debugging
3503information.
3504
3505Sun @command{as} 4.x is broken in that it cannot cope with long symbol names.
3506A typical error message might look similar to the following:
3507
3508@smallexample
3509/usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error:
3510 can't compute value of an expression involving an external symbol.
3511@end smallexample
3512
3513This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris
35142.6 and has been fixed in later (5.x) versions of the assembler,
3515starting with Solaris 7.
3516
3517Starting with Solaris 7, the operating system is capable of executing
351864-bit SPARC V9 binaries. GCC 3.1 and later properly supports
3519this; the @option{-m64} option enables 64-bit code generation.