Improve g77 doc infrastructure

From-SVN: r25743
This commit is contained in:
Craig Burley 1999-03-13 12:04:03 +00:00 committed by Craig Burley
parent 4b632bf12c
commit 51efa892bf
11 changed files with 820 additions and 1041 deletions

View File

@ -1,3 +1,17 @@
Sat Mar 13 14:26:55 1999 Craig Burley <craig@jcb-sc.com>
* RELEASE-PREP: New file, lists things to do for a release.
* Make-lang.in, bugs.texi, bugs0.texi, g77.texi, g77install.texi,
install0.texi, news.texi, news0.texi: Accommodate new doc
architecture.
Consolidate news items. Don't describe old news items in
various generated docs.
Don't describe FSF-g77 installation stuff in various EGCS-g77
generated docs.
Move description of AUTOMATIC to more suitable location.
* root.texi: New file for new doc architecture.
Thu Mar 11 17:32:55 1999 Craig Burley <craig@jcb-sc.com>
* g77.texi: Add AUTOMATIC to list of unsupported extensions.

View File

@ -244,7 +244,7 @@ f77.dvi: f/g77.dvi
# g77 documentation.
f/g77.info: $(srcdir)/f/g77.texi $(srcdir)/f/bugs.texi \
$(srcdir)/f/g77install.texi $(srcdir)/f/news.texi \
$(srcdir)/f/intdoc.texi
$(srcdir)/f/intdoc.texi $(srcdir)/f/root.texi
case "$(LANGUAGES)" in \
*[fF]77*) touch lang-f77;; \
*) rm -f lang-f77;; \
@ -256,7 +256,7 @@ f/g77.info: $(srcdir)/f/g77.texi $(srcdir)/f/bugs.texi \
f/g77.dvi: $(srcdir)/f/g77.texi $(srcdir)/f/bugs.texi \
$(srcdir)/f/g77install.texi $(srcdir)/f/news.texi \
$(srcdir)/f/intdoc.texi
$(srcdir)/f/intdoc.texi $(srcdir)/f/root.texi
case "$(LANGUAGES)" in \
*[fF]77*) touch lang-f77;; \
*) rm -f lang-f77;; \
@ -306,15 +306,15 @@ $(srcdir)/f/intdoc.texi: f/intdoc.c f/intdoc.in f/ansify.c f/intrin.def f/intrin
rm f/intdoc f/ansify f/intdoc.h0; \
else true; fi
$(srcdir)/f/BUGS: f/bugs0.texi f/bugs.texi
$(srcdir)/f/BUGS: f/bugs0.texi f/bugs.texi f/root.texi
cd $(srcdir)/f; $(MAKEINFO) -D BUGSONLY --no-header --no-split \
--no-validate -o BUGS bugs0.texi
$(srcdir)/f/INSTALL: f/install0.texi f/g77install.texi
$(srcdir)/f/INSTALL: f/install0.texi f/g77install.texi f/root.texi
cd $(srcdir)/f; $(MAKEINFO) -D INSTALLONLY --no-header --no-split \
--no-validate -o INSTALL install0.texi
$(srcdir)/f/NEWS: f/news0.texi f/news.texi
$(srcdir)/f/NEWS: f/news0.texi f/news.texi f/root.texi
cd $(srcdir)/f; $(MAKEINFO) -D NEWSONLY --no-header --no-split \
--no-validate -o NEWS news0.texi

5
gcc/f/RELEASE-PREP Normal file
View File

@ -0,0 +1,5 @@
1999-03-13 RELEASE-PREP
Things to do to prepare a g77 release (FSF, egcs, whatever).
- Update root.texi: clear DEVELOPMENT flag, set version info.

View File

@ -1,30 +1,43 @@
@c Copyright (C) 1995-1998 Free Software Foundation, Inc.
@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 When changing the above copyright notice, be sure to
@c change the one in `bugs0.texi' accordingly, to effect
@c the change in the derived file `BUGS'.
@c The text of this file appears in the file BUGS
@c in the G77 distribution, as well as in the G77 manual.
@c 1999-03-03
@c Keep this the same as the dates above, since it's used
@c in the standalone derivations of this file (e.g. BUGS).
@set copyrights-bugs 1995-1999
@ifclear BUGSONLY
@node Actual Bugs
@section Actual Bugs We Haven't Fixed Yet
@end ifclear
@set last-update-bugs 1999-03-13
@include root.texi
@ifset DOC-BUGS
@c The immediately following lines apply to the BUGS file
@c which is derived from this file.
@emph{Note:} This file is automatically generated from the files
@file{bugs0.texi} and @file{bugs.texi}.
@file{BUGS} is @emph{not} a source file,
although it is normally included within source distributions.
This file lists known bugs in the @value{which-g77} version
of the GNU Fortran compiler.
Copyright (C) @value{copyrights-bugs} 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 Known Bugs In GNU Fortran
@end ifset
@ifset DOC-G77
@node Known Bugs
@section Known Bugs In GNU Fortran
@end ifset
This section identifies bugs that @code{g77} @emph{users}
might run into in
@ifhtml
the current development
@end ifhtml
version
@ifnothtml
@value{version-g77}
@end ifnothtml
might run into in the @value{which-g77} version
of @code{g77}.
This includes bugs that are actually in the @code{gcc}
back end (GBE) or in @code{libf2c}, because those
@ -32,22 +45,56 @@ sets of code are at least somewhat under the control
of (and necessarily intertwined with) @code{g77},
so it isn't worth separating them out.
@ifset DOC-G77
For information on bugs in @emph{other} versions of @code{g77},
@ifhtml
see the page on Fortran news.
@end ifhtml
@ifnothtml
@ref{News,,News About GNU Fortran}.
@end ifnothtml
There, lists of bugs fixed in various versions of @code{g77},
can help determine what bugs existed in prior versions.
@end ifset
@ifset DOC-BUGS
For information on bugs in @emph{other} versions of @code{g77},
see @file{@value{path-g77}/NEWS}.
There, lists of bugs fixed in various versions of @code{g77},
can help determine what bugs existed in prior versions.
@end ifset
@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
An online, ``live'' version of this document
(derived directly from the mainline, development version
of @code{g77} within @code{egcs})
is available via
@uref{http://egcs.cygnus.com/onlinedocs/g77_bugs.html}.
Follow the ``Known Bugs'' link.
@ifset DOC-G77
For information on bugs that might afflict people who
configure, port, build, and install @code{g77},
@ifhtml
see the chapter on installing in the @code{g77} documentation.
@end ifhtml
@ifnothtml
@ref{Problems Installing}.
@end ifnothtml
@end ifset
@ifset DOC-BUGS
For information on bugs that might afflict people who
configure, port, build, and install @code{g77},
see "Problems Installing" in @file{@value{path-g77}/INSTALL}.
@end ifset
The following information was last updated on @value{last-update-bugs}:
@itemize @bullet
@item
@ -129,14 +176,11 @@ improvements to the compiler.)
Note that @code{g77} does display a warning message to
notify the user before the compiler appears to hang.
@ifhtml
See the @code{g77} installation documentation
@end ifhtml
@ifnothtml
@ifset DOC-G77
@xref{Large Initialization,,Initialization of Large Aggregate Areas},
@end ifnothtml
for information on how to change the point at which
@code{g77} decides to issue this warning.
@end ifset
@cindex debugging
@cindex common blocks
@ -154,13 +198,10 @@ As of Version 0.5.19, a temporary kludge solution is provided whereby
some rudimentary information on a member is written as a string that
is the member's value as a character string.
@ifhtml
See the @code{g77} documentation
@end ifhtml
@ifnothtml
@ifset DOC-G77
@xref{Code Gen Options,,Options for Code Generation Conventions},
@end ifnothtml
for information on the @samp{-fdebug-kludge} option.
@end ifset
@cindex code, displaying main source
@cindex displaying main source code

View File

@ -1,21 +1,9 @@
\input texinfo @c -*-texinfo-*-
@c %**start of header
@c %**start of header
@setfilename BUGS
@set BUGSONLY
@c %**end of header
@c The immediately following lines apply to the BUGS file
@c which is generated using this file.
NOTE: This file is automatically generated from the files
`bugs0.texi' and `bugs.texi'. `BUGS' is *not* a source file,
although it is normally included within source distributions.
This file lists known bugs in the GNU Fortran compiler.
Copyright (C) 1995-1998 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 Bugs in GNU Fortran
@c This tells bugs.texi that it's generating just the BUGS file.
@set DOC-BUGS
@include bugs.texi
@bye

File diff suppressed because it is too large Load Diff

View File

@ -1,17 +1,35 @@
@c Copyright (C) 1995-1998 Free Software Foundation, Inc.
@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 When changing the above copyright notice, be sure to
@c change the one in `install0.texi' accordingly, to effect
@c the change in the derived file `INSTALL'.
@c The text of this file appears in the file INSTALL
@c in the G77 distribution, as well as in the G77 manual.
@c 1998-07-13
@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-03-13
@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-g77 0.5.24
@set version-gcc 2.8.1
@set version-autoconf 2.12
@set version-bison 1.25
@ -24,20 +42,32 @@
@set version-tar 1.12
@set version-texinfo 3.12
@ifclear INSTALLONLY
@ifset DOC-G77
@node Installation
@chapter Installing GNU Fortran
@end ifclear
@cindex installing, GNU Fortran
@end ifset
The following information describes how to install @code{g77}.
@ifset EGCS-G77
@set OMIT-FSF-G77
Note that, for @code{egcs} users,
much of this information is obsolete,
much of the information is obsolete,
and is superceded by the
@code{egcs} installation procedures.
Such information is explicitly flagged as such.
Such information is accordingly omitted and flagged as such.
@ifset DEVELOPMENT
@ifclear DOC-INSTALL
@clear OMIT-FSF-G77
(It is not actually omitted from the development version of this documentation,
so the @code{g77} developers can easily find all the documentation
for all versions of @code{g77} in one place.)
@end ifclear
@end ifset
@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
@ -49,6 +79,25 @@ 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}.
@ -63,10 +112,12 @@ are ongoing.
@section Prerequisites
@cindex prerequisites
@emph{Version info:}
For @code{egcs} users, the following information is
@ifset EGCS-G77
For @code{egcs} users, this information is
superceded by the @code{egcs} 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.
@ -342,6 +393,8 @@ instead of the entire @file{.tar.gz} distribution
to rebuild derived files, such as @code{makeinfo}).
@end table
@end ifclear
@node Problems Installing
@section Problems Installing
@cindex problems installing
@ -389,7 +442,7 @@ so there are no plans for an interim fix.
This requirement does not mean you must already have @code{gcc}
installed to build @code{g77}.
As long as you have a working C compiler, you can use a
bootstrap build to automate the process of first building
``bootstrap'' build to automate the process of first building
@code{gcc} using the working C compiler you have, then building
@code{g77} and rebuilding @code{gcc} using that just-built @code{gcc},
and so on.
@ -429,10 +482,12 @@ is not yet established.
@cindex @code{ld}, can't find _strtoul
@cindex SunOS4
@emph{Version info:}
The following information does not apply to the
@ifset EGCS-G77
This information does not apply to the
@code{egcs} version of @code{g77}.
@end ifset
@ifclear OMIT-FSF-G77
On SunOS4 systems, linking the @code{f771} program used to
produce an error message concerning an undefined symbol named
@samp{_strtoul}, because the @samp{strtoul} library function
@ -447,7 +502,7 @@ but every attempt at this has failed for at least one kind of system.
To limit the failures to those few systems actually missing the
required routines, the bare-bones versions are still provided,
in @file{gcc/f/proj.c},
in @file{@value{path-g77}/proj.c},
if the appropriate macros are defined.
These are @code{NEED_BSEARCH} for @samp{bsearch} and
@code{NEED_STRTOUL} for @samp{NEED_STRTOUL}.
@ -455,7 +510,7 @@ These are @code{NEED_BSEARCH} for @samp{bsearch} and
Therefore, if you are sure your system is missing
@code{bsearch} or @code{strtoul} in its library,
define the relevant macro(s) before building @code{g77}.
This can be done by editing @file{gcc/f/proj.c} and inserting
This can be done by editing @file{@value{path-g77}/proj.c} and inserting
either or both of the following @samp{#define} statements
before the comment shown:
@ -474,15 +529,17 @@ To build with the bundled @code{cc} on SunOS4, for example, try:
make bootstrap BOOT_CFLAGS='-O2 -g -DNEED_STRTOUL'
@end smallexample
If you then encounter problems compiling @file{gcc/f/proj.c},
If you then encounter problems compiling @file{@value{path-g77}/proj.c},
it might be due to a discrepancy between how @samp{bsearch}
or @samp{strtoul} are defined by that file and how they're
declared by your system's header files.
In that case, you'll have to use some basic knowledge of C
to work around the problem, perhaps by editing @file{gcc/f/proj.c}
to work around the problem, perhaps by editing @file{@value{path-g77}/proj.c}
somewhat.
@end ifclear
@node Cleanup Kills Stage Directories
@subsubsection Cleanup Kills Stage Directories
@cindex stage directories
@ -536,7 +593,9 @@ be fixed in a future version of @code{gcc}.
A linker bug on some versions of AIX 4.1 might prevent building
when @code{g77} is built within @code{gcc}.
It might also occur when building within @code{egcs}.
@ifset DOC-G77
@xref{LINKFAIL}.
@end ifset
@node Cross-compiler Problems
@subsection Cross-compiler Problems
@ -601,7 +660,7 @@ system, depending on the systems involved in the configuration.
@section Changing Settings Before Building
Here are some internal @code{g77} settings that can be changed
by editing source files in @file{gcc/f/} before building.
by editing source files in @file{@value{path-g77}/} before building.
This information, and perhaps even these settings, represent
stop-gap solutions to problems people doing various ports
@ -641,7 +700,7 @@ the use of unit numbers higher than 99, you can change the
value of the @samp{MXUNIT} macro, which represents the maximum unit
number, to an appropriately higher value.
To do this, edit the file @file{f/runtime/libI77/fio.h} in your
To do this, edit the file @file{@value{path-libf2c}/libI77/fio.h} in your
@code{g77} source tree, changing the following line:
@example
@ -707,7 +766,7 @@ modify the @code{g77} source tree so that the version of
@code{libg2c} is built with the @samp{ALWAYS_FLUSH} macro
defined, enabling this behavior.
To do this, find this line in @file{f/runtime/f2c.h} in
To do this, find this line in @file{@value{path-libf2c}/f2c.h} in
your @code{g77} source tree:
@example
@ -729,7 +788,7 @@ Then build or rebuild @code{g77} as appropriate.
@cindex segmentation violation
@code{g77}, on most machines, puts many variables and arrays on the stack
where possible, and can be configured (by changing
@samp{FFECOM_sizeMAXSTACKITEM} in @file{gcc/f/com.c}) to force
@samp{FFECOM_sizeMAXSTACKITEM} in @file{@value{path-g77}/com.c}) to force
smaller-sized entities into static storage (saving
on stack space) or permit larger-sized entities to be put on the
stack (which can improve run-time performance, as it presents
@ -777,7 +836,7 @@ a factor of 10.
This size currently is quite small, since @code{g77}
currently has a known bug requiring too much memory
and time to handle such cases.
In @file{gcc/f/data.c}, the macro
In @file{@value{path-g77}/data.c}, the macro
@samp{FFEDATA_sizeTOO_BIG_INIT_} is defined
to the minimum size for the warning to appear.
The size is specified in storage units,
@ -831,10 +890,12 @@ systems.
@section Quick Start
@cindex quick start
@emph{Version info:}
For @code{egcs} users, the following information is
@ifset EGCS-G77
For @code{egcs} users, this information is
superceded by the @code{egcs} installation instructions.
@end ifset
@ifclear OMIT-FSF-G77
This procedure configures, builds, and installs @code{g77}
``out of the box'' and works on most UNIX systems.
Each command is identified by a unique number,
@ -1112,13 +1173,17 @@ around anymore.
Removing them can free up a lot of disk space.
@end table
@end ifclear
@node Complete Installation
@section Complete Installation
@emph{Version info:}
For @code{egcs} users, the following information is
mostly superceded by the @code{egcs} installation instructions.
@ifset EGCS-G77
For @code{egcs} users, this information is
superceded by the @code{egcs} installation instructions.
@end ifset
@ifclear OMIT-FSF-G77
Here is the complete @code{g77}-specific information on how
to configure, build, and install @code{g77}.
@ -1270,7 +1335,7 @@ the directories they create.)
If your version of @code{gcc} is older than the oldest version
supported by @code{g77}
(as casually determined by listing the contents of @file{gcc/f/INSTALL/},
(as casually determined by listing the contents of @file{@value{path-g77}/INSTALL/},
which contains these installation instructions in plain-text format),
you should obtain a newer, supported version of @code{gcc}.
(You could instead obtain an older version of @code{g77},
@ -1295,9 +1360,7 @@ it is likely that @file{gcc-2.8.2} would work well with @code{g77}.
However, @file{gcc-2.9.0} would almost certainly
not work with that version of @code{g77}
without appropriate modifications,
so a new version of @code{g77} would be needed (and you should
wait for it rather than bothering the maintainers---@pxref{Changes,,
User-Visible Changes}).
so a new version of @code{g77} would be needed.
@cindex distributions, why separate
@cindex separate distributions
@ -1314,7 +1377,7 @@ and such changes require corresponding changes to
the @code{g77} front end (FFE).
@c @pindex config-lang.in
@c @emph{Note:} @code{g77}'s configuration file @file{gcc/f/config-lang.in}
@c @emph{Note:} @code{g77}'s configuration file @file{@value{path-g77}/config-lang.in}
@c sometimes ensures that the source code for the version of @code{gcc}
@c being configured has at least one indication of being an appropriate
@c version as required specifically by @code{g77}.
@ -1907,7 +1970,7 @@ do @emph{not} do @samp{make maintainer-clean}, and, to ensure that
type these commands:
@example
sh# @kbd{cd gcc/f/runtime}
sh# @kbd{cd @value{path-libf2c}}
sh# @kbd{touch configure libU77/configure}
sh# @kbd{cd ../../..}
sh#
@ -1978,11 +2041,19 @@ sh# @kbd{cd ..}
sh#
@end example
@end ifclear
@node Distributing Binaries
@section Distributing Binaries
@cindex binaries, distributing
@cindex code, distributing
@ifset EGCS-G77
For @code{egcs} users, this information is
superceded by the @code{egcs} installation instructions.
@end ifset
@ifclear OMIT-FSF-G77
If you are building @code{g77} for distribution to others in binary form,
first make sure you are aware of your legal responsibilities (read
the file @file{gcc/COPYING} thoroughly).
@ -2101,7 +2172,7 @@ If it is not included, users will have trouble understanding
diagnostics messages and other such things, and will send
you a lot of email asking questions.
Please edit this documentation (by editing @file{gcc/f/*.texi}
Please edit this documentation (by editing @file{@value{path-g77}/*.texi}
and doing @samp{make doc} from the @file{/usr/src/gcc} directory)
to reflect any changes you've made to @code{g77}, or at
least to encourage users of your binary distribution to
@ -2172,3 +2243,5 @@ and distributions, about which nothing could be done for the
user.
Once you are quite certain a bug report does not involve
your efforts, you can forward it to us.
@end ifclear

View File

@ -1,21 +1,9 @@
\input texinfo @c -*-texinfo-*-
@c %**start of header
@setfilename INSTALL
@set INSTALLONLY
@c %**end of header
@c The immediately following lines apply to the INSTALL file
@c which is generated using this file.
NOTE: This file is automatically generated from the files
`install0.texi' and `g77install.texi'. `INSTALL' is *not* a source
file, although it is normally included within source distributions.
This file contains installation information for the GNU Fortran compiler.
Copyright (C) 1995-1998 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
@c This tells g77install.texi that it's generating just the INSTALL file.
@set DOC-INSTALL
@include g77install.texi
@bye

File diff suppressed because it is too large Load Diff

View File

@ -1,21 +1,9 @@
\input texinfo @c -*-texinfo-*-
@c %**start of header
@setfilename NEW
@set NEWSONLY
@c %**start of header
@setfilename NEWS
@c %**end of header
@c The immediately following lines apply to the NEWS file
@c which is generated using this file.
NOTE: This file is automatically generated from the files
`news0.texi' and `news.texi'. `NEWS' is *not* a source file,
although it is normally included within source distributions.
This file lists recent changes to the GNU Fortran compiler.
Copyright (C) 1995-1999 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 News About GNU Fortran
@c This tells news.texi that it's generating just the NEWS file.
@set DOC-NEWS
@include news.texi
@bye

33
gcc/f/root.texi Normal file
View File

@ -0,0 +1,33 @@
@c DEVELOPMENT is set to indicate an in-development version,
@c as compared to a release version. When making a release
@c (e.g. a release branch in the CVS repository for egcs),
@c clear this and set the version information correctly.
@set DEVELOPMENT
@set version-g77 0.5.24
@set version-egcs 1.2
@c EGCS-G77 is set to indicate this is the EGCS version of g77.
@set EGCS-G77
@ifclear EGCS-G77
@c FSF-G77 is set to indicate this is the FSF version of g77.
@set FSF-G77
@end ifclear
@ifset EGCS-G77
@set email-general egcs@@egcs.cygnus.com
@set email-bugs egcs-bugs@@egcs.cygnus.com
@set path-g77 egcs/gcc/f
@set path-libf2c egcs/libf2c
@set which-g77 EGCS-@value{version-egcs}
@end ifset
@ifset FSF-G77
@set email-general fortran@@gnu.org
@set email-bugs fortran@@gnu.org
@set path-g77 gcc/f
@set path-libf2c gcc/f/runtime
@set which-g77 FSF-@value{version-g77}
@end ifset
@set email-burley craig@@jcb-sc.com