.ppTo watch the log file during while the install script runs do:.br.nf.ft CW% tail -f log.fi.ft LR.ppThis will run the install script and save all output in the file named\fIlog\fR.   You can monitor the progress of the install by using\fItail -f\fR.  (\fITail\fR shows the last few lines of a file.  The -foption causes it to print additional lines as they are added to thefile.  Note that \fItail\fR with the -f option does not ever exit.  Ithas no way of knowing that the file being watched will not have anyadditional text added to it.   If you are watching the install with\fItail\fR, you must kill it with control-C, or whatever your\s-1UNIX\s+1 interrupt character is, when you see the message indicatingthe end of the ESPS install script.)   When the install script completesit will print the message:.ft CWESPS general part of installation done..ft LR.ppIf something goes wrong and you need to stop the installation process,just use the \s-1UNIX\s+1 \fIkill\fR command to kill the process.  Youcan supply the process number(s) printed after the install command, orthe \fIcsh\fR job number supplied by the \fIjob\fR command..br.nf.ft CW% jobs [1]  +Running   install -l >& log% kill %1.fi.ft LR.sh 3 "Checking the Results".ppThe install script produces a large amount of output (the log file willbe about 100K bytes).   Many of the messages from \fImake\fR might looklike errors, but they are normal.   Each error message from \fImake\fR in theinstall log, should be followed by a message from \fImake\fR saying thatit is ignoring the error.   All of these are expected.   Any unexpectederrors will not be ignored and will cause the \fImake\fR to stop.Searching the log file for the word \fBStop\fR is an effective way tocheck for these errors.   A few C programs produce warnings aboutunreachable statements, depending on some installation variables.  Thesecan be ignored..ppTo quickly check the log file do:.br.nf.ft CW% grep Stop log.ft LR.fi.ppThere should be no Stops in the log file.   Also check for the worderror.  All errors should have ignored after them..br.nf.ft CW% grep rror log.ft LR.fi.ppThere will be several screens of error messages, but all should befollowed by the phrase .ft CW(ignored)..ft LR.ppThe \fItarget\fR directory (\fI$HOME/espsB\fR by default) should look likethis: (this example assumes the default name).ft CW.br.nf% cd $HOME/espsB% ls.TStab(;);l l l l.bin/;demo/;doc/;general@lib/;man/;include/.TE.ppThe bin directory should contain about 70 programs.   The doc directorywill contain about about about 5 documents (all of which you have inhardcopy form).  The lib directory will contain about 10 files,including the ESPS library, \fIlibespsg.a\fR, the ESPS lint library,some plot programs (that are called by other programs), and an examplemakefile, \fImakefile.ex\fR.  The symbolic link, \fIgeneral\fR, is alink back to the \fIgeneral\fR directory in the \fIsource\fR directory..ppThere is also a demo directory.  This directory contains severaldemo scripts.  There is a README file in that directory.  We stronglysuggest that you take the time to try these examples.  Not only do theyprovide an introduction to some ESPS commands, but they serve as a checkon the installation..ppWe also suggest that you use \fIeman -k\fR (followed by a keyword tosearch for) to familiarize yourself with the system.  See the \fIeman\fRmanual page for details.  Note that the first time you look at a manual page, it is formated into a printable form (from troff source).  Thisformated version is stored, so that if that manual page is requestedagain, it is available instantly..sh 2 "Setting Up the ESPS User Environment".ppAfter ESPS is installed, if it is to be used by more than one user, itis usually more convenient to allow users to access it through filesystem links that make it appear that ESPS is installed under adirectory such as \fI/usr/esps\fR.    For example, if you installed ESPS inyour directory \fIespsB\fR (the default), you could have a super-user do thefollowing:  (lets assume your home directory is \fI/u/smith\fR).br.ft CW.nf# cd /usr# ln -s /u/smith/espsB esps.fi.ft LR.ppAfter this is done, all users on the system can find ESPS files under\fI/usr/esps\fR.  This has the advantage, that a new version of ESPS can beinstalled and tested without disturbing other users on the system.  Whenthe ESPS maintainer is ready to switch his users over to the newversion, he simply redefines the \fI/usr/esps\fR symbolic link.   See the\fIln\fR man page for more information on symbolic links..sh 2 "Search Paths".ppIn order to execute ESPS programs users must place the ESPS binarydirectory on their default search path.   If ESPS is installed asdescribed above, that path would be \fI/usr/esps/bin\fR.    .sh 2 "ESPS Compilation Environment".ppThe ESPS install script creates several programs to aid users who writetheir own programs using the ESPS library.   \fIecc\fR invokes the Ccompiler with the correct options to cause the ESPS include files andlibrary to be searched.  It can be used in cases where you wouldnormally use the \fIcc\fR command.  Additional \fIcc\fR options can bespecified with \fIecc\fR.   The program \fIemake\fR calls make with thecorrect environment defined.  For more information on this, seereference [1] and the \fIemake\fR manual page.  A prototype makefilesuitable for use with \fIemake\fR is in the ESPS \fIlib\fR directory..sh 1 "More About the Install Script".ppThe install script, by default, changes to each ESPS source directoryand runs \fImake -e\fR.  The -e option to \fImake\fR causes it to use theenvironment variables as macro definitions.   If a list of sourcedirectories are given on the \fIinstall\fR command line, then only thesewill be made.   The names given, must be exactly the directory nameunder \fIesps/general/src\fR.  Note that this is not always exactly thesame as the installed name of the program.   To cause the manual pagesto be updated, you must specify \fI../man\fR. If \fIinstall\fR isrun without the -l option, then the library is not remade..sh 1 "A Word about the Speech I/O Programs".ppThe ESPS speech output program, \fIplay\fR, has the device names for theMasscomp EF12M clock and digital-to-analog converter compiledinto it.   If these are not correct for your system, you can either editthe source file (esps/general/src/mcplay/mcplay.c) or use \fIplay\fR command linearguments to supply alternate device names.   See the \fIplay\fR manual page fordetails.   The next version of the install script willallow the installer to specify the default clock and converter name atinstallation time..ppThe ESPS speech input program, \fIrecord\fR does not currently havecommand line arguments for specifying alternate clock and converternames.   This version of the program uses the Masscomp program\fIdacq\fR.  If this program works correctly on your system, then\fIrecord\fR should work.   .ppIf you have trouble with \fIplay\fR or \fIrecord\fR call Entropic forhelp..sh 1 "In Case of Difficultly".ppIf you have questions about the installation process, or havedifficultly running the script please call Entropic for help..lp.nfEntropic Speech, Inc.(202) 547-1420esps@wrl.epi.com (seimso!epiwrl!esps)