next up previous contents
Next: Building in Remote Directories Up: The Makefile System and Previous: Variables in Makefiles   Contents

The Install System

SUIF comes with a simple installation script that will attempt to identify various components of your system and set some variables in Makefile.std appropriately. If you are installing on a system for which we have not catered, there is a good chance you will have to modify these scripts. Please ensure that when you do modify the scripts the existing funcionality is retained, and please send us your changes for inclusin in the release. This is especially important if you are installing the system on a new machine or with a new compiler.

Installation of the system requires the following steps:

The following files are part of the install system. These are all in the ``nci'' directory:

File Description
install The installation script
Makefile.proto The prototype for Makefile.std
packing.lst List of files present in release
Makefile.std Generated by the install script from the prototype Makefile and from variables deduced by the install script (see below)
nci_setup.csh Script to ``source''; to set environment variables for use with nci system
nci_setup.sh Script to ``.'' for users of Bourne Shell and derivatives.

When you run the install script, a number of variable values are deduced and these are placed into Makefile.std together with the contents of Makefile.proto. The deduced variables are as follows:

Variable Description
ARCH First thing from ``uname -a'' output
NCIHOME Always the directory the install script is run from.
MAKE gmake if possible, else make. Note that the Makefiles use a number of gmake features and are not compatible with many other make programs.
AWK Looks for gawk, then nawk, then awk. On SunOS, awk does not work; you need at least nawk. This should be available.
CXX C++ compiler name. Looks for eg++, g++, CC and cc, in that order.
CC C compiler name. Looks for egcc, gcc and then cc, in that order.
COMPILER_NAME This is important because it is used to access option file names. It is the variable you will most likely want to change. The install script guesses a value for this based on the COMPILER_NAME and the ARCH values.
PERL Currently always perl.


next up previous contents
Next: Building in Remote Directories Up: The Makefile System and Previous: Variables in Makefiles   Contents
David Heine
1999-11-22