Software: Apache/2.0.54 (Unix) mod_perl/1.99_09 Perl/v5.8.0 mod_ssl/2.0.54 OpenSSL/0.9.7l DAV/2 FrontPage/5.0.2.2635 PHP/4.4.0 mod_gzip/2.0.26.1a uname -a: Linux snow.he.net 4.4.276-v2-mono-1 #1 SMP Wed Jul 21 11:21:17 PDT 2021 i686 uid=99(nobody) gid=98(nobody) groups=98(nobody) Safe-mode: OFF (not secure) /usr/doc/gcc-3.2.2/INSTALL/ drwxr-xr-x | |
| Viewing file: Select action/file-type: P lease read this document carefully before installing the GNU Compiler Collection on your machine.
1750a-*-*MIL-STD-1750A processors. This target is obsoleted in GCC 3.1. The MIL-STD-1750A cross configuration produces output for
You should ignore a fatal error during the building of The GCC produced the same sections as the Fairchild F9450 C Compiler, namely:
The smallest addressable unit is 16 bits ( a29kAMD 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-*-bsdAMD Am29050 used in a system running a variant of BSD Unix. alpha*-*-*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. We require binutils 2.11.2 or newer. Previous binutils releases had a number of problems with DWARF 2 debugging information, not the least of which is incorrect linking of shared libraries. alpha*-dec-osf*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 In Digital Unix V4.0, virtual memory exhausted bootstrap failures
may be fixed by configuring with In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
currently (2001-06-13) work with % 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 The GCC writes a 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.
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 There is a bug in DEC's assembler that produces incorrect line numbers
for ECOFF format when the To avoid this behavior, specify alphaev5-cray-unicosmk*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
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 configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld \
--enable-languages=c
The comparison test during arc-*-elfArgonaut ARC processor. This configuration is intended for embedded systems. arm-*-aoutAdvanced 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 You may need to make a variant of the file arm-*-elfThis configuration is intended for embedded systems. arm*-*-linux-gnuWe require GNU binutils 2.10 or newer. arm-*-riscixThe 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 You will need to install GNU avrATMEL AVR-family micro controllers. These are used in embedded applications. There are no standard Unix configurations. See "AVR Options" in the main manual for the list of supported MCU types. Use Further installation notes and other useful information about AVR tools can also be obtained from: We strongly recommend using binutils 2.11 or newer. The following error: Error: register required indicates that you should upgrade to a newer version of the binutils. c4xTexas 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 Further installation notes and other useful information about C4x tools can also be obtained from: CRISCRIS 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 for a list of CRIS-specific options. There are a few different CRIS targets:
For Pre-packaged tools can be obtained from ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/. More information about this platform is available at http://developer.axis.com/. DOSPlease have a look at our 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. dsp16xxA port to the AT&T DSP1610 family of processors. *-*-freebsd*The version of binutils installed in For FreeBSD 1, 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 Support for FreeBSD 1 is obsoleted in GCC 3.1. 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 In principle, Shared elxsi-elxsi-bsdThe Elxsi's C compiler has known limitations that prevent it from compiling GCC. Please contact mrs@wrs.com for more details. Support for this processor is obsoleted in GCC 3.1. h8300-hmsHitachi H8/300 series of processors. Please have a look at our 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. hppa*-hp-hpux*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 Specifically, 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. More specific information to hppa*-hp-hpux9The 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. The configuration scripts for GCC will also trigger a bug in the hpux9
shell. To avoid this problem set hppa*-hp-hpux10For hpux10.20, we highly recommend you pick up the latest sed patch
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 hppa*-hp-hpux11GCC 3.0 and up support HP-UX 11. On 64-bit capable systems, there
are two distinct ports. The You must use GNU binutils 2.11 or above with the 32-bit port. Thread
support is not currently implemented, so
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. i370-*-*This port is very preliminary and has many known bugs. We hope to have a higher-quality port for this machine soon. *-*-linux-gnuIf 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
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. i?86-*-linux*oldldUse this configuration to generate This configuration is obsoleted in GCC 3.1. i?86-*-linux*aoutUse this configuration to generate i?86-*-linux*You will need binutils 2.9.1.0.15 or newer for exception handling to work. 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. i?86-*-scoCompilation 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. i?86-*-sco3.2v4Use this configuration for SCO release 3.2 version 4. i?86-*-sco3.2v5*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 /usr/tmp/ccaNlqBc.s:22:unknown instruction: fcomip /usr/tmp/ccaNlqBc.s:50:unknown instruction: fucomip 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. 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
In general, the Look in Systems based on OpenServer before 5.0.4 ( 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
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 i?86-*-udkThis target emulates the SCO Universal Development Kit and requires that
package be installed. (If it is installed, you will have a
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 After the usual i?86-*-iscThis 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, i?86-ibm-aixThis 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. i?86-sequent-bsdThis configuration is obsoleted in GCC 3.1. Go to the Berkeley universe before compiling. i?86-sequent-ptx1*, i?86-sequent-ptx2*, i?86-sequent-sysv3*This configuration is obsoleted in GCC 3.1. You must install GNU The i860-intel-osf*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 If this happens, then you need to link most programs with the library
#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. ia64-*-linuxIA-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. 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. 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. *-lynx-lynxosLynxOS 2.2 and earlier comes with GCC 1.x already installed as
*-ibm-aix*AIX Make frequently has problems with GCC makefiles. GNU Make 3.76 or newer is recommended to build on this platform. Errors involving 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 Building
Extract the shared object from each the GCC 3.1 % ar -x libstdc++.a libstdc++.so.4 Enable the % strip -e libstdc++.so.4 Archive the runtime-only shared object in the GCC 3.2
% ar -q libstdc++.a libstdc++.so.4 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 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
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 Some versions of the AIX binder (linker) can fail with a relocation
overflow severe error when the The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core with a segmentation fault when invoked by any version of GCC. A fix for APAR IX87327 is available from IBM Customer Support and from its techsupport.services.ibm.com website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above. The initial assembler shipped with AIX 4.3.0 generates incorrect object files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS TO ASSEMBLE/BIND) is available from IBM Customer Support and from its techsupport.services.ibm.com 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., 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 m32r-*-elfMitsubishi M32R processor. This configuration is intended for embedded systems. m68000-hp-bsdHP 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. m6811-elfMotorola 68HC11 family micro controllers. These are used in embedded applications. There are no standard Unix configurations. m6812-elfMotorola 68HC12 family micro controllers. These are used in embedded applications. There are no standard Unix configurations. m68k-altosAltos 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. m68k-apple-auxApple 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 Note the C compiler that comes
with this system cannot compile GCC. You can find binaries of GCC
for bootstrapping on m68k-att-sysvAT&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/. m68k-bull-sysvBull 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 m68k-crds-unosUse The Unos assembler is named #!/bin/sh casm $* The default Unos library is named When compiling GCC with the standard compiler, to overcome bugs in
the support of (Perhaps simply defining 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 m68k-hp-hpuxHP 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 _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. 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: sh internal 1K buffer overflow To fix this, you can also change the first line of the fixproto script to look like: #!/bin/ksh m68k-*-nextstep*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 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 m68k-ncr-*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 To solve this problem, reconfigure the kernel adding the following line to the configuration file: MAXUMEM = 4096 m68k-sunSun 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. m68k-sun-sunos4.1.1It is reported that you may need the GNU assembler on this platform. m88k-*-svr3Motorola 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. It is best, however, to use an older version of GCC for bootstrapping if you have one. m88k-*-dguxMotorola 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
If you do not specify a configuration name, m88k-tektronix-sysv3Tektronix 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. mips-*-*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 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. 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 mips-mips-bsdMIPS 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
If you use the MIPS C compiler to bootstrap, it may be necessary
to increase its table size for switch statements with the
mips-dec-*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
If you use the MIPS C compiler to bootstrap, it may be necessary
to increase its table size for switch statements with the
mips-mips-riscos*These configurations are obsoleted in GCC 3.1. If you use the MIPS C compiler to bootstrap, it may be necessary
to increase its table size for switch statements with the
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:
The revision mips-sgi-irix4This configuration is obsoleted in GCC 3.1. 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. 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
In a compiler configured with target The 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. mips-sgi-irix5This 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.
If you use the MIPS C compiler to bootstrap, it may be necessary
to increase its table size for switch statements with the
To enable debugging under IRIX 5, you must use GNU When building GCC, the build process loops rebuilding mips-sgi-irix6If you are using IRIX test.o: ELF N32 MSB ... If you see: test.o: ELF 32-bit MSB ... or test.o: ELF 64-bit MSB ... then your version of If you want the resulting test.o: ELF N32 MSB mips-3 ... If you get: test.o: ELF N32 MSB mips-4 ... instead, you should set the environment variable 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 You must not use GNU GCC does not currently support generating O32 ABI binaries in the
The 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 See http://freeware.sgi.com/ for more information about using GCC on IRIX platforms. mips-sony-sysvSony 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. ns32k-encoreThis configuration is obsoleted in GCC 3.1. Encore ns32000 system. Encore systems are supported only under BSD. ns32k-*-genixNational Semiconductor ns32000 system. This configuration is obsoleted in GCC 3.1. Genix has bugs in ns32k-sequentThis configuration is obsoleted in GCC 3.1. Go to the Berkeley universe before compiling. ns32k-utekUTEK ns32000 system ("merlin"). This configuration is obsoleted in GCC 3.1. The C compiler that comes with this system cannot compile GCC; contact
powerpc-*-*You can specify a default version for the powerpc-*-darwin*PowerPC running Darwin (Mac OS X kernel). GCC 3.0 does not support Darwin, but 3.1 and later releases will work. 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 registration required). Versions of the assembler prior to "cctools-364" cannot handle the
4-argument form of Also, the default stack limit of 512K is too small, and a bootstrap will
typically fail when self-compiling 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. powerpc-*-elf, powerpc-*-sysv4PowerPC system in big endian mode, running System V.4. powerpc-*-linux-gnu*You will need binutils 2.13.90.0.10 or newer for a working GCC. powerpc-*-netbsd*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-*-eabiaixEmbedded PowerPC system in big endian mode with powerpc-*-eabisimEmbedded PowerPC system in big endian mode for use in running under the PSIM simulator. powerpc-*-eabiEmbedded PowerPC system in big endian mode. powerpcle-*-elf, powerpcle-*-sysv4PowerPC system in little endian mode, running System V.4. powerpcle-*-eabisimEmbedded PowerPC system in little endian mode for use in running under the PSIM simulator. powerpcle-*-eabiEmbedded PowerPC system in little endian mode. powerpcle-*-winnt, powerpcle-*-pePowerPC system in little endian mode running Windows NT. romp-*-aos, romp-*-machThese configurations are obsoleted in GCC 3.1. We recommend you compile GCC with an earlier version of itself; if you
compile GCC with s390-*-linux*S/390 system running Linux for S/390. s390x-*-linux*zSeries system (64-bit) running Linux for zSeries. *-*-solaris2*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 binaries page for details. The Solaris 2 Solaris 2 comes with a number of optional OS packages. Some of these
packages are needed to use GCC fully, namely To check whether an optional package is installed, use
the Trying to use the linker and other tools in
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 Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
newer:
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, 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC, 108653-22 for Intel) that fix this bug. sparc-sun-solaris2*When GCC is configured to use binutils 2.11.2 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 /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 When configuring on a Solaris 7 or later system that is running a kernel
that supports only 32-bit binaries, one must configure with
sparc-sun-solaris2.7Sun 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 recommend it only for people who use Sun's compilers. Here are some workarounds to this problem:
sparc-sun-sunos4*A bug in the SunOS 4 linker will cause it to crash when linking
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. Sometimes on a Sun 4 you may observe a crash in the program
sparc-unknown-linux-gnulibc1It has been reported that you might need binutils 2.8.1.0.23 for this platform, too. sparc-*-linux*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 sparc64-*-*GCC version 2.95 is not able to compile code correctly for
sparcv9-*-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]
*-*-sysv*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. This problem can also result because the kernel parameter 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 that too indicates a problem with disk space, ulimit, or On a System V release 4 system, make sure vax-dec-ultrixDon't try compiling with VAX C ( we32k-*-*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. Don't use The system's compiler runs out of capacity when compiling mv /lib/cpp /lib/cpp.att
cp cpp /lib/cpp.gnu
echo '/lib/cpp.gnu -traditional ${1+"$@"}' > /lib/cpp
chmod +x /lib/cpp
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 xtensa-*-elfThis target is intended for embedded Xtensa systems using the
The Xtensa configuration information must be specified prior to
building GCC. The xtensa-*-linux*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
Microsoft Windows (32-bit)A port of GCC 2.95.x is included with the Cygwin environment. Current (as of early 2001) snapshots of GCC will build under Cygwin without modification. OS/2GCC 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/. Older systemsGCC 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. We are planning to remove support for more older systems, starting in
GCC 3.1. Each release will have a list of "obsoleted" systems.
Support for these systems is still present in that release, but
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. 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 For some systems, old versions of GNU binutils may also be useful,
and are available from 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. all ELF targets (SVR4, Solaris 2, etc.)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. |
:: Command execute :: | |
--[ c99shell v. 1.0 pre-release build #13 powered by Captain Crunch Security Team | http://ccteam.ru | Generation time: 0.0314 ]-- |