Unzip and de-tar the distribution file as follows:svm v1.0gunzip -c svm.1.0.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 svm):
setenv ARCH `uname -m` set path = ($path path-root/svm.1.0/bin/$ARCH)Assuming that the 'uname' command works on your system, svm 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'.
The directory 'tests' contains an 'rtests' script which checks that the svm programs are running correctly. You can change to that directory and run the script 'rtests' without any arguments.
COMPILATION
The svm makefile assumes that the 'uname -m' command works on your system. Try it out. If it raises an error, you will need to edit the makefile by replacing this lineARCH = `uname -m`with something arbitrary, such asARCH = fooAssuming you've checked those two items, you can now do the following:
cd svm.1.0/src make allThis will create the svm executables in the directory 'svm.1.0/bin/ARCH', where 'ARCH' is taken from the makefile.
Note that svm prefers the 'gcc' compiler. If this compiler is not available on your system, you can comment out the 'gcc' line and comment in the line following it (for 'cc'). Also, 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 -Wtraditional -Werror") from the 'gcc' line.