Release Date: Sept 2003
Before installing this patch you must already have nmake release lu3.6 installed. If you already have a valid license for lu3.6 you do not need a new license to use this patch. For any license requests please contact the Bell Labs Licensing Team.
This patch is to be applied to an existing nmake lu3.6 installation. All current lu3.6 nmake users are entitled to download and install this patch -- a new license is not needed to use the patch. If you do not have version lu3.6 installed then you should not install this patch.
This patch will replace several files in your lu3.6 node (details are below). Any file to be replaced will first be backed up so it may be recovered if necessary. The install script also provides a rollback feature to uninstall the patch and return the lu3.6 node to its previous state.
All actions performed by the install script are logged into a file called install.log. If the install script is executed more than once each instance will be saved in the log file.
This patch contains the following components (found under the update/ subdirectory):
Plus the following patch support files:
The following fixes are provided in this patch:
::) and a compiler that supports
-xar(such as the Sun C++ compiler), nmake would try to generate each shared library using object files from all the shared library targets in the makefile. This has been fixed.
javadeps=1caused the value to be compiled into the
.mofile. When running nmake again without setting javadeps nmake would not fall back to the default but would unexpectedly use
javadeps=1and rerun jdeps. This is fixed and the value is no longer compiled into the
-dflag to jdeps is included only when
JAVACLASSDESTis not "
:JAVA:man page has been updated to document the
GLOBALJAVADEPSvariable, which missing in the lu3.6 release.
globaljavadepsfile existed down the viewpath nmake would not pass the proper flag to javadeps to read it. This has been fixed.
Note: The following changes are in the separate JavaDeps lu2.1.1 package. JavaDeps must be downloaded and installed independent of the core nmake package. The changes are listed here for convenience. For more details and to download JavaDeps see the JavaDeps page.
globaljavadepsfile down the viewpath javadeps would try to update that file. Now javadeps will read the file down the viewpath and write updates to the local directory.
We recommend installing this patch while no one is running the nmake command. Use the following steps to install the patch.
$ cd <nmake_root>
patch01" will be created which contains the patch files.
$ zcat <downloaded_file> | tar xvf -
$ cd patch01
$ ./install.shIf you are happy with the summary then press '
y' and '
enter' (or '
return') to start the update. Any other key will abort the update before any changes are made.
* Do you want to start the install? (y/n) yAs the install script executes it will show you what files are being backed up and installed. A file named
install.logwill be created or appended to containing the actions taken by the installation script.
To back-out the patch and restore the original files run the
install.sh script again. If the patch has already been
installed the script will ask if you would like to restore the original
files or reinstall the patch. The restore option is only available
after the patch has been successfully installed.
READMEand the directory
$ cd <nmake_lu3.6_root>/patch01
install.shscript. If that patch has already been installed you will be asked if you want to restore or reinstall the software. To back-out the patch chose the restore option, number 1.
$ ./install.sh * You have the following options: 1) Restore - backout the patch and restore original files. 2) Install - attempt to install the patch again. Select 1 or 2 --> 1You will then be given a summary of the files to be restored. If you are happy with the summary then press '
y' and '
enter' (or '
return') to start the restore. Any other key will abort the restore before any changes are made.
* Do you want to start the restore? (y/n) yAs the script executes you will be shown what files are being restored. The
install.logfile will be appended with the actions taken by the restore.