summaryrefslogtreecommitdiff
path: root/gnu/usr.bin/gcc/f/gbe/README
diff options
context:
space:
mode:
Diffstat (limited to 'gnu/usr.bin/gcc/f/gbe/README')
-rw-r--r--gnu/usr.bin/gcc/f/gbe/README64
1 files changed, 42 insertions, 22 deletions
diff --git a/gnu/usr.bin/gcc/f/gbe/README b/gnu/usr.bin/gcc/f/gbe/README
index 0e7585f90c3..1752b600aed 100644
--- a/gnu/usr.bin/gcc/f/gbe/README
+++ b/gnu/usr.bin/gcc/f/gbe/README
@@ -1,33 +1,53 @@
-951118
-
-This directory contains .diff files for various GNU CC distributions.
-The name of a file tells which version to which it applies. Prior to
-gcc version 2.7.1, g77 will not build without the appropriate .diff
-file applied to the GNU CC distribution via patch. That is because
-g77 needs certain changes to be made to the GNU CC back end, which
-it shares with not only the C front end, but with other GNU front
-ends (C++, Objective-C, Pascal, ADA, Chill, ...) as well. Version
-2.7.1 of gcc includes the changes needed by g77 versions through 0.5.17.
-Future versions of g77 might again require changes to versions 2.7.1,
-and later versions, of gcc.
+961207
+
+This directory contains .diff files for various GNU CC distributions
+supported by this version of GNU Fortran.
+
+The name of a file includes which gcc version to which it applies.
+For example, 2.7.2.1.diff is the patch file for gcc version 2.7.2.1.
+
+To apply a .diff file to, say, gcc 2.7.2, one might use the following
+command (where the current directory contains the gcc source distribution
+after merging into it the g77 source distribution, which would be
+named gcc-2.7.2 in this example):
+
+ patch -p1 -d gcc-2.7.2 < gcc-2.7.2/f/gbe/2.7.2.diff
+
+
+This version of g77 is best combined with gcc versions 2.7.2 or 2.7.2.1.
+
+However, note that applying the patch for version 2.7.2.1
+does _not_ update the gcc.info* files that constitute the Info
+documentation for gcc. Therefore, after applying the 2.7.2.1.diff
+patch to the gcc-2.7.2.1 source directory, you must rebuild the
+Info documentation yourself via:
+
+ cd gcc-2.7.2.1; make -f Makefile.in gcc.info
+
+If the above command doesn't work because you don't have makeinfo
+installed, you are STRONGLY encouraged to obtain the most recent
+version of the GNU texinfo package (texinfo-3.9.tar.gz as of this
+writing), build, and install it, then try the above command (as
+makeinfo is part of texinfo).
+
+(The 2.7.2.1 patch omits the gcc.info* patches because your gcc-2.7.2.1
+might have one of at least two different versions of these gcc.info*
+files, depending on how you obtained the gcc source directory -- by
+unpacking gcc-2.7.2.1.tar.gz directly, or by applying a patch to upgrade
+a copy of gcc-2.7.2.)
This distribution of g77 is not supported for versions of gcc prior
to 2.6.2. The 2.6.3 patch file should work for version 2.6.2, but
you should probably use gcc-2.6.3 in any case if that is possible.
-To apply a .diff file to, say, gcc 2.7.0, one might use the following
-command:
-
- patch -p1 -d gcc-2.7.0 < gcc-2.7.0/f/gbe/2.7.0.diff
-
If you are using a version of gcc more recent than the most
recent .diff file's version, try the most recent .diff ONLY
if the difference is in the third field. E.g. the above
-patch might work on gcc-2.6.4 or gcc-2.6.5 if these were
+patch might work on gcc-2.7.3 or gcc-2.7.4 if these were
released. On the other hand, it probably wouldn't work for
-a more major release like gcc-2.7.0 or gcc-3.0.0, and you
+a more major release like gcc-2.8.0 or gcc-3.0.0, and you
shouldn't try it. If the .diff file is missing, don't bother
asking `fortran@gnu.ai.mit.edu' for it -- it is certainly
-being worked on. In the meantime, watch the usual channels
-(see gcc/f/DOC *TROUBLE (BUGS, ETC.)*) for information on
-support for the new version of gcc.
+being worked on. In the meantime, watch the usual place
+(`info -f g77') for information on support for the recent
+versions of gcc.