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 libg2c, which
uses a variation of the GNU autoconf configuration
system.
Generally, you shouldn't have to be concerned with
either g77 or libg2c configuration, unless
you're configuring g77 as a cross-compiler.
In this case, the libg2c 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 plain-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,
or by starting in an empty directory
and typing a command such as ../gcc/configure to
build with separate build and source directories,
is known to work with GNU make,
but it is known to not 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
used to issue a warning message about this
when configuring for building binaries outside the source directory,
but no longer does this as of version 0.5.23.
Instead, g77 simply rejects most common attempts
to build it using a non-GNU make when the
build directory is not the same as the source directory,
issuing an explanatory diagnostic.
Go to the first, previous, next, last section, table of contents.