g77install.texi

gcc-2.95.3 Linux下最常用的C编译器

@c Copyright (C) 1995-1999 Free Software Foundation, Inc.
@c This is part of the G77 manual.
@c For copying conditions, see the file g77.texi.

@c The text of this file appears in the file INSTALL
@c in the G77 distribution, as well as in the G77 manual.

@c Keep this the same as the dates above, since it's used
@c in the standalone derivations of this file (e.g. INSTALL).
@set copyrights 1995-1999

@set last-update-install 1999-07-17

@include root.texi

@ifset DOC-INSTALL
@c The immediately following lines apply to the INSTALL file
@c which is generated using this file.
@emph{Note:} This file is automatically generated from the files
@file{install0.texi} and @file{g77install.texi}.
@file{INSTALL} is @emph{not} a source file,
although it is normally included within source distributions.

This file contains installation information for the GNU Fortran compiler.
Copyright (C) @value{copyrights-install} Free Software Foundation, Inc.
You may copy, distribute, and modify it freely as long as you preserve
this copyright notice and permission notice.

@node Top,,, (dir)
@chapter Installing GNU Fortran
@end ifset

@set version-autoconf 2.12
@set version-bison 1.25
@set version-gperf 2.5
@set version-gzip 1.2.4
@set version-make 3.76.1
@set version-makeinfo 1.68
@set version-patch 2.5
@set version-sed 2.05
@set version-tar 1.12
@set version-texinfo 3.12

@ifset DOC-G77
@node Installation
@chapter Installing GNU Fortran
@cindex installing, GNU Fortran
@end ifset

The following information describes how to install @code{g77}.

@clear OMIT-FSF-G77

@ifset EGCS-G77
@set OMIT-FSF-G77
@end ifset

@ifset GCC-G77
@set OMIT-FSF-G77
@end ifset

@ifset OMIT-FSF-G77
Note that, for users of the @value{which-g77} version of @code{g77},
much of the information is obsolete,
and is superceded by the
@value{which-gcc} installation procedures.
Such information is accordingly omitted and flagged as such.
@end ifset

@ifclear OMIT-FSF-G77
The information in this file generally pertains to dealing
with @emph{source} distributions of @code{g77} and @code{gcc}.
It is possible that some of this information will be applicable
to some @emph{binary} distributions of these products---however,
since these distributions are not made by the maintainers of
@code{g77}, responsibility for binary distributions rests with
whoever built and first distributed them.

Nevertheless, efforts to make @code{g77} easier to both build
and install from source and package up as a binary distribution
are ongoing.
@end ifclear

@ifset DEVELOPMENT
@emph{Warning:} The information below is still under development,
and might not accurately reflect the @code{g77} code base
of which it is a part.
Efforts are made to keep it somewhat up-to-date,
but they are particularly concentrated
on any version of this information
that is distributed as part of a @emph{released} @code{g77}.

In particular, while this information is intended to apply to
the @value{which-g77} version of @code{g77},
only an official @emph{release} of that version
is expected to contain documentation that is
most consistent with the @code{g77} product in that version.
@end ifset

The following information was last updated on @value{last-update-install}:

@menu
* Prerequisites::          Make sure your system is ready for @code{g77}.
* Problems Installing::    Known trouble areas.
* Settings::               Changing @code{g77} internals before building.
* Quick Start::            The easier procedure for non-experts.
* Complete Installation::  For experts, or those who want to be: the details.
* Distributing Binaries::  If you plan on distributing your @code{g77}.
@end menu

@node Prerequisites
@section Prerequisites
@cindex prerequisites

@ifset OMIT-FSF-G77
For users of the @value{which-g77} version of @code{g77},
this information is superceded by the
@value{which-gcc} installation instructions.
@end ifset

@ifclear OMIT-FSF-G77
The procedures described to unpack, configure, build, and
install @code{g77} assume your system has certain programs
already installed.

The following prerequisites should be met by your
system before you follow the @code{g77} installation instructions:

@table @asis
@item @code{gzip} and @code{tar}
To unpack the @code{gcc} and @code{g77} distributions,
you'll need the @code{gunzip} utility in the @code{gzip}
distribution.
Most UNIX systems already have @code{gzip} installed.
If yours doesn't, you can get it from the FSF.

Note that you'll need @code{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 @code{gzip} used to package this release
is @value{version-gzip}.
(The version of GNU @code{tar} used to package this release
is @value{version-tar}.)

@item @file{gcc-@value{version-gcc}.tar.gz}
You need to have this, or some other applicable, version
of @code{gcc} on your system.
The version should be an exact copy of a distribution
from the FSF.
Its size is approximately 8.4MB.

If you've already unpacked @file{gcc-@value{version-gcc}.tar.gz} into a
directory (named @file{gcc-@value{version-gcc}}) called the @dfn{source tree}
for @code{gcc}, you can delete the distribution
itself, but you'll need to remember to skip any instructions to unpack
this distribution.

Without an applicable @code{gcc} source tree, you cannot
build @code{g77}.
You can obtain an FSF distribution of @code{gcc} from the FSF.

@item @file{g77-@value{version-g77}.tar.gz}
You probably have already unpacked this package,
or you are reading an advance copy of these installation instructions,
which are contained in this distribution.
The size of this package is approximately 1.4MB.

You can obtain an FSF distribution of @code{g77} from the FSF,
the same way you obtained @code{gcc}.

@item Enough disk space
The amount of disk space needed to unpack, build, install,
and use @code{g77} depends on the type of system you're
using, how you build @code{g77}, and how much of it you
install (primarily, which languages you install).

The sizes shown below assume all languages distributed in
@c As of `Version 2.249', texinfo.tex loses on a construction like
@c @code{...@value{...-...}...} since the hyphen is expanded as
@c -@discretionary{}{}{}, even though @value resets its catcode.
@c Fortunately this is currently the only instance.  Kluge, kluge.
@iftex
@begingroup @let@codedash=@realdash
@end iftex
@code{gcc-@value{version-gcc}},
@iftex
@endgroup
@end iftex
plus @code{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.

@itemize ---
@item
@code{gcc} and @code{g77} distributions occupy 10MB
packed, 40MB unpacked.
These consist of the source code and documentation,
plus some derived files (mostly documentation), for
@code{gcc} and @code{g77}.
Any deviations from these numbers for different
kinds of systems are likely to be very minor.

@item
A ``bootstrap'' build requires an additional 91MB
for a total of 132MB on an ix86, and an additional
136MB for a total of 177MB on an Alpha.

@item
Removing @file{gcc/stage1} after the build recovers
13MB for a total of 119MB on an ix86, and recovers
21MB for a total of 155MB on an Alpha.

After doing this, the integrity of the build can
still be verified via @samp{make compare}, and the
@code{gcc} compiler modified and used to build itself for
testing fairly quickly, using the copy of the compiler
kept in @code{gcc/stage2}.

@item
Removing @file{gcc/stage2} after the build further
recovers 39MB for a total of 80MB, and recovers
57MB for a total of 98MB on an Alpha.

After doing this, the compiler can still be installed,
especially if GNU @code{make} is used to avoid
gratuitous rebuilds (or, the installation can be done
by hand).

@item
Installing @code{gcc} and @code{g77} copies
23MB onto the @samp{--prefix} disk for a total of 103MB
on an ix86, and copies 31MB onto the @samp{--prefix}
disk for a total of 130MB on an Alpha.
@end itemize

After installation, if no further modifications and
builds of @code{gcc} or @code{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 @code{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 @file{gcc/stage1} and @file{gcc/stage2}
directories.

Installing @code{gcc} and @code{g77} over existing
versions might require less @emph{new} disk space,
but note that, unlike many products, @code{gcc}
installs itself in a way that avoids overwriting other
installed versions of itself, so that other versions may
easily be invoked (via @samp{gcc -V @var{version}}).

So, the amount of space saved as a result of having
an existing version of @code{gcc} and @code{g77}
already installed is not much---typically only the
command drivers (@code{gcc}, @code{g77}, @code{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).

@item @code{make}
Your system must have @code{make}, and you will probably save
yourself a lot of trouble if it is GNU @code{make} (sometimes
referred to as @code{gmake}).
In particular, you probably need GNU @code{make}
to build outside the source directory
(with @code{configure}'s @samp{--srcdir} option.)

The version of GNU @code{make} used to develop this release
is @value{version-make}.

@item @code{cc}
Your system must have a working C compiler.
If it doesn't, you might be able to obtain
a prebuilt binary of some version of @code{gcc}
from the network or on CD-ROM,
perhaps from the FSF@.
The best source of information about binaries
is probably a system-specific Usenet news group,
initially via its FAQ.

@xref{Installation,,Installing GNU CC,gcc,Using and Porting GNU CC},
for more information on prerequisites for installing @code{gcc}.

@item @code{sed}
All UNIX systems have @code{sed}, but some have a broken
version that cannot handle configuring, building, or
installing @code{gcc} or @code{g77}.

The version of GNU @code{sed} used to develop this release
is @value{version-sed}.
(Note that GNU @code{sed} version 3.0 was withdrawn by the
FSF---if you happen to have this version installed, replace
it with version @value{version-sed} immediately.
See a GNU distribution site for further explanation.)

@item @code{root} access or equivalent
To perform the complete installation procedures on a system,
you need to have @code{root} access to that system, or
equivalent access to the @samp{--prefix} directory tree
specified on the @code{configure} command line.

Portions of the procedure (such as configuring and building
@code{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 @code{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.

@item @code{autoconf}
The version of GNU @code{autoconf} used to develop this release
is @value{version-autoconf}.

@code{autoconf} is not needed in the typical case of
installing @code{gcc} and @code{g77}.
@xref{Missing tools?}, for information on when it
might be needed and how to work around not having it.

@item @code{bison}
The version of GNU @code{bison} used to develop this release
is @value{version-bison}.

@code{bison} is not needed in the typical case of
installing @code{gcc} and @code{g77}.
@xref{Missing tools?}, for information on when it
might be needed and how to work around not having it.

@item @code{gperf}
The version of GNU @code{gperf} used to develop this release
is @value{version-gperf}.

@code{gperf} is not needed in the typical case of
installing @code{gcc} and @code{g77}.
@xref{Missing tools?}, for information on when it
might be needed and how to work around not having it.

@item @code{makeinfo}
The version of GNU @code{makeinfo} used to develop this release
is @value{version-makeinfo}.