Go to the first, previous, next, last section, table of contents.
Building g77
requires building enough of gcc
that
these instructions assume you're going to build all of
gcc
, including g++
, protoize
, and so on.
You can save a little time and disk space by changes the
`LANGUAGES' macro definition in gcc/Makefile.in
or gcc/Makefile
, but if you do that, you're on your own.
One change is almost certainly going to cause failures:
removing `c' or `f77' from the definition of the
`LANGUAGES' macro.
After configuring gcc
, which configures g77
and
libg2c
automatically, you're ready to start the actual
build by invoking make
.
Note: You must have run the `configure'
script in gcc
before you run make
,
even if you're using an already existing gcc
development directory,
because `./configure' does the work to recognize that you've added
g77
to the configuration.
There are two general approaches to building GNU CC from scratch:
gcc
, that is then
used to compile ("bootstrap") the entire system.
On all systems without a recent version of gcc
already installed, the bootstrap method must be
used.
In particular, g77
uses extensions to the C
language offered, apparently, only by gcc
.
On most systems with a recent version of gcc
already installed, the straight method can be
used.
This is an advantage, because it takes less CPU time
and disk space for the build.
However, it does require that the system have fairly
recent versions of many GNU programs and other
programs, which are not enumerated here.
gcc
.
Go to the first, previous, next, last section, table of contents.