Welcome | spec | C-PLOT | Support | Users | Contact
 
Contents -> ADMINISTRATOR'S GUIDE -> Steps For Installing spec -> Installing the spec Program Files
spec Manual


5.3.2. - Installing the spec Program Files



To install the spec files, particularly for a first time installation, you may need to install as root. Use the su command to gain super-user privileges. If you are updating from previous distributions, you can copy the most recent install_data file containing your default installation parameters to the new distribution directory. Then, from the current spec distribution directory, type ./Install to run the installation program.

The Install program will first indicate the current installation parameters. You may either accept those or enter new parameters. When entering new parameters, the default response to each question is given in parenthesis. Most questions present a number of choices. You can either type the number of the choice or you can type out the literal selection. If one of the options is the word "other ," such as for the name of a directory, you can directly type your selection when prompted. For most questions, the first choice listed is probably the best response. For example, 
    Choices for binaries directory are:

      1) /usr/local/bin
      2) /usr/local
      3) /usr/local/spec/bin
      4) /u/bin
      5) /LocalLibrary/Spec/bin
      6) other

Choose binaries directory (/usr/local/bin)?


Entering a single minus sign (-) will move back to the question for the previous parameter, allowing you to enter a different value.

The installation questions ask for the following parameters:
platform
Selects from the supported combinations of computer and operating system.
geometry
Selects from the supported diffractometer configurations.
installed name
Selects a name for the installed program. For configurations with special geometry code, the first four letters of the name must match the first four letters of the geometry configuration. Thus, fourcL and fourcR might be the names for the left- and right-hand sides of a rotating anode lab with two four-circle diffractometers.
additional geometries
Asks if you want to enter more combinations of the previous two items.
file ownership
Selects the name of the owner of the spec files.
binaries directory
Selects where the programs that users run directly from the shell will go. (It's better to put spec files in some place other than the standard /bin or /usr/bin, in order to be able to distinguish files that are standard UNIX from those that have been added locally.) This directory should be in each spec user's search path.
auxiliary directory
Selects where spec puts its auxiliary files. Among the auxiliary files are user's state files, which can occupy significant disk space if there are many users running spec. Thus, this directory should not be on a file system that is in danger of running out of space.
ESRF library directory
Gives the location of the ESRF device server libraries if installing on an ESRF device server platform.
EPICS library directory
Gives the location of the EPICS channel access libraries if installing on an EPICS platform.
config file permissions
Selects who can change the hardware configuration file. On a low-security site, select the first choice, which lets all spec users make changes as needed. See security notes 5.5.8.3 for additional considerations.
data points type
Selects the precision for spec's internal data-points arrays. The choice affects both the virtual memory consumption of spec while it is running and the disk space consumed by user state files. Single precision data is suitable for most installations.
alternate history code
Selects an alternative library that can be linked with spec to provide a more powerful history recall syntax than the standard spec history mechanism. The alternative library also includes command line editing features. See the files in the readline subdirectory of the distribution for additional information.
CAMAC hardware support
Selects whether to include CAMAC hardware support in the installed programs.
KSC 3929 SCSI-CAMAC file location
Gives the location of Kinetic Systems supplied interface file for their model 3929 SCSI-to-CAMAC crate controller. If using the CSS-supplied software on the HP platform, enter no. If using the CSS-supplied driver on the SunOS 4.1 platform, enter no.
Nat Instr GPIB file location
Gives the path name of the cib.o file that may be needed to be linked with spec when using National Instruments GPIB boards. You may enter no for the PCII and AT-GPIB models of the board for PC computers, for the SB-GPIB board with versions 1.3 and 2.1 of the driver for Sun computers, for the 1014-1S board for Sun computers and for the boards for IBM PS/2 and RS/6000 AIX systems.
SICL GPIB library flags
Sets the flags required to load the libsicl.a file, necessary if you are using the SICL GPIB presently supported on HP 700 series platforms with either HP or IOtech devices. Note, CSS has an alternative to the IOtech version of libsicl.a for the SCIS488/H product. Contact CSS for more information.
VME hardware support
Selects whether to include direct support for VME hardware in the installed program. Note, this option does not refer to the VME hardwared used in ESRF and EPICS environments.
Nat Instr VME file location
Gives the location of the nivxi.o file that will be needed to be linked in with spec if you are using a National Instruments VME controller.
Extra compiler flags
Allows you to add extra compiler flags for both compiling the site-dependent source files and linking.
Extra object files
Allows you to specify extra site-dependent object files to include when linking the spec executable.
Extra library flags
Allows you to specify extra site-dependent libraries to be searched during the link phase when producing the spec executable.



After answering the questions, the installation should then continue automatically, producing output similar to the following: 
    Checking if u_hook.c needs compiling ...
Compiling u_hook.c ...
Checking if u_hdw.c needs compiling ...
Compiling u_hdw.c ...
Checking if readline library is up to date (may take some time) ...
Checking if geo_fourc.c needs compiling ...
Checking if spec needs to be linked ...
Linking spec ...
Making directory /usr/local/lib/spec.d
Making directory /usr/local/lib/spec.d/help
Making directory /usr/local/lib/spec.d/hgr
Making directory /usr/local/lib/spec.d/fourc
Making directory /usr/local/lib/spec.d/fourc/userfiles
Installing config auxiliary files ...

Installing fourc ...
 ln /usr/local/bin/spec /usr/local/bin/fourc
Installing prototype config file ...
 Fixing "fourc" config and settings file permissions ...
  No settings file.  Creating one.
Installing macros ...
 Installing /usr/local/lib/spec.d/standard.mac ...
 Installing /usr/local/lib/spec.d/four.mac ...

Installing help files ...
 Clearing out old help files ...
 Making the "help" help file ... 
 Making the "changes" help file ... 
 Copying help files ... 
 Changing ownership of help files to specadm ... 
  cp chk_file /usr/local/lib/spec.d
Installing the "chelp" program ...
Installing the "showscans" package ...
  cp show.awk /usr/local/lib/spec.d
  cp scans /usr/local/bin
Installing the "contents" program ...
  cp contents /usr/local/bin
Installing the "tidy_spec" program ...
  cp tidy_spec /usr/local/bin


If you change certain parameters that require relinking spec and don't see the Linking spec ... message when rerunning the Install program, simply remove the spec file and run Install again.


  Top
  Prev | Next