MantisBT - CMake
View Issue Details
0004550CMakeCMakepublic2007-03-07 11:182016-06-10 14:30
Matthew Woehlke 
Brad King 
normalmajoralways
closedmoved 
 
 
0004550: Solaris 2.7 (SPARC) build failure, WSC6
I get this using CC: "CC: Sun WorkShop 6 update 2 C++ 5.3 2001/05/15" (the Solaris version isn't really relevant since this is the same compiler we use on all Solaris SPARC machines).

CC -I/path/to/cmake-2.4.6/Source -I/path/to/cmake-2.4.6/Bootstrap.cmk -c /path/to/cmake-2.4.6/Source/cmake.cxx -o cmake.o
CC -I/path/to/cmake-2.4.6/Source -I/path/to/cmake-2.4.6/Bootstrap.cmk -c /path/to/cmake-2.4.6/Source/cmakemain.cxx -o cmakemain.o
CC -I/path/to/cmake-2.4.6/Source -I/path/to/cmake-2.4.6/Bootstrap.cmk -c /path/to/cmake-2.4.6/Source/cmakewizard.cxx -o cmakewizard.o
CC -I/path/to/cmake-2.4.6/Source -I/path/to/cmake-2.4.6/Bootstrap.cmk -c /path/to/cmake-2.4.6/Source/cmCommandArgumentLexer.cxx -o cmCommandArgumentLexer.o
"cmCommandArgumentLexer.cxx", line 13: Warning (Anachronism): End of file while skipping text -- Check #if .. #endif pairing.
"cmCommandArgumentLexer.cxx", line 34: Warning (Anachronism): End of file while skipping text -- Check #if .. #endif pairing.
"cmCommandArgumentLexer.cxx", line 29: Warning (Anachronism): End of file while skipping text -- Check #if .. #endif pairing.
"cmCommandArgumentLexer.cxx", line 121: Warning (Anachronism): End of file while skipping text -- Check #if .. #endif pairing.
"cmCommandArgumentLexer.cxx", line 161: Warning (Anachronism): End of file while skipping text -- Check #if .. #endif pairing.
...

It seems to be a problem with the '#line' directive. I can't preprocess (i.e. 'CC -E') this:

====
#include "cmStandardIncludes.h"

#line 2 "cmCommandArgumentLexer.cxx"

#line 4 "cmCommandArgumentLexer.cxx"

#define YY_INT_ALIGNED short int

/* A lexical scanner generated by flex */

#define FLEX_SCANNER
#define YY_FLEX_MAJOR_VERSION 2
#define YY_FLEX_MINOR_VERSION 5
#define YY_FLEX_SUBMINOR_VERSION 33
#if YY_FLEX_SUBMINOR_VERSION > 0
#define FLEX_BETA
#endif
====

...but it goes through OK if I comment out the '#line' lines.
No tags attached.
Issue History
2008-01-10 15:46Bill HoffmanAssigned ToBill Hoffman => Brad King
2008-01-10 16:58Brad KingNote Added: 0010128
2012-08-13 10:44Brad KingStatusassigned => backlog
2012-08-13 10:44Brad KingNote Added: 0030562
2016-06-10 14:27Kitware RobotNote Added: 0041346
2016-06-10 14:27Kitware RobotStatusbacklog => resolved
2016-06-10 14:27Kitware RobotResolutionopen => moved
2016-06-10 14:30Kitware RobotStatusresolved => closed

Notes
(0010128)
Brad King   
2008-01-10 16:58   
Current CMake HEAD in CVS has explicit #line directives in the following files:

Source/cmDependsJavaLexer.cxx
Source/cmCommandArgumentParser.cxx
Source/cmDependsJavaParser.cxx
Source/cmDependsFortranLexer.cxx
Source/cmCommandArgumentLexer.cxx
Source/cmExprLexer.cxx
Source/cmDependsFortranParser.cxx
Source/cmDependsFortranParserTokens.h
Source/cmListFileLexer.c

There are a total of 632 directives. Does this still happen? Which directives need to be commented out to build? All of them? Just those in the header file?

FYI, this is a bug in your compiler. We may be able to work around it, but the only way to make sure it keeps building is to submit a nightly dashboard entry. Let me know if you want to set one up and I can help. It would require about 1 hour of compute time per night.
(0030562)
Brad King   
2012-08-13 10:44   
Sending issues I'm not actively working on to the backlog to await someone with time for them.

If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it:

 http://www.cmake.org/mailman/listinfo/cmake [^]

It's easy to re-activate a bug here if you can find a CMake developer or contributor who has the bandwidth to take it on.
(0041346)
Kitware Robot   
2016-06-10 14:27   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.