Nokia nmake Product Builder
Release Notes -- Nokia nmake 3.0
[Table of Contents]
The following is a list of known bugs:
- When giving a value to a functional variable on the command line, the
returning value may not be correct. To work around the problem, use the
reread option. For example:
nmake -o reread FUN=zz
where FUN is the functional variable.
- Using link=* to install targets in any adjacent
nodes under viewpathing may result incorrect installation. To
work around this problem, one can use
link=* to install in alternate views. For example, if
VPATH is set to:
you can use the default actions to install the targets in /n3
(the default action for installation is to copy the
targets into install area), and specify link=* in /n2
to install the targets, then again use the default action
to install in /n1.
- Panic on some file name aliasing cases, such as:
all : lib.a $(PWD)/b.o
lib.a :: a.c
To work around the problem, one can remove the $(PWD).
- The special atom .ACCEPT used as an immediate rule affects only
the first nmake invocation. The work around is to use it as
a dynamic attribute.
- The coshell executable does not run on the Pyramid machine running
OSx5.1, the IBM machine running AIX3.2, and the DEC machine running OSF1.2
- cpp cannot handle
the definition of #macdef block containing more than one
#if, #ifdef, #ifndef, or #elif.
This will cause core dumping.
#macdef ARGPRINT(arg1, arg2, arg3)
#if arg3 == 1
printf("arg is 3\n");
#if arg2 == 2
printf("arg is 2\n");
#if arg1 == 3
printf("arg is 1\n");
The user has to find a different way to write the macro to avoid the
- Cannot handle file name >= 15 characters when building
archive targets on those machines that ar(1) will truncate the
file names to 14 characters (e.g., HPs). Recompile those
file at every nmake invocation, since the truncated file names
do not match the actual names. The work around for the problem is to
change the file name to be <= 14 characters if it is possible.
- If INSTALLROOT is not set in the makefile or on the command line,
the output from -M command line option gives incorrect value for
INSTALLROOT. If INSTALLROOT is set and exported in the
environment, the output from -M command line option still gives
incorrect output for this variable. If the value of INSTALLROOT
is set, but the value does not start with "..", the output from
-M always gives $HOME as the value of this variable.
The work around is to use -k in conjunction with -M
and set value to INSTALLROOT either on the command line, or in
the makefile, or in the environment.
- On Star Server FT B20 machine, probe does not generate correct
value for CC.PIC when probing for /bin/cc. Manual
modification is needed. The correct value should be -D_PIC.
- The coshell environment variable HOMEHOST used in action
block of assertions does not get any value.
- The information in <nmake_install_root>/lib/cs/local
may not be generated correctly. For example, type may contain
machine name instead of machine type. Manual modification is needed.
- The :LINK: does not handle archive files, so user should
avoid to use :LINK: on archive files.
The followings are some remarks:
[Table of Contents]
Last Update: Friday,12-Aug-2016 12:29:08 EDT