g77
is configured automatically when you configure
gcc
.
There are two parts of g77
that are configured in two
different ways---g77
, which "camps on" to the
gcc
configuration mechanism, and libf2c
, which
uses a variation of the GNU autoconf
configuration
system.
Generally, you shouldn't have to be concerned with
either g77
or libf2c
configuration, unless
you're configuring g77
as a cross-compiler.
In this case, the libf2c
configuration, and possibly the
g77
and gcc
configurations as well,
might need special attention.
(This also might be the case if you're porting gcc
to
a whole new system--even if it is just a new operating system
on an existing, supported CPU.)
To configure the system, see section `Installing GNU CC' in Using and Porting GNU CC, following the instructions for running `./configure'. Pay special attention to the `--prefix=' option, which you almost certainly will need to specify.
(Note that gcc
installation information is provided
as a straight text file in `gcc/INSTALL'.)
The information printed by the invocation of `./configure' should show that the `f' directory (the Fortran language) has been configured. If it does not, there is a problem.
Note: Configuring with the `--srcdir' argument is known
to work with GNU make
, but it is not known to work with
other variants of make
.
Irix5.2 and SunOS4.1 versions of make
definitely
won't work outside the source directory at present.
g77
's
portion of the `configure' script issues a warning message
about this when you configure for building binaries outside
the source directory.
Go to the first, previous, next, last section, table of contents.