researchv10no/cmd/pfort/readme - annotate

Return to readme CVS log

Up to [Research Unix] / researchv10no / cmd / pfort

Annotation of researchv10no/cmd/pfort/readme, revision 1.1.1.1

1.1 root 1: pfort can be compiled with the command run.
2: If the .o files already exist, the lod file can be used.
3: In each case, the .f files from the pfort tape
4: (or the corresponding .o files) without the last
5: line on the tape (which started with a dot in column one)
6: are compiled and loaded. In addition, the files pack.f
7: and unpack.f, written by me, are included in the compilation.
8: These pack and unpack routines are machine dependent
9: and must be written in assembly language on machines
10: that do not provide for byte manipulation in their
11: fortran. For the VAX, f77 programs were adequate for the job.
12: See readpfort2 for runcoms for making and testing
13: the pack and unpack programs.
14: See readpfort1 for how the tape was read.
15: The undefined: L15 recurs when run is used, and one gets
16: a huge PFORT file with 206760 bytes. (This has happened to
17: me before when something was undefined ore missing.)
18: However, a subsequent use of the lod command works and does not
19: complain about anything missing. It produced the PFORT file in this
20: directory which is slightly smaller than the OPFORT file
21: made previously. The latter is identical to /usr/lbin/PFORT
22: which I have executed on various files.
23: The compilation was done with the command
24: run > outt 2>outt2
25: The error messages in outt2 are all warnings. These warnings
26: may explain why I could not use the options to suppress printout.
27: the lod command produces output even though it complains about L15. !!!

unix.superglobalmegacorp.com

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.