619 lines
27 KiB
HTML
619 lines
27 KiB
HTML
<html lang="en">
|
|
<head>
|
|
<title>Installing GCC: Old documentation</title>
|
|
<meta http-equiv="Content-Type" content="text/html">
|
|
<meta name=description content="Installing GCC: Old documentation">
|
|
<meta name=generator content="makeinfo 4.2">
|
|
<link href="http://www.gnu.org/software/texinfo/" rel=generator-home>
|
|
<!--
|
|
Copyright © 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
|
|
1999, 2000, 2001, 2002, 2003 Free Software Foundation, Inc.
|
|
<br><p>
|
|
<p>Permission is granted to copy, distribute and/or modify this document
|
|
under the terms of the GNU Free Documentation License, Version 1.2 or
|
|
any later version published by the Free Software Foundation; with no
|
|
Invariant Sections, the Front-Cover texts being (a) (see below), and
|
|
with the Back-Cover Texts being (b) (see below). A copy of the
|
|
license is included in the section entitled "<a href="./gfdl.html">GNU Free Documentation License</a>".
|
|
|
|
<p>(a) The FSF's Front-Cover Text is:
|
|
|
|
<p>A GNU Manual
|
|
|
|
<p>(b) The FSF's Back-Cover Text is:
|
|
|
|
<p>You have freedom to copy and modify this GNU Manual, like GNU
|
|
software. Copies published by the Free Software Foundation raise
|
|
funds for GNU development.-->
|
|
</head>
|
|
<body>
|
|
<h1>Installing GCC: Old documentation</h1>
|
|
<h1 align="center">Old installation documentation</h1>
|
|
|
|
<p>Note most of this information is out of date and superseded by the
|
|
previous chapters of this manual. It is provided for historical
|
|
reference only, because of a lack of volunteers to merge it into the
|
|
main manual.
|
|
|
|
<p>Here is the procedure for installing GNU CC on a GNU or Unix system.
|
|
See <a href="#VMS%20Install">VMS Install</a>, for VMS systems.
|
|
|
|
<ol type=1 start=1>
|
|
</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
|
|
<code>as</code>, <code>ld</code> or whatever is appropriate.
|
|
|
|
<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><li>Specify the host, build and target machine configurations. You do this
|
|
when you run the <code>configure</code> script.
|
|
|
|
<p>The <dfn>build</dfn> machine is the system which you are using, the
|
|
<dfn>host</dfn> machine is the system where you want to run the resulting
|
|
compiler (normally the build machine), and the <dfn>target</dfn> machine is
|
|
the system for which you want the compiler to generate code.
|
|
|
|
<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 <code>configure</code>; 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
|
|
<code>configure</code> cannot figure out what your configuration is or guesses
|
|
wrong.
|
|
|
|
<p>In those cases, specify the build machine's <dfn>configuration name</dfn>
|
|
with the <code>--host</code> 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="#Cross-Compiler">Cross-Compiler</a>.)
|
|
|
|
<p>Here is an example:
|
|
|
|
<br><pre>./configure --host=sparc-sun-sunos4.1
|
|
</pre>
|
|
|
|
<p>A configuration name may be canonical or it may be more or less
|
|
abbreviated.
|
|
|
|
<p>A canonical configuration name has three parts, separated by dashes.
|
|
It looks like this: <code><var>cpu</var>-<var>company</var>-<var>system</var></code>.
|
|
(The three parts may themselves contain dashes; <code>configure</code>
|
|
can figure out which dashes serve which purpose.) For example,
|
|
<code>m68k-sun-sunos4.1</code> specifies a Sun 3.
|
|
|
|
<p>You can also replace parts of the configuration by nicknames or aliases.
|
|
For example, <code>sun3</code> stands for <code>m68k-sun</code>, so
|
|
<code>sun3-sunos4.1</code> is another way to specify a Sun 3.
|
|
|
|
<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>See <a href="#Configurations">Configurations</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.
|
|
|
|
</ol>
|
|
|
|
<h2><a name="Configurations"></a>Configurations Supported by GNU CC</h2>
|
|
|
|
<p>Here are the possible CPU types:
|
|
|
|
<blockquote>
|
|
1750a, a29k, alpha, arm, avr, c<var>n</var>, clipper, dsp16xx, elxsi, fr30, h8300,
|
|
hppa1.0, hppa1.1, i370, i386, i486, i586, i686, i786, i860, i960, ip2k, m32r,
|
|
m68000, m68k, m6811, m6812, m88k, mcore, mips, mipsel, mips64, mips64el,
|
|
mn10200, mn10300, ns32k, pdp11, powerpc, powerpcle, romp, rs6000, sh, sparc,
|
|
sparclite, sparc64, v850, vax, we32k.
|
|
</blockquote>
|
|
|
|
<p>Here are the recognized company names. As you can see, customary
|
|
abbreviations are used rather than the longer official names.
|
|
|
|
<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 <code><var>cpu</var>-<var>system</var></code>, if it is not needed. For example,
|
|
<code>vax-ultrix4.2</code> is equivalent to <code>vax-dec-ultrix4.2</code>.
|
|
|
|
<p>Here is a list of system types:
|
|
|
|
<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,
|
|
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 <code>configure</code> guesses the
|
|
operating system from the CPU and company.
|
|
|
|
<p>You can add a version number to the system type; this may or may not
|
|
make a difference. For example, you can write <code>bsd4.3</code> or
|
|
<code>bsd4.4</code> to distinguish versions of BSD. In practice, the version
|
|
number is most needed for <code>sysv3</code> and <code>sysv4</code>, which are often
|
|
treated differently.
|
|
|
|
<p><code>linux-gnu</code> is the canonical name for the GNU/Linux target; however
|
|
GNU CC will also accept <code>linux</code>. The version of the kernel in use is
|
|
not relevant on these systems. A suffix such as <code>libc1</code> or <code>aout</code>
|
|
distinguishes major versions of the C library; all of the suffixed versions
|
|
are obsolete.
|
|
|
|
<p>If you specify an impossible combination such as <code>i860-dg-vms</code>,
|
|
then you may get an error message from <code>configure</code>, or it may
|
|
ignore part of the information and do the best it can with the rest.
|
|
<code>configure</code> always prints the canonical name for the alternative
|
|
that it used. GNU CC does not support all possible alternatives.
|
|
|
|
<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 <code>sun3</code>, mentioned above, is an alias for <code>m68k-sun</code>.
|
|
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:
|
|
|
|
<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 <code>local</code> as the company name to access them. If you use
|
|
configuration <code><var>cpu</var>-local</code>, the configuration name
|
|
without the cpu prefix
|
|
is used to form the configuration file names.
|
|
|
|
<p>Thus, if you specify <code>m68k-local</code>, configuration uses
|
|
files <code>m68k.md</code>, <code>local.h</code>, <code>m68k.c</code>,
|
|
<code>xm-local.h</code>, <code>t-local</code>, and <code>x-local</code>, all in the
|
|
directory <code>config/m68k</code>.
|
|
|
|
<p>Here is a list of configurations that have special treatment or special
|
|
things you must know:
|
|
|
|
<dl>
|
|
<dt><code>vax-dec-vms</code>
|
|
<dd>See <a href="#VMS%20Install">VMS Install</a>, for details on how to install GNU CC on VMS.
|
|
</dl>
|
|
|
|
<h2><a name="Cross-Compiler"></a>Building and Installing a Cross-Compiler</h2>
|
|
|
|
<p>GNU CC can function as a cross-compiler for many machines, but not all.
|
|
|
|
<ul>
|
|
<li>Cross-compilers for the Mips as target using the Mips assembler
|
|
currently do not work, because the auxiliary programs
|
|
<code>mips-tdump.c</code> and <code>mips-tfile.c</code> 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.
|
|
|
|
<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.
|
|
|
|
<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.
|
|
|
|
<h2>Steps of Cross-Compilation</h2>
|
|
|
|
<p>To compile and run a program using a cross-compiler involves several
|
|
steps:
|
|
|
|
<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.
|
|
|
|
<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.
|
|
|
|
<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 <code>crt<small>...</small>.o</code>) 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.
|
|
|
|
<h2>Configuring a Cross-Compiler</h2>
|
|
|
|
<p>To build GNU CC as a cross-compiler, you start out by running
|
|
<code>configure</code>. Use the <code>--target=<var>target</var></code> to specify the
|
|
target type. If <code>configure</code> was unable to correctly identify the
|
|
system you are running on, also specify the <code>--build=<var>build</var></code>
|
|
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
|
|
<code>configure</code> can correctly identify:
|
|
|
|
<br><pre>./configure --target=m68k-hp-bsd4.3
|
|
</pre>
|
|
|
|
<h2>Tools and Libraries for a Cross-Compiler</h2>
|
|
|
|
<p>If you have a cross-assembler and cross-linker available, you should
|
|
install them now. Put them in the directory
|
|
<code>/usr/local/<var>target</var>/bin</code>. Here is a table of the tools
|
|
you should put in this directory:
|
|
|
|
<dl>
|
|
<dt><code>as</code>
|
|
<dd>This should be the cross-assembler.
|
|
|
|
<br><dt><code>ld</code>
|
|
<dd>This should be the cross-linker.
|
|
|
|
<br><dt><code>ar</code>
|
|
<dd>This should be the cross-archiver: a program which can manipulate
|
|
archive files (linker libraries) in the target machine's format.
|
|
|
|
<br><dt><code>ranlib</code>
|
|
<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>The easiest way to provide these files is to build the Binutils package
|
|
and GAS. Configure them with the same <code>--host</code> and <code>--target</code>
|
|
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>If you want to install libraries to use with the cross-compiler, such as
|
|
a standard C library, put them in the directory
|
|
<code>/usr/local/<var>target</var>/lib</code>; 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:
|
|
|
|
<br><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>
|
|
|
|
<p>The precise set of libraries you'll need, and their locations on
|
|
the target machine, vary depending on its operating system.
|
|
|
|
<p>Many targets require "start files" such as <code>crt0.o</code> and
|
|
<code>crtn.o</code> which are linked into each executable; these too should be
|
|
placed in <code>/usr/local/<var>target</var>/lib</code>. There may be several
|
|
alternatives for <code>crt0.o</code>, 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:
|
|
|
|
<br><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>
|
|
|
|
<h2>Cross-Compilers and Header Files</h2>
|
|
|
|
<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
|
|
<code>libc.a</code>, then you probably need to compile with the header files
|
|
that go with the library you use.
|
|
|
|
<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>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>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>Otherwise, you're on your own in finding header files to use when
|
|
cross-compiling.
|
|
|
|
<p>When you have found suitable header files, you should put them in the
|
|
directory <code>/usr/local/<var>target</var>/include</code>, 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>Provide the header files before you build the cross-compiler, because
|
|
the build stage actually runs the cross-compiler to produce parts of
|
|
<code>libgcc.a</code>. (These are the parts that <em>can</em> be compiled with
|
|
GNU CC.) Some of them need suitable header files.
|
|
|
|
<p>Here's an example showing how to copy the header files from a target
|
|
machine. On the target machine, do this:
|
|
|
|
<br><pre>(cd /usr/include; tar cf - .) > tarfile
|
|
</pre>
|
|
|
|
<p>Then, on the host machine, do this:
|
|
|
|
<br><pre>ftp <var>target-machine</var>
|
|
lcd /usr/local/<var>target</var>/include
|
|
get tarfile
|
|
quit
|
|
tar xf tarfile
|
|
</pre>
|
|
|
|
<h2>Actually Building the Cross-Compiler</h2>
|
|
|
|
<p>Now you can proceed just as for compiling a single-machine compiler
|
|
through the step of building stage 1.
|
|
|
|
<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>To install the cross-compiler, use <code>make install</code>, as usual.
|
|
|
|
<h2><a name="VMS%20Install"></a>Installing GNU CC on VMS</h2>
|
|
|
|
<p>The VMS version of GNU CC is distributed in a backup saveset containing
|
|
both source code and precompiled binaries.
|
|
|
|
<p>To install the <code>gcc</code> 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:
|
|
|
|
<ol type=1 start=1>
|
|
</p><li>Define the VMS logical names <code>GNU_CC</code> and <code>GNU_CC_INCLUDE</code>
|
|
to point to the directories where the GNU CC executables
|
|
(<code>gcc-cpp.exe</code>, <code>gcc-cc1.exe</code>, etc.) and the C include files are
|
|
kept respectively. This should be done with the commands:
|
|
|
|
<br><pre>$ assign /system /translation=concealed -
|
|
disk:[gcc.] gnu_cc
|
|
$ assign /system /translation=concealed -
|
|
disk:[gcc.include.] gnu_cc_include
|
|
</pre>
|
|
|
|
<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
|
|
<code>GCC_INSTALL.COM</code> script in the <code>[GCC]</code> directory.
|
|
|
|
</p><li>Install the <code>GCC</code> command with the command line:
|
|
|
|
<br><pre>$ set command /table=sys$common:[syslib]dcltables -
|
|
/output=sys$common:[syslib]dcltables gnu_cc:[000000]gcc
|
|
$ install replace sys$common:[syslib]dcltables
|
|
</pre>
|
|
|
|
<li>To install the help file, do the following:
|
|
|
|
<br><pre>$ library/help sys$library:helplib.hlb gcc.hlp
|
|
</pre>
|
|
|
|
<p>Now you can invoke the compiler with a command like <code>gcc /verbose
|
|
file.c</code>, which is equivalent to the command <code>gcc -v -c file.c</code> in
|
|
Unix.
|
|
</ol>
|
|
|
|
<p>If you wish to use GNU C++ you must first install GNU CC, and then
|
|
perform the following steps:
|
|
|
|
<ol type=1 start=1>
|
|
</p><li>Define the VMS logical name <code>GNU_GXX_INCLUDE</code> to point to the
|
|
directory where the preprocessor will search for the C++ header files.
|
|
This can be done with the command:
|
|
|
|
<br><pre>$ assign /system /translation=concealed -
|
|
disk:[gcc.gxx_include.] gnu_gxx_include
|
|
</pre>
|
|
|
|
<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><li>Obtain the file <code>gcc-cc1plus.exe</code>, and place this in the same
|
|
directory that <code>gcc-cc1.exe</code> is kept.
|
|
|
|
<p>The GNU C++ compiler can be invoked with a command like <code>gcc /plus
|
|
/verbose file.cc</code>, which is equivalent to the command <code>g++ -v -c
|
|
file.cc</code> 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
|
|
<code>/version</code> option to determine the version number of the binaries and
|
|
compare it with the source file <code>version.c</code> 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:
|
|
|
|
<ol type=1 start=1>
|
|
</p><li>Execute the command procedure <code>vmsconfig.com</code> to set up the files
|
|
<code>tm.h</code>, <code>config.h</code>, <code>aux-output.c</code>, and <code>md.</code>, and
|
|
to create files <code>tconfig.h</code> and <code>hconfig.h</code>. This procedure
|
|
also creates several linker option files used by <code>make-cc1.com</code> and
|
|
a data file used by <code>make-l2.com</code>.
|
|
|
|
<br><pre>$ @vmsconfig.com
|
|
</pre>
|
|
|
|
<li>Setup the logical names and command tables as defined above. In
|
|
addition, define the VMS logical name <code>GNU_BISON</code> to point at the
|
|
to the directories where the Bison executable is kept. This should be
|
|
done with the command:
|
|
|
|
<br><pre>$ assign /system /translation=concealed -
|
|
disk:[bison.] gnu_bison
|
|
</pre>
|
|
|
|
<p>You may, if you choose, use the <code>INSTALL_BISON.COM</code> script in the
|
|
<code>[BISON]</code> directory.
|
|
|
|
</p><li>Install the <code>BISON</code> command with the command line:
|
|
|
|
<br><pre>$ set command /table=sys$common:[syslib]dcltables -
|
|
/output=sys$common:[syslib]dcltables -
|
|
gnu_bison:[000000]bison
|
|
$ install replace sys$common:[syslib]dcltables
|
|
</pre>
|
|
|
|
<li>Type <code>@make-gcc</code> to recompile everything, or submit the file
|
|
<code>make-gcc.com</code> to a batch queue. If you wish to build the GNU C++
|
|
compiler as well as the GNU CC compiler, you must first edit
|
|
<code>make-gcc.com</code> and follow the instructions that appear in the
|
|
comments.
|
|
|
|
<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 <code>libgcc2.c</code>. To compile this you should use the command procedure
|
|
<code>make-l2.com</code>, which will generate the library <code>libgcc2.olb</code>.
|
|
<code>libgcc2.olb</code> should be built using the compiler built from
|
|
the same distribution that <code>libgcc2.c</code> came from, and
|
|
<code>make-gcc.com</code> will automatically do all of this for you.
|
|
|
|
<p>To install the library, use the following commands:
|
|
|
|
<br><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
|
|
</pre>
|
|
|
|
<p>The first command simply removes old modules that will be replaced with
|
|
modules from <code>libgcc2</code> under different module names. The modules
|
|
<code>new</code> and <code>eprintf</code> may not actually be present in your
|
|
<code>gcclib.olb</code>--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 <code>libgcc2.c</code>.
|
|
|
|
<p>Whenever you update the compiler on your system, you should also update the
|
|
library with the above procedure.
|
|
|
|
</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):
|
|
|
|
<br><pre>$ assign dua0:[gcc.build_dir.]/translation=concealed, -
|
|
dua1:[gcc.source_dir.]/translation=concealed gcc_build
|
|
$ set default gcc_build:[000000]
|
|
</pre>
|
|
|
|
<p>where the directory <code>dua1:[gcc.source_dir]</code> contains the source
|
|
code, and the directory <code>dua0:[gcc.build_dir]</code> 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 <code>gcc_build</code> 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><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.
|
|
|
|
<li>If you want to build GNU CC with the VAX C compiler, you will need to
|
|
make minor changes in <code>make-cccp.com</code> and <code>make-cc1.com</code>
|
|
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 <code>libgcc2</code> in order to build <code>gcclib</code> (see above);
|
|
<code>make-l2.com</code> expects to be able to find it operational in
|
|
<code>gnu_cc:[000000]gnu-as.exe</code>.
|
|
|
|
<p>To use GNU CC on VMS, you need the VMS driver programs
|
|
<code>gcc.exe</code>, <code>gcc.com</code>, and <code>gcc.cld</code>. They are
|
|
distributed with the VMS binaries (<code>gcc-vms</code>) rather than the
|
|
GNU CC sources. GAS is also included in <code>gcc-vms</code>, as is Bison.
|
|
|
|
<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
|
|
<code>make-cccp.com</code> and <code>make-cc1.com</code>. 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 <code>VAXCRTL</code> library.
|
|
Now this should work.
|
|
|
|
<p>Even with this version, however, GNU CC itself should not be linked with
|
|
the sharable <code>VAXCRTL</code>. The version of <code>qsort</code> in
|
|
<code>VAXCRTL</code> has a bug (known to be present in VMS versions V4.6
|
|
through V5.5) which causes the compiler to fail.
|
|
|
|
<p>The executables are generated by <code>make-cc1.com</code> and
|
|
<code>make-cccp.com</code> use the object library version of <code>VAXCRTL</code> in
|
|
order to make use of the <code>qsort</code> routine in <code>gcclib.olb</code>. If
|
|
you wish to link the compiler executables with the shareable image
|
|
version of <code>VAXCRTL</code>, you should edit the file <code>tm.h</code> (created
|
|
by <code>vmsconfig.com</code>) to define the macro <code>QSORT_WORKAROUND</code>.
|
|
|
|
<p><code>QSORT_WORKAROUND</code> is always defined when GNU CC is compiled with
|
|
VAX C, to avoid a problem in case <code>gcclib.olb</code> is not yet
|
|
available.
|
|
<hr />
|
|
<p>
|
|
<a href="./index.html">Return to the GCC Installation page</a>
|
|
|
|
</body></html>
|
|
|