Nokia nmake Product Builder
Release Notes -- Nokia nmake 12
[Table of Contents]
5. Known Problems and Remarks
5.1 Known Problems
The following is a list of known problems:
- 980009 - problem in link=*
The problem about using linking (specified using the
variable) to install targets in any adjacent nodes in viewpathing
still exists. You may still use linking to install, but only in
alternate nodes -- installation using copying must alternate with
installation using linking. The problem occurs with both symbolic
and hard linking.
- 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.
- 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,
CC.REPOSITORY is defined and
CC.DIALECT contains either
is used to trigger the metarule. Note that
CC.DIALECT are defined as such in the probe file
for some C++ compilers.
The work-around is to add
.IMPLICIT to the
assertion, or to not use the
:: assertion (such as add
the target to
- 020018 - adding shared lib building in same makefile won't re-link
An executable target will not be re-linked 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
- 020051 - first metarule is used by mistake
When multiple metarules generate the same source file target,
%.c, the first metarule defined matching an existing
file will be triggered instead of the metarule matching the explicit file
- 070010 - fails to bind large files
nmake does not have
large file support
and cannot reference files over 2 GiB in size.
- :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.
Users should not use these two flags together.
- 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.
- When the
SHELL environment variable points to
ksh93 you may get the following warnings when building your shell
warning: line 1: `...` obsolete, use $(...).
The warning is generated running your script with
To eliminate the warning either update your shell scripts as
indicated by the message or set
SHELL to another version
of ksh that does not generate the warning, such as ksh88.
- The Solaris 10 ksh initializes PWD to the full, physical
path with no symbolic links. When running nmake somewhere under a
symbolic link make sure the nmake ksh is in the PATH first to avoid
viewpathing problems caused by the Solaris ksh PWD.
[Table of Contents]
Last Update: Friday,12-Aug-2016 12:25:28 EDT