STAMS SOLVER TOOLSET MANUAL

INSTALLATION

Authors: W.S.C. Gurney, I. Thurlbeck

PRE-INSTALLATION CHECKS

The X11 version of the STAMS SOLVER Toolset requires:

the presence of a compiler, either the SUN Pascal on SunOS/Solaris, DEC Pascal on Digital UNIX/OSF1, or GNU Pascal on Linux/x86 (Intel).
that your path set-up will allow access to the pascal compiler driver by simply typing pc (or gpc for Linux).
that it has access to the X11 library Xlib. Specifically, use of the compiler driver switch -lX11 must result in correct linking of the Xlib routines.

Using GNU Pascal

If you are running Linux you will need to download and compile the source code for both the GCC and GNU Pascal compilers as listed on the Solver Download Page. If you can't face this, you can try one of our binary distributions of GCC and GNU Pascal (which includes a C,C++,Fortran compiler as well), also listed on the download page. Note this is for Linux/x86 (Intel) only.

To use the binary distribution, you must unpack it in the directory /usr/local as follows (change the path to the GCC+GPC binary distribution file as required):

cd /usr/local
tar zxvf /path/to/gcc-2.95.2-gpc-19991030-rh61.tar.gz

Finally add the following to your shell start up file to access the GNU Pascal compiler:

Bourne Shell (sh/bash):
```
PATH=/usr/local/gcc/bin:$PATH
```
C Shell (csh):
```
set path = ( /usr/local/gcc/bin $path)
```

Double check by typing gpc -v to see if the Pascal compiler starts. The information printed should be:

Reading specs from /usr/local/gcc/lib/gcc-lib/i586-pc-linux-gnu/2.95.2/specs
gpc version 19991030, based on 2.95.2 19991024 (release)

NOTE that you will also have gcc, g++, and g77 compilers as well.

NOTE that you can install this binary GCC+GPC distribution without fear of breaking your current compiler installation (assuming it's not already in /usr/local/gcc).

SOLVER INSTALLATION

The X11 version of the STAMS SOLVER Toolset is designed as a network system. That is to say, it is designed so that a single copy of the toolset system files will be available to all users. The only things kept locally by users will normally be problem definition files. This greatly simplifies maintenance and optimises the use of disk space. The installation procedure is now:

Decide where you want to keep the solver source code. Create a suitable directory and change directory into it. E.g.:
```
	mkdir /usr/local/solver-5.2-src
	cd /usr/local/solver-5.2-src
	
```
Copy the solver distribution file into source directory. Unzip it by typing gunzip solver-5.2.tar.gz. This produces a file solver-5.2.tar which you unpack by typing tar xvf solver-5.2.tar.
Edit the Makefile which you will now find in the source directory and:
- Set the variable SSD to the directory where you intend to install SOLVER.
  NOTE: Don't set this to be the same as the source directory.
  If you choose something like /usr/local/solver for the SSD then solver will be installed as follows:
```
	/usr/local/solver/bin           binaries and scripts
	/usr/local/solver/modules       library and header files
	/usr/local/solver/toolsrc       source code
    	
```
- Set the variable PC to the name of the Pascal compiler you wish to use. Normally use pc on Sun or Dec and gpc on Linux/x86.
Compile the whole SOLVER system by typing make.
Install the binaries, scripts and other source modules by typing make install.
Add the path to the solver scripts and binaries to your shell startup file (this example assumes /usr/local/solver for the SSD):
- Bourne Shell (sh/bash):
```
PATH=/usr/local/solver/bin:$PATH
```
- C Shell (csh):
```
set path = ( /usr/local/solver/bin $path)
```

Hopefully, that's it.

QUICK TEST

Assuming you used the suggested install directories, try the following:

cd /tmp
cp /usr/local/solver-5.2-src/examples/solver/exp.* .
solv exp

This should compile the example and launch the application. If it fails during compilation there should be enough information printed to diagnose the problem. If the compiled application does not launch (can't find exp.solver) make sure you put the current directory in your PATH, PATH=$PATH:. or set path = ($path .)

PROBLEMS

Its possible for both link-time and run-time problems to occur on Sun Solaris 2.x machines due to problems with the LD_LIBRARY_PATH environment variable. This is sometimes caused by different versions of the X11 library being on the system.
If you have a link problem with utilsrc/plotter, try un-setting your LD_LIBRARY_PATH variable: unsetenv LD_LIBRARY_PATH
You may have to set an alternate SYS_X11_LIBDIR directory in the Makefile if you have OpenWindows installed in a strange place.
Run time problems on Solaris machines are again normally due to LD_LIBRARY_PATH.
If you cleared this to do the compilation, reset it to the default, but make sure it includes /usr/openwin/lib, eg: setenv LD_LIBRARY_PATH /usr/openwin/lib:/usr/lib