KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q39037: Error U1005 Syntax Error: Colon Missing

Article: Q39037
Product(s): See article
Version(s): 5.00 5.10 | 5.10
Operating System(s): MS-DOS | OS/2
Keyword(s): ENDUSER | s_pascal h_fortran h_masm s_quickc s_make s_error | mspl13_c
Last Modified: 15-JAN-1990

The following error is from "MAKE Error Messages" in the manual
"CodeView and Utilities", Section C.4, Page 376, and in the "Microsoft
QuickC Compiler Programmer's Guide," Section D.6, Page 382:

U1005       syntax error : colon missing

            A line that should be an outfile/infile line lacked a
            colon indicating the separation between outfile and
            infile. MAKE expects any line following a blank line to be
            an outfile/infile line.

Note: MAKE expects a blank character or tab(s) after the colon between
outfile and infile. If such a space is missing, this error occurs.

Error messages displayed by the Microsoft Program Maintenance Utility,
MAKE, have one of the following formats:

   {filename | MAKE} : fatal error U1xxx: messagetext
   {filename | MAKE} : warning U4xxx: messagetext

The message begins with the input-file name (filename), if one exists,
or with the name of the utility. If possible, MAKE prints a warning
and continues operation. In some cases, errors are fatal and MAKE
terminates processing.

This problem can also be caused by using a NMAKE compatible make file
with MAKE.

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.

Copyright Microsoft Corporation 1986-2002.