Nokia Networks Home

Nokia nmake Product Builder

Quick Links

Related Products

Package Installation Instructions

The download packages are distributed in a compressed or gzipped tar format (older releases are in cpio format). 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. 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 requires a maximum of 22MB disk space depending on the platform.
  3. 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
  4. 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
  5. Copy or move your license file to file: <nmake_root>/lib/license/make
  6. Make sure cc is in your $PATH, or the variable CC is defined in your Makefiles or shell environment to a valid C or C++ compiler. If you are not using a C/C++ compiler then you can set CC= in the Makefiles to clear the default compiler setting.
  7. 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
  8. If you would like to access the man pages then add the nmake man directory to $MANPATH.
        export MANPATH=$MANPATH:<nmake_root>/man
  9. Some Solaris and Linux 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 10 KSH Compatibility and Solaris KSH Hangs FAQs for details. 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.
  10. If you are upgrading nmake please send us a note to nmake@alcatel-lucent.com indicating the nmake version and host line from the license file (<nmake_root>/lib/license/make installed above). This helps us know what versions are being used since the license covers all recent releases. Thanks!
Last Update: Friday,12-Aug-2016 12:11:11 EDT