Understanding the makefile:

Ok.  The purpose of the makefile is to make two libraries:
	libmaster.a: Routines for the master process
	libhence.a:  General routines for the master & slaves.
and the executable 'master'

The makefile uses a bunch of environment variables:

	ARCH: This is the result of bob's archtype command.  It's
              in ~plank/bin/archtype.
	jsp: Is my home directory.  You should change it to 
              ~plank or /turquoise/homes/plank
	bm: This is bob's home directory: ~manchek or /white/homes/manchek
	BIN: This is where I keep my binaries: $jsp/bin/$ARCH.
             The executable 'master' is made there.  You should change
             it to the location of your choice, as the makefile will 
             crash otherwise.

The include directory is $jsp/include.  

Master needs a bunch of libraries:
	librb.a: Red-black trees: in $jsp/lib/$ARCH
	libdl.a: Doubly-linked lists: in $jsp/lib/$ARCH
	liballoc.a: Bob's malloc with error-checking: in $jsp/lib/$ARCH
	libpvm.a: Pvm's library: in $bm/pvm_public/$ARCH
    none of these libraries need to be copied.

Libmaster.a and libhence.a are both made in $jsp/lib/$ARCH.  You should
change this (the makefile variables MAINLIB and MASLIB) to somewhere
in your own directory.

All of the .o files are made in ./$ARCH.  This is so that you
can keep around .o files for different machines.

Finally, the makefile is maintained by the routine makepvmdep, which is
in $jsp/bin.  It puts all the dependency junk below the '# +mkdep+' line.
If you type make, and it can't find a bizarre header, like 
'/usr/include/stdlib.', then try remaking the makefile by typing
'make depend'.

Look in the file maketmplt for a makefile which makes master in ., and
libmaster.a & libhence.a in ./$ARCH.

---------------------------------------------------------------
Example slave programs are in the directory examples.  The slave 
wrappers are made by calling

"$jsp/bin/SUN4/wrap sub.defs" on a sun4.

The makefile is like the makefile in this directory.

----------------------------------------------------------------
Documentation on hence programs is in ../param/exp.tex, etc.

To try a killer examples, try 'master test.gr'.  It basically beats
on all the special-purpose nodes, firing up almost 200 pvm processes.
After it's done, ./test shouldn't
return a thing.  It uses the cost matrix in cost.mat, and the pvm
hosts file in hosts.

