Alcatel-Lucent nmake: 3.1 Release Notes (Known Bugs and Remarks)

Release Notes -- Alcatel-Lucent nmake 3.1

The following is a list of known bugs:

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.
The state information of .SOURCE.mk does not work correctly in viewpathing. For instance, VPATH is set as VPATH=A:B and the Makefile contains statements like
```
    .SOURCE.mk : incl
    include "global.mk"
```
The B node is built by using the "global.mk" in the B node. Then, the A node is built by using the "global.mk" in the A node. If the "global.mk" in A is removed, nmake cannot detect that "global.mk" is changed when the A node is built again.

To work around the problem, users may use the -I flag on the command line to point the directory where the "global.mk" is located.
```
    nmake -Iincl
```
or to avoid using .SOURCE.mk in the makefile and use:
```
    include "./incl/global.mk"
```
instead.

:LINK: does not handle archive files that are generated by :: or :LIBRARY: assertion operators. Users should avoid use of :LINK: on archive files.
When the cpp -I-S flag is on, -D-M is disabled. User should not use these two flags together.
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, this generated header file always gets regenerated during the build. Since :cc: uses a separate statefile, the information in this statefile is not in sync with it in the normal statefile. Users should avoid this practice and should generate the header file in a separate makefile at an earlier time during the build.