           Steps to compile and link individual f_solve programs.
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


1. Run the following UNIX C-shell or tcshell commands to set various 
   environment variables:

   setenv MK4_ROOT      <path_to_root_directorty_of_your_solve_source_code> 
   setenv SAVE_DIR      <directory_for_input_solve_mod_files_etc.> 
   source ${MK4_ROOT}/solve_var

  alias  rmo $cwd/*.o; echo "All object files were deleted in $cwd"

       For example:

  setenv MK4_ROOT       /box3/mk4
  setenv SAVE_DIR       /data1/solve_files/
  source ${MK4_ROOT}/solve_var

  It is desirable to put these commands in the startup command file
  ( .tcshrc under tcsh or .cshrc and csh ) since these environment variables 
  always should be setup before compilation and lining SOLVE. Compilation 
  scripts check setting these environment variables and refuse to work unless 
  these variables are setup.

There are two ways to compile and link an individual SOLVE program

Alternative a:

2a. Run the make_one_solve script, which is located in the solve source
   directory, as follows:
    
    make_one_solve <your_installation> <solve_subdirectory_to_be_made>
  
     e.g., make_one_solve GSFC norml

3a. Check make_one_solve_errs in your solve source directory for errors.

Alternative b:
2b.
  
  cd <target_directory>
  rmo
  make 


Please, never use command "touch", use "rmo" instead of! Touch resets
modification dates of source files what makes difficult version changes tracing.

For questions, please contact Karen Baver at kdb@leo.gsfc.nasa.gov or
Leonid Petrov pet@leo.gsfc.nasa.gov

     ********   K. Baver   5/26/99    ***********
