G. Levine
10/96

On the Alpha we have an Ada83 GNU compiler, which you probably don't
  want to use.  If you do, you must create a library once

   mkdir ada  (or any directory name)
   cd ada
   amklib adalib     

Then each time you login (or put in your login shell)

setenv ADALIB @/home/faculty/levine/myadalib/adalib  
                                      (for csh or tcsh)

or

ADALIB=@/home/faculty/levine/myadalib/adalib; export ADALIB 
                                                       (for sh)

To compile:
   ada <filename>
   ald <procedure name>     (redirect to other than a.out with -o switch)
   a.out
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For the GNAT environment (Ada95)

you may have to create a path to /usr/local/adainclude
   (in case the compiler cannot find the system files)   

 either place in your login file, or place in any file the command

setenv PATH .:$HOME/bin:/usr/local/bin:/bin:/sbin:/usr/sbin:/usr/include/cxx:
/usr/local/adainclude

and execute it (in the c and tcsh shells) with 

   source <filename>

You must compile each Ada95 unit separately, whether a package or procedure
specification, or a body
 use the extension   .ads   for specifications
                     .adb   for body
Use the same name for the file as for the package or procedure
             (don't worry about case sensitivity for this name)

Compile with
   gnatmake <filename>

An executable file will be created with the calling procedure's name -

Run it by typing the filename (no extension)