2976 lines
137 KiB
HTML
2976 lines
137 KiB
HTML
<HTML>
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<!-- Created on March, 17 2001 by texi2html 1.64 -->
|
|
<!--
|
|
Written by: Lionel Cons <Lionel.Cons@cern.ch> (original author)
|
|
Karl Berry <karl@freefriends.org>
|
|
Olaf Bachmann <obachman@mathematik.uni-kl.de>
|
|
and many others.
|
|
Maintained by: Olaf Bachmann <obachman@mathematik.uni-kl.de>
|
|
Send bugs and suggestions to <texi2html@mathematik.uni-kl.de>
|
|
|
|
-->
|
|
<HEAD>
|
|
<TITLE>Using and Porting the GNU Compiler Collection (GCC): Installation</TITLE>
|
|
|
|
<META NAME="description" CONTENT="Using and Porting the GNU Compiler Collection (GCC): Installation">
|
|
<META NAME="keywords" CONTENT="Using and Porting the GNU Compiler Collection (GCC): Installation">
|
|
<META NAME="resource-type" CONTENT="document">
|
|
<META NAME="distribution" CONTENT="global">
|
|
<META NAME="Generator" CONTENT="texi2html 1.64">
|
|
|
|
</HEAD>
|
|
|
|
<BODY LANG="" BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#800080" ALINK="#FF0000">
|
|
|
|
<A NAME="SEC46"></A>
|
|
<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
|
|
<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_2.html#SEC45" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_2.html#SEC45"> < </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC47" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC47"> > </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_4.html#SEC61" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_4.html#SEC61"> << </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc.html#SEC_Top" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc.html#SEC_Top"> Up </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_4.html#SEC61" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_4.html#SEC61"> >> </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc.html#SEC_Top" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc.html#SEC_Top">Top</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_toc.html#SEC_Contents" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_toc.html#SEC_Contents">Contents</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_24.html#SEC261" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_24.html#SEC261">Index</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_abt.html#SEC_About" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_abt.html#SEC_About"> ? </A>]</TD>
|
|
</TR></TABLE>
|
|
<H1> 3. Installing GNU CC </H1>
|
|
<!--docid::SEC46::-->
|
|
<P>
|
|
|
|
<BLOCKQUOTE><TABLE BORDER=0 CELLSPACING=0>
|
|
<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="gcc_3.html#SEC47" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC47">3.1 Files Created by <CODE>configure</CODE></A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP">Files created by running <CODE>configure</CODE>.</TD></TR>
|
|
<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="gcc_3.html#SEC48" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC48">3.2 Configurations Supported by GNU CC</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
|
|
<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="gcc_3.html#SEC49" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC49">3.3 Compilation in a Separate Directory</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP">Compiling in a separate directory (not where the source is).</TD></TR>
|
|
<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="gcc_3.html#SEC50" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC50">3.4 Building and Installing a Cross-Compiler</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP">Building and installing a cross-compiler.</TD></TR>
|
|
<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="gcc_3.html#SEC57" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC57">3.5 Installing GNU CC on the Sun</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP">See below for installation on the Sun.</TD></TR>
|
|
<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="gcc_3.html#SEC58" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC58">3.6 Installing GNU CC on VMS</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP">See below for installation on VMS.</TD></TR>
|
|
<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="gcc_3.html#SEC59" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC59">3.7 <CODE>collect2</CODE></A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP">How <CODE>collect2</CODE> works; how it finds <CODE>ld</CODE>.</TD></TR>
|
|
<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="gcc_3.html#SEC60" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC60">3.8 Standard Header File Directories</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP">Understanding the standard header file directories.</TD></TR>
|
|
</TABLE></BLOCKQUOTE>
|
|
<P>
|
|
|
|
Here is the procedure for installing GNU CC on a GNU or Unix system.
|
|
See <A HREF="gcc_3.html#SEC58" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC58">3.6 Installing GNU CC on VMS</A>, for VMS systems. In this section we assume you
|
|
compile in the same directory that contains the source files; see
|
|
<A HREF="gcc_3.html#SEC49" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC49">3.3 Compilation in a Separate Directory</A>, to find out how to compile in a separate directory on
|
|
Unix systems.
|
|
</P><P>
|
|
|
|
You cannot install GNU C 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.
|
|
</P><P>
|
|
|
|
<OL>
|
|
<LI>
|
|
If you have built GNU CC previously in the same directory for a
|
|
different target machine, do <SAMP>`make distclean'</SAMP> to delete all files
|
|
that might be invalid. One of the files this deletes is
|
|
<TT>`Makefile'</TT>; if <SAMP>`make distclean'</SAMP> complains that <TT>`Makefile'</TT>
|
|
does not exist, it probably means that the directory is already suitably
|
|
clean.
|
|
<P>
|
|
|
|
<LI>
|
|
On a System V release 4 system, make sure <TT>`/usr/bin'</TT> precedes
|
|
<TT>`/usr/ucb'</TT> in <CODE>PATH</CODE>. The <CODE>cc</CODE> command in
|
|
<TT>`/usr/ucb'</TT> uses libraries which have bugs.
|
|
<P>
|
|
|
|
<A NAME="IDX234"></A>
|
|
<A NAME="IDX235"></A>
|
|
<LI>
|
|
Make sure the Bison parser generator is installed. (This is
|
|
unnecessary if the Bison output files <TT>`c-parse.c'</TT> and
|
|
<TT>`cexp.c'</TT> are more recent than <TT>`c-parse.y'</TT> and <TT>`cexp.y'</TT>
|
|
and you do not plan to change the <SAMP>`.y'</SAMP> files.)
|
|
<P>
|
|
|
|
Bison versions older than Sept 8, 1988 will produce incorrect output
|
|
for <TT>`c-parse.c'</TT>.
|
|
</P><P>
|
|
|
|
<LI>
|
|
If you have chosen a configuration for GNU CC which requires other GNU
|
|
tools (such as GAS or the GNU linker) instead of the standard system
|
|
tools, install the required tools in the build directory under the names
|
|
<TT>`as'</TT>, <TT>`ld'</TT> or whatever is appropriate. This will enable the
|
|
compiler to find the proper tools for compilation of the program
|
|
<TT>`enquire'</TT>.
|
|
<P>
|
|
|
|
Alternatively, you can do subsequent compilation using a value of the
|
|
<CODE>PATH</CODE> environment variable such that the necessary GNU tools come
|
|
before the standard system tools.
|
|
</P><P>
|
|
|
|
<LI>
|
|
Specify the host, build and target machine configurations. You do this
|
|
when you run the <TT>`configure'</TT> script.
|
|
<P>
|
|
|
|
The <EM>build</EM> machine is the system which you are using, the
|
|
<EM>host</EM> machine is the system where you want to run the resulting
|
|
compiler (normally the build machine), and the <EM>target</EM> machine is
|
|
the system for which you want the compiler to generate code.
|
|
</P><P>
|
|
|
|
If you are building a compiler to produce code for the machine it runs
|
|
on (a native compiler), you normally do not need to specify any operands
|
|
to <TT>`configure'</TT>; it will try to guess the type of machine you are on
|
|
and use that as the build, host and target machines. So you don't need
|
|
to specify a configuration when building a native compiler unless
|
|
<TT>`configure'</TT> cannot figure out what your configuration is or guesses
|
|
wrong.
|
|
</P><P>
|
|
|
|
In those cases, specify the build machine's <EM>configuration name</EM>
|
|
with the <SAMP>`--host'</SAMP> option; the host and target will default to be
|
|
the same as the host machine. (If you are building a cross-compiler,
|
|
see <A HREF="gcc_3.html#SEC50" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC50">3.4 Building and Installing a Cross-Compiler</A>.)
|
|
</P><P>
|
|
|
|
Here is an example:
|
|
</P><P>
|
|
|
|
<TABLE><tr><td> </td><td class=smallexample><FONT SIZE=-1><pre>./configure --host=sparc-sun-sunos4.1
|
|
</FONT></pre></td></tr></table></P><P>
|
|
|
|
A configuration name may be canonical or it may be more or less
|
|
abbreviated.
|
|
</P><P>
|
|
|
|
A canonical configuration name has three parts, separated by dashes.
|
|
It looks like this: <SAMP>`<VAR>cpu</VAR>-<VAR>company</VAR>-<VAR>system</VAR>'</SAMP>.
|
|
(The three parts may themselves contain dashes; <TT>`configure'</TT>
|
|
can figure out which dashes serve which purpose.) For example,
|
|
<SAMP>`m68k-sun-sunos4.1'</SAMP> specifies a Sun 3.
|
|
</P><P>
|
|
|
|
You can also replace parts of the configuration by nicknames or aliases.
|
|
For example, <SAMP>`sun3'</SAMP> stands for <SAMP>`m68k-sun'</SAMP>, so
|
|
<SAMP>`sun3-sunos4.1'</SAMP> is another way to specify a Sun 3. You can also
|
|
use simply <SAMP>`sun3-sunos'</SAMP>, since the version of SunOS is assumed by
|
|
default to be version 4.
|
|
</P><P>
|
|
|
|
You can specify a version number after any of the system types, and some
|
|
of the CPU types. In most cases, the version is irrelevant, and will be
|
|
ignored. So you might as well specify the version if you know it.
|
|
</P><P>
|
|
|
|
See <A HREF="gcc_3.html#SEC48" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC48">3.2 Configurations Supported by GNU CC</A>, for a list of supported configuration names and
|
|
notes on many of the configurations. You should check the notes in that
|
|
section before proceeding any further with the installation of GNU CC.
|
|
</P><P>
|
|
|
|
<LI>
|
|
When running <CODE>configure</CODE>, you may also need to specify certain
|
|
additional options that describe variant hardware and software
|
|
configurations. These are <SAMP>`--with-gnu-as'</SAMP>, <SAMP>`--with-gnu-ld'</SAMP>,
|
|
<SAMP>`--with-stabs'</SAMP> and <SAMP>`--nfp'</SAMP>.
|
|
<P>
|
|
|
|
<DL COMPACT>
|
|
<DT><SAMP>`--with-gnu-as'</SAMP>
|
|
<DD>If you will use GNU CC with the GNU assembler (GAS), you should declare
|
|
this by using the <SAMP>`--with-gnu-as'</SAMP> option when you run
|
|
<TT>`configure'</TT>.
|
|
<P>
|
|
|
|
Using this option does not install GAS. It only modifies the output of
|
|
GNU CC to work with GAS. Building and installing GAS is up to you.
|
|
</P><P>
|
|
|
|
Conversely, if you <EM>do not</EM> wish to use GAS and do not specify
|
|
<SAMP>`--with-gnu-as'</SAMP> when building GNU CC, it is up to you to make sure
|
|
that GAS is not installed. GNU CC searches for a program named
|
|
<CODE>as</CODE> in various directories; if the program it finds is GAS, then
|
|
it runs GAS. If you are not sure where GNU CC finds the assembler it is
|
|
using, try specifying <SAMP>`-v'</SAMP> when you run it.
|
|
</P><P>
|
|
|
|
The systems where it makes a difference whether you use GAS are<BR>
|
|
<SAMP>`hppa1.0-<VAR>any</VAR>-<VAR>any</VAR>'</SAMP>, <SAMP>`hppa1.1-<VAR>any</VAR>-<VAR>any</VAR>'</SAMP>,
|
|
<SAMP>`i386-<VAR>any</VAR>-sysv'</SAMP>, <SAMP>`i386-<VAR>any</VAR>-isc'</SAMP>,<BR>
|
|
<SAMP>`i860-<VAR>any</VAR>-bsd'</SAMP>, <SAMP>`m68k-bull-sysv'</SAMP>,<BR>
|
|
<SAMP>`m68k-hp-hpux'</SAMP>, <SAMP>`m68k-sony-bsd'</SAMP>,<BR>
|
|
<SAMP>`m68k-altos-sysv'</SAMP>, <SAMP>`m68000-hp-hpux'</SAMP>,<BR>
|
|
<SAMP>`m68000-att-sysv'</SAMP>, <SAMP>`<VAR>any</VAR>-lynx-lynxos'</SAMP>,
|
|
and <SAMP>`mips-<VAR>any</VAR>'</SAMP>).
|
|
On any other system, <SAMP>`--with-gnu-as'</SAMP> has no effect.
|
|
</P><P>
|
|
|
|
On the systems listed above (except for the HP-PA, for ISC on the
|
|
386, and for <SAMP>`mips-sgi-irix5.*'</SAMP>), if you use GAS, you should also
|
|
use the GNU linker (and specify <SAMP>`--with-gnu-ld'</SAMP>).
|
|
</P><P>
|
|
|
|
<DT><SAMP>`--with-gnu-ld'</SAMP>
|
|
<DD>Specify the option <SAMP>`--with-gnu-ld'</SAMP> if you plan to use the GNU
|
|
linker with GNU CC.
|
|
<P>
|
|
|
|
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.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`--with-stabs'</SAMP>
|
|
<DD>On MIPS based systems and on Alphas, you must specify whether you want
|
|
GNU CC to create the normal ECOFF debugging format, or to use BSD-style
|
|
stabs passed through the ECOFF symbol table. The normal ECOFF debug
|
|
format cannot fully handle languages other than C. BSD stabs format can
|
|
handle other languages, but it only works with the GNU debugger GDB.
|
|
<P>
|
|
|
|
Normally, GNU CC uses the ECOFF debugging format by default; if you
|
|
prefer BSD stabs, specify <SAMP>`--with-stabs'</SAMP> when you configure GNU
|
|
CC.
|
|
</P><P>
|
|
|
|
No matter which default you choose when you configure GNU CC, the user
|
|
can use the <SAMP>`-gcoff'</SAMP> and <SAMP>`-gstabs+'</SAMP> options to specify explicitly
|
|
the debug format for a particular compilation.
|
|
</P><P>
|
|
|
|
<SAMP>`--with-stabs'</SAMP> is meaningful on the ISC system on the 386, also, if
|
|
<SAMP>`--with-gas'</SAMP> is used. It selects use of stabs debugging
|
|
information embedded in COFF output. This kind of debugging information
|
|
supports C++ well; ordinary COFF debugging information does not.
|
|
</P><P>
|
|
|
|
<SAMP>`--with-stabs'</SAMP> is also meaningful on 386 systems running SVR4. It
|
|
selects use of stabs debugging information embedded in ELF output. The
|
|
C++ compiler currently (2.6.0) does not support the DWARF debugging
|
|
information normally used on 386 SVR4 platforms; stabs provide a
|
|
workable alternative. This requires gas and gdb, as the normal SVR4
|
|
tools can not generate or interpret stabs.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`--nfp'</SAMP>
|
|
<DD>On certain systems, you must specify whether the machine has a floating
|
|
point unit. These systems include <SAMP>`m68k-sun-sunos<VAR>n</VAR>'</SAMP> and
|
|
<SAMP>`m68k-isi-bsd'</SAMP>. On any other system, <SAMP>`--nfp'</SAMP> currently has no
|
|
effect, though perhaps there are other systems where it could usefully
|
|
make a difference.
|
|
<P>
|
|
|
|
<A NAME="IDX236"></A>
|
|
<A NAME="IDX237"></A>
|
|
<DT><SAMP>`--enable-haifa'</SAMP>
|
|
<DD><DT><SAMP>`--disable-haifa'</SAMP>
|
|
<DD>Use <SAMP>`--enable-haifa'</SAMP> 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
|
|
<SAMP>`--disable-haifa'</SAMP> to disable it in these cases. <CODE>configure</CODE>
|
|
will print out whether the Haifa scheduler is enabled when it is run.
|
|
<P>
|
|
|
|
<A NAME="IDX238"></A>
|
|
<A NAME="IDX239"></A>
|
|
<DT><SAMP>`--enable-threads=<VAR>type</VAR>'</SAMP>
|
|
<DD>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 <VAR>type</VAR>, probably
|
|
<SAMP>`posix'</SAMP>. The possibilities for <VAR>type</VAR> are <SAMP>`single'</SAMP>,
|
|
<SAMP>`posix'</SAMP>, <SAMP>`win32'</SAMP>, <SAMP>`solaris'</SAMP>, <SAMP>`irix'</SAMP> and <SAMP>`mach'</SAMP>.
|
|
<P>
|
|
|
|
<A NAME="IDX240"></A>
|
|
<DT><SAMP>`--enable-checking'</SAMP>
|
|
<DD>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.
|
|
<P>
|
|
|
|
The <TT>`configure'</TT> 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 named
|
|
<TT>`cp'</TT>. <TT>`configure'</TT> inserts rules into <TT>`Makefile'</TT> to build
|
|
all of those compilers.
|
|
</P><P>
|
|
|
|
Here we spell out what files will be set up by <CODE>configure</CODE>. Normally
|
|
you need not be concerned with these files.
|
|
</P><P>
|
|
|
|
<UL>
|
|
<LI>
|
|
A file named <TT>`config.h'</TT> is created that contains a <SAMP>`#include'</SAMP>
|
|
of the top-level config file for the machine you will run the compiler
|
|
on (see section <A HREF="gcc_18.html#SEC251" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_18.html#SEC251">18. The Configuration File</A>). This file is responsible for defining information
|
|
about the host machine. It includes <TT>`tm.h'</TT>.
|
|
<P>
|
|
|
|
The top-level config file is located in the subdirectory <TT>`config'</TT>.
|
|
Its name is always <TT>`xm-<VAR>something</VAR>.h'</TT>; usually
|
|
<TT>`xm-<VAR>machine</VAR>.h'</TT>, but there are some exceptions.
|
|
</P><P>
|
|
|
|
If your system does not support symbolic links, you might want to
|
|
set up <TT>`config.h'</TT> to contain a <SAMP>`#include'</SAMP> command which
|
|
refers to the appropriate file.
|
|
</P><P>
|
|
|
|
<LI>
|
|
A file named <TT>`tconfig.h'</TT> is created which includes the top-level config
|
|
file for your target machine. This is used for compiling certain
|
|
programs to run on that machine.
|
|
<P>
|
|
|
|
<LI>
|
|
A file named <TT>`tm.h'</TT> is created which includes the
|
|
machine-description macro file for your target machine. It should be in
|
|
the subdirectory <TT>`config'</TT> and its name is often
|
|
<TT>`<VAR>machine</VAR>.h'</TT>.
|
|
</UL>
|
|
<P>
|
|
|
|
<A NAME="IDX241"></A>
|
|
<A NAME="IDX242"></A>
|
|
<DT><SAMP>`--enable-nls'</SAMP>
|
|
<DD><DT><SAMP>`--disable-nls'</SAMP>
|
|
<DD>The <SAMP>`--enable-nls'</SAMP> option enables Native Language Support (NLS),
|
|
which lets GCC output diagnostics in languages other than American
|
|
English. No translations are available yet, so the main users of this
|
|
option now are those translating GCC's diagnostics who want to test
|
|
their work. Once translations become available, Native Language Support
|
|
will become enabled by default. The <SAMP>`--disable-nls'</SAMP> option
|
|
disables NLS.
|
|
<P>
|
|
|
|
<A NAME="IDX243"></A>
|
|
<DT><SAMP>`--with-included-gettext'</SAMP>
|
|
<DD>If NLS is enabled, the GCC build procedure normally attempts to use the
|
|
host's <CODE>gettext</CODE> libraries, and falls back on GCC's copy of the GNU
|
|
<CODE>gettext</CODE> library only if the host libraries do not suffice. The
|
|
<SAMP>`--with-included-gettext'</SAMP> option causes the build procedure to
|
|
prefer its copy of GNU <CODE>gettext</CODE>.
|
|
<P>
|
|
|
|
<A NAME="IDX244"></A>
|
|
<DT><SAMP>`--with-catgets'</SAMP>
|
|
<DD>If NLS is enabled, and if the host lacks <CODE>gettext</CODE> but has the
|
|
inferior <CODE>catgets</CODE> interface, the GCC build procedure normally
|
|
ignores <CODE>catgets</CODE> and instead uses GCC's copy of the GNU
|
|
<CODE>gettext</CODE> library. The <SAMP>`--with-catgets'</SAMP> option causes the
|
|
build procedure to use the host's <CODE>catgets</CODE> in this situation.
|
|
</DL>
|
|
<P>
|
|
|
|
<LI>
|
|
In certain cases, you should specify certain other options when you run
|
|
<CODE>configure</CODE>.
|
|
<P>
|
|
|
|
<UL>
|
|
<LI>
|
|
The standard directory for installing GNU CC is <TT>`/usr/local/lib'</TT>.
|
|
If you want to install its files somewhere else, specify
|
|
<SAMP>`--prefix=<VAR>dir</VAR>'</SAMP> when you run <TT>`configure'</TT>. Here <VAR>dir</VAR>
|
|
is a directory name to use instead of <TT>`/usr/local'</TT> for all purposes
|
|
with one exception: the directory <TT>`/usr/local/include'</TT> is searched
|
|
for header files no matter where you install the compiler. To override
|
|
this name, use the <CODE>--with-local-prefix</CODE> option below. The directory
|
|
you specify need not exist, but its parent directory must exist.
|
|
<P>
|
|
|
|
<LI>
|
|
Specify <SAMP>`--with-local-prefix=<VAR>dir</VAR>'</SAMP> if you want the compiler to
|
|
search directory <TT>`<VAR>dir</VAR>/include'</TT> for locally installed header
|
|
files <EM>instead</EM> of <TT>`/usr/local/include'</TT>.
|
|
<P>
|
|
|
|
You should specify <SAMP>`--with-local-prefix'</SAMP> <STRONG>only</STRONG> if your site has
|
|
a different convention (not <TT>`/usr/local'</TT>) for where to put
|
|
site-specific files.
|
|
</P><P>
|
|
|
|
The default value for <SAMP>`--with-local-prefix'</SAMP> is <TT>`/usr/local'</TT>
|
|
regardless of the value of <SAMP>`--prefix'</SAMP>. Specifying <SAMP>`--prefix'</SAMP>
|
|
has no effect on which directory GNU CC searches for local header files.
|
|
This may seem counterintuitive, but actually it is logical.
|
|
</P><P>
|
|
|
|
The purpose of <SAMP>`--prefix'</SAMP> is to specify where to <EM>install GNU
|
|
CC</EM>. The local header files in <TT>`/usr/local/include'</TT>---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 <SAMP>`--prefix'</SAMP> value.)
|
|
</P><P>
|
|
|
|
<STRONG>Do not</STRONG> specify <TT>`/usr'</TT> as the <SAMP>`--with-local-prefix'</SAMP>! The
|
|
directory you use for <SAMP>`--with-local-prefix'</SAMP> <STRONG>must not</STRONG> 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 <CODE>fixincludes</CODE> script.
|
|
</P><P>
|
|
|
|
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.
|
|
</UL>
|
|
<P>
|
|
|
|
<LI>
|
|
Build the compiler. Just type <SAMP>`make LANGUAGES=c'</SAMP> in the compiler
|
|
directory.
|
|
<P>
|
|
|
|
<SAMP>`LANGUAGES=c'</SAMP> specifies that only the C compiler should be
|
|
compiled. The makefile normally builds compilers for all the supported
|
|
languages; currently, C, C++ and Objective C. However, C is the only
|
|
language that is sure to work when you build with other non-GNU C
|
|
compilers. In addition, building anything but C at this stage is a
|
|
waste of time.
|
|
</P><P>
|
|
|
|
In general, you can specify the languages to build by typing the
|
|
argument <SAMP>`LANGUAGES="<VAR>list</VAR>"'</SAMP>, where <VAR>list</VAR> is one or more
|
|
words from the list <SAMP>`c'</SAMP>, <SAMP>`c++'</SAMP>, and <SAMP>`objective-c'</SAMP>. If
|
|
you have any additional GNU compilers as subdirectories of the GNU CC
|
|
source directory, you may also specify their names in this list.
|
|
</P><P>
|
|
|
|
Ignore any warnings you may see about "statement not reached" in
|
|
<TT>`insn-emit.c'</TT>; they are normal. Also, warnings about "unknown
|
|
escape sequence" are normal in <TT>`genopinit.c'</TT> and perhaps some
|
|
other files. Likewise, you should ignore warnings about "constant is
|
|
so large that it is unsigned" in <TT>`insn-emit.c'</TT> and
|
|
<TT>`insn-recog.c'</TT>, a warning about a comparison always being zero
|
|
in <TT>`enquire.o'</TT>, and warnings about shift counts exceeding type
|
|
widths in <TT>`cexp.y'</TT>. Any other compilation errors may represent bugs in
|
|
the port to your machine or operating system, and
|
|
should be investigated and reported (see section <A HREF="gcc_8.html#SEC135" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_8.html#SEC135">8. Reporting Bugs</A>).
|
|
</P><P>
|
|
|
|
Some compilers fail to compile GNU CC because they have bugs or
|
|
limitations. For example, the Microsoft compiler is said to run out of
|
|
macro space. Some Ultrix compilers run out of expression space; then
|
|
you need to break up the statement where the problem happens.
|
|
</P><P>
|
|
|
|
<LI>
|
|
If you are building a cross-compiler, stop here. See section <A HREF="gcc_3.html#SEC50" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC50">3.4 Building and Installing a Cross-Compiler</A>.
|
|
<P>
|
|
|
|
<A NAME="IDX245"></A>
|
|
<LI>
|
|
Move the first-stage object files and executables into a subdirectory
|
|
with this command:
|
|
<P>
|
|
|
|
<TABLE><tr><td> </td><td class=smallexample><FONT SIZE=-1><pre>make stage1
|
|
</FONT></pre></td></tr></table></P><P>
|
|
|
|
The files are moved into a subdirectory named <TT>`stage1'</TT>.
|
|
Once installation is complete, you may wish to delete these files
|
|
with <CODE>rm -r stage1</CODE>.
|
|
</P><P>
|
|
|
|
<LI>
|
|
If you have chosen a configuration for GNU CC which requires other GNU
|
|
tools (such as GAS or the GNU linker) instead of the standard system
|
|
tools, install the required tools in the <TT>`stage1'</TT> subdirectory
|
|
under the names <TT>`as'</TT>, <TT>`ld'</TT> or whatever is appropriate. This
|
|
will enable the stage 1 compiler to find the proper tools in the
|
|
following stage.
|
|
<P>
|
|
|
|
Alternatively, you can do subsequent compilation using a value of the
|
|
<CODE>PATH</CODE> environment variable such that the necessary GNU tools come
|
|
before the standard system tools.
|
|
</P><P>
|
|
|
|
<LI>
|
|
Recompile the compiler with itself, with this command:
|
|
<P>
|
|
|
|
<TABLE><tr><td> </td><td class=smallexample><FONT SIZE=-1><pre>make CC="stage1/xgcc -Bstage1/" CFLAGS="-g -O2"
|
|
</FONT></pre></td></tr></table></P><P>
|
|
|
|
This is called making the stage 2 compiler.
|
|
</P><P>
|
|
|
|
The command shown above builds compilers for all the supported
|
|
languages. If you don't want them all, you can specify the languages to
|
|
build by typing the argument <SAMP>`LANGUAGES="<VAR>list</VAR>"'</SAMP>. <VAR>list</VAR>
|
|
should contain one or more words from the list <SAMP>`c'</SAMP>, <SAMP>`c++'</SAMP>,
|
|
<SAMP>`objective-c'</SAMP>, and <SAMP>`proto'</SAMP>. Separate the words with spaces.
|
|
<SAMP>`proto'</SAMP> stands for the programs <CODE>protoize</CODE> and
|
|
<CODE>unprotoize</CODE>; they are not a separate language, but you use
|
|
<CODE>LANGUAGES</CODE> to enable or disable their installation.
|
|
</P><P>
|
|
|
|
If you are going to build the stage 3 compiler, then you might want to
|
|
build only the C language in stage 2.
|
|
</P><P>
|
|
|
|
Once you have built the stage 2 compiler, if you are short of disk
|
|
space, you can delete the subdirectory <TT>`stage1'</TT>.
|
|
</P><P>
|
|
|
|
On a 68000 or 68020 system lacking floating point hardware,
|
|
unless you have selected a <TT>`tm.h'</TT> file that expects by default
|
|
that there is no such hardware, do this instead:
|
|
</P><P>
|
|
|
|
<TABLE><tr><td> </td><td class=smallexample><FONT SIZE=-1><pre>make CC="stage1/xgcc -Bstage1/" CFLAGS="-g -O2 -msoft-float"
|
|
</FONT></pre></td></tr></table></P><P>
|
|
|
|
<LI>
|
|
If you wish to test the compiler by compiling it with itself one more
|
|
time, install any other necessary GNU tools (such as GAS or the GNU
|
|
linker) in the <TT>`stage2'</TT> subdirectory as you did in the
|
|
<TT>`stage1'</TT> subdirectory, then do this:
|
|
<P>
|
|
|
|
<TABLE><tr><td> </td><td class=smallexample><FONT SIZE=-1><pre>make stage2
|
|
make CC="stage2/xgcc -Bstage2/" CFLAGS="-g -O2"
|
|
</FONT></pre></td></tr></table></P><P>
|
|
|
|
This is called making the stage 3 compiler. Aside from the <SAMP>`-B'</SAMP>
|
|
option, the compiler options should be the same as when you made the
|
|
stage 2 compiler. But the <CODE>LANGUAGES</CODE> option need not be the
|
|
same. The command shown above builds compilers for all the supported
|
|
languages; if you don't want them all, you can specify the languages to
|
|
build by typing the argument <SAMP>`LANGUAGES="<VAR>list</VAR>"'</SAMP>, as described
|
|
above.
|
|
</P><P>
|
|
|
|
If you do not have to install any additional GNU tools, you may use the
|
|
command
|
|
</P><P>
|
|
|
|
<TABLE><tr><td> </td><td class=smallexample><FONT SIZE=-1><pre>make bootstrap LANGUAGES=<VAR>language-list</VAR> BOOT_CFLAGS=<VAR>option-list</VAR>
|
|
</FONT></pre></td></tr></table></P><P>
|
|
|
|
instead of making <TT>`stage1'</TT>, <TT>`stage2'</TT>, and performing
|
|
the two compiler builds.
|
|
</P><P>
|
|
|
|
<LI>
|
|
Compare the latest object files with the stage 2 object files--they
|
|
ought to be identical, aside from time stamps (if any).
|
|
<P>
|
|
|
|
On some systems, meaningful comparison of object files is impossible;
|
|
they always appear "different." This is currently true on Solaris and
|
|
some systems that use ELF object file format. On some versions of Irix
|
|
on SGI machines and DEC Unix (OSF/1) on Alpha systems, you will not be
|
|
able to compare the files without specifying <TT>`-save-temps'</TT>; see the
|
|
description of individual systems above to see if you get comparison
|
|
failures. You may have similar problems on other systems.
|
|
</P><P>
|
|
|
|
Use this command to compare the files:
|
|
</P><P>
|
|
|
|
<TABLE><tr><td> </td><td class=smallexample><FONT SIZE=-1><pre>make compare
|
|
</FONT></pre></td></tr></table></P><P>
|
|
|
|
This will mention any object files that differ between stage 2 and stage
|
|
3. Any difference, no matter how innocuous, indicates that the stage 2
|
|
compiler has compiled GNU CC incorrectly, and is therefore a potentially
|
|
serious bug which you should investigate and report (see section <A HREF="gcc_8.html#SEC135" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_8.html#SEC135">8. Reporting Bugs</A>).
|
|
</P><P>
|
|
|
|
If your system does not put time stamps in the object files, then this
|
|
is a faster way to compare them (using the Bourne shell):
|
|
</P><P>
|
|
|
|
<TABLE><tr><td> </td><td class=smallexample><FONT SIZE=-1><pre>for file in *.o; do
|
|
cmp $file stage2/$file
|
|
done
|
|
</FONT></pre></td></tr></table></P><P>
|
|
|
|
If you have built the compiler with the <SAMP>`-mno-mips-tfile'</SAMP> option on
|
|
MIPS machines, you will not be able to compare the files.
|
|
</P><P>
|
|
|
|
<LI>
|
|
Install the compiler driver, the compiler's passes and run-time support
|
|
with <SAMP>`make install'</SAMP>. Use the same value for <CODE>CC</CODE>,
|
|
<CODE>CFLAGS</CODE> and <CODE>LANGUAGES</CODE> that you used when compiling the
|
|
files that are being installed. One reason this is necessary is that
|
|
some versions of Make have bugs and recompile files gratuitously when
|
|
you do this step. If you use the same variable values, those files will
|
|
be recompiled properly.
|
|
<P>
|
|
|
|
For example, if you have built the stage 2 compiler, you can use the
|
|
following command:
|
|
</P><P>
|
|
|
|
<TABLE><tr><td> </td><td class=smallexample><FONT SIZE=-1><pre>make install CC="stage2/xgcc -Bstage2/" CFLAGS="-g -O" LANGUAGES="<VAR>list</VAR>"
|
|
</FONT></pre></td></tr></table></P><P>
|
|
|
|
This copies the files <TT>`cc1'</TT>, <TT>`cpp'</TT> and <TT>`libgcc.a'</TT> to
|
|
files <TT>`cc1'</TT>, <TT>`cpp'</TT> and <TT>`libgcc.a'</TT> in the directory
|
|
<TT>`/usr/local/lib/gcc-lib/<VAR>target</VAR>/<VAR>version</VAR>'</TT>, which is where
|
|
the compiler driver program looks for them. Here <VAR>target</VAR> is the
|
|
canonicalized form of target machine type specified when you ran
|
|
<TT>`configure'</TT>, and <VAR>version</VAR> 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., <TT>`cc1plus'</TT> for C++) to the same directory.
|
|
</P><P>
|
|
|
|
This also copies the driver program <TT>`xgcc'</TT> into
|
|
<TT>`/usr/local/bin/gcc'</TT>, so that it appears in typical execution
|
|
search paths. It also copies <TT>`gcc.1'</TT> into
|
|
<TT>`/usr/local/man/man1'</TT> and info pages into <TT>`/usr/local/info'</TT>.
|
|
</P><P>
|
|
|
|
On some systems, this command causes recompilation of some files. This
|
|
is usually due to bugs in <CODE>make</CODE>. You should either ignore this
|
|
problem, or use GNU Make.
|
|
</P><P>
|
|
|
|
<A NAME="IDX246"></A>
|
|
<STRONG>Warning: there is a bug in <CODE>alloca</CODE> in the Sun library. To
|
|
avoid this bug, be sure to install the executables of GNU CC that were
|
|
compiled by GNU CC. (That is, the executables from stage 2 or 3, not
|
|
stage 1.) They use <CODE>alloca</CODE> as a built-in function and never the
|
|
one in the library.</STRONG>
|
|
</P><P>
|
|
|
|
(It is usually better to install GNU CC executables from stage 2 or 3,
|
|
since they usually run faster than the ones compiled with some other
|
|
compiler.)
|
|
</P><P>
|
|
|
|
<LI>
|
|
<A NAME="IDX247"></A>
|
|
<A NAME="IDX248"></A>
|
|
If you're going to use C++, you need to install the C++ runtime library.
|
|
This includes all I/O functionality, special class libraries, etc.
|
|
<P>
|
|
|
|
The standard C++ runtime library for GNU CC is called <SAMP>`libstdc++'</SAMP>.
|
|
An obsolescent library <SAMP>`libg++'</SAMP> 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 <SAMP>`libg++'</SAMP> then you probably don't
|
|
need it.
|
|
</P><P>
|
|
|
|
Here's one way to build and install <SAMP>`libstdc++'</SAMP> for GNU CC:
|
|
</P><P>
|
|
|
|
<UL>
|
|
<LI>
|
|
Build and install GNU CC, so that invoking <SAMP>`gcc'</SAMP> obtains the GNU CC
|
|
that was just built.
|
|
<P>
|
|
|
|
<LI>
|
|
Obtain a copy of a compatible <SAMP>`libstdc++'</SAMP> distribution. For
|
|
example, the <SAMP>`libstdc++-2.8.0.tar.gz'</SAMP> distribution should be
|
|
compatible with GCC 2.8.0. GCC distributors normally distribute
|
|
<SAMP>`libstdc++'</SAMP> as well.
|
|
<P>
|
|
|
|
<LI>
|
|
Set the <SAMP>`CXX'</SAMP> environment variable to <SAMP>`gcc'</SAMP> while running the
|
|
<SAMP>`libstdc++'</SAMP> distribution's <TT>`configure'</TT> command. Use the same
|
|
<TT>`configure'</TT> options that you used when you invoked GCC's
|
|
<TT>`configure'</TT> command.
|
|
<P>
|
|
|
|
<LI>
|
|
Invoke <SAMP>`make'</SAMP> to build the C++ runtime.
|
|
<P>
|
|
|
|
<LI>
|
|
Invoke <SAMP>`make install'</SAMP> to install the C++ runtime.
|
|
<P>
|
|
|
|
</UL>
|
|
<P>
|
|
|
|
To summarize, after building and installing GNU CC, invoke the following
|
|
shell commands in the topmost directory of the C++ library distribution.
|
|
For <VAR>configure-options</VAR>, use the same options that
|
|
you used to configure GNU CC.
|
|
</P><P>
|
|
|
|
<TABLE><tr><td> </td><td class=example><pre>$ CXX=gcc ./configure <VAR>configure-options</VAR>
|
|
$ make
|
|
$ make install
|
|
</pre></td></tr></table></P><P>
|
|
|
|
<LI>
|
|
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 <TT>`objc'</TT>. 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. See section <A HREF="gcc_3.html#SEC55" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC55">Cross-Compilers and Header Files</A>, for
|
|
discussion about header files issues for cross-compilation.
|
|
<P>
|
|
|
|
When you run <TT>`configure'</TT>, 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
|
|
<VAR>OBJC_THREAD_FILE</VAR> makefile variable on the command line when you
|
|
run make, for example:
|
|
</P><P>
|
|
|
|
<TABLE><tr><td> </td><td class=smallexample><FONT SIZE=-1><pre>make CC="stage2/xgcc -Bstage2/" CFLAGS="-g -O2" OBJC_THREAD_FILE=thr-single
|
|
</FONT></pre></td></tr></table></P><P>
|
|
|
|
Below is a list of the currently available back-ends.
|
|
</P><P>
|
|
|
|
<UL>
|
|
<LI>thr-single
|
|
Disable thread support, should work for all platforms.
|
|
<LI>thr-decosf1
|
|
DEC OSF/1 thread support.
|
|
<LI>thr-irix
|
|
SGI IRIX thread support.
|
|
<LI>thr-mach
|
|
Generic MACH thread support, known to work on NEXTSTEP.
|
|
<LI>thr-os2
|
|
IBM OS/2 thread support.
|
|
<LI>thr-posix
|
|
Generix POSIX thread support.
|
|
<LI>thr-pthreads
|
|
PCThreads on Linux-based GNU systems.
|
|
<LI>thr-solaris
|
|
SUN Solaris thread support.
|
|
<LI>thr-win32
|
|
Microsoft Win32 API thread support.
|
|
</UL>
|
|
</OL>
|
|
<P>
|
|
|
|
<A NAME="Configuration Files"></A>
|
|
<HR SIZE="6">
|
|
<A NAME="SEC47"></A>
|
|
<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
|
|
<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC46" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC46"> < </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC48" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC48"> > </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC46" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC46"> << </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC46" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC46"> Up </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_4.html#SEC61" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_4.html#SEC61"> >> </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc.html#SEC_Top" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc.html#SEC_Top">Top</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_toc.html#SEC_Contents" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_toc.html#SEC_Contents">Contents</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_24.html#SEC261" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_24.html#SEC261">Index</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_abt.html#SEC_About" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_abt.html#SEC_About"> ? </A>]</TD>
|
|
</TR></TABLE>
|
|
<H2> 3.1 Files Created by <CODE>configure</CODE> </H2>
|
|
<!--docid::SEC47::-->
|
|
<P>
|
|
|
|
Here we spell out what files will be set up by <CODE>configure</CODE>. Normally
|
|
you need not be concerned with these files.
|
|
</P><P>
|
|
|
|
<UL>
|
|
<LI>
|
|
A file named <TT>`config.h'</TT> is created that contains a <SAMP>`#include'</SAMP>
|
|
of the top-level config file for the machine you will run the compiler
|
|
on (see section <A HREF="gcc_18.html#SEC251" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_18.html#SEC251">18. The Configuration File</A>). This file is responsible for defining information
|
|
about the host machine. It includes <TT>`tm.h'</TT>.
|
|
<P>
|
|
|
|
The top-level config file is located in the subdirectory <TT>`config'</TT>.
|
|
Its name is always <TT>`xm-<VAR>something</VAR>.h'</TT>; usually
|
|
<TT>`xm-<VAR>machine</VAR>.h'</TT>, but there are some exceptions.
|
|
</P><P>
|
|
|
|
If your system does not support symbolic links, you might want to
|
|
set up <TT>`config.h'</TT> to contain a <SAMP>`#include'</SAMP> command which
|
|
refers to the appropriate file.
|
|
</P><P>
|
|
|
|
<LI>
|
|
A file named <TT>`tconfig.h'</TT> is created which includes the top-level config
|
|
file for your target machine. This is used for compiling certain
|
|
programs to run on that machine.
|
|
<P>
|
|
|
|
<LI>
|
|
A file named <TT>`tm.h'</TT> is created which includes the
|
|
machine-description macro file for your target machine. It should be in
|
|
the subdirectory <TT>`config'</TT> and its name is often
|
|
<TT>`<VAR>machine</VAR>.h'</TT>.
|
|
<P>
|
|
|
|
<LI>
|
|
The command file <TT>`configure'</TT> also constructs the file
|
|
<TT>`Makefile'</TT> by adding some text to the template file
|
|
<TT>`Makefile.in'</TT>. The additional text comes from files in the
|
|
<TT>`config'</TT> directory, named <TT>`t-<VAR>target</VAR>'</TT> and
|
|
<TT>`x-<VAR>host</VAR>'</TT>. If these files do not exist, it means nothing
|
|
needs to be added for a given target or host.
|
|
</UL>
|
|
<P>
|
|
|
|
<A NAME="Configurations"></A>
|
|
<HR SIZE="6">
|
|
<A NAME="SEC48"></A>
|
|
<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
|
|
<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC47" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC47"> < </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC49" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC49"> > </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC49" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC49"> << </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC46" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC46"> Up </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_4.html#SEC61" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_4.html#SEC61"> >> </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc.html#SEC_Top" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc.html#SEC_Top">Top</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_toc.html#SEC_Contents" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_toc.html#SEC_Contents">Contents</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_24.html#SEC261" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_24.html#SEC261">Index</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_abt.html#SEC_About" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_abt.html#SEC_About"> ? </A>]</TD>
|
|
</TR></TABLE>
|
|
<H2> 3.2 Configurations Supported by GNU CC </H2>
|
|
<!--docid::SEC48::-->
|
|
<P>
|
|
|
|
Here are the possible CPU types:
|
|
</P><P>
|
|
|
|
<BLOCKQUOTE>
|
|
1750a, a29k, alpha, arm, c<VAR>n</VAR>, clipper, dsp16xx, elxsi, h8300,
|
|
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.
|
|
</BLOCKQUOTE>
|
|
<P>
|
|
|
|
Here are the recognized company names. As you can see, customary
|
|
abbreviations are used rather than the longer official names.
|
|
</P><P>
|
|
|
|
<BLOCKQUOTE>
|
|
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.
|
|
</BLOCKQUOTE>
|
|
<P>
|
|
|
|
The company name is meaningful only to disambiguate when the rest of
|
|
the information supplied is insufficient. You can omit it, writing
|
|
just <SAMP>`<VAR>cpu</VAR>-<VAR>system</VAR>'</SAMP>, if it is not needed. For example,
|
|
<SAMP>`vax-ultrix4.2'</SAMP> is equivalent to <SAMP>`vax-dec-ultrix4.2'</SAMP>.
|
|
</P><P>
|
|
|
|
Here is a list of system types:
|
|
</P><P>
|
|
|
|
<BLOCKQUOTE>
|
|
386bsd, aix, acis, amigaos, aos, aout, aux, bosx, bsd, clix, coff, ctix, cxux,
|
|
dgux, dynix, ebmon, ecoff, elf, esix, freebsd, hms, 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, xenix.
|
|
</BLOCKQUOTE>
|
|
<P>
|
|
|
|
You can omit the system type; then <TT>`configure'</TT> guesses the
|
|
operating system from the CPU and company.
|
|
</P><P>
|
|
|
|
You can add a version number to the system type; this may or may not
|
|
make a difference. For example, you can write <SAMP>`bsd4.3'</SAMP> or
|
|
<SAMP>`bsd4.4'</SAMP> to distinguish versions of BSD. In practice, the version
|
|
number is most needed for <SAMP>`sysv3'</SAMP> and <SAMP>`sysv4'</SAMP>, which are often
|
|
treated differently.
|
|
</P><P>
|
|
|
|
If you specify an impossible combination such as <SAMP>`i860-dg-vms'</SAMP>,
|
|
then you may get an error message from <TT>`configure'</TT>, or it may
|
|
ignore part of the information and do the best it can with the rest.
|
|
<TT>`configure'</TT> always prints the canonical name for the alternative
|
|
that it used. GNU CC does not support all possible alternatives.
|
|
</P><P>
|
|
|
|
Often a particular model of machine has a name. Many machine names are
|
|
recognized as aliases for CPU/company combinations. Thus, the machine
|
|
name <SAMP>`sun3'</SAMP>, mentioned above, is an alias for <SAMP>`m68k-sun'</SAMP>.
|
|
Sometimes we accept a company name as a machine name, when the name is
|
|
popularly used for a particular machine. Here is a table of the known
|
|
machine names:
|
|
</P><P>
|
|
|
|
<BLOCKQUOTE>
|
|
3300, 3b1, 3b<VAR>n</VAR>, 7300, altos3068, altos,
|
|
apollo68, att-7300, balance,
|
|
convex-c<VAR>n</VAR>, crds, decstation-3100,
|
|
decstation, delta, encore,
|
|
fx2800, gmicro, hp7<VAR>nn</VAR>, hp8<VAR>nn</VAR>,
|
|
hp9k2<VAR>nn</VAR>, hp9k3<VAR>nn</VAR>, hp9k7<VAR>nn</VAR>,
|
|
hp9k8<VAR>nn</VAR>, iris4d, iris, isi68,
|
|
m3230, magnum, merlin, miniframe,
|
|
mmax, news-3600, news800, news, next,
|
|
pbd, pc532, pmax, powerpc, powerpcle, ps2, risc-news,
|
|
rtpc, sun2, sun386i, sun386, sun3,
|
|
sun4, symmetry, tower-32, tower.
|
|
</BLOCKQUOTE>
|
|
<P>
|
|
|
|
Remember that a machine name specifies both the cpu type and the company
|
|
name.
|
|
If you want to install your own homemade configuration files, you can
|
|
use <SAMP>`local'</SAMP> as the company name to access them. If you use
|
|
configuration <SAMP>`<VAR>cpu</VAR>-local'</SAMP>, the configuration name
|
|
without the cpu prefix
|
|
is used to form the configuration file names.
|
|
</P><P>
|
|
|
|
Thus, if you specify <SAMP>`m68k-local'</SAMP>, configuration uses
|
|
files <TT>`m68k.md'</TT>, <TT>`local.h'</TT>, <TT>`m68k.c'</TT>,
|
|
<TT>`xm-local.h'</TT>, <TT>`t-local'</TT>, and <TT>`x-local'</TT>, all in the
|
|
directory <TT>`config/m68k'</TT>.
|
|
</P><P>
|
|
|
|
Here is a list of configurations that have special treatment or special
|
|
things you must know:
|
|
</P><P>
|
|
|
|
<DL COMPACT>
|
|
<DT><SAMP>`1750a-*-*'</SAMP>
|
|
<DD>MIL-STD-1750A processors.
|
|
<P>
|
|
|
|
The MIL-STD-1750A cross configuration produces output for
|
|
<CODE>as1750</CODE>, an assembler/linker available under the GNU Public
|
|
License for the 1750A. <CODE>as1750</CODE> can be obtained at
|
|
<EM>ftp://ftp.fta-berlin.de/pub/crossgcc/1750gals/</EM>.
|
|
A similarly licensed simulator for
|
|
the 1750A is available from same address.
|
|
</P><P>
|
|
|
|
You should ignore a fatal error during the building of libgcc (libgcc is
|
|
not yet implemented for the 1750A.)
|
|
</P><P>
|
|
|
|
The <CODE>as1750</CODE> assembler requires the file <TT>`ms1750.inc'</TT>, which is
|
|
found in the directory <TT>`config/1750a'</TT>.
|
|
</P><P>
|
|
|
|
GNU CC produced the same sections as the Fairchild F9450 C Compiler,
|
|
namely:
|
|
</P><P>
|
|
|
|
<DL COMPACT>
|
|
<DT><CODE>Normal</CODE>
|
|
<DD>The program code section.
|
|
<P>
|
|
|
|
<DT><CODE>Static</CODE>
|
|
<DD>The read/write (RAM) data section.
|
|
<P>
|
|
|
|
<DT><CODE>Konst</CODE>
|
|
<DD>The read-only (ROM) constants section.
|
|
<P>
|
|
|
|
<DT><CODE>Init</CODE>
|
|
<DD>Initialization section (code to copy KREL to SREL).
|
|
</DL>
|
|
<P>
|
|
|
|
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
|
|
GNU CC.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`alpha-*-osf1'</SAMP>
|
|
<DD>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.CC.)
|
|
<P>
|
|
|
|
GNU CC writes a <SAMP>`.verstamp'</SAMP> 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 <TT>`/usr/include/stamp.h'</TT>. If you install a
|
|
new version of DEC Unix, you should rebuild GCC to pick up the new version
|
|
stamp.
|
|
</P><P>
|
|
|
|
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.
|
|
</P><P>
|
|
|
|
<CODE>make compare</CODE> may fail on old versions of DEC Unix unless you add
|
|
<SAMP>`-save-temps'</SAMP> to <CODE>CFLAGS</CODE>. 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 <CODE>stage1</CODE> and
|
|
<CODE>stage2</CODE> compilations. The option <SAMP>`-save-temps'</SAMP> forces a
|
|
fixed name to be used for the assembler input file, instead of a
|
|
randomly chosen name in <TT>`/tmp'</TT>. Do not add <SAMP>`-save-temps'</SAMP>
|
|
unless the comparisons fail without that option. If you add
|
|
<SAMP>`-save-temps'</SAMP>, you will have to manually delete the <SAMP>`.i'</SAMP> and
|
|
<SAMP>`.s'</SAMP> files after each series of compilations.
|
|
</P><P>
|
|
|
|
GNU CC 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 <SAMP>`--with-stabs'</SAMP> option of <TT>`configure'</TT> above
|
|
for more information on these formats and how to select them.
|
|
</P><P>
|
|
|
|
There is a bug in DEC's assembler that produces incorrect line numbers
|
|
for ECOFF format when the <SAMP>`.align'</SAMP> directive is used. To work
|
|
around this problem, GNU CC 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 <SAMP>`-O'</SAMP> is specified are
|
|
different depending on whether or not <SAMP>`-g'</SAMP> is also specified.
|
|
</P><P>
|
|
|
|
To avoid this behavior, specify <SAMP>`-gstabs+'</SAMP> and use GDB instead of
|
|
DBX. DEC is now aware of this problem with the assembler and hopes to
|
|
provide a fix shortly.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`arc-*-elf'</SAMP>
|
|
<DD>Argonaut ARC processor.
|
|
This configuration is intended for embedded systems.
|
|
<P>
|
|
|
|
<DT><SAMP>`arm-*-aout'</SAMP>
|
|
<DD>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 <TT>`a.out'</TT> format object modules.
|
|
<P>
|
|
|
|
You may need to make a variant of the file <TT>`arm.h'</TT> for your particular
|
|
configuration.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`arm-*-linuxaout'</SAMP>
|
|
<DD>Any of the ARM family processors running the Linux-based GNU system with
|
|
the <TT>`a.out'</TT> 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 <TT>`sunsite.unc.edu:/pub/Linux/GCC'</TT> and other mirror sites for
|
|
Linux-based GNU systems.
|
|
<P>
|
|
|
|
<DT><SAMP>`arm-*-riscix'</SAMP>
|
|
<DD>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 and via ftp
|
|
<TT>`ftp.acorn.com:/pub/riscix/as+xterm.tar.Z'</TT>. To enable stabs
|
|
debugging, pass <SAMP>`--with-gnu-as'</SAMP> to configure.
|
|
<P>
|
|
|
|
You will need to install GNU <TT>`sed'</TT> before you can run configure.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`a29k'</SAMP>
|
|
<DD>AMD Am29k-family processors. These are normally used in embedded
|
|
applications. There are no standard Unix configurations.
|
|
This configuration
|
|
corresponds to AMD's standard calling sequence and binary interface
|
|
and is compatible with other 29k tools.
|
|
<P>
|
|
|
|
You may need to make a variant of the file <TT>`a29k.h'</TT> for your
|
|
particular configuration.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`a29k-*-bsd'</SAMP>
|
|
<DD>AMD Am29050 used in a system running a variant of BSD Unix.
|
|
<P>
|
|
|
|
<DT><SAMP>`decstation-*'</SAMP>
|
|
<DD>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 <SAMP>`alpha-dec'</SAMP>.) To configure GCC
|
|
for these platforms use the following configurations:
|
|
<P>
|
|
|
|
<DL COMPACT>
|
|
<DT><SAMP>`decstation-ultrix'</SAMP>
|
|
<DD>Ultrix configuration.
|
|
<P>
|
|
|
|
<DT><SAMP>`decstation-osf1'</SAMP>
|
|
<DD>Dec's version of OSF/1.
|
|
<P>
|
|
|
|
<DT><SAMP>`decstation-osfrose'</SAMP>
|
|
<DD>Open Software Foundation reference port of OSF/1 which uses the
|
|
OSF/rose object file format instead of ECOFF. Normally, you
|
|
would not select this configuration.
|
|
</DL>
|
|
<P>
|
|
|
|
The MIPS C compiler needs to be told to increase its table size
|
|
for switch statements with the <SAMP>`-Wf,-XNg1500'</SAMP> option in
|
|
order to compile <TT>`cp/parse.c'</TT>. If you use the <SAMP>`-O2'</SAMP>
|
|
optimization option, you also need to use <SAMP>`-Olimit 3000'</SAMP>.
|
|
Both of these options are automatically generated in the
|
|
<TT>`Makefile'</TT> that the shell script <TT>`configure'</TT> builds.
|
|
If you override the <CODE>CC</CODE> make variable and use the MIPS
|
|
compilers, you may need to add <SAMP>`-Wf,-XNg1500 -Olimit 3000'</SAMP>.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`elxsi-elxsi-bsd'</SAMP>
|
|
<DD>The Elxsi's C compiler has known limitations that prevent it from
|
|
compiling GNU C. Please contact <CODE>mrs@cygnus.com</CODE> for more details.
|
|
<P>
|
|
|
|
<DT><SAMP>`dsp16xx'</SAMP>
|
|
<DD>A port to the AT&T DSP1610 family of processors.
|
|
<P>
|
|
|
|
<DT><SAMP>`h8300-*-*'</SAMP>
|
|
<DD>Hitachi H8/300 series of processors.
|
|
<P>
|
|
|
|
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.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`hppa*-*-*'</SAMP>
|
|
<DD>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 <EM>not</EM> specify a target
|
|
when configuring GNU CC, the <TT>`configure'</TT> script will try to automatically
|
|
determine the right processor type and operating system.
|
|
<P>
|
|
|
|
<SAMP>`-g'</SAMP> does not work on HP-UX, since that system uses a peculiar
|
|
debugging format which GNU CC does not know about. However, <SAMP>`-g'</SAMP>
|
|
will work if you also use GAS and GDB in conjunction with GCC. We
|
|
highly recommend using GAS for all HP-PA configurations.
|
|
</P><P>
|
|
|
|
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.
|
|
</P><P>
|
|
|
|
On some versions of HP-UX, you will need to install GNU <TT>`sed'</TT>.
|
|
</P><P>
|
|
|
|
You will need to be install GAS into a directory before <CODE>/bin</CODE>,
|
|
<CODE>/usr/bin</CODE>, and <CODE>/usr/ccs/bin</CODE> in your search path. You
|
|
should install GAS before you build GNU CC.
|
|
</P><P>
|
|
|
|
To enable debugging, you must configure GNU CC with the <SAMP>`--with-gnu-as'</SAMP>
|
|
option before building.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`i370-*-*'</SAMP>
|
|
<DD>This port is very preliminary and has many known bugs. We hope to
|
|
have a higher-quality port for this machine soon.
|
|
<P>
|
|
|
|
<DT><SAMP>`i386-*-linux-gnuoldld'</SAMP>
|
|
<DD>Use this configuration to generate <TT>`a.out'</TT> 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.
|
|
<P>
|
|
|
|
<DT><SAMP>`i386-*-linux-gnuaout'</SAMP>
|
|
<DD>Use this configuration to generate <TT>`a.out'</TT> binaries on Linux-based
|
|
GNU systems. This configuration is being superseded. You must use
|
|
gas/binutils version 2.5.2 or later.
|
|
<P>
|
|
|
|
<DT><SAMP>`i386-*-linux-gnu'</SAMP>
|
|
<DD>Use this configuration to generate ELF binaries on Linux-based GNU
|
|
systems. You must use gas/binutils version 2.5.2 or later.
|
|
<P>
|
|
|
|
<DT><SAMP>`i386-*-sco'</SAMP>
|
|
<DD>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.
|
|
<P>
|
|
|
|
<DT><SAMP>`i386-*-sco3.2v4'</SAMP>
|
|
<DD>Use this configuration for SCO release 3.2 version 4.
|
|
<P>
|
|
|
|
<DT><SAMP>`i386-*-sco3.2v5*'</SAMP>
|
|
<DD>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.
|
|
<P>
|
|
|
|
GNU CC can generate COFF binaries if you specify <SAMP>`-mcoff'</SAMP> or ELF
|
|
binaries, the default. A full <SAMP>`make bootstrap'</SAMP> is recommended
|
|
so that an ELF compiler that builds ELF is generated.
|
|
</P><P>
|
|
|
|
You must have TLS597 from <A HREF="tppmsgs/msgs0.htm#2" tppabs="ftp://ftp.sco.com/TLS">ftp://ftp.sco.com/TLS</A> installed for ELF
|
|
C++ binaries to work correctly on releases before 5.0.4.
|
|
</P><P>
|
|
|
|
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 <SAMP>`--with-gnu-as'</SAMP>. 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.
|
|
</P><P>
|
|
|
|
<EM>NOTE:</EM> If you are building C++, you must follow the instructions
|
|
about invoking <SAMP>`make bootstrap'</SAMP> because the native OpenServer
|
|
compiler may build a <TT>`cc1plus'</TT> that will not correctly parse many
|
|
valid C++ programs. You must do a <SAMP>`make bootstrap'</SAMP> if you are
|
|
building with the native compiler.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`i386-*-isc'</SAMP>
|
|
<DD>It may be a good idea to link with GNU malloc instead of the malloc that
|
|
comes with the system.
|
|
<P>
|
|
|
|
In ISC version 4.1, <TT>`sed'</TT> core dumps when building
|
|
<TT>`deduced.h'</TT>. Use the version of <TT>`sed'</TT> from version 4.0.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`i386-*-esix'</SAMP>
|
|
<DD>It may be good idea to link with GNU malloc instead of the malloc that
|
|
comes with the system.
|
|
<P>
|
|
|
|
<DT><SAMP>`i386-ibm-aix'</SAMP>
|
|
<DD>You need to use GAS version 2.1 or later, and LD from
|
|
GNU binutils version 2.2 or later.
|
|
<P>
|
|
|
|
<DT><SAMP>`i386-sequent-bsd'</SAMP>
|
|
<DD>Go to the Berkeley universe before compiling.
|
|
<P>
|
|
|
|
<DT><SAMP>`i386-sequent-ptx1*'</SAMP>
|
|
<DD><DT><SAMP>`i386-sequent-ptx2*'</SAMP>
|
|
<DD>You must install GNU <TT>`sed'</TT> before running <TT>`configure'</TT>.
|
|
<P>
|
|
|
|
<DT><SAMP>`i386-sun-sunos4'</SAMP>
|
|
<DD>You may find that you need another version of GNU CC to begin
|
|
bootstrapping with, since the current version when built with the
|
|
system's own compiler seems to get an infinite loop compiling part of
|
|
<TT>`libgcc2.c'</TT>. GNU CC version 2 compiled with GNU CC (any version)
|
|
seems not to have this problem.
|
|
<P>
|
|
|
|
See <A HREF="gcc_3.html#SEC57" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC57">3.5 Installing GNU CC on the Sun</A>, for information on installing GNU CC on Sun
|
|
systems.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`i[345]86-*-winnt3.5'</SAMP>
|
|
<DD>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
|
|
<TT>`cs.washington.edu:pub/gnat'</TT> or <TT>`cs.nyu.edu:pub/gnat'</TT>. You
|
|
must also use the Microsoft header files from the Windows NT 3.5 SDK.
|
|
Find these on the CDROM in the <TT>`/mstools/h'</TT> directory dated 9/4/94. You
|
|
must use a fixed version of Microsoft linker made especially for NT 3.5,
|
|
which is also is available on the NT 3.5 SDK CDROM. If you do not have
|
|
this linker, can you also use the linker from Visual C/C++ 1.0 or 2.0.
|
|
<P>
|
|
|
|
Installing GNU CC for NT builds a wrapper linker, called <TT>`ld.exe'</TT>,
|
|
which mimics the behaviour of Unix <TT>`ld'</TT> in the specification of
|
|
libraries (<SAMP>`-L'</SAMP> and <SAMP>`-l'</SAMP>). <TT>`ld.exe'</TT> looks for both Unix
|
|
and Microsoft named libraries. For example, if you specify
|
|
<SAMP>`-lfoo'</SAMP>, <TT>`ld.exe'</TT> will look first for <TT>`libfoo.a'</TT>
|
|
and then for <TT>`foo.lib'</TT>.
|
|
</P><P>
|
|
|
|
You may install GNU CC for Windows NT in one of two ways, depending on
|
|
whether or not you have a Unix-like shell and various Unix-like
|
|
utilities.
|
|
</P><P>
|
|
|
|
<OL>
|
|
<LI>
|
|
If you do not have a Unix-like shell and few Unix-like utilities, you
|
|
will use a DOS style batch script called <TT>`configure.bat'</TT>. Invoke
|
|
it as <CODE>configure winnt</CODE> from an MSDOS console window or from the
|
|
program manager dialog box. <TT>`configure.bat'</TT> assumes you have
|
|
already installed and have in your path a Unix-like <TT>`sed'</TT> program
|
|
which is used to create a working <TT>`Makefile'</TT> from <TT>`Makefile.in'</TT>.
|
|
<P>
|
|
|
|
<TT>`Makefile'</TT> uses the Microsoft Nmake program maintenance utility and
|
|
the Visual C/C++ V8.00 compiler to build GNU CC. You need only have the
|
|
utilities <TT>`sed'</TT> and <TT>`touch'</TT> to use this installation method,
|
|
which only automatically builds the compiler itself. You must then
|
|
examine what <TT>`fixinc.winnt'</TT> does, edit the header files by hand and
|
|
build <TT>`libgcc.a'</TT> manually.
|
|
</P><P>
|
|
|
|
<LI>
|
|
The second type of installation assumes you are running a Unix-like
|
|
shell, have a complete suite of Unix-like utilities in your path, and
|
|
have a previous version of GNU CC already installed, either through
|
|
building it via the above installation method or acquiring a pre-built
|
|
binary. In this case, use the <TT>`configure'</TT> script in the normal
|
|
fashion.
|
|
</OL>
|
|
<P>
|
|
|
|
<DT><SAMP>`i860-intel-osf1'</SAMP>
|
|
<DD>This is the Paragon.
|
|
If you have version 1.0 of the operating system,
|
|
see <A HREF="gcc_7.html#SEC120" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_7.html#SEC120">7.2 Installation Problems</A>, for special things you need to do to
|
|
compensate for peculiarities in the system.
|
|
<P>
|
|
|
|
<DT><SAMP>`*-lynx-lynxos'</SAMP>
|
|
<DD>LynxOS 2.2 and earlier comes with GNU CC 1.x already installed as
|
|
<TT>`/bin/gcc'</TT>. You should compile with this instead of <TT>`/bin/cc'</TT>.
|
|
You can tell GNU CC to use the GNU assembler and linker, by specifying
|
|
<SAMP>`--with-gnu-as --with-gnu-ld'</SAMP> when configuring. These will produce
|
|
COFF format object files and executables; otherwise GNU CC will use the
|
|
installed tools, which produce <TT>`a.out'</TT> format executables.
|
|
<P>
|
|
|
|
<DT><SAMP>`m32r-*-elf'</SAMP>
|
|
<DD>Mitsubishi M32R processor.
|
|
This configuration is intended for embedded systems.
|
|
<P>
|
|
|
|
<DT><SAMP>`m68000-hp-bsd'</SAMP>
|
|
<DD>HP 9000 series 200 running BSD. Note that the C compiler that comes
|
|
with this system cannot compile GNU CC; contact <CODE>law@cygnus.com</CODE>
|
|
to get binaries of GNU CC for bootstrapping.
|
|
<P>
|
|
|
|
<DT><SAMP>`m68k-altos'</SAMP>
|
|
<DD>Altos 3068. You must use the GNU assembler, linker and debugger.
|
|
Also, you must fix a kernel bug. Details in the file <TT>`README.ALTOS'</TT>.
|
|
<P>
|
|
|
|
<DT><SAMP>`m68k-apple-aux'</SAMP>
|
|
<DD>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 <SAMP>`--with-gnu-as'</SAMP> and <SAMP>`--with-gnu-ld'</SAMP>
|
|
options to <CODE>configure</CODE>.
|
|
<P>
|
|
|
|
Note the C compiler that comes
|
|
with this system cannot compile GNU CC. You can find binaries of GNU CC
|
|
for bootstrapping on <CODE>jagubox.gsfc.nasa.gov</CODE>.
|
|
You will also a patched version of <TT>`/bin/ld'</TT> there that
|
|
raises some of the arbitrary limits found in the original.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`m68k-att-sysv'</SAMP>
|
|
<DD>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 bugs in that
|
|
compiler. You can bootstrap it more easily with
|
|
previous versions of GNU CC if you have them.
|
|
<P>
|
|
|
|
Installing GNU CC on the 3b1 is difficult if you do not already have
|
|
GNU CC running, due to bugs in the installed C compiler. However,
|
|
the following procedure might work. We are unable to test it.
|
|
</P><P>
|
|
|
|
<OL>
|
|
<LI>
|
|
Comment out the <SAMP>`#include "config.h"'</SAMP> line near the start of
|
|
<TT>`cccp.c'</TT> and do <SAMP>`make cpp'</SAMP>. This makes a preliminary version
|
|
of GNU cpp.
|
|
<P>
|
|
|
|
<LI>
|
|
Save the old <TT>`/lib/cpp'</TT> and copy the preliminary GNU cpp to that
|
|
file name.
|
|
<P>
|
|
|
|
<LI>
|
|
Undo your change in <TT>`cccp.c'</TT>, or reinstall the original version,
|
|
and do <SAMP>`make cpp'</SAMP> again.
|
|
<P>
|
|
|
|
<LI>
|
|
Copy this final version of GNU cpp into <TT>`/lib/cpp'</TT>.
|
|
<P>
|
|
|
|
<A NAME="IDX249"></A>
|
|
<LI>
|
|
Replace every occurrence of <CODE>obstack_free</CODE> in the file
|
|
<TT>`tree.c'</TT> with <CODE>_obstack_free</CODE>.
|
|
<P>
|
|
|
|
<LI>
|
|
Run <CODE>make</CODE> to get the first-stage GNU CC.
|
|
<P>
|
|
|
|
<LI>
|
|
Reinstall the original version of <TT>`/lib/cpp'</TT>.
|
|
<P>
|
|
|
|
<LI>
|
|
Now you can compile GNU CC with itself and install it in the normal
|
|
fashion.
|
|
</OL>
|
|
<P>
|
|
|
|
<DT><SAMP>`m68k-bull-sysv'</SAMP>
|
|
<DD>Bull DPX/2 series 200 and 300 with BOS-2.00.45 up to BOS-2.01. GNU CC works
|
|
either with native assembler or GNU assembler. You can use
|
|
GNU assembler with native coff generation by providing <SAMP>`--with-gnu-as'</SAMP> to
|
|
the configure script or use GNU assembler with dbx-in-coff encapsulation
|
|
by providing <SAMP>`--with-gnu-as --stabs'</SAMP>. For any problem with native
|
|
assembler or for availability of the DPX/2 port of GAS, contact
|
|
<CODE>F.Pierresteguy@frcl.bull.fr</CODE>.
|
|
<P>
|
|
|
|
<DT><SAMP>`m68k-crds-unox'</SAMP>
|
|
<DD>Use <SAMP>`configure unos'</SAMP> for building on Unos.
|
|
<P>
|
|
|
|
The Unos assembler is named <CODE>casm</CODE> instead of <CODE>as</CODE>. For some
|
|
strange reason linking <TT>`/bin/as'</TT> to <TT>`/bin/casm'</TT> changes the
|
|
behavior, and does not work. So, when installing GNU CC, you should
|
|
install the following script as <TT>`as'</TT> in the subdirectory where
|
|
the passes of GCC are installed:
|
|
</P><P>
|
|
|
|
<TABLE><tr><td> </td><td class=example><pre>#!/bin/sh
|
|
casm $*
|
|
</pre></td></tr></table></P><P>
|
|
|
|
The default Unos library is named <TT>`libunos.a'</TT> instead of
|
|
<TT>`libc.a'</TT>. To allow GNU CC to function, either change all
|
|
references to <SAMP>`-lc'</SAMP> in <TT>`gcc.c'</TT> to <SAMP>`-lunos'</SAMP> or link
|
|
<TT>`/lib/libc.a'</TT> to <TT>`/lib/libunos.a'</TT>.
|
|
</P><P>
|
|
|
|
<A NAME="IDX250"></A>
|
|
When compiling GNU CC with the standard compiler, to overcome bugs in
|
|
the support of <CODE>alloca</CODE>, do not use <SAMP>`-O'</SAMP> when making stage 2.
|
|
Then use the stage 2 compiler with <SAMP>`-O'</SAMP> 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.
|
|
</P><P>
|
|
|
|
(Perhaps simply defining <CODE>ALLOCA</CODE> in <TT>`x-crds'</TT> as described in
|
|
the comments there will make the above paragraph superfluous. Please
|
|
inform us of whether this works.)
|
|
</P><P>
|
|
|
|
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 <TT>`cc1'</TT> fails, try putting the object files into a library
|
|
and linking from that library.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`m68k-hp-hpux'</SAMP>
|
|
<DD>HP 9000 series 300 or 400 running HP-UX. HP-UX version 8.0 has a bug in
|
|
the assembler that prevents compilation of GNU CC. To fix it, get patch
|
|
PHCO_4484 from HP.
|
|
<P>
|
|
|
|
In addition, if you wish to use gas <SAMP>`--with-gnu-as'</SAMP> 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.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`m68k-sun'</SAMP>
|
|
<DD>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.
|
|
<P>
|
|
|
|
See <A HREF="gcc_3.html#SEC57" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC57">3.5 Installing GNU CC on the Sun</A>, for information on installing GNU CC on Sun
|
|
systems.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`m88k-*-svr3'</SAMP>
|
|
<DD>Motorola m88k running the AT&T/Unisoft/Motorola V.3 reference port.
|
|
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.
|
|
<P>
|
|
|
|
It is best, however, to use an older version of GNU CC for bootstrapping
|
|
if you have one.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`m88k-*-dgux'</SAMP>
|
|
<DD>Motorola m88k running DG/UX. To build 88open BCS native or cross
|
|
compilers on DG/UX, specify the configuration name as
|
|
<SAMP>`m88k-*-dguxbcs'</SAMP> and build in the 88open BCS software development
|
|
environment. To build ELF native or cross compilers on DG/UX, specify
|
|
<SAMP>`m88k-*-dgux'</SAMP> and build in the DG/UX ELF development environment.
|
|
You set the software development environment by issuing
|
|
<SAMP>`sde-target'</SAMP> command and specifying either <SAMP>`m88kbcs'</SAMP> or
|
|
<SAMP>`m88kdguxelf'</SAMP> as the operand.
|
|
<P>
|
|
|
|
If you do not specify a configuration name, <TT>`configure'</TT> guesses the
|
|
configuration based on the current software development environment.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`m88k-tektronix-sysv3'</SAMP>
|
|
<DD>Tektronix XD88 running UTekV 3.2e. 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.
|
|
<P>
|
|
|
|
<DT><SAMP>`mips-mips-bsd'</SAMP>
|
|
<DD>MIPS machines running the MIPS operating system in BSD mode. It's
|
|
possible that some old versions of the system lack the functions
|
|
<CODE>memcpy</CODE>, <CODE>memcmp</CODE>, and <CODE>memset</CODE>. If your system lacks
|
|
these, you must remove or undo the definition of
|
|
<CODE>TARGET_MEM_FUNCTIONS</CODE> in <TT>`mips-bsd.h'</TT>.
|
|
<P>
|
|
|
|
The MIPS C compiler needs to be told to increase its table size
|
|
for switch statements with the <SAMP>`-Wf,-XNg1500'</SAMP> option in
|
|
order to compile <TT>`cp/parse.c'</TT>. If you use the <SAMP>`-O2'</SAMP>
|
|
optimization option, you also need to use <SAMP>`-Olimit 3000'</SAMP>.
|
|
Both of these options are automatically generated in the
|
|
<TT>`Makefile'</TT> that the shell script <TT>`configure'</TT> builds.
|
|
If you override the <CODE>CC</CODE> make variable and use the MIPS
|
|
compilers, you may need to add <SAMP>`-Wf,-XNg1500 -Olimit 3000'</SAMP>.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`mips-mips-riscos*'</SAMP>
|
|
<DD>The MIPS C compiler needs to be told to increase its table size
|
|
for switch statements with the <SAMP>`-Wf,-XNg1500'</SAMP> option in
|
|
order to compile <TT>`cp/parse.c'</TT>. If you use the <SAMP>`-O2'</SAMP>
|
|
optimization option, you also need to use <SAMP>`-Olimit 3000'</SAMP>.
|
|
Both of these options are automatically generated in the
|
|
<TT>`Makefile'</TT> that the shell script <TT>`configure'</TT> builds.
|
|
If you override the <CODE>CC</CODE> make variable and use the MIPS
|
|
compilers, you may need to add <SAMP>`-Wf,-XNg1500 -Olimit 3000'</SAMP>.
|
|
<P>
|
|
|
|
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:
|
|
</P><P>
|
|
|
|
<DL COMPACT>
|
|
<DT><SAMP>`mips-mips-riscos<CODE>rev</CODE>'</SAMP>
|
|
<DD>Default configuration for RISC-OS, revision <CODE>rev</CODE>.
|
|
<P>
|
|
|
|
<DT><SAMP>`mips-mips-riscos<CODE>rev</CODE>bsd'</SAMP>
|
|
<DD>BSD 4.3 configuration for RISC-OS, revision <CODE>rev</CODE>.
|
|
<P>
|
|
|
|
<DT><SAMP>`mips-mips-riscos<CODE>rev</CODE>sysv4'</SAMP>
|
|
<DD>System V.4 configuration for RISC-OS, revision <CODE>rev</CODE>.
|
|
<P>
|
|
|
|
<DT><SAMP>`mips-mips-riscos<CODE>rev</CODE>sysv'</SAMP>
|
|
<DD>System V.3 configuration for RISC-OS, revision <CODE>rev</CODE>.
|
|
</DL>
|
|
<P>
|
|
|
|
The revision <CODE>rev</CODE> 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 (see <A HREF="gcc_7.html#SEC120" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_7.html#SEC120">7.2 Installation Problems</A>, for more details).
|
|
</P><P>
|
|
|
|
<DT><SAMP>`mips-sgi-*'</SAMP>
|
|
<DD>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.
|
|
<P>
|
|
|
|
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.
|
|
</P><P>
|
|
|
|
<CODE>make compare</CODE> may fail on version 5 of IRIX unless you add
|
|
<SAMP>`-save-temps'</SAMP> to <CODE>CFLAGS</CODE>. 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 <CODE>stage1</CODE> and
|
|
<CODE>stage2</CODE> compilations. The option <SAMP>`-save-temps'</SAMP> forces a
|
|
fixed name to be used for the assembler input file, instead of a
|
|
randomly chosen name in <TT>`/tmp'</TT>. Do not add <SAMP>`-save-temps'</SAMP>
|
|
unless the comparisons fail without that option. If you do you
|
|
<SAMP>`-save-temps'</SAMP>, you will have to manually delete the <SAMP>`.i'</SAMP> and
|
|
<SAMP>`.s'</SAMP> files after each series of compilations.
|
|
</P><P>
|
|
|
|
The MIPS C compiler needs to be told to increase its table size
|
|
for switch statements with the <SAMP>`-Wf,-XNg1500'</SAMP> option in
|
|
order to compile <TT>`cp/parse.c'</TT>. If you use the <SAMP>`-O2'</SAMP>
|
|
optimization option, you also need to use <SAMP>`-Olimit 3000'</SAMP>.
|
|
Both of these options are automatically generated in the
|
|
<TT>`Makefile'</TT> that the shell script <TT>`configure'</TT> builds.
|
|
If you override the <CODE>CC</CODE> make variable and use the MIPS
|
|
compilers, you may need to add <SAMP>`-Wf,-XNg1500 -Olimit 3000'</SAMP>.
|
|
</P><P>
|
|
|
|
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
|
|
<SAMP>`mips-sgi-irix4loser'</SAMP>. This configuration inhibits assembler
|
|
optimization.
|
|
</P><P>
|
|
|
|
In a compiler configured with target <SAMP>`mips-sgi-irix4'</SAMP>, you can turn
|
|
off assembler optimization by using the <SAMP>`-noasmopt'</SAMP> option. This
|
|
compiler option passes the option <SAMP>`-O0'</SAMP> to the assembler, to
|
|
inhibit reordering.
|
|
</P><P>
|
|
|
|
The <SAMP>`-noasmopt'</SAMP> option can be useful for testing whether a problem
|
|
is due to erroneous assembler reordering. Even if a problem does not go
|
|
away with <SAMP>`-noasmopt'</SAMP>, it may still be due to assembler
|
|
reordering--perhaps GNU CC itself was miscompiled as a result.
|
|
</P><P>
|
|
|
|
To enable debugging under Irix 5, you must use GNU as 2.5 or later,
|
|
and use the <SAMP>`--with-gnu-as'</SAMP> configure option when configuring gcc.
|
|
GNU as is distributed as part of the binutils package.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`mips-sony-sysv'</SAMP>
|
|
<DD>Sony MIPS NEWS. This works in NEWSOS 5.0.1, but not in 5.0.2 (which
|
|
uses ELF instead of COFF). Support for 5.0.2 will probably be provided
|
|
soon by volunteers. In particular, the linker does not like the
|
|
code generated by GCC when shared libraries are linked in.
|
|
<P>
|
|
|
|
<DT><SAMP>`ns32k-encore'</SAMP>
|
|
<DD>Encore ns32000 system. Encore systems are supported only under BSD.
|
|
<P>
|
|
|
|
<DT><SAMP>`ns32k-*-genix'</SAMP>
|
|
<DD>National Semiconductor ns32000 system. Genix has bugs in <CODE>alloca</CODE>
|
|
and <CODE>malloc</CODE>; you must get the compiled versions of these from GNU
|
|
Emacs.
|
|
<P>
|
|
|
|
<DT><SAMP>`ns32k-sequent'</SAMP>
|
|
<DD>Go to the Berkeley universe before compiling.
|
|
<P>
|
|
|
|
<DT><SAMP>`ns32k-utek'</SAMP>
|
|
<DD>UTEK ns32000 system ("merlin"). The C compiler that comes with this
|
|
system cannot compile GNU CC; contact <SAMP>`tektronix!reed!mason'</SAMP> to get
|
|
binaries of GNU CC for bootstrapping.
|
|
<P>
|
|
|
|
<DT><SAMP>`romp-*-aos'</SAMP>
|
|
<DD><DT><SAMP>`romp-*-mach'</SAMP>
|
|
<DD>The only operating systems supported for the IBM RT PC are AOS and
|
|
MACH. GNU CC does not support AIX running on the RT. We recommend you
|
|
compile GNU CC with an earlier version of itself; if you compile GNU CC
|
|
with <CODE>hc</CODE>, 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.
|
|
<P>
|
|
|
|
<DT><SAMP>`rs6000-*-aix'</SAMP>
|
|
<DD><DT><SAMP>`powerpc-*-aix'</SAMP>
|
|
<DD>Various early versions of each release of the IBM XLC compiler will not
|
|
bootstrap GNU CC. Symptoms include differences between the stage2 and
|
|
stage3 object files, and errors when compiling <TT>`libgcc.a'</TT> or
|
|
<TT>`enquire'</TT>. Known problematic releases include: 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.
|
|
<P>
|
|
|
|
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 <TT>`README.RS6000'</TT> for more details on any of these problems.
|
|
</P><P>
|
|
|
|
GNU CC does not yet support the 64-bit PowerPC instructions.
|
|
</P><P>
|
|
|
|
Objective C does not work on this architecture because it makes assumptions
|
|
that are incompatible with the calling conventions.
|
|
</P><P>
|
|
|
|
AIX on the RS/6000 provides support (NLS) for environments outside of
|
|
the United States. Compilers and assemblers use NLS to support
|
|
locale-specific representations of various objects including
|
|
floating-point numbers ("." vs "," for separating decimal fractions).
|
|
There have been problems reported where the library linked with GNU CC
|
|
does not produce the same floating-point formats that the assembler
|
|
accepts. If you have this problem, set the LANG environment variable to
|
|
"C" or "En_US".
|
|
</P><P>
|
|
|
|
Due to changes in the way that GNU CC invokes the binder (linker) for AIX
|
|
4.1, you may now receive warnings of duplicate symbols from the link step
|
|
that were not reported before. The assembly files generated by GNU CC for
|
|
AIX have always 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.
|
|
</P><P>
|
|
|
|
By default, AIX 4.1 produces code that can be used on either Power or
|
|
PowerPC processors.
|
|
</P><P>
|
|
|
|
You can specify a default version for the <SAMP>`-mcpu='</SAMP><VAR>cpu_type</VAR>
|
|
switch by using the configure option <SAMP>`--with-cpu-'</SAMP><VAR>cpu_type</VAR>.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`powerpc-*-elf'</SAMP>
|
|
<DD><DT><SAMP>`powerpc-*-sysv4'</SAMP>
|
|
<DD>PowerPC system in big endian mode, running System V.4.
|
|
<P>
|
|
|
|
You can specify a default version for the <SAMP>`-mcpu='</SAMP><VAR>cpu_type</VAR>
|
|
switch by using the configure option <SAMP>`--with-cpu-'</SAMP><VAR>cpu_type</VAR>.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`powerpc-*-linux-gnu'</SAMP>
|
|
<DD>PowerPC system in big endian mode, running the Linux-based GNU system.
|
|
<P>
|
|
|
|
You can specify a default version for the <SAMP>`-mcpu='</SAMP><VAR>cpu_type</VAR>
|
|
switch by using the configure option <SAMP>`--with-cpu-'</SAMP><VAR>cpu_type</VAR>.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`powerpc-*-eabiaix'</SAMP>
|
|
<DD>Embedded PowerPC system in big endian mode with -mcall-aix selected as
|
|
the default.
|
|
<P>
|
|
|
|
You can specify a default version for the <SAMP>`-mcpu='</SAMP><VAR>cpu_type</VAR>
|
|
switch by using the configure option <SAMP>`--with-cpu-'</SAMP><VAR>cpu_type</VAR>.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`powerpc-*-eabisim'</SAMP>
|
|
<DD>Embedded PowerPC system in big endian mode for use in running under the
|
|
PSIM simulator.
|
|
<P>
|
|
|
|
You can specify a default version for the <SAMP>`-mcpu='</SAMP><VAR>cpu_type</VAR>
|
|
switch by using the configure option <SAMP>`--with-cpu-'</SAMP><VAR>cpu_type</VAR>.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`powerpc-*-eabi'</SAMP>
|
|
<DD>Embedded PowerPC system in big endian mode.
|
|
<P>
|
|
|
|
You can specify a default version for the <SAMP>`-mcpu='</SAMP><VAR>cpu_type</VAR>
|
|
switch by using the configure option <SAMP>`--with-cpu-'</SAMP><VAR>cpu_type</VAR>.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`powerpcle-*-elf'</SAMP>
|
|
<DD><DT><SAMP>`powerpcle-*-sysv4'</SAMP>
|
|
<DD>PowerPC system in little endian mode, running System V.4.
|
|
<P>
|
|
|
|
You can specify a default version for the <SAMP>`-mcpu='</SAMP><VAR>cpu_type</VAR>
|
|
switch by using the configure option <SAMP>`--with-cpu-'</SAMP><VAR>cpu_type</VAR>.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`powerpcle-*-solaris2*'</SAMP>
|
|
<DD>PowerPC system in little endian mode, running Solaris 2.5.1 or higher.
|
|
<P>
|
|
|
|
You can specify a default version for the <SAMP>`-mcpu='</SAMP><VAR>cpu_type</VAR>
|
|
switch by using the configure option <SAMP>`--with-cpu-'</SAMP><VAR>cpu_type</VAR>.
|
|
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.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`powerpcle-*-eabisim'</SAMP>
|
|
<DD>Embedded PowerPC system in little endian mode for use in running under
|
|
the PSIM simulator.
|
|
<P>
|
|
|
|
<DT><SAMP>`powerpcle-*-eabi'</SAMP>
|
|
<DD>Embedded PowerPC system in little endian mode.
|
|
<P>
|
|
|
|
You can specify a default version for the <SAMP>`-mcpu='</SAMP><VAR>cpu_type</VAR>
|
|
switch by using the configure option <SAMP>`--with-cpu-'</SAMP><VAR>cpu_type</VAR>.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`powerpcle-*-winnt'</SAMP>
|
|
<DD><DT><SAMP>`powerpcle-*-pe'</SAMP>
|
|
<DD>PowerPC system in little endian mode running Windows NT.
|
|
<P>
|
|
|
|
You can specify a default version for the <SAMP>`-mcpu='</SAMP><VAR>cpu_type</VAR>
|
|
switch by using the configure option <SAMP>`--with-cpu-'</SAMP><VAR>cpu_type</VAR>.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`vax-dec-ultrix'</SAMP>
|
|
<DD>Don't try compiling with Vax C (<CODE>vcc</CODE>). It produces incorrect code
|
|
in some cases (for example, when <CODE>alloca</CODE> is used).
|
|
<P>
|
|
|
|
Meanwhile, compiling <TT>`cp/parse.c'</TT> with pcc does not work because of
|
|
an internal table size limitation in that compiler. To avoid this
|
|
problem, compile just the GNU C compiler first, and use it to recompile
|
|
building all the languages that you want to run.
|
|
</P><P>
|
|
|
|
<DT><SAMP>`sparc-sun-*'</SAMP>
|
|
<DD>See <A HREF="gcc_3.html#SEC57" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC57">3.5 Installing GNU CC on the Sun</A>, for information on installing GNU CC on Sun
|
|
systems.
|
|
<P>
|
|
|
|
<DT><SAMP>`vax-dec-vms'</SAMP>
|
|
<DD>See <A HREF="gcc_3.html#SEC58" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC58">3.6 Installing GNU CC on VMS</A>, for details on how to install GNU CC on VMS.
|
|
<P>
|
|
|
|
<DT><SAMP>`we32k-*-*'</SAMP>
|
|
<DD>These computers are also known as the 3b2, 3b5, 3b20 and other similar
|
|
names. (However, the 3b1 is actually a 68000; see
|
|
<A HREF="gcc_3.html#SEC48" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC48">3.2 Configurations Supported by GNU CC</A>.)
|
|
<P>
|
|
|
|
Don't use <SAMP>`-g'</SAMP> when compiling with the system's compiler. The
|
|
system's linker seems to be unable to handle such a large program with
|
|
debugging information.
|
|
</P><P>
|
|
|
|
The system's compiler runs out of capacity when compiling <TT>`stmt.c'</TT>
|
|
in GNU CC. You can work around this by building <TT>`cpp'</TT> in GNU CC
|
|
first, then use that instead of the system's preprocessor with the
|
|
system's C compiler to compile <TT>`stmt.c'</TT>. Here is how:
|
|
</P><P>
|
|
|
|
<TABLE><tr><td> </td><td class=smallexample><FONT SIZE=-1><pre>mv /lib/cpp /lib/cpp.att
|
|
cp cpp /lib/cpp.gnu
|
|
echo '/lib/cpp.gnu -traditional ${1+"$@"}' > /lib/cpp
|
|
chmod +x /lib/cpp
|
|
</FONT></pre></td></tr></table></P><P>
|
|
|
|
The system's compiler produces bad code for some of the GNU CC
|
|
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:
|
|
</P><P>
|
|
|
|
<TABLE><tr><td> </td><td class=smallexample><FONT SIZE=-1><pre>make LANGUAGES=c CC=stage1/xgcc CFLAGS="-Bstage1/ -g"
|
|
make stage2
|
|
make CC=stage2/xgcc CFLAGS="-Bstage2/ -g -O"
|
|
</FONT></pre></td></tr></table></P><P>
|
|
|
|
You may need to raise the ULIMIT setting to build a C++ compiler,
|
|
as the file <TT>`cc1plus'</TT> is larger than one megabyte.
|
|
</DL>
|
|
<P>
|
|
|
|
<A NAME="Other Dir"></A>
|
|
<HR SIZE="6">
|
|
<A NAME="SEC49"></A>
|
|
<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
|
|
<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC48" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC48"> < </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC50" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC50"> > </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC50" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC50"> << </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC46" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC46"> Up </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_4.html#SEC61" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_4.html#SEC61"> >> </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc.html#SEC_Top" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc.html#SEC_Top">Top</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_toc.html#SEC_Contents" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_toc.html#SEC_Contents">Contents</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_24.html#SEC261" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_24.html#SEC261">Index</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_abt.html#SEC_About" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_abt.html#SEC_About"> ? </A>]</TD>
|
|
</TR></TABLE>
|
|
<H2> 3.3 Compilation in a Separate Directory </H2>
|
|
<!--docid::SEC49::-->
|
|
<P>
|
|
|
|
If you wish to build the object files and executables in a directory
|
|
other than the one containing the source files, here is what you must
|
|
do differently:
|
|
</P><P>
|
|
|
|
<OL>
|
|
<LI>
|
|
Make sure you have a version of Make that supports the <CODE>VPATH</CODE>
|
|
feature. (GNU Make supports it, as do Make versions on most BSD
|
|
systems.)
|
|
<P>
|
|
|
|
<LI>
|
|
If you have ever run <TT>`configure'</TT> in the source directory, you must undo
|
|
the configuration. Do this by running:
|
|
<P>
|
|
|
|
<TABLE><tr><td> </td><td class=example><pre>make distclean
|
|
</pre></td></tr></table></P><P>
|
|
|
|
<LI>
|
|
Go to the directory in which you want to build the compiler before
|
|
running <TT>`configure'</TT>:
|
|
<P>
|
|
|
|
<TABLE><tr><td> </td><td class=example><pre>mkdir gcc-sun3
|
|
cd gcc-sun3
|
|
</pre></td></tr></table></P><P>
|
|
|
|
On systems that do not support symbolic links, this directory must be
|
|
on the same file system as the source code directory.
|
|
</P><P>
|
|
|
|
<LI>
|
|
Specify where to find <TT>`configure'</TT> when you run it:
|
|
<P>
|
|
|
|
<TABLE><tr><td> </td><td class=example><pre>../gcc/configure <small>...</small>
|
|
</pre></td></tr></table></P><P>
|
|
|
|
This also tells <CODE>configure</CODE> where to find the compiler sources;
|
|
<CODE>configure</CODE> takes the directory from the file name that was used to
|
|
invoke it. But if you want to be sure, you can specify the source
|
|
directory with the <SAMP>`--srcdir'</SAMP> option, like this:
|
|
</P><P>
|
|
|
|
<TABLE><tr><td> </td><td class=example><pre>../gcc/configure --srcdir=../gcc <VAR>other options</VAR>
|
|
</pre></td></tr></table></P><P>
|
|
|
|
The directory you specify with <SAMP>`--srcdir'</SAMP> need not be the same
|
|
as the one that <CODE>configure</CODE> is found in.
|
|
</OL>
|
|
<P>
|
|
|
|
Now, you can run <CODE>make</CODE> in that directory. You need not repeat the
|
|
configuration steps shown above, when ordinary source files change. You
|
|
must, however, run <CODE>configure</CODE> again when the configuration files
|
|
change, if your system does not support symbolic links.
|
|
</P><P>
|
|
|
|
<A NAME="Cross-Compiler"></A>
|
|
<HR SIZE="6">
|
|
<A NAME="SEC50"></A>
|
|
<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
|
|
<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC49" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC49"> < </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC51" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC51"> > </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC57" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC57"> << </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC46" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC46"> Up </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC57" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC57"> >> </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc.html#SEC_Top" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc.html#SEC_Top">Top</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_toc.html#SEC_Contents" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_toc.html#SEC_Contents">Contents</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_24.html#SEC261" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_24.html#SEC261">Index</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_abt.html#SEC_About" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_abt.html#SEC_About"> ? </A>]</TD>
|
|
</TR></TABLE>
|
|
<H2> 3.4 Building and Installing a Cross-Compiler </H2>
|
|
<!--docid::SEC50::-->
|
|
<P>
|
|
|
|
GNU CC can function as a cross-compiler for many machines, but not all.
|
|
</P><P>
|
|
|
|
<UL>
|
|
<LI>
|
|
Cross-compilers for the Mips as target using the Mips assembler
|
|
currently do not work, because the auxiliary programs
|
|
<TT>`mips-tdump.c'</TT> and <TT>`mips-tfile.c'</TT> 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.
|
|
<P>
|
|
|
|
<LI>
|
|
Cross-compilers between machines with different floating point formats
|
|
have not all been made to work. GNU CC now has a floating point
|
|
emulator with which these can work, but each target machine description
|
|
needs to be updated to take advantage of it.
|
|
<P>
|
|
|
|
<LI>
|
|
Cross-compilation between machines of different word sizes is
|
|
somewhat problematic and sometimes does not work.
|
|
</UL>
|
|
<P>
|
|
|
|
Since GNU CC generates assembler code, you probably need a
|
|
cross-assembler that GNU CC can run, in order to produce object files.
|
|
If you want to link on other than the target machine, you need a
|
|
cross-linker as well. You also need header files and libraries suitable
|
|
for the target machine that you can install on the host machine.
|
|
</P><P>
|
|
|
|
<BLOCKQUOTE><TABLE BORDER=0 CELLSPACING=0>
|
|
<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="gcc_3.html#SEC51" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC51">3.4.1 Steps of Cross-Compilation</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP">Using a cross-compiler involves several steps
|
|
that may be carried out on different machines.</TD></TR>
|
|
<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="gcc_3.html#SEC52" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC52">3.4.2 Configuring a Cross-Compiler</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP">Configuring a cross-compiler.</TD></TR>
|
|
<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="gcc_3.html#SEC53" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC53">3.4.3 Tools and Libraries for a Cross-Compiler</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP">Where to put the linker and assembler, and the C library.</TD></TR>
|
|
<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="gcc_3.html#SEC55" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC55">3.4.5 Cross-Compilers and Header Files</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP">Finding and installing header files
|
|
for a cross-compiler.</TD></TR>
|
|
<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="gcc_3.html#SEC54" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC54">3.4.4 <TT>`libgcc.a'</TT> and Cross-Compilers</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP">Supplying arithmetic runtime routines (<TT>`libgcc1.a'</TT>).</TD></TR>
|
|
<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="gcc_3.html#SEC56" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC56">3.4.6 Actually Building the Cross-Compiler</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP">Actually compiling the cross-compiler.</TD></TR>
|
|
</TABLE></BLOCKQUOTE>
|
|
<P>
|
|
|
|
<A NAME="Steps of Cross"></A>
|
|
<HR SIZE="6">
|
|
<A NAME="SEC51"></A>
|
|
<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
|
|
<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC50" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC50"> < </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC52" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC52"> > </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC57" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC57"> << </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC50" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC50"> Up </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC57" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC57"> >> </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc.html#SEC_Top" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc.html#SEC_Top">Top</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_toc.html#SEC_Contents" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_toc.html#SEC_Contents">Contents</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_24.html#SEC261" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_24.html#SEC261">Index</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_abt.html#SEC_About" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_abt.html#SEC_About"> ? </A>]</TD>
|
|
</TR></TABLE>
|
|
<H3> 3.4.1 Steps of Cross-Compilation </H3>
|
|
<!--docid::SEC51::-->
|
|
<P>
|
|
|
|
To compile and run a program using a cross-compiler involves several
|
|
steps:
|
|
</P><P>
|
|
|
|
<UL>
|
|
<LI>
|
|
Run the cross-compiler on the host machine to produce assembler files
|
|
for the target machine. This requires header files for the target
|
|
machine.
|
|
<P>
|
|
|
|
<LI>
|
|
Assemble the files produced by the cross-compiler. You can do this
|
|
either with an assembler on the target machine, or with a
|
|
cross-assembler on the host machine.
|
|
<P>
|
|
|
|
<LI>
|
|
Link those files to make an executable. You can do this either with a
|
|
linker on the target machine, or with a cross-linker on the host
|
|
machine. Whichever machine you use, you need libraries and certain
|
|
startup files (typically <TT>`crt<small>...</small>.o'</TT>) for the target machine.
|
|
</UL>
|
|
<P>
|
|
|
|
It is most convenient to do all of these steps on the same host machine,
|
|
since then you can do it all with a single invocation of GNU CC. This
|
|
requires a suitable cross-assembler and cross-linker. For some targets,
|
|
the GNU assembler and linker are available.
|
|
</P><P>
|
|
|
|
<A NAME="Configure Cross"></A>
|
|
<HR SIZE="6">
|
|
<A NAME="SEC52"></A>
|
|
<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
|
|
<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC51" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC51"> < </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC53" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC53"> > </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC53" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC53"> << </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC50" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC50"> Up </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC57" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC57"> >> </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc.html#SEC_Top" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc.html#SEC_Top">Top</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_toc.html#SEC_Contents" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_toc.html#SEC_Contents">Contents</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_24.html#SEC261" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_24.html#SEC261">Index</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_abt.html#SEC_About" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_abt.html#SEC_About"> ? </A>]</TD>
|
|
</TR></TABLE>
|
|
<H3> 3.4.2 Configuring a Cross-Compiler </H3>
|
|
<!--docid::SEC52::-->
|
|
<P>
|
|
|
|
To build GNU CC as a cross-compiler, you start out by running
|
|
<TT>`configure'</TT>. Use the <SAMP>`--target=<VAR>target</VAR>'</SAMP> to specify the
|
|
target type. If <TT>`configure'</TT> was unable to correctly identify the
|
|
system you are running on, also specify the <SAMP>`--build=<VAR>build</VAR>'</SAMP>
|
|
option. For example, here is how to configure for a cross-compiler that
|
|
produces code for an HP 68030 system running BSD on a system that
|
|
<TT>`configure'</TT> can correctly identify:
|
|
</P><P>
|
|
|
|
<TABLE><tr><td> </td><td class=smallexample><FONT SIZE=-1><pre>./configure --target=m68k-hp-bsd4.3
|
|
</FONT></pre></td></tr></table></P><P>
|
|
|
|
<A NAME="Tools and Libraries"></A>
|
|
<HR SIZE="6">
|
|
<A NAME="SEC53"></A>
|
|
<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
|
|
<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC52" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC52"> < </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC54" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC54"> > </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC54" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC54"> << </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC50" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC50"> Up </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC57" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC57"> >> </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc.html#SEC_Top" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc.html#SEC_Top">Top</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_toc.html#SEC_Contents" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_toc.html#SEC_Contents">Contents</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_24.html#SEC261" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_24.html#SEC261">Index</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_abt.html#SEC_About" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_abt.html#SEC_About"> ? </A>]</TD>
|
|
</TR></TABLE>
|
|
<H3> 3.4.3 Tools and Libraries for a Cross-Compiler </H3>
|
|
<!--docid::SEC53::-->
|
|
<P>
|
|
|
|
If you have a cross-assembler and cross-linker available, you should
|
|
install them now. Put them in the directory
|
|
<TT>`/usr/local/<VAR>target</VAR>/bin'</TT>. Here is a table of the tools
|
|
you should put in this directory:
|
|
</P><P>
|
|
|
|
<DL COMPACT>
|
|
<DT><TT>`as'</TT>
|
|
<DD>This should be the cross-assembler.
|
|
<P>
|
|
|
|
<DT><TT>`ld'</TT>
|
|
<DD>This should be the cross-linker.
|
|
<P>
|
|
|
|
<DT><TT>`ar'</TT>
|
|
<DD>This should be the cross-archiver: a program which can manipulate
|
|
archive files (linker libraries) in the target machine's format.
|
|
<P>
|
|
|
|
<DT><TT>`ranlib'</TT>
|
|
<DD>This should be a program to construct a symbol table in an archive file.
|
|
</DL>
|
|
<P>
|
|
|
|
The installation of GNU CC will find these programs in that directory,
|
|
and copy or link them to the proper place to for the cross-compiler to
|
|
find them when run later.
|
|
</P><P>
|
|
|
|
The easiest way to provide these files is to build the Binutils package
|
|
and GAS. Configure them with the same <SAMP>`--host'</SAMP> and <SAMP>`--target'</SAMP>
|
|
options that you use for configuring GNU CC, then build and install
|
|
them. They install their executables automatically into the proper
|
|
directory. Alas, they do not support all the targets that GNU CC
|
|
supports.
|
|
</P><P>
|
|
|
|
If you want to install libraries to use with the cross-compiler, such as
|
|
a standard C library, put them in the directory
|
|
<TT>`/usr/local/<VAR>target</VAR>/lib'</TT>; 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:
|
|
</P><P>
|
|
|
|
<TABLE><tr><td> </td><td class=example><pre>ftp <VAR>target-machine</VAR>
|
|
lcd /usr/local/<VAR>target</VAR>/lib
|
|
cd /lib
|
|
get libc.a
|
|
cd /usr/lib
|
|
get libg.a
|
|
get libm.a
|
|
quit
|
|
</pre></td></tr></table></P><P>
|
|
|
|
The precise set of libraries you'll need, and their locations on
|
|
the target machine, vary depending on its operating system.
|
|
</P><P>
|
|
|
|
<A NAME="IDX251"></A>
|
|
Many targets require "start files" such as <TT>`crt0.o'</TT> and
|
|
<TT>`crtn.o'</TT> which are linked into each executable; these too should be
|
|
placed in <TT>`/usr/local/<VAR>target</VAR>/lib'</TT>. There may be several
|
|
alternatives for <TT>`crt0.o'</TT>, for use with profiling or other
|
|
compilation options. Check your target's definition of
|
|
<CODE>STARTFILE_SPEC</CODE> to find out what start files it uses.
|
|
Here's an example of copying these files from a target machine:
|
|
</P><P>
|
|
|
|
<TABLE><tr><td> </td><td class=example><pre>ftp <VAR>target-machine</VAR>
|
|
lcd /usr/local/<VAR>target</VAR>/lib
|
|
prompt
|
|
cd /lib
|
|
mget *crt*.o
|
|
cd /usr/lib
|
|
mget *crt*.o
|
|
quit
|
|
</pre></td></tr></table></P><P>
|
|
|
|
<A NAME="Cross Runtime"></A>
|
|
<HR SIZE="6">
|
|
<A NAME="SEC54"></A>
|
|
<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
|
|
<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC53" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC53"> < </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC55" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC55"> > </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC55" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC55"> << </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC50" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC50"> Up </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC57" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC57"> >> </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc.html#SEC_Top" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc.html#SEC_Top">Top</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_toc.html#SEC_Contents" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_toc.html#SEC_Contents">Contents</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_24.html#SEC261" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_24.html#SEC261">Index</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_abt.html#SEC_About" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_abt.html#SEC_About"> ? </A>]</TD>
|
|
</TR></TABLE>
|
|
<H3> 3.4.4 <TT>`libgcc.a'</TT> and Cross-Compilers </H3>
|
|
<!--docid::SEC54::-->
|
|
<P>
|
|
|
|
Code compiled by GNU CC uses certain runtime support functions
|
|
implicitly. Some of these functions can be compiled successfully with
|
|
GNU CC itself, but a few cannot be. These problem functions are in the
|
|
source file <TT>`libgcc1.c'</TT>; the library made from them is called
|
|
<TT>`libgcc1.a'</TT>.
|
|
</P><P>
|
|
|
|
When you build a native compiler, these functions are compiled with some
|
|
other compiler--the one that you use for bootstrapping GNU CC.
|
|
Presumably it knows how to open code these operations, or else knows how
|
|
to call the run-time emulation facilities that the machine comes with.
|
|
But this approach doesn't work for building a cross-compiler. The
|
|
compiler that you use for building knows about the host system, not the
|
|
target system.
|
|
</P><P>
|
|
|
|
So, when you build a cross-compiler you have to supply a suitable
|
|
library <TT>`libgcc1.a'</TT> that does the job it is expected to do.
|
|
</P><P>
|
|
|
|
To compile <TT>`libgcc1.c'</TT> with the cross-compiler itself does not
|
|
work. The functions in this file are supposed to implement arithmetic
|
|
operations that GNU CC does not know how to open code for your target
|
|
machine. If these functions are compiled with GNU CC itself, they
|
|
will compile into infinite recursion.
|
|
</P><P>
|
|
|
|
On any given target, most of these functions are not needed. If GNU CC
|
|
can open code an arithmetic operation, it will not call these functions
|
|
to perform the operation. It is possible that on your target machine,
|
|
none of these functions is needed. If so, you can supply an empty
|
|
library as <TT>`libgcc1.a'</TT>.
|
|
</P><P>
|
|
|
|
Many targets need library support only for multiplication and division.
|
|
If you are linking with a library that contains functions for
|
|
multiplication and division, you can tell GNU CC to call them directly
|
|
by defining the macros <CODE>MULSI3_LIBCALL</CODE>, and the like. These
|
|
macros need to be defined in the target description macro file. For
|
|
some targets, they are defined already. This may be sufficient to
|
|
avoid the need for libgcc1.a; if so, you can supply an empty library.
|
|
</P><P>
|
|
|
|
Some targets do not have floating point instructions; they need other
|
|
functions in <TT>`libgcc1.a'</TT>, which do floating arithmetic.
|
|
Recent versions of GNU CC have a file which emulates floating point.
|
|
With a certain amount of work, you should be able to construct a
|
|
floating point emulator that can be used as <TT>`libgcc1.a'</TT>. Perhaps
|
|
future versions will contain code to do this automatically and
|
|
conveniently. That depends on whether someone wants to implement it.
|
|
</P><P>
|
|
|
|
Some embedded targets come with all the necessary <TT>`libgcc1.a'</TT>
|
|
routines written in C or assembler. These targets build
|
|
<TT>`libgcc1.a'</TT> automatically and you do not need to do anything
|
|
special for them. Other embedded targets do not need any
|
|
<TT>`libgcc1.a'</TT> routines since all the necessary operations are
|
|
supported by the hardware.
|
|
</P><P>
|
|
|
|
If your target system has another C compiler, you can configure GNU CC
|
|
as a native compiler on that machine, build just <TT>`libgcc1.a'</TT> with
|
|
<SAMP>`make libgcc1.a'</SAMP> on that machine, and use the resulting file with
|
|
the cross-compiler. To do this, execute the following on the target
|
|
machine:
|
|
</P><P>
|
|
|
|
<TABLE><tr><td> </td><td class=example><pre>cd <VAR>target-build-dir</VAR>
|
|
./configure --host=sparc --target=sun3
|
|
make libgcc1.a
|
|
</pre></td></tr></table></P><P>
|
|
|
|
And then this on the host machine:
|
|
</P><P>
|
|
|
|
<TABLE><tr><td> </td><td class=example><pre>ftp <VAR>target-machine</VAR>
|
|
binary
|
|
cd <VAR>target-build-dir</VAR>
|
|
get libgcc1.a
|
|
quit
|
|
</pre></td></tr></table></P><P>
|
|
|
|
Another way to provide the functions you need in <TT>`libgcc1.a'</TT> is to
|
|
define the appropriate <CODE>perform_<small>...</small></CODE> macros for those
|
|
functions. If these definitions do not use the C arithmetic operators
|
|
that they are meant to implement, you should be able to compile them
|
|
with the cross-compiler you are building. (If these definitions already
|
|
exist for your target file, then you are all set.)
|
|
</P><P>
|
|
|
|
To build <TT>`libgcc1.a'</TT> using the perform macros, use
|
|
<SAMP>`LIBGCC1=libgcc1.a OLDCC=./xgcc'</SAMP> when building the compiler.
|
|
Otherwise, you should place your replacement library under the name
|
|
<TT>`libgcc1.a'</TT> in the directory in which you will build the
|
|
cross-compiler, before you run <CODE>make</CODE>.
|
|
</P><P>
|
|
|
|
<A NAME="Cross Headers"></A>
|
|
<HR SIZE="6">
|
|
<A NAME="SEC55"></A>
|
|
<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
|
|
<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC54" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC54"> < </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC56" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC56"> > </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC56" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC56"> << </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC50" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC50"> Up </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC57" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC57"> >> </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc.html#SEC_Top" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc.html#SEC_Top">Top</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_toc.html#SEC_Contents" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_toc.html#SEC_Contents">Contents</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_24.html#SEC261" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_24.html#SEC261">Index</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_abt.html#SEC_About" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_abt.html#SEC_About"> ? </A>]</TD>
|
|
</TR></TABLE>
|
|
<H3> 3.4.5 Cross-Compilers and Header Files </H3>
|
|
<!--docid::SEC55::-->
|
|
<P>
|
|
|
|
If you are cross-compiling a standalone program or a program for an
|
|
embedded system, then you may not need any header files except the few
|
|
that are part of GNU CC (and those of your program). However, if you
|
|
intend to link your program with a standard C library such as
|
|
<TT>`libc.a'</TT>, then you probably need to compile with the header files
|
|
that go with the library you use.
|
|
</P><P>
|
|
|
|
The GNU C compiler does not come with these files, because (1) they are
|
|
system-specific, and (2) they belong in a C library, not in a compiler.
|
|
</P><P>
|
|
|
|
If the GNU C library supports your target machine, then you can get the
|
|
header files from there (assuming you actually use the GNU library when
|
|
you link your program).
|
|
</P><P>
|
|
|
|
If your target machine comes with a C compiler, it probably comes with
|
|
suitable header files also. If you make these files accessible from the host
|
|
machine, the cross-compiler can use them also.
|
|
</P><P>
|
|
|
|
Otherwise, you're on your own in finding header files to use when
|
|
cross-compiling.
|
|
</P><P>
|
|
|
|
When you have found suitable header files, put them in the directory
|
|
<TT>`/usr/local/<VAR>target</VAR>/include'</TT>, 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.
|
|
</P><P>
|
|
|
|
Provide the header files before you build the cross-compiler, because
|
|
the build stage actually runs the cross-compiler to produce parts of
|
|
<TT>`libgcc.a'</TT>. (These are the parts that <EM>can</EM> be compiled with
|
|
GNU CC.) Some of them need suitable header files.
|
|
</P><P>
|
|
|
|
Here's an example showing how to copy the header files from a target
|
|
machine. On the target machine, do this:
|
|
</P><P>
|
|
|
|
<TABLE><tr><td> </td><td class=example><pre>(cd /usr/include; tar cf - .) > tarfile
|
|
</pre></td></tr></table></P><P>
|
|
|
|
Then, on the host machine, do this:
|
|
</P><P>
|
|
|
|
<TABLE><tr><td> </td><td class=example><pre>ftp <VAR>target-machine</VAR>
|
|
lcd /usr/local/<VAR>target</VAR>/include
|
|
get tarfile
|
|
quit
|
|
tar xf tarfile
|
|
</pre></td></tr></table></P><P>
|
|
|
|
<A NAME="Build Cross"></A>
|
|
<HR SIZE="6">
|
|
<A NAME="SEC56"></A>
|
|
<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
|
|
<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC55" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC55"> < </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC57" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC57"> > </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC57" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC57"> << </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC50" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC50"> Up </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC57" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC57"> >> </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc.html#SEC_Top" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc.html#SEC_Top">Top</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_toc.html#SEC_Contents" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_toc.html#SEC_Contents">Contents</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_24.html#SEC261" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_24.html#SEC261">Index</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_abt.html#SEC_About" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_abt.html#SEC_About"> ? </A>]</TD>
|
|
</TR></TABLE>
|
|
<H3> 3.4.6 Actually Building the Cross-Compiler </H3>
|
|
<!--docid::SEC56::-->
|
|
<P>
|
|
|
|
Now you can proceed just as for compiling a single-machine compiler
|
|
through the step of building stage 1. If you have not provided some
|
|
sort of <TT>`libgcc1.a'</TT>, then compilation will give up at the point
|
|
where it needs that file, printing a suitable error message. If you
|
|
do provide <TT>`libgcc1.a'</TT>, then building the compiler will automatically
|
|
compile and link a test program called <TT>`libgcc1-test'</TT>; if you get
|
|
errors in the linking, it means that not all of the necessary routines
|
|
in <TT>`libgcc1.a'</TT> are available.
|
|
</P><P>
|
|
|
|
You must provide the header file <TT>`float.h'</TT>. One way to do this is
|
|
to compile <TT>`enquire'</TT> and run it on your target machine. The job of
|
|
<TT>`enquire'</TT> is to run on the target machine and figure out by
|
|
experiment the nature of its floating point representation.
|
|
<TT>`enquire'</TT> records its findings in the header file <TT>`float.h'</TT>.
|
|
If you can't produce this file by running <TT>`enquire'</TT> on the target
|
|
machine, then you will need to come up with a suitable <TT>`float.h'</TT> in
|
|
some other way (or else, avoid using it in your programs).
|
|
</P><P>
|
|
|
|
Do not try to build stage 2 for a cross-compiler. It doesn't work to
|
|
rebuild GNU CC as a cross-compiler using the cross-compiler, because
|
|
that would produce a program that runs on the target machine, not on the
|
|
host. For example, if you compile a 386-to-68030 cross-compiler with
|
|
itself, the result will not be right either for the 386 (because it was
|
|
compiled into 68030 code) or for the 68030 (because it was configured
|
|
for a 386 as the host). If you want to compile GNU CC into 68030 code,
|
|
whether you compile it on a 68030 or with a cross-compiler on a 386, you
|
|
must specify a 68030 as the host when you configure it.
|
|
</P><P>
|
|
|
|
To install the cross-compiler, use <SAMP>`make install'</SAMP>, as usual.
|
|
</P><P>
|
|
|
|
<A NAME="Sun Install"></A>
|
|
<HR SIZE="6">
|
|
<A NAME="SEC57"></A>
|
|
<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
|
|
<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC56" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC56"> < </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC58" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC58"> > </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC58" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC58"> << </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC46" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC46"> Up </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_4.html#SEC61" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_4.html#SEC61"> >> </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc.html#SEC_Top" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc.html#SEC_Top">Top</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_toc.html#SEC_Contents" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_toc.html#SEC_Contents">Contents</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_24.html#SEC261" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_24.html#SEC261">Index</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_abt.html#SEC_About" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_abt.html#SEC_About"> ? </A>]</TD>
|
|
</TR></TABLE>
|
|
<H2> 3.5 Installing GNU CC on the Sun </H2>
|
|
<!--docid::SEC57::-->
|
|
<P>
|
|
|
|
On Solaris, do not use the linker or other tools in
|
|
<TT>`/usr/ucb'</TT> to build GNU CC. Use <CODE>/usr/ccs/bin</CODE>.
|
|
</P><P>
|
|
|
|
If the assembler reports <SAMP>`Error: misaligned data'</SAMP> when bootstrapping,
|
|
you are probably using an obsolete version of the GNU assembler. Upgrade
|
|
to the latest version of GNU <CODE>binutils</CODE>, or use the Solaris assembler.
|
|
</P><P>
|
|
|
|
Make sure the environment variable <CODE>FLOAT_OPTION</CODE> is not set when
|
|
you compile <TT>`libgcc.a'</TT>. If this option were set to <CODE>f68881</CODE>
|
|
when <TT>`libgcc.a'</TT> is compiled, the resulting code would demand to be
|
|
linked with a special startup file and would not link properly without
|
|
special pains.
|
|
</P><P>
|
|
|
|
<A NAME="IDX252"></A>
|
|
There is a bug in <CODE>alloca</CODE> in certain versions of the Sun library.
|
|
To avoid this bug, install the binaries of GNU CC that were compiled by
|
|
GNU CC. They use <CODE>alloca</CODE> as a built-in function and never the one
|
|
in the library.
|
|
</P><P>
|
|
|
|
Some versions of the Sun compiler crash when compiling GNU CC. The
|
|
problem is a segmentation fault in cpp. This problem seems to be due to
|
|
the bulk of data in the environment variables. You may be able to avoid
|
|
it by using the following command to compile GNU CC with Sun CC:
|
|
</P><P>
|
|
|
|
<TABLE><tr><td> </td><td class=example><pre>make CC="TERMCAP=x OBJS=x LIBFUNCS=x STAGESTUFF=x cc"
|
|
</pre></td></tr></table></P><P>
|
|
|
|
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.
|
|
</P><P>
|
|
|
|
<A NAME="VMS Install"></A>
|
|
<HR SIZE="6">
|
|
<A NAME="SEC58"></A>
|
|
<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
|
|
<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC57" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC57"> < </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC59" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC59"> > </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC59" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC59"> << </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC46" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC46"> Up </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_4.html#SEC61" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_4.html#SEC61"> >> </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc.html#SEC_Top" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc.html#SEC_Top">Top</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_toc.html#SEC_Contents" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_toc.html#SEC_Contents">Contents</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_24.html#SEC261" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_24.html#SEC261">Index</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_abt.html#SEC_About" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_abt.html#SEC_About"> ? </A>]</TD>
|
|
</TR></TABLE>
|
|
<H2> 3.6 Installing GNU CC on VMS </H2>
|
|
<!--docid::SEC58::-->
|
|
<P>
|
|
|
|
The VMS version of GNU CC is distributed in a backup saveset containing
|
|
both source code and precompiled binaries.
|
|
</P><P>
|
|
|
|
To install the <TT>`gcc'</TT> command so you can use the compiler easily, in
|
|
the same manner as you use the VMS C compiler, you must install the VMS CLD
|
|
file for GNU CC as follows:
|
|
</P><P>
|
|
|
|
<OL>
|
|
<LI>
|
|
Define the VMS logical names <SAMP>`GNU_CC'</SAMP> and <SAMP>`GNU_CC_INCLUDE'</SAMP>
|
|
to point to the directories where the GNU CC executables
|
|
(<TT>`gcc-cpp.exe'</TT>, <TT>`gcc-cc1.exe'</TT>, etc.) and the C include files are
|
|
kept respectively. This should be done with the commands:<P>
|
|
|
|
<TABLE><tr><td> </td><td class=smallexample><FONT SIZE=-1><pre>$ assign /system /translation=concealed -
|
|
disk:[gcc.] gnu_cc
|
|
$ assign /system /translation=concealed -
|
|
disk:[gcc.include.] gnu_cc_include
|
|
</FONT></pre></td></tr></table></P><P>
|
|
|
|
with the appropriate disk and directory names. These commands can be
|
|
placed in your system startup file so they will be executed whenever
|
|
the machine is rebooted. You may, if you choose, do this via the
|
|
<TT>`GCC_INSTALL.COM'</TT> script in the <TT>`[GCC]'</TT> directory.
|
|
</P><P>
|
|
|
|
<LI>
|
|
Install the <TT>`GCC'</TT> command with the command line:
|
|
<P>
|
|
|
|
<TABLE><tr><td> </td><td class=smallexample><FONT SIZE=-1><pre>$ set command /table=sys$common:[syslib]dcltables -
|
|
/output=sys$common:[syslib]dcltables gnu_cc:[000000]gcc
|
|
$ install replace sys$common:[syslib]dcltables
|
|
</FONT></pre></td></tr></table></P><P>
|
|
|
|
<LI>
|
|
To install the help file, do the following:
|
|
<P>
|
|
|
|
<TABLE><tr><td> </td><td class=smallexample><FONT SIZE=-1><pre>$ library/help sys$library:helplib.hlb gcc.hlp
|
|
</FONT></pre></td></tr></table></P><P>
|
|
|
|
Now you can invoke the compiler with a command like <SAMP>`gcc /verbose
|
|
file.c'</SAMP>, which is equivalent to the command <SAMP>`gcc -v -c file.c'</SAMP> in
|
|
Unix.
|
|
</OL>
|
|
<P>
|
|
|
|
If you wish to use GNU C++ you must first install GNU CC, and then
|
|
perform the following steps:
|
|
</P><P>
|
|
|
|
<OL>
|
|
<LI>
|
|
Define the VMS logical name <SAMP>`GNU_GXX_INCLUDE'</SAMP> to point to the
|
|
directory where the preprocessor will search for the C++ header files.
|
|
This can be done with the command:<P>
|
|
|
|
<TABLE><tr><td> </td><td class=smallexample><FONT SIZE=-1><pre>$ assign /system /translation=concealed -
|
|
disk:[gcc.gxx_include.] gnu_gxx_include
|
|
</FONT></pre></td></tr></table></P><P>
|
|
|
|
with the appropriate disk and directory name. If you are going to be
|
|
using a C++ runtime library, this is where its install procedure will install
|
|
its header files.
|
|
</P><P>
|
|
|
|
<LI>
|
|
Obtain the file <TT>`gcc-cc1plus.exe'</TT>, and place this in the same
|
|
directory that <TT>`gcc-cc1.exe'</TT> is kept.
|
|
<P>
|
|
|
|
The GNU C++ compiler can be invoked with a command like <SAMP>`gcc /plus
|
|
/verbose file.cc'</SAMP>, which is equivalent to the command <SAMP>`g++ -v -c
|
|
file.cc'</SAMP> in Unix.
|
|
</OL>
|
|
<P>
|
|
|
|
We try to put corresponding binaries and sources on the VMS distribution
|
|
tape. But sometimes the binaries will be from an older version than the
|
|
sources, because we don't always have time to update them. (Use the
|
|
<SAMP>`/version'</SAMP> option to determine the version number of the binaries and
|
|
compare it with the source file <TT>`version.c'</TT> to tell whether this is
|
|
so.) In this case, you should use the binaries you get to recompile the
|
|
sources. If you must recompile, here is how:
|
|
</P><P>
|
|
|
|
<OL>
|
|
<LI>
|
|
Execute the command procedure <TT>`vmsconfig.com'</TT> to set up the files
|
|
<TT>`tm.h'</TT>, <TT>`config.h'</TT>, <TT>`aux-output.c'</TT>, and <TT>`md.'</TT>, and
|
|
to create files <TT>`tconfig.h'</TT> and <TT>`hconfig.h'</TT>. This procedure
|
|
also creates several linker option files used by <TT>`make-cc1.com'</TT> and
|
|
a data file used by <TT>`make-l2.com'</TT>.<P>
|
|
|
|
<TABLE><tr><td> </td><td class=smallexample><FONT SIZE=-1><pre>$ @vmsconfig.com
|
|
</FONT></pre></td></tr></table></P><P>
|
|
|
|
<LI>
|
|
Setup the logical names and command tables as defined above. In
|
|
addition, define the VMS logical name <SAMP>`GNU_BISON'</SAMP> to point at the
|
|
to the directories where the Bison executable is kept. This should be
|
|
done with the command:<P>
|
|
|
|
<TABLE><tr><td> </td><td class=smallexample><FONT SIZE=-1><pre>$ assign /system /translation=concealed -
|
|
disk:[bison.] gnu_bison
|
|
</FONT></pre></td></tr></table></P><P>
|
|
|
|
You may, if you choose, use the <TT>`INSTALL_BISON.COM'</TT> script in the
|
|
<TT>`[BISON]'</TT> directory.
|
|
</P><P>
|
|
|
|
<LI>
|
|
Install the <SAMP>`BISON'</SAMP> command with the command line:<P>
|
|
|
|
<TABLE><tr><td> </td><td class=smallexample><FONT SIZE=-1><pre>$ set command /table=sys$common:[syslib]dcltables -
|
|
/output=sys$common:[syslib]dcltables -
|
|
gnu_bison:[000000]bison
|
|
$ install replace sys$common:[syslib]dcltables
|
|
</FONT></pre></td></tr></table></P><P>
|
|
|
|
<LI>
|
|
Type <SAMP>`@make-gcc'</SAMP> to recompile everything (alternatively, submit
|
|
the file <TT>`make-gcc.com'</TT> to a batch queue). If you wish to build
|
|
the GNU C++ compiler as well as the GNU CC compiler, you must first edit
|
|
<TT>`make-gcc.com'</TT> and follow the instructions that appear in the
|
|
comments.<P>
|
|
|
|
<LI>
|
|
In order to use GCC, you need a library of functions which GCC compiled code
|
|
will call to perform certain tasks, and these functions are defined in the
|
|
file <TT>`libgcc2.c'</TT>. To compile this you should use the command procedure
|
|
<TT>`make-l2.com'</TT>, which will generate the library <TT>`libgcc2.olb'</TT>.
|
|
<TT>`libgcc2.olb'</TT> should be built using the compiler built from
|
|
the same distribution that <TT>`libgcc2.c'</TT> came from, and
|
|
<TT>`make-gcc.com'</TT> will automatically do all of this for you.
|
|
<P>
|
|
|
|
To install the library, use the following commands:</P><P>
|
|
|
|
<TABLE><tr><td> </td><td class=smallexample><FONT SIZE=-1><pre>$ library gnu_cc:[000000]gcclib/delete=(new,eprintf)
|
|
$ library gnu_cc:[000000]gcclib/delete=L_*
|
|
$ library libgcc2/extract=*/output=libgcc2.obj
|
|
$ library gnu_cc:[000000]gcclib libgcc2.obj
|
|
</FONT></pre></td></tr></table></P><P>
|
|
|
|
The first command simply removes old modules that will be replaced with
|
|
modules from <TT>`libgcc2'</TT> under different module names. The modules
|
|
<CODE>new</CODE> and <CODE>eprintf</CODE> may not actually be present in your
|
|
<TT>`gcclib.olb'</TT>---if the VMS librarian complains about those modules
|
|
not being present, simply ignore the message and continue on with the
|
|
next command. The second command removes the modules that came from the
|
|
previous version of the library <TT>`libgcc2.c'</TT>.
|
|
</P><P>
|
|
|
|
Whenever you update the compiler on your system, you should also update the
|
|
library with the above procedure.
|
|
</P><P>
|
|
|
|
<LI>
|
|
You may wish to build GCC in such a way that no files are written to the
|
|
directory where the source files reside. An example would be the when
|
|
the source files are on a read-only disk. In these cases, execute the
|
|
following DCL commands (substituting your actual path names):
|
|
<P>
|
|
|
|
<TABLE><tr><td> </td><td class=smallexample><FONT SIZE=-1><pre>$ assign dua0:[gcc.build_dir.]/translation=concealed, -
|
|
dua1:[gcc.source_dir.]/translation=concealed gcc_build
|
|
$ set default gcc_build:[000000]
|
|
</FONT></pre></td></tr></table></P><P>
|
|
|
|
where the directory <TT>`dua1:[gcc.source_dir]'</TT> contains the source
|
|
code, and the directory <TT>`dua0:[gcc.build_dir]'</TT> is meant to contain
|
|
all of the generated object files and executables. Once you have done
|
|
this, you can proceed building GCC as described above. (Keep in mind
|
|
that <TT>`gcc_build'</TT> is a rooted logical name, and thus the device
|
|
names in each element of the search list must be an actual physical
|
|
device name rather than another rooted logical name).
|
|
</P><P>
|
|
|
|
<LI>
|
|
<STRONG>If you are building GNU CC with a previous version of GNU CC,
|
|
you also should check to see that you have the newest version of the
|
|
assembler</STRONG>. In particular, GNU CC version 2 treats global constant
|
|
variables slightly differently from GNU CC version 1, and GAS version
|
|
1.38.1 does not have the patches required to work with GCC version 2.
|
|
If you use GAS 1.38.1, then <CODE>extern const</CODE> variables will not have
|
|
the read-only bit set, and the linker will generate warning messages
|
|
about mismatched psect attributes for these variables. These warning
|
|
messages are merely a nuisance, and can safely be ignored.
|
|
<P>
|
|
|
|
If you are compiling with a version of GNU CC older than 1.33, specify
|
|
<SAMP>`/DEFINE=("inline=")'</SAMP> as an option in all the compilations. This
|
|
requires editing all the <CODE>gcc</CODE> commands in <TT>`make-cc1.com'</TT>.
|
|
(The older versions had problems supporting <CODE>inline</CODE>.) Once you
|
|
have a working 1.33 or newer GNU CC, you can change this file back.
|
|
</P><P>
|
|
|
|
<LI>
|
|
If you want to build GNU CC with the VAX C compiler, you will need to
|
|
make minor changes in <TT>`make-cccp.com'</TT> and <TT>`make-cc1.com'</TT>
|
|
to choose alternate definitions of <CODE>CC</CODE>, <CODE>CFLAGS</CODE>, and
|
|
<CODE>LIBS</CODE>. See comments in those files. However, you must
|
|
also have a working version of the GNU assembler (GNU as, aka GAS) as
|
|
it is used as the back-end for GNU CC to produce binary object modules
|
|
and is not included in the GNU CC sources. GAS is also needed to
|
|
compile <TT>`libgcc2'</TT> in order to build <TT>`gcclib'</TT> (see above);
|
|
<TT>`make-l2.com'</TT> expects to be able to find it operational in
|
|
<TT>`gnu_cc:[000000]gnu-as.exe'</TT>.
|
|
<P>
|
|
|
|
To use GNU CC on VMS, you need the VMS driver programs
|
|
<TT>`gcc.exe'</TT>, <TT>`gcc.com'</TT>, and <TT>`gcc.cld'</TT>. They are
|
|
distributed with the VMS binaries (<TT>`gcc-vms'</TT>) rather than the
|
|
GNU CC sources. GAS is also included in <TT>`gcc-vms'</TT>, as is Bison.
|
|
</P><P>
|
|
|
|
Once you have successfully built GNU CC with VAX C, you should use the
|
|
resulting compiler to rebuild itself. Before doing this, be sure to
|
|
restore the <CODE>CC</CODE>, <CODE>CFLAGS</CODE>, and <CODE>LIBS</CODE> definitions in
|
|
<TT>`make-cccp.com'</TT> and <TT>`make-cc1.com'</TT>. The second generation
|
|
compiler will be able to take advantage of many optimizations that must
|
|
be suppressed when building with other compilers.
|
|
</OL>
|
|
<P>
|
|
|
|
Under previous versions of GNU CC, the generated code would occasionally
|
|
give strange results when linked with the sharable <TT>`VAXCRTL'</TT> library.
|
|
Now this should work.
|
|
</P><P>
|
|
|
|
Even with this version, however, GNU CC itself should not be linked with
|
|
the sharable <TT>`VAXCRTL'</TT>. The version of <CODE>qsort</CODE> in
|
|
<TT>`VAXCRTL'</TT> has a bug (known to be present in VMS versions V4.6
|
|
through V5.5) which causes the compiler to fail.
|
|
</P><P>
|
|
|
|
The executables are generated by <TT>`make-cc1.com'</TT> and
|
|
<TT>`make-cccp.com'</TT> use the object library version of <TT>`VAXCRTL'</TT> in
|
|
order to make use of the <CODE>qsort</CODE> routine in <TT>`gcclib.olb'</TT>. If
|
|
you wish to link the compiler executables with the shareable image
|
|
version of <TT>`VAXCRTL'</TT>, you should edit the file <TT>`tm.h'</TT> (created
|
|
by <TT>`vmsconfig.com'</TT>) to define the macro <CODE>QSORT_WORKAROUND</CODE>.
|
|
</P><P>
|
|
|
|
<CODE>QSORT_WORKAROUND</CODE> is always defined when GNU CC is compiled with
|
|
VAX C, to avoid a problem in case <TT>`gcclib.olb'</TT> is not yet
|
|
available.
|
|
</P><P>
|
|
|
|
<A NAME="Collect2"></A>
|
|
<HR SIZE="6">
|
|
<A NAME="SEC59"></A>
|
|
<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
|
|
<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC58" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC58"> < </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC60" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC60"> > </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC60" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC60"> << </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC46" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC46"> Up </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_4.html#SEC61" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_4.html#SEC61"> >> </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc.html#SEC_Top" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc.html#SEC_Top">Top</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_toc.html#SEC_Contents" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_toc.html#SEC_Contents">Contents</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_24.html#SEC261" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_24.html#SEC261">Index</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_abt.html#SEC_About" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_abt.html#SEC_About"> ? </A>]</TD>
|
|
</TR></TABLE>
|
|
<H2> 3.7 <CODE>collect2</CODE> </H2>
|
|
<!--docid::SEC59::-->
|
|
<P>
|
|
|
|
GNU CC uses a utility called <CODE>collect2</CODE> on nearly all systems to arrange
|
|
to call various initialization functions at start time.
|
|
</P><P>
|
|
|
|
The program <CODE>collect2</CODE> works by linking the program once and
|
|
looking through the linker output file for symbols with particular names
|
|
indicating they are constructor functions. If it finds any, it
|
|
creates a new temporary <SAMP>`.c'</SAMP> file containing a table of them,
|
|
compiles it, and links the program a second time including that file.
|
|
</P><P>
|
|
|
|
<A NAME="IDX253"></A>
|
|
<A NAME="IDX254"></A>
|
|
The actual calls to the constructors are carried out by a subroutine
|
|
called <CODE>__main</CODE>, which is called (automatically) at the beginning
|
|
of the body of <CODE>main</CODE> (provided <CODE>main</CODE> was compiled with GNU
|
|
CC). Calling <CODE>__main</CODE> is necessary, even when compiling C code, to
|
|
allow linking C and C++ object code together. (If you use
|
|
<SAMP>`-nostdlib'</SAMP>, you get an unresolved reference to <CODE>__main</CODE>,
|
|
since it's defined in the standard GCC library. Include <SAMP>`-lgcc'</SAMP> at
|
|
the end of your compiler command line to resolve this reference.)
|
|
</P><P>
|
|
|
|
The program <CODE>collect2</CODE> is installed as <CODE>ld</CODE> in the directory
|
|
where the passes of the compiler are installed. When <CODE>collect2</CODE>
|
|
needs to find the <EM>real</EM> <CODE>ld</CODE>, it tries the following file
|
|
names:
|
|
</P><P>
|
|
|
|
<UL>
|
|
<LI>
|
|
<TT>`real-ld'</TT> in the directories listed in the compiler's search
|
|
directories.
|
|
<P>
|
|
|
|
<LI>
|
|
<TT>`real-ld'</TT> in the directories listed in the environment variable
|
|
<CODE>PATH</CODE>.
|
|
<P>
|
|
|
|
<LI>
|
|
The file specified in the <CODE>REAL_LD_FILE_NAME</CODE> configuration macro,
|
|
if specified.
|
|
<P>
|
|
|
|
<LI>
|
|
<TT>`ld'</TT> in the compiler's search directories, except that
|
|
<CODE>collect2</CODE> will not execute itself recursively.
|
|
<P>
|
|
|
|
<LI>
|
|
<TT>`ld'</TT> in <CODE>PATH</CODE>.
|
|
</UL>
|
|
<P>
|
|
|
|
"The compiler's search directories" means all the directories where
|
|
<CODE>gcc</CODE> searches for passes of the compiler. This includes
|
|
directories that you specify with <SAMP>`-B'</SAMP>.
|
|
</P><P>
|
|
|
|
Cross-compilers search a little differently:
|
|
</P><P>
|
|
|
|
<UL>
|
|
<LI>
|
|
<TT>`real-ld'</TT> in the compiler's search directories.
|
|
<P>
|
|
|
|
<LI>
|
|
<TT>`<VAR>target</VAR>-real-ld'</TT> in <CODE>PATH</CODE>.
|
|
<P>
|
|
|
|
<LI>
|
|
The file specified in the <CODE>REAL_LD_FILE_NAME</CODE> configuration macro,
|
|
if specified.
|
|
<P>
|
|
|
|
<LI>
|
|
<TT>`ld'</TT> in the compiler's search directories.
|
|
<P>
|
|
|
|
<LI>
|
|
<TT>`<VAR>target</VAR>-ld'</TT> in <CODE>PATH</CODE>.
|
|
</UL>
|
|
<P>
|
|
|
|
<CODE>collect2</CODE> explicitly avoids running <CODE>ld</CODE> using the file name
|
|
under which <CODE>collect2</CODE> itself was invoked. In fact, it remembers
|
|
up a list of such names--in case one copy of <CODE>collect2</CODE> finds
|
|
another copy (or version) of <CODE>collect2</CODE> installed as <CODE>ld</CODE> in a
|
|
second place in the search path.
|
|
</P><P>
|
|
|
|
<CODE>collect2</CODE> searches for the utilities <CODE>nm</CODE> and <CODE>strip</CODE>
|
|
using the same algorithm as above for <CODE>ld</CODE>.
|
|
</P><P>
|
|
|
|
<A NAME="Header Dirs"></A>
|
|
<HR SIZE="6">
|
|
<A NAME="SEC60"></A>
|
|
<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
|
|
<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC59" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC59"> < </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_4.html#SEC61" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_4.html#SEC61"> > </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC46" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC46"> << </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC46" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC46"> Up </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_4.html#SEC61" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_4.html#SEC61"> >> </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc.html#SEC_Top" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc.html#SEC_Top">Top</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_toc.html#SEC_Contents" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_toc.html#SEC_Contents">Contents</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_24.html#SEC261" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_24.html#SEC261">Index</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_abt.html#SEC_About" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_abt.html#SEC_About"> ? </A>]</TD>
|
|
</TR></TABLE>
|
|
<H2> 3.8 Standard Header File Directories </H2>
|
|
<!--docid::SEC60::-->
|
|
<P>
|
|
|
|
<CODE>GCC_INCLUDE_DIR</CODE> means the same thing for native and cross. It is
|
|
where GNU CC stores its private include files, and also where GNU CC
|
|
stores the fixed include files. A cross compiled GNU CC runs
|
|
<CODE>fixincludes</CODE> on the header files in <TT>`$(tooldir)/include'</TT>.
|
|
(If the cross compilation header files need to be fixed, they must be
|
|
installed before GNU CC is built. If the cross compilation header files
|
|
are already suitable for ANSI C and GNU CC, nothing special need be
|
|
done).
|
|
</P><P>
|
|
|
|
<CODE>GPLUSPLUS_INCLUDE_DIR</CODE> means the same thing for native and cross. It
|
|
is where <CODE>g++</CODE> looks first for header files. The C++ library
|
|
installs only target independent header files in that directory.
|
|
</P><P>
|
|
|
|
<CODE>LOCAL_INCLUDE_DIR</CODE> is used only for a native compiler. It is
|
|
normally <TT>`/usr/local/include'</TT>. GNU CC searches this directory so
|
|
that users can install header files in <TT>`/usr/local/include'</TT>.
|
|
</P><P>
|
|
|
|
<CODE>CROSS_INCLUDE_DIR</CODE> is used only for a cross compiler. GNU CC
|
|
doesn't install anything there.
|
|
</P><P>
|
|
|
|
<CODE>TOOL_INCLUDE_DIR</CODE> is used for both native and cross compilers. It
|
|
is the place for other packages to install header files that GNU CC will
|
|
use. For a cross-compiler, this is the equivalent of
|
|
<TT>`/usr/include'</TT>. When you build a cross-compiler,
|
|
<CODE>fixincludes</CODE> processes any header files in this directory.
|
|
</P><P>
|
|
|
|
<A NAME="C Extensions"></A>
|
|
<HR SIZE="6">
|
|
<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
|
|
<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_3.html#SEC46" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_3.html#SEC46"> << </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_4.html#SEC61" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_4.html#SEC61"> >> </A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc.html#SEC_Top" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc.html#SEC_Top">Top</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_toc.html#SEC_Contents" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_toc.html#SEC_Contents">Contents</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_24.html#SEC261" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_24.html#SEC261">Index</A>]</TD>
|
|
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gcc_abt.html#SEC_About" tppabs="http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_abt.html#SEC_About"> ? </A>]</TD>
|
|
</TR></TABLE>
|
|
<BR>
|
|
<FONT SIZE="-1">
|
|
This document was generated
|
|
by <I>GCC Administrator</I> on <I>March, 17 2001</I>
|
|
using <A HREF="tppmsgs/msgs0.htm#1" tppabs="http://www.mathematik.uni-kl.de/~obachman/Texi2html"><I>texi2html</I></A>
|
|
|
|
</BODY>
|
|
</HTML>
|