FIX: Macros w/ Different Case Can't Be Assigned to Each Other

Last reviewed: September 16, 1997
Article ID: Q86813
1.11 1.12 1.13 1.20 | 1.11 1.12 1.13
MS-DOS              | OS/2
kbtool kbbuglist kbfixlist

The information in this article applies to:

  • Microsoft NMAKE for MS-DOS, versions 1.11, 1.12, 1.13, and 1.2
  • Microsoft NMAKE for OS/2, versions 1.11, 1.12, and 1.13

SYMPTOMS

NMAKE version 1.11, 1.12, 1.13, or 1.2 macros that are the same but have a different case cannot be assigned to one another. This kind of macro assignment results in nothing being assigned. For example, the sample makefile below displays

   upper and

when the output should be as follow:

   upper and lowercase

RESOLUTION

Even though NMAKE macros are case sensitive, this type of assignment is not successful. Two workarounds are:

- Use a temporary MACRO to perform the assignment. For example,

     target= file.exe;
     TEMP = $(target)
     TARGET = $(TEMP)

  -or-

- Give each macro a unique name.

STATUS

Microsoft has confirmed this to be a problem in NMAKE versions 1.11, 1.12, 1.13, and 1.2 for MS-DOS and versions 1.11, 1.12, and 1.13 for OS/2. This problem was corrected in NMAKE version 1.3.

Sample Makefile

target = lowercase TARGET = upper and $(target)

ALL:

   @echo $(TARGET)


Additional reference words: 1.11 1.12 1.13 1.20 buglist1.11 buglist1.12
buglist1.13 buglist1.20 fixlist1.30
KBCategory: kbtool kbbuglist kbfixlist
KBSubcategory: NmakeIss
Keywords : kb16bitonly
Solution Type : kbfix


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 16, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.