OpenCores
URL https://opencores.org/ocsvn/openrisc/openrisc/trunk

Subversion Repositories openrisc

[/] [openrisc/] [trunk/] [gnu-old/] [gcc-4.2.2/] [gcc/] [doc/] [gccinstall.info] - Blame information for rev 154

Go to most recent revision | Details | Compare with Previous | View Log

Line No. Rev Author Line
1 38 julius
This is doc/gccinstall.info, produced by makeinfo version 4.8 from
2
/scratch/mitchell/gcc-releases/gcc-4.2.2/gcc-4.2.2/gcc/doc/install.texi.
3
 
4
   Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
5
1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006 Free Software
6
Foundation, Inc.
7
 
8
   Permission is granted to copy, distribute and/or modify this document
9
under the terms of the GNU Free Documentation License, Version 1.2 or
10
any later version published by the Free Software Foundation; with no
11
Invariant Sections, the Front-Cover texts being (a) (see below), and
12
with the Back-Cover Texts being (b) (see below).  A copy of the license
13
is included in the section entitled "GNU Free Documentation License".
14
 
15
   (a) The FSF's Front-Cover Text is:
16
 
17
   A GNU Manual
18
 
19
   (b) The FSF's Back-Cover Text is:
20
 
21
   You have freedom to copy and modify this GNU Manual, like GNU
22
software.  Copies published by the Free Software Foundation raise
23
funds for GNU development.
24
 
25
   Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
26
1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006 Free Software
27
Foundation, Inc.
28
 
29
   Permission is granted to copy, distribute and/or modify this document
30
under the terms of the GNU Free Documentation License, Version 1.2 or
31
any later version published by the Free Software Foundation; with no
32
Invariant Sections, the Front-Cover texts being (a) (see below), and
33
with the Back-Cover Texts being (b) (see below).  A copy of the license
34
is included in the section entitled "GNU Free Documentation License".
35
 
36
   (a) The FSF's Front-Cover Text is:
37
 
38
   A GNU Manual
39
 
40
   (b) The FSF's Back-Cover Text is:
41
 
42
   You have freedom to copy and modify this GNU Manual, like GNU
43
software.  Copies published by the Free Software Foundation raise
44
funds for GNU development.
45
 
46
INFO-DIR-SECTION Software development
47
START-INFO-DIR-ENTRY
48
* gccinstall: (gccinstall).    Installing the GNU Compiler Collection.
49
END-INFO-DIR-ENTRY
50
 
51

52
File: gccinstall.info,  Node: Top,  Up: (dir)
53
 
54
* Menu:
55
 
56
* Installing GCC::  This document describes the generic installation
57
                    procedure for GCC as well as detailing some target
58
                    specific installation instructions.
59
 
60
* Specific::        Host/target specific installation notes for GCC.
61
* Binaries::        Where to get pre-compiled binaries.
62
 
63
* Old::             Old installation documentation.
64
 
65
* GNU Free Documentation License:: How you can copy and share this manual.
66
* Concept Index::   This index has two entries.
67
 
68

69
File: gccinstall.info,  Node: Installing GCC,  Next: Binaries,  Up: Top
70
 
71
1 Installing GCC
72
****************
73
 
74
   The latest version of this document is always available at
75
http://gcc.gnu.org/install/.
76
 
77
   This document describes the generic installation procedure for GCC
78
as well as detailing some target specific installation instructions.
79
 
80
   GCC includes several components that previously were separate
81
distributions with their own installation instructions.  This document
82
supersedes all package specific installation instructions.
83
 
84
   _Before_ starting the build/install procedure please check the *Note
85
host/target specific installation notes: Specific.  We recommend you
86
browse the entire generic installation instructions before you proceed.
87
 
88
   Lists of successful builds for released versions of GCC are
89
available at `http://gcc.gnu.org/buildstat.html'.  These lists are
90
updated as new information becomes available.
91
 
92
   The installation procedure itself is broken into five steps.
93
 
94
* Menu:
95
 
96
* Prerequisites::
97
* Downloading the source::
98
* Configuration::
99
* Building::
100
* Testing:: (optional)
101
* Final install::
102
 
103
   Please note that GCC does not support `make uninstall' and probably
104
won't do so in the near future as this would open a can of worms.
105
Instead, we suggest that you install GCC into a directory of its own
106
and simply remove that directory when you do not need that specific
107
version of GCC any longer, and, if shared libraries are installed there
108
as well, no more binaries exist that use them.
109
 
110

111
File: gccinstall.info,  Node: Prerequisites,  Next: Downloading the source,  Up: Installing GCC
112
 
113
2 Prerequisites
114
***************
115
 
116
   GCC requires that various tools and packages be available for use in
117
the build procedure.  Modifying GCC sources requires additional tools
118
described below.
119
 
120
Tools/packages necessary for building GCC
121
=========================================
122
 
123
ISO C90 compiler
124
     Necessary to bootstrap GCC, although versions of GCC prior to 3.4
125
     also allow bootstrapping with a traditional (K&R) C compiler.
126
 
127
     To build all languages in a cross-compiler or other configuration
128
     where 3-stage bootstrap is not performed, you need to start with
129
     an existing GCC binary (version 2.95 or later) because source code
130
     for language frontends other than C might use GCC extensions.
131
 
132
GNAT
133
     In order to build the Ada compiler (GNAT) you must already have
134
     GNAT installed because portions of the Ada frontend are written in
135
     Ada (with GNAT extensions.)  Refer to the Ada installation
136
     instructions for more specific information.
137
 
138
A "working" POSIX compatible shell, or GNU bash
139
     Necessary when running `configure' because some `/bin/sh' shells
140
     have bugs and may crash when configuring the target libraries.  In
141
     other cases, `/bin/sh' or `ksh' have disastrous corner-case
142
     performance problems.  This can cause target `configure' runs to
143
     literally take days to complete in some cases.
144
 
145
     So on some platforms `/bin/ksh' is sufficient, on others it isn't.
146
     See the host/target specific instructions for your platform, or
147
     use `bash' to be sure.  Then set `CONFIG_SHELL' in your
148
     environment to your "good" shell prior to running
149
     `configure'/`make'.
150
 
151
     `zsh' is not a fully compliant POSIX shell and will not work when
152
     configuring GCC.
153
 
154
GNU binutils
155
     Necessary in some circumstances, optional in others.  See the
156
     host/target specific instructions for your platform for the exact
157
     requirements.
158
 
159
gzip version 1.2.4 (or later) or
160
bzip2 version 1.0.2 (or later)
161
     Necessary to uncompress GCC `tar' files when source code is
162
     obtained via FTP mirror sites.
163
 
164
GNU make version 3.79.1 (or later)
165
     You must have GNU make installed to build GCC.
166
 
167
GNU tar version 1.14 (or later)
168
     Necessary (only on some platforms) to untar the source code.  Many
169
     systems' `tar' programs will also work, only try GNU `tar' if you
170
     have problems.
171
 
172
GNU Multiple Precision Library (GMP) version 4.1 (or later)
173
     Necessary to build the Fortran frontend.  If you do not have it
174
     installed in your library search path, you will have to configure
175
     with the `--with-gmp' configure option.  See also `--with-gmp-lib'
176
     and `--with-gmp-include'.
177
 
178
MPFR Library version 2.2.1 (or later)
179
     Necessary to build the Fortran frontend.  It can be downloaded from
180
     `http://www.mpfr.org/'.  The version of MPFR that is bundled with
181
     GMP 4.1.x contains numerous bugs.  Although GNU Fortran will appear
182
     to function with the buggy versions of MPFR, there are a few GNU
183
     Fortran bugs that will not be fixed when using this version.  It
184
     is strongly recommended to upgrade to the recommended version of
185
     MPFR.
186
 
187
     The `--with-mpfr' configure option should be used if your MPFR
188
     Library is not installed in your default library search path.  See
189
     also `--with-mpfr-lib' and `--with-mpfr-include'.
190
 
191
`jar', or InfoZIP (`zip' and `unzip')
192
     Necessary to build libgcj, the GCJ runtime.
193
 
194
 
195
Tools/packages necessary for modifying GCC
196
==========================================
197
 
198
autoconf versions 2.13 and 2.59
199
GNU m4 version 1.4 (or later)
200
     Necessary when modifying `configure.ac', `aclocal.m4', etc.  to
201
     regenerate `configure' and `config.in' files.  Most directories
202
     require autoconf 2.59 (exactly), but the toplevel still requires
203
     autoconf 2.13 (exactly).
204
 
205
automake version 1.9.6
206
     Necessary when modifying a `Makefile.am' file to regenerate its
207
     associated `Makefile.in'.
208
 
209
     Much of GCC does not use automake, so directly edit the
210
     `Makefile.in' file.  Specifically this applies to the `gcc',
211
     `intl', `libcpp', `libiberty', `libobjc' directories as well as
212
     any of their subdirectories.
213
 
214
     For directories that use automake, GCC requires the latest release
215
     in the 1.9.x series, which is currently 1.9.6.  When regenerating
216
     a directory to a newer version, please update all the directories
217
     using an older 1.9.x to the latest released version.
218
 
219
gettext version 0.14.5 (or later)
220
     Needed to regenerate `gcc.pot'.
221
 
222
gperf version 2.7.2 (or later)
223
     Necessary when modifying `gperf' input files, e.g.
224
     `gcc/cp/cfns.gperf' to regenerate its associated header file, e.g.
225
     `gcc/cp/cfns.h'.
226
 
227
DejaGnu 1.4.4
228
Expect
229
Tcl
230
     Necessary to run the GCC testsuite; see the section on testing for
231
     details.
232
 
233
autogen version 5.5.4 (or later) and
234
guile version 1.4.1 (or later)
235
     Necessary to regenerate `fixinc/fixincl.x' from
236
     `fixinc/inclhack.def' and `fixinc/*.tpl'.
237
 
238
     Necessary to run `make check' for `fixinc'.
239
 
240
     Necessary to regenerate the top level `Makefile.in' file from
241
     `Makefile.tpl' and `Makefile.def'.
242
 
243
GNU Bison version 1.28 (or later)
244
     Berkeley `yacc' (`byacc') is also reported to work other than for
245
     GCJ.
246
 
247
     Necessary when modifying `*.y' files.
248
 
249
     Necessary to build GCC during development because the generated
250
     output files are not included in the SVN repository.  They are
251
     included in releases.
252
 
253
Flex version 2.5.4 (or later)
254
     Necessary when modifying `*.l' files.
255
 
256
     Necessary to build GCC during development because the generated
257
     output files are not included in the SVN repository.  They are
258
     included in releases.
259
 
260
Texinfo version 4.4 (or later)
261
     Necessary for running `makeinfo' when modifying `*.texi' files to
262
     test your changes.
263
 
264
     Necessary for running `make dvi' or `make pdf' to create printable
265
     documentation in DVI or PDF format.  Texinfo version 4.8 or later
266
     is required for `make pdf'.
267
 
268
     Necessary to build GCC documentation during development because the
269
     generated output files are not included in the SVN repository.
270
     They are included in releases.
271
 
272
TeX (any working version)
273
     Necessary for running `texi2dvi' and `texi2pdf', which are used
274
     when running `make dvi' or `make pdf' to create DVI or PDF files,
275
     respectively.
276
 
277
SVN (any version)
278
SSH (any version)
279
     Necessary to access the SVN repository.  Public releases and weekly
280
     snapshots of the development sources are also available via FTP.
281
 
282
Perl version 5.6.1 (or later)
283
     Necessary when regenerating `Makefile' dependencies in libiberty.
284
     Necessary when regenerating `libiberty/functions.texi'.  Necessary
285
     when generating manpages from Texinfo manuals.  Necessary when
286
     targetting Darwin, building libstdc++, and not using
287
     `--disable-symvers'.  Used by various scripts to generate some
288
     files included in SVN (mainly Unicode-related and rarely changing)
289
     from source tables.
290
 
291
GNU diffutils version 2.7 (or later)
292
     Useful when submitting patches for the GCC source code.
293
 
294
patch version 2.5.4 (or later)
295
     Necessary when applying patches, created with `diff', to one's own
296
     sources.
297
 
298
 
299

300
File: gccinstall.info,  Node: Downloading the source,  Next: Configuration,  Prev: Prerequisites,  Up: Installing GCC
301
 
302
3 Downloading GCC
303
*****************
304
 
305
   GCC is distributed via SVN and FTP tarballs compressed with `gzip' or
306
`bzip2'.  It is possible to download a full distribution or specific
307
components.
308
 
309
   Please refer to the releases web page for information on how to
310
obtain GCC.
311
 
312
   The full distribution includes the C, C++, Objective-C, Fortran,
313
Java, and Ada (in the case of GCC 3.1 and later) compilers.  The full
314
distribution also includes runtime libraries for C++, Objective-C,
315
Fortran, and Java.  In GCC 3.0 and later versions, the GNU compiler
316
testsuites are also included in the full distribution.
317
 
318
   If you choose to download specific components, you must download the
319
core GCC distribution plus any language specific distributions you wish
320
to use.  The core distribution includes the C language front end as
321
well as the shared components.  Each language has a tarball which
322
includes the language front end as well as the language runtime (when
323
appropriate).
324
 
325
   Unpack the core distribution as well as any language specific
326
distributions in the same directory.
327
 
328
   If you also intend to build binutils (either to upgrade an existing
329
installation or for use in place of the corresponding tools of your
330
OS), unpack the binutils distribution either in the same directory or a
331
separate one.  In the latter case, add symbolic links to any components
332
of the binutils you intend to build alongside the compiler (`bfd',
333
`binutils', `gas', `gprof', `ld', `opcodes', ...) to the directory
334
containing the GCC sources.
335
 
336

337
File: gccinstall.info,  Node: Configuration,  Next: Building,  Prev: Downloading the source,  Up: Installing GCC
338
 
339
4 Installing GCC: Configuration
340
*******************************
341
 
342
   Like most GNU software, GCC must be configured before it can be
343
built.  This document describes the recommended configuration procedure
344
for both native and cross targets.
345
 
346
   We use SRCDIR to refer to the toplevel source directory for GCC; we
347
use OBJDIR to refer to the toplevel build/object directory.
348
 
349
   If you obtained the sources via SVN, SRCDIR must refer to the top
350
`gcc' directory, the one where the `MAINTAINERS' can be found, and not
351
its `gcc' subdirectory, otherwise the build will fail.
352
 
353
   If either SRCDIR or OBJDIR is located on an automounted NFS file
354
system, the shell's built-in `pwd' command will return temporary
355
pathnames.  Using these can lead to various sorts of build problems.
356
To avoid this issue, set the `PWDCMD' environment variable to an
357
automounter-aware `pwd' command, e.g., `pawd' or `amq -w', during the
358
configuration and build phases.
359
 
360
   First, we *highly* recommend that GCC be built into a separate
361
directory than the sources which does *not* reside within the source
362
tree.  This is how we generally build GCC; building where SRCDIR ==
363
OBJDIR should still work, but doesn't get extensive testing; building
364
where OBJDIR is a subdirectory of SRCDIR is unsupported.
365
 
366
   If you have previously built GCC in the same directory for a
367
different target machine, do `make distclean' to delete all files that
368
might be invalid.  One of the files this deletes is `Makefile'; if
369
`make distclean' complains that `Makefile' does not exist or issues a
370
message like "don't know how to make distclean" it probably means that
371
the directory is already suitably clean.  However, with the recommended
372
method of building in a separate OBJDIR, you should simply use a
373
different OBJDIR for each target.
374
 
375
   Second, when configuring a native system, either `cc' or `gcc' must
376
be in your path or you must set `CC' in your environment before running
377
configure.  Otherwise the configuration scripts may fail.
378
 
379
   To configure GCC:
380
 
381
        % mkdir OBJDIR
382
        % cd OBJDIR
383
        % SRCDIR/configure [OPTIONS] [TARGET]
384
 
385
Target specification
386
====================
387
 
388
   * GCC has code to correctly determine the correct value for TARGET
389
     for nearly all native systems.  Therefore, we highly recommend you
390
     not provide a configure target when configuring a native compiler.
391
 
392
   * TARGET must be specified as `--target=TARGET' when configuring a
393
     cross compiler; examples of valid targets would be m68k-coff,
394
     sh-elf, etc.
395
 
396
   * Specifying just TARGET instead of `--target=TARGET' implies that
397
     the host defaults to TARGET.
398
 
399
Options specification
400
=====================
401
 
402
Use OPTIONS to override several configure time options for GCC.  A list
403
of supported OPTIONS follows; `configure --help' may list other
404
options, but those not listed below may not work and should not
405
normally be used.
406
 
407
   Note that each `--enable' option has a corresponding `--disable'
408
option and that each `--with' option has a corresponding `--without'
409
option.
410
 
411
`--prefix=DIRNAME'
412
     Specify the toplevel installation directory.  This is the
413
     recommended way to install the tools into a directory other than
414
     the default.  The toplevel installation directory defaults to
415
     `/usr/local'.
416
 
417
     We *highly* recommend against DIRNAME being the same or a
418
     subdirectory of OBJDIR or vice versa.  If specifying a directory
419
     beneath a user's home directory tree, some shells will not expand
420
     DIRNAME correctly if it contains the `~' metacharacter; use
421
     `$HOME' instead.
422
 
423
     The following standard `autoconf' options are supported.  Normally
424
     you should not need to use these options.
425
    `--exec-prefix=DIRNAME'
426
          Specify the toplevel installation directory for
427
          architecture-dependent files.  The default is `PREFIX'.
428
 
429
    `--bindir=DIRNAME'
430
          Specify the installation directory for the executables called
431
          by users (such as `gcc' and `g++').  The default is
432
          `EXEC-PREFIX/bin'.
433
 
434
    `--libdir=DIRNAME'
435
          Specify the installation directory for object code libraries
436
          and internal data files of GCC.  The default is
437
          `EXEC-PREFIX/lib'.
438
 
439
    `--libexecdir=DIRNAME'
440
          Specify the installation directory for internal executables
441
          of GCC.    The default is `EXEC-PREFIX/libexec'.
442
 
443
    `--with-slibdir=DIRNAME'
444
          Specify the installation directory for the shared libgcc
445
          library.  The default is `LIBDIR'.
446
 
447
    `--infodir=DIRNAME'
448
          Specify the installation directory for documentation in info
449
          format.  The default is `PREFIX/info'.
450
 
451
    `--datadir=DIRNAME'
452
          Specify the installation directory for some
453
          architecture-independent data files referenced by GCC.  The
454
          default is `PREFIX/share'.
455
 
456
    `--mandir=DIRNAME'
457
          Specify the installation directory for manual pages.  The
458
          default is `PREFIX/man'.  (Note that the manual pages are
459
          only extracts from the full GCC manuals, which are provided
460
          in Texinfo format.  The manpages are derived by an automatic
461
          conversion process from parts of the full manual.)
462
 
463
    `--with-gxx-include-dir=DIRNAME'
464
          Specify the installation directory for G++ header files.  The
465
          default is `PREFIX/include/c++/VERSION'.
466
 
467
 
468
`--program-prefix=PREFIX'
469
     GCC supports some transformations of the names of its programs when
470
     installing them.  This option prepends PREFIX to the names of
471
     programs to install in BINDIR (see above).  For example, specifying
472
     `--program-prefix=foo-' would result in `gcc' being installed as
473
     `/usr/local/bin/foo-gcc'.
474
 
475
`--program-suffix=SUFFIX'
476
     Appends SUFFIX to the names of programs to install in BINDIR (see
477
     above).  For example, specifying `--program-suffix=-3.1' would
478
     result in `gcc' being installed as `/usr/local/bin/gcc-3.1'.
479
 
480
`--program-transform-name=PATTERN'
481
     Applies the `sed' script PATTERN to be applied to the names of
482
     programs to install in BINDIR (see above).  PATTERN has to consist
483
     of one or more basic `sed' editing commands, separated by
484
     semicolons.  For example, if you want the `gcc' program name to be
485
     transformed to the installed program `/usr/local/bin/myowngcc' and
486
     the `g++' program name to be transformed to
487
     `/usr/local/bin/gspecial++' without changing other program names,
488
     you could use the pattern
489
     `--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/''
490
     to achieve this effect.
491
 
492
     All three options can be combined and used together, resulting in
493
     more complex conversion patterns.  As a basic rule, PREFIX (and
494
     SUFFIX) are prepended (appended) before further transformations
495
     can happen with a special transformation script PATTERN.
496
 
497
     As currently implemented, this option only takes effect for native
498
     builds; cross compiler binaries' names are not transformed even
499
     when a transformation is explicitly asked for by one of these
500
     options.
501
 
502
     For native builds, some of the installed programs are also
503
     installed with the target alias in front of their name, as in
504
     `i686-pc-linux-gnu-gcc'.  All of the above transformations happen
505
     before the target alias is prepended to the name--so, specifying
506
     `--program-prefix=foo-' and `program-suffix=-3.1', the resulting
507
     binary would be installed as
508
     `/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1'.
509
 
510
     As a last shortcoming, none of the installed Ada programs are
511
     transformed yet, which will be fixed in some time.
512
 
513
`--with-local-prefix=DIRNAME'
514
     Specify the installation directory for local include files.  The
515
     default is `/usr/local'.  Specify this option if you want the
516
     compiler to search directory `DIRNAME/include' for locally
517
     installed header files _instead_ of `/usr/local/include'.
518
 
519
     You should specify `--with-local-prefix' *only* if your site has a
520
     different convention (not `/usr/local') for where to put
521
     site-specific files.
522
 
523
     The default value for `--with-local-prefix' is `/usr/local'
524
     regardless of the value of `--prefix'.  Specifying `--prefix' has
525
     no effect on which directory GCC searches for local header files.
526
     This may seem counterintuitive, but actually it is logical.
527
 
528
     The purpose of `--prefix' is to specify where to _install GCC_.
529
     The local header files in `/usr/local/include'--if you put any in
530
     that directory--are not part of GCC.  They are part of other
531
     programs--perhaps many others.  (GCC installs its own header files
532
     in another directory which is based on the `--prefix' value.)
533
 
534
     Both the local-prefix include directory and the GCC-prefix include
535
     directory are part of GCC's "system include" directories.
536
     Although these two directories are not fixed, they need to be
537
     searched in the proper order for the correct processing of the
538
     include_next directive.  The local-prefix include directory is
539
     searched before the GCC-prefix include directory.  Another
540
     characteristic of system include directories is that pedantic
541
     warnings are turned off for headers in these directories.
542
 
543
     Some autoconf macros add `-I DIRECTORY' options to the compiler
544
     command line, to ensure that directories containing installed
545
     packages' headers are searched.  When DIRECTORY is one of GCC's
546
     system include directories, GCC will ignore the option so that
547
     system directories continue to be processed in the correct order.
548
     This may result in a search order different from what was
549
     specified but the directory will still be searched.
550
 
551
     GCC automatically searches for ordinary libraries using
552
     `GCC_EXEC_PREFIX'.  Thus, when the same installation prefix is
553
     used for both GCC and packages, GCC will automatically search for
554
     both headers and libraries.  This provides a configuration that is
555
     easy to use.  GCC behaves in a manner similar to that when it is
556
     installed as a system compiler in `/usr'.
557
 
558
     Sites that need to install multiple versions of GCC may not want to
559
     use the above simple configuration.  It is possible to use the
560
     `--program-prefix', `--program-suffix' and
561
     `--program-transform-name' options to install multiple versions
562
     into a single directory, but it may be simpler to use different
563
     prefixes and the `--with-local-prefix' option to specify the
564
     location of the site-specific files for each version.  It will
565
     then be necessary for users to specify explicitly the location of
566
     local site libraries (e.g., with `LIBRARY_PATH').
567
 
568
     The same value can be used for both `--with-local-prefix' and
569
     `--prefix' provided it is not `/usr'.  This can be used to avoid
570
     the default search of `/usr/local/include'.
571
 
572
     *Do not* specify `/usr' as the `--with-local-prefix'!  The
573
     directory you use for `--with-local-prefix' *must not* contain any
574
     of the system's standard header files.  If it did contain them,
575
     certain programs would be miscompiled (including GNU Emacs, on
576
     certain targets), because this would override and nullify the
577
     header file corrections made by the `fixincludes' script.
578
 
579
     Indications are that people who use this option use it based on
580
     mistaken ideas of what it is for.  People use it as if it
581
     specified where to install part of GCC.  Perhaps they make this
582
     assumption because installing GCC creates the directory.
583
 
584
`--enable-shared[=PACKAGE[,...]]'
585
     Build shared versions of libraries, if shared libraries are
586
     supported on the target platform.  Unlike GCC 2.95.x and earlier,
587
     shared libraries are enabled by default on all platforms that
588
     support shared libraries.
589
 
590
     If a list of packages is given as an argument, build shared
591
     libraries only for the listed packages.  For other packages, only
592
     static libraries will be built.  Package names currently
593
     recognized in the GCC tree are `libgcc' (also known as `gcc'),
594
     `libstdc++' (not `libstdc++-v3'), `libffi', `zlib', `boehm-gc',
595
     `ada', `libada', `libjava' and `libobjc'.  Note `libiberty' does
596
     not support shared libraries at all.
597
 
598
     Use `--disable-shared' to build only static libraries.  Note that
599
     `--disable-shared' does not accept a list of package names as
600
     argument, only `--enable-shared' does.
601
 
602
`--with-gnu-as'
603
     Specify that the compiler should assume that the assembler it
604
     finds is the GNU assembler.  However, this does not modify the
605
     rules to find an assembler and will result in confusion if the
606
     assembler found is not actually the GNU assembler.  (Confusion may
607
     also result if the compiler finds the GNU assembler but has not
608
     been configured with `--with-gnu-as'.)  If you have more than one
609
     assembler installed on your system, you may want to use this
610
     option in connection with `--with-as=PATHNAME' or
611
     `--with-build-time-tools=PATHNAME'.
612
 
613
     The following systems are the only ones where it makes a difference
614
     whether you use the GNU assembler.  On any other system,
615
     `--with-gnu-as' has no effect.
616
 
617
        * `hppa1.0-ANY-ANY'
618
 
619
        * `hppa1.1-ANY-ANY'
620
 
621
        * `i386-ANY-sysv'
622
 
623
        * `m68k-bull-sysv'
624
 
625
        * `m68k-hp-hpux'
626
 
627
        * `m68000-hp-hpux'
628
 
629
        * `m68000-att-sysv'
630
 
631
        * `sparc-sun-solaris2.ANY'
632
 
633
        * `sparc64-ANY-solaris2.ANY'
634
 
635
     On the systems listed above (except for the HP-PA, the SPARC, for
636
     ISC on the 386, if you use the GNU assembler, you should also use
637
     the GNU linker (and specify `--with-gnu-ld').
638
 
639
`--with-as=PATHNAME'
640
     Specify that the compiler should use the assembler pointed to by
641
     PATHNAME, rather than the one found by the standard rules to find
642
     an assembler, which are:
643
        * Unless GCC is being built with a cross compiler, check the
644
          `LIBEXEC/gcc/TARGET/VERSION' directory.  LIBEXEC defaults to
645
          `EXEC-PREFIX/libexec'; EXEC-PREFIX defaults to PREFIX, which
646
          defaults to `/usr/local' unless overridden by the
647
          `--prefix=PATHNAME' switch described above.  TARGET is the
648
          target system triple, such as `sparc-sun-solaris2.7', and
649
          VERSION denotes the GCC version, such as 3.0.
650
 
651
        * If the target system is the same that you are building on,
652
          check operating system specific directories (e.g.
653
          `/usr/ccs/bin' on Sun Solaris 2).
654
 
655
        * Check in the `PATH' for a tool whose name is prefixed by the
656
          target system triple.
657
 
658
        * Check in the `PATH' for a tool whose name is not prefixed by
659
          the target system triple, if the host and target system
660
          triple are the same (in other words, we use a host tool if it
661
          can be used for the target as well).
662
 
663
     You may want to use `--with-as' if no assembler is installed in
664
     the directories listed above, or if you have multiple assemblers
665
     installed and want to choose one that is not found by the above
666
     rules.
667
 
668
`--with-gnu-ld'
669
     Same as `--with-gnu-as' but for the linker.
670
 
671
`--with-ld=PATHNAME'
672
     Same as `--with-as' but for the linker.
673
 
674
`--with-stabs'
675
     Specify that stabs debugging information should be used instead of
676
     whatever format the host normally uses.  Normally GCC uses the
677
     same debug format as the host system.
678
 
679
     On MIPS based systems and on Alphas, you must specify whether you
680
     want GCC to create the normal ECOFF debugging format, or to use
681
     BSD-style stabs passed through the ECOFF symbol table.  The normal
682
     ECOFF debug format cannot fully handle languages other than C.
683
     BSD stabs format can handle other languages, but it only works
684
     with the GNU debugger GDB.
685
 
686
     Normally, GCC uses the ECOFF debugging format by default; if you
687
     prefer BSD stabs, specify `--with-stabs' when you configure GCC.
688
 
689
     No matter which default you choose when you configure GCC, the user
690
     can use the `-gcoff' and `-gstabs+' options to specify explicitly
691
     the debug format for a particular compilation.
692
 
693
     `--with-stabs' is meaningful on the ISC system on the 386, also, if
694
     `--with-gas' is used.  It selects use of stabs debugging
695
     information embedded in COFF output.  This kind of debugging
696
     information supports C++ well; ordinary COFF debugging information
697
     does not.
698
 
699
     `--with-stabs' is also meaningful on 386 systems running SVR4.  It
700
     selects use of stabs debugging information embedded in ELF output.
701
     The C++ compiler currently (2.6.0) does not support the DWARF
702
     debugging information normally used on 386 SVR4 platforms; stabs
703
     provide a workable alternative.  This requires gas and gdb, as the
704
     normal SVR4 tools can not generate or interpret stabs.
705
 
706
`--disable-multilib'
707
     Specify that multiple target libraries to support different target
708
     variants, calling conventions, etc. should not be built.  The
709
     default is to build a predefined set of them.
710
 
711
     Some targets provide finer-grained control over which multilibs
712
     are built (e.g., `--disable-softfloat'):
713
    `arc-*-elf*'
714
          biendian.
715
 
716
    `arm-*-*'
717
          fpu, 26bit, underscore, interwork, biendian, nofmult.
718
 
719
    `m68*-*-*'
720
          softfloat, m68881, m68000, m68020.
721
 
722
    `mips*-*-*'
723
          single-float, biendian, softfloat.
724
 
725
    `powerpc*-*-*, rs6000*-*-*'
726
          aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos,
727
          biendian, sysv, aix.
728
 
729
 
730
`--enable-threads'
731
     Specify that the target supports threads.  This affects the
732
     Objective-C compiler and runtime library, and exception handling
733
     for other languages like C++ and Java.  On some systems, this is
734
     the default.
735
 
736
     In general, the best (and, in many cases, the only known) threading
737
     model available will be configured for use.  Beware that on some
738
     systems, GCC has not been taught what threading models are
739
     generally available for the system.  In this case,
740
     `--enable-threads' is an alias for `--enable-threads=single'.
741
 
742
`--disable-threads'
743
     Specify that threading support should be disabled for the system.
744
     This is an alias for `--enable-threads=single'.
745
 
746
`--enable-threads=LIB'
747
     Specify that LIB is the thread support library.  This affects the
748
     Objective-C compiler and runtime library, and exception handling
749
     for other languages like C++ and Java.  The possibilities for LIB
750
     are:
751
 
752
    `aix'
753
          AIX thread support.
754
 
755
    `dce'
756
          DCE thread support.
757
 
758
    `gnat'
759
          Ada tasking support.  For non-Ada programs, this setting is
760
          equivalent to `single'.  When used in conjunction with the
761
          Ada run time, it causes GCC to use the same thread primitives
762
          as Ada uses.  This option is necessary when using both Ada
763
          and the back end exception handling, which is the default for
764
          most Ada targets.
765
 
766
    `mach'
767
          Generic MACH thread support, known to work on NeXTSTEP.
768
          (Please note that the file needed to support this
769
          configuration, `gthr-mach.h', is missing and thus this
770
          setting will cause a known bootstrap failure.)
771
 
772
    `no'
773
          This is an alias for `single'.
774
 
775
    `posix'
776
          Generic POSIX/Unix98 thread support.
777
 
778
    `posix95'
779
          Generic POSIX/Unix95 thread support.
780
 
781
    `rtems'
782
          RTEMS thread support.
783
 
784
    `single'
785
          Disable thread support, should work for all platforms.
786
 
787
    `solaris'
788
          Sun Solaris 2 thread support.
789
 
790
    `vxworks'
791
          VxWorks thread support.
792
 
793
    `win32'
794
          Microsoft Win32 API thread support.
795
 
796
    `nks'
797
          Novell Kernel Services thread support.
798
 
799
`--enable-tls'
800
     Specify that the target supports TLS (Thread Local Storage).
801
     Usually configure can correctly determine if TLS is supported.  In
802
     cases where it guesses incorrectly, TLS can be explicitly enabled
803
     or disabled with `--enable-tls' or `--disable-tls'.  This can
804
     happen if the assembler supports TLS but the C library does not,
805
     or if the assumptions made by the configure test are incorrect.
806
 
807
`--disable-tls'
808
     Specify that the target does not support TLS.  This is an alias
809
     for `--enable-tls=no'.
810
 
811
`--with-cpu=CPU'
812
     Specify which cpu variant the compiler should generate code for by
813
     default.  CPU will be used as the default value of the `-mcpu='
814
     switch.  This option is only supported on some targets, including
815
     ARM, i386, PowerPC, and SPARC.
816
 
817
`--with-schedule=CPU'
818
`--with-arch=CPU'
819
`--with-tune=CPU'
820
`--with-abi=ABI'
821
`--with-fpu=TYPE'
822
`--with-float=TYPE'
823
     These configure options provide default values for the
824
     `-mschedule=', `-march=', `-mtune=', `-mabi=', and `-mfpu='
825
     options and for `-mhard-float' or `-msoft-float'.  As with
826
     `--with-cpu', which switches will be accepted and acceptable values
827
     of the arguments depend on the target.
828
 
829
`--with-mode=MODE'
830
     Specify if the compiler should default to `-marm' or `-mthumb'.
831
     This option is only supported on ARM targets.
832
 
833
`--with-divide=TYPE'
834
     Specify how the compiler should generate code for checking for
835
     division by zero.  This option is only supported on the MIPS
836
     target.  The possibilities for TYPE are:
837
    `traps'
838
          Division by zero checks use conditional traps (this is the
839
          default on systems that support conditional traps).
840
 
841
    `breaks'
842
          Division by zero checks use the break instruction.
843
 
844
`--enable-__cxa_atexit'
845
     Define if you want to use __cxa_atexit, rather than atexit, to
846
     register C++ destructors for local statics and global objects.
847
     This is essential for fully standards-compliant handling of
848
     destructors, but requires __cxa_atexit in libc.  This option is
849
     currently only available on systems with GNU libc.  When enabled,
850
     this will cause `-fuse-cxa-exit' to be passed by default.
851
 
852
`--enable-target-optspace'
853
     Specify that target libraries should be optimized for code space
854
     instead of code speed.  This is the default for the m32r platform.
855
 
856
`--disable-cpp'
857
     Specify that a user visible `cpp' program should not be installed.
858
 
859
`--with-cpp-install-dir=DIRNAME'
860
     Specify that the user visible `cpp' program should be installed in
861
     `PREFIX/DIRNAME/cpp', in addition to BINDIR.
862
 
863
`--enable-initfini-array'
864
     Force the use of sections `.init_array' and `.fini_array' (instead
865
     of `.init' and `.fini') for constructors and destructors.  Option
866
     `--disable-initfini-array' has the opposite effect.  If neither
867
     option is specified, the configure script will try to guess
868
     whether the `.init_array' and `.fini_array' sections are supported
869
     and, if they are, use them.
870
 
871
`--enable-maintainer-mode'
872
     The build rules that regenerate the GCC master message catalog
873
     `gcc.pot' are normally disabled.  This is because it can only be
874
     rebuilt if the complete source tree is present.  If you have
875
     changed the sources and want to rebuild the catalog, configuring
876
     with `--enable-maintainer-mode' will enable this.  Note that you
877
     need a recent version of the `gettext' tools to do so.
878
 
879
`--disable-bootstrap'
880
     For a native build, the default configuration is to perform a
881
     3-stage bootstrap of the compiler when `make' is invoked, testing
882
     that GCC can compile itself correctly.  If you want to disable
883
     this process, you can configure with `--disable-bootstrap'.
884
 
885
`--enable-bootstrap'
886
     In special cases, you may want to perform a 3-stage build even if
887
     the target and host triplets are different.  This could happen
888
     when the host can run code compiled for the target (e.g. host is
889
     i686-linux, target is i486-linux).  Starting from GCC 4.2, to do
890
     this you have to configure explicitly with `--enable-bootstrap'.
891
 
892
`--enable-generated-files-in-srcdir'
893
     Neither the .c and .h files that are generated from Bison and flex
894
     nor the info manuals and man pages that are built from the .texi
895
     files are present in the SVN development tree.  When building GCC
896
     from that development tree, or from one of our snapshots, those
897
     generated files are placed in your build directory, which allows
898
     for the source to be in a readonly directory.
899
 
900
     If you configure with `--enable-generated-files-in-srcdir' then
901
     those generated files will go into the source directory.  This is
902
     mainly intended for generating release or prerelease tarballs of
903
     the GCC sources, since it is not a requirement that the users of
904
     source releases to have flex, Bison, or makeinfo.
905
 
906
`--enable-version-specific-runtime-libs'
907
     Specify that runtime libraries should be installed in the compiler
908
     specific subdirectory (`LIBDIR/gcc') rather than the usual places.
909
     In addition, `libstdc++''s include files will be installed into
910
     `LIBDIR' unless you overruled it by using
911
     `--with-gxx-include-dir=DIRNAME'.  Using this option is
912
     particularly useful if you intend to use several versions of GCC in
913
     parallel.  This is currently supported by `libgfortran',
914
     `libjava', `libmudflap', `libstdc++', and `libobjc'.
915
 
916
`--with-java-home=DIRNAME'
917
     This `libjava' option overrides the default value of the
918
     `java.home' system property.  It is also used to set
919
     `sun.boot.class.path' to `DIRNAME/lib/rt.jar'.  By default
920
     `java.home' is set to `PREFIX' and `sun.boot.class.path' to
921
     `DATADIR/java/libgcj-VERSION.jar'.
922
 
923
`--enable-languages=LANG1,LANG2,...'
924
     Specify that only a particular subset of compilers and their
925
     runtime libraries should be built.  For a list of valid values for
926
     LANGN you can issue the following command in the `gcc' directory
927
     of your GCC source tree:
928
          grep language= */config-lang.in
929
     Currently, you can use any of the following: `all', `ada', `c',
930
     `c++', `fortran', `java', `objc', `obj-c++', `treelang'.  Building
931
     the Ada compiler has special requirements, see below.  If you do
932
     not pass this flag, or specify the option `all', then all default
933
     languages available in the `gcc' sub-tree will be configured.
934
     Ada, Objective-C++, and treelang are not default languages; the
935
     rest are.  Re-defining `LANGUAGES' when calling `make' *does not*
936
     work anymore, as those language sub-directories might not have been
937
     configured!
938
 
939
`--disable-libada'
940
     Specify that the run-time libraries and tools used by GNAT should
941
     not be built.  This can be useful for debugging, or for
942
     compatibility with previous Ada build procedures, when it was
943
     required to explicitly do a `make -C gcc gnatlib_and_tools'.
944
 
945
`--disable-libssp'
946
     Specify that the run-time libraries for stack smashing protection
947
     should not be built.
948
 
949
`--disable-libgomp'
950
     Specify that the run-time libraries used by GOMP should not be
951
     built.
952
 
953
`--with-dwarf2'
954
     Specify that the compiler should use DWARF 2 debugging information
955
     as the default.
956
 
957
`--enable-targets=all'
958
`--enable-targets=TARGET_LIST'
959
     Some GCC targets, e.g. powerpc64-linux, build bi-arch compilers.
960
     These are compilers that are able to generate either 64-bit or
961
     32-bit code.  Typically, the corresponding 32-bit target, e.g.
962
     powerpc-linux for powerpc64-linux, only generates 32-bit code.
963
     This option enables the 32-bit target to be a bi-arch compiler,
964
     which is useful when you want a bi-arch compiler that defaults to
965
     32-bit, and you are building a bi-arch or multi-arch binutils in a
966
     combined tree.  Currently, this option only affects powerpc-linux.
967
 
968
`--enable-secureplt'
969
     This option enables `-msecure-plt' by default for powerpc-linux.
970
     *Note RS/6000 and PowerPC Options: (gcc)RS/6000 and PowerPC
971
     Options,
972
 
973
`--enable-win32-registry'
974
`--enable-win32-registry=KEY'
975
`--disable-win32-registry'
976
     The `--enable-win32-registry' option enables Microsoft
977
     Windows-hosted GCC to look up installations paths in the registry
978
     using the following key:
979
 
980
          `HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\KEY'
981
 
982
     KEY defaults to GCC version number, and can be overridden by the
983
     `--enable-win32-registry=KEY' option.  Vendors and distributors
984
     who use custom installers are encouraged to provide a different
985
     key, perhaps one comprised of vendor name and GCC version number,
986
     to avoid conflict with existing installations.  This feature is
987
     enabled by default, and can be disabled by
988
     `--disable-win32-registry' option.  This option has no effect on
989
     the other hosts.
990
 
991
`--nfp'
992
     Specify that the machine does not have a floating point unit.  This
993
     option only applies to `m68k-sun-sunosN'.  On any other system,
994
     `--nfp' has no effect.
995
 
996
`--enable-werror'
997
`--disable-werror'
998
`--enable-werror=yes'
999
`--enable-werror=no'
1000
     When you specify this option, it controls whether certain files in
1001
     the compiler are built with `-Werror' in bootstrap stage2 and
1002
     later.  If you don't specify it, `-Werror' is turned on for the
1003
     main development trunk.  However it defaults to off for release
1004
     branches and final releases.  The specific files which get
1005
     `-Werror' are controlled by the Makefiles.
1006
 
1007
`--enable-checking'
1008
`--enable-checking=LIST'
1009
     When you specify this option, the compiler is built to perform
1010
     internal consistency checks of the requested complexity.  This
1011
     does not change the generated code, but adds error checking within
1012
     the compiler.  This will slow down the compiler and may only work
1013
     properly if you are building the compiler with GCC.  This is `yes'
1014
     by default when building from SVN or snapshots, but `release' for
1015
     releases.  More control over the checks may be had by specifying
1016
     LIST.  The categories of checks available are `yes' (most common
1017
     checks `assert,misc,tree,gc,rtlflag,runtime'), `no' (no checks at
1018
     all), `all' (all but `valgrind'), `release' (cheapest checks
1019
     `assert,runtime') or `none' (same as `no').  Individual checks can
1020
     be enabled with these flags `assert', `fold', `gc', `gcac' `misc',
1021
     `rtl', `rtlflag', `runtime', `tree', and `valgrind'.
1022
 
1023
     The `valgrind' check requires the external `valgrind' simulator,
1024
     available from `http://valgrind.org/'.  The `rtl', `gcac' and
1025
     `valgrind' checks are very expensive.  To disable all checking,
1026
     `--disable-checking' or `--enable-checking=none' must be
1027
     explicitly requested.  Disabling assertions will make the compiler
1028
     and runtime slightly faster but increase the risk of undetected
1029
     internal errors causing wrong code to be generated.
1030
 
1031
`--enable-coverage'
1032
`--enable-coverage=LEVEL'
1033
     With this option, the compiler is built to collect self coverage
1034
     information, every time it is run.  This is for internal
1035
     development purposes, and only works when the compiler is being
1036
     built with gcc.  The LEVEL argument controls whether the compiler
1037
     is built optimized or not, values are `opt' and `noopt'.  For
1038
     coverage analysis you want to disable optimization, for
1039
     performance analysis you want to enable optimization.  When
1040
     coverage is enabled, the default level is without optimization.
1041
 
1042
`--enable-gather-detailed-mem-stats'
1043
     When this option is specified more detailed information on memory
1044
     allocation is gathered.  This information is printed when using
1045
     `-fmem-report'.
1046
 
1047
`--with-gc'
1048
`--with-gc=CHOICE'
1049
     With this option you can specify the garbage collector
1050
     implementation used during the compilation process.  CHOICE can be
1051
     one of `page' and `zone', where `page' is the default.
1052
 
1053
`--enable-nls'
1054
`--disable-nls'
1055
     The `--enable-nls' option enables Native Language Support (NLS),
1056
     which lets GCC output diagnostics in languages other than American
1057
     English.  Native Language Support is enabled by default if not
1058
     doing a canadian cross build.  The `--disable-nls' option disables
1059
     NLS.
1060
 
1061
`--with-included-gettext'
1062
     If NLS is enabled, the `--with-included-gettext' option causes the
1063
     build procedure to prefer its copy of GNU `gettext'.
1064
 
1065
`--with-catgets'
1066
     If NLS is enabled, and if the host lacks `gettext' but has the
1067
     inferior `catgets' interface, the GCC build procedure normally
1068
     ignores `catgets' and instead uses GCC's copy of the GNU `gettext'
1069
     library.  The `--with-catgets' option causes the build procedure
1070
     to use the host's `catgets' in this situation.
1071
 
1072
`--with-libiconv-prefix=DIR'
1073
     Search for libiconv header files in `DIR/include' and libiconv
1074
     library files in `DIR/lib'.
1075
 
1076
`--enable-obsolete'
1077
     Enable configuration for an obsoleted system.  If you attempt to
1078
     configure GCC for a system (build, host, or target) which has been
1079
     obsoleted, and you do not specify this flag, configure will halt
1080
     with an error message.
1081
 
1082
     All support for systems which have been obsoleted in one release
1083
     of GCC is removed entirely in the next major release, unless
1084
     someone steps forward to maintain the port.
1085
 
1086
`--enable-decimal-float'
1087
`--disable-decimal-float'
1088
     Enable (or disable) support for the C decimal floating point
1089
     extension.  This is enabled by default only on PowerPC GNU/Linux
1090
     systems.  Other systems may also support it, but require the user
1091
     to specifically enable it.
1092
 
1093
`--with-long-double-128'
1094
     Specify if `long double' type should be 128-bit by default on
1095
     selected GNU/Linux architectures.  If using
1096
     `--without-long-double-128', `long double' will be by default
1097
     64-bit, the same as `double' type.  When neither of these
1098
     configure options are used, the default will be 128-bit `long
1099
     double' when built against GNU C Library 2.4 and later, 64-bit
1100
     `long double' otherwise.
1101
 
1102
 
1103
Cross-Compiler-Specific Options
1104
-------------------------------
1105
 
1106
The following options only apply to building cross compilers.
1107
`--with-sysroot'
1108
`--with-sysroot=DIR'
1109
     Tells GCC to consider DIR as the root of a tree that contains a
1110
     (subset of) the root filesystem of the target operating system.
1111
     Target system headers, libraries and run-time object files will be
1112
     searched in there.  The specified directory is not copied into the
1113
     install tree, unlike the options `--with-headers' and
1114
     `--with-libs' that this option obsoletes.  The default value, in
1115
     case `--with-sysroot' is not given an argument, is
1116
     `${gcc_tooldir}/sys-root'.  If the specified directory is a
1117
     subdirectory of `${exec_prefix}', then it will be found relative to
1118
     the GCC binaries if the installation tree is moved.
1119
 
1120
`--with-build-sysroot'
1121
`--with-build-sysroot=DIR'
1122
     Tells GCC to consider DIR as the system root (see
1123
     `--with-sysroot') while building target libraries, instead of the
1124
     directory specified with `--with-sysroot'.  This option is only
1125
     useful when you are already using `--with-sysroot'.  You can use
1126
     `--with-build-sysroot' when you are configuring with `--prefix'
1127
     set to a directory that is different from the one in which you are
1128
     installing GCC and your target libraries.
1129
 
1130
     This option affects the system root for the compiler used to build
1131
     target libraries (which runs on the build system); it does not
1132
     affect the compiler which is used to build GCC itself.
1133
 
1134
`--with-headers'
1135
`--with-headers=DIR'
1136
     Deprecated in favor of `--with-sysroot'.  Specifies that target
1137
     headers are available when building a cross compiler.  The DIR
1138
     argument specifies a directory which has the target include files.
1139
     These include files will be copied into the `gcc' install
1140
     directory.  _This option with the DIR argument is required_ when
1141
     building a cross compiler, if `PREFIX/TARGET/sys-include' doesn't
1142
     pre-exist.  If `PREFIX/TARGET/sys-include' does pre-exist, the DIR
1143
     argument may be omitted.  `fixincludes' will be run on these files
1144
     to make them compatible with GCC.
1145
 
1146
`--without-headers'
1147
     Tells GCC not use any target headers from a libc when building a
1148
     cross compiler.  When crossing to GNU/Linux, you need the headers
1149
     so GCC can build the exception handling for libgcc.
1150
 
1151
`--with-libs'
1152
`--with-libs=``DIR1 DIR2 ... DIRN'''
1153
     Deprecated in favor of `--with-sysroot'.  Specifies a list of
1154
     directories which contain the target runtime libraries.  These
1155
     libraries will be copied into the `gcc' install directory.  If the
1156
     directory list is omitted, this option has no effect.
1157
 
1158
`--with-newlib'
1159
     Specifies that `newlib' is being used as the target C library.
1160
     This causes `__eprintf' to be omitted from `libgcc.a' on the
1161
     assumption that it will be provided by `newlib'.
1162
 
1163
`--with-build-time-tools=DIR'
1164
     Specifies where to find the set of target tools (assembler,
1165
     linker, etc.)  that will be used while building GCC itself.  This
1166
     option can be useful if the directory layouts are different
1167
     between the system you are building GCC on, and the system where
1168
     you will deploy it.
1169
 
1170
     For example, on a `ia64-hp-hpux' system, you may have the GNU
1171
     assembler and linker in `/usr/bin', and the native tools in a
1172
     different path, and build a toolchain that expects to find the
1173
     native tools in `/usr/bin'.
1174
 
1175
     When you use this option, you should ensure that DIR includes
1176
     `ar', `as', `ld', `nm', `ranlib' and `strip' if necessary, and
1177
     possibly `objdump'.  Otherwise, GCC may use an inconsistent set of
1178
     tools.
1179
 
1180
Fortran-Specific Options
1181
------------------------
1182
 
1183
The following options apply to the build of the Fortran front end.
1184
 
1185
`--with-gmp=PATHNAME'
1186
`--with-gmp-include=PATHNAME'
1187
`--with-gmp-lib=PATHNAME'
1188
`--with-mpfr=PATHNAME'
1189
`--with-mpfr-include=PATHNAME'
1190
`--with-mpfr-lib=PATHNAME'
1191
     If you do not have GMP (the GNU Multiple Precision library) and the
1192
     MPFR Libraries installed in a standard location and you want to
1193
     build the Fortran front-end, you can explicitly specify the
1194
     directory where they are installed (`--with-gmp=GMPINSTALLDIR',
1195
     `--with-mpfr=MPFRINSTALLDIR').  The `--with-gmp=GMPINSTALLDIR'
1196
     option is shorthand for `--with-gmp-lib=GMPINSTALLDIR/lib' and
1197
     `--with-gmp-include=GMPINSTALLDIR/include'.  Likewise the
1198
     `--with-mpfr=MPFRINSTALLDIR' option is shorthand for
1199
     `--with-mpfr-lib=MPFRINSTALLDIR/lib' and
1200
     `--with-mpfr-include=MPFRINSTALLDIR/include'.  If these shorthand
1201
     assumptions are not correct, you can use the explicit include and
1202
     lib options directly.
1203
 
1204
 
1205
Java-Specific Options
1206
---------------------
1207
 
1208
The following option applies to the build of the Java front end.
1209
 
1210
`--disable-libgcj'
1211
     Specify that the run-time libraries used by GCJ should not be
1212
     built.  This is useful in case you intend to use GCJ with some
1213
     other run-time, or you're going to install it separately, or it
1214
     just happens not to build on your particular machine.  In general,
1215
     if the Java front end is enabled, the GCJ libraries will be
1216
     enabled too, unless they're known to not work on the target
1217
     platform.  If GCJ is enabled but `libgcj' isn't built, you may
1218
     need to port it; in this case, before modifying the top-level
1219
     `configure.in' so that `libgcj' is enabled by default on this
1220
     platform, you may use `--enable-libgcj' to override the default.
1221
 
1222
 
1223
   The following options apply to building `libgcj'.
1224
 
1225
General Options
1226
...............
1227
 
1228
`--disable-getenv-properties'
1229
     Don't set system properties from `GCJ_PROPERTIES'.
1230
 
1231
`--enable-hash-synchronization'
1232
     Use a global hash table for monitor locks.  Ordinarily, `libgcj''s
1233
     `configure' script automatically makes the correct choice for this
1234
     option for your platform.  Only use this if you know you need the
1235
     library to be configured differently.
1236
 
1237
`--enable-interpreter'
1238
     Enable the Java interpreter.  The interpreter is automatically
1239
     enabled by default on all platforms that support it.  This option
1240
     is really only useful if you want to disable the interpreter
1241
     (using `--disable-interpreter').
1242
 
1243
`--disable-java-net'
1244
     Disable java.net.  This disables the native part of java.net only,
1245
     using non-functional stubs for native method implementations.
1246
 
1247
`--disable-jvmpi'
1248
     Disable JVMPI support.
1249
 
1250
`--with-ecos'
1251
     Enable runtime eCos target support.
1252
 
1253
`--without-libffi'
1254
     Don't use `libffi'.  This will disable the interpreter and JNI
1255
     support as well, as these require `libffi' to work.
1256
 
1257
`--enable-libgcj-debug'
1258
     Enable runtime debugging code.
1259
 
1260
`--enable-libgcj-multifile'
1261
     If specified, causes all `.java' source files to be compiled into
1262
     `.class' files in one invocation of `gcj'.  This can speed up
1263
     build time, but is more resource-intensive.  If this option is
1264
     unspecified or disabled, `gcj' is invoked once for each `.java'
1265
     file to compile into a `.class' file.
1266
 
1267
`--with-libiconv-prefix=DIR'
1268
     Search for libiconv in `DIR/include' and `DIR/lib'.
1269
 
1270
`--enable-sjlj-exceptions'
1271
     Force use of the `setjmp'/`longjmp'-based scheme for exceptions.
1272
     `configure' ordinarily picks the correct value based on the
1273
     platform.  Only use this option if you are sure you need a
1274
     different setting.
1275
 
1276
`--with-system-zlib'
1277
     Use installed `zlib' rather than that included with GCC.
1278
 
1279
`--with-win32-nlsapi=ansi, unicows or unicode'
1280
     Indicates how MinGW `libgcj' translates between UNICODE characters
1281
     and the Win32 API.
1282
    `ansi'
1283
          Use the single-byte `char' and the Win32 A functions natively,
1284
          translating to and from UNICODE when using these functions.
1285
          If unspecified, this is the default.
1286
 
1287
    `unicows'
1288
          Use the `WCHAR' and Win32 W functions natively.  Adds
1289
          `-lunicows' to `libgcj.spec' to link with `libunicows'.
1290
          `unicows.dll' needs to be deployed on Microsoft Windows 9X
1291
          machines running built executables.  `libunicows.a', an
1292
          open-source import library around Microsoft's `unicows.dll',
1293
          is obtained from `http://libunicows.sourceforge.net/', which
1294
          also gives details on getting `unicows.dll' from Microsoft.
1295
 
1296
    `unicode'
1297
          Use the `WCHAR' and Win32 W functions natively.  Does _not_
1298
          add `-lunicows' to `libgcj.spec'.  The built executables will
1299
          only run on Microsoft Windows NT and above.
1300
 
1301
AWT-Specific Options
1302
....................
1303
 
1304
`--with-x'
1305
     Use the X Window System.
1306
 
1307
`--enable-java-awt=PEER(S)'
1308
     Specifies the AWT peer library or libraries to build alongside
1309
     `libgcj'.  If this option is unspecified or disabled, AWT will be
1310
     non-functional.  Current valid values are `gtk' and `xlib'.
1311
     Multiple libraries should be separated by a comma (i.e.
1312
     `--enable-java-awt=gtk,xlib').
1313
 
1314
`--enable-gtk-cairo'
1315
     Build the cairo Graphics2D implementation on GTK.
1316
 
1317
`--enable-java-gc=TYPE'
1318
     Choose garbage collector.  Defaults to `boehm' if unspecified.
1319
 
1320
`--disable-gtktest'
1321
     Do not try to compile and run a test GTK+ program.
1322
 
1323
`--disable-glibtest'
1324
     Do not try to compile and run a test GLIB program.
1325
 
1326
`--with-libart-prefix=PFX'
1327
     Prefix where libart is installed (optional).
1328
 
1329
`--with-libart-exec-prefix=PFX'
1330
     Exec prefix where libart is installed (optional).
1331
 
1332
`--disable-libarttest'
1333
     Do not try to compile and run a test libart program.
1334
 
1335
 
1336

1337
File: gccinstall.info,  Node: Building,  Next: Testing,  Prev: Configuration,  Up: Installing GCC
1338
 
1339
5 Building
1340
**********
1341
 
1342
   Now that GCC is configured, you are ready to build the compiler and
1343
runtime libraries.
1344
 
1345
   Some commands executed when making the compiler may fail (return a
1346
nonzero status) and be ignored by `make'.  These failures, which are
1347
often due to files that were not found, are expected, and can safely be
1348
ignored.
1349
 
1350
   It is normal to have compiler warnings when compiling certain files.
1351
Unless you are a GCC developer, you can generally ignore these warnings
1352
unless they cause compilation to fail.  Developers should attempt to fix
1353
any warnings encountered, however they can temporarily continue past
1354
warnings-as-errors by specifying the configure flag `--disable-werror'.
1355
 
1356
   On certain old systems, defining certain environment variables such
1357
as `CC' can interfere with the functioning of `make'.
1358
 
1359
   If you encounter seemingly strange errors when trying to build the
1360
compiler in a directory other than the source directory, it could be
1361
because you have previously configured the compiler in the source
1362
directory.  Make sure you have done all the necessary preparations.
1363
 
1364
   If you build GCC on a BSD system using a directory stored in an old
1365
System V file system, problems may occur in running `fixincludes' if the
1366
System V file system doesn't support symbolic links.  These problems
1367
result in a failure to fix the declaration of `size_t' in
1368
`sys/types.h'.  If you find that `size_t' is a signed type and that
1369
type mismatches occur, this could be the cause.
1370
 
1371
   The solution is not to use such a directory for building GCC.
1372
 
1373
   When building from SVN or snapshots, or if you modify parser sources,
1374
you need the Bison parser generator installed.  If you do not modify
1375
parser sources, releases contain the Bison-generated files and you do
1376
not need Bison installed to build them.
1377
 
1378
   When building from SVN or snapshots, or if you modify Texinfo
1379
documentation, you need version 4.4 or later of Texinfo installed if you
1380
want Info documentation to be regenerated.  Releases contain Info
1381
documentation pre-built for the unmodified documentation in the release.
1382
 
1383
5.1 Building a native compiler
1384
==============================
1385
 
1386
For a native build, the default configuration is to perform a 3-stage
1387
bootstrap of the compiler when `make' is invoked.  This will build the
1388
entire GCC system and ensure that it compiles itself correctly.  It can
1389
be disabled with the `--disable-bootstrap' parameter to `configure',
1390
but bootstrapping is suggested because the compiler will be tested more
1391
completely and could also have better performance.
1392
 
1393
   The bootstrapping process will complete the following steps:
1394
 
1395
   * Build tools necessary to build the compiler.
1396
 
1397
   * Perform a 3-stage bootstrap of the compiler.  This includes
1398
     building three times the target tools for use by the compiler such
1399
     as binutils (bfd, binutils, gas, gprof, ld, and opcodes) if they
1400
     have been individually linked or moved into the top level GCC
1401
     source tree before configuring.
1402
 
1403
   * Perform a comparison test of the stage2 and stage3 compilers.
1404
 
1405
   * Build runtime libraries using the stage3 compiler from the
1406
     previous step.
1407
 
1408
 
1409
   If you are short on disk space you might consider `make
1410
bootstrap-lean' instead.  The sequence of compilation is the same
1411
described above, but object files from the stage1 and stage2 of the
1412
3-stage bootstrap of the compiler are deleted as soon as they are no
1413
longer needed.
1414
 
1415
   If you want to save additional space during the bootstrap and in the
1416
final installation as well, you can build the compiler binaries without
1417
debugging information as in the following example.  This will save
1418
roughly 40% of disk space both for the bootstrap and the final
1419
installation.  (Libraries will still contain debugging information.)
1420
 
1421
          make CFLAGS='-O' LIBCFLAGS='-g -O2' \
1422
            LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap
1423
 
1424
   If you wish to use non-default GCC flags when compiling the stage2
1425
and stage3 compilers, set `BOOT_CFLAGS' on the command line when doing
1426
`make'.  Non-default optimization flags are less well tested here than
1427
the default of `-g -O2', but should still work.  In a few cases, you
1428
may find that you need to specify special flags such as `-msoft-float'
1429
here to complete the bootstrap; or, if the native compiler miscompiles
1430
the stage1 compiler, you may need to work around this, by choosing
1431
`BOOT_CFLAGS' to avoid the parts of the stage1 compiler that were
1432
miscompiled, or by using `make bootstrap4' to increase the number of
1433
stages of bootstrap.
1434
 
1435
   Note that using non-standard `CFLAGS' can cause bootstrap to fail if
1436
these trigger a warning with the new compiler.  For example using `-O2
1437
-g -mcpu=i686' on `i686-pc-linux-gnu' will cause bootstrap failure as
1438
`-mcpu=' is deprecated in 3.4.0 and above.
1439
 
1440
   If you used the flag `--enable-languages=...' to restrict the
1441
compilers to be built, only those you've actually enabled will be
1442
built.  This will of course only build those runtime libraries, for
1443
which the particular compiler has been built.  Please note, that
1444
re-defining `LANGUAGES' when calling `make' *does not* work anymore!
1445
 
1446
   If the comparison of stage2 and stage3 fails, this normally indicates
1447
that the stage2 compiler has compiled GCC incorrectly, and is therefore
1448
a potentially serious bug which you should investigate and report.  (On
1449
a few systems, meaningful comparison of object files is impossible; they
1450
always appear "different".  If you encounter this problem, you will
1451
need to disable comparison in the `Makefile'.)
1452
 
1453
   If you do not want to bootstrap your compiler, you can configure with
1454
`--disable-bootstrap'.  In particular cases, you may want to bootstrap
1455
your compiler even if the target system is not the same as the one you
1456
are building on: for example, you could build a
1457
`powerpc-unknown-linux-gnu' toolchain on a
1458
`powerpc64-unknown-linux-gnu' host.  In this case, pass
1459
`--enable-bootstrap' to the configure script.
1460
 
1461
5.2 Building a cross compiler
1462
=============================
1463
 
1464
When building a cross compiler, it is not generally possible to do a
1465
3-stage bootstrap of the compiler.  This makes for an interesting
1466
problem as parts of GCC can only be built with GCC.
1467
 
1468
   To build a cross compiler, we first recommend building and
1469
installing a native compiler.  You can then use the native GCC compiler
1470
to build the cross compiler.  The installed native compiler needs to be
1471
GCC version 2.95 or later.
1472
 
1473
   Assuming you have already installed a native copy of GCC and
1474
configured your cross compiler, issue the command `make', which
1475
performs the following steps:
1476
 
1477
   * Build host tools necessary to build the compiler.
1478
 
1479
   * Build target tools for use by the compiler such as binutils (bfd,
1480
     binutils, gas, gprof, ld, and opcodes) if they have been
1481
     individually linked or moved into the top level GCC source tree
1482
     before configuring.
1483
 
1484
   * Build the compiler (single stage only).
1485
 
1486
   * Build runtime libraries using the compiler from the previous step.
1487
 
1488
   Note that if an error occurs in any step the make process will exit.
1489
 
1490
   If you are not building GNU binutils in the same source tree as GCC,
1491
you will need a cross-assembler and cross-linker installed before
1492
configuring GCC.  Put them in the directory `PREFIX/TARGET/bin'.  Here
1493
is a table of the tools you should put in this directory:
1494
 
1495
`as'
1496
     This should be the cross-assembler.
1497
 
1498
`ld'
1499
     This should be the cross-linker.
1500
 
1501
`ar'
1502
     This should be the cross-archiver: a program which can manipulate
1503
     archive files (linker libraries) in the target machine's format.
1504
 
1505
`ranlib'
1506
     This should be a program to construct a symbol table in an archive
1507
     file.
1508
 
1509
   The installation of GCC will find these programs in that directory,
1510
and copy or link them to the proper place to for the cross-compiler to
1511
find them when run later.
1512
 
1513
   The easiest way to provide these files is to build the Binutils
1514
package.  Configure it with the same `--host' and `--target' options
1515
that you use for configuring GCC, then build and install them.  They
1516
install their executables automatically into the proper directory.
1517
Alas, they do not support all the targets that GCC supports.
1518
 
1519
   If you are not building a C library in the same source tree as GCC,
1520
you should also provide the target libraries and headers before
1521
configuring GCC, specifying the directories with `--with-sysroot' or
1522
`--with-headers' and `--with-libs'.  Many targets also require "start
1523
files" such as `crt0.o' and `crtn.o' which are linked into each
1524
executable.  There may be several alternatives for `crt0.o', for use
1525
with profiling or other compilation options.  Check your target's
1526
definition of `STARTFILE_SPEC' to find out what start files it uses.
1527
 
1528
5.3 Building in parallel
1529
========================
1530
 
1531
GNU Make 3.79 and above, which is necessary to build GCC, support
1532
building in parallel.  To activate this, you can use `make -j 2'
1533
instead of `make'.  You can also specify a bigger number, and in most
1534
cases using a value greater than the number of processors in your
1535
machine will result in fewer and shorter I/O latency hits, thus
1536
improving overall throughput; this is especially true for slow drives
1537
and network filesystems.
1538
 
1539
5.4 Building the Ada compiler
1540
=============================
1541
 
1542
In order to build GNAT, the Ada compiler, you need a working GNAT
1543
compiler (GNAT version 3.14 or later, or GCC version 3.1 or later).
1544
This includes GNAT tools such as `gnatmake' and `gnatlink', since the
1545
Ada front end is written in Ada and uses some GNAT-specific extensions.
1546
 
1547
   In order to build a cross compiler, it is suggested to install the
1548
new compiler as native first, and then use it to build the cross
1549
compiler.
1550
 
1551
   `configure' does not test whether the GNAT installation works and
1552
has a sufficiently recent version; if too old a GNAT version is
1553
installed, the build will fail unless `--enable-languages' is used to
1554
disable building the Ada front end.
1555
 
1556
5.5 Building with profile feedback
1557
==================================
1558
 
1559
It is possible to use profile feedback to optimize the compiler itself.
1560
This should result in a faster compiler binary.  Experiments done on
1561
x86 using gcc 3.3 showed approximately 7 percent speedup on compiling C
1562
programs.  To bootstrap the compiler with profile feedback, use `make
1563
profiledbootstrap'.
1564
 
1565
   When `make profiledbootstrap' is run, it will first build a `stage1'
1566
compiler.  This compiler is used to build a `stageprofile' compiler
1567
instrumented to collect execution counts of instruction and branch
1568
probabilities.  Then runtime libraries are compiled with profile
1569
collected.  Finally a `stagefeedback' compiler is built using the
1570
information collected.
1571
 
1572
   Unlike standard bootstrap, several additional restrictions apply.
1573
The compiler used to build `stage1' needs to support a 64-bit integral
1574
type.  It is recommended to only use GCC for this.  Also parallel make
1575
is currently not supported since collisions in profile collecting may
1576
occur.
1577
 
1578

1579
File: gccinstall.info,  Node: Testing,  Next: Final install,  Prev: Building,  Up: Installing GCC
1580
 
1581
6 Installing GCC: Testing
1582
*************************
1583
 
1584
   Before you install GCC, we encourage you to run the testsuites and to
1585
compare your results with results from a similar configuration that have
1586
been submitted to the gcc-testresults mailing list.  Some of these
1587
archived results are linked from the build status lists at
1588
`http://gcc.gnu.org/buildstat.html', although not everyone who reports
1589
a successful build runs the testsuites and submits the results.  This
1590
step is optional and may require you to download additional software,
1591
but it can give you confidence in your new GCC installation or point out
1592
problems before you install and start using your new GCC.
1593
 
1594
   First, you must have downloaded the testsuites.  These are part of
1595
the full distribution, but if you downloaded the "core" compiler plus
1596
any front ends, you must download the testsuites separately.
1597
 
1598
   Second, you must have the testing tools installed.  This includes
1599
DejaGnu, Tcl, and Expect; the DejaGnu site has links to these.
1600
 
1601
   If the directories where `runtest' and `expect' were installed are
1602
not in the `PATH', you may need to set the following environment
1603
variables appropriately, as in the following example (which assumes
1604
that DejaGnu has been installed under `/usr/local'):
1605
 
1606
          TCL_LIBRARY = /usr/local/share/tcl8.0
1607
          DEJAGNULIBS = /usr/local/share/dejagnu
1608
 
1609
   (On systems such as Cygwin, these paths are required to be actual
1610
paths, not mounts or links; presumably this is due to some lack of
1611
portability in the DejaGnu code.)
1612
 
1613
   Finally, you can run the testsuite (which may take a long time):
1614
          cd OBJDIR; make -k check
1615
 
1616
   This will test various components of GCC, such as compiler front
1617
ends and runtime libraries.  While running the testsuite, DejaGnu might
1618
emit some harmless messages resembling `WARNING: Couldn't find the
1619
global config file.' or `WARNING: Couldn't find tool init file' that
1620
can be ignored.
1621
 
1622
6.1 How can you run the testsuite on selected tests?
1623
====================================================
1624
 
1625
In order to run sets of tests selectively, there are targets `make
1626
check-gcc' and `make check-g++' in the `gcc' subdirectory of the object
1627
directory.  You can also just run `make check' in a subdirectory of the
1628
object directory.
1629
 
1630
   A more selective way to just run all `gcc' execute tests in the
1631
testsuite is to use
1632
 
1633
         make check-gcc RUNTESTFLAGS="execute.exp OTHER-OPTIONS"
1634
 
1635
   Likewise, in order to run only the `g++' "old-deja" tests in the
1636
testsuite with filenames matching `9805*', you would use
1637
 
1638
         make check-g++ RUNTESTFLAGS="old-deja.exp=9805* OTHER-OPTIONS"
1639
 
1640
   The `*.exp' files are located in the testsuite directories of the GCC
1641
source, the most important ones being `compile.exp', `execute.exp',
1642
`dg.exp' and `old-deja.exp'.  To get a list of the possible `*.exp'
1643
files, pipe the output of `make check' into a file and look at the
1644
`Running ...  .exp' lines.
1645
 
1646
6.2 Passing options and running multiple testsuites
1647
===================================================
1648
 
1649
You can pass multiple options to the testsuite using the
1650
`--target_board' option of DejaGNU, either passed as part of
1651
`RUNTESTFLAGS', or directly to `runtest' if you prefer to work outside
1652
the makefiles.  For example,
1653
 
1654
         make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fno-strength-reduce"
1655
 
1656
   will run the standard `g++' testsuites ("unix" is the target name
1657
for a standard native testsuite situation), passing `-O3
1658
-fno-strength-reduce' to the compiler on every test, i.e., slashes
1659
separate options.
1660
 
1661
   You can run the testsuites multiple times using combinations of
1662
options with a syntax similar to the brace expansion of popular shells:
1663
 
1664
         ..."--target_board=arm-sim/{-mhard-float,-msoft-float}{-O1,-O2,-O3,}"
1665
 
1666
   (Note the empty option caused by the trailing comma in the final
1667
group.)  The following will run each testsuite eight times using the
1668
`arm-sim' target, as if you had specified all possible combinations
1669
yourself:
1670
 
1671
         --target_board=arm-sim/-mhard-float/-O1
1672
         --target_board=arm-sim/-mhard-float/-O2
1673
         --target_board=arm-sim/-mhard-float/-O3
1674
         --target_board=arm-sim/-mhard-float
1675
         --target_board=arm-sim/-msoft-float/-O1
1676
         --target_board=arm-sim/-msoft-float/-O2
1677
         --target_board=arm-sim/-msoft-float/-O3
1678
         --target_board=arm-sim/-msoft-float
1679
 
1680
   They can be combined as many times as you wish, in arbitrary ways.
1681
This list:
1682
 
1683
         ..."--target_board=unix/-Wextra{-O3,-fno-strength-reduce}{-fomit-frame-pointer,}"
1684
 
1685
   will generate four combinations, all involving `-Wextra'.
1686
 
1687
   The disadvantage to this method is that the testsuites are run in
1688
serial, which is a waste on multiprocessor systems.  For users with GNU
1689
Make and a shell which performs brace expansion, you can run the
1690
testsuites in parallel by having the shell perform the combinations and
1691
`make' do the parallel runs.  Instead of using `--target_board', use a
1692
special makefile target:
1693
 
1694
         make -jN check-TESTSUITE//TEST-TARGET/OPTION1/OPTION2/...
1695
 
1696
   For example,
1697
 
1698
         make -j3 check-gcc//sh-hms-sim/{-m1,-m2,-m3,-m3e,-m4}/{,-nofpu}
1699
 
1700
   will run three concurrent "make-gcc" testsuites, eventually testing
1701
all ten combinations as described above.  Note that this is currently
1702
only supported in the `gcc' subdirectory.  (To see how this works, try
1703
typing `echo' before the example given here.)
1704
 
1705
6.3 Additional testing for Java Class Libraries
1706
===============================================
1707
 
1708
The Java runtime tests can be executed via `make check' in the
1709
`TARGET/libjava/testsuite' directory in the build tree.
1710
 
1711
   The Mauve Project provides a suite of tests for the Java Class
1712
Libraries.  This suite can be run as part of libgcj testing by placing
1713
the Mauve tree within the libjava testsuite at
1714
`libjava/testsuite/libjava.mauve/mauve', or by specifying the location
1715
of that tree when invoking `make', as in `make MAUVEDIR=~/mauve check'.
1716
 
1717
   Jacks is a free testsuite that tests Java compiler front ends.  This
1718
suite can be run as part of libgcj testing by placing the Jacks tree
1719
within the libjava testsuite at `libjava/testsuite/libjava.jacks/jacks'.
1720
 
1721
6.4 How to interpret test results
1722
=================================
1723
 
1724
The result of running the testsuite are various `*.sum' and `*.log'
1725
files in the testsuite subdirectories.  The `*.log' files contain a
1726
detailed log of the compiler invocations and the corresponding results,
1727
the `*.sum' files summarize the results.  These summaries contain
1728
status codes for all tests:
1729
 
1730
   * PASS: the test passed as expected
1731
 
1732
   * XPASS: the test unexpectedly passed
1733
 
1734
   * FAIL: the test unexpectedly failed
1735
 
1736
   * XFAIL: the test failed as expected
1737
 
1738
   * UNSUPPORTED: the test is not supported on this platform
1739
 
1740
   * ERROR: the testsuite detected an error
1741
 
1742
   * WARNING: the testsuite detected a possible problem
1743
 
1744
   It is normal for some tests to report unexpected failures.  At the
1745
current time the testing harness does not allow fine grained control
1746
over whether or not a test is expected to fail.  This problem should be
1747
fixed in future releases.
1748
 
1749
6.5 Submitting test results
1750
===========================
1751
 
1752
If you want to report the results to the GCC project, use the
1753
`contrib/test_summary' shell script.  Start it in the OBJDIR with
1754
 
1755
         SRCDIR/contrib/test_summary -p your_commentary.txt \
1756
             -m gcc-testresults@gcc.gnu.org |sh
1757
 
1758
   This script uses the `Mail' program to send the results, so make
1759
sure it is in your `PATH'.  The file `your_commentary.txt' is prepended
1760
to the testsuite summary and should contain any special remarks you
1761
have on your results or your build environment.  Please do not edit the
1762
testsuite result block or the subject line, as these messages may be
1763
automatically processed.
1764
 
1765

1766
File: gccinstall.info,  Node: Final install,  Prev: Testing,  Up: Installing GCC
1767
 
1768
7 Installing GCC: Final installation
1769
************************************
1770
 
1771
   Now that GCC has been built (and optionally tested), you can install
1772
it with
1773
     cd OBJDIR; make install
1774
 
1775
   We strongly recommend to install into a target directory where there
1776
is no previous version of GCC present.
1777
 
1778
   That step completes the installation of GCC; user level binaries can
1779
be found in `PREFIX/bin' where PREFIX is the value you specified with
1780
the `--prefix' to configure (or `/usr/local' by default).  (If you
1781
specified `--bindir', that directory will be used instead; otherwise,
1782
if you specified `--exec-prefix', `EXEC-PREFIX/bin' will be used.)
1783
Headers for the C++ and Java libraries are installed in
1784
`PREFIX/include'; libraries in `LIBDIR' (normally `PREFIX/lib');
1785
internal parts of the compiler in `LIBDIR/gcc' and `LIBEXECDIR/gcc';
1786
documentation in info format in `INFODIR' (normally `PREFIX/info').
1787
 
1788
   When installing cross-compilers, GCC's executables are not only
1789
installed into `BINDIR', that is, `EXEC-PREFIX/bin', but additionally
1790
into `EXEC-PREFIX/TARGET-ALIAS/bin', if that directory exists.
1791
Typically, such "tooldirs" hold target-specific binutils, including
1792
assembler and linker.
1793
 
1794
   Installation into a temporary staging area or into a `chroot' jail
1795
can be achieved with the command
1796
 
1797
     make DESTDIR=PATH-TO-ROOTDIR install
1798
 
1799
where PATH-TO-ROOTDIR is the absolute path of a directory relative to
1800
which all installation paths will be interpreted.  Note that the
1801
directory specified by `DESTDIR' need not exist yet; it will be created
1802
if necessary.
1803
 
1804
   There is a subtle point with tooldirs and `DESTDIR': If you relocate
1805
a cross-compiler installation with e.g. `DESTDIR=ROOTDIR', then the
1806
directory `ROOTDIR/EXEC-PREFIX/TARGET-ALIAS/bin' will be filled with
1807
duplicated GCC executables only if it already exists, it will not be
1808
created otherwise.  This is regarded as a feature, not as a bug,
1809
because it gives slightly more control to the packagers using the
1810
`DESTDIR' feature.
1811
 
1812
   If you are bootstrapping a released version of GCC then please
1813
quickly review the build status page for your release, available from
1814
`http://gcc.gnu.org/buildstat.html'.  If your system is not listed for
1815
the version of GCC that you built, send a note to 
1816
indicating that you successfully built and installed GCC.  Include the
1817
following information:
1818
 
1819
   * Output from running `SRCDIR/config.guess'.  Do not send that file
1820
     itself, just the one-line output from running it.
1821
 
1822
   * The output of `gcc -v' for your newly installed `gcc'.  This tells
1823
     us which version of GCC you built and the options you passed to
1824
     configure.
1825
 
1826
   * Whether you enabled all languages or a subset of them.  If you
1827
     used a full distribution then this information is part of the
1828
     configure options in the output of `gcc -v', but if you downloaded
1829
     the "core" compiler plus additional front ends then it isn't
1830
     apparent which ones you built unless you tell us about it.
1831
 
1832
   * If the build was for GNU/Linux, also include:
1833
        * The distribution name and version (e.g., Red Hat 7.1 or
1834
          Debian 2.2.3); this information should be available from
1835
          `/etc/issue'.
1836
 
1837
        * The version of the Linux kernel, available from `uname
1838
          --version' or `uname -a'.
1839
 
1840
        * The version of glibc you used; for RPM-based systems like Red
1841
          Hat, Mandrake, and SuSE type `rpm -q glibc' to get the glibc
1842
          version, and on systems like Debian and Progeny use `dpkg -l
1843
          libc6'.
1844
     For other systems, you can include similar information if you
1845
     think it is relevant.
1846
 
1847
   * Any other information that you think would be useful to people
1848
     building GCC on the same configuration.  The new entry in the
1849
     build status list will include a link to the archived copy of your
1850
     message.
1851
 
1852
   We'd also like to know if the *Note host/target specific
1853
installation notes: Specific.  didn't include your host/target
1854
information or if that information is incomplete or out of date.  Send
1855
a note to  detailing how the information should be
1856
changed.
1857
 
1858
   If you find a bug, please report it following the bug reporting
1859
guidelines.
1860
 
1861
   If you want to print the GCC manuals, do `cd OBJDIR; make dvi'.  You
1862
will need to have `texi2dvi' (version at least 4.4) and TeX installed.
1863
This creates a number of `.dvi' files in subdirectories of `OBJDIR';
1864
these may be converted for printing with programs such as `dvips'.
1865
Alternately, by using `make pdf' in place of `make dvi', you can create
1866
documentation in the form of `.pdf' files; this requires `texi2pdf',
1867
which is included with Texinfo version 4.8 and later.  You can also buy
1868
printed manuals from the Free Software Foundation, though such manuals
1869
may not be for the most recent version of GCC.
1870
 
1871
   If you would like to generate online HTML documentation, do `cd
1872
OBJDIR; make html' and HTML will be generated for the gcc manuals in
1873
`OBJDIR/gcc/HTML'.
1874
 
1875

1876
File: gccinstall.info,  Node: Binaries,  Next: Specific,  Prev: Installing GCC,  Up: Top
1877
 
1878
8 Installing GCC: Binaries
1879
**************************
1880
 
1881
   We are often asked about pre-compiled versions of GCC.  While we
1882
cannot provide these for all platforms, below you'll find links to
1883
binaries for various platforms where creating them by yourself is not
1884
easy due to various reasons.
1885
 
1886
   Please note that we did not create these binaries, nor do we support
1887
them.  If you have any problems installing them, please contact their
1888
makers.
1889
 
1890
   * AIX:
1891
        * Bull's Freeware and Shareware Archive for AIX;
1892
 
1893
        * UCLA Software Library for AIX.
1894
 
1895
   * DOS--DJGPP.
1896
 
1897
   * Renesas H8/300[HS]--GNU Development Tools for the Renesas
1898
     H8/300[HS] Series.
1899
 
1900
   * HP-UX:
1901
        * HP-UX Porting Center;
1902
 
1903
        * Binaries for HP-UX 11.00 at Aachen University of Technology.
1904
 
1905
   * Motorola 68HC11/68HC12--GNU Development Tools for the Motorola
1906
     68HC11/68HC12.
1907
 
1908
   * SCO OpenServer/Unixware.
1909
 
1910
   * Solaris 2 (SPARC, Intel)--Sunfreeware.
1911
 
1912
   * SGI--SGI Freeware.
1913
 
1914
   * Microsoft Windows:
1915
        * The Cygwin project;
1916
 
1917
        * The MinGW project.
1918
 
1919
   * The Written Word offers binaries for AIX 4.3.2.  IRIX 6.5, Digital
1920
     UNIX 4.0D and 5.1, GNU/Linux (i386), HP-UX 10.20, 11.00, and
1921
     11.11, and Solaris/SPARC 2.5.1, 2.6, 7, 8, and 9.
1922
 
1923
   * OpenPKG offers binaries for quite a number of platforms.
1924
 
1925
   * The GFortran Wiki has links to GNU Fortran binaries for several
1926
     platforms.
1927
 
1928
   In addition to those specific offerings, you can get a binary
1929
distribution CD-ROM from the Free Software Foundation.  It contains
1930
binaries for a number of platforms, and includes not only GCC, but
1931
other stuff as well.  The current CD does not contain the latest
1932
version of GCC, but it should allow bootstrapping the compiler.  An
1933
updated version of that disk is in the works.
1934
 
1935

1936
File: gccinstall.info,  Node: Specific,  Next: Old,  Prev: Binaries,  Up: Top
1937
 
1938
9 Host/target specific installation notes for GCC
1939
*************************************************
1940
 
1941
   Please read this document carefully _before_ installing the GNU
1942
Compiler Collection on your machine.
1943
 
1944
   Note that this list of install notes is _not_ a list of supported
1945
hosts or targets.  Not all supported hosts and targets are listed here,
1946
only the ones that require host-specific or target-specific information
1947
are.
1948
 
1949
alpha*-*-*
1950
==========
1951
 
1952
This section contains general configuration information for all
1953
alpha-based platforms using ELF (in particular, ignore this section for
1954
DEC OSF/1, Digital UNIX and Tru64 UNIX).  In addition to reading this
1955
section, please read all other sections that match your target.
1956
 
1957
   We require binutils 2.11.2 or newer.  Previous binutils releases had
1958
a number of problems with DWARF 2 debugging information, not the least
1959
of which is incorrect linking of shared libraries.
1960
 
1961
alpha*-dec-osf*
1962
===============
1963
 
1964
Systems using processors that implement the DEC Alpha architecture and
1965
are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
1966
Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
1967
 
1968
   As of GCC 3.2, versions before `alpha*-dec-osf4' are no longer
1969
supported.  (These are the versions which identify themselves as DEC
1970
OSF/1.)
1971
 
1972
   In Digital Unix V4.0, virtual memory exhausted bootstrap failures
1973
may be fixed by configuring with `--with-gc=simple', reconfiguring
1974
Kernel Virtual Memory and Swap parameters per the `/usr/sbin/sys_check'
1975
Tuning Suggestions, or applying the patch in
1976
`http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html'.
1977
 
1978
   In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
1979
currently (2001-06-13) work with `mips-tfile'.  As a workaround, we
1980
need to use the old assembler, invoked via the barely documented
1981
`-oldas' option.  To bootstrap GCC, you either need to use the Compaq C
1982
Compiler:
1983
 
1984
        % CC=cc SRCDIR/configure [OPTIONS] [TARGET]
1985
 
1986
   or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX
1987
V4.0:
1988
 
1989
        % CC=gcc -Wa,-oldas SRCDIR/configure [OPTIONS] [TARGET]
1990
 
1991
   As of GNU binutils 2.11.2, neither GNU `as' nor GNU `ld' are
1992
supported on Tru64 UNIX, so you must not configure GCC with
1993
`--with-gnu-as' or `--with-gnu-ld'.
1994
 
1995
   GCC writes a `.verstamp' directive to the assembler output file
1996
unless it is built as a cross-compiler.  It gets the version to use from
1997
the system header file `/usr/include/stamp.h'.  If you install a new
1998
version of DEC Unix, you should rebuild GCC to pick up the new version
1999
stamp.
2000
 
2001
   Note that since the Alpha is a 64-bit architecture, cross-compilers
2002
from 32-bit machines will not generate code as efficient as that
2003
generated when the compiler is running on a 64-bit machine because many
2004
optimizations that depend on being able to represent a word on the
2005
target in an integral value on the host cannot be performed.  Building
2006
cross-compilers on the Alpha for 32-bit machines has only been tested in
2007
a few cases and may not work properly.
2008
 
2009
   `make compare' may fail on old versions of DEC Unix unless you add
2010
`-save-temps' to `CFLAGS'.  On these systems, the name of the assembler
2011
input file is stored in the object file, and that makes comparison fail
2012
if it differs between the `stage1' and `stage2' compilations.  The
2013
option `-save-temps' forces a fixed name to be used for the assembler
2014
input file, instead of a randomly chosen name in `/tmp'.  Do not add
2015
`-save-temps' unless the comparisons fail without that option.  If you
2016
add `-save-temps', you will have to manually delete the `.i' and `.s'
2017
files after each series of compilations.
2018
 
2019
   GCC now supports both the native (ECOFF) debugging format used by DBX
2020
and GDB and an encapsulated STABS format for use only with GDB.  See the
2021
discussion of the `--with-stabs' option of `configure' above for more
2022
information on these formats and how to select them.
2023
 
2024
   There is a bug in DEC's assembler that produces incorrect line
2025
numbers for ECOFF format when the `.align' directive is used.  To work
2026
around this problem, GCC will not emit such alignment directives while
2027
writing ECOFF format debugging information even if optimization is
2028
being performed.  Unfortunately, this has the very undesirable
2029
side-effect that code addresses when `-O' is specified are different
2030
depending on whether or not `-g' is also specified.
2031
 
2032
   To avoid this behavior, specify `-gstabs+' and use GDB instead of
2033
DBX.  DEC is now aware of this problem with the assembler and hopes to
2034
provide a fix shortly.
2035
 
2036
alphaev5-cray-unicosmk*
2037
=======================
2038
 
2039
Cray T3E systems running Unicos/Mk.
2040
 
2041
   This port is incomplete and has many known bugs.  We hope to improve
2042
the support for this target soon.  Currently, only the C front end is
2043
supported, and it is not possible to build parallel applications.  Cray
2044
modules are not supported; in particular, Craylibs are assumed to be in
2045
`/opt/ctl/craylibs/craylibs'.
2046
 
2047
   On this platform, you need to tell GCC where to find the assembler
2048
and the linker.  The simplest way to do so is by providing `--with-as'
2049
and `--with-ld' to `configure', e.g.
2050
 
2051
         configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld \
2052
           --enable-languages=c
2053
 
2054
   The comparison test at the end of the bootstrapping process fails on
2055
Unicos/Mk because the assembler inserts timestamps into object files.
2056
You should be able to work around this by doing `make all' after
2057
getting this failure.
2058
 
2059
arc-*-elf
2060
=========
2061
 
2062
Argonaut ARC processor.  This configuration is intended for embedded
2063
systems.
2064
 
2065
arm-*-elf
2066
=========
2067
 
2068
xscale-*-*
2069
==========
2070
 
2071
ARM-family processors.  Subtargets that use the ELF object format
2072
require GNU binutils 2.13 or newer.  Such subtargets include:
2073
`arm-*-freebsd', `arm-*-netbsdelf', `arm-*-*linux', `arm-*-rtems' and
2074
`arm-*-kaos'.
2075
 
2076
arm-*-coff
2077
==========
2078
 
2079
ARM-family processors.  Note that there are two different varieties of
2080
PE format subtarget supported: `arm-wince-pe' and `arm-pe' as well as a
2081
standard COFF target `arm-*-coff'.
2082
 
2083
arm-*-aout
2084
==========
2085
 
2086
ARM-family processors.  These targets support the AOUT file format:
2087
`arm-*-aout', `arm-*-netbsd'.
2088
 
2089
avr
2090
===
2091
 
2092
ATMEL AVR-family micro controllers.  These are used in embedded
2093
applications.  There are no standard Unix configurations.  *Note AVR
2094
Options: (gcc)AVR Options, for the list of supported MCU types.
2095
 
2096
   Use `configure --target=avr --enable-languages="c"' to configure GCC.
2097
 
2098
   Further installation notes and other useful information about AVR
2099
tools can also be obtained from:
2100
 
2101
   * http://www.nongnu.org/avr/
2102
 
2103
   * http://home.overta.ru/users/denisc/
2104
 
2105
   * http://www.amelek.gda.pl/avr/
2106
 
2107
   We _strongly_ recommend using binutils 2.13 or newer.
2108
 
2109
   The following error:
2110
       Error: register required
2111
 
2112
   indicates that you should upgrade to a newer version of the binutils.
2113
 
2114
Blackfin
2115
========
2116
 
2117
The Blackfin processor, an Analog Devices DSP.  *Note Blackfin Options:
2118
(gcc)Blackfin Options,
2119
 
2120
   More information, and a version of binutils with support for this
2121
processor, is available at `http://blackfin.uclinux.org'
2122
 
2123
c4x
2124
===
2125
 
2126
Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal
2127
Processors.  These are used in embedded applications.  There are no
2128
standard Unix configurations.  *Note TMS320C3x/C4x Options:
2129
(gcc)TMS320C3x/C4x Options, for the list of supported MCU types.
2130
 
2131
   GCC can be configured as a cross compiler for both the C3x and C4x
2132
architectures on the same system.  Use `configure --target=c4x
2133
--enable-languages="c,c++"' to configure.
2134
 
2135
   Further installation notes and other useful information about C4x
2136
tools can also be obtained from:
2137
 
2138
   * http://www.elec.canterbury.ac.nz/c4x/
2139
 
2140
CRIS
2141
====
2142
 
2143
CRIS is the CPU architecture in Axis Communications ETRAX
2144
system-on-a-chip series.  These are used in embedded applications.
2145
 
2146
   *Note CRIS Options: (gcc)CRIS Options, for a list of CRIS-specific
2147
options.
2148
 
2149
   There are a few different CRIS targets:
2150
`cris-axis-aout'
2151
     Old target.  Includes a multilib for the `elinux' a.out-based
2152
     target.  No multilibs for newer architecture variants.
2153
 
2154
`cris-axis-elf'
2155
     Mainly for monolithic embedded systems.  Includes a multilib for
2156
     the `v10' core used in `ETRAX 100 LX'.
2157
 
2158
`cris-axis-linux-gnu'
2159
     A GNU/Linux port for the CRIS architecture, currently targeting
2160
     `ETRAX 100 LX' by default.
2161
 
2162
   For `cris-axis-aout' and `cris-axis-elf' you need binutils 2.11 or
2163
newer.  For `cris-axis-linux-gnu' you need binutils 2.12 or newer.
2164
 
2165
   Pre-packaged tools can be obtained from
2166
`ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/'.  More
2167
information about this platform is available at
2168
`http://developer.axis.com/'.
2169
 
2170
CRX
2171
===
2172
 
2173
The CRX CompactRISC architecture is a low-power 32-bit architecture with
2174
fast context switching and architectural extensibility features.
2175
 
2176
   *Note CRX Options: (gcc)CRX Options,
2177
 
2178
   Use `configure --target=crx-elf --enable-languages=c,c++' to
2179
configure GCC for building a CRX cross-compiler. The option
2180
`--target=crx-elf' is also used to build the `newlib' C library for CRX.
2181
 
2182
   It is also possible to build libstdc++-v3 for the CRX architecture.
2183
This needs to be done in a separate step with the following configure
2184
settings: `gcc/libstdc++-v3/configure --host=crx-elf --with-newlib
2185
--enable-sjlj-exceptions --enable-cxx-flags='-fexceptions -frtti''
2186
 
2187
DOS
2188
===
2189
 
2190
Please have a look at the binaries page.
2191
 
2192
   You cannot install GCC by itself on MSDOS; it will not compile under
2193
any MSDOS compiler except itself.  You need to get the complete
2194
compilation package DJGPP, which includes binaries as well as sources,
2195
and includes all the necessary compilation tools and libraries.
2196
 
2197
*-*-freebsd*
2198
============
2199
 
2200
The version of binutils installed in `/usr/bin' probably works with
2201
this release of GCC.  However, on FreeBSD 4, bootstrapping against the
2202
latest FSF binutils is known to improve overall testsuite results; and,
2203
on FreeBSD/alpha, using binutils 2.14 or later is required to build
2204
libjava.
2205
 
2206
   Support for FreeBSD 1 was discontinued in GCC 3.2.
2207
 
2208
   Support for FreeBSD 2 will be discontinued after GCC 3.4.  The
2209
following was true for GCC 3.1 but the current status is unknown.  For
2210
FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All configuration
2211
support and files as shipped with GCC 2.95 are still in place.  FreeBSD
2212
2.2.7 has been known to bootstrap completely; however, it is unknown
2213
which version of binutils was used (it is assumed that it was the
2214
system copy in `/usr/bin') and C++ EH failures were noted.
2215
 
2216
   For FreeBSD using the ELF file format: DWARF 2 debugging is now the
2217
default for all CPU architectures.  It had been the default on
2218
FreeBSD/alpha since its inception.  You may use `-gstabs' instead of
2219
`-g', if you really want the old debugging format.  There are no known
2220
issues with mixing object files and libraries with different debugging
2221
formats.  Otherwise, this release of GCC should now match more of the
2222
configuration used in the stock FreeBSD configuration of GCC.  In
2223
particular, `--enable-threads' is now configured by default.  However,
2224
as a general user, do not attempt to replace the system compiler with
2225
this release.  Known to bootstrap and check with good results on
2226
FreeBSD 4.9-STABLE and 5-CURRENT.  In the past, known to bootstrap and
2227
check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4, 4.5,
2228
4.8-STABLE.
2229
 
2230
   In principle, `--enable-threads' is now compatible with
2231
`--enable-libgcj' on FreeBSD.  However, it has only been built and
2232
tested on `i386-*-freebsd[45]' and `alpha-*-freebsd[45]'.  The static
2233
library may be incorrectly built (symbols are missing at link time).
2234
There is a rare timing-based startup hang (probably involves an
2235
assumption about the thread library).  Multi-threaded boehm-gc
2236
(required for libjava) exposes severe threaded signal-handling bugs on
2237
FreeBSD before 4.5-RELEASE.  Other CPU architectures supported by
2238
FreeBSD will require additional configuration tuning in, at the very
2239
least, both boehm-gc and libffi.
2240
 
2241
   Shared `libgcc_s.so' is now built and installed by default.
2242
 
2243
h8300-hms
2244
=========
2245
 
2246
Renesas H8/300 series of processors.
2247
 
2248
   Please have a look at the binaries page.
2249
 
2250
   The calling convention and structure layout has changed in release
2251
2.6.  All code must be recompiled.  The calling convention now passes
2252
the first three arguments in function calls in registers.  Structures
2253
are no longer a multiple of 2 bytes.
2254
 
2255
hppa*-hp-hpux*
2256
==============
2257
 
2258
Support for HP-UX version 9 and older was discontinued in GCC 3.4.
2259
 
2260
   We require using gas/binutils on all hppa platforms; you may
2261
encounter a variety of problems if you try to use the HP assembler.
2262
 
2263
   Specifically, `-g' does not work on HP-UX (since that system uses a
2264
peculiar debugging format which GCC does not know about), unless you
2265
use GAS and GDB.  It may be helpful to configure GCC with the
2266
`--with-gnu-as' and `--with-as=...' options to ensure that GCC can find
2267
GAS.
2268
 
2269
   If you wish to use the pa-risc 2.0 architecture support with a 32-bit
2270
runtime, you must use gas/binutils 2.11 or newer.
2271
 
2272
   There are two default scheduling models for instructions.  These are
2273
PROCESSOR_7100LC and PROCESSOR_8000.  They are selected from the pa-risc
2274
architecture specified for the target machine when configuring.
2275
PROCESSOR_8000 is the default.  PROCESSOR_7100LC is selected when the
2276
target is a `hppa1*' machine.
2277
 
2278
   The PROCESSOR_8000 model is not well suited to older processors.
2279
Thus, it is important to completely specify the machine architecture
2280
when configuring if you want a model other than PROCESSOR_8000.  The
2281
macro TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
2282
default scheduling model is desired.
2283
 
2284
   As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
2285
through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
2286
This namespace change might cause problems when bootstrapping with an
2287
earlier version of GCC or the HP compiler as essentially the same
2288
namespace is required for an entire build.  This problem can be avoided
2289
in a number of ways.  With HP cc, `UNIX_STD' can be set to `95' or
2290
`98'.  Another way is to add an appropriate set of predefines to `CC'.
2291
The description for the `munix=' option contains a list of the
2292
predefines used with each standard.
2293
 
2294
   As of GCC 4.1, `DWARF2' exception handling is available on HP-UX.
2295
It is now the default.  This exposed a bug in the handling of data
2296
relocations in the GAS assembler.  The handling of 64-bit data
2297
relocations was seriously broken, affecting debugging and exception
2298
support on all `hppa64-*-*' targets.  Under some circumstances, 32-bit
2299
data relocations could also be handled incorrectly.  This problem is
2300
fixed in GAS version 2.16.91 20051125.
2301
 
2302
   GCC versions prior to 4.1 incorrectly passed and returned complex
2303
values.  They are now passed in the same manner as aggregates.
2304
 
2305
   More specific information to `hppa*-hp-hpux*' targets follows.
2306
 
2307
hppa*-hp-hpux10
2308
===============
2309
 
2310
For hpux10.20, we _highly_ recommend you pick up the latest sed patch
2311
`PHCO_19798' from HP.  HP has two sites which provide patches free of
2312
charge:
2313
 
2314
   * `http://us.itrc.hp.com/service/home/home.do' US, Canada,
2315
     Asia-Pacific, and Latin-America.
2316
 
2317
   * `http://europe.itrc.hp.com/service/home/home.do' Europe.
2318
 
2319
   The HP assembler on these systems has some problems.  Most notably
2320
the assembler inserts timestamps into each object file it creates,
2321
causing the 3-stage comparison test to fail during a bootstrap.  You
2322
should be able to continue by saying `make all-host all-target' after
2323
getting the failure from `make'.
2324
 
2325
   GCC 4.0 requires CVS binutils as of April 28, 2004 or later.  Earlier
2326
versions require binutils 2.8 or later.
2327
 
2328
   The C++ ABI has changed incompatibly in GCC 4.0.  COMDAT subspaces
2329
are used for one-only code and data.  This resolves many of the previous
2330
problems in using C++ on this target.  However, the ABI is not
2331
compatible with the one implemented under HP-UX 11 using secondary
2332
definitions.
2333
 
2334
hppa*-hp-hpux11
2335
===============
2336
 
2337
GCC 3.0 and up support HP-UX 11.  GCC 2.95.x is not supported and cannot
2338
be used to compile GCC 3.0 and up.
2339
 
2340
   Refer to binaries for information about obtaining precompiled GCC
2341
binaries for HP-UX.  Precompiled binaries must be obtained to build the
2342
Ada language as it can't be bootstrapped using C.  Ada is only
2343
available for the 32-bit PA-RISC runtime.  The libffi and libjava
2344
haven't been ported to HP-UX and don't build.
2345
 
2346
   Starting with GCC 3.4 an ISO C compiler is required to bootstrap.
2347
The bundled compiler supports only traditional C; you will need either
2348
HP's unbundled compiler, or a binary distribution of GCC.
2349
 
2350
   It is possible to build GCC 3.3 starting with the bundled HP
2351
compiler, but the process requires several steps.  GCC 3.3 can then be
2352
used to build later versions.  The fastjar program contains ISO C code
2353
and can't be built with the HP bundled compiler.  This problem can be
2354
avoided by not building the Java language.  For example, use the
2355
`--enable-languages="c,c++,f77,objc"' option in your configure command.
2356
 
2357
   There are several possible approaches to building the distribution.
2358
Binutils can be built first using the HP tools.  Then, the GCC
2359
distribution can be built.  The second approach is to build GCC first
2360
using the HP tools, then build binutils, then rebuild GCC.  There have
2361
been problems with various binary distributions, so it is best not to
2362
start from a binary distribution.
2363
 
2364
   On 64-bit capable systems, there are two distinct targets.  Different
2365
installation prefixes must be used if both are to be installed on the
2366
same system.  The `hppa[1-2]*-hp-hpux11*' target generates code for the
2367
32-bit PA-RISC runtime architecture and uses the HP linker.  The
2368
`hppa64-hp-hpux11*' target generates 64-bit code for the PA-RISC 2.0
2369
architecture.  The HP and GNU linkers are both supported for this
2370
target.
2371
 
2372
   The script config.guess now selects the target type based on the
2373
compiler detected during configuration.  You must define `PATH' or `CC'
2374
so that configure finds an appropriate compiler for the initial
2375
bootstrap.  When `CC' is used, the definition should contain the
2376
options that are needed whenever `CC' is used.
2377
 
2378
   Specifically, options that determine the runtime architecture must be
2379
in `CC' to correctly select the target for the build.  It is also
2380
convenient to place many other compiler options in `CC'.  For example,
2381
`CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"' can
2382
be used to bootstrap the GCC 3.3 branch with the HP compiler in 64-bit
2383
K&R/bundled mode.  The `+DA2.0W' option will result in the automatic
2384
selection of the `hppa64-hp-hpux11*' target.  The macro definition
2385
table of cpp needs to be increased for a successful build with the HP
2386
compiler.  _CLASSIC_TYPES and _HPUX_SOURCE need to be defined when
2387
building with the bundled compiler, or when using the `-Ac' option.
2388
These defines aren't necessary with `-Ae'.
2389
 
2390
   It is best to explicitly configure the `hppa64-hp-hpux11*' target
2391
with the `--with-ld=...' option.  This overrides the standard search
2392
for ld.  The two linkers supported on this target require different
2393
commands.  The default linker is determined during configuration.  As a
2394
result, it's not possible to switch linkers in the middle of a GCC
2395
build.  This has been been reported to sometimes occur in unified
2396
builds of binutils and GCC.
2397
 
2398
   GCC 3.0 through 3.2 require binutils 2.11 or above.  GCC 3.3 through
2399
GCC 4.0 require binutils 2.14 or later.
2400
 
2401
   Although the HP assembler can be used for an initial build, it
2402
shouldn't be used with any languages other than C and perhaps Fortran
2403
due to its many limitations.  For example, it does not support weak
2404
symbols or alias definitions.  As a result, explicit template
2405
instantiations are required when using C++.  This makes it difficult if
2406
not impossible to build many C++ applications.  You can't generate
2407
debugging information when using the HP assembler.  Finally,
2408
bootstrapping fails in the final comparison of object modules due to
2409
the time stamps that it inserts into the modules.  The bootstrap can be
2410
continued from this point with `make all-host all-target'.
2411
 
2412
   A recent linker patch must be installed for the correct operation of
2413
GCC 3.3 and later.  `PHSS_26559' and `PHSS_24304' are the oldest linker
2414
patches that are known to work.  They are for HP-UX 11.00 and 11.11,
2415
respectively.  `PHSS_24303', the companion to `PHSS_24304', might be
2416
usable but it hasn't been tested.  These patches have been superseded.
2417
Consult the HP patch database to obtain the currently recommended
2418
linker patch for your system.
2419
 
2420
   The patches are necessary for the support of weak symbols on the
2421
32-bit port, and for the running of initializers and finalizers.  Weak
2422
symbols are implemented using SOM secondary definition symbols.  Prior
2423
to HP-UX 11, there are bugs in the linker support for secondary symbols.
2424
The patches correct a problem of linker core dumps creating shared
2425
libraries containing secondary symbols, as well as various other
2426
linking issues involving secondary symbols.
2427
 
2428
   GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
2429
run initializers and finalizers on the 64-bit port.  The 32-bit port
2430
uses the linker `+init' and `+fini' options for the same purpose.  The
2431
patches correct various problems with the +init/+fini options,
2432
including program core dumps.  Binutils 2.14 corrects a problem on the
2433
64-bit port resulting from HP's non-standard use of the .init and .fini
2434
sections for array initializers and finalizers.
2435
 
2436
   There are a number of issues to consider in selecting which linker to
2437
use with the 64-bit port.  The GNU 64-bit linker can only create dynamic
2438
binaries.  The `-static' option causes linking with archive libraries
2439
but doesn't produce a truly static binary.  Dynamic binaries still
2440
require final binding by the dynamic loader to resolve a set of
2441
dynamic-loader-defined symbols.  The default behavior of the HP linker
2442
is the same as the GNU linker.  However, it can generate true 64-bit
2443
static binaries using the `+compat' option.
2444
 
2445
   The HP 64-bit linker doesn't support linkonce semantics.  As a
2446
result, C++ programs have many more sections than they should.
2447
 
2448
   The GNU 64-bit linker has some issues with shared library support
2449
and exceptions.  As a result, we only support libgcc in archive format.
2450
For similar reasons, dwarf2 unwind and exception support are disabled.
2451
The GNU linker also has problems creating binaries with `-static'.  It
2452
doesn't provide stubs for internal calls to global functions in shared
2453
libraries, so these calls can't be overloaded.
2454
 
2455
   Thread support is not implemented in GCC 3.0 through 3.2, so the
2456
`--enable-threads' configure option does not work.  In 3.3 and later,
2457
POSIX threads are supported.  The optional DCE thread library is not
2458
supported.
2459
 
2460
   This port still is undergoing significant development.
2461
 
2462
*-*-linux-gnu
2463
=============
2464
 
2465
Versions of libstdc++-v3 starting with 3.2.1 require bugfixes present
2466
in glibc 2.2.5 and later.  More information is available in the
2467
libstdc++-v3 documentation.
2468
 
2469
i?86-*-linux*aout
2470
=================
2471
 
2472
Use this configuration to generate `a.out' binaries on Linux-based GNU
2473
systems.  This configuration is being superseded.
2474
 
2475
i?86-*-linux*
2476
=============
2477
 
2478
As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
2479
See bug 10877 for more information.
2480
 
2481
   If you receive Signal 11 errors when building on GNU/Linux, then it
2482
is possible you have a hardware problem.  Further information on this
2483
can be found on www.bitwizard.nl.
2484
 
2485
i?86-*-sco3.2v5*
2486
================
2487
 
2488
Use this for the SCO OpenServer Release 5 family of operating systems.
2489
 
2490
   Unlike earlier versions of GCC, the ability to generate COFF with
2491
this target is no longer provided.
2492
 
2493
   Earlier versions of GCC emitted DWARF 1 when generating ELF to allow
2494
the system debugger to be used.  That support was too burdensome to
2495
maintain.  GCC now emits only DWARF 2 for this target.  This means you
2496
may use either the UDK debugger or GDB to debug programs built by this
2497
version of GCC.
2498
 
2499
   GCC is now only supported on releases 5.0.4 and later, and requires
2500
that you install Support Level Supplement OSS646B or later, and Support
2501
Level Supplement OSS631C or later.  If you are using release 5.0.7 of
2502
OpenServer, you must have at least the first maintenance pack installed
2503
(this includes the relevant portions of OSS646).  OSS646, also known as
2504
the "Execution Environment Update", provides updated link editors and
2505
assemblers, as well as updated standard C and math libraries.  The C
2506
startup modules are also updated to support the System V gABI draft, and
2507
GCC relies on that behavior.  OSS631 provides a collection of commonly
2508
used open source libraries, some of which GCC depends on (such as GNU
2509
gettext and zlib).  SCO OpenServer Release 5.0.7 has all of this built
2510
in by default, but OSS631C and later also apply to that release.  Please
2511
visit ftp://ftp.sco.com/pub/openserver5 for the latest versions of
2512
these (and other potentially useful) supplements.
2513
 
2514
   Although there is support for using the native assembler, it is
2515
recommended that you configure GCC to use the GNU assembler.  You do
2516
this by using the flags `--with-gnu-as'.  You should use a modern
2517
version of GNU binutils.  Version 2.13.2.1 was used for all testing.
2518
In general, only the `--with-gnu-as' option is tested.  A modern
2519
bintuils (as well as a plethora of other development related GNU
2520
utilities) can be found in Support Level Supplement OSS658A, the "GNU
2521
Development Tools" package.  See the SCO web and ftp sites for details.
2522
That package also contains the currently "officially supported" version
2523
of GCC, version 2.95.3.  It is useful for bootstrapping this version.
2524
 
2525
i?86-*-solaris2.10
2526
==================
2527
 
2528
Use this for Solaris 10 or later on x86 and x86-64 systems.  This
2529
configuration is supported by GCC 4.0 and later versions only.
2530
 
2531
   It is recommended that you configure GCC to use the GNU assembler in
2532
`/usr/sfw/bin/gas' but the Sun linker, using the options `--with-gnu-as
2533
--with-as=/usr/sfw/bin/gas --without-gnu-ld --with-ld=/usr/ccs/bin/ld'.
2534
 
2535
i?86-*-udk
2536
==========
2537
 
2538
This target emulates the SCO Universal Development Kit and requires that
2539
package be installed.  (If it is installed, you will have a
2540
`/udk/usr/ccs/bin/cc' file present.)  It's very much like the
2541
`i?86-*-unixware7*' target but is meant to be used when hosting on a
2542
system where UDK isn't the default compiler such as OpenServer 5 or
2543
Unixware 2.  This target will generate binaries that will run on
2544
OpenServer, Unixware 2, or Unixware 7, with the same warnings and
2545
caveats as the SCO UDK.
2546
 
2547
   This target is a little tricky to build because we have to
2548
distinguish it from the native tools (so it gets headers, startups, and
2549
libraries from the right place) while making the tools not think we're
2550
actually building a cross compiler.   The easiest way to do this is
2551
with a configure command like this:
2552
 
2553
         CC=/udk/usr/ccs/bin/cc /YOUR/PATH/TO/gcc/configure \
2554
           --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-
2555
 
2556
   _You should substitute `i686' in the above command with the
2557
appropriate processor for your host._
2558
 
2559
   After the usual `make' and `make install', you can then access the
2560
UDK-targeted GCC tools by adding `udk-' before the commonly known name.
2561
For example, to invoke the C compiler, you would use `udk-gcc'.  They
2562
will coexist peacefully with any native-target GCC tools you may have
2563
installed.
2564
 
2565
ia64-*-linux
2566
============
2567
 
2568
IA-64 processor (also known as IPF, or Itanium Processor Family)
2569
running GNU/Linux.
2570
 
2571
   If you are using the installed system libunwind library with
2572
`--with-system-libunwind', then you must use libunwind 0.98 or later.
2573
 
2574
   None of the following versions of GCC has an ABI that is compatible
2575
with any of the other versions in this list, with the exception that
2576
Red Hat 2.96 and Trillian 000171 are compatible with each other: 3.1,
2577
3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.  This primarily
2578
affects C++ programs and programs that create shared libraries.  GCC
2579
3.1 or later is recommended for compiling linux, the kernel.  As of
2580
version 3.1 GCC is believed to be fully ABI compliant, and hence no
2581
more major ABI changes are expected.
2582
 
2583
ia64-*-hpux*
2584
============
2585
 
2586
Building GCC on this target requires the GNU Assembler.  The bundled HP
2587
assembler will not work.  To prevent GCC from using the wrong assembler,
2588
the option `--with-gnu-as' may be necessary.
2589
 
2590
   The GCC libunwind library has not been ported to HPUX.  This means
2591
that for GCC versions 3.2.3 and earlier, `--enable-libunwind-exceptions'
2592
is required to build GCC.  For GCC 3.3 and later, this is the default.
2593
For gcc 3.4.3 and later, `--enable-libunwind-exceptions' is removed and
2594
the system libunwind library will always be used.
2595
 
2596
*-ibm-aix*
2597
==========
2598
 
2599
Support for AIX version 3 and older was discontinued in GCC 3.4.
2600
 
2601
   "out of memory" bootstrap failures may indicate a problem with
2602
process resource limits (ulimit).  Hard limits are configured in the
2603
`/etc/security/limits' system configuration file.
2604
 
2605
   To speed up the configuration phases of bootstrapping and installing
2606
GCC, one may use GNU Bash instead of AIX `/bin/sh', e.g.,
2607
 
2608
        % CONFIG_SHELL=/opt/freeware/bin/bash
2609
        % export CONFIG_SHELL
2610
 
2611
   and then proceed as described in the build instructions, where we
2612
strongly recommend specifying an absolute path to invoke
2613
SRCDIR/configure.
2614
 
2615
   Because GCC on AIX is built as a 32-bit executable by default,
2616
(although it can generate 64-bit programs) the GMP and MPFR libraries
2617
required by gfortran must be 32-bit libraries.  Building GMP and MPFR
2618
as static archive libraries works better than shared libraries.
2619
 
2620
   Errors involving `alloca' when building GCC generally are due to an
2621
incorrect definition of `CC' in the Makefile or mixing files compiled
2622
with the native C compiler and GCC.  During the stage1 phase of the
2623
build, the native AIX compiler *must* be invoked as `cc' (not `xlc').
2624
Once `configure' has been informed of `xlc', one needs to use `make
2625
distclean' to remove the configure cache files and ensure that `CC'
2626
environment variable does not provide a definition that will confuse
2627
`configure'.  If this error occurs during stage2 or later, then the
2628
problem most likely is the version of Make (see above).
2629
 
2630
   The native `as' and `ld' are recommended for bootstrapping on AIX 4
2631
and required for bootstrapping on AIX 5L.  The GNU Assembler reports
2632
that it supports WEAK symbols on AIX 4, which causes GCC to try to
2633
utilize weak symbol functionality although it is not supported.  The GNU
2634
Assembler and Linker do not support AIX 5L sufficiently to bootstrap
2635
GCC.  The native AIX tools do interoperate with GCC.
2636
 
2637
   Building `libstdc++.a' requires a fix for an AIX Assembler bug APAR
2638
IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1).  It also requires a fix
2639
for another AIX Assembler bug and a co-dependent AIX Archiver fix
2640
referenced as APAR IY53606 (AIX 5.2) or a APAR IY54774 (AIX 5.1)
2641
 
2642
   `libstdc++' in GCC 3.4 increments the major version number of the
2643
shared object and GCC installation places the `libstdc++.a' shared
2644
library in a common location which will overwrite the and GCC 3.3
2645
version of the shared library.  Applications either need to be
2646
re-linked against the new shared library or the GCC 3.1 and GCC 3.3
2647
versions of the `libstdc++' shared object needs to be available to the
2648
AIX runtime loader.  The GCC 3.1 `libstdc++.so.4', if present, and GCC
2649
3.3 `libstdc++.so.5' shared objects can be installed for runtime
2650
dynamic loading using the following steps to set the `F_LOADONLY' flag
2651
in the shared object for _each_ multilib `libstdc++.a' installed:
2652
 
2653
   Extract the shared objects from the currently installed
2654
`libstdc++.a' archive:
2655
        % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
2656
 
2657
   Enable the `F_LOADONLY' flag so that the shared object will be
2658
available for runtime dynamic loading, but not linking:
2659
        % strip -e libstdc++.so.4 libstdc++.so.5
2660
 
2661
   Archive the runtime-only shared object in the GCC 3.4 `libstdc++.a'
2662
archive:
2663
        % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
2664
 
2665
   Linking executables and shared libraries may produce warnings of
2666
duplicate symbols.  The assembly files generated by GCC for AIX always
2667
have included multiple symbol definitions for certain global variable
2668
and function declarations in the original program.  The warnings should
2669
not prevent the linker from producing a correct library or runnable
2670
executable.
2671
 
2672
   AIX 4.3 utilizes a "large format" archive to support both 32-bit and
2673
64-bit object modules.  The routines provided in AIX 4.3.0 and AIX 4.3.1
2674
to parse archive libraries did not handle the new format correctly.
2675
These routines are used by GCC and result in error messages during
2676
linking such as "not a COFF file".  The version of the routines shipped
2677
with AIX 4.3.1 should work for a 32-bit environment.  The `-g' option
2678
of the archive command may be used to create archives of 32-bit objects
2679
using the original "small format".  A correct version of the routines
2680
is shipped with AIX 4.3.2 and above.
2681
 
2682
   Some versions of the AIX binder (linker) can fail with a relocation
2683
overflow severe error when the `-bbigtoc' option is used to link
2684
GCC-produced object files into an executable that overflows the TOC.  A
2685
fix for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC)
2686
is available from IBM Customer Support and from its
2687
techsupport.services.ibm.com website as PTF U455193.
2688
 
2689
   The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump
2690
core with a segmentation fault when invoked by any version of GCC.  A
2691
fix for APAR IX87327 is available from IBM Customer Support and from its
2692
techsupport.services.ibm.com website as PTF U461879.  This fix is
2693
incorporated in AIX 4.3.3 and above.
2694
 
2695
   The initial assembler shipped with AIX 4.3.0 generates incorrect
2696
object files.  A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM
2697
COMPILER FAILS TO ASSEMBLE/BIND) is available from IBM Customer Support
2698
and from its techsupport.services.ibm.com website as PTF U453956.  This
2699
fix is incorporated in AIX 4.3.1 and above.
2700
 
2701
   AIX provides National Language Support (NLS).  Compilers and
2702
assemblers use NLS to support locale-specific representations of
2703
various data formats including floating-point numbers (e.g., `.'  vs
2704
`,' for separating decimal fractions).  There have been problems
2705
reported where GCC does not produce the same floating-point formats
2706
that the assembler expects.  If one encounters this problem, set the
2707
`LANG' environment variable to `C' or `En_US'.
2708
 
2709
   By default, GCC for AIX 4.1 and above produces code that can be used
2710
on both Power or PowerPC processors.
2711
 
2712
   A default can be specified with the `-mcpu=CPU_TYPE' switch and
2713
using the configure option `--with-cpu-CPU_TYPE'.
2714
 
2715
iq2000-*-elf
2716
============
2717
 
2718
Vitesse IQ2000 processors.  These are used in embedded applications.
2719
There are no standard Unix configurations.
2720
 
2721
m32c-*-elf
2722
==========
2723
 
2724
Renesas M32C processor.  This configuration is intended for embedded
2725
systems.
2726
 
2727
m32r-*-elf
2728
==========
2729
 
2730
Renesas M32R processor.  This configuration is intended for embedded
2731
systems.
2732
 
2733
m6811-elf
2734
=========
2735
 
2736
Motorola 68HC11 family micro controllers.  These are used in embedded
2737
applications.  There are no standard Unix configurations.
2738
 
2739
m6812-elf
2740
=========
2741
 
2742
Motorola 68HC12 family micro controllers.  These are used in embedded
2743
applications.  There are no standard Unix configurations.
2744
 
2745
m68k-hp-hpux
2746
============
2747
 
2748
HP 9000 series 300 or 400 running HP-UX.  HP-UX version 8.0 has a bug in
2749
the assembler that prevents compilation of GCC.  This bug manifests
2750
itself during the first stage of compilation, while building
2751
`libgcc2.a':
2752
 
2753
     _floatdisf
2754
     cc1: warning: `-g' option not supported on this version of GCC
2755
     cc1: warning: `-g1' option not supported on this version of GCC
2756
     ./xgcc: Internal compiler error: program as got fatal signal 11
2757
 
2758
   A patched version of the assembler is available as the file
2759
`ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler'.  If you have
2760
HP software support, the patch can also be obtained directly from HP,
2761
as described in the following note:
2762
 
2763
     This is the patched assembler, to patch SR#1653-010439, where the
2764
     assembler aborts on floating point constants.
2765
 
2766
     The bug is not really in the assembler, but in the shared library
2767
     version of the function "cvtnum(3c)".  The bug on "cvtnum(3c)" is
2768
     SR#4701-078451.  Anyway, the attached assembler uses the archive
2769
     library version of "cvtnum(3c)" and thus does not exhibit the bug.
2770
 
2771
   This patch is also known as PHCO_4484.
2772
 
2773
   In addition gdb does not understand that native HP-UX format, so you
2774
must use gas if you wish to use gdb.
2775
 
2776
   On HP-UX version 8.05, but not on 8.07 or more recent versions, the
2777
`fixproto' shell script triggers a bug in the system shell.  If you
2778
encounter this problem, upgrade your operating system or use BASH (the
2779
GNU shell) to run `fixproto'.  This bug will cause the fixproto program
2780
to report an error of the form:
2781
 
2782
     ./fixproto: sh internal 1K buffer overflow
2783
 
2784
   To fix this, you can also change the first line of the fixproto
2785
script to look like:
2786
 
2787
     #!/bin/ksh
2788
 
2789
mips-*-*
2790
========
2791
 
2792
If on a MIPS system you get an error message saying "does not have gp
2793
sections for all it's [sic] sectons [sic]", don't worry about it.  This
2794
happens whenever you use GAS with the MIPS linker, but there is not
2795
really anything wrong, and it is okay to use the output file.  You can
2796
stop such warnings by installing the GNU linker.
2797
 
2798
   It would be nice to extend GAS to produce the gp tables, but they are
2799
optional, and there should not be a warning about their absence.
2800
 
2801
   The libstdc++ atomic locking routines for MIPS targets requires MIPS
2802
II and later.  A patch went in just after the GCC 3.3 release to make
2803
`mips*-*-*' use the generic implementation instead.  You can also
2804
configure for `mipsel-elf' as a workaround.  The `mips*-*-linux*'
2805
target continues to use the MIPS II routines.  More work on this is
2806
expected in future releases.
2807
 
2808
   MIPS systems check for division by zero (unless
2809
`-mno-check-zero-division' is passed to the compiler) by generating
2810
either a conditional trap or a break instruction.  Using trap results
2811
in smaller code, but is only supported on MIPS II and later.  Also,
2812
some versions of the Linux kernel have a bug that prevents trap from
2813
generating the proper signal (`SIGFPE').  To enable the use of break,
2814
use the `--with-divide=breaks' `configure' option when configuring GCC.
2815
The default is to use traps on systems that support them.
2816
 
2817
   Cross-compilers for the MIPS as target using the MIPS assembler
2818
currently do not work, because the auxiliary programs `mips-tdump.c'
2819
and `mips-tfile.c' can't be compiled on anything but a MIPS.  It does
2820
work to cross compile for a MIPS if you use the GNU assembler and
2821
linker.
2822
 
2823
   The assembler from GNU binutils 2.17 and earlier has a bug in the way
2824
it sorts relocations for REL targets (o32, o64, EABI).  This can cause
2825
bad code to be generated for simple C++ programs.  Also the linker from
2826
GNU binutils versions prior to 2.17 has a bug which causes the runtime
2827
linker stubs in very large programs, like `libgcj.so', to be
2828
incorrectly generated.  Binutils CVS snapshots and releases made after
2829
Nov. 9, 2006 are thought to be free from both of these problems.
2830
 
2831
mips-sgi-irix5
2832
==============
2833
 
2834
In order to compile GCC on an SGI running IRIX 5, the `compiler_dev.hdr'
2835
subsystem must be installed from the IDO CD-ROM supplied by SGI.  It is
2836
also available for download from
2837
`ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist'.
2838
 
2839
   If you use the MIPS C compiler to bootstrap, it may be necessary to
2840
increase its table size for switch statements with the `-Wf,-XNg1500'
2841
option.  If you use the `-O2' optimization option, you also need to use
2842
`-Olimit 3000'.
2843
 
2844
   To enable debugging under IRIX 5, you must use GNU binutils 2.15 or
2845
later, and use the `--with-gnu-ld' `configure' option when configuring
2846
GCC.  You need to use GNU `ar' and `nm', also distributed with GNU
2847
binutils.
2848
 
2849
   Some users have reported that `/bin/sh' will hang during bootstrap.
2850
This problem can be avoided by running the commands:
2851
 
2852
        % CONFIG_SHELL=/bin/ksh
2853
        % export CONFIG_SHELL
2854
 
2855
   before starting the build.
2856
 
2857
mips-sgi-irix6
2858
==============
2859
 
2860
If you are using SGI's MIPSpro `cc' as your bootstrap compiler, you must
2861
ensure that the N32 ABI is in use.  To test this, compile a simple C
2862
file with `cc' and then run `file' on the resulting object file.  The
2863
output should look like:
2864
 
2865
     test.o: ELF N32 MSB ...
2866
 
2867
   If you see:
2868
 
2869
     test.o: ELF 32-bit MSB ...
2870
 
2871
   or
2872
 
2873
     test.o: ELF 64-bit MSB ...
2874
 
2875
   then your version of `cc' uses the O32 or N64 ABI by default.  You
2876
should set the environment variable `CC' to `cc -n32' before
2877
configuring GCC.
2878
 
2879
   If you want the resulting `gcc' to run on old 32-bit systems with
2880
the MIPS R4400 CPU, you need to ensure that only code for the `mips3'
2881
instruction set architecture (ISA) is generated.  While GCC 3.x does
2882
this correctly, both GCC 2.95 and SGI's MIPSpro `cc' may change the ISA
2883
depending on the machine where GCC is built.  Using one of them as the
2884
bootstrap compiler may result in `mips4' code, which won't run at all
2885
on `mips3'-only systems.  For the test program above, you should see:
2886
 
2887
     test.o: ELF N32 MSB mips-3 ...
2888
 
2889
   If you get:
2890
 
2891
     test.o: ELF N32 MSB mips-4 ...
2892
 
2893
   instead, you should set the environment variable `CC' to `cc -n32
2894
-mips3' or `gcc -mips3' respectively before configuring GCC.
2895
 
2896
   MIPSpro C 7.4 may cause bootstrap failures, due to a bug when
2897
inlining `memcmp'.  Either add `-U__INLINE_INTRINSICS' to the `CC'
2898
environment variable as a workaround or upgrade to MIPSpro C 7.4.1m.
2899
 
2900
   GCC on IRIX 6 is usually built to support the N32, O32 and N64 ABIs.
2901
If you build GCC on a system that doesn't have the N64 libraries
2902
installed or cannot run 64-bit binaries, you need to configure with
2903
`--disable-multilib' so GCC doesn't try to use them.  This will disable
2904
building the O32 libraries, too.  Look for `/usr/lib64/libc.so.1' to
2905
see if you have the 64-bit libraries installed.
2906
 
2907
   To enable debugging for the O32 ABI, you must use GNU `as' from GNU
2908
binutils 2.15 or later.  You may also use GNU `ld', but this is not
2909
required and currently causes some problems with Ada.
2910
 
2911
   The `--enable-threads' option doesn't currently work, a patch is in
2912
preparation for a future release.  The `--enable-libgcj' option is
2913
disabled by default: IRIX 6 uses a very low default limit (20480) for
2914
the command line length.  Although `libtool' contains a workaround for
2915
this problem, at least the N64 `libgcj' is known not to build despite
2916
this, running into an internal error of the native `ld'.  A sure fix is
2917
to increase this limit (`ncargs') to its maximum of 262144 bytes.  If
2918
you have root access, you can use the `systune' command to do this.
2919
 
2920
   `wchar_t' support in `libstdc++' is not available for old IRIX 6.5.x
2921
releases, x < 19.  The problem cannot be autodetected and in order to
2922
build GCC for such targets you need to configure with
2923
`--disable-wchar_t'.
2924
 
2925
   See `http://freeware.sgi.com/' for more information about using GCC
2926
on IRIX platforms.
2927
 
2928
powerpc-*-*
2929
===========
2930
 
2931
You can specify a default version for the `-mcpu=CPU_TYPE' switch by
2932
using the configure option `--with-cpu-CPU_TYPE'.
2933
 
2934
powerpc-*-darwin*
2935
=================
2936
 
2937
PowerPC running Darwin (Mac OS X kernel).
2938
 
2939
   Pre-installed versions of Mac OS X may not include any developer
2940
tools, meaning that you will not be able to build GCC from source.  Tool
2941
binaries are available at
2942
`http://developer.apple.com/darwin/projects/compiler/' (free
2943
registration required).
2944
 
2945
   This version of GCC requires at least cctools-590.7.
2946
 
2947
   The version of GCC shipped by Apple typically includes a number of
2948
extensions not available in a standard GCC release.  These extensions
2949
are generally for backwards compatibility and best avoided.
2950
 
2951
powerpc-*-elf, powerpc-*-sysv4
2952
==============================
2953
 
2954
PowerPC system in big endian mode, running System V.4.
2955
 
2956
powerpc*-*-linux-gnu*
2957
=====================
2958
 
2959
You will need binutils 2.15 or newer for a working GCC.
2960
 
2961
powerpc-*-netbsd*
2962
=================
2963
 
2964
PowerPC system in big endian mode running NetBSD.  To build the
2965
documentation you will need Texinfo version 4.4 (NetBSD 1.5.1 included
2966
Texinfo version 3.12).
2967
 
2968
powerpc-*-eabisim
2969
=================
2970
 
2971
Embedded PowerPC system in big endian mode for use in running under the
2972
PSIM simulator.
2973
 
2974
powerpc-*-eabi
2975
==============
2976
 
2977
Embedded PowerPC system in big endian mode.
2978
 
2979
powerpcle-*-elf, powerpcle-*-sysv4
2980
==================================
2981
 
2982
PowerPC system in little endian mode, running System V.4.
2983
 
2984
powerpcle-*-eabisim
2985
===================
2986
 
2987
Embedded PowerPC system in little endian mode for use in running under
2988
the PSIM simulator.
2989
 
2990
powerpcle-*-eabi
2991
================
2992
 
2993
Embedded PowerPC system in little endian mode.
2994
 
2995
s390-*-linux*
2996
=============
2997
 
2998
S/390 system running GNU/Linux for S/390.
2999
 
3000
s390x-*-linux*
3001
==============
3002
 
3003
zSeries system (64-bit) running GNU/Linux for zSeries.
3004
 
3005
s390x-ibm-tpf*
3006
==============
3007
 
3008
zSeries system (64-bit) running TPF.  This platform is supported as
3009
cross-compilation target only.
3010
 
3011
*-*-solaris2*
3012
=============
3013
 
3014
Sun does not ship a C compiler with Solaris 2.  To bootstrap and install
3015
GCC you first have to install a pre-built compiler, see the binaries
3016
page for details.
3017
 
3018
   The Solaris 2 `/bin/sh' will often fail to configure `libstdc++-v3',
3019
`boehm-gc' or `libjava'.  We therefore recommend using the following
3020
initial sequence of commands
3021
 
3022
        % CONFIG_SHELL=/bin/ksh
3023
        % export CONFIG_SHELL
3024
 
3025
   and proceed as described in the configure instructions.  In addition
3026
we strongly recommend specifying an absolute path to invoke
3027
SRCDIR/configure.
3028
 
3029
   Solaris 2 comes with a number of optional OS packages.  Some of these
3030
are needed to use GCC fully, namely `SUNWarc', `SUNWbtool', `SUNWesu',
3031
`SUNWhea', `SUNWlibm', `SUNWsprot', and `SUNWtoo'.  If you did not
3032
install all optional packages when installing Solaris 2, you will need
3033
to verify that the packages that GCC needs are installed.
3034
 
3035
   To check whether an optional package is installed, use the `pkginfo'
3036
command.  To add an optional package, use the `pkgadd' command.  For
3037
further details, see the Solaris 2 documentation.
3038
 
3039
   Trying to use the linker and other tools in `/usr/ucb' to install
3040
GCC has been observed to cause trouble.  For example, the linker may
3041
hang indefinitely.  The fix is to remove `/usr/ucb' from your `PATH'.
3042
 
3043
   The build process works more smoothly with the legacy Sun tools so,
3044
if you have `/usr/xpg4/bin' in your `PATH', we recommend that you place
3045
`/usr/bin' before `/usr/xpg4/bin' for the duration of the build.
3046
 
3047
   All releases of GNU binutils prior to 2.11.2 have known bugs on this
3048
platform.  We recommend the use of GNU binutils 2.11.2 or later, or the
3049
vendor tools (Sun `as', Sun `ld').  Note that your mileage may vary if
3050
you use a combination of the GNU tools and the Sun tools: while the
3051
combination GNU `as' + Sun `ld' should reasonably work, the reverse
3052
combination Sun `as' + GNU `ld' is known to cause memory corruption at
3053
runtime in some cases for C++ programs.
3054
 
3055
   The stock GNU binutils 2.15 release is broken on this platform
3056
because of a single bug.  It has been fixed on the 2.15 branch in the
3057
CVS repository.  You can obtain a working version by checking out the
3058
binutils-2_15-branch from the CVS repository or applying the patch
3059
`http://sourceware.org/ml/binutils-cvs/2004-09/msg00036.html' to the
3060
release.
3061
 
3062
   We recommend using GNU binutils 2.16 or later in conjunction with
3063
GCC 4.x, or the vendor tools (Sun `as', Sun `ld').  However, for
3064
Solaris 10 and above, an additional patch is required in order for the
3065
GNU linker to be able to cope with a new flavor of shared libraries.
3066
You can obtain a working version by checking out the
3067
binutils-2_16-branch from the CVS repository or applying the patch
3068
`http://sourceware.org/ml/binutils-cvs/2005-07/msg00122.html' to the
3069
release.
3070
 
3071
   Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
3072
newer: `g++' will complain that types are missing.  These headers assume
3073
that omitting the type means `int'; this assumption worked for C89 but
3074
is wrong for C++, and is now wrong for C99 also.
3075
 
3076
   `g++' accepts such (invalid) constructs with the option
3077
`-fpermissive'; it will assume that any missing type is `int' (as
3078
defined by C89).
3079
 
3080
   There are patches for Solaris 2.6 (105633-56 or newer for SPARC,
3081
106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC,
3082
108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
3083
108653-22 for Intel) that fix this bug.
3084
 
3085
   Sun bug 4927647 sometimes causes random spurious testsuite failures
3086
related to missing diagnostic output.  This bug doesn't affect GCC
3087
itself, rather it is a kernel bug triggered by the `expect' program
3088
which is used only by the GCC testsuite driver.  When the bug causes
3089
the `expect' program to miss anticipated output, extra testsuite
3090
failures appear.
3091
 
3092
   There are patches for Solaris 8 (117350-12 or newer for SPARC,
3093
117351-12 or newer for Intel) and Solaris 9 (117171-11 or newer for
3094
SPARC, 117172-11 or newer for Intel) that address this problem.
3095
 
3096
sparc-sun-solaris2*
3097
===================
3098
 
3099
When GCC is configured to use binutils 2.11.2 or later the binaries
3100
produced are smaller than the ones produced using Sun's native tools;
3101
this difference is quite significant for binaries containing debugging
3102
information.
3103
 
3104
   Sun `as' 4.x is broken in that it cannot cope with long symbol names.
3105
A typical error message might look similar to the following:
3106
 
3107
     /usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error:
3108
       can't compute value of an expression involving an external symbol.
3109
 
3110
   This is Sun bug 4237974.  This is fixed with patch 108908-02 for
3111
Solaris 2.6 and has been fixed in later (5.x) versions of the assembler,
3112
starting with Solaris 7.
3113
 
3114
   Starting with Solaris 7, the operating system is capable of executing
3115
64-bit SPARC V9 binaries.  GCC 3.1 and later properly supports this;
3116
the `-m64' option enables 64-bit code generation.  However, if all you
3117
want is code tuned for the UltraSPARC CPU, you should try the
3118
`-mtune=ultrasparc' option instead, which produces code that, unlike
3119
full 64-bit code, can still run on non-UltraSPARC machines.
3120
 
3121
   When configuring on a Solaris 7 or later system that is running a
3122
kernel that supports only 32-bit binaries, one must configure with
3123
`--disable-multilib', since we will not be able to build the 64-bit
3124
target libraries.
3125
 
3126
   GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions
3127
of the GNU compiler (especially GCC 3.0.x versions), which lead to the
3128
miscompilation of the stage1 compiler and the subsequent failure of the
3129
bootstrap process.  A workaround is to use GCC 3.2.3 as an intermediary
3130
stage, i.e. to bootstrap that compiler with the base compiler and then
3131
use it to bootstrap the final compiler.
3132
 
3133
   GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE
3134
Studio 7) and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes
3135
a bootstrap failure in form of a miscompilation of the stage1 compiler
3136
by the Sun compiler.  This is Sun bug 4974440.  This is fixed with
3137
patch 112760-07.
3138
 
3139
   GCC 3.4 changed the default debugging format from STABS to DWARF-2
3140
for 32-bit code on Solaris 7 and later.  If you use the Sun assembler,
3141
this change apparently runs afoul of Sun bug 4910101 (which is
3142
referenced as a x86-only problem by Sun, probably because they do not
3143
use DWARF-2).  A symptom of the problem is that you cannot compile C++
3144
programs like `groff' 1.19.1 without getting messages similar to the
3145
following:
3146
 
3147
     ld: warning: relocation error: R_SPARC_UA32: ...
3148
       external symbolic relocation against non-allocatable section
3149
       .debug_info cannot be processed at runtime: relocation ignored.
3150
 
3151
   To work around this problem, compile with `-gstabs+' instead of
3152
plain `-g'.
3153
 
3154
   When configuring the GNU Multiple Precision Library (GMP) or the MPFR
3155
library on a Solaris 7 or later system, the canonical target triplet
3156
must be specified as the `build' parameter on the configure line.  This
3157
triplet can be obtained by invoking ./config.guess in the toplevel
3158
source directory of GCC (and not that of GMP or MPFR).  For example on
3159
a Solaris 7 system:
3160
 
3161
        % ./configure --build=sparc-sun-solaris2.7 --prefix=xxx
3162
 
3163
sparc-sun-solaris2.7
3164
====================
3165
 
3166
Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
3167
the dynamic linker.  This problem (Sun bug 4210064) affects GCC 2.8 and
3168
later, including all EGCS releases.  Sun formerly recommended 107058-01
3169
for all Solaris 7 users, but around 1999-09-01 it started to recommend
3170
it only for people who use Sun's compilers.
3171
 
3172
   Here are some workarounds to this problem:
3173
   * Do not install Sun patch 107058-01 until after Sun releases a
3174
     complete patch for bug 4210064.  This is the simplest course to
3175
     take, unless you must also use Sun's C compiler.  Unfortunately
3176
     107058-01 is preinstalled on some new Solaris 7-based hosts, so
3177
     you may have to back it out.
3178
 
3179
   * Copy the original, unpatched Solaris 7 `/usr/ccs/bin/as' into
3180
     `/usr/local/libexec/gcc/sparc-sun-solaris2.7/3.4/as', adjusting
3181
     the latter name to fit your local conventions and software version
3182
     numbers.
3183
 
3184
   * Install Sun patch 106950-03 (1999-05-25) or later.  Nobody with
3185
     both 107058-01 and 106950-03 installed has reported the bug with
3186
     GCC and Sun's dynamic linker.  This last course of action is
3187
     riskiest, for two reasons.  First, you must install 106950 on all
3188
     hosts that run code generated by GCC; it doesn't suffice to
3189
     install it only on the hosts that run GCC itself.  Second, Sun
3190
     says that 106950-03 is only a partial fix for bug 4210064, but Sun
3191
     doesn't know whether the partial fix is adequate for GCC.
3192
     Revision -08 or later should fix the bug.  The current (as of
3193
     2004-05-23) revision is -24, and is included in the Solaris 7
3194
     Recommended Patch Cluster.
3195
 
3196
   GCC 3.3 triggers a bug in version 5.0 Alpha 03/27/98 of the Sun
3197
assembler, which causes a bootstrap failure when linking the 64-bit
3198
shared version of libgcc.  A typical error message is:
3199
 
3200
     ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o:
3201
       symbol :  offset 0xffffffff7ec133e7 is non-aligned.
3202
 
3203
   This bug has been fixed in the final 5.0 version of the assembler.
3204
 
3205
   A similar problem was reported for version Sun WorkShop 6 99/08/18
3206
of the Sun assembler, which causes a bootstrap failure with GCC 4.0.0:
3207
 
3208
     ld: fatal: relocation error: R_SPARC_DISP32:
3209
       file .libs/libstdc++.lax/libsupc++convenience.a/vterminate.o:
3210
         symbol : offset 0xfccd33ad is non-aligned
3211
 
3212
   This bug has been fixed in more recent revisions of the assembler.
3213
 
3214
sparc-*-linux*
3215
==============
3216
 
3217
GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4 or
3218
newer on this platform.  All earlier binutils and glibc releases
3219
mishandled unaligned relocations on `sparc-*-*' targets.
3220
 
3221
sparc64-*-solaris2*
3222
===================
3223
 
3224
When configuring the GNU Multiple Precision Library (GMP) or the MPFR
3225
library, the canonical target triplet must be specified as the `build'
3226
parameter on the configure line.  For example on a Solaris 7 system:
3227
 
3228
        % ./configure --build=sparc64-sun-solaris2.7 --prefix=xxx
3229
 
3230
   The following compiler flags must be specified in the configure step
3231
in order to bootstrap this target with the Sun compiler:
3232
 
3233
        % CC="cc -xarch=v9 -xildoff" SRCDIR/configure [OPTIONS] [TARGET]
3234
 
3235
   `-xarch=v9' specifies the SPARC-V9 architecture to the Sun toolchain
3236
and `-xildoff' turns off the incremental linker.
3237
 
3238
sparcv9-*-solaris2*
3239
===================
3240
 
3241
This is a synonym for sparc64-*-solaris2*.
3242
 
3243
*-*-sysv*
3244
=========
3245
 
3246
On System V release 3, you may get this error message while linking:
3247
 
3248
     ld fatal: failed to write symbol name SOMETHING
3249
      in strings table for file WHATEVER
3250
 
3251
   This probably indicates that the disk is full or your ulimit won't
3252
allow the file to be as large as it needs to be.
3253
 
3254
   This problem can also result because the kernel parameter `MAXUMEM'
3255
is too small.  If so, you must regenerate the kernel and make the value
3256
much larger.  The default value is reported to be 1024; a value of 32768
3257
is said to work.  Smaller values may also work.
3258
 
3259
   On System V, if you get an error like this,
3260
 
3261
     /usr/local/lib/bison.simple: In function `yyparse':
3262
     /usr/local/lib/bison.simple:625: virtual memory exhausted
3263
 
3264
that too indicates a problem with disk space, ulimit, or `MAXUMEM'.
3265
 
3266
   On a System V release 4 system, make sure `/usr/bin' precedes
3267
`/usr/ucb' in `PATH'.  The `cc' command in `/usr/ucb' uses libraries
3268
which have bugs.
3269
 
3270
vax-dec-ultrix
3271
==============
3272
 
3273
Don't try compiling with VAX C (`vcc').  It produces incorrect code in
3274
some cases (for example, when `alloca' is used).
3275
 
3276
*-*-vxworks*
3277
============
3278
 
3279
Support for VxWorks is in flux.  At present GCC supports _only_ the
3280
very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC.
3281
We welcome patches for other architectures supported by VxWorks 5.5.
3282
Support for VxWorks AE would also be welcome; we believe this is merely
3283
a matter of writing an appropriate "configlette" (see below).  We are
3284
not interested in supporting older, a.out or COFF-based, versions of
3285
VxWorks in GCC 3.
3286
 
3287
   VxWorks comes with an older version of GCC installed in
3288
`$WIND_BASE/host'; we recommend you do not overwrite it.  Choose an
3289
installation PREFIX entirely outside $WIND_BASE.  Before running
3290
`configure', create the directories `PREFIX' and `PREFIX/bin'.  Link or
3291
copy the appropriate assembler, linker, etc. into `PREFIX/bin', and set
3292
your PATH to include that directory while running both `configure' and
3293
`make'.
3294
 
3295
   You must give `configure' the `--with-headers=$WIND_BASE/target/h'
3296
switch so that it can find the VxWorks system headers.  Since VxWorks
3297
is a cross compilation target only, you must also specify
3298
`--target=TARGET'.  `configure' will attempt to create the directory
3299
`PREFIX/TARGET/sys-include' and copy files into it; make sure the user
3300
running `configure' has sufficient privilege to do so.
3301
 
3302
   GCC's exception handling runtime requires a special "configlette"
3303
module, `contrib/gthr_supp_vxw_5x.c'.  Follow the instructions in that
3304
file to add the module to your kernel build.  (Future versions of
3305
VxWorks will incorporate this module.)
3306
 
3307
x86_64-*-*, amd64-*-*
3308
=====================
3309
 
3310
GCC supports the x86-64 architecture implemented by the AMD64 processor
3311
(amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD.
3312
On GNU/Linux the default is a bi-arch compiler which is able to generate
3313
both 64-bit x86-64 and 32-bit x86 code (via the `-m32' switch).
3314
 
3315
xtensa-*-elf
3316
============
3317
 
3318
This target is intended for embedded Xtensa systems using the `newlib'
3319
C library.  It uses ELF but does not support shared objects.
3320
Designed-defined instructions specified via the Tensilica Instruction
3321
Extension (TIE) language are only supported through inline assembly.
3322
 
3323
   The Xtensa configuration information must be specified prior to
3324
building GCC.  The `include/xtensa-config.h' header file contains the
3325
configuration information.  If you created your own Xtensa
3326
configuration with the Xtensa Processor Generator, the downloaded files
3327
include a customized copy of this header file, which you can use to
3328
replace the default header file.
3329
 
3330
xtensa-*-linux*
3331
===============
3332
 
3333
This target is for Xtensa systems running GNU/Linux.  It supports ELF
3334
shared objects and the GNU C library (glibc).  It also generates
3335
position-independent code (PIC) regardless of whether the `-fpic' or
3336
`-fPIC' options are used.  In other respects, this target is the same
3337
as the `xtensa-*-elf' target.
3338
 
3339
Microsoft Windows (32-bit)
3340
==========================
3341
 
3342
Ports of GCC are included with the Cygwin environment.
3343
 
3344
   GCC will build under Cygwin without modification; it does not build
3345
with Microsoft's C++ compiler and there are no plans to make it do so.
3346
 
3347
OS/2
3348
====
3349
 
3350
GCC does not currently support OS/2.  However, Andrew Zabolotny has been
3351
working on a generic OS/2 port with pgcc.  The current code can be found
3352
at http://www.goof.com/pcg/os2/.
3353
 
3354
Older systems
3355
=============
3356
 
3357
GCC contains support files for many older (1980s and early 1990s) Unix
3358
variants.  For the most part, support for these systems has not been
3359
deliberately removed, but it has not been maintained for several years
3360
and may suffer from bitrot.
3361
 
3362
   Starting with GCC 3.1, each release has a list of "obsoleted"
3363
systems.  Support for these systems is still present in that release,
3364
but `configure' will fail unless the `--enable-obsolete' option is
3365
given.  Unless a maintainer steps forward, support for these systems
3366
will be removed from the next release of GCC.
3367
 
3368
   Support for old systems as hosts for GCC can cause problems if the
3369
workarounds for compiler, library and operating system bugs affect the
3370
cleanliness or maintainability of the rest of GCC.  In some cases, to
3371
bring GCC up on such a system, if still possible with current GCC, may
3372
require first installing an old version of GCC which did work on that
3373
system, and using it to compile a more recent GCC, to avoid bugs in the
3374
vendor compiler.  Old releases of GCC 1 and GCC 2 are available in the
3375
`old-releases' directory on the GCC mirror sites.  Header bugs may
3376
generally be avoided using `fixincludes', but bugs or deficiencies in
3377
libraries and the operating system may still cause problems.
3378
 
3379
   Support for older systems as targets for cross-compilation is less
3380
problematic than support for them as hosts for GCC; if an enthusiast
3381
wishes to make such a target work again (including resurrecting any of
3382
the targets that never worked with GCC 2, starting from the last
3383
version before they were removed), patches following the usual
3384
requirements would be likely to be accepted, since they should not
3385
affect the support for more modern targets.
3386
 
3387
   For some systems, old versions of GNU binutils may also be useful,
3388
and are available from `pub/binutils/old-releases' on sourceware.org
3389
mirror sites.
3390
 
3391
   Some of the information on specific systems above relates to such
3392
older systems, but much of the information about GCC on such systems
3393
(which may no longer be applicable to current GCC) is to be found in
3394
the GCC texinfo manual.
3395
 
3396
all ELF targets (SVR4, Solaris 2, etc.)
3397
=======================================
3398
 
3399
C++ support is significantly better on ELF targets if you use the GNU
3400
linker; duplicate copies of inlines, vtables and template
3401
instantiations will be discarded automatically.
3402
 
3403

3404
File: gccinstall.info,  Node: Old,  Next: GNU Free Documentation License,  Prev: Specific,  Up: Top
3405
 
3406
10 Old installation documentation
3407
*********************************
3408
 
3409
   Note most of this information is out of date and superseded by the
3410
previous chapters of this manual.  It is provided for historical
3411
reference only, because of a lack of volunteers to merge it into the
3412
main manual.
3413
 
3414
* Menu:
3415
 
3416
* Configurations::    Configurations Supported by GCC.
3417
 
3418
   Here is the procedure for installing GCC on a GNU or Unix system.
3419
 
3420
  1. If you have chosen a configuration for GCC which requires other GNU
3421
     tools (such as GAS or the GNU linker) instead of the standard
3422
     system tools, install the required tools in the build directory
3423
     under the names `as', `ld' or whatever is appropriate.
3424
 
3425
     Alternatively, you can do subsequent compilation using a value of
3426
     the `PATH' environment variable such that the necessary GNU tools
3427
     come before the standard system tools.
3428
 
3429
  2. Specify the host, build and target machine configurations.  You do
3430
     this when you run the `configure' script.
3431
 
3432
     The "build" machine is the system which you are using, the "host"
3433
     machine is the system where you want to run the resulting compiler
3434
     (normally the build machine), and the "target" machine is the
3435
     system for which you want the compiler to generate code.
3436
 
3437
     If you are building a compiler to produce code for the machine it
3438
     runs on (a native compiler), you normally do not need to specify
3439
     any operands to `configure'; it will try to guess the type of
3440
     machine you are on and use that as the build, host and target
3441
     machines.  So you don't need to specify a configuration when
3442
     building a native compiler unless `configure' cannot figure out
3443
     what your configuration is or guesses wrong.
3444
 
3445
     In those cases, specify the build machine's "configuration name"
3446
     with the `--host' option; the host and target will default to be
3447
     the same as the host machine.
3448
 
3449
     Here is an example:
3450
 
3451
          ./configure --host=sparc-sun-sunos4.1
3452
 
3453
     A configuration name may be canonical or it may be more or less
3454
     abbreviated.
3455
 
3456
     A canonical configuration name has three parts, separated by
3457
     dashes.  It looks like this: `CPU-COMPANY-SYSTEM'.  (The three
3458
     parts may themselves contain dashes; `configure' can figure out
3459
     which dashes serve which purpose.)  For example,
3460
     `m68k-sun-sunos4.1' specifies a Sun 3.
3461
 
3462
     You can also replace parts of the configuration by nicknames or
3463
     aliases.  For example, `sun3' stands for `m68k-sun', so
3464
     `sun3-sunos4.1' is another way to specify a Sun 3.
3465
 
3466
     You can specify a version number after any of the system types,
3467
     and some of the CPU types.  In most cases, the version is
3468
     irrelevant, and will be ignored.  So you might as well specify the
3469
     version if you know it.
3470
 
3471
     See *Note Configurations::, for a list of supported configuration
3472
     names and notes on many of the configurations.  You should check
3473
     the notes in that section before proceeding any further with the
3474
     installation of GCC.
3475
 
3476
 
3477

3478
File: gccinstall.info,  Node: Configurations,  Up: Old
3479
 
3480
10.1 Configurations Supported by GCC
3481
====================================
3482
 
3483
   Here are the possible CPU types:
3484
 
3485
     1750a, a29k, alpha, arm, avr, cN, clipper, dsp16xx, elxsi, fr30,
3486
     h8300, hppa1.0, hppa1.1, i370, i386, i486, i586, i686, i786, i860,
3487
     i960, ip2k, m32r, m68000, m68k, m6811, m6812, m88k, mcore, mips,
3488
     mipsel, mips64, mips64el, mn10200, mn10300, ns32k, pdp11, powerpc,
3489
     powerpcle, romp, rs6000, sh, sparc, sparclite, sparc64, v850, vax,
3490
     we32k.
3491
 
3492
   Here are the recognized company names.  As you can see, customary
3493
abbreviations are used rather than the longer official names.
3494
 
3495
     acorn, alliant, altos, apollo, apple, att, bull, cbm, convergent,
3496
     convex, crds, dec, dg, dolphin, elxsi, encore, harris, hitachi,
3497
     hp, ibm, intergraph, isi, mips, motorola, ncr, next, ns, omron,
3498
     plexus, sequent, sgi, sony, sun, tti, unicom, wrs.
3499
 
3500
   The company name is meaningful only to disambiguate when the rest of
3501
the information supplied is insufficient.  You can omit it, writing
3502
just `CPU-SYSTEM', if it is not needed.  For example, `vax-ultrix4.2'
3503
is equivalent to `vax-dec-ultrix4.2'.
3504
 
3505
   Here is a list of system types:
3506
 
3507
     386bsd, aix, acis, amigaos, aos, aout, aux, bosx, bsd, clix, coff,
3508
     ctix, cxux, dgux, dynix, ebmon, ecoff, elf, esix, freebsd, hms,
3509
     genix, gnu, linux, linux-gnu, hiux, hpux, iris, irix, isc, luna,
3510
     lynxos, mach, minix, msdos, mvs, netbsd, newsos, nindy, ns, osf,
3511
     osfrose, ptx, riscix, riscos, rtu, sco, sim, solaris, sunos, sym,
3512
     sysv, udi, ultrix, unicos, uniplus, unos, vms, vsta, vxworks,
3513
     winnt, xenix.
3514
 
3515
You can omit the system type; then `configure' guesses the operating
3516
system from the CPU and company.
3517
 
3518
   You can add a version number to the system type; this may or may not
3519
make a difference.  For example, you can write `bsd4.3' or `bsd4.4' to
3520
distinguish versions of BSD.  In practice, the version number is most
3521
needed for `sysv3' and `sysv4', which are often treated differently.
3522
 
3523
   `linux-gnu' is the canonical name for the GNU/Linux target; however
3524
GCC will also accept `linux'.  The version of the kernel in use is not
3525
relevant on these systems.  A suffix such as `libc1' or `aout'
3526
distinguishes major versions of the C library; all of the suffixed
3527
versions are obsolete.
3528
 
3529
   If you specify an impossible combination such as `i860-dg-vms', then
3530
you may get an error message from `configure', or it may ignore part of
3531
the information and do the best it can with the rest.  `configure'
3532
always prints the canonical name for the alternative that it used.  GCC
3533
does not support all possible alternatives.
3534
 
3535
   Often a particular model of machine has a name.  Many machine names
3536
are recognized as aliases for CPU/company combinations.  Thus, the
3537
machine name `sun3', mentioned above, is an alias for `m68k-sun'.
3538
Sometimes we accept a company name as a machine name, when the name is
3539
popularly used for a particular machine.  Here is a table of the known
3540
machine names:
3541
 
3542
     3300, 3b1, 3bN, 7300, altos3068, altos, apollo68, att-7300,
3543
     balance, convex-cN, crds, decstation-3100, decstation, delta,
3544
     encore, fx2800, gmicro, hp7NN, hp8NN, hp9k2NN, hp9k3NN, hp9k7NN,
3545
     hp9k8NN, iris4d, iris, isi68, m3230, magnum, merlin, miniframe,
3546
     mmax, news-3600, news800, news, next, pbd, pc532, pmax, powerpc,
3547
     powerpcle, ps2, risc-news, rtpc, sun2, sun386i, sun386, sun3,
3548
     sun4, symmetry, tower-32, tower.
3549
 
3550
Remember that a machine name specifies both the cpu type and the company
3551
name.  If you want to install your own homemade configuration files,
3552
you can use `local' as the company name to access them.  If you use
3553
configuration `CPU-local', the configuration name without the cpu prefix
3554
is used to form the configuration file names.
3555
 
3556
   Thus, if you specify `m68k-local', configuration uses files
3557
`m68k.md', `local.h', `m68k.c', `xm-local.h', `t-local', and `x-local',
3558
all in the directory `config/m68k'.
3559
 
3560

3561
File: gccinstall.info,  Node: GNU Free Documentation License,  Next: Concept Index,  Prev: Old,  Up: Top
3562
 
3563
GNU Free Documentation License
3564
******************************
3565
 
3566
                      Version 1.2, November 2002
3567
 
3568
     Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.
3569
     51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA
3570
 
3571
     Everyone is permitted to copy and distribute verbatim copies
3572
     of this license document, but changing it is not allowed.
3573
 
3574
  0. PREAMBLE
3575
 
3576
     The purpose of this License is to make a manual, textbook, or other
3577
     functional and useful document "free" in the sense of freedom: to
3578
     assure everyone the effective freedom to copy and redistribute it,
3579
     with or without modifying it, either commercially or
3580
     noncommercially.  Secondarily, this License preserves for the
3581
     author and publisher a way to get credit for their work, while not
3582
     being considered responsible for modifications made by others.
3583
 
3584
     This License is a kind of "copyleft", which means that derivative
3585
     works of the document must themselves be free in the same sense.
3586
     It complements the GNU General Public License, which is a copyleft
3587
     license designed for free software.
3588
 
3589
     We have designed this License in order to use it for manuals for
3590
     free software, because free software needs free documentation: a
3591
     free program should come with manuals providing the same freedoms
3592
     that the software does.  But this License is not limited to
3593
     software manuals; it can be used for any textual work, regardless
3594
     of subject matter or whether it is published as a printed book.
3595
     We recommend this License principally for works whose purpose is
3596
     instruction or reference.
3597
 
3598
  1. APPLICABILITY AND DEFINITIONS
3599
 
3600
     This License applies to any manual or other work, in any medium,
3601
     that contains a notice placed by the copyright holder saying it
3602
     can be distributed under the terms of this License.  Such a notice
3603
     grants a world-wide, royalty-free license, unlimited in duration,
3604
     to use that work under the conditions stated herein.  The
3605
     "Document", below, refers to any such manual or work.  Any member
3606
     of the public is a licensee, and is addressed as "you".  You
3607
     accept the license if you copy, modify or distribute the work in a
3608
     way requiring permission under copyright law.
3609
 
3610
     A "Modified Version" of the Document means any work containing the
3611
     Document or a portion of it, either copied verbatim, or with
3612
     modifications and/or translated into another language.
3613
 
3614
     A "Secondary Section" is a named appendix or a front-matter section
3615
     of the Document that deals exclusively with the relationship of the
3616
     publishers or authors of the Document to the Document's overall
3617
     subject (or to related matters) and contains nothing that could
3618
     fall directly within that overall subject.  (Thus, if the Document
3619
     is in part a textbook of mathematics, a Secondary Section may not
3620
     explain any mathematics.)  The relationship could be a matter of
3621
     historical connection with the subject or with related matters, or
3622
     of legal, commercial, philosophical, ethical or political position
3623
     regarding them.
3624
 
3625
     The "Invariant Sections" are certain Secondary Sections whose
3626
     titles are designated, as being those of Invariant Sections, in
3627
     the notice that says that the Document is released under this
3628
     License.  If a section does not fit the above definition of
3629
     Secondary then it is not allowed to be designated as Invariant.
3630
     The Document may contain zero Invariant Sections.  If the Document
3631
     does not identify any Invariant Sections then there are none.
3632
 
3633
     The "Cover Texts" are certain short passages of text that are
3634
     listed, as Front-Cover Texts or Back-Cover Texts, in the notice
3635
     that says that the Document is released under this License.  A
3636
     Front-Cover Text may be at most 5 words, and a Back-Cover Text may
3637
     be at most 25 words.
3638
 
3639
     A "Transparent" copy of the Document means a machine-readable copy,
3640
     represented in a format whose specification is available to the
3641
     general public, that is suitable for revising the document
3642
     straightforwardly with generic text editors or (for images
3643
     composed of pixels) generic paint programs or (for drawings) some
3644
     widely available drawing editor, and that is suitable for input to
3645
     text formatters or for automatic translation to a variety of
3646
     formats suitable for input to text formatters.  A copy made in an
3647
     otherwise Transparent file format whose markup, or absence of
3648
     markup, has been arranged to thwart or discourage subsequent
3649
     modification by readers is not Transparent.  An image format is
3650
     not Transparent if used for any substantial amount of text.  A
3651
     copy that is not "Transparent" is called "Opaque".
3652
 
3653
     Examples of suitable formats for Transparent copies include plain
3654
     ASCII without markup, Texinfo input format, LaTeX input format,
3655
     SGML or XML using a publicly available DTD, and
3656
     standard-conforming simple HTML, PostScript or PDF designed for
3657
     human modification.  Examples of transparent image formats include
3658
     PNG, XCF and JPG.  Opaque formats include proprietary formats that
3659
     can be read and edited only by proprietary word processors, SGML or
3660
     XML for which the DTD and/or processing tools are not generally
3661
     available, and the machine-generated HTML, PostScript or PDF
3662
     produced by some word processors for output purposes only.
3663
 
3664
     The "Title Page" means, for a printed book, the title page itself,
3665
     plus such following pages as are needed to hold, legibly, the
3666
     material this License requires to appear in the title page.  For
3667
     works in formats which do not have any title page as such, "Title
3668
     Page" means the text near the most prominent appearance of the
3669
     work's title, preceding the beginning of the body of the text.
3670
 
3671
     A section "Entitled XYZ" means a named subunit of the Document
3672
     whose title either is precisely XYZ or contains XYZ in parentheses
3673
     following text that translates XYZ in another language.  (Here XYZ
3674
     stands for a specific section name mentioned below, such as
3675
     "Acknowledgements", "Dedications", "Endorsements", or "History".)
3676
     To "Preserve the Title" of such a section when you modify the
3677
     Document means that it remains a section "Entitled XYZ" according
3678
     to this definition.
3679
 
3680
     The Document may include Warranty Disclaimers next to the notice
3681
     which states that this License applies to the Document.  These
3682
     Warranty Disclaimers are considered to be included by reference in
3683
     this License, but only as regards disclaiming warranties: any other
3684
     implication that these Warranty Disclaimers may have is void and
3685
     has no effect on the meaning of this License.
3686
 
3687
  2. VERBATIM COPYING
3688
 
3689
     You may copy and distribute the Document in any medium, either
3690
     commercially or noncommercially, provided that this License, the
3691
     copyright notices, and the license notice saying this License
3692
     applies to the Document are reproduced in all copies, and that you
3693
     add no other conditions whatsoever to those of this License.  You
3694
     may not use technical measures to obstruct or control the reading
3695
     or further copying of the copies you make or distribute.  However,
3696
     you may accept compensation in exchange for copies.  If you
3697
     distribute a large enough number of copies you must also follow
3698
     the conditions in section 3.
3699
 
3700
     You may also lend copies, under the same conditions stated above,
3701
     and you may publicly display copies.
3702
 
3703
  3. COPYING IN QUANTITY
3704
 
3705
     If you publish printed copies (or copies in media that commonly
3706
     have printed covers) of the Document, numbering more than 100, and
3707
     the Document's license notice requires Cover Texts, you must
3708
     enclose the copies in covers that carry, clearly and legibly, all
3709
     these Cover Texts: Front-Cover Texts on the front cover, and
3710
     Back-Cover Texts on the back cover.  Both covers must also clearly
3711
     and legibly identify you as the publisher of these copies.  The
3712
     front cover must present the full title with all words of the
3713
     title equally prominent and visible.  You may add other material
3714
     on the covers in addition.  Copying with changes limited to the
3715
     covers, as long as they preserve the title of the Document and
3716
     satisfy these conditions, can be treated as verbatim copying in
3717
     other respects.
3718
 
3719
     If the required texts for either cover are too voluminous to fit
3720
     legibly, you should put the first ones listed (as many as fit
3721
     reasonably) on the actual cover, and continue the rest onto
3722
     adjacent pages.
3723
 
3724
     If you publish or distribute Opaque copies of the Document
3725
     numbering more than 100, you must either include a
3726
     machine-readable Transparent copy along with each Opaque copy, or
3727
     state in or with each Opaque copy a computer-network location from
3728
     which the general network-using public has access to download
3729
     using public-standard network protocols a complete Transparent
3730
     copy of the Document, free of added material.  If you use the
3731
     latter option, you must take reasonably prudent steps, when you
3732
     begin distribution of Opaque copies in quantity, to ensure that
3733
     this Transparent copy will remain thus accessible at the stated
3734
     location until at least one year after the last time you
3735
     distribute an Opaque copy (directly or through your agents or
3736
     retailers) of that edition to the public.
3737
 
3738
     It is requested, but not required, that you contact the authors of
3739
     the Document well before redistributing any large number of
3740
     copies, to give them a chance to provide you with an updated
3741
     version of the Document.
3742
 
3743
  4. MODIFICATIONS
3744
 
3745
     You may copy and distribute a Modified Version of the Document
3746
     under the conditions of sections 2 and 3 above, provided that you
3747
     release the Modified Version under precisely this License, with
3748
     the Modified Version filling the role of the Document, thus
3749
     licensing distribution and modification of the Modified Version to
3750
     whoever possesses a copy of it.  In addition, you must do these
3751
     things in the Modified Version:
3752
 
3753
       A. Use in the Title Page (and on the covers, if any) a title
3754
          distinct from that of the Document, and from those of
3755
          previous versions (which should, if there were any, be listed
3756
          in the History section of the Document).  You may use the
3757
          same title as a previous version if the original publisher of
3758
          that version gives permission.
3759
 
3760
       B. List on the Title Page, as authors, one or more persons or
3761
          entities responsible for authorship of the modifications in
3762
          the Modified Version, together with at least five of the
3763
          principal authors of the Document (all of its principal
3764
          authors, if it has fewer than five), unless they release you
3765
          from this requirement.
3766
 
3767
       C. State on the Title page the name of the publisher of the
3768
          Modified Version, as the publisher.
3769
 
3770
       D. Preserve all the copyright notices of the Document.
3771
 
3772
       E. Add an appropriate copyright notice for your modifications
3773
          adjacent to the other copyright notices.
3774
 
3775
       F. Include, immediately after the copyright notices, a license
3776
          notice giving the public permission to use the Modified
3777
          Version under the terms of this License, in the form shown in
3778
          the Addendum below.
3779
 
3780
       G. Preserve in that license notice the full lists of Invariant
3781
          Sections and required Cover Texts given in the Document's
3782
          license notice.
3783
 
3784
       H. Include an unaltered copy of this License.
3785
 
3786
       I. Preserve the section Entitled "History", Preserve its Title,
3787
          and add to it an item stating at least the title, year, new
3788
          authors, and publisher of the Modified Version as given on
3789
          the Title Page.  If there is no section Entitled "History" in
3790
          the Document, create one stating the title, year, authors,
3791
          and publisher of the Document as given on its Title Page,
3792
          then add an item describing the Modified Version as stated in
3793
          the previous sentence.
3794
 
3795
       J. Preserve the network location, if any, given in the Document
3796
          for public access to a Transparent copy of the Document, and
3797
          likewise the network locations given in the Document for
3798
          previous versions it was based on.  These may be placed in
3799
          the "History" section.  You may omit a network location for a
3800
          work that was published at least four years before the
3801
          Document itself, or if the original publisher of the version
3802
          it refers to gives permission.
3803
 
3804
       K. For any section Entitled "Acknowledgements" or "Dedications",
3805
          Preserve the Title of the section, and preserve in the
3806
          section all the substance and tone of each of the contributor
3807
          acknowledgements and/or dedications given therein.
3808
 
3809
       L. Preserve all the Invariant Sections of the Document,
3810
          unaltered in their text and in their titles.  Section numbers
3811
          or the equivalent are not considered part of the section
3812
          titles.
3813
 
3814
       M. Delete any section Entitled "Endorsements".  Such a section
3815
          may not be included in the Modified Version.
3816
 
3817
       N. Do not retitle any existing section to be Entitled
3818
          "Endorsements" or to conflict in title with any Invariant
3819
          Section.
3820
 
3821
       O. Preserve any Warranty Disclaimers.
3822
 
3823
     If the Modified Version includes new front-matter sections or
3824
     appendices that qualify as Secondary Sections and contain no
3825
     material copied from the Document, you may at your option
3826
     designate some or all of these sections as invariant.  To do this,
3827
     add their titles to the list of Invariant Sections in the Modified
3828
     Version's license notice.  These titles must be distinct from any
3829
     other section titles.
3830
 
3831
     You may add a section Entitled "Endorsements", provided it contains
3832
     nothing but endorsements of your Modified Version by various
3833
     parties--for example, statements of peer review or that the text
3834
     has been approved by an organization as the authoritative
3835
     definition of a standard.
3836
 
3837
     You may add a passage of up to five words as a Front-Cover Text,
3838
     and a passage of up to 25 words as a Back-Cover Text, to the end
3839
     of the list of Cover Texts in the Modified Version.  Only one
3840
     passage of Front-Cover Text and one of Back-Cover Text may be
3841
     added by (or through arrangements made by) any one entity.  If the
3842
     Document already includes a cover text for the same cover,
3843
     previously added by you or by arrangement made by the same entity
3844
     you are acting on behalf of, you may not add another; but you may
3845
     replace the old one, on explicit permission from the previous
3846
     publisher that added the old one.
3847
 
3848
     The author(s) and publisher(s) of the Document do not by this
3849
     License give permission to use their names for publicity for or to
3850
     assert or imply endorsement of any Modified Version.
3851
 
3852
  5. COMBINING DOCUMENTS
3853
 
3854
     You may combine the Document with other documents released under
3855
     this License, under the terms defined in section 4 above for
3856
     modified versions, provided that you include in the combination
3857
     all of the Invariant Sections of all of the original documents,
3858
     unmodified, and list them all as Invariant Sections of your
3859
     combined work in its license notice, and that you preserve all
3860
     their Warranty Disclaimers.
3861
 
3862
     The combined work need only contain one copy of this License, and
3863
     multiple identical Invariant Sections may be replaced with a single
3864
     copy.  If there are multiple Invariant Sections with the same name
3865
     but different contents, make the title of each such section unique
3866
     by adding at the end of it, in parentheses, the name of the
3867
     original author or publisher of that section if known, or else a
3868
     unique number.  Make the same adjustment to the section titles in
3869
     the list of Invariant Sections in the license notice of the
3870
     combined work.
3871
 
3872
     In the combination, you must combine any sections Entitled
3873
     "History" in the various original documents, forming one section
3874
     Entitled "History"; likewise combine any sections Entitled
3875
     "Acknowledgements", and any sections Entitled "Dedications".  You
3876
     must delete all sections Entitled "Endorsements."
3877
 
3878
  6. COLLECTIONS OF DOCUMENTS
3879
 
3880
     You may make a collection consisting of the Document and other
3881
     documents released under this License, and replace the individual
3882
     copies of this License in the various documents with a single copy
3883
     that is included in the collection, provided that you follow the
3884
     rules of this License for verbatim copying of each of the
3885
     documents in all other respects.
3886
 
3887
     You may extract a single document from such a collection, and
3888
     distribute it individually under this License, provided you insert
3889
     a copy of this License into the extracted document, and follow
3890
     this License in all other respects regarding verbatim copying of
3891
     that document.
3892
 
3893
  7. AGGREGATION WITH INDEPENDENT WORKS
3894
 
3895
     A compilation of the Document or its derivatives with other
3896
     separate and independent documents or works, in or on a volume of
3897
     a storage or distribution medium, is called an "aggregate" if the
3898
     copyright resulting from the compilation is not used to limit the
3899
     legal rights of the compilation's users beyond what the individual
3900
     works permit.  When the Document is included in an aggregate, this
3901
     License does not apply to the other works in the aggregate which
3902
     are not themselves derivative works of the Document.
3903
 
3904
     If the Cover Text requirement of section 3 is applicable to these
3905
     copies of the Document, then if the Document is less than one half
3906
     of the entire aggregate, the Document's Cover Texts may be placed
3907
     on covers that bracket the Document within the aggregate, or the
3908
     electronic equivalent of covers if the Document is in electronic
3909
     form.  Otherwise they must appear on printed covers that bracket
3910
     the whole aggregate.
3911
 
3912
  8. TRANSLATION
3913
 
3914
     Translation is considered a kind of modification, so you may
3915
     distribute translations of the Document under the terms of section
3916
     4.  Replacing Invariant Sections with translations requires special
3917
     permission from their copyright holders, but you may include
3918
     translations of some or all Invariant Sections in addition to the
3919
     original versions of these Invariant Sections.  You may include a
3920
     translation of this License, and all the license notices in the
3921
     Document, and any Warranty Disclaimers, provided that you also
3922
     include the original English version of this License and the
3923
     original versions of those notices and disclaimers.  In case of a
3924
     disagreement between the translation and the original version of
3925
     this License or a notice or disclaimer, the original version will
3926
     prevail.
3927
 
3928
     If a section in the Document is Entitled "Acknowledgements",
3929
     "Dedications", or "History", the requirement (section 4) to
3930
     Preserve its Title (section 1) will typically require changing the
3931
     actual title.
3932
 
3933
  9. TERMINATION
3934
 
3935
     You may not copy, modify, sublicense, or distribute the Document
3936
     except as expressly provided for under this License.  Any other
3937
     attempt to copy, modify, sublicense or distribute the Document is
3938
     void, and will automatically terminate your rights under this
3939
     License.  However, parties who have received copies, or rights,
3940
     from you under this License will not have their licenses
3941
     terminated so long as such parties remain in full compliance.
3942
 
3943
 10. FUTURE REVISIONS OF THIS LICENSE
3944
 
3945
     The Free Software Foundation may publish new, revised versions of
3946
     the GNU Free Documentation License from time to time.  Such new
3947
     versions will be similar in spirit to the present version, but may
3948
     differ in detail to address new problems or concerns.  See
3949
     `http://www.gnu.org/copyleft/'.
3950
 
3951
     Each version of the License is given a distinguishing version
3952
     number.  If the Document specifies that a particular numbered
3953
     version of this License "or any later version" applies to it, you
3954
     have the option of following the terms and conditions either of
3955
     that specified version or of any later version that has been
3956
     published (not as a draft) by the Free Software Foundation.  If
3957
     the Document does not specify a version number of this License,
3958
     you may choose any version ever published (not as a draft) by the
3959
     Free Software Foundation.
3960
 
3961
ADDENDUM: How to use this License for your documents
3962
====================================================
3963
 
3964
To use this License in a document you have written, include a copy of
3965
the License in the document and put the following copyright and license
3966
notices just after the title page:
3967
 
3968
       Copyright (C)  YEAR  YOUR NAME.
3969
       Permission is granted to copy, distribute and/or modify this document
3970
       under the terms of the GNU Free Documentation License, Version 1.2
3971
       or any later version published by the Free Software Foundation;
3972
       with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
3973
       Texts.  A copy of the license is included in the section entitled ``GNU
3974
       Free Documentation License''.
3975
 
3976
   If you have Invariant Sections, Front-Cover Texts and Back-Cover
3977
Texts, replace the "with...Texts." line with this:
3978
 
3979
         with the Invariant Sections being LIST THEIR TITLES, with
3980
         the Front-Cover Texts being LIST, and with the Back-Cover Texts
3981
         being LIST.
3982
 
3983
   If you have Invariant Sections without Cover Texts, or some other
3984
combination of the three, merge those two alternatives to suit the
3985
situation.
3986
 
3987
   If your document contains nontrivial examples of program code, we
3988
recommend releasing these examples in parallel under your choice of
3989
free software license, such as the GNU General Public License, to
3990
permit their use in free software.
3991
 
3992

3993
File: gccinstall.info,  Node: Concept Index,  Prev: GNU Free Documentation License,  Up: Top
3994
 
3995
Concept Index
3996
*************
3997
 
3998
 
3999
* Menu:
4000
4001
* Binaries:                              Binaries.              (line 6)
4002
* Configuration:                         Configuration.         (line 6)
4003
* configurations supported by GCC:       Configurations.        (line 6)
4004
* Downloading GCC:                       Downloading the source.
4005
                                                                (line 6)
4006
* Downloading the Source:                Downloading the source.
4007
                                                                (line 6)
4008
* FDL, GNU Free Documentation License:   GNU Free Documentation License.
4009
                                                                (line 6)
4010
* Host specific installation:            Specific.              (line 6)
4011
* Installing GCC: Binaries:              Binaries.              (line 6)
4012
* Installing GCC: Building:              Building.              (line 6)
4013
* Installing GCC: Configuration:         Configuration.         (line 6)
4014
* Installing GCC: Testing:               Testing.               (line 6)
4015
* Prerequisites:                         Prerequisites.         (line 6)
4016
* Specific:                              Specific.              (line 6)
4017
* Specific installation notes:           Specific.              (line 6)
4018
* Target specific installation:          Specific.              (line 6)
4019
 
4020
 
4021
* Testsuite:                             Testing.               (line 6)
4022
4023
4024

4025
Tag Table:
4026
Node: Top1945
4027
Node: Installing GCC2503
4028
Node: Prerequisites4018
4029
Node: Downloading the source11338
4030
Node: Configuration12972
4031
Ref: with-gnu-as25506
4032
Ref: with-as26736
4033
Ref: with-gnu-ld28149
4034
Node: Building56454
4035
Node: Testing67467
4036
Node: Final install75329
4037
Node: Binaries80376
4038
Node: Specific82240
4039
Ref: alpha-x-x82746
4040
Ref: alpha-dec-osf83235
4041
Ref: alphaev5-cray-unicosmk86812
4042
Ref: arc-x-elf87732
4043
Ref: arm-x-elf87832
4044
Ref: xscale-x-x87853
4045
Ref: arm-x-coff88089
4046
Ref: arm-x-aout88291
4047
Ref: avr88413
4048
Ref: bfin89097
4049
Ref: c4x89339
4050
Ref: cris89937
4051
Ref: crx90919
4052
Ref: dos91582
4053
Ref: x-x-freebsd91905
4054
Ref: h8300-hms94288
4055
Ref: hppa-hp-hpux94640
4056
Ref: hppa-hp-hpux1097128
4057
Ref: hppa-hp-hpux1198185
4058
Ref: x-x-linux-gnu105053
4059
Ref: ix86-x-linuxaout105245
4060
Ref: ix86-x-linux105404
4061
Ref: ix86-x-sco32v5105717
4062
Ref: ix86-x-solaris210107886
4063
Ref: ix86-x-udk108272
4064
Ref: ia64-x-linux109625
4065
Ref: ia64-x-hpux110395
4066
Ref: x-ibm-aix110950
4067
Ref: iq2000-x-elf116933
4068
Ref: m32c-x-elf117073
4069
Ref: m32r-x-elf117175
4070
Ref: m6811-elf117277
4071
Ref: m6812-elf117427
4072
Ref: m68k-hp-hpux117577
4073
Ref: mips-x-x119316
4074
Ref: mips-sgi-irix5121470
4075
Ref: mips-sgi-irix6122418
4076
Ref: powerpc-x-x125328
4077
Ref: powerpc-x-darwin125473
4078
Ref: powerpc-x-elf126064
4079
Ref: powerpc-x-linux-gnu126183
4080
Ref: powerpc-x-netbsd126285
4081
Ref: powerpc-x-eabisim126481
4082
Ref: powerpc-x-eabi126607
4083
Ref: powerpcle-x-elf126683
4084
Ref: powerpcle-x-eabisim126813
4085
Ref: powerpcle-x-eabi126946
4086
Ref: s390-x-linux127029
4087
Ref: s390x-x-linux127101
4088
Ref: s390x-ibm-tpf127188
4089
Ref: x-x-solaris2127319
4090
Ref: sparc-sun-solaris2131347
4091
Ref: sparc-sun-solaris27134511
4092
Ref: sparc-x-linux136975
4093
Ref: sparc64-x-solaris2137200
4094
Ref: sparcv9-x-solaris2137845
4095
Ref: x-x-sysv137930
4096
Ref: vax-dec-ultrix138891
4097
Ref: x-x-vxworks139043
4098
Ref: x86-64-x-x140565
4099
Ref: xtensa-x-elf140893
4100
Ref: xtensa-x-linux141562
4101
Ref: windows141900
4102
Ref: os2142154
4103
Ref: older142345
4104
Ref: elf144462
4105
Node: Old144720
4106
Node: Configurations147857
4107
Node: GNU Free Documentation License151839

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.