Installing Gist

Unzip and de-tar the distribution file as follows:
	gunzip -c gist.2.0.1.tar.ARCH.gz | tar xvf -

At this point you have two options: either compile the programs from the provided source code, or use the program binaries that were provided in the tar file. Using the binaries is easier, but it may not be an option if you are using an architecture that is not supported. If you choose (or must) compile the source code, do so by following the steps in the "COMPILATION" section below.

Once you have the program binaries available, you will need to either copy these executables into your path or add the following lines to your .cshrc or .login file (where 'path-root' is the location where you installed Gist):

	setenv ARCH `uname -ms | tr -d ' '`
	set path = ($path path-root/gist.2.0.1/bin/$ARCH)

Assuming that the 'uname' command works on your system, Gist may then be used in a file system shared by multiple operating systems. To compile for a new operating system, be sure to run 'make clean' before trying to 'make all'.

COMPILATION

The Gist makefile assumes that the 'uname' command works on your system. Try it out. If it raises an error, you will need to edit the makefile by replacing this line
	ARCH    = `uname -ms | tr -d ' '`
with something arbitrary, such as
	ARCH    = foo

You can now do the following:

	cd gist.2.0.3/src
	make all

This will create the Gist executables in the directory 'gist.2.0.3/bin/ARCH', where 'ARCH' is taken from the makefile.

Note that Gist prefers the 'gcc' compiler. If 'gcc' gives you lots of warnings (it shouldn't, but it might), you can probably get rid of most of them by removing the safety flags ("-Wall -W -Werror") from the 'gcc' line.

Note that Gist uses calls to the Unix utilities 'hostname' and 'date', which can cause problems in situations where /bin/ or /usr/bin are not in your path. Users who are calling compute-weights from an environment where absolute paths are needed (as in many cgi-scripts) will have have to set the absolute path in the makefile by and adding -DUTIL_PATH="path/to/utils" to the CFLAGS variable. See the makefile for more information.

Gist