collect2 works; how it finds ld.
Here is the procedure for installing GNU CC on a Unix system. See section Installing GNU CC on VMS, for VMS systems. In this section we assume you compile in the same directory that contains the source files; see section Compilation in a Separate Directory, to find out how to compile in a separate directory on Unix systems.
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.
PATH. The cc command in
`/usr/ucb' uses libraries which have bugs.
./configure --build=sparc-sun-sunos4.1A configuration name may be canonical or it may be more or less abbreviated. A canonical configuration name has three parts, separated by dashes. It looks like this: `cpu-company-system'. (The three parts may themselves contain dashes; `configure' can figure out which dashes serve which purpose.) For example, `m68k-sun-sunos4.1' specifies a Sun 3. You can also replace parts of the configuration by nicknames or aliases. For example, `sun3' stands for `m68k-sun', so `sun3-sunos4.1' is another way to specify a Sun 3. You can also use simply `sun3-sunos', since the version of SunOS is assumed by default to be version 4. `sun3-bsd' also works, since `configure' knows that the only BSD variant on a Sun 3 is SunOS. 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. See section Configurations Supported by GNU CC, 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. There are four additional options you can specify independently to describe variant hardware and software configurations. These are `--with-gnu-as', `--with-gnu-ld', `--with-stabs' and `--nfp'.
as 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 `-v' when you run it.
The systems where it makes a difference whether you use GAS arecollect2, a program
which otherwise serves as a front-end for the system's linker on most
configurations.
configure. Normally
you need not be concerned with these files.
--local-prefix option below.
fixincludes script.
PATH environment variable such that the necessary GNU tools come
before the standard system tools.
make stage1The files are moved into a subdirectory named `stage1'. Once installation is complete, you may wish to delete these files with
rm -r stage1.
PATH environment variable such that the necessary GNU tools come
before the standard system tools.
make CC="stage1/xgcc -Bstage1/" CFLAGS="-g -O2"This is called making the stage 2 compiler. 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 `LANGUAGES="list"'. list should contain one or more words from the list `c', `c++', `objective-c', and `proto'. Separate the words with spaces. `proto' stands for the programs
protoize and
unprotoize; they are not a separate language, but you use
LANGUAGES to enable or disable their installation.
If you are going to build the stage 3 compiler, then you might want to
build only the C language in stage 2.
Once you have built the stage 2 compiler, if you are short of disk
space, you can delete the subdirectory `stage1'.
On a 68000 or 68020 system lacking floating point hardware,
unless you have selected a `tm.h' file that expects by default
that there is no such hardware, do this instead:
make CC="stage1/xgcc -Bstage1/" CFLAGS="-g -O2 -msoft-float"
make stage2 make CC="stage2/xgcc -Bstage2/" CFLAGS="-g -O2"This is called making the stage 3 compiler. Aside from the `-B' option, the compiler options should be the same as when you made the stage 2 compiler. But the
LANGUAGES 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 `LANGUAGES="list"', as described
above.
If you do not have to install any additional GNU tools, you may use the
command
make bootstrap LANGUAGES=language-list BOOT_CFLAGS=option-listinstead of making `stage1', `stage2', and performing the two compiler builds.
make compareThis 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 Reporting Bugs). 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):
for file in *.o; do cmp $file stage2/$file doneIf you have built the compiler with the `-mno-mips-tfile' option on MIPS machines, you will not be able to compare the files.
CC,
CFLAGS and LANGUAGES 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.
For example, if you have built the stage 2 compiler, you can use the
following command:
make install CC="stage2/xgcc -Bstage2/" CFLAGS="-g -O" LANGUAGES="list"This copies the files `cc1', `cpp' and `libgcc.a' to files `cc1', `cpp' and `libgcc.a' in the directory `/usr/local/lib/gcc-lib/target/version', which is where the compiler driver program looks for them. Here target is the target machine type specified when you ran `configure', and version is the version number of GNU CC. This naming scheme permits various versions and/or cross-compilers to coexist. This also copies the driver program `xgcc' into `/usr/local/bin/gcc', so that it appears in typical execution search paths. On some systems, this command causes recompilation of some files. This is usually due to bugs in
make. You should either ignore this
problem, or use GNU Make.
Warning: there is a bug in alloca 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 alloca as a built-in function and never the
one in the library.
(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.)
Here are the possible CPU types:
1750a, a29k, alpha, arm, cn, clipper, dsp16xx, elxsi, h8300, hppa1.0, hppa1.1, i370, i386, i486, i586, i860, i960, m68000, m68k, m88k, mips, mipsel, mips64, mips64el, ns32k, powerpc, powerpcle, pyramid, romp, rs6000, sh, sparc, sparclite, sparc64, vax, we32k.
Here are the recognized company names. As you can see, customary abbreviations are used rather than the longer official names.
acorn, alliant, altos, apollo, att, bull, cbm, convergent, convex, crds, dec, dg, dolphin, elxsi, encore, harris, hitachi, hp, ibm, intergraph, isi, mips, motorola, ncr, next, ns, omron, plexus, sequent, sgi, sony, sun, tti, unicom, wrs.
The company name is meaningful only to disambiguate when the rest of the information supplied is insufficient. You can omit it, writing just `cpu-system', if it is not needed. For example, `vax-ultrix4.2' is equivalent to `vax-dec-ultrix4.2'.
Here is a list of system types:
386bsd, aix, acis, amigados, aos, aout, bosx, bsd, clix, coff, ctix, cxux, dgux, dynix, ebmon, ecoff, elf, esix, freebsd, hms, genix, gnu, gnu/linux, hiux, hpux, iris, irix, isc, luna, lynxos, 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.
You can omit the system type; then `configure' guesses the operating system from the CPU and company.
You can add a version number to the system type; this may or may not make a difference. For example, you can write `bsd4.3' or `bsd4.4' to distinguish versions of BSD. In practice, the version number is most needed for `sysv3' and `sysv4', which are often treated differently.
If you specify an impossible combination such as `i860-dg-vms', then you may get an error message from `configure', or it may ignore part of the information and do the best it can with the rest. `configure' always prints the canonical name for the alternative that it used. GNU CC does not support all possible alternatives.
Often a particular model of machine has a name. Many machine names are recognized as aliases for CPU/company combinations. Thus, the machine name `sun3', mentioned above, is an alias for `m68k-sun'. 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:
3300, 3b1, 3bn, 7300, altos3068, altos, apollo68, att-7300, balance, convex-cn, crds, decstation-3100, decstation, delta, encore, fx2800, gmicro, hp7nn, hp8nn, hp9k2nn, hp9k3nn, hp9k7nn, hp9k8nn, 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.
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 `local' as the company name to access them. If you use configuration `cpu-local', the configuration name without the cpu prefix is used to form the configuration file names.
Thus, if you specify `m68k-local', configuration uses files `m68k.md', `local.h', `m68k.c', `xm-local.h', `t-local', and `x-local', all in the directory `config/m68k'.
Here is a list of configurations that have special treatment or special things you must know:
as1750, an assembler/linker available under the GNU Public
License for the 1750A. Contact kellogg@space.otn.dasa.de for more
details on obtaining `as1750'. A similarly licensed simulator for
the 1750A is available from same address.
You should ignore a fatal error during the building of libgcc (libgcc is
not yet implemented for the 1750A.)
The as1750 assembler requires the file `ms1750.inc', which is
found in the directory `config/1750a'.
GNU CC produced the same sections as the Fairchild F9450 C Compiler,
namely:
Normal
Static
Konst
Init
make compare may fail on old versions of DEC Unix unless you add
`-save-temps' to CFLAGS. On these systems, the name of the
assembler input file is stored in the object file, and that makes
comparison fail if it differs between the stage1 and
stage2 compilations. The option `-save-temps' forces a
fixed name to be used for the assembler input file, instead of a
randomly chosen name in `/tmp'. Do not add `-save-temps'
unless the comparisons fail without that option. If you add
`-save-temps', you will have to manually delete the `.i' and
`.s' files after each series of compilations.
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 `--with-stabs' option of `configure' above
for more information on these formats and how to select them.
There is a bug in DEC's assembler that produces incorrect line numbers
for ECOFF format when the `.align' directive is used. To work
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 `-O' is specified are
different depending on whether or not `-g' is also specified.
To avoid this behavior, specify `-gstabs+' and use GDB instead of
DBX. DEC is now aware of this problem with the assembler and hopes to
provide a fix shortly.
CC make variable and use the MIPS
compilers, you may need to add `-Wf,-XNg1500 -Olimit 3000'.
mrs@cygnus.com for more details.
/usr/local/lib/gcc-lib/configuration/gccversion/aswhere configuration is the configuration name (perhaps `hpnnn-hpux') and gccversion is the GNU CC version number. Do this before starting the build process, otherwise you will get errors from the HPUX assembler while building `libgcc2.a'. The command
make install-dirwill create the necessary directory hierarchy so you can install GAS before building GCC. To enable debugging, configure GNU CC with the `--with-gnu-as' option before building. It has been reported that GNU CC produces invalid assembly code for 1.1 machines running HP-UX 8.02 when using the HP assembler. Typically the errors look like this:
as: bug.s @line#15 [err#1060]
Argument 0 or 2 in FARG upper
- lookahead = ARGW1=FR,RTNVAL=GR
as: foo.s @line#28 [err#1060]
Argument 0 or 2 in FARG upper
- lookahead = ARGW1=FR
You can check the version of HP-UX you are running by executing the command
`uname -r'. If you are indeed running HP-UX 8.02 on a PA and
using the HP assembler then configure GCC with "hpnnn-hpux8.02".
configure winnt from an MSDOS console window or from the
program manager dialog box. `configure.bat' assumes you have
already installed and have in your path a Unix-like `sed' program
which is used to create a working `Makefile' from `Makefile.in'.
`Makefile' 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 `sed' and `touch' to use this installation method,
which only automatically builds the compiler itself. You must then
examine what `fixinc.winnt' does, edit the header files by hand and
build `libgcc.a' manually.
law@cs.utah.edu
to get binaries of GNU CC for bootstrapping.
obstack_free in the file
`tree.c' with _obstack_free.
make to get the first-stage GNU CC.
F.Pierresteguy@frcl.bull.fr.
casm instead of as. For some
strange reason linking `/bin/as' to `/bin/casm' changes the
behavior, and does not work. So, when installing GNU CC, you should
install the following script as `as' in the subdirectory where
the passes of GCC are installed:
#!/bin/sh casm $*The default Unos library is named `libunos.a' instead of `libc.a'. To allow GNU CC to function, either change all references to `-lc' in `gcc.c' to `-lunos' or link `/lib/libc.a' to `/lib/libunos.a'. When compiling GNU CC with the standard compiler, to overcome bugs in the support of
alloca, do not use `-O' when making stage 2.
Then use the stage 2 compiler with `-O' to make the stage 3
compiler. This compiler will have the same characteristics as the usual
stage 2 compiler on other systems. Use it to make a stage 4 compiler
and compare that with stage 3 to verify proper compilation.
(Perhaps simply defining ALLOCA in `x-crds' as described in
the comments there will make the above paragraph superfluous. Please
inform us of whether this works.)
Unos uses memory segmentation instead of demand paging, so you will need
a lot of memory. 5 Mb is barely enough if no other tasks are running.
If linking `cc1' fails, try putting the object files into a library
and linking from that library.
memcpy, memcmp, and memset. If your system lacks
these, you must remove or undo the definition of
TARGET_MEM_FUNCTIONS in `mips-bsd.h'.
The MIPS C compiler needs to be told to increase its table size
for switch statements with the `-Wf,-XNg1500' option in
order to compile `cp/parse.c'. If you use the `-O2'
optimization option, you also need to use `-Olimit 3000'.
Both of these options are automatically generated in the
`Makefile' that the shell script `configure' builds.
If you override the CC make variable and use the MIPS
compilers, you may need to add `-Wf,-XNg1500 -Olimit 3000'.
CC make variable and use the MIPS
compilers, you may need to add `-Wf,-XNg1500 -Olimit 3000'.
MIPS computers running RISC-OS can support four different
personalities: default, BSD 4.3, System V.3, and System V.4
(older versions of RISC-OS don't support V.4). To configure GCC
for these platforms use the following configurations:
rev'
rev.
revbsd'
rev.
revsysv4'
rev.
revsysv'
rev.
rev mentioned above is the revision of
RISC-OS to use. You must reconfigure GCC when going from a
RISC-OS revision 4 to RISC-OS revision 5. This has the effect of
avoiding a linker
bug (see section Installation Problems, for more details).
make compare may fail on version 5 of IRIX unless you add
`-save-temps' to CFLAGS. On these systems, the name of the
assembler input file is stored in the object file, and that makes
comparison fail if it differs between the stage1 and
stage2 compilations. The option `-save-temps' forces a
fixed name to be used for the assembler input file, instead of a
randomly chosen name in `/tmp'. Do not add `-save-temps'
unless the comparisons fail without that option. If you do you
`-save-temps', you will have to manually delete the `.i' and
`.s' files after each series of compilations.
The MIPS C compiler needs to be told to increase its table size
for switch statements with the `-Wf,-XNg1500' option in
order to compile `cp/parse.c'. If you use the `-O2'
optimization option, you also need to use `-Olimit 3000'.
Both of these options are automatically generated in the
`Makefile' that the shell script `configure' builds.
If you override the CC make variable and use the MIPS
compilers, you may need to add `-Wf,-XNg1500 -Olimit 3000'.
On Irix version 4.0.5F, and perhaps on some other versions as well,
there is an assembler bug that reorders instructions incorrectly. To
work around it, specify the target configuration
`mips-sgi-irix4loser'. This configuration inhibits assembler
optimization.
In a compiler configured with target `mips-sgi-irix4', you can turn
off assembler optimization by using the `-noasmopt' option. This
compiler option passes the option `-O0' to the assembler, to
inhibit reordering.
The `-noasmopt' option can be useful for testing whether a problem
is due to erroneous assembler reordering. Even if a problem does not go
away with `-noasmopt', it may still be due to assembler
reordering--perhaps GNU CC itself was miscompiled as a result.
To enable debugging under Irix 5, you must use GNU as 2.5 or later,
and use the `--with-gnu-as' configure option when configuring gcc.
GNU as is distributed as part of the binutils package.
alloca
and malloc; you must get the compiled versions of these from GNU
Emacs.
hc, the Metaware compiler, it will work, but you will get
mismatches between the stage 2 and stage 3 compilers in various files.
These errors are minor differences in some floating-point constants and
can be safely ignored; the stage 3 compiler is correct.
vcc). It produces incorrect code
in some cases (for example, when alloca is used).
Meanwhile, compiling `cp/parse.c' 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.
mv /lib/cpp /lib/cpp.att
cp cpp /lib/cpp.gnu
echo '/lib/cpp.gnu -traditional ${1+"$@"}' > /lib/cpp
chmod +x /lib/cpp
The system's compiler produces bad code for some of the 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:
make LANGUAGES=c CC=stage1/xgcc CFLAGS="-Bstage1/ -g" make stage2 make CC=stage2/xgcc CFLAGS="-Bstage2/ -g -O"You may need to raise the ULIMIT setting to build a C++ compiler, as the file `cc1plus' is larger than one megabyte.
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:
VPATH
feature. (GNU Make supports it, as do Make versions on most BSD
systems.)
make distclean
mkdir gcc-sun3 cd gcc-sun3On systems that do not support symbolic links, this directory must be on the same file system as the source code directory.
../gcc/configure ...This also tells
configure where to find the compiler sources;
configure 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 `--srcdir' option, like this:
../gcc/configure --srcdir=../gcc other optionsThe directory you specify with `--srcdir' need not be the same as the one that
configure is found in.
Now, you can run make in that directory. You need not repeat the
configuration steps shown above, when ordinary source files change. You
must, however, run configure again when the configuration files
change, if your system does not support symbolic links.
GNU CC can function as a cross-compiler for many machines, but not all.
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.
To compile and run a program using a cross-compiler involves several steps:
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.
To build GNU CC as a cross-compiler, you start out by running `configure'. Use the `--target=target' to specify the target type. If `configure' was unable to correctly identify the system you are running on, also specify the `--build=build' 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 `configure' can correctly identify:
./configure --target=m68k-hp-bsd4.3
If you have a cross-assembler and cross-linker available, you should install them now. Put them in the directory `/usr/local/target/bin'. Here is a table of the tools you should put in this directory:
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.
The easiest way to provide these files is to build the Binutils package and GAS. Configure them with the same `--host' and `--target' 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.
If you want to install libraries to use with the cross-compiler, such as a standard C library, put them in the directory `/usr/local/target/lib'; installation of GNU CC copies all all the files in that subdirectory into the proper place for GNU CC to find them and link with them. Here's an example of copying some libraries from a target machine:
ftp target-machine lcd /usr/local/target/lib cd /lib get libc.a cd /usr/lib get libg.a get libm.a quit
The precise set of libraries you'll need, and their locations on the target machine, vary depending on its operating system.
Many targets require "start files" such as `crt0.o' and
`crtn.o' which are linked into each executable; these too should be
placed in `/usr/local/target/lib'. There may be several
alternatives for `crt0.o', for use with profiling or other
compilation options. Check your target's definition of
STARTFILE_SPEC to find out what start files it uses.
Here's an example of copying these files from a target machine:
ftp target-machine lcd /usr/local/target/lib prompt cd /lib mget *crt*.o cd /usr/lib mget *crt*.o quit
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 `libgcc1.c'; the library made from them is called `libgcc1.a'.
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.
So, when you build a cross-compiler you have to supply a suitable library `libgcc1.a' that does the job it is expected to do.
To compile `libgcc1.c' 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.
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 `libgcc1.a'.
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 MULSI3_LIBCALL, 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.
Some targets do not have floating point instructions; they need other functions in `libgcc1.a', 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 `libgcc1.a'. Perhaps future versions will contain code to do this automatically and conveniently. That depends on whether someone wants to implement it.
Some embedded targets come with all the necessary `libgcc1.a' routines written in C or assembler. These targets build `libgcc1.a' automatically and you do not need to do anything special for them. Other embedded targets do not need any `libgcc1.a' routines since all the necessary operations are supported by the hardware.
If your target system has another C compiler, you can configure GNU CC as a native compiler on that machine, build just `libgcc1.a' with `make libgcc1.a' on that machine, and use the resulting file with the cross-compiler. To do this, execute the following on the target machine:
cd target-build-dir ./configure --host=sparc --target=sun3 make libgcc1.a
And then this on the host machine:
ftp target-machine binary cd target-build-dir get libgcc1.a quit
Another way to provide the functions you need in `libgcc1.a' is to
define the appropriate perform_... 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.)
To build `libgcc1.a' using the perform macros, use
`LIBGCC1=libgcc1.a OLDCC=./xgcc' when building the compiler.
Otherwise, you should place your replacement library under the name
`libgcc1.a' in the directory in which you will build the
cross-compiler, before you run make.
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 `libc.a', then you probably need to compile with the header files that go with the library you use.
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.
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).
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.
Otherwise, you're on your own in finding header files to use when cross-compiling.
When you have found suitable header files, put them in `/usr/local/target/include', before building the cross compiler. Then installation will run fixincludes properly and install the corrected versions of the header files where the compiler will use them.
Provide the header files before you build the cross-compiler, because the build stage actually runs the cross-compiler to produce parts of `libgcc.a'. (These are the parts that can be compiled with GNU CC.) Some of them need suitable header files.
Here's an example showing how to copy the header files from a target machine. On the target machine, do this:
(cd /usr/include; tar cf - .) > tarfile
Then, on the host machine, do this:
ftp target-machine lcd /usr/local/target/include get tarfile quit tar xf tarfile
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 `libgcc1.a', then compilation will give up at the point where it needs that file, printing a suitable error message. If you do provide `libgcc1.a', then building the compiler will automatically compile and link a test program called `libgcc1-test'; if you get errors in the linking, it means that not all of the necessary routines in `libgcc1.a' are available.
You must provide the header file `float.h'. One way to do this is to compile `enquire' and run it on your target machine. The job of `enquire' is to run on the target machine and figure out by experiment the nature of its floating point representation. `enquire' records its findings in the header file `float.h'. If you can't produce this file by running `enquire' on the target machine, then you will need to come up with a suitable `float.h' in some other way (or else, avoid using it in your programs).
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.
To install the cross-compiler, use `make install', as usual.
On Solaris (version 2.1), do not use the linker or other tools in
`/usr/ucb' to build GNU CC. Use /usr/ccs/bin.
Make sure the environment variable FLOAT_OPTION is not set when
you compile `libgcc.a'. If this option were set to f68881
when `libgcc.a' is compiled, the resulting code would demand to be
linked with a special startup file and would not link properly without
special pains.
There is a bug in alloca 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 alloca as a built-in function and never the one
in the library.
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:
make CC="TERMCAP=x OBJS=x LIBFUNCS=x STAGESTUFF=x cc"
The VMS version of GNU CC is distributed in a backup saveset containing both source code and precompiled binaries.
To install the `gcc' 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:
$ assign /system /translation=concealed - disk:[gcc.] gnu_cc $ assign /system /translation=concealed - disk:[gcc.include.] gnu_cc_includewith 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 `GCC_INSTALL.COM' script in the `[GCC]' directory.
$ set command /table=sys$common:[syslib]dcltables - /output=sys$common:[syslib]dcltables gnu_cc:[000000]gcc $ install replace sys$common:[syslib]dcltables
$ library/help sys$library:helplib.hlb gcc.hlpNow you can invoke the compiler with a command like `gcc /verbose file.c', which is equivalent to the command `gcc -v -c file.c' in Unix.
If you wish to use GNU C++ you must first install GNU CC, and then perform the following steps:
$ assign /system /translation=concealed - disk:[gcc.gxx_include.] gnu_gxx_includewith the appropriate disk and directory name. If you are going to be using libg++, this is where the libg++ install procedure will install the libg++ header files.
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 `/version' option to determine the version number of the binaries and compare it with the source file `version.c' 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:
$ @vmsconfig.com
$ assign /system /translation=concealed - disk:[bison.] gnu_bisonYou may, if you choose, use the `INSTALL_BISON.COM' script in the `[BISON]' directory.
$ set command /table=sys$common:[syslib]dcltables - /output=sys$common:[syslib]dcltables - gnu_bison:[000000]bison $ install replace sys$common:[syslib]dcltables
$ 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.objThe first command simply removes old modules that will be replaced with modules from `libgcc2' under different module names. The modules
new and eprintf may not actually be present in your
`gcclib.olb'---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 `libgcc2.c'.
Whenever you update the compiler on your system, you should also update the
library with the above procedure.
$ assign dua0:[gcc.build_dir.]/translation=concealed, -
dua1:[gcc.source_dir.]/translation=concealed gcc_build
$ set default gcc_build:[000000]
where the directory `dua1:[gcc.source_dir]' contains the source
code, and the directory `dua0:[gcc.build_dir]' 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 `gcc_build' 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).
extern const 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.
If you are compiling with a version of GNU CC older than 1.33, specify
`/DEFINE=("inline=")' as an option in all the compilations. This
requires editing all the gcc commands in `make-cc1.com'.
(The older versions had problems supporting inline.) Once you
have a working 1.33 or newer GNU CC, you can change this file back.
CC, CFLAGS, and
LIBS. 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 `libgcc2' in order to build `gcclib' (see above);
`make-l2.com' expects to be able to find it operational in
`gnu_cc:[000000]gnu-as.exe'.
To use GNU CC on VMS, you need the VMS driver programs
`gcc.exe', `gcc.com', and `gcc.cld'. They are
distributed with the VMS binaries (`gcc-vms') rather than the
GNU CC sources. GAS is also included in `gcc-vms', as is Bison.
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 CC, CFLAGS, and LIBS definitions in
`make-cccp.com' and `make-cc1.com'. The second generation
compiler will be able to take advantage of many optimizations that must
be suppressed when building with other compilers.
Under previous versions of GNU CC, the generated code would occasionally give strange results when linked with the sharable `VAXCRTL' library. Now this should work.
Even with this version, however, GNU CC itself should not be linked with
the sharable `VAXCRTL'. The version of qsort in
`VAXCRTL' has a bug (known to be present in VMS versions V4.6
through V5.5) which causes the compiler to fail.
The executables are generated by `make-cc1.com' and
`make-cccp.com' use the object library version of `VAXCRTL' in
order to make use of the qsort routine in `gcclib.olb'. If
you wish to link the compiler executables with the shareable image
version of `VAXCRTL', you should edit the file `tm.h' (created
by `vmsconfig.com') to define the macro QSORT_WORKAROUND.
QSORT_WORKAROUND is always defined when GNU CC is compiled with
VAX C, to avoid a problem in case `gcclib.olb' is not yet
available.
collect2
Many target systems do not have support in the assembler and linker for
"constructors"---initialization functions to be called before the
official "start" of main. On such systems, GNU CC uses a
utility called collect2 to arrange to call these functions at
start time.
The program collect2 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 `.c' file containing a table of them,
compiles it, and links the program a second time including that file.
The actual calls to the constructors are carried out by a subroutine
called __main, which is called (automatically) at the beginning
of the body of main (provided main was compiled with GNU
CC). Calling __main is necessary, even when compiling C code, to
allow linking C and C++ object code together. (If you use
`-nostdlib', you get an unresolved reference to __main,
since it's defined in the standard GCC library. Include `-lgcc' at
the end of your compiler command line to resolve this reference.)
The program collect2 is installed as ld in the directory
where the passes of the compiler are installed. When collect2
needs to find the real ld, it tries the following file
names:
PATH.
REAL_LD_FILE_NAME configuration macro,
if specified.
collect2 will not execute itself recursively.
PATH.
"The compiler's search directories" means all the directories where
gcc searches for passes of the compiler. This includes
directories that you specify with `-B'.
Cross-compilers search a little differently:
PATH.
REAL_LD_FILE_NAME configuration macro,
if specified.
PATH.
collect2 explicitly avoids running ld using the file name
under which collect2 itself was invoked. In fact, it remembers
up a list of such names--in case one copy of collect2 finds
another copy (or version) of collect2 installed as ld in a
second place in the search path.
collect2 searches for the utilities nm and strip
using the same algorithm as above for ld.
GCC_INCLUDE_DIR 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
fixincludes on the header files in `$(tooldir)/include'.
(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).
GPLUS_INCLUDE_DIR means the same thing for native and cross. It
is where g++ looks first for header files. libg++
installs only target independent header files in that directory.
LOCAL_INCLUDE_DIR is used only for a native compiler. It is
normally `/usr/local/include'. GNU CC searches this directory so
that users can install header files in `/usr/local/include'.
CROSS_INCLUDE_DIR is used only for a cross compiler. GNU CC
doesn't install anything there.
TOOL_INCLUDE_DIR 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
`/usr/include'. When you build a cross-compiler,
fixincludes processes any header files in this directory.