CODEWITHSUNDEEP
makefilebuild-processclearcase
Coding Ninja
Coding Ninja

Reputation: 112

Column 0 error while trying to build the code in clearcase dynamic view

I have been trying to build the code present in a dynamic view. I use clearmake.exe all command while trying to build the code. The issue here is that when I am building my code in Windows 2003 server, the build is successful, where as, when I am building the same code in Windows 2008 R2 server, the compilation fails with the following syntax error :

Clearmake.exe: Error: Syntax error in file “makefile”, line 2, column 0.

I could have very well debugged my makefile if there is a column 0. I strongly believe this is not related to the makefile script. Can someone help me here? I am completely stumped and helpless.

Note :

1) The Cygwin version I am using in Windows 2003 environment is 1.90.4.1 and the one I am using in Windows 2008 R2 environment is 2.6.0.

2)The clearcase version I am using in Windows 2003 environment is 8.0.0.15 and the one we are using in Windows 2008 R2 environment is 8.0.0.7.

Upvotes: 1

Views: 175

Answers (2)

Brian Cowan
Brian Cowan

Reputation: 1073

Well, I have more questions than answers:

  1. Why is the newer environment using the older CC release?
  2. Is the makefile generated by something from Cygwin? Otherwise the Cygwin version isn't really an issue.

It really can't be related to anything BUT the makefile. If the makefile is generated by something cygwin-based before clearmake sees it, it coud be there. If it is literally the same version of the same makefile (in other words, if the makefile is under source control and NOT generated by the build environment and the views select the same version) then it would most likely be an issue with the makefile parser.

Upvotes: 0

VonC
VonC

Reputation: 1324537

Check for any special characters or eol (end-of-line) discrepancies between the two makefiles.
For instance, a "syntax error column 0" appear here:

The last one has an obvious solution:

Workaround:
Customer is working around this issue by adding a newline character to the end of his makefile.

Upvotes: 1

Related Questions