| 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
|
|---|
|
|---|
