-This file documents the installation of the GNU compiler. Copyright
+This is Info file INSTALL, produced by Makeinfo version 1.68 from the
+input file install1.texi.
+
+ This file documents the installation of the GNU compiler. Copyright
(C) 1988, 1989, 1992, 1994, 1995 Free Software Foundation, Inc. You
may copy, distribute, and modify it freely as long as you preserve this
copyright notice and permission notice.
+\1f
+File: INSTALL, Node: Installation, Up: (dir)
+
Installing GNU CC
*****************
+ Note most of this information is out of date and superceded by the
+EGCS install procedures. It is provided for historical reference only.
+
+* Menu:
+
+* Configurations:: Configurations Supported by GNU CC.
+* Other Dir:: Compiling in a separate directory (not where the source is).
+* Cross-Compiler:: Building and installing a cross-compiler.
+* Sun Install:: See below for installation on the Sun.
+* VMS Install:: See below for installation on VMS.
+* Collect2:: How `collect2' works; how it finds `ld'.
+* Header Dirs:: Understanding the standard header file directories.
+
Here is the procedure for installing GNU CC on a Unix system. See
*Note VMS Install::, for VMS systems. In this section we assume you
compile in the same directory that contains the source files; see *Note
what your configuration is or guesses wrong.
In those cases, specify the build machine's "configuration name"
- with the `--build' option; the host and target will default to be
- the same as the build machine. (If you are building a
+ with the `--host' option; the host and target will default to be
+ the same as the host machine. (If you are building a
cross-compiler, see *Note Cross-Compiler::.)
Here is an example:
- ./configure --build=sparc-sun-sunos4.1
+ ./configure --host=sparc-sun-sunos4.1
A configuration name may be canonical or it may be more or less
abbreviated.
aliases. For example, `sun3' stands for `m68k-sun', so
`sun3-sunos4.1' is another way to specify a Sun 3. You can also
use simply `sun3-sunos', since the version of SunOS is assumed by
- default to be version 4. `sun3-bsd' also works, since `configure'
- knows that the only BSD variant on a Sun 3 is SunOS.
+ default to be version 4.
You can specify a version number after any of the system types,
and some of the CPU types. In most cases, the version is
are
`hppa1.0-ANY-ANY', `hppa1.1-ANY-ANY', `i386-ANY-sysv',
`i386-ANY-isc',
- `i860-ANY-bsd', `m68k-bull-sysv', `m68k-hp-hpux',
- `m68k-sony-bsd',
- `m68k-altos-sysv', `m68000-hp-hpux', `m68000-att-sysv',
- `ANY-lynx-lynxos', and `mips-ANY'). On any other system,
- `--with-gnu-as' has no effect.
+ `i860-ANY-bsd', `m68k-bull-sysv',
+ `m68k-hp-hpux', `m68k-sony-bsd',
+ `m68k-altos-sysv', `m68000-hp-hpux',
+ `m68000-att-sysv', `ANY-lynx-lynxos', and `mips-ANY'). On
+ any other system, `--with-gnu-as' has no effect.
On the systems listed above (except for the HP-PA, for ISC on
the 386, and for `mips-sgi-irix5.*'), if you use GAS, you
This option does not cause the GNU linker to be installed; it
just modifies the behavior of GNU CC to work with the GNU
- linker. Specifically, it inhibits the installation of
- `collect2', a program which otherwise serves as a front-end
- for the system's linker on most configurations.
+ linker.
`--with-stabs'
On MIPS based systems and on Alphas, you must specify whether
`--nfp' currently has no effect, though perhaps there are
other systems where it could usefully make a difference.
+ `--enable-haifa'
+ `--disable-haifa'
+ Use `--enable-haifa' to enable use of an experimental
+ instruction scheduler (from IBM Haifa). This may or may not
+ produce better code. Some targets on which it is known to be
+ a win enable it by default; use `--disable-haifa' to disable
+ it in these cases. `configure' will print out whether the
+ Haifa scheduler is enabled when it is run.
+
+ `--enable-threads=TYPE'
+ Certain systems, notably Linux-based GNU systems, can't be
+ relied on to supply a threads facility for the Objective C
+ runtime and so will default to single-threaded runtime. They
+ may, however, have a library threads implementation
+ available, in which case threads can be enabled with this
+ option by supplying a suitable TYPE, probably `posix'. The
+ possibilities for TYPE are `single', `posix', `win32',
+ `solaris', `irix' and `mach'.
+
+ `--enable-checking'
+ When you specify this option, the compiler is built to
+ perform checking of tree node types when referencing fields
+ of that node. This does not change the generated code, but
+ adds error checking within the compiler. This will slow down
+ the compiler and may only work properly if you are building
+ the compiler with GNU C.
+
The `configure' script searches subdirectories of the source
directory for other compilers that are to be integrated into GNU
CC. The GNU compiler for C++, called G++ is in a subdirectory
name to use instead of `/usr/local' for all purposes with one
exception: the directory `/usr/local/include' is searched for
header files no matter where you install the compiler. To override
- this name, use the `--local-prefix' option below.
+ this name, use the `--with-local-prefix' option below. The
+ directory you specify need not exist, but its parent directory
+ must exist.
- 5. Specify `--local-prefix=DIR' if you want the compiler to search
- directory `DIR/include' for locally installed header files
+ 5. Specify `--with-local-prefix=DIR' if you want the compiler to
+ search directory `DIR/include' for locally installed header files
*instead* of `/usr/local/include'.
- You should specify `--local-prefix' *only* if your site has a
+ You should specify `--with-local-prefix' *only* if your site has a
different convention (not `/usr/local') for where to put
site-specific files.
- *Do not* specify `/usr' as the `--local-prefix'! The directory
- you use for `--local-prefix' *must not* contain any of the
- system's standard header files. If it did contain them, certain
- programs would be miscompiled (including GNU Emacs, on certain
- targets), because this would override and nullify the header file
- corrections made by the `fixincludes' script.
+ The default value for `--with-local-prefix' is `/usr/local'
+ regardless of the value of `--prefix'. Specifying `--prefix' has
+ no effect on which directory GNU CC searches for local header
+ files. This may seem counterintuitive, but actually it is logical.
+
+ The purpose of `--prefix' is to specify where to *install GNU CC*.
+ The local header files in `/usr/local/include'--if you put any in
+ that directory--are not part of GNU CC. They are part of other
+ programs--perhaps many others. (GNU CC installs its own header
+ files in another directory which is based on the `--prefix' value.)
+
+ *Do not* specify `/usr' as the `--with-local-prefix'! The
+ directory you use for `--with-local-prefix' *must not* contain any
+ of the system's standard header files. If it did contain them,
+ certain programs would be miscompiled (including GNU Emacs, on
+ certain targets), because this would override and nullify the
+ header file corrections made by the `fixincludes' script.
+
+ Indications are that people who use this option use it based on
+ mistaken ideas of what it is for. People use it as if it specified
+ where to install part of GNU CC. Perhaps they make this assumption
+ because installing GNU CC creates the directory.
6. Make sure the Bison parser generator is installed. (This is
unnecessary if the Bison output files `c-parse.c' and `cexp.c' are
escape sequence" are normal in `genopinit.c' and perhaps some
other files. Likewise, you should ignore warnings about "constant
is so large that it is unsigned" in `insn-emit.c' and
- `insn-recog.c' and a warning about a comparison always being zero
- in `enquire.o'. Any other compilation errors may represent bugs in
+ `insn-recog.c', a warning about a comparison always being zero in
+ `enquire.o', and warnings about shift counts exceeding type widths
+ in `cexp.y'. Any other compilation errors may represent bugs in
the port to your machine or operating system, and should be
investigated and reported.
This copies the files `cc1', `cpp' and `libgcc.a' to files `cc1',
`cpp' and `libgcc.a' in the directory
`/usr/local/lib/gcc-lib/TARGET/VERSION', which is where the
- compiler driver program looks for them. Here TARGET is the target
- machine type specified when you ran `configure', and VERSION is
- the version number of GNU CC. This naming scheme permits various
- versions and/or cross-compilers to coexist.
+ compiler driver program looks for them. Here TARGET is the
+ canonicalized form of target machine type specified when you ran
+ `configure', and VERSION is the version number of GNU CC. This
+ naming scheme permits various versions and/or cross-compilers to
+ coexist. It also copies the executables for compilers for other
+ languages (e.g., `cc1plus' for C++) to the same directory.
This also copies the driver program `xgcc' into
`/usr/local/bin/gcc', so that it appears in typical execution
- search paths.
+ search paths. It also copies `gcc.1' into `/usr/local/man/man1'
+ and info pages into `/usr/local/info'.
On some systems, this command causes recompilation of some files.
This is usually due to bugs in `make'. You should either ignore
some other compiler.)
16. If you're going to use C++, it's likely that you need to also
- install the libg++ distribution. It should be available from the
- same place where you got the GNU C distribution. Just as GNU C
- does not distribute a C runtime library, it also does not include
- a C++ run-time library. All I/O functionality, special class
- libraries, etc., are available in the libg++ distribution.
+ install a C++ runtime library. Just as GNU C does not distribute
+ a C runtime library, it also does not include a C++ runtime
+ library. All I/O functionality, special class libraries, etc., are
+ provided by the C++ runtime library.
+
+ The standard C++ runtime library for GNU CC is called `libstdc++'.
+ An obsolescent library `libg++' may also be available, but it's
+ necessary only for older software that hasn't been converted yet;
+ if you don't know whether you need `libg++' then you probably don't
+ need it.
+
+ Here's one way to build and install `libstdc++' for GNU CC:
+
+ * Build and install GNU CC, so that invoking `gcc' obtains the
+ GNU CC that was just built.
+
+ * Obtain a copy of a compatible `libstdc++' distribution. For
+ example, the `libstdc++-2.8.0.tar.gz' distribution should be
+ compatible with GCC 2.8.0. GCC distributors normally
+ distribute `libstdc++' as well.
+
+ * Set the `CXX' environment variable to `gcc' while running the
+ `libstdc++' distribution's `configure' command. Use the same
+ `configure' options that you used when you invoked GCC's
+ `configure' command.
+
+ * Invoke `make' to build the C++ runtime.
+
+ * Invoke `make install' to install the C++ runtime.
+
+ To summarize, after building and installing GNU CC, invoke the
+ following shell commands in the topmost directory of the C++
+ library distribution. For CONFIGURE-OPTIONS, use the same options
+ that you used to configure GNU CC.
+
+ $ CXX=gcc ./configure CONFIGURE-OPTIONS
+ $ make
+ $ make install
+
+ 17. GNU CC includes a runtime library for Objective-C because it is an
+ integral part of the language. You can find the files associated
+ with the library in the subdirectory `objc'. The GNU Objective-C
+ Runtime Library requires header files for the target's C library in
+ order to be compiled,and also requires the header files for the
+ target's thread library if you want thread support. *Note
+ Cross-Compilers and Header Files: Cross Headers, for discussion
+ about header files issues for cross-compilation.
+
+ When you run `configure', it picks the appropriate Objective-C
+ thread implementation file for the target platform. In some
+ situations, you may wish to choose a different back-end as some
+ platforms support multiple thread implementations or you may wish
+ to disable thread support completely. You do this by specifying a
+ value for the OBJC_THREAD_FILE makefile variable on the command
+ line when you run make, for example:
+
+ make CC="stage2/xgcc -Bstage2/" CFLAGS="-g -O2" OBJC_THREAD_FILE=thr-single
+
+ Below is a list of the currently available back-ends.
+
+ * thr-single Disable thread support, should work for all
+ platforms.
+
+ * thr-decosf1 DEC OSF/1 thread support.
+
+ * thr-irix SGI IRIX thread support.
+
+ * thr-mach Generic MACH thread support, known to work on
+ NEXTSTEP.
+
+ * thr-os2 IBM OS/2 thread support.
+
+ * thr-posix Generix POSIX thread support.
+
+ * thr-pthreads PCThreads on Linux-based GNU systems.
+
+ * thr-solaris SUN Solaris thread support.
+
+ * thr-win32 Microsoft Win32 API thread support.
+
+\1f
+File: INSTALL, Node: Configurations, Next: Other Dir, Up: Installation
Configurations Supported by GNU CC
==================================
Here are the possible CPU types:
1750a, a29k, alpha, arm, cN, clipper, dsp16xx, elxsi, h8300,
- hppa1.0, hppa1.1, i370, i386, i486, i586, i860, i960, m68000, m68k,
- m88k, mips, mipsel, mips64, mips64el, ns32k, powerpc, powerpcle,
- pyramid, romp, rs6000, sh, sparc, sparclite, sparc64, vax, we32k.
+ hppa1.0, hppa1.1, i370, i386, i486, i586, i860, i960, m32r,
+ m68000, m68k, m88k, mips, mipsel, mips64, mips64el, ns32k,
+ powerpc, powerpcle, pyramid, romp, rs6000, sh, sparc, sparclite,
+ sparc64, vax, we32k.
Here are the recognized company names. As you can see, customary
abbreviations are used rather than the longer official names.
- acorn, alliant, altos, apollo, att, bull, cbm, convergent, convex,
- crds, dec, dg, dolphin, elxsi, encore, harris, hitachi, hp, ibm,
- intergraph, isi, mips, motorola, ncr, next, ns, omron, plexus,
- sequent, sgi, sony, sun, tti, unicom, wrs.
+ acorn, alliant, altos, apollo, apple, att, bull, cbm, convergent,
+ convex, crds, dec, dg, dolphin, elxsi, encore, harris, hitachi,
+ hp, ibm, intergraph, isi, mips, motorola, ncr, next, ns, omron,
+ plexus, sequent, sgi, sony, sun, tti, unicom, wrs.
The company name is meaningful only to disambiguate when the rest of
the information supplied is insufficient. You can omit it, writing
Here is a list of system types:
- 386bsd, aix, acis, amigados, aos, aout, bosx, bsd, clix, coff,
+ 386bsd, aix, acis, amigaos, aos, aout, aux, bosx, bsd, clix, coff,
ctix, cxux, dgux, dynix, ebmon, ecoff, elf, esix, freebsd, hms,
- genix, gnu, gnu/linux, hiux, hpux, iris, irix, isc, luna, lynxos,
+ genix, gnu, linux-gnu, hiux, hpux, iris, irix, isc, luna, lynxos,
mach, minix, msdos, mvs, netbsd, newsos, nindy, ns, osf, osfrose,
ptx, riscix, riscos, rtu, sco, sim, solaris, sunos, sym, sysv,
udi, ultrix, unicos, uniplus, unos, vms, vsta, vxworks, winnt,
`1750a-*-*'
MIL-STD-1750A processors.
- Starting with GCC 2.6.1, the MIL-STD-1750A cross configuration no
- longer supports the Tektronix Assembler, but instead produces
- output for `as1750', an assembler/linker available under the GNU
- Public License for the 1750A. Contact *kellogg@space.otn.dasa.de*
- for more details on obtaining `as1750'. A similarly licensed
- simulator for the 1750A is available from same address.
+ The MIL-STD-1750A cross configuration produces output for
+ `as1750', an assembler/linker available under the GNU 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.)
`alpha-*-osf1'
Systems using processors that implement the DEC Alpha architecture
and are running the DEC Unix (OSF/1) operating system, for example
- the DEC Alpha AXP systems. (VMS on the Alpha is not currently
- supported by GNU CC.)
+ the DEC Alpha AXP systems.CC.)
GNU CC writes a `.verstamp' directive to the assembler output file
unless it is built as a cross-compiler. It gets the version to
DBX. DEC is now aware of this problem with the assembler and
hopes to provide a fix shortly.
-`arm'
+`arc-*-elf'
+ Argonaut ARC processor. This configuration is intended for
+ embedded systems.
+
+`arm-*-aout'
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.
+ instruction sequences and will produce `a.out' format object
+ modules.
You may need to make a variant of the file `arm.h' for your
particular configuration.
+`arm-*-linuxaout'
+ Any of the ARM family processors running the Linux-based GNU
+ system with the `a.out' binary format (ELF is not yet supported).
+ You must use version 2.8.1.0.7 or later of the GNU/Linux binutils,
+ which you can download from `sunsite.unc.edu:/pub/Linux/GCC' and
+ other mirror sites for Linux-based GNU systems.
+
`arm-*-riscix'
The ARM2 or ARM3 processor running RISC iX, Acorn's port of BSD
Unix. 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.
+ support included, is now available from Acorn and via 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.
`a29k'
AMD Am29k-family processors. These are normally used in embedded
AMD Am29050 used in a system running a variant of BSD Unix.
`decstation-*'
- DECstations can support three different personalities: Ultrix, DEC
- OSF/1, and OSF/rose. To configure GCC for these platforms use the
- following configurations:
+ 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:
`decstation-ultrix'
Ultrix configuration.
A port to the AT&T DSP1610 family of processors.
`h8300-*-*'
+ Hitachi H8/300 series of processors.
+
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*-*-*'
- There are two variants of this CPU, called 1.0 and 1.1, which have
- different machine descriptions. You must use the right one for
- your machine. All 7NN machines and 8N7 machines use 1.1, while
- all other 8NN machines use 1.0.
-
- The easiest way to handle this problem is to use `configure hpNNN'
- or `configure hpNNN-hpux', where NNN is the model number of the
- machine. Then `configure' will figure out if the machine is a 1.0
- or 1.1. Use `uname -a' to find out the model number of your
- machine.
+ There are several variants of the HP-PA processor which run a
+ variety of operating systems. GNU CC must be configured to use
+ the correct processor type and operating system, or GNU CC will
+ not function correctly. The easiest way to handle this problem is
+ to *not* specify a target when configuring GNU CC, the `configure'
+ script will try to automatically determine the right processor
+ type and operating system.
`-g' does not work on HP-UX, since that system uses a peculiar
debugging format which GNU CC does not know about. However, `-g'
will work if you also use GAS and GDB in conjunction with GCC. We
highly recommend using GAS for all HP-PA configurations.
- You should be using GAS-2.3 (or later) along with GDB-4.12 (or
+ You should be using GAS-2.6 (or later) along with GDB-4.16 (or
later). These can be retrieved from all the traditional GNU ftp
archive sites.
- Build GAS and install the resulting binary as:
-
- /usr/local/lib/gcc-lib/CONFIGURATION/GCCVERSION/as
-
- where CONFIGURATION is the configuration name (perhaps
- `hpNNN-hpux') and GCCVERSION is the GNU CC version number. Do
- this *before* starting the build process, otherwise you will get
- errors from the HPUX assembler while building `libgcc2.a'. The
- command
-
- make install-dir
-
- will create the necessary directory hierarchy so you can install
- GAS before building GCC.
+ On some versions of HP-UX, you will need to install GNU `sed'.
- To enable debugging, configure GNU CC with the `--with-gnu-as'
- option before building.
+ You will need to be install GAS into a directory before `/bin',
+ `/usr/bin', and `/usr/ccs/bin' in your search path. You should
+ install GAS before you build GNU CC.
- It has been reported that GNU CC produces invalid assembly code for
- 1.1 machines running HP-UX 8.02 when using the HP assembler.
- Typically the errors look like this:
- as: bug.s @line#15 [err#1060]
- Argument 0 or 2 in FARG upper
- - lookahead = ARGW1=FR,RTNVAL=GR
- as: foo.s @line#28 [err#1060]
- Argument 0 or 2 in FARG upper
- - lookahead = ARGW1=FR
-
- You can check the version of HP-UX you are running by executing
- the command `uname -r'. If you are indeed running HP-UX 8.02 on
- a PA and using the HP assembler then configure GCC with
- "hpNNN-hpux8.02".
+ To enable debugging, you must configure GNU CC with the
+ `--with-gnu-as' option before building.
`i370-*-*'
This port is very preliminary and has many known bugs. We hope to
have a higher-quality port for this machine soon.
-`i386-*-linuxoldld'
- Use this configuration to generate a.out binaries on Linux if you
- do not have gas/binutils version 2.5.2 or later installed. This is
- an obsolete configuration.
+`i386-*-linux-gnuoldld'
+ 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 is an obsolete configuration.
-`i386-*-linuxaout'
- Use this configuration to generate a.out binaries on Linux. This
- configuration is being superseded. You must use gas/binutils
- version 2.5.2 or later.
+`i386-*-linux-gnuaout'
+ 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.
-`i386-*-linux'
- Use this configuration to generate ELF binaries on Linux. You must
- use gas/binutils version 2.5.2 or later.
+`i386-*-linux-gnu'
+ Use this configuration to generate ELF binaries on Linux-based GNU
+ systems. You must use gas/binutils version 2.5.2 or later.
`i386-*-sco'
Compilation with RCC is recommended. Also, it may be a good idea
`i386-*-sco3.2v4'
Use this configuration for SCO release 3.2 version 4.
+`i386-*-sco3.2v5*'
+ Use this for the SCO OpenServer Release family including 5.0.0,
+ 5.0.2, 5.0.4, 5.0.5, Internet FastStart 1.0, and Internet
+ FastStart 1.1.
+
+ GNU CC can generate COFF binaries if you specify `-mcoff' or ELF
+ binaries, the default. A full `make bootstrap' is recommended
+ so that an ELF compiler that builds ELF is generated.
+
+ You must have TLS597 from `ftp://ftp.sco.com/TLS' installed for ELF
+ C++ binaries to work correctly on releases before 5.0.4.
+
+ 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 have complex asms) you must configure this
+ package `--with-gnu-as'. To do this, install (cp or symlink)
+ gcc/as to your copy of the GNU assembler. You must use a recent
+ version of GNU binutils; version 2.9.1 seems to work well. If you
+ select this option, you will be unable to build COFF images.
+ Trying to do so will result in non-obvious failures. In general,
+ the "-with-gnu-as" option isn't as well tested as the native
+ assembler.
+
+ *NOTE:* If you are building C++, you must follow the instructions
+ about invoking `make bootstrap' because the native OpenServer
+ compiler may build a `cc1plus' that will not correctly parse many
+ valid C++ programs. You must do a `make bootstrap' if you are
+ building with the native compiler.
+
`i386-*-isc'
It may be a good idea to link with GNU malloc instead of the
malloc that comes with the system.
that comes with the system.
`i386-ibm-aix'
- You need to use GAS version 2.1 or later, and and LD from GNU
- binutils version 2.2 or later.
+ You need to use GAS version 2.1 or later, and LD from GNU binutils
+ version 2.2 or later.
`i386-sequent-bsd'
- Go to the Berkeley universe before compiling. In addition, you
- probably need to create a file named `string.h' containing just
- one line: `#include <strings.h>'.
+ Go to the Berkeley universe before compiling.
`i386-sequent-ptx1*'
- Sequent DYNIX/ptx 1.x.
-
`i386-sequent-ptx2*'
- Sequent DYNIX/ptx 2.x.
+ You must install GNU `sed' before running `configure'.
`i386-sun-sunos4'
You may find that you need another version of GNU CC to begin
Sun systems.
`i[345]86-*-winnt3.5'
- This version requires a GAS that has not let been released. Until
+ This version requires a GAS that has not yet been released. Until
it is, you can get a prebuilt binary version via anonymous ftp from
`cs.washington.edu:pub/gnat' or `cs.nyu.edu:pub/gnat'. You must
also use the Microsoft header files from the Windows NT 3.5 SDK.
You can tell GNU CC 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
- GNU CC will use the installed tools, which produce a.out format
+ GNU CC will use the installed tools, which produce `a.out' format
executables.
+`m32r-*-elf'
+ Mitsubishi M32R processor. This configuration is intended for
+ embedded systems.
+
`m68000-hp-bsd'
HP 9000 series 200 running BSD. Note that the C compiler that
comes with this system cannot compile GNU CC; contact
- `law@cs.utah.edu' to get binaries of GNU CC for bootstrapping.
+ `law@cygnus.com' to get binaries of GNU CC for bootstrapping.
`m68k-altos'
Altos 3068. You must use the GNU assembler, linker and debugger.
Also, you must fix a kernel bug. Details in the file
`README.ALTOS'.
+`m68k-apple-aux'
+ Apple Macintosh running A/UX. 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 GNU C++. You enabled 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 GNU
+ CC. You can find binaries of GNU CC 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.
+
`m68k-att-sysv'
AT&T 3b1, a.k.a. 7300 PC. Special procedures are needed to
compile GNU CC with this machine's standard C compiler, due to
However, the following procedure might work. We are unable to
test it.
- 1. Comment out the `#include "config.h"' line on line 37 of
+ 1. Comment out the `#include "config.h"' line near the start of
`cccp.c' and do `make cpp'. This makes a preliminary version
of GNU cpp.
In addition, if you wish to use gas `--with-gnu-as' 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
+ 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
+ that native HP-UX format, so you must use gas if you wish to use
gdb.
`m68k-sun'
Emacs.
`ns32k-sequent'
- Go to the Berkeley universe before compiling. In addition, you
- probably need to create a file named `string.h' containing just
- one line: `#include <strings.h>'.
+ Go to the Berkeley universe before compiling.
`ns32k-utek'
UTEK ns32000 system ("merlin"). The C compiler that comes with
xlc-1.2.1.8, xlc-1.3.0.0 (distributed with AIX 3.2.5), and
xlc-1.3.0.19. Both xlc-1.2.1.28 and xlc-1.3.0.24 (PTF 432238) are
known to produce working versions of GNU CC, but most other recent
- releases correctly bootstrap GNU CC. Also, releases of AIX prior
- to AIX 3.2.4 include a version of the IBM assembler which does not
- accept debugging directives: assembler updates are available as
- PTFs. Also, if you are using AIX 3.2.5 or greater and the GNU
- assembler, you must have a version modified after October 16th,
- 1995 in order for the GNU C compiler to build. See the file
- `README.RS6000' for more details on of these problems.
+ releases correctly bootstrap GNU CC.
+
+ Release 4.3.0 of AIX and ones prior to AIX 3.2.4 include a version
+ of the IBM assembler which does not accept debugging directives:
+ assembler updates are available as PTFs. Also, if you are using
+ AIX 3.2.5 or greater and the GNU assembler, you must have a
+ version modified after October 16th, 1995 in order for the GNU C
+ compiler to build. See the file `README.RS6000' for more details
+ on any of these problems.
GNU CC does not yet support the 64-bit PowerPC instructions.
prevent the linker from producing a correct library or runnable
executable.
+ By default, AIX 4.1 produces code that can be used on either Power
+ or PowerPC processors.
+
+ You can specify a default version for the `-mcpu='CPU_TYPE switch
+ by using the configure option `--with-cpu-'CPU_TYPE.
+
`powerpc-*-elf'
`powerpc-*-sysv4'
PowerPC system in big endian mode, running System V.4.
- This configuration is currently under development.
+ You can specify a default version for the `-mcpu='CPU_TYPE switch
+ by using the configure option `--with-cpu-'CPU_TYPE.
+
+`powerpc-*-linux-gnu'
+ PowerPC system in big endian mode, running the Linux-based GNU
+ system.
+
+ You can specify a default version for the `-mcpu='CPU_TYPE switch
+ by using the configure option `--with-cpu-'CPU_TYPE.
`powerpc-*-eabiaix'
Embedded PowerPC system in big endian mode with -mcall-aix
- selected as the default. This system is currently under
- development.
+ selected as the default.
+
+ You can specify a default version for the `-mcpu='CPU_TYPE switch
+ by using the configure option `--with-cpu-'CPU_TYPE.
`powerpc-*-eabisim'
Embedded PowerPC system in big endian mode for use in running
- under the PSIM simulator. This system is currently under
- development.
+ under the PSIM simulator.
+
+ You can specify a default version for the `-mcpu='CPU_TYPE switch
+ by using the configure option `--with-cpu-'CPU_TYPE.
`powerpc-*-eabi'
Embedded PowerPC system in big endian mode.
- This configuration is currently under development.
+ You can specify a default version for the `-mcpu='CPU_TYPE switch
+ by using the configure option `--with-cpu-'CPU_TYPE.
`powerpcle-*-elf'
`powerpcle-*-sysv4'
PowerPC system in little endian mode, running System V.4.
- This configuration is currently under development.
+ You can specify a default version for the `-mcpu='CPU_TYPE switch
+ by using the configure option `--with-cpu-'CPU_TYPE.
-`powerpcle-*-sysv4'
- Embedded PowerPC system in little endian mode.
+`powerpcle-*-solaris2*'
+ PowerPC system in little endian mode, running Solaris 2.5.1 or
+ higher.
- This system is currently under development.
+ You can specify a default version for the `-mcpu='CPU_TYPE switch
+ by using the configure option `--with-cpu-'CPU_TYPE. Beta
+ versions of the Sun 4.0 compiler do not seem to be able to build
+ GNU CC correctly. There are also problems with the host assembler
+ and linker that are fixed by using the GNU versions of these tools.
`powerpcle-*-eabisim'
Embedded PowerPC system in little endian mode for use in running
under the PSIM simulator.
- This system is currently under development.
-
`powerpcle-*-eabi'
Embedded PowerPC system in little endian mode.
- This configuration is currently under development.
+ You can specify a default version for the `-mcpu='CPU_TYPE switch
+ by using the configure option `--with-cpu-'CPU_TYPE.
+
+`powerpcle-*-winnt'
+`powerpcle-*-pe'
+ PowerPC system in little endian mode running Windows NT.
+
+ You can specify a default version for the `-mcpu='CPU_TYPE switch
+ by using the configure option `--with-cpu-'CPU_TYPE.
`vax-dec-ultrix'
Don't try compiling with Vax C (`vcc'). It produces incorrect code
You may need to raise the ULIMIT setting to build a C++ compiler,
as the file `cc1plus' is larger than one megabyte.
+\1f
+File: INSTALL, Node: Other Dir, Next: Cross-Compiler, Prev: Configurations, Up: Installation
+
Compilation in a Separate Directory
===================================
must, however, run `configure' again when the configuration files
change, if your system does not support symbolic links.
+\1f
+File: INSTALL, Node: Cross-Compiler, Next: Sun Install, Prev: Other Dir, Up: Installation
+
Building and Installing a Cross-Compiler
========================================
cross-linker as well. You also need header files and libraries suitable
for the target machine that you can install on the host machine.
+* Menu:
+
+* Steps of Cross:: Using a cross-compiler involves several steps
+ that may be carried out on different machines.
+* Configure Cross:: Configuring a cross-compiler.
+* Tools and Libraries:: Where to put the linker and assembler, and the C library.
+* Cross Headers:: Finding and installing header files
+ for a cross-compiler.
+* Cross Runtime:: Supplying arithmetic runtime routines (`libgcc1.a').
+* Build Cross:: Actually compiling the cross-compiler.
+
+\1f
+File: INSTALL, Node: Steps of Cross, Next: Configure Cross, Up: Cross-Compiler
+
Steps of Cross-Compilation
--------------------------
CC. This requires a suitable cross-assembler and cross-linker. For
some targets, the GNU assembler and linker are available.
+\1f
+File: INSTALL, Node: Configure Cross, Next: Tools and Libraries, Prev: Steps of Cross, Up: Cross-Compiler
+
Configuring a Cross-Compiler
----------------------------
./configure --target=m68k-hp-bsd4.3
+\1f
+File: INSTALL, Node: Tools and Libraries, Next: Cross Headers, Prev: Configure Cross, Up: Cross-Compiler
+
Tools and Libraries for a Cross-Compiler
----------------------------------------
If you want to install libraries to use with the cross-compiler,
such as a standard C library, put them in the directory
-`/usr/local/TARGET/lib'; installation of GNU CC copies all all the
-files in that subdirectory into the proper place for GNU CC to find
-them and link with them. Here's an example of copying some libraries
-from a target machine:
+`/usr/local/TARGET/lib'; installation of GNU CC copies all the files in
+that subdirectory into the proper place for GNU CC to find them and
+link with them. Here's an example of copying some libraries from a
+target machine:
ftp TARGET-MACHINE
lcd /usr/local/TARGET/lib
mget *crt*.o
quit
+\1f
+File: INSTALL, Node: Cross Runtime, Next: Build Cross, Prev: Cross Headers, Up: Cross-Compiler
+
`libgcc.a' and Cross-Compilers
------------------------------
`libgcc1.a' in the directory in which you will build the
cross-compiler, before you run `make'.
+\1f
+File: INSTALL, Node: Cross Headers, Next: Cross Runtime, Prev: Tools and Libraries, Up: Cross-Compiler
+
Cross-Compilers and Header Files
--------------------------------
Otherwise, you're on your own in finding header files to use when
cross-compiling.
- When you have found suitable header files, put them in
+ When you have found suitable header files, put them in the directory
`/usr/local/TARGET/include', before building the cross compiler. Then
installation will run fixincludes properly and install the corrected
versions of the header files where the compiler will use them.
quit
tar xf tarfile
+\1f
+File: INSTALL, Node: Build Cross, Prev: Cross Runtime, Up: Cross-Compiler
+
Actually Building the Cross-Compiler
------------------------------------
To install the cross-compiler, use `make install', as usual.
+\1f
+File: INSTALL, Node: Sun Install, Next: VMS Install, Prev: Cross-Compiler, Up: Installation
+
Installing GNU CC on the Sun
============================
- On Solaris (version 2.1), do not use the linker or other tools in
-`/usr/ucb' to build GNU CC. Use `/usr/ccs/bin'.
+ On Solaris, do not use the linker or other tools in `/usr/ucb' to
+build GNU CC. Use `/usr/ccs/bin'.
+
+ If the assembler reports `Error: misaligned data' when bootstrapping,
+you are probably using an obsolete version of the GNU assembler.
+Upgrade to the latest version of GNU `binutils', or use the Solaris
+assembler.
Make sure the environment variable `FLOAT_OPTION' is not set when
you compile `libgcc.a'. If this option were set to `f68881' when
make CC="TERMCAP=x OBJS=x LIBFUNCS=x STAGESTUFF=x cc"
+ SunOS 4.1.3 and 4.1.3_U1 have bugs that can cause intermittent core
+dumps when compiling GNU CC. A common symptom is an internal compiler
+error which does not recur if you run it again. To fix the problem,
+install Sun recommended patch 100726 (for SunOS 4.1.3) or 101508 (for
+SunOS 4.1.3_U1), or upgrade to a later SunOS release.
+
+\1f
+File: INSTALL, Node: VMS Install, Next: Collect2, Prev: Sun Install, Up: Installation
+
Installing GNU CC on VMS
========================
disk:[gcc.gxx_include.] gnu_gxx_include
with the appropriate disk and directory name. If you are going to
- be using libg++, this is where the libg++ install procedure will
- install the libg++ header files.
+ be using a C++ runtime library, this is where its install
+ procedure will install its header files.
2. Obtain the file `gcc-cc1plus.exe', and place this in the same
directory that `gcc-cc1.exe' is kept.
`QSORT_WORKAROUND' is always defined when GNU CC is compiled with
VAX C, to avoid a problem in case `gcclib.olb' is not yet available.
+\1f
+File: INSTALL, Node: Collect2, Next: Header Dirs, Prev: VMS Install, Up: Installation
+
`collect2'
==========
- Many target systems do not have support in the assembler and linker
-for "constructors"--initialization functions to be called before the
-official "start" of `main'. On such systems, GNU CC uses a utility
-called `collect2' to arrange to call these functions at start time.
+ GNU CC uses a utility called `collect2' on nearly all systems to
+arrange to call various initialization functions at start time.
The program `collect2' works by linking the program once and looking
through the linker output file for symbols with particular names
`collect2' searches for the utilities `nm' and `strip' using the
same algorithm as above for `ld'.
+\1f
+File: INSTALL, Node: Header Dirs, Prev: Collect2, Up: Installation
+
Standard Header File Directories
================================
already suitable for ANSI C and GNU CC, nothing special need be done).
`GPLUS_INCLUDE_DIR' means the same thing for native and cross. It
-is where `g++' looks first for header files. `libg++' installs only
-target independent header files in that directory.
+is where `g++' looks first for header files. The C++ library installs
+only target independent header files in that directory.
`LOCAL_INCLUDE_DIR' is used only for a native compiler. It is
normally `/usr/local/include'. GNU CC searches this directory so that
When you build a cross-compiler, `fixincludes' processes any header
files in this directory.
+
+\1f
+Tag Table:
+Node: Installation\7f351
+Node: Configurations\7f26618
+Node: Other Dir\7f65739
+Node: Cross-Compiler\7f67454
+Node: Steps of Cross\7f69284
+Node: Configure Cross\7f70401
+Node: Tools and Libraries\7f71037
+Node: Cross Runtime\7f73475
+Node: Cross Headers\7f77555
+Node: Build Cross\7f79553
+Node: Sun Install\7f81428
+Node: VMS Install\7f83099
+Node: Collect2\7f93028
+Node: Header Dirs\7f95592
+\1f
+End Tag Table
OSDN Git Service
