Note that this list of install notes is not a list of supported +hosts or targets. Not all supported hosts and targets are listed +here, only the ones that require host-specific or target-specific +information are. +
MIL-STD-1750A processors. This target is obsoleted in GCC 3.1. - -
The MIL-STD-1750A cross configuration produces output for
-as1750, an assembler/linker available under the GNU General Public
-License for the 1750A. as1750 can be obtained at
-ftp://ftp.fta-berlin.de/pub/crossgcc/1750gals/.
-A similarly licensed simulator for
-the 1750A is available from same address.
-
-
You should ignore a fatal error during the building of libgcc
-(libgcc is not yet implemented for the 1750A.)
-
-
The as1750 assembler requires the file ms1750.inc, which is
-found in the directory gcc/config/1750a.
-
-
GCC produced the same sections as the Fairchild F9450 C Compiler, -namely: - -
Normal
- Static
- Konst
- Init
- The smallest addressable unit is 16 bits (BITS_PER_UNIT is 16). This
-means that type char is represented with a 16-bit word per character.
-The 1750A's "Load/Store Upper/Lower Byte" instructions are not used by
-GCC.
-
-
AMD Am29k-family processors. These are normally used in embedded -applications. This configuration corresponds to AMD's standard calling -sequence and binary interface and is compatible with other 29k tools. - -
AMD has abandoned this processor. All existing a29k targets are obsoleted -in GCC 3.1. - -
You may need to make a variant of the file a29k.h for your
-particular configuration.
-
-
AMD Am29050 used in a system running a variant of BSD Unix. - -
This section contains general configuration information for all +
This section contains general configuration information for all alpha-based platforms using ELF (in particular, ignore this section for DEC OSF/1, Digital UNIX and Tru64 UNIX). In addition to reading this section, please read all other sections that match your target. @@ -194,233 +132,161 @@ Previous binutils releases had a number of problems with DWARF 2 debugging information, not the least of which is incorrect linking of shared libraries. -
Systems using processors that implement the DEC Alpha architecture and +
Systems using processors that implement the DEC Alpha architecture and are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq Tru64 UNIX) operating system, for example the DEC Alpha AXP systems. -
Support for versions before alpha*-dec-osf4 is obsoleted in GCC
-3.1. (These are the versions which identify themselves as DEC OSF/1.)
+
As of GCC 3.2, versions before alpha*-dec-osf4 are no longer
+supported. (These are the versions which identify themselves as DEC
+OSF/1.)
In Digital Unix V4.0, virtual memory exhausted bootstrap failures
-may be fixed by configuring with --with-gc=simple,
+may be fixed by configuring with --with-gc=simple,
reconfiguring Kernel Virtual Memory and Swap parameters
-per the /usr/sbin/sys_check Tuning Suggestions,
+per the /usr/sbin/sys_check Tuning Suggestions,
or applying the patch in
http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html.
In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
-currently (2001-06-13) work with mips-tfile. As a workaround,
+currently (2001-06-13) work with mips-tfile. As a workaround,
we need to use the old assembler, invoked via the barely documented
--oldas option. To bootstrap GCC, you either need to use the
+-oldas option. To bootstrap GCC, you either need to use the
Compaq C Compiler:
-
% CC=cc srcdir/configure [options] [target] -- +
% CC=cc srcdir/configure [options] [target] +
or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0: -
% CC=gcc -Wa,-oldas srcdir/configure [options] [target] -- -
As of GNU binutils 2.11.2, neither GNU as nor GNU ld
+
% CC=gcc -Wa,-oldas srcdir/configure [options] [target] ++
As of GNU binutils 2.11.2, neither GNU as nor GNU ld
are supported on Tru64 UNIX, so you must not configure GCC with
---with-gnu-as or --with-gnu-ld.
+--with-gnu-as or --with-gnu-ld.
-
The --enable-threads options isn't supported yet. A patch is
-in preparation for a future release.
-
-
GCC writes a .verstamp directive to the assembler output file
+
GCC writes a ‘.verstamp’ directive to the assembler output file
unless it is built as a cross-compiler. It gets the version to use from
-the system header file /usr/include/stamp.h. If you install a
+the system header file /usr/include/stamp.h. If you install a
new version of DEC Unix, you should rebuild GCC to pick up the new version
stamp.
-
Note that since the Alpha is a 64-bit architecture, cross-compilers from -32-bit machines will not generate code as efficient as that generated -when the compiler is running on a 64-bit machine because many -optimizations that depend on being able to represent a word on the -target in an integral value on the host cannot be performed. Building -cross-compilers on the Alpha for 32-bit machines has only been tested in -a few cases and may not work properly. - -
make compare may fail on old versions of DEC Unix unless you add
--save-temps to CFLAGS. On these systems, the name of the
-assembler input file is stored in the object file, and that makes
+
‘make compare’ may fail on old versions of DEC Unix unless you add
+-save-temps to BOOT_CFLAGS. On these systems, the name
+of the assembler input file is stored in the object file, and that makes
comparison fail if it differs between the stage1 and
-stage2 compilations. The option -save-temps forces a
+stage2 compilations. The option -save-temps forces a
fixed name to be used for the assembler input file, instead of a
-randomly chosen name in /tmp. Do not add -save-temps
+randomly chosen name in /tmp. Do not add -save-temps
unless the comparisons fail without that option. If you add
--save-temps, you will have to manually delete the .i and
-.s files after each series of compilations.
+-save-temps, you will have to manually delete the ‘.i’ and
+‘.s’ files after each series of compilations.
GCC now supports both the native (ECOFF) debugging format used by DBX
and GDB and an encapsulated STABS format for use only with GDB. See the
-discussion of the --with-stabs option of configure above
+discussion of the --with-stabs option of configure above
for more information on these formats and how to select them.
There is a bug in DEC's assembler that produces incorrect line numbers
-for ECOFF format when the .align directive is used. To work
+for ECOFF format when the ‘.align’ directive is used. To work
around this problem, GCC will not emit such alignment directives
while writing ECOFF format debugging information even if optimization is
being performed. Unfortunately, this has the very undesirable
-side-effect that code addresses when -O is specified are
-different depending on whether or not -g is also specified.
+side-effect that code addresses when -O is specified are
+different depending on whether or not -g is also specified.
-
To avoid this behavior, specify -gstabs+ and use GDB instead of
+
To avoid this behavior, specify -gstabs+ and use GDB instead of DBX. DEC is now aware of this problem with the assembler and hopes to provide a fix shortly. -
Cray T3E systems running Unicos/Mk. - -
This port is incomplete and has many known bugs. We hope to improve the
-support for this target soon. Currently, only the C front end is supported,
-and it is not possible to build parallel applications. Cray modules are not
-supported; in particular, Craylibs are assumed to be in
-/opt/ctl/craylibs/craylibs.
-
-
You absolutely must use GNU make on this platform. Also, you
-need to tell GCC where to find the assembler and the linker. The
-simplest way to do so is by providing --with-as and
---with-ld to configure, e.g.
-
-
configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld \ - --enable-languages=c -- -
The comparison test during make bootstrap fails on Unicos/Mk
-because the assembler inserts timestamps into object files. You should
-be able to work around this by doing make all after getting this
-failure.
-
-
Argonaut ARC processor. +
Argonaut ARC processor. This configuration is intended for embedded systems. -
Advanced RISC Machines ARM-family processors. These are often used in
-embedded applications. There are no standard Unix configurations.
-This configuration corresponds to the basic instruction sequences and will
-produce a.out format object modules.
+
ARM-family processors. Subtargets that use the ELF object format
+require GNU binutils 2.13 or newer. Such subtargets include:
+arm-*-freebsd, arm-*-netbsdelf, arm-*-*linux
+and arm-*-rtems.
-
You may need to make a variant of the file arm.h for your particular
-configuration.
+
ARM-family processors. Note that there are two different varieties
+of PE format subtarget supported: arm-wince-pe and
+arm-pe as well as a standard COFF target arm-*-coff.
-
This configuration is intended for embedded systems. +
ARM-family processors. These targets support the AOUT file format:
+arm-*-aout, arm-*-netbsd.
-
We require GNU binutils 2.10 or newer. +
The ARM2 or ARM3 processor running RISC iX, Acorn's port of BSD Unix. -This configuration is obsoleted in GCC 3.1. - -
If you are running a version of RISC iX prior to 1.2 then you must
-specify the version number during configuration. Note that the
-assembler shipped with RISC iX does not support stabs debugging
-information; a new version of the assembler, with stabs support
-included, is now available from Acorn and via ftp
-ftp://ftp.acorn.com/pub/riscix/as+xterm.tar.Z. To enable stabs
-debugging, pass --with-gnu-as to configure.
-
-
You will need to install GNU sed before you can run configure.
-
-
ATMEL AVR-family micro controllers. These are used in embedded +
ATMEL AVR-family micro controllers. These are used in embedded applications. There are no standard Unix configurations. -See "AVR Options" in the main manual +See “AVR Options” in the main manual for the list of supported MCU types. -
Use configure --target=avr --enable-languages="c" to configure GCC.
+
Use ‘configure --target=avr --enable-languages="c"’ to configure GCC.
Further installation notes and other useful information about AVR tools can also be obtained from:
We strongly recommend using binutils 2.11 or newer. +
We strongly recommend using binutils 2.13 or newer.
The following error: -
Error: register required -- +
Error: register required +
indicates that you should upgrade to a newer version of the binutils. -
Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal -Processors. These are used in embedded applications. There are no -standard Unix configurations. -See "TMS320C3x/C4x Options" in the main manual -for the list of supported MCU types. +
GCC can be configured as a cross compiler for both the C3x and C4x
-architectures on the same system. Use configure --target=c4x
---enable-languages="c,c++" to configure.
-
-
Further installation notes and other useful information about C4x tools -can also be obtained from: +
The Blackfin processor, an Analog Devices DSP. +See “Blackfin Options” in the main manual -
+More information, and a version of binutils with support for this processor, +is available at http://blackfin.uclinux.org -
CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip +
CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip series. These are used in embedded applications. -
See "CRIS Options" in the main manual +
See “CRIS Options” in the main manual for a list of CRIS-specific options.
There are a few different CRIS targets:
cris-axis-aout
- elinux a.out-based
-target. No multilibs for newer architecture variants.
-cris-axis-elf
- v10 core used in ETRAX 100 LX.
-cris-axis-linux-gnu
- ETRAX 100 LX by default.
+cris-axis-elfcris-axis-linux-gnuFor cris-axis-aout and cris-axis-elf you need binutils 2.11
+
For cris-axis-elf you need binutils 2.11
or newer. For cris-axis-linux-gnu you need binutils 2.12 or newer.
Pre-packaged tools can be obtained from
@@ -428,527 +294,411 @@ or newer. For cris-axis-linux-gnu you need binutils 2.12 or newer.
information about this platform is available at
http://developer.axis.com/.
-
The CRX CompactRISC architecture is a low-power 32-bit architecture with +fast context switching and architectural extensibility features. + +
See “CRX Options” in the main manual for a list of CRX-specific options. + +
Use ‘configure --target=crx-elf --enable-languages=c,c++’ to configure +GCC for building a CRX cross-compiler. The option ‘--target=crx-elf’ +is also used to build the ‘newlib’ C library for CRX. -
It is also possible to build libstdc++-v3 for the CRX architecture. This +needs to be done in a separate step with the following configure settings: +‘gcc/libstdc++-v3/configure --host=crx-elf --with-newlib +--enable-sjlj-exceptions --enable-cxx-flags='-fexceptions -frtti'’ -
Please have a look at our binaries page. +
Please have a look at the binaries page.
You cannot install GCC by itself on MSDOS; it will not compile under any MSDOS compiler except itself. You need to get the complete compilation package DJGPP, which includes binaries as well as sources, and includes all the necessary compilation tools and libraries. -
A port to the AT&T DSP1610 family of processors. +
The version of binutils installed in /usr/bin probably works with +this release of GCC. However, on FreeBSD 4, bootstrapping against the +latest FSF binutils is known to improve overall testsuite results; and, +on FreeBSD/alpha, using binutils 2.14 or later is required to build libjava. -
Support for FreeBSD 1 was discontinued in GCC 3.2. -
The version of binutils installed in /usr/bin is known to work unless
-otherwise specified in any per-architecture notes. However, binutils
-2.12.1 or greater is known to improve overall testsuite results.
-
-
For FreeBSD 1, FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All +
Support for FreeBSD 2 will be discontinued after GCC 3.4. The
+following was true for GCC 3.1 but the current status is unknown.
+For FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
configuration support and files as shipped with GCC 2.95 are still in
place. FreeBSD 2.2.7 has been known to bootstrap completely; however,
it is unknown which version of binutils was used (it is assumed that it
-was the system copy in /usr/bin) and C++ EH failures were noted.
-
-
Support for FreeBSD 1 is obsoleted in GCC 3.1. +was the system copy in /usr/bin) and C++ EH failures were noted.
For FreeBSD using the ELF file format: DWARF 2 debugging is now the
default for all CPU architectures. It had been the default on
-FreeBSD/alpha since its inception. You may use -gstabs instead
-of -g, if you really want the old debugging format. There are
+FreeBSD/alpha since its inception. You may use -gstabs instead
+of -g, if you really want the old debugging format. There are
no known issues with mixing object files and libraries with different
debugging formats. Otherwise, this release of GCC should now match more
of the configuration used in the stock FreeBSD configuration of GCC. In
-particular, --enable-threads is now configured by default.
+particular, --enable-threads is now configured by default.
However, as a general user, do not attempt to replace the system
compiler with this release. Known to bootstrap and check with good
-results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4, 4.5-STABLE and 5-CURRENT.
+results on FreeBSD 4.9-STABLE and 5-CURRENT. In the past, known to
+bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2,
+4.3, 4.4, 4.5, 4.8-STABLE.
-
In principle, --enable-threads is now compatible with
---enable-libgcj on FreeBSD. However, it has only been built
-and tested on i386-*-freebsd4.5 and alpha-*-freebsd5.0.
+
In principle, --enable-threads is now compatible with
+--enable-libgcj on FreeBSD. However, it has only been built
+and tested on ‘i386-*-freebsd[45]’ and ‘alpha-*-freebsd[45]’.
The static
library may be incorrectly built (symbols are missing at link time).
There is a rare timing-based startup hang (probably involves an
-assupmtion about the thread library). Multi-threaded boehm-gc (required for
+assumption about the thread library). Multi-threaded boehm-gc (required for
libjava) exposes severe threaded signal-handling bugs on FreeBSD before
-4.5-RELEASE. The alpha port may not fully bootstrap without some manual
-intervention: gcjh will crash with a floating-point exception while
-generating java/lang/Double.h (just copy the version built on
-i386-*-freebsd* and rerun the top-level gmake with no
-arguments and it
-should properly complete the bootstrap). Other CPU architectures
+4.5-RELEASE. Other CPU architectures
supported by FreeBSD will require additional configuration tuning in, at
the very least, both boehm-gc and libffi.
-
Shared libgcc_s.so is now built and installed by default.
+
Shared libgcc_s.so is now built and installed by default. -
The Elxsi's C compiler has known limitations that prevent it from -compiling GCC. Please contact mrs@wrs.com for more details. +
Renesas H8/300 series of processors. -
Support for this processor is obsoleted in GCC 3.1. - -
Hitachi H8/300 series of processors. - -
Please have a look at our binaries page. +
Please have a look at the binaries page.
The calling convention and structure layout has changed in release 2.6. All code must be recompiled. The calling convention now passes the first three arguments in function calls in registers. Structures are no longer a multiple of 2 bytes. -
We highly recommend using gas/binutils 2.8 or newer on all hppa
-platforms; you may encounter a variety of problems when using the HP
-assembler. The HP assembler does not work with the hppa64-hp-hpux11*
-port.
+
Specifically, -g does not work on HP-UX (since that system
-uses a peculiar debugging format which GCC does not know about), unless you
-use GAS and GDB and configure GCC with the
---with-gnu-as and
---with-as=... options.
+
If you wish to use the pa-risc 2.0 architecture support with a 32-bit -runtime, you must use either the HP assembler, gas/binutils 2.11 or newer, -or a recent -snapshot of gas. +
Support for HP-UX version 9 and older was discontinued in GCC 3.4. -
More specific information to hppa*-hp-hpux* targets follows.
+
We require using gas/binutils on all hppa platforms. Version 2.19 or +later is recommended. -
It may be helpful to configure GCC with the +--with-gnu-as and +--with-as=... options to ensure that GCC can find GAS. -
The HP assembler should not be used with GCC. It is rarely tested and may +not work. It shouldn't be used with any languages other than C due to its +many limitations. -
The HP assembler has major problems on this platform. We've tried to work -around the worst of the problems. However, those workarounds may be causing -linker crashes in some circumstances; the workarounds also probably prevent -shared libraries from working. Use the GNU assembler to avoid these problems. +
Specifically, -g does not work (HP-UX uses a peculiar debugging +format which GCC does not know about). It also inserts timestamps +into each object file it creates, causing the 3-stage comparison test to +fail during a bootstrap. You should be able to continue by saying +‘make all-host all-target’ after getting the failure from ‘make’. -
The configuration scripts for GCC will also trigger a bug in the hpux9
-shell. To avoid this problem set CONFIG_SHELL to /bin/ksh
-and SHELL to /bin/ksh in your environment.
+
Various GCC features are not supported. For example, it does not support weak +symbols or alias definitions. As a result, explicit template instantiations +are required when using C++. This makes it difficult if not impossible to +build many C++ applications. -
There are two default scheduling models for instructions. These are +PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc +architecture specified for the target machine when configuring. +PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when +the target is a ‘hppa1*’ machine. -
For hpux10.20, we highly recommend you pick up the latest sed patch
-PHCO_19798 from HP. HP has two sites which provide patches free of
-charge:
-
-
The PROCESSOR_8000 model is not well suited to older processors. Thus, +it is important to completely specify the machine architecture when +configuring if you want a model other than PROCESSOR_8000. The macro +TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different +default scheduling model is desired. -
The HP assembler on these systems is much better than the hpux9 assembler,
-but still has some problems. Most notably the assembler inserts timestamps
-into each object file it creates, causing the 3-stage comparison test to fail
-during a make bootstrap. You should be able to continue by
-saying make all after getting the failure from make
-bootstrap.
+
As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10 +through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later. +This namespace change might cause problems when bootstrapping with +an earlier version of GCC or the HP compiler as essentially the same +namespace is required for an entire build. This problem can be avoided +in a number of ways. With HP cc, UNIX_STD can be set to ‘95’ +or ‘98’. Another way is to add an appropriate set of predefines +to CC. The description for the munix= option contains +a list of the predefines used with each standard. -
More specific information to ‘hppa*-hp-hpux*’ targets follows. -
GCC 3.0 and up support HP-UX 11. On 64-bit capable systems, there
-are two distinct ports. The hppa2.0w-hp-hpux11* port generates
-code for the 32-bit pa-risc runtime architecture. It uses the HP
-linker and is currently the default selected by config.guess. The
-optional hppa64-hp-hpux11* port generates 64-bit code for the
-pa-risc 2.0 architecture. It must be explicitly selected using the
---host=hppa64-hp-hpux11* configure option. Different prefixes
-must be used if both ports are to be installed on the same system.
+
You must use GNU binutils 2.11 or above with the 32-bit port. Thread
-support is not currently implemented, so --enable-threads does
-not work. See:
+
For hpux10.20, we highly recommend you pick up the latest sed patch
+PHCO_19798 from HP. HP has two sites which provide patches free of
+charge:
GCC 2.95.x is not supported under HP-UX 11 and cannot be used to -compile GCC 3.0 and up. Refer to binaries for -information about obtaining precompiled GCC binaries for HP-UX. - -
GNU binutils 2.13 or later is recommended with the 64-bit port. -The HP assembler is not supported. It is highly recommended -that the GNU linker be used as well. Either binutils must be built -prior to gcc, or a binary distribution of gcc or binutils must be -obtained for the initial builds. When starting with a HP compiler, -it is preferable to use the ANSI compiler as the bundled compiler -only supports traditional C. Bootstrapping with the bundled compiler -is tested infrequently and problems often arise because of the subtle -differences in semantics between traditional and ISO C. There also -have been problems reported with various binary distributions. This -port still is undergoing significant development. - -
This port is very preliminary and has many known bugs. We hope to -have a higher-quality port for this machine soon. - -
If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install
-out-of-the-box. You'll get compile errors while building libstdc++.
-The patch glibc-2.2.patch, that is to be
-applied in the GCC source tree, fixes the compatibility problems.
-
-
- -
Currently Glibc 2.2.3 (and older releases) and GCC 3.0 are out of sync -since the latest exception handling changes for GCC. Compiling glibc -with GCC 3.0 will give a binary incompatible glibc and therefore cause -lots of problems and might make your system completly unusable. This -will definitly need fixes in glibc but might also need fixes in GCC. We -strongly advise to wait for glibc 2.2.4 and to read the release notes of -glibc 2.2.4 whether patches for GCC 3.0 are needed. You can use glibc -2.2.3 with GCC 3.0, just do not try to recompile it. - -
Use this configuration to generate a.out binaries on Linux-based
-GNU systems if you do not have gas/binutils version 2.5.2 or later
-installed.
-
-
This configuration is obsoleted in GCC 3.1. - -
Use this configuration to generate a.out binaries on Linux-based
-GNU systems. This configuration is being superseded. You must use
-gas/binutils version 2.5.2 or later.
-
-
You will need binutils 2.9.1.0.15 or newer for exception handling to work. +
The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are +used for one-only code and data. This resolves many of the previous +problems in using C++ on this target. However, the ABI is not compatible +with the one implemented under HP-UX 11 using secondary definitions. + +
GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot +be used to compile GCC 3.0 and up. + +
The libffi and libjava libraries haven't been ported to 64-bit HP-UX and don't build. + +
Refer to binaries for information about obtaining +precompiled GCC binaries for HP-UX. Precompiled binaries must be obtained +to build the Ada language as it can't be bootstrapped using C. Ada is +only available for the 32-bit PA-RISC runtime. + +
Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The +bundled compiler supports only traditional C; you will need either HP's +unbundled compiler, or a binary distribution of GCC. + +
It is possible to build GCC 3.3 starting with the bundled HP compiler, +but the process requires several steps. GCC 3.3 can then be used to +build later versions. The fastjar program contains ISO C code and +can't be built with the HP bundled compiler. This problem can be +avoided by not building the Java language. For example, use the +--enable-languages="c,c++,f77,objc" option in your configure +command. + +
There are several possible approaches to building the distribution. +Binutils can be built first using the HP tools. Then, the GCC +distribution can be built. The second approach is to build GCC +first using the HP tools, then build binutils, then rebuild GCC. +There have been problems with various binary distributions, so it +is best not to start from a binary distribution. + +
On 64-bit capable systems, there are two distinct targets. Different +installation prefixes must be used if both are to be installed on +the same system. The ‘hppa[1-2]*-hp-hpux11*’ target generates code +for the 32-bit PA-RISC runtime architecture and uses the HP linker. +The ‘hppa64-hp-hpux11*’ target generates 64-bit code for the +PA-RISC 2.0 architecture. + +
The script config.guess now selects the target type based on the compiler +detected during configuration. You must define PATH or CC so +that configure finds an appropriate compiler for the initial bootstrap. +When CC is used, the definition should contain the options that are +needed whenever CC is used. + +
Specifically, options that determine the runtime architecture must be +in CC to correctly select the target for the build. It is also +convenient to place many other compiler options in CC. For example, +CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE" +can be used to bootstrap the GCC 3.3 branch with the HP compiler in +64-bit K&R/bundled mode. The +DA2.0W option will result in +the automatic selection of the ‘hppa64-hp-hpux11*’ target. The +macro definition table of cpp needs to be increased for a successful +build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to +be defined when building with the bundled compiler, or when using the +-Ac option. These defines aren't necessary with -Ae. + +
It is best to explicitly configure the ‘hppa64-hp-hpux11*’ target +with the --with-ld=... option. This overrides the standard +search for ld. The two linkers supported on this target require different +commands. The default linker is determined during configuration. As a +result, it's not possible to switch linkers in the middle of a GCC build. +This has been reported to sometimes occur in unified builds of binutils +and GCC. + +
A recent linker patch must be installed for the correct operation of
+GCC 3.3 and later. PHSS_26559 and PHSS_24304 are the
+oldest linker patches that are known to work. They are for HP-UX
+11.00 and 11.11, respectively. PHSS_24303, the companion to
+PHSS_24304, might be usable but it hasn't been tested. These
+patches have been superseded. Consult the HP patch database to obtain
+the currently recommended linker patch for your system.
+
+
The patches are necessary for the support of weak symbols on the +32-bit port, and for the running of initializers and finalizers. Weak +symbols are implemented using SOM secondary definition symbols. Prior +to HP-UX 11, there are bugs in the linker support for secondary symbols. +The patches correct a problem of linker core dumps creating shared +libraries containing secondary symbols, as well as various other +linking issues involving secondary symbols. + +
GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to +run initializers and finalizers on the 64-bit port. The 32-bit port +uses the linker +init and +fini options for the same +purpose. The patches correct various problems with the +init/+fini +options, including program core dumps. Binutils 2.14 corrects a +problem on the 64-bit port resulting from HP's non-standard use of +the .init and .fini sections for array initializers and finalizers. + +
Although the HP and GNU linkers are both supported for the +‘hppa64-hp-hpux11*’ target, it is strongly recommended that the +HP linker be used for link editing on this target. + +
At this time, the GNU linker does not support the creation of long +branch stubs. As a result, it can't successfully link binaries +containing branch offsets larger than 8 megabytes. In addition, +there are problems linking shared libraries, linking executables +with -static, and with dwarf2 unwind and exception support. +It also doesn't provide stubs for internal calls to global functions +in shared libraries, so these calls can't be overloaded. + +
The HP dynamic loader does not support GNU symbol versioning, so symbol +versioning is not supported. It may be necessary to disable symbol +versioning with --disable-symvers when using GNU ld. + +
POSIX threads are the default. The optional DCE thread library is not +supported, so --enable-threads=dce does not work. + +
Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present +in glibc 2.2.5 and later. More information is available in the +libstdc++-v3 documentation. + +
As of GCC 3.3, binutils 2.13.1 or later is required for this platform. +See bug 10877 for more information.
If you receive Signal 11 errors when building on GNU/Linux, then it is possible you have a hardware problem. Further information on this can be found on www.bitwizard.nl. -
Compilation with RCC is recommended. Also, it may be a good idea to -link with GNU malloc instead of the malloc that comes with the system. - -
Use this configuration for SCO release 3.2 version 4. - -
Use this for the SCO OpenServer Release 5 family of operating systems. - -
Unlike earlier versions of GCC, the ability to generate COFF with this -target is no longer provided. - -
Earlier versions of GCC emitted DWARF 1 when generating ELF to allow -the system debugger to be used. That support was too burdensome to -maintain. GCC now emits only DWARF 2 for this target. This means you -may use either the UDK debugger or GDB to debug programs built by this -version of GCC. +
Use of the -march=pentiumpro flag can result in
-unrecognized opcodes when using the native assembler on OS versions before
-5.0.6. (Support for P6 opcodes was added to the native ELF assembler in
-that version.) While it's rather rare to see these emitted by GCC yet,
-errors of the basic form:
+
/usr/tmp/ccaNlqBc.s:22:unknown instruction: fcomip - /usr/tmp/ccaNlqBc.s:50:unknown instruction: fucomip -+
Use this for Solaris 10 or later on x86 and x86-64 systems. This +configuration is supported by GCC 4.0 and later versions only. -
are symptoms of this problem. You may work around this by not -building affected files with that flag, by using the GNU assembler, or -by using the assembler provided with the current version of the OS. -Users of GNU assembler should see the note below for hazards on doing -so. +
It is recommended that you configure GCC to use the GNU assembler in +/usr/sfw/bin/gas but the Sun linker, using the options +--with-gnu-as --with-as=/usr/sfw/bin/gas --without-gnu-ld +--with-ld=/usr/ccs/bin/ld. -
The native SCO assembler that is provided with the OS at no
-charge is normally required. If, however, you must be able to use
-the GNU assembler (perhaps you're compiling code with asms that
-require GAS syntax) you may configure this package using the flags
---with-gnu-as. You must
-use a recent version of GNU binutils; versions past 2.9.1 seem to work
-well.
+
In general, the --with-gnu-as option isn't as well tested
-as the native assembler.
+
Look in gcc/config/i386/sco5.h (search for "messy") for
-additional OpenServer-specific flags.
-
-
Systems based on OpenServer before 5.0.4 (uname -X
-will tell you what you're running) require TLS597 from
-ftp://ftp.sco.com/TLS/
-for C++ constructors and destructors to work right.
-
-
The system linker in (at least) 5.0.4 and 5.0.5 will sometimes
-do the wrong thing for a construct that GCC will emit for PIC
-code. This can be seen as execution testsuite failures when using
--fPIC on 921215-1.c, 931002-1.c, nestfunc-1.c, and gcov-1.c.
-For 5.0.5, an updated linker that will cure this problem is
-available. You must install both
-ftp://ftp.sco.com/Supplements/rs505a/
-and OSS499A.
-
-
The dynamic linker in OpenServer 5.0.5 (earlier versions may show
-the same problem) aborts on certain G77-compiled programs. It's particularly
-likely to be triggered by building Fortran code with the -fPIC flag.
-Although it's conceivable that the error could be triggered by other
-code, only G77-compiled code has been observed to cause this abort.
-If you are getting core dumps immediately upon execution of your
-G77 program--and especially if it's compiled with -fPIC--try applying
-sco_osr5_g77.patch to your libf2c and
-rebuilding GCC.
-Affected faults, when analyzed in a debugger, will show a stack
-backtrace with a fault occurring in rtld() and the program
-running as /usr/lib/ld.so.1. This problem has been reported to SCO
-engineering and will hopefully be addressed in later releases.
-
-
This target emulates the SCO Universal Development Kit and requires that
-package be installed. (If it is installed, you will have a
-/udk/usr/ccs/bin/cc file present.) It's very much like the
-i?86-*-unixware7* target
-but is meant to be used when hosting on a system where UDK isn't the
-default compiler such as OpenServer 5 or Unixware 2. This target will
-generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
-with the same warnings and caveats as the SCO UDK.
-
-
This target is a little tricky to build because we have to distinguish -it from the native tools (so it gets headers, startups, and libraries -from the right place) while making the tools not think we're actually -building a cross compiler. The easiest way to do this is with a configure -command like this: - -
CC=/udk/usr/ccs/bin/cc /your/path/to/gcc/configure \ - --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk- -- -
You should substitute i686 in the above command with the appropriate
-processor for your host.
-
-
After the usual make bootstrap and
-make install, you can then access the UDK-targeted GCC
-tools by adding udk- before the commonly known name. For
-example, to invoke the C compiler, you would use udk-gcc.
-They will coexist peacefully with any native-target GCC tools you may
-have installed.
-
-
This configuration is obsoleted in GCC 3.1. - -
It may be a good idea to link with GNU malloc instead of the malloc that -comes with the system. - -
In ISC version 4.1, sed core dumps when building
-deduced.h. Use the version of sed from version 4.0.
-
-
This configuration is obsoleted in GCC 3.1. - -
You need to use GAS version 2.1 or later, and LD from -GNU binutils version 2.2 or later. - -
This configuration is obsoleted in GCC 3.1. - -
Go to the Berkeley universe before compiling. - -
This configuration is obsoleted in GCC 3.1. - -
You must install GNU sed before running configure.
-
-
The fixproto shell script may trigger a bug in the system shell.
-If you encounter this problem, upgrade your operating system or
-use bash (the GNU shell) to run fixproto.
-
-
All support for the i860 processor is obsoleted in GCC 3.1. - -
On the Intel Paragon (an i860 machine), if you are using operating
-system version 1.0, you will get warnings or errors about redefinition
-of va_arg when you build GCC.
-
-
If this happens, then you need to link most programs with the library
-iclib.a. You must also modify stdio.h as follows: before
-the lines
-
-
#if defined(__i860__) && !defined(_VA_LIST) - #include <va_list.h> -- -
insert the line - -
#if __PGC__ -- -
and after the lines - -
extern int vprintf(const char *, va_list ); - extern int vsprintf(char *, const char *, va_list ); - #endif -- -
insert the line - -
#endif /* __PGC__ */ -- -
These problems don't exist in operating system version 1.1. - -
IA-64 processor (also known as IPF, or Itanium Processor Family) +
IA-64 processor (also known as IPF, or Itanium Processor Family) running GNU/Linux. -
The toolchain is not completely finished, so requirements will continue -to change. -GCC 3.0.1 and later require glibc 2.2.4. -GCC 3.0.2 requires binutils from 2001-09-05 or later. -GCC 3.0.1 requires binutils 2.11.1 or later. +
If you are using the installed system libunwind library with +--with-system-libunwind, then you must use libunwind 0.98 or +later.
None of the following versions of GCC has an ABI that is compatible with any of the other versions in this list, with the exception that Red Hat 2.96 and Trillian 000171 are compatible with each other: -3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717. +3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717. This primarily affects C++ programs and programs that create shared libraries. -Because of these ABI incompatibilities, GCC 3.0.2 is not recommended for -user programs on GNU/Linux systems built using earlier compiler releases. -GCC 3.0.2 is recommended for compiling linux, the kernel. -GCC 3.0.2 is believed to be fully ABI compliant, and hence no more major -ABI changes are expected. +GCC 3.1 or later is recommended for compiling linux, the kernel. +As of version 3.1 GCC is believed to be fully ABI compliant, and hence no +more major ABI changes are expected. -
LynxOS 2.2 and earlier comes with GCC 1.x already installed as
-/bin/gcc. You should compile with this instead of /bin/cc.
-You can tell GCC to use the GNU assembler and linker, by specifying
---with-gnu-as --with-gnu-ld when configuring. These will produce
-COFF format object files and executables; otherwise GCC will use the
-installed tools, which produce a.out format executables.
+
Building GCC on this target requires the GNU Assembler. The bundled HP +assembler will not work. To prevent GCC from using the wrong assembler, +the option --with-gnu-as may be necessary. -
The GCC libunwind library has not been ported to HPUX. This means that for +GCC versions 3.2.3 and earlier, --enable-libunwind-exceptions +is required to build GCC. For GCC 3.3 and later, this is the default. +For gcc 3.4.3 and later, --enable-libunwind-exceptions is +removed and the system libunwind library will always be used. -
AIX Make frequently has problems with GCC makefiles. GNU Make 3.76 or -newer is recommended to build on this platform. +
Support for AIX version 3 and older was discontinued in GCC 3.4. + +
“out of memory” bootstrap failures may indicate a problem with +process resource limits (ulimit). Hard limits are configured in the +/etc/security/limits system configuration file. + +
To speed up the configuration phases of bootstrapping and installing GCC, +one may use GNU Bash instead of AIX /bin/sh, e.g., + +
% CONFIG_SHELL=/opt/freeware/bin/bash + % export CONFIG_SHELL ++
and then proceed as described in the build instructions, where we strongly recommend specifying an absolute path +to invoke srcdir/configure. + +
Because GCC on AIX is built as a 32-bit executable by default, +(although it can generate 64-bit programs) the GMP and MPFR libraries +required by gfortran must be 32-bit libraries. Building GMP and MPFR +as static archive libraries works better than shared libraries.
Errors involving alloca when building GCC generally are due
to an incorrect definition of CC in the Makefile or mixing files
compiled with the native C compiler and GCC. During the stage1 phase of
-the build, the native AIX compiler must be invoked as cc
-(not xlc). Once configure has been informed of
-xlc, one needs to use make distclean to remove the
-configure cache files and ensure that CC environment variable
-does not provide a definition that will confuse configure.
+the build, the native AIX compiler must be invoked as cc
+(not xlc). Once configure has been informed of
+xlc, one needs to use ‘make distclean’ to remove the
+configure cache files and ensure that CC environment variable
+does not provide a definition that will confuse configure.
If this error occurs during stage2 or later, then the problem most likely
is the version of Make (see above).
-
The GNU Assembler incorrectly reports that it supports WEAK symbols on
-AIX which causes GCC to try to utilize weak symbol functionality which
-is not really supported on the platform. The native as and
-ld still are recommended. The native AIX tools do
-interoperate with GCC.
-
-
Building libstdc++.a requires a fix for a AIX Assembler bug
-APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1).
-
-
libstdc++ in GCC 3.2 increments the major version number of the
-shared object and GCC installation places the libstdc++.a
-shared library in a common location which will overwrite the GCC 3.1
-version of the shared library. Applications either need to be
-re-linked against the new shared library or the GCC 3.1 version of the
-libstdc++ shared object needs to be available to the AIX
-runtime loader. The GCC 3.1 libstdc++.so.4 shared object can
-be installed for runtime dynamic loading using the following steps to
-set the F_LOADONLY flag in the shared object for each
-multilib libstdc++.a installed:
-
-
Extract the shared object from each the GCC 3.1 libstdc++.a
-archive:
-
% ar -x libstdc++.a libstdc++.so.4 -- -
Enable the F_LOADONLY flag so that the shared object will be
+
The native as and ld are recommended for bootstrapping +on AIX 4 and required for bootstrapping on AIX 5L. The GNU Assembler +reports that it supports WEAK symbols on AIX 4, which causes GCC to try to +utilize weak symbol functionality although it is not supported. The GNU +Assembler and Linker do not support AIX 5L sufficiently to bootstrap GCC. +The native AIX tools do interoperate with GCC. + +
Building libstdc++.a requires a fix for an AIX Assembler bug +APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a +fix for another AIX Assembler bug and a co-dependent AIX Archiver fix +referenced as APAR IY53606 (AIX 5.2) or a APAR IY54774 (AIX 5.1) + +
‘libstdc++’ in GCC 3.4 increments the major version number of the +shared object and GCC installation places the libstdc++.a +shared library in a common location which will overwrite the and GCC +3.3 version of the shared library. Applications either need to be +re-linked against the new shared library or the GCC 3.1 and GCC 3.3 +versions of the ‘libstdc++’ shared object needs to be available +to the AIX runtime loader. The GCC 3.1 ‘libstdc++.so.4’, if +present, and GCC 3.3 ‘libstdc++.so.5’ shared objects can be +installed for runtime dynamic loading using the following steps to set +the ‘F_LOADONLY’ flag in the shared object for each +multilib libstdc++.a installed: + +
Extract the shared objects from the currently installed +libstdc++.a archive: +
% ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5 ++
Enable the ‘F_LOADONLY’ flag so that the shared object will be available for runtime dynamic loading, but not linking: -
% strip -e libstdc++.so.4 -- -
Archive the runtime-only shared object in the GCC 3.2
-libstdc++.a archive:
-
% ar -q libstdc++.a libstdc++.so.4 -- +
% strip -e libstdc++.so.4 libstdc++.so.5 ++
Archive the runtime-only shared object in the GCC 3.4 +libstdc++.a archive: +
% ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5 +
Linking executables and shared libraries may produce warnings of duplicate symbols. The assembly files generated by GCC for AIX always have included multiple symbol definitions for certain global variable @@ -956,18 +706,18 @@ and function declarations in the original program. The warnings should not prevent the linker from producing a correct library or runnable executable. -
AIX 4.3 utilizes a "large format" archive to support both 32-bit and +
AIX 4.3 utilizes a “large format” archive to support both 32-bit and
64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
to parse archive libraries did not handle the new format correctly.
These routines are used by GCC and result in error messages during
-linking such as "not a COFF file". The version of the routines shipped
-with AIX 4.3.1 should work for a 32-bit environment. The -g
+linking such as “not a COFF file”. The version of the routines shipped
+with AIX 4.3.1 should work for a 32-bit environment. The -g
option of the archive command may be used to create archives of 32-bit
-objects using the original "small format". A correct version of the
+objects using the original “small format”. A correct version of the
routines is shipped with AIX 4.3.2 and above.
Some versions of the AIX binder (linker) can fail with a relocation
-overflow severe error when the -bbigtoc option is used to link
+overflow severe error when the -bbigtoc option is used to link
GCC-produced object files into an executable that overflows the TOC. A fix
for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
available from IBM Customer Support and from its
@@ -988,330 +738,96 @@ website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
AIX provides National Language Support (NLS). Compilers and assemblers
use NLS to support locale-specific representations of various data
-formats including floating-point numbers (e.g., . vs , for
+formats including floating-point numbers (e.g., ‘.’ vs ‘,’ for
separating decimal fractions). There have been problems reported where
GCC does not produce the same floating-point formats that the assembler
-expects. If one encounters this problem, set the LANG
-environment variable to C or En_US.
+expects. If one encounters this problem, set the LANG
+environment variable to ‘C’ or ‘En_US’.
By default, GCC for AIX 4.1 and above produces code that can be used on both Power or PowerPC processors. -
A default can be specified with the -mcpu=cpu_type
-switch and using the configure option --with-cpu-cpu_type.
-
-
Mitsubishi M32R processor. -This configuration is intended for embedded systems. - -
HP 9000 series 200 running BSD. Note that the C compiler that comes -with this system cannot compile GCC; contact law@cygnus.com -to get binaries of GCC for bootstrapping. +
A default can be specified with the -mcpu=cpu_type +switch and using the configure option --with-cpu-cpu_type. -
Motorola 68HC11 family micro controllers. These are used in embedded +
Vitesse IQ2000 processors. These are used in embedded applications. There are no standard Unix configurations. -
Motorola 68HC12 family micro controllers. These are used in embedded -applications. There are no standard Unix configurations. - -
Altos 3068. This configuration is obsoleted in GCC 3.1. - -
You must use the GNU assembler, linker and debugger. -Also, you must fix a kernel bug. - -
Apple Macintosh running A/UX. -This configuration is obsoleted in GCC 3.1. - -
You may configure GCC to use either the system assembler and
-linker or the GNU assembler and linker. You should use the GNU configuration
-if you can, especially if you also want to use G++. You enable
-that configuration with the --with-gnu-as and --with-gnu-ld
-options to configure.
-
-
Note the C compiler that comes
-with this system cannot compile GCC. You can find binaries of GCC
-for bootstrapping on jagubox.gsfc.nasa.gov.
-You will also a patched version of /bin/ld there that
-raises some of the arbitrary limits found in the original.
-
-
AT&T 3b1, a.k.a. 7300 PC. This version of GCC cannot -be compiled with the system C compiler, which is too buggy. -You will need to get a previous version of GCC and use it to -bootstrap. Binaries are available from the OSU-CIS archive, at -ftp://archive.cis.ohio-state.edu/pub/att7300/. - -
Bull DPX/2 series 200 and 300 with BOS-2.00.45 up to BOS-2.01. -This configuration is obsoleted in GCC 3.1. - -
GCC works
-either with native assembler or GNU assembler. You can use
-GNU assembler with native COFF generation by providing --with-gnu-as to
-the configure script or use GNU assembler with stabs-in-COFF encapsulation
-by providing --with-gnu-as --stabs. For any problem with the native
-assembler or for availability of the DPX/2 port of GAS, contact
-F.Pierresteguy@frcl.bull.fr.
-
-
Use configure unos for building on Unos.
-
-
The Unos assembler is named casm instead of as. For some
-strange reason linking /bin/as to /bin/casm changes the
-behavior, and does not work. So, when installing GCC, you should
-install the following script as as in the subdirectory where
-the passes of GCC are installed:
-
-
#!/bin/sh - casm $* -- -
The default Unos library is named libunos.a instead of
-libc.a. To allow GCC to function, either change all
-references to -lc in gcc.c to -lunos or link
-/lib/libc.a to /lib/libunos.a.
-
-
When compiling GCC with the standard compiler, to overcome bugs in
-the support of alloca, do not use -O when making stage 2.
-Then use the stage 2 compiler with -O to make the stage 3
-compiler. This compiler will have the same characteristics as the usual
-stage 2 compiler on other systems. Use it to make a stage 4 compiler
-and compare that with stage 3 to verify proper compilation.
-
-
(Perhaps simply defining ALLOCA in x-crds as described in
-the comments there will make the above paragraph superfluous. Please
-inform us of whether this works.)
-
-
Unos uses memory segmentation instead of demand paging, so you will need
-a lot of memory. 5 Mb is barely enough if no other tasks are running.
-If linking cc1 fails, try putting the object files into a library
-and linking from that library.
-
-
HP 9000 series 300 or 400 running HP-UX. HP-UX version 8.0 has a bug in
-the assembler that prevents compilation of GCC. This
-bug manifests itself during the first stage of compilation, while
-building libgcc2.a:
+
_floatdisf - cc1: warning: `-g' option not supported on this version of GCC - cc1: warning: `-g1' option not supported on this version of GCC - ./xgcc: Internal compiler error: program as got fatal signal 11 -- -
A patched version of the assembler is available as the file -ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler. If you -have HP software support, the patch can also be obtained directly from -HP, as described in the following note: - -
-This is the patched assembler, to patch SR#1653-010439, where the -assembler aborts on floating point constants. - -- -The bug is not really in the assembler, but in the shared library -version of the function "cvtnum(3c)". The bug on "cvtnum(3c)" is -SR#4701-078451. Anyway, the attached assembler uses the archive -library version of "cvtnum(3c)" and thus does not exhibit the bug. -
This patch is also known as PHCO_4484. - -
In addition, if you wish to use gas, you must use -gas version 2.1 or later, and you must use the GNU linker version 2.1 or -later. Earlier versions of gas relied upon a program which converted the -gas output into the native HP-UX format, but that program has not been -kept up to date. gdb does not understand that native HP-UX format, so -you must use gas if you wish to use gdb. - -
On HP-UX version 8.05, but not on 8.07 or more recent versions, the
-fixproto shell script triggers a bug in the system shell. If you
-encounter this problem, upgrade your operating system or use BASH (the
-GNU shell) to run fixproto. This bug will cause the fixproto
-program to report an error of the form:
-
-
./fixproto: sh internal 1K buffer overflow -- -
To fix this, you can also change the first line of the fixproto script -to look like: - -
#!/bin/ksh -- -
These configurations are obsoleted in GCC 3.1. - -
Current GCC versions probably do not work on version 2 of the NeXT -operating system. - -
On NeXTStep 3.0, the Objective-C compiler does not work, due, -apparently, to a kernel bug that it happens to trigger. This problem -does not happen on 3.1. - -
You absolutely must use GNU sed and GNU make on this platform. - -
On NeXTSTEP 3.x where x < 3 the build of GCC will abort during -stage1 with an error message like this: - -
_eh - /usr/tmp/ccbbsZ0U.s:987:Unknown pseudo-op: .section - /usr/tmp/ccbbsZ0U.s:987:Rest of line ignored. 1st junk character - valued 95 (_). -- -
The reason for this is the fact that NeXT's assembler for these
-versions of the operating system does not support the .section
-pseudo op that's needed for full C++ exception functionality.
-
-
As NeXT's assembler is a derived work from GNU as, a free -replacement that does can be obtained at -ftp://ftp.next.peak.org:/next-ftp/next/apps/devtools/as.3.3.NIHS.s.tar.gz. - -
If you try to build the integrated C++ & C++ runtime libraries on this system -you will run into trouble with include files. The way to get around this is -to use the following sequence. Note you must have write permission to -the directory prefix you specified in the configuration process of GCC -for this sequence to work. - -
cd bld-gcc - make all-texinfo all-bison all-byacc all-binutils all-gas all-ld - cd gcc - make bootstrap - make install-headers-tar - cd .. - make bootstrap3 -- -
On the Tower models 4n0 and 6n0, by default a process is not
-allowed to have more than one megabyte of memory. GCC cannot compile
-itself (or many other programs) with -O in that much memory.
-
-
To solve this problem, reconfigure the kernel adding the following line -to the configuration file: - -
MAXUMEM = 4096 -- -
Sun 3. We do not provide a configuration file to use the Sun FPA by -default, because programs that establish signal handlers for floating -point traps inherently cannot work with the FPA. - -
Renesas M32C processor. +This configuration is intended for embedded systems. -
It is reported that you may need the GNU assembler on this platform. +
Renesas M32R processor. +This configuration is intended for embedded systems. -
Motorola m88k running the AT&T/Unisoft/Motorola V.3 reference port. -These configurations are obsoleted in GCC 3.1. +
These systems tend to use the Green Hills C, revision 1.8.5, as the -standard C compiler. There are apparently bugs in this compiler that -result in object files differences between stage 2 and stage 3. If this -happens, make the stage 4 compiler and compare it to the stage 3 -compiler. If the stage 3 and stage 4 object files are identical, this -suggests you encountered a problem with the standard C compiler; the -stage 3 and 4 compilers may be usable. +
Motorola 68HC11 family micro controllers. These are used in embedded +applications. There are no standard Unix configurations. -
It is best, however, to use an older version of GCC for bootstrapping -if you have one. +
Motorola 68HC12 family micro controllers. These are used in embedded +applications. There are no standard Unix configurations. -
Motorola m88k running DG/UX. -These configurations are obsoleted in GCC 3.1. +
To build 88open BCS native or cross
-compilers on DG/UX, specify the configuration name as
-m88k-*-dguxbcs and build in the 88open BCS software development
-environment. To build ELF native or cross compilers on DG/UX, specify
-m88k-*-dgux and build in the DG/UX ELF development environment.
-You set the software development environment by issuing
-sde-target command and specifying either m88kbcs or
-m88kdguxelf as the operand.
+
If you do not specify a configuration name, configure guesses the
-configuration based on the current software development environment.
+
By default, ‘m68k-*-aout’, ‘m68k-*-coff*’, +‘m68k-*-elf*’, ‘m68k-*-rtems’, ‘m68k-*-uclinux’ and +‘m68k-*-linux’ +build libraries for both M680x0 and ColdFire processors. If you only +need the M680x0 libraries, you can omit the ColdFire ones by passing +--with-arch=m68k to configure. Alternatively, you +can omit the M680x0 libraries by passing --with-arch=cf to +configure. These targets default to 5206 or 5475 code as +appropriate for the target system when +configured with --with-arch=cf and 68020 code otherwise. -
The ‘m68k-*-netbsd’ and +‘m68k-*-openbsd’ targets also support the --with-arch +option. They will generate ColdFire CFV4e code when configured with +--with-arch=cf and 68020 code otherwise. -
You can override the default processors listed above by configuring +with --with-cpu=target. This target can either +be a -mcpu argument or one of the following values: +‘m68000’, ‘m68010’, ‘m68020’, ‘m68030’, +‘m68040’, ‘m68060’, ‘m68020-40’ and ‘m68020-60’. -
Tektronix XD88 running UTekV 3.2e. -These configurations are obsoleted in GCC 3.1. +
Do not turn on -optimization while building stage1 if you bootstrap with -the buggy Green Hills compiler. Also, the bundled LAI -System V NFS is buggy so if you build in an NFS mounted -directory, start from a fresh reboot, or avoid NFS all together. -Otherwise you may have trouble getting clean comparisons -between stages. +
GCC 4.3 changed the uClinux configuration so that it uses the +‘m68k-linux-gnu’ ABI rather than the ‘m68k-elf’ ABI. +It also added improved support for C++ and flat shared libraries, +both of which were ABI changes. However, you can still use the +original ABI by configuring for ‘m68k-uclinuxoldabi’ or +‘m68k-vendor-uclinuxoldabi’. -
If you use the 1.31 version of the MIPS assembler (such as was shipped
-with Ultrix 3.1), you will need to use the -fno-delayed-branch switch
-when optimizing floating point code. Otherwise, the assembler will
-complain when the GCC compiler fills a branch delay slot with a
-floating point instruction, such as add.d.
+
If on a MIPS system you get an error message saying "does not have gp -sections for all it's [sic] sectons [sic]", don't worry about it. This +
If on a MIPS system you get an error message saying “does not have gp +sections for all it's [sic] sectons [sic]”, don't worry about it. This happens whenever you use GAS with the MIPS linker, but there is not really anything wrong, and it is okay to use the output file. You can stop such warnings by installing the GNU linker. @@ -1319,546 +835,399 @@ stop such warnings by installing the GNU linker.
It would be nice to extend GAS to produce the gp tables, but they are optional, and there should not be a warning about their absence. -
Users have reported some problems with version 2.0 of the MIPS -compiler tools that were shipped with Ultrix 4.1. Version 2.10 -which came with Ultrix 4.2 seems to work fine. - -
Users have also reported some problems with version 2.20 of the -MIPS compiler tools that were shipped with RISC/os 4.x. The earlier -version 2.11 seems to work fine. - -
Some versions of the MIPS linker will issue an assertion failure
-when linking code that uses alloca against shared
-libraries on RISC-OS 5.0, and DEC's OSF/1 systems. This is a bug
-in the linker, that is supposed to be fixed in future revisions.
-To protect against this, GCC passes -non_shared to the
-linker unless you pass an explicit -shared or
--call_shared switch.
-
-
MIPS machines running the MIPS operating system in BSD mode. -These configurations are obsoleted in GCC 3.1. - -
It's possible that some old versions of the system lack the functions
-memcpy, memmove, memcmp, and memset. If your
-system lacks these, you must remove or undo the definition of
-TARGET_MEM_FUNCTIONS in mips-bsd.h.
-
-
If you use the MIPS C compiler to bootstrap, it may be necessary
-to increase its table size for switch statements with the
--Wf,-XNg1500 option. If you use the -O2
-optimization option, you also need to use -Olimit 3000.
-Both of these options are automatically generated in the
-Makefile that the shell script configure builds.
-If you override the CC make variable and use the MIPS
-compilers, you may need to add -Wf,-XNg1500 -Olimit 3000.
-
-
These configurations are obsoleted in GCC 3.1. - -
MIPS-based DECstations can support three different personalities:
-Ultrix, DEC OSF/1, and OSF/rose. (Alpha-based DECstation products have
-a configuration name beginning with alpha*-dec.) To configure GCC
-for these platforms use the following configurations:
-
-
mips-dec-ultrix
- mips-dec-osf1
- mips-dec-osfrose
- If you use the MIPS C compiler to bootstrap, it may be necessary
-to increase its table size for switch statements with the
--Wf,-XNg1500 option. If you use the -O2
-optimization option, you also need to use -Olimit 3000.
-Both of these options are automatically generated in the
-Makefile that the shell script configure builds.
-If you override the CC make variable and use the MIPS
-compilers, you may need to add -Wf,-XNg1500 -Olimit 3000.
-
-
These configurations are obsoleted in GCC 3.1. +
The libstdc++ atomic locking routines for MIPS targets requires MIPS II +and later. A patch went in just after the GCC 3.3 release to +make ‘mips*-*-*’ use the generic implementation instead. You can also +configure for ‘mipsel-elf’ as a workaround. The +‘mips*-*-linux*’ target continues to use the MIPS II routines. More +work on this is expected in future releases. + + + +
The built-in __sync_* functions are available on MIPS II and
+later systems and others that support the ‘ll’, ‘sc’ and
+‘sync’ instructions. This can be overridden by passing
+--with-llsc or --without-llsc when configuring GCC.
+Since the Linux kernel emulates these instructions if they are
+missing, the default for ‘mips*-*-linux*’ targets is
+--with-llsc. The --with-llsc and
+--without-llsc configure options may be overridden at compile
+time by passing the -mllsc or -mno-llsc options to
+the compiler.
+
+
MIPS systems check for division by zero (unless
+-mno-check-zero-division is passed to the compiler) by
+generating either a conditional trap or a break instruction. Using
+trap results in smaller code, but is only supported on MIPS II and
+later. Also, some versions of the Linux kernel have a bug that
+prevents trap from generating the proper signal (SIGFPE). To enable
+the use of break, use the --with-divide=breaks
+configure option when configuring GCC. The default is to
+use traps on systems that support them.
+
+
Cross-compilers for the MIPS as target using the MIPS assembler +currently do not work, because the auxiliary programs +mips-tdump.c and mips-tfile.c can't be compiled on +anything but a MIPS. It does work to cross compile for a MIPS +if you use the GNU assembler and linker. + +
The assembler from GNU binutils 2.17 and earlier has a bug in the way +it sorts relocations for REL targets (o32, o64, EABI). This can cause +bad code to be generated for simple C++ programs. Also the linker +from GNU binutils versions prior to 2.17 has a bug which causes the +runtime linker stubs in very large programs, like libgcj.so, to +be incorrectly generated. GNU Binutils 2.18 and later (and snapshots +made after Nov. 9, 2006) should be free from both of these problems. + +
In order to compile GCC on an SGI running IRIX 5, the ‘compiler_dev.hdr’ +subsystem must be installed from the IDO CD-ROM supplied by SGI. +It is also available for download from +ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist.
If you use the MIPS C compiler to bootstrap, it may be necessary
to increase its table size for switch statements with the
--Wf,-XNg1500 option. If you use the -O2
-optimization option, you also need to use -Olimit 3000.
-Both of these options are automatically generated in the
-Makefile that the shell script configure builds.
-If you override the CC make variable and use the MIPS
-compilers, you may need to add -Wf,-XNg1500 -Olimit 3000.
-
-
MIPS computers running RISC-OS can support four different -personalities: default, BSD 4.3, System V.3, and System V.4 -(older versions of RISC-OS don't support V.4). To configure GCC -for these platforms use the following configurations: - -
mips-mips-riscosrevmips-mips-riscosrevbsd
- mips-mips-riscosrevsysv4
- mips-mips-riscosrevsysv
- The revision rev mentioned above is the revision of
-RISC-OS to use. You must reconfigure GCC when going from a
-RISC-OS revision 4 to RISC-OS revision 5. This has the effect of
-avoiding a linker bug.
-
-
This configuration is obsoleted in GCC 3.1. +
To enable debugging under IRIX 5, you must use GNU binutils 2.15 or +later, and use the --with-gnu-ld configure option +when configuring GCC. You need to use GNU ar and nm, +also distributed with GNU binutils. -
In order to compile GCC on an SGI running IRIX 4, the "c.hdr.lib" -option must be installed from the CD-ROM supplied from Silicon Graphics. -This is found on the 2nd CD in release 4.0.1. +
Some users have reported that /bin/sh will hang during bootstrap. +This problem can be avoided by running the commands: -
On IRIX version 4.0.5F, and perhaps on some other versions as well,
-there is an assembler bug that reorders instructions incorrectly. To
-work around it, specify the target configuration
-mips-sgi-irix4loser. This configuration inhibits assembler
-optimization.
+
% CONFIG_SHELL=/bin/ksh + % export CONFIG_SHELL ++
before starting the build. -
In a compiler configured with target mips-sgi-irix4, you can turn
-off assembler optimization by using the -noasmopt option. This
-compiler option passes the option -O0 to the assembler, to
-inhibit reordering.
+
The -noasmopt option can be useful for testing whether a problem
-is due to erroneous assembler reordering. Even if a problem does not go
-away with -noasmopt, it may still be due to assembler
-reordering--perhaps GCC itself was miscompiled as a result.
+
You may get the following warning on IRIX 4 platforms, it can be safely -ignored. -
warning: foo.o does not have gp tables for all its sections. -- -
This configuration has considerable problems, which will be fixed in a -future release. - -
In order to compile GCC on an SGI running IRIX 5, the "compiler_dev.hdr" -subsystem must be installed from the IDO CD-ROM supplied by Silicon -Graphics. It is also available for download from -http://www.sgi.com/developers/devtools/apis/ido.html. - -
make compare may fail on version 5 of IRIX unless you add
--save-temps to CFLAGS. On these systems, the name of the
-assembler input file is stored in the object file, and that makes
-comparison fail if it differs between the stage1 and
-stage2 compilations. The option -save-temps forces a
-fixed name to be used for the assembler input file, instead of a
-randomly chosen name in /tmp. Do not add -save-temps
-unless the comparisons fail without that option. If you do you
--save-temps, you will have to manually delete the .i and
-.s files after each series of compilations.
-
-
If you use the MIPS C compiler to bootstrap, it may be necessary
-to increase its table size for switch statements with the
--Wf,-XNg1500 option. If you use the -O2
-optimization option, you also need to use -Olimit 3000.
-
-
To enable debugging under IRIX 5, you must use GNU as 2.11.2
-or later,
-and use the --with-gnu-as configure option when configuring GCC.
-GNU as is distributed as part of the binutils package.
-When using release 2.11.2, you need to apply a patch
-http://sources.redhat.com/ml/binutils/2001-07/msg00352.html
-which will be included in the next release of binutils.
-
-
When building GCC, the build process loops rebuilding cc1 over
-and over again. This happens on mips-sgi-irix5.2, and possibly
-other platforms. It has been reported that this is a known bug in the
-make shipped with IRIX 5.2. We recommend you use GNU
-make instead of the vendor supplied make program;
-however, you may have success with smake on IRIX 5.2 if you do
-not have GNU make available.
-
-
If you are using IRIX cc as your bootstrap compiler, you must
+
If you are using SGI's MIPSpro cc as your bootstrap compiler, you must
ensure that the N32 ABI is in use. To test this, compile a simple C
-file with cc and then run file on the
+file with cc and then run file on the
resulting object file. The output should look like:
-
test.o: ELF N32 MSB ... -- +
test.o: ELF N32 MSB ... +
If you see: -
test.o: ELF 32-bit MSB ... -- +
test.o: ELF 32-bit MSB ... +
or -
test.o: ELF 64-bit MSB ... -- -
then your version of cc uses the O32 or N64 ABI by default. You
-should set the environment variable CC to cc -n32
+
test.o: ELF 64-bit MSB ... ++
then your version of cc uses the O32 or N64 ABI by default. You +should set the environment variable CC to ‘cc -n32’ before configuring GCC. -
If you want the resulting gcc to run on old 32-bit systems
-with the MIPS R4400 CPU, you need to ensure that only code for the mips3
+
If you want the resulting gcc to run on old 32-bit systems
+with the MIPS R4400 CPU, you need to ensure that only code for the ‘mips3’
instruction set architecture (ISA) is generated. While GCC 3.x does
-this correctly, both GCC 2.95 and SGI's MIPSpro cc may change
+this correctly, both GCC 2.95 and SGI's MIPSpro cc may change
the ISA depending on the machine where GCC is built. Using one of them
-as the bootstrap compiler may result in mips4 code, which won't run at
-all on mips3-only systems. For the test program above, you should see:
-
-
test.o: ELF N32 MSB mips-3 ... -+as the bootstrap compiler may result in ‘mips4’ code, which won't run at +all on ‘mips3’-only systems. For the test program above, you should see: +
test.o: ELF N32 MSB mips-3 ... +
If you get: -
test.o: ELF N32 MSB mips-4 ... -- -
instead, you should set the environment variable CC to cc
--n32 -mips3 or gcc -mips3 respectively before configuring GCC.
-
-
GCC on IRIX 6 is usually built to support both the N32 and N64 ABIs. If
-you build GCC on a system that doesn't have the N64 libraries installed,
-you need to configure with --disable-multilib so GCC doesn't
-try to use them. Look for /usr/lib64/libc.so.1 to see if you
+
test.o: ELF N32 MSB mips-4 ... ++
instead, you should set the environment variable CC to ‘cc +-n32 -mips3’ or ‘gcc -mips3’ respectively before configuring GCC. + +
MIPSpro C 7.4 may cause bootstrap failures, due to a bug when inlining
+memcmp. Either add -U__INLINE_INTRINSICS to the CC
+environment variable as a workaround or upgrade to MIPSpro C 7.4.1m.
+
+
GCC on IRIX 6 is usually built to support the N32, O32 and N64 ABIs. If +you build GCC on a system that doesn't have the N64 libraries installed +or cannot run 64-bit binaries, +you need to configure with --disable-multilib so GCC doesn't +try to use them. This will disable building the O32 libraries, too. +Look for /usr/lib64/libc.so.1 to see if you have the 64-bit libraries installed. -
You must not use GNU as (which isn't built anyway as of
-binutils 2.11.2) on IRIX 6 platforms; doing so will only cause problems.
-
-
GCC does not currently support generating O32 ABI binaries in the
-mips-sgi-irix6 configurations. It is possible to create a GCC
-with O32 ABI only support by configuring it for the mips-sgi-irix5
-target and using a patched GNU as 2.11.2 as documented in the
-mips-sgi-irix5 section above. Using the
-native assembler requires patches to GCC which will be included in a
-future release. It is
-expected that O32 ABI support will be available again in a future release.
+
To enable debugging for the O32 ABI, you must use GNU as from +GNU binutils 2.15 or later. You may also use GNU ld, but +this is not required and currently causes some problems with Ada. -
The --enable-threads option doesn't currently work, a patch is
-in preparation for a future release. The --enable-libgcj
+
The --enable-libgcj
option is disabled by default: IRIX 6 uses a very low default limit
-(20480) for the command line length. Although libtool contains a
-workaround for this problem, at least the N64 libgcj is known not
+(20480) for the command line length. Although libtool contains a
+workaround for this problem, at least the N64 ‘libgcj’ is known not
to build despite this, running into an internal error of the native
-ld. A sure fix is to increase this limit (ncargs) to
+ld. A sure fix is to increase this limit (‘ncargs’) to
its maximum of 262144 bytes. If you have root access, you can use the
-systune command to do this.
-
-
GCC does not correctly pass/return structures which are -smaller than 16 bytes and which are not 8 bytes. The problem is very -involved and difficult to fix. It affects a number of other targets also, -but IRIX 6 is affected the most, because it is a 64-bit target, and 4 byte -structures are common. The exact problem is that structures are being padded -at the wrong end, e.g. a 4 byte structure is loaded into the lower 4 bytes -of the register when it should be loaded into the upper 4 bytes of the -register. - -
GCC is consistent with itself, but not consistent with the SGI C compiler
-(and the SGI supplied runtime libraries), so the only failures that can
-happen are when there are library functions that take/return such
-structures. There are very few such library functions. Currently this
-is known to affect inet_ntoa, inet_lnaof,
-inet_netof, inet_makeaddr, and semctl. Until the
-bug is fixed, GCC contains workarounds for the known affected functions.
+systune command to do this.
+
+
wchar_t support in ‘libstdc++’ is not available for old
+IRIX 6.5.x releases, x < 19. The problem cannot be autodetected
+and in order to build GCC for such targets you need to configure with
+--disable-wchar_t.
See http://freeware.sgi.com/ for more information about using GCC on IRIX platforms. -
Sony MIPS NEWS. This configuration is obsoleted in GCC 3.1. - -
This works in NEWSOS 5.0.1, but not in 5.0.2 (which uses ELF instead of -COFF). In particular, the linker does not like the code generated by -GCC when shared libraries are linked in. - -
This configuration is obsoleted in GCC 3.1. +
You can specify a default version for the -mcpu=cpu_type +switch by using the configure option --with-cpu-cpu_type. -
Encore ns32000 system. Encore systems are supported only under BSD. - -
National Semiconductor ns32000 system. This configuration is obsoleted -in GCC 3.1. - -
Genix has bugs in alloca and malloc; you must get the
-compiled versions of these from GNU Emacs.
-
-
This configuration is obsoleted in GCC 3.1. - -
Go to the Berkeley universe before compiling. - -
UTEK ns32000 system ("merlin"). This configuration is obsoleted in -GCC 3.1. - -
The C compiler that comes with this system cannot compile GCC; contact
-tektronix!reed!mason to get binaries of GCC for bootstrapping.
-
-
You can specify a default version for the -mcpu=cpu_type
-switch by using the configure option --with-cpu-cpu_type.
-
-
You will need +binutils 2.15 +or newer for a working GCC. -
PowerPC running Darwin (Mac OS X kernel). +
GCC 3.0 does not support Darwin, but 3.1 and later releases will work. +
PowerPC running Darwin (Mac OS X kernel).
Pre-installed versions of Mac OS X may not include any developer tools, meaning that you will not be able to build GCC from source. Tool binaries are available at -http://www.opensource.apple.com/projects/darwin (free +http://developer.apple.com/darwin/projects/compiler/ (free registration required). -
Versions of the assembler prior to "cctools-364" cannot handle the
-4-argument form of rlwinm and related mask-using instructions. Darwin
-1.3 (Mac OS X 10.0) uses cctools-353 for instance. To get cctools-364,
-check out cctools with tag Apple-364, build it, and
-install the assembler as usr/bin/as. See
-http://www.opensource.apple.com/tools/cvs/docs.html for details.
-
-
Also, the default stack limit of 512K is too small, and a bootstrap will
-typically fail when self-compiling expr.c. Set the stack to 800K
-or more, for instance by doing limit stack 800. It's also
-convenient to use the GNU preprocessor instead of Apple's during the
-first stage of bootstrapping; this is automatic when doing make
-bootstrap, but to do it from the toplevel objdir you will need to say
-make CC='cc -no-cpp-precomp' bootstrap.
-
-
Note that the version of GCC shipped by Apple typically includes a -number of extensions not available in a standard GCC release. These -extensions are generally specific to Mac programming. - -
This version of GCC requires at least cctools-590.36. The +cctools-590.36 package referenced from +http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html will not work +on systems older than 10.3.9 (aka darwin7.9.0). -
PowerPC system in big endian mode, running System V.4. +
PowerPC system in big endian mode, running System V.4. -
You will need -binutils 2.13.90.0.10 -or newer for a working GCC. - -
PowerPC system in big endian mode running NetBSD. To build the -documentation you will need Texinfo version 4.1 (NetBSD 1.5.1 included -Texinfo version 3.12). +
PowerPC system in big endian mode running Linux. -
Embedded PowerPC system in big endian mode with -mcall-aix selected as
-the default.
+
PowerPC system in big endian mode running NetBSD. -
Embedded PowerPC system in big endian mode for use in running under the +
Embedded PowerPC system in big endian mode for use in running under the PSIM simulator. -
Embedded PowerPC system in big endian mode. +
Embedded PowerPC system in big endian mode. -
PowerPC system in little endian mode, running System V.4. +
PowerPC system in little endian mode, running System V.4. -
Embedded PowerPC system in little endian mode for use in running under +
Embedded PowerPC system in little endian mode for use in running under the PSIM simulator. -
Embedded PowerPC system in little endian mode. - -
PowerPC system in little endian mode running Windows NT. +
Embedded PowerPC system in little endian mode. -
These configurations are obsoleted in GCC 3.1. +
S/390 system running GNU/Linux for S/390. -
We recommend you compile GCC with an earlier version of itself; if you
-compile GCC with hc, the Metaware compiler, it will work, but
-you will get mismatches between the stage 2 and stage 3 compilers in
-various files. These errors are minor differences in some
-floating-point constants and can be safely ignored; the stage 3 compiler
-is correct.
+
zSeries system (64-bit) running GNU/Linux for zSeries. -
S/390 system running Linux for S/390. +
zSeries system (64-bit) running TPF. This platform is +supported as cross-compilation target only. -
zSeries system (64-bit) running Linux for zSeries. +
Sun does not ship a C compiler with Solaris 2. To bootstrap and install -GCC you first have to install a pre-built compiler, see our +
Sun does not ship a C compiler with Solaris 2. To bootstrap and install +GCC you first have to install a pre-built compiler, see the binaries page for details. -
The Solaris 2 /bin/sh will often fail to configure
-libstdc++-v3, boehm-gc or
-libjava. If you encounter this problem, set CONFIG_SHELL to
-/bin/ksh in your environment before running configure.
+
The Solaris 2 /bin/sh will often fail to configure +libstdc++-v3, boehm-gc or libjava. We therefore +recommend using the following initial sequence of commands + +
% CONFIG_SHELL=/bin/ksh + % export CONFIG_SHELL ++
and proceed as described in the configure instructions. +In addition we strongly recommend specifying an absolute path to invoke +srcdir/configure.
Solaris 2 comes with a number of optional OS packages. Some of these
-packages are needed to use GCC fully, namely SUNWarc,
+are needed to use GCC fully, namely SUNWarc,
SUNWbtool, SUNWesu, SUNWhea, SUNWlibm,
SUNWsprot, and SUNWtoo. If you did not install all
optional packages when installing Solaris 2, you will need to verify that
the packages that GCC needs are installed.
To check whether an optional package is installed, use
-the pkginfo command. To add an optional package, use the
-pkgadd command. For further details, see the Solaris 2
+the pkginfo command. To add an optional package, use the
+pkgadd command. For further details, see the Solaris 2
documentation.
Trying to use the linker and other tools in
-/usr/ucb to install GCC has been observed to cause trouble.
+/usr/ucb to install GCC has been observed to cause trouble.
For example, the linker may hang indefinitely. The fix is to remove
-/usr/ucb from your PATH.
-
-
All releases of GNU binutils prior to 2.11.2 have known bugs on this
-platform. We recommend the use of GNU binutils 2.11.2 or the vendor
-tools (Sun as, Sun ld).
+/usr/ucb from your PATH.
+
+
The build process works more smoothly with the legacy Sun tools so, if you +have /usr/xpg4/bin in your PATH, we recommend that you place +/usr/bin before /usr/xpg4/bin for the duration of the build. + +
We recommend the use of GNU binutils 2.14 or later, or the vendor tools +(Sun as, Sun ld). Note that your mileage may vary +if you use a combination of the GNU tools and the Sun tools: while the +combination GNU as + Sun ld should reasonably work, +the reverse combination Sun as + GNU ld is known to +cause memory corruption at runtime in some cases for C++ programs. + +
The stock GNU binutils 2.15 release is broken on this platform because of a +single bug. It has been fixed on the 2.15 branch in the CVS repository. +You can obtain a working version by checking out the binutils-2_15-branch +from the CVS repository or applying the patch +http://sourceware.org/ml/binutils-cvs/2004-09/msg00036.html to the +release. + +
We recommend the use of GNU binutils 2.16 or later in conjunction with GCC +4.x, or the vendor tools (Sun as, Sun ld). However, +for Solaris 10 and above, an additional patch is required in order for the +GNU linker to be able to cope with a new flavor of shared libraries. You +can obtain a working version by checking out the binutils-2_16-branch from +the CVS repository or applying the patch +http://sourceware.org/ml/binutils-cvs/2005-07/msg00122.html to the +release.
Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
-newer: g++ will complain that types are missing. These headers assume
-that omitting the type means int; this assumption worked for C89 but
-is wrong for C++, and is now wrong for C99 also.
+newer: g++ will complain that types are missing. These headers
+assume that omitting the type means int; this assumption worked for
+C89 but is wrong for C++, and is now wrong for C99 also.
-
g++ accepts such (invalid) constructs with the option
--fpermissive; it
-will assume that any missing type is int (as defined by C89).
+
g++ accepts such (invalid) constructs with the option
+-fpermissive; it will assume that any missing type is int
+(as defined by C89).
-
There are patches for Solaris 2.6 (105633-56 or newer for SPARC, -106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC, +
There are patches for Solaris 7 (108376-21 or newer for SPARC, 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC, 108653-22 for Intel) that fix this bug. -
Sun bug 4927647 sometimes causes random spurious testsuite failures +related to missing diagnostic output. This bug doesn't affect GCC +itself, rather it is a kernel bug triggered by the expect +program which is used only by the GCC testsuite driver. When the bug +causes the expect program to miss anticipated output, extra +testsuite failures appear. + +
There are patches for Solaris 8 (117350-12 or newer for SPARC, +117351-12 or newer for Intel) and Solaris 9 (117171-11 or newer for +SPARC, 117172-11 or newer for Intel) that address this problem. + +
When GCC is configured to use binutils 2.11.2 or later the binaries +
When GCC is configured to use binutils 2.14 or later the binaries produced are smaller than the ones produced using Sun's native tools; this difference is quite significant for binaries containing debugging information. -
Sun as 4.x is broken in that it cannot cope with long symbol names.
-A typical error message might look similar to the following:
-
-
/usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error: - can't compute value of an expression involving an external symbol. -- -
This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris -2.6 and has been fixed in later (5.x) versions of the assembler, -starting with Solaris 7. -
Starting with Solaris 7, the operating system is capable of executing
64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
-this; the -m64 option enables 64-bit code generation.
+this; the -m64 option enables 64-bit code generation.
However, if all you want is code tuned for the UltraSPARC CPU, you
-should try the -mtune=ultrasparc option instead, which produces
+should try the -mtune=ultrasparc option instead, which produces
code that, unlike full 64-bit code, can still run on non-UltraSPARC
machines.
When configuring on a Solaris 7 or later system that is running a kernel
that supports only 32-bit binaries, one must configure with
---disable-multilib, since we will not be able to build the
+--disable-multilib, since we will not be able to build the
64-bit target libraries.
-
Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in +
GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of +the GNU compiler (especially GCC 3.0.x versions), which lead to the +miscompilation of the stage1 compiler and the subsequent failure of the +bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary +stage, i.e. to bootstrap that compiler with the base compiler and then +use it to bootstrap the final compiler. + +
GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7) +and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap +failure in form of a miscompilation of the stage1 compiler by the Sun +compiler. This is Sun bug 4974440. This is fixed with patch 112760-07. + +
GCC 3.4 changed the default debugging format from STABS to DWARF-2 for +32-bit code on Solaris 7 and later. If you use the Sun assembler, this +change apparently runs afoul of Sun bug 4910101 (which is referenced as +a x86-only problem by Sun, probably because they do not use DWARF-2). +A symptom of the problem is that you cannot compile C++ programs like +groff 1.19.1 without getting messages similar to the following: + +
ld: warning: relocation error: R_SPARC_UA32: ... + external symbolic relocation against non-allocatable section + .debug_info cannot be processed at runtime: relocation ignored. ++
To work around this problem, compile with -gstabs+ instead of +plain -g. + +
When configuring the GNU Multiple Precision Library (GMP) or the MPFR +library on a Solaris 7 or later system, the canonical target triplet +must be specified as the build parameter on the configure +line. This triplet can be obtained by invoking ./config.guess in +the toplevel source directory of GCC (and not that of GMP or MPFR). +For example on a Solaris 7 system: + +
% ./configure --build=sparc-sun-solaris2.7 --prefix=xxx ++
Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8 and later, including all EGCS releases. Sun formerly recommended 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to @@ -1873,8 +1242,8 @@ is preinstalled on some new Solaris 7-based hosts, so you may have to back it out.
/usr/ccs/bin/as into
-/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/3.1/as,
+/usr/ccs/bin/as into
+/usr/local/libexec/gcc/sparc-sun-solaris2.7/3.4/as,
adjusting the latter name to fit your local conventions and software
version numbers.
@@ -1886,252 +1255,288 @@ run code generated by GCC; it doesn't suffice to install it only on
the hosts that run GCC itself. Second, Sun says that 106950-03 is
only a partial fix for bug 4210064, but Sun doesn't know whether the
partial fix is adequate for GCC. Revision -08 or later should fix
-the bug. The current (as of 2001-09-24) revision is -14, and is included in
+the bug. The current (as of 2004-05-23) revision is -24, and is included in
the Solaris 7 Recommended Patch Cluster.
- -
GCC 3.3 triggers a bug in version 5.0 Alpha 03/27/98 of the Sun assembler, +which causes a bootstrap failure when linking the 64-bit shared version of +libgcc. A typical error message is: -
ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o: + symbol <unknown>: offset 0xffffffff7ec133e7 is non-aligned. ++
This bug has been fixed in the final 5.0 version of the assembler. -
A bug in the SunOS 4 linker will cause it to crash when linking
--fPIC compiled objects (and will therefore not allow you to build
-shared libraries).
+
A similar problem was reported for version Sun WorkShop 6 99/08/18 of the +Sun assembler, which causes a bootstrap failure with GCC 4.0.0: -
To fix this problem you can either use the most recent version of -binutils or get the latest SunOS 4 linker patch (patch ID 100170-10) -from Sun's patch site. +
ld: fatal: relocation error: R_SPARC_DISP32: + file .libs/libstdc++.lax/libsupc++convenience.a/vterminate.o: + symbol <unknown>: offset 0xfccd33ad is non-aligned ++
This bug has been fixed in more recent revisions of the assembler. -
Sometimes on a Sun 4 you may observe a crash in the program
-genflags or genoutput while building GCC. This is said to
-be due to a bug in sh. You can probably get around it by running
-genflags or genoutput manually and then retrying the
-make.
+
GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
+or newer on this platform. All earlier binutils and glibc
+releases mishandled unaligned relocations on sparc-*-* targets.
-
It has been reported that you might need -binutils 2.8.1.0.23 -for this platform, too. +
When configuring the GNU Multiple Precision Library (GMP) or the +MPFR library, the canonical target triplet must be specified as +the build parameter on the configure line. For example +on a Solaris 7 system: -
GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
-or newer on this platform. All earlier binutils and glibc
-releases mishandled unaligned relocations on sparc-*-* targets.
+
% ./configure --build=sparc64-sun-solaris2.7 --prefix=xxx ++
The following compiler flags must be specified in the configure +step in order to bootstrap this target with the Sun compiler: -
% CC="cc -xarch=v9 -xildoff" srcdir/configure [options] [target] ++
-xarch=v9 specifies the SPARC-V9 architecture to the Sun toolchain +and -xildoff turns off the incremental linker. -
GCC version 2.95 is not able to compile code correctly for
-sparc64 targets. Users of the Linux kernel, at least,
-can use the sparc32 program to start up a new shell
-invocation with an environment that causes configure to
-recognize (via uname -a) the system as sparc-*-* instead.
+
This is a synonym for sparc64-*-solaris2*. -
The following compiler flags must be specified in the configure -step in order to bootstrap this target with the Sun compiler: +
% CC="cc -xildoff -xarch=v9" srcdir/configure [options] [target] -+
Support for VxWorks is in flux. At present GCC supports only the +very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC. +We welcome patches for other architectures supported by VxWorks 5.5. +Support for VxWorks AE would also be welcome; we believe this is merely +a matter of writing an appropriate “configlette” (see below). We are +not interested in supporting older, a.out or COFF-based, versions of +VxWorks in GCC 3. -
-xildoff turns off the incremental linker, and -xarch=v9
-specifies the v9 architecture to the Sun linker and assembler.
+
VxWorks comes with an older version of GCC installed in +$WIND_BASE/host; we recommend you do not overwrite it. +Choose an installation prefix entirely outside $WIND_BASE. +Before running configure, create the directories prefix +and prefix/bin. Link or copy the appropriate assembler, +linker, etc. into prefix/bin, and set your PATH to +include that directory while running both configure and +make. -
You must give configure the +--with-headers=$WIND_BASE/target/h switch so that it can +find the VxWorks system headers. Since VxWorks is a cross compilation +target only, you must also specify --target=target. +configure will attempt to create the directory +prefix/target/sys-include and copy files into it; +make sure the user running configure has sufficient privilege +to do so. -
GCC's exception handling runtime requires a special “configlette” +module, contrib/gthr_supp_vxw_5x.c. Follow the instructions in +that file to add the module to your kernel build. (Future versions of +VxWorks will incorporate this module.) -
On System V release 3, you may get this error message -while linking: +
ld fatal: failed to write symbol name something - in strings table for file whatever -+
This probably indicates that the disk is full or your ulimit won't allow -the file to be as large as it needs to be. +
GCC supports the x86-64 architecture implemented by the AMD64 processor +(amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD. +On GNU/Linux the default is a bi-arch compiler which is able to generate +both 64-bit x86-64 and 32-bit x86 code (via the -m32 switch). -
This problem can also result because the kernel parameter MAXUMEM
-is too small. If so, you must regenerate the kernel and make the value
-much larger. The default value is reported to be 1024; a value of 32768
-is said to work. Smaller values may also work.
+
On System V, if you get an error like this, +
/usr/local/lib/bison.simple: In function `yyparse': - /usr/local/lib/bison.simple:625: virtual memory exhausted -+
This target is intended for embedded Xtensa systems using the +‘newlib’ C library. It uses ELF but does not support shared +objects. Designed-defined instructions specified via the +Tensilica Instruction Extension (TIE) language are only supported +through inline assembly. -
that too indicates a problem with disk space, ulimit, or MAXUMEM.
+
The Xtensa configuration information must be specified prior to +building GCC. The include/xtensa-config.h header +file contains the configuration information. If you created your +own Xtensa configuration with the Xtensa Processor Generator, the +downloaded files include a customized copy of this header file, +which you can use to replace the default header file. -
On a System V release 4 system, make sure /usr/bin precedes
-/usr/ucb in PATH. The cc command in
-/usr/ucb uses libraries which have bugs.
+
This target is for Xtensa systems running GNU/Linux. It supports ELF +shared objects and the GNU C library (glibc). It also generates +position-independent code (PIC) regardless of whether the +-fpic or -fPIC options are used. In other +respects, this target is the same as the +‘xtensa*-*-elf’ target. -
Don't try compiling with VAX C (vcc). It produces incorrect code
-in some cases (for example, when alloca is used).
+
These computers are also known as the 3b2, 3b5, 3b20 and other similar -names. (However, the 3b1 is actually a 68000.) -These configurations are obsoleted in GCC 3.1. +
The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not +supported. -
Don't use -g when compiling with the system's compiler. The
-system's linker seems to be unable to handle such a large program with
-debugging information.
+
However, the 32-bit port has limited support for Microsoft +Windows 3.11 in the Win32s environment, as a target only. See below. -
The system's compiler runs out of capacity when compiling stmt.c
-in GCC. You can work around this by building cpp in GCC
-first, then use that instead of the system's preprocessor with the
-system's C compiler to compile stmt.c. Here is how:
+
mv /lib/cpp /lib/cpp.att
- cp cpp /lib/cpp.gnu
- echo '/lib/cpp.gnu -traditional ${1+"$@"}' > /lib/cpp
- chmod +x /lib/cpp
-
+The 32-bit versions of Windows, including Windows 95, Windows NT, Windows +XP, and Windows Vista, are supported by several different target +platforms. These targets differ in which Windows subsystem they target +and which C libraries are used. -
The system's compiler produces bad code for some of the GCC -optimization files. So you must build the stage 2 compiler without -optimization. Then build a stage 3 compiler with optimization. -That executable should work. Here are the necessary commands: +
make LANGUAGES=c CC=stage1/xgcc CFLAGS="-Bstage1/ -g" - make stage2 - make CC=stage2/xgcc CFLAGS="-Bstage2/ -g -O" -+
You may need to raise the ULIMIT setting to build a C++ compiler,
-as the file cc1plus is larger than one megabyte.
+
GCC contains support for x86-64 using the mingw-w64 +runtime library, available from http://mingw-w64.sourceforge.net/. +This library should be used with the target triple x86_64-pc-mingw32. -
Presently Windows for Itanium is not supported. -
This target is intended for embedded Xtensa systems using the
-newlib C library. It uses ELF but does not support shared
-objects. Designed-defined instructions specified via the
-Tensilica Instruction Extension (TIE) language are only supported
-through inline assembly.
+
Windows CE is supported as a target only on ARM (arm-wince-pe), Hitachi +SuperH (sh-wince-pe), and MIPS (mips-wince-pe). -
The Xtensa configuration information must be specified prior to
-building GCC. The gcc/config/xtensa/xtensa-config.h header
-file contains the configuration information. If you created your
-own Xtensa configuration with the Xtensa Processor Generator, the
-downloaded files include a customized copy of this header file,
-which you can use to replace the default header file.
+
GCC no longer supports Windows NT on the Alpha or PowerPC. -
GCC no longer supports the Windows POSIX subsystem. However, it does +support the Interix subsystem. See above. -
This target is for Xtensa systems running GNU/Linux. It supports ELF
-shared objects and the GNU C library (glibc). It also generates
-position-independent code (PIC) regardless of whether the
--fpic or -fPIC options are used. In other
-respects, this target is the same as the
-xtensa-*-elf target.
+
Old target names including *-*-winnt and *-*-windowsnt are no longer used. + +
PW32 (i386-pc-pw32) support was never completed, and the project seems to +be inactive. See http://pw32.sourceforge.net/ for more information. -
UWIN support has been removed due to a lack of maintenance. -
A port of GCC 2.95.x is included with the +
Ports of GCC are included with the Cygwin environment. -
Current (as of early 2001) snapshots of GCC will build under Cygwin -without modification. +
GCC will build under Cygwin without modification; it does not build +with Microsoft's C++ compiler and there are no plans to make it do so. + +
Cygwin can be compiled with i?86-pc-cygwin. + +
The Interix target is used by OpenNT, Interix, Services For UNIX (SFU), +and Subsystem for UNIX-based Applications (SUA). Applications compiled +with this target run in the Interix subsystem, which is separate from +the Win32 subsystem. This target was last known to work in GCC 3.3. -
For more information, see http://www.interix.com/. -
GCC does not currently support OS/2. However, Andrew Zabolotny has been +
GCC will build with and support only MinGW runtime 3.12 and later.
+Earlier versions of headers are incompatible with the new default semantics
+of extern inline in -std=c99 and -std=gnu99 modes.
+
+
GCC does not currently support OS/2. However, Andrew Zabolotny has been working on a generic OS/2 port with pgcc. The current code can be found at http://www.goof.com/pcg/os2/. -
An older copy of GCC 2.8.1 is included with the EMX tools available at -ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/. - -
GCC contains support files for many older (1980s and early +
GCC contains support files for many older (1980s and early 1990s) Unix variants. For the most part, support for these systems has not been deliberately removed, but it has not been maintained for -several years and may suffer from bitrot. Support from some systems -has been removed from GCC 3: fx80, ns32-ns-genix, pyramid, tahoe, -gmicro, spur; most of these targets had not been updated since GCC -version 1. +several years and may suffer from bitrot. -
We are planning to remove support for more older systems, starting in -GCC 3.1. Each release will have a list of "obsoleted" systems. +
Starting with GCC 3.1, each release has a list of “obsoleted” systems.
Support for these systems is still present in that release, but
-configure will fail unless the --enable-obsolete
-option is given. Unless a maintainer steps forward, support for
-these systems will be removed from the next release of GCC.
-
-
Support for older systems as targets for cross-compilation is less -problematic than support for them as hosts for GCC; if an enthusiast -wishes to make such a target work again (including resurrecting any -of the targets that never worked with GCC 2, starting from the last -CVS version before they were removed), patches -following the usual requirements -would be likely to be accepted, since they should not affect the -support for more modern targets. +configure will fail unless the --enable-obsolete +option is given. Unless a maintainer steps forward, support for these +systems will be removed from the next release of GCC.
Support for old systems as hosts for GCC can cause problems if the
workarounds for compiler, library and operating system bugs affect the
cleanliness or maintainability of the rest of GCC. In some cases, to
bring GCC up on such a system, if still possible with current GCC, may
require first installing an old version of GCC which did work on that
-system, and using it to compile a more recent GCC, to avoid bugs in
-the vendor compiler. Old releases of GCC 1 and GCC 2 are available in
-the old-releases directory on the
-GCC mirror sites. Header bugs may generally
-be avoided using fixincludes, but bugs or deficiencies in
-libraries and the operating system may still cause problems.
+system, and using it to compile a more recent GCC, to avoid bugs in the
+vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
+old-releases directory on the GCC mirror sites. Header bugs may generally be avoided using
+fixincludes, but bugs or deficiencies in libraries and the
+operating system may still cause problems.
+
+
Support for older systems as targets for cross-compilation is less +problematic than support for them as hosts for GCC; if an enthusiast +wishes to make such a target work again (including resurrecting any of +the targets that never worked with GCC 2, starting from the last +version before they were removed), patches +following the usual requirements would be +likely to be accepted, since they should not affect the support for more +modern targets.
For some systems, old versions of GNU binutils may also be useful,
-and are available from pub/binutils/old-releases on
-sources.redhat.com mirror sites.
+and are available from pub/binutils/old-releases on
+sourceware.org mirror sites.
Some of the information on specific systems above relates to such older systems, but much of the information about GCC on such systems (which may no longer be applicable to current GCC) is to be found in the GCC texinfo manual. -
C++ support is significantly better on ELF targets if you use the +
C++ support is significantly better on ELF targets if you use the GNU linker; duplicate copies of inlines, vtables and template instantiations will be discarded automatically. -
-Return to the GCC Installation page +