This file contains instructions for installing f2c on your system.  This
saveset contains an executable image for f2c as well as an object library
for f2c support.  Command files for building f2c and the f2c support library
are also included if you desire to rebuild f2c.  The steps to install f2c on
a VAX/VMS system are;

1.  Decide where you want f2c, the f2c support library, and the f2c header
    file to live.  We keep these files in a public directory named
    SYS$PUBLIC:.  If you want to also keep these files in an equivalent
    directory,  just copy the files to the directory and set the protection
    to read/execute.  If you want to keep the files in another directory
    will probably want to modify main.c and names.c to contain the directory
    path for the f2c header file.  You may want to change the directory to
    something of your own liking ( i.e. #include "user:f2c.h" ) or let
    your users specify their own headers ( i.e. have main.c be #include 
    "f2c.h" and the file f2c.h be either a copy of the f2c header file
    or a file which is just #include "user:f2c.h" ).  You will also need
    to modify the link message in sysdep.c which prints the header message
    at the top of each source file converted by f2c to reflect the new path
    of the f2c support library.  In either case,  once you have decided where
    you want these files to reside,  copy these files to that directory and
    set the protection to read/execute.

2.  Define a foreign command for the access of f2c.  We use;

    $ f2c :== $sys$public:f2c.exe

    in SYLOGIN.COM.  You may want to put the definition there are have users
    add it to their LOGIN.COM files.  The directory specification should be
    the directory where you decided to put f2c.

3.  If you desire,  copy the f2c documentation files ( f2c.1, f2c.ps, f2c.doc,
    f2c.dvi and f2c_technical_report.ps ) to some public documentation area.
    f2c.1 and f2c_technical_report.ps are the documentation files as provided
    by AT&T.  f2c.ps, f2c.doc, and f2c.dvi are locally developed documentation
    files which were created by running the f2c man page through tr2tex and
    then using the resulting output as a base for local documentation.  If
    you choose to use these TeX based documents,  please be sure to make the
    appropriate changes in the location of files.  Be sure and set the
    appropriate protection for the documentation files.

    You may also wish to install the f2c help file in a help library.  If
    you have changed the location of where the header or object library
    files reside,  you will first need to edit F2C.RNH to reflect these
    changes.  If you modify the source file for the f2c help file,  you
    will need to use RUNOFF on the file before installing it in a help
    library.  F2C.RNH and the resulting .HLP file were locally developed.



Good luck!!!

Robert Schneider

+-------------------------------------+-------------------------------------+
|Robert Schneider                     |  Internet: robert@perv.pe.utexas.edu|
|Department of Petroleum Engineering  |  BITNET: pefv673@utchpc             |
|University of Texas at Austin        |  THEnet: PERV::ROBERT               |
+-------------------------------------+-------------------------------------+