![]() |
| UNIX is a registered trademark of The Open Group in the United States and other countries |
To install FreeUSP from a source distribution, the following environment variables must be set (case sensitivity required):
Note that FreeUSP = top level directory where FreeUSP is installed; DEPTROOT = $FreeUSP/trcgp.
Thus, in a C shell(csh):
setenv FreeUSP /home/jqpub/FreeUSP
setenv DEPTROOT $FreeUSP/trcgp
Note that the proper quotes are important and completely necessary.
setenv TARCH `${DEPTROOT}/bin/tarch`
setenv MANPATH ${DEPTROOT}/man:${DEPTROOT}/usp/man
Or, conversely, in a Bourne shell (sh):
FreeUSP=/home/jqpub/FreeUSP; export FreeUSP
DEPTROOT=$FreeUSP/trcgp;export DEPTROOT
TARCH=`${DEPTROOT}/bin/tarch`; export TARCH
MANPATH=${DEPTROOT}/man:${DEPTROOT}/usp/man
The following must also be added to your PATH:
csh
set path = ( $FreeUSP/dist/bin $DEPTROOT/bin $DEPTROOT/usp/bin ${DEPTROOT}/bin/${TARCH} ${DEPTROOT}/usp/bin/${TARCH} $path )
sh
PATH=$FreeUSP/dist/bin:$DEPTROOT/bin:$DEPTROOT/usp/bin:${DEPTROOT}/bin/${TARCH}:${DEPTROOT}/usp/bin/${TARCH}:$PATH; export PATH
In addition, please be sure that you have included the proper paths for:
ar, gnu make, the LessTif libraries and header files (for Linux), and your compiler.
Also be sure that you have a adequate number of file descriptors available.
This is usually accomplished by typing the command limit (in a csh). Should you see
descriptors 200
then type:
limit descriptors unlimited
(or 1024 or whatever suits you). We believe that 256 should be sufficient.
To see the sh limit type:
ulimit -a
To set the sh limit type:
ulimit -n 256
Try a man ulimit on your system for more information.
FreeUSP makes assumptions as to where LessTif is installed, to wit: for header files (.h) - /usr/X11R6/include or /usr/local/LessTif/MotifN.N/include for library files (.a, .so) - /usr/X11R6/lib or /usr/local/LessTif/MotifN.N/lib
Should LessTif be installed differently on your system, either symbolically link the proper directories, or change the $DEPTROOT/etc/gmake/Motif* files to reflect your installation.
For installations where more than one architecture is used or separate installations are desired, a methodology exists in FreeUSP whereby synchronization among systems may be maintained, both at the source level and at the binary level. For initial installation, each installation should be handled independently to provide the initial framework. After that has occurred, however, one system can be defined the "master" and other systems supported by virtue of the "remotes" targets throughout the source structure. Refer to the man page on shadow for more information on the implementation.
One caveat of note, while the FreeUSP code is not kernel dependent, the underlying support structure is. Thus, if you are runnning an OS rev not listed in README.support, FreeUSP will probably run with some minor tweaking to the OS_REVS stanza in $FreeUSP/dist/bin/usp-generic-set-path for your architecture. See the FAQ on supported architechtures for more information.
Compiling the codes:
Note that to simply run the ToolKit, all you have to do is add $FreeUSP/dist/bin to your path.
For corrections or communication with the world of FreeUSP users and hackers, please email freeusplist@freeusp.org