Package Installation Instructions

The download packages are distributed in a compressed or gzipped tar format (older releases are in cpio format). The SFU/Interix package is a BSD-style pkg_add package (see below). After downloading the package to the target machine, follow these instructions to install the software.

1. If necessary rename the downloaded file (see warning.)
2. On SFU/Interix Platforms
   1. The SFU/Interix package is distributed as a BSD-style pkg_add package. See the packaging instructions from Interop Systems for information on obtaining and installing the packaging commands. For more information on the SFU/Interix platform see Support for Windows.
   2. The package must be installed by the Administrator or an account in the Administrators group. Run the following command and answer the prompts. The package will be installed in /opt/nmake.<release>, which will be referred to as <nmake_root>. Installation will consume about 4 MB.

      $ pkg_add nmake-alu3.9-sfu.3.5-bin.tgz
      
      +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
                 Welcome to the Lucent(R) nmake Product Builder
        
        This script will install Lucent(R) nmake at /opt/nmake.alu3.9.
        The files and directories will be owned by richb.
      
        Do you want to proceed [y/n]? y
        Unpacking files...
        Creating directories...
        Setting permissions...
        Installation complete!
      
        See /opt/nmake.alu3.9/README.nmake for information.
      
        For support, updates and documentation:
          http://www.bell-labs.com/project/nmake/
          nmake@alcatel-lucent.com 

   
   For all other platforms
   1. Go to the directory where you wish to install the software. You may want to make a new directory. The nmake bin, lib, man, fun, and share directories will be created here. This directory will be referred to as <nmake_root>. Installation will consume between 4 and 7 MB, depending on the platform.
   2. Run the following command to uncompress and unpack the downloaded file:
      • For tar.Z files:

        zcat downloaded_file | tar xvf -

      • For Linux® tar.gz files:

        tar xzvf downloaded_file

      • For UWIN tar.gz files:

        gunzip -c downloaded_file | tar xvf -

      • For cpio.Z files:

        zcat downloaded_file | cpio -icdumv

   3. Make sure lib/probe/probe and lib/ssd have the proper setuid bits set. The permissions are set correctly in the tar packages, but we have observed that some systems do not preserve the setuid bits when unpacking. The permissions should look as follows:

      -rwsr-xr-x   lib/probe/probe
      -rwsr-sr-x   lib/ssd

      If they are not set correctly then run the following commands:

      chmod 4755 lib/probe/probe
      chmod 6755 lib/ssd

3. Copy or move your license file to file: <nmake_root>/lib/license/make
4. Make sure cc is in your $PATH, or the variable CC must be defined in your Makefiles or shell environment to a valid C or C++ compiler.
5. Add the nmake bin directory to $PATH. (Note, executing nmake using the path to the executable while a different nmake executable exists in the $PATH may cause errors):

       export PATH=<nmake_root>/bin:$PATH

6. If you would like to access the man pages then add the nmake man directory to $MANPATH.

       export MANPATH=$MANPATH:<nmake_root>/man

7. Some Solaris, Linux and SFU platforms require the nmake bin directory in the PATH prior to the system ksh to pick up the included ksh88i. If you are installing nmake on Solaris see the Solaris KSH FAQ for details. SFU and some Linux distributions install pdksh, which is not compatible, at /bin/ksh and/or /usr/bin/ksh. Some Linux distributions also have a true AT&T ksh available which can be used with nmake; check your distribution. Also see the probe FAQ for the probe shell requirements.