The procedures described to unpack, configure, build, and
install g77
assume your system has certain programs
already installed.
The following prerequisites should be met by your
system before you follow the g77
installation instructions:
gzip
gcc
and g77
distributions,
you'll need the gunzip
utility in the gzip
distribution.
Most UNIX systems already have gzip
installed.
If yours doesn't, you can get it from the FSF.
Note that you'll need tar
and other utilities
as well, but all UNIX systems have these.
There are GNU versions of all these available--in fact,
a complete GNU UNIX system can be put together on
most systems, if desired.
The version of GNU gzip
used to package this release
is 1.24.
(The version of GNU tar
used to package this release
is 1.11.2.)
gcc
on your system.
The version should be an exact copy of a distribution
from the FSF.
Its size is approximately 7.1MB.
If you've already unpacked `gcc-2.7.2.3.tar.gz' into a
directory (named `gcc-2.7.2.3') called the source tree
for gcc
, you can delete the distribution
itself, but you'll need to remember to skip any instructions to unpack
this distribution.
Without an applicable gcc
source tree, you cannot
build g77
.
You can obtain an FSF distribution of gcc
from the FSF.
g77
from the FSF,
the same way you obtained gcc
.
g77
depends on the type of system you're
using, how you build g77
, and how much of it you
install (primarily, which languages you install).
The sizes shown below assume all languages distributed
in gcc-2.7.2.3
, plus g77
, will be built
and installed.
These sizes are indicative of GNU/Linux systems on
Intel x86 running COFF and on Digital Alpha (AXP) systems
running ELF.
These should be fairly representative of 32-bit and 64-bit
systems, respectively.
Note that all sizes are approximate and subject to change without
notice!
They are based on preliminary releases of g77 made shortly
before the public beta release.
gcc
and g77
distributions occupy 8.6MB
packed, 35MB unpacked.
These consist of the source code and documentation,
plus some derived files (mostly documentation), for
gcc
and g77
.
Any deviations from these numbers for different
kinds of systems are likely to be very minor.
gcc
compiler modified and used to build itself for
testing fairly quickly, using the copy of the compiler
kept in gcc/stage2
.
make
is used to avoid
gratuitous rebuilds (or, the installation can be done
by hand).
gcc
and g77
copies
14.9MB onto the `--prefix' disk for a total of 79.2MB
on an ix86, and copies ??MB onto the `--prefix'
disk for a total of ??MB on an Alpha.
gcc
or g77
are planned, the
source and build directory may be removed, leaving
the total impact on a system's disk storage as
that of the amount copied during installation.
Systems with the appropriate version of gcc
installed don't require the complete
bootstrap build.
Doing a "straight build" requires about as much
space as does a bootstrap build followed by removing
both the `gcc/stage1' and `gcc/stage2'
directories.
Installing gcc
and g77
over existing
versions might require less new disk space,
but note that, unlike many products, gcc
installs itself in a way that avoids overwriting other
installed versions of itself, so that other versions may
easily be invoked (via `gcc -V version').
So, the amount of space saved as a result of having
an existing version of gcc
and g77
already installed is not much--typically only the
command drivers (gcc
, g77
, g++
,
and so on, which are small) and the documentation
is overwritten by the new installation.
The rest of the new installation is done without
replacing existing installed versions (assuming
they have different version numbers).
patch
patch
does yourself,
by hand, without much trouble, having patch
installed
makes installation of new versions of GNU utilities such as
g77
so much easier that it is worth getting.
You can obtain patch
the same way you obtained
gcc
and g77
.
In any case, you can apply patches by hand--patch files
are designed for humans to read them.
The version of GNU patch
used to develop this release
is 2.4.
make
make
, and you will probably save
yourself a lot of trouble if it is GNU make
(sometimes
referred to as gmake
).
The version of GNU make
used to develop this release
is 3.73.
cc
gcc
.
bison
bison
installed, you can usually
work around any need for it, since g77
itself does
not use it, and gcc
normally includes all files
generated by running it in its distribution.
You can obtain bison
the same way you obtained
gcc
and g77
.
The version of GNU bison
used to develop this release
is 1.25.
See section Missing bison
?,
for information on how to work around not having bison
.
makeinfo
makeinfo
, you can usually work
around any need for it.
You can obtain makeinfo
the same way you obtained
gcc
and g77
.
The version of GNU makeinfo
used to develop this release
is 1.68, from GNU texinfo
version 3.11.
See section Missing makeinfo
?,
for information on getting around the lack of makeinfo
.
sed
sed
, but some have a broken
version that cannot handle configuring, building, or
installing gcc
or g77
.
The version of GNU sed
used to develop this release
is 2.05.
(Note that GNU sed
version 3.0 was withdrawn by the
FSF--if you happen to have this version installed, replace
it with version 2.05 immediately.
See a GNU distribution site for further explanation.)
root
access or equivalent
root
access to that system, or
equivalent access to the `--prefix' directory tree
specified on the configure
command line.
Portions of the procedure (such as configuring and building
g77
) can be performed by any user with enough disk
space and virtual memory.
However, these instructions are oriented towards less-experienced
users who want to install g77
on their own personal
systems.
System administrators with more experience will want to
determine for themselves how they want to modify the
procedures described below to suit the needs of their
installation.
Go to the first, previous, next, last section, table of contents.