There is 1 other file named ftn5a.fig in the archive. Click here to see a list.
FORTRAN-10 Installation Guide
COPYRIGHT (C) 1975,1977 BY
DIGITAL EQUIPMENT CORPORATION, MAYNARD, MASS.
THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND COPIED
ONLY IN ACCORDANCE WITH THE TERMS OF SUCH LICENSE AND WITH THE
INCLUSION OF THE ABOVE COPYRIGHT NOTICE. THIS SOFTWARE OR ANY OTHER
COPIES THEREOF MAY NOT BE PROVIDED OR OTHERWISE MADE AVAILABLE TO ANY
OTHER PERSON. NO TITLE TO AND OWNERSHIP OF THE SOFTWARE IS HEREBY
THE INFORMATION IN THIS SOFTWARE IS SUBJECT TO CHANGE WITHOUT NOTICE
AND SHOULD NOT BE CONSTRUED AS A COMMITMENT BY DIGITAL EQUIPMENT
DIGITAL ASSUMES NO RESPONSIBILITY FOR THE USE OR RELIABILITY OF ITS
SOFTWARE ON EQUIPMENT WHICH IS NOT SUPPLIED BY DIGITAL.
FTN5A.FIG - Fortran-10 Page 2
FORTRAN-10 Installation Guide
This document describes the procedures for installing version 5A(621)
of the FORTRAN compiler, version 5A(721) of FOROTS (the FORTRAN object
time system) and FORLIB (the FORTRAN library) and version 5A(101) of
FORDDT (the FORTRAN debugger). The procedures described herein are:
1. Installation of the FORTRAN binary files
Building the FORTRAN compiler from sources
Using the FORTRAN compiler with DDT
Building a single segment version of FORTRAN
2. Installation of the FOROTS and FORLIB binary files
Building FOROTS and FORLIB from sources
3. Installation of FORDDT
FORTRAN, FORLIB, FOROTS and FORDDT should be installed on SYS:.
The release is in the form of a BACKUP tape in INTERCHANGE format.
The following files (or groups of files) are included:
1. FORTRAN binary files
2. FORTRAN source and object files
3. B10FTN.CTL - control file to build the compiler from sources
4. *.CMD - loader and assembly indirect command files
5. FORDDT.MAC and .REL
6. FTN5A1.DIR - a directory of all files on the tape
7. .DOC and .HLP files for all software
8. FOROTS and FORLIB source and command files
9. B10FRS.CTL - control file to build FORLIB and FOROTS for both
the KA10 and KI/KL10 from sources
10. BLIS10.EXE version 7B(222) which is used by this release of
FORTRAN, BLIS10.HLP and BLIS10.ERR (the BLIS10 error message
11. B10FDT.CTL - control file to build FORDDT from the source
FTN5A.FIG - Fortran-10 Page 3
2.0 INSTALLATION AND BUILDING OF THE COMPILER
2.1 Installation of the FORTRAN Binary Files
The following files comprise the FORTRAN compiler. Merely copying
these files from the distribution tape provides a working FORTRAN
compiler. FORTRAN works on a KA10, KI10 or KL10. The files are:
2.2 Building the FORTRAN Compiler From Sources
LINK 2B(436) or later
MAKLIB 2(14) or later
Running the control file B10FTN.CTL will build the compiler from its
sources and produce the binary files. It has successfully built and
loaded the compiler at the Digital Equipment Corporation - Marlboro
computer facilities. This, however, in no way guarantees its
operation or support.
The control file used to build the compiler in house uses a private
pack called FTN. All references to BLIS10 are on "BLS:" in order to
use version 7B(222) of BLIS10. All references to MACRO are on "ASM:"
in order to use MACRO 52. BLIS10.EXE 7B(222) is included on the
FORTRAN release tape. One other set of files references [10,7] (DEC:)
and [5,11] (REL:) for several files. These are the LINK .CMD files
which use WILD, HELPER, and JOBDAT from [10,7] and SCAN from REL:.
It should be noted that building the FORTRAN compiler from the sources
provided is not a trivial computational task. It requires a
considerable amount of computer resources. All of the modules will
compile within 70K of user core with the exception of LEXICA.BLI which
requires 75K. The complete execution of B10FTN.CTL required at least
2 and 1/2 hours on a KA10. It is advised that only installations
desiring to modify the compiler contemplate completely rebuilding it.
In addition, it should be noted that the supplied control files are
divided into clearly commented sections so that it can easily be
determined which phases need to be reloaded if modifications are made.
FTN5A.FIG - Fortran-10 Page 4
Therefore, installations inserting their own modifications into the
compiler usually need only recompile the modules changed and reload
the overlays affected without rebuilding the entire compiler. See
MODULE.DOC for a list of which modules are in which phases.
(Note: when loading the programs LEFT72, LEFTFM and BUILD, undefined
globals may be encountered. These should be ignored.)
When LINKing the .REL files, in all but FORTRA, one can expect 4
undefined globals (.TNEWL, .POPJ1, .SWDON and .TCRLF.). These are due
to the particular method used to load the compiler and can be ignored.
They occur in the code which is loaded into the .LOW segment (to line
up all data references). Since these .LOW segments are unused, the
undefined references are meaningless.
The set of control files called LIST?.CTL will produce a complete set
of source listings of the compiler.
2.3 Using the FORTRAN Compiler with DDT
The release tape contains a version of the segmented compiler loaded
with DDT under the names DORT*.EXE. These files must be renamed to
FORT*.EXE before use.
If for some reason it is desired to load the compiler with DDT, there
is a series of LINK indirect files included which are analogous to the
?.CMD files used in B10FTN.CTL. They are D?.CMD and are used in the
same fashion as the ?.CMD files.
Since only break points in the low segment are phase independent, the
standard technique to set a break point is to set one in FORTRA -
module MAIN at GETSG+53 and then SAVE the segment. This will cause a
break point to occur at the beginning of each phase of the compiler
just after it is loaded. At this point, break points can be set in
the particular phase. These phase-dependent breakpoints should be
removed prior to bringing the next segment into core.
2.4 Building a Single Segment Version of FORTRAN
The LINK indirect file ALL.CMD (and the DDT version DALL.CMD) is
included and can be used to load a 81K single segment version of the
compiler. This is particularly attractive for installations where the
job mix contains many FORTRAN compilations of several small
subroutines, especially if they are handled in batch mode. The single
segment version is comprised of the same modules as the multi-segment
version with the exceptions that the ERROV?.BLI modules are not needed
and ONESEG.REL is used instead of MAIN.REL. ONESEG is simply a
recompilation of MAIN.BLI, recompiled with the compilation control
variable FT1SEG in the REQUIREd file FT1SEG.REQ (built as FT1SEG.ON in
B10FTN.CTL) set to 1 rather than 0. This eliminates the GETSEGs.
Note that ONESEG.REL and FT1SEG.ON as well as SINGLE.EXE, etc are
included on the FORTRAN release tape.
FTN5A.FIG - Fortran-10 Page 5
3.0 FOROTS AND FORLIB
3.1 Installation of the FOROTS and FORLIB Binary Files
FOROTS and FORLIB are processor dependent. Therefore the FORTRAN
release tape contains versions to run on both the KA10 and KI/KL10:
FORLKA.REL and FOROKA.SHR are for the KA; FORLKI.REL and FOROKI.EXE
are for the KI or KL. Rename the appropriate modules to FORLIB.REL
and FOROTS.EXE or .SHR.
3.2 Building FOROTS and FORLIB From Sources
The control file B10FRS.CTL can be used to build FOROTS and FORLIB
(both the KA and KI/KL versions) from the sources. Notice that the
build process uses structure FTN and field image software and ASM:
for MACRO 52 and MKL: for MAKLIB.
4.0 Installation of FORDDT
To install FORDDT, copy FORDDT.REL and FORDDT.HLP from the release
tape. FORDDT will work on a KA10, KI10 or KL10.
To rebuild, simply assemble FORDDT.MAC, run off FDT5A.RNH or use the
control file B10FDT.CTL.
[End of FTN5A.FIG]