Unbacking, compiling and linking

These instructions assume that you already have a copy of the program, in the form of a (decompressed) backup saveset. Instructions for obtaining a copy can be obtained on request.

SPECX V6.3 runs only under the DEC VMS operating system. One logical name must be defined before the installation can start -- SYS_SPECX points to the top level SPECX directory, in which the various .EXE and initialization files will be put (note that in the following examples ``mydisk'' and ``mydir'' should be replaced with something suitable to your own circumstances!)

$ assign mydisk::[mydir.specx] sys_specx

Additionally, if MONGO is being used as the graphics package, MONGODIR points to the top level MONGO directory.

$ assign mydisk::[mydir.mongo] mongodir

You are now ready to unback the saveset and create the program.

1. Set the default directory to sys_specx and unback the files.

           $ set default sys_specx
           $ backup/log  [wherever the .bck is]specx63.bck/save/-
                         sele=[specx...]*.*/-
                         excl=[specx.local]*.* -
                         [...]*.*
   

   This will create all the SPECX source and library files. Note: if you do not already have a working copy of the program, and so do not have your own customizations, then you should also create a default specx_local directory: in this case use instead the backup command:

           $ backup/log  [wherever the .bck is]specx63.bck/save/-
                         sele=[specx...]*.* -
                         [...]*.*
   

2. If you do not already have a copy of the GSD routines (required if SPECX is to read GSD files) then these are also available on the backup save set. Decide where they are going to go, and then unback these also...

           $ backup/log  [wherever the .bck is]specx63.bck/save/-
                         sele=[gsd]*.* -
                         [wherever GSD goes]*.*
   

3. In principle you don't have to recompile the source, but just relink. You can try this if you want, although a MAKE file is included in the release which does everything from scratch. Before you do anything, you have to set up logical names for a few things.

   Edit the file [specx.local]specx_logicals.com If you are a non-MRAO, non-JCMT/JACH site, then the appropriate assignments are easy: Note that the assignment for DISK$SPECX requires the physical device name, and the directory name will need changing depending on where you have put things. As an example, the MRAO version of this file is reproduced below.

      $ !------------------------------------------------------
      $ !       specx_local:specx_logicals.com
      $ !         -- assign logical names for SPECX development
      $ !------------------------------------------------------
      $   assign/nolog  _mrao$dka300:[user.rachael.]           disk$specx
      $   assign/nolog  disk$specx:[specx.external]            specx_external
      $   assign/nolog  disk$specx:[specx.lib.genlib]          genlib
      $   assign/nolog  disk$specx:[gsd]                       mt_gsddir
      $ !
      $   exit
   

4. Declare logical names required for compilation and linking:

           $ set def sys_specx
           $ @specxdev
   

5. Now try relinking. If you are running PGPLOT, then you should have a logical name PGPLOT_DIR already defined, and this directory should contain either an options file (.OPT) or an object library (.OLB). Edit sys_specx:link.com to make sure you are linking in the correct mode.

   Try to link:

           $ @link
   

   You may need to compile the two fortran modules in [SPECX.LIB.STARLINK] before you can get a clean linkage.

   If you are not running PGPLOT, but some other package, then consult §1.2.5 for instructions on either linking with MONGO83 or MONGO87, or modifying the SXG_ routines to connect to another graphics package altogether.

6. If this fails, or if you want to be safe, then try instead to recompile and link the whole thing:

           $ @make_specx
   

7. Obviously you can conserve disk space by deleting stuff now. At the very least you can go through and delete all the .FOR and .TXT files in the subdirectories; if you are satisified that you don't want to relink then delete all the .OBJ and .OLB files also.