| 1 |
|
|---|
| 2 | ====== old index for f2c, now "readme from f2c" ============
|
|---|
| 3 |
|
|---|
| 4 | FILES:
|
|---|
| 5 |
|
|---|
| 6 | f2c.h Include file necessary for compiling output of the converter.
|
|---|
| 7 | See the second NOTE below.
|
|---|
| 8 |
|
|---|
| 9 | f2c.1 Man page for f2c.
|
|---|
| 10 |
|
|---|
| 11 | f2c.1t Source for f2c.1 (to be processed by troff -man or nroff -man).
|
|---|
| 12 |
|
|---|
| 13 | libf77 Library of non I/O support routines the generated C may need.
|
|---|
| 14 | Fortran main programs result in a C function named MAIN__ that
|
|---|
| 15 | is meant to be invoked by the main() in libf77.
|
|---|
| 16 |
|
|---|
| 17 | libi77 Library of Fortran I/O routines the generated C may need.
|
|---|
| 18 | Note that some vendors (e.g., BSD, Sun and MIPS) provide a
|
|---|
| 19 | libF77 and libI77 that are incompatible with f2c -- they
|
|---|
| 20 | provide some differently named routines or routines with the
|
|---|
| 21 | names that f2c expects, but with different calling sequences.
|
|---|
| 22 | On such systems, the recommended procedure is to merge
|
|---|
| 23 | libf77 and libi77 into a single library, say libf2c, and to
|
|---|
| 24 | install it where you can access it by specifying -lf2c . The
|
|---|
| 25 | definition of link_msg in sysdep.c assumes this arrangement.
|
|---|
| 26 |
|
|---|
| 27 | Both libf77 and libi77 are bundles, meant to be unpacked by the
|
|---|
| 28 | Bourne (or Korn) shell. MS-DOS users can use the MKS Toolkit
|
|---|
| 29 | to unpack libf77 and libi77.
|
|---|
| 30 |
|
|---|
| 31 | libf2c.zip
|
|---|
| 32 | Only available by ftp: combination of libf77 and libi77, with
|
|---|
| 33 | Unix and PC makefiles.
|
|---|
| 34 |
|
|---|
| 35 | f2c.ps Postscript for a technical report on f2c. After you strip the
|
|---|
| 36 | mail header, the first line should be "%!PS".
|
|---|
| 37 |
|
|---|
| 38 | fixes The complete change log, reporting bug fixes and other changes.
|
|---|
| 39 | (Some recent change-log entries are given below).
|
|---|
| 40 |
|
|---|
| 41 | fc A shell script that uses f2c and imitates much of the behavior
|
|---|
| 42 | of commonly found f77 commands. You will almost certainly
|
|---|
| 43 | need to adjust some of the shell-variable assignments to make
|
|---|
| 44 | this script work on your system.
|
|---|
| 45 |
|
|---|
| 46 |
|
|---|
| 47 | SUBDIRECTORY:
|
|---|
| 48 |
|
|---|
| 49 | f2c/src Source for the converter itself, including a file of checksums
|
|---|
| 50 | and source for a program to compute the checksums (to verify
|
|---|
| 51 | correct transmission of the source), is available: ask netlib
|
|---|
| 52 | (e.g., [email protected]) to
|
|---|
| 53 | send all from f2c/src
|
|---|
| 54 | If the checksums show damage to just a few source files, or if
|
|---|
| 55 | the change log file (see "fixes" below) reports corrections to
|
|---|
| 56 | some source files, you can request those files individually
|
|---|
| 57 | "from f2c/src". For example, to get defs.h and xsum0.out, you
|
|---|
| 58 | would ask netlib to
|
|---|
| 59 | send defs.h xsum0.out from f2c/src
|
|---|
| 60 | "all from f2c/src" is about 640 kilobytes long; for convenience
|
|---|
| 61 | (and checksums), it includes copies of f2c.h, f2c.1, and f2c.1t.
|
|---|
| 62 |
|
|---|
| 63 | Tip: if asked to send over 99,000 bytes in one request, netlib
|
|---|
| 64 | breaks the shipment into 1000 line pieces and sends each piece
|
|---|
| 65 | separately (since otherwise some mailers might gag). To avoid
|
|---|
| 66 | the hassle of reassembling the pieces, try to keep each request
|
|---|
| 67 | under 99,000 bytes long. The final number in each line of
|
|---|
| 68 | xsum0.out gives the length of each file in f2c/src. For
|
|---|
| 69 | example,
|
|---|
| 70 | send exec.c expr.c from f2c/src
|
|---|
| 71 | send format.c format_data.c from f2c/src
|
|---|
| 72 | will give you slightly less hassle than
|
|---|
| 73 | send exec.c expr.c format.c format_data.c from f2c/src
|
|---|
| 74 | Alternatively, if all the mailers in your return path allow
|
|---|
| 75 | long messages, you can supply an appropriate mailsize line in
|
|---|
| 76 | your netlib request, e.g.
|
|---|
| 77 | mailsize 200k
|
|---|
| 78 | send exec.c expr.c format.c format_data.c from f2c/src
|
|---|
| 79 |
|
|---|
| 80 | The makefile used to generate gram.c; now we distribute a
|
|---|
| 81 | working gram.c, and you must say
|
|---|
| 82 | make gram1.c
|
|---|
| 83 | mv gram1.c gram.c
|
|---|
| 84 | if you want to generate your own gram.c -- there are just too
|
|---|
| 85 | many broken variants of yacc floating around nowadays for
|
|---|
| 86 | generation of gram.c to be the default.
|
|---|
| 87 |
|
|---|
| 88 | NOTE: You may exercise f2c by sending [email protected]
|
|---|
| 89 | a message whose first line is "execute f2c" and whose remaining
|
|---|
|
|---|
