Alcatel-Lucent nmake Product Builder

Release Notes -- Alcatel-Lucent nmake lu3.7

October 2004
[Table of Contents] [Previous Section] [Next Section]

5. Known Problems and Remarks

5.1 Known Problems

The following is a list of known problems:

1. 980009 - problem in link=*
   The problem about using link=* to install targets in any adjacent nodes in viewpathing still exists. You may still use link=* to install, but only in alternate nodes.
2. 030042 - :cc: generated header rebuild
   If a C file is built by using :cc: and this C file shares a generated header file with a C++ file specified in the same makefile, the generated header file may get regenerated during the build causing the source files to keep recompiling. This can be avoided by building the C++ files before the C files, or by generating the header file in a separate makefile at an earlier time during the build.
3. 990099 - metarules not searched when CC.REPOSITORY is set
   The metarules may not be searched under the following conditions: there is a user defined metarule for a non-compiled file, variable CC.REPOSITORY is defined, and :: is used to trigger the metarule. Note that CC.REPOSITORY is defined automatically for some C++ compilers in the probe file. The work-around is to add .IMPLICIT to the :: assertion, or to not use the :: assertion (such as add the target to :ALL: instead.)
4. 020018 - adding shared lib building in same makefile won't relink
   An executable target will not be relinked when a shared library that is built in the same makefile is added as a prerequisite to the executable. The work-around is to set force_shared=1.
5. 020051 - first metarule is used by mistake
   When multiple metarules generate the same source file target, such as %.c, the first metarule defined will be triggered instead of the metarule matching the file prerequisite suffix.
6. 040018 - error updating jar target after target is removed
   If a jar target is deleted or touched and the state file still exists, running nmake again does not regenerate the target but leads to a jar error. Use clobber to delete the target and state file to keep the files in sync.
7. 040065 - jar index option does not work with full path
   When a jar target file includes a manifest file that defines Class-Path, any jar files defined in the manifest Class-Path should exist or may lead to an error when generating the index of the target jar. The work-around is to reference the target jar with a relative path instead of full path.
8. 040070 - clean does not remove object files on AIX
   The clean common action my not delete the .o object files on AIX platforms.

5.2 Remarks

1. AIX - The AIX package does not have the global version strings in the binary executables.
2. :LINK: does not handle archive files that are generated by :: or :LIBRARY: assertion operators. Users should avoid use of :LINK: on archive files.
3. When the cpp -I-S flag is on, -D-M is disabled. Users should not use these two flags together.
4. Users should avoid including the same header file with both <...>-style and "..."-style #include statements in source files managed by a single makefile. nmake will assign .STD.INCLUDE and .LCL.INCLUDE attributes to the header file, and this can result in incorrect -I lists in the compiler command lines generated.

[Table of Contents] [Previous Section] [Next Section]