Error build

[GoogleCodeExporter]

What steps will reproduce the problem?
1. sudo ./build.py --install
2.
3.

What is the expected output? What do you see instead?
g++ -o .release_build/ocelot/ocelot/parser/implementation/PTXLexer.os -c -O2 
-Wall -Werror -std=c++0x -D_DEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS 
-D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fPIC -Iocelot -I/usr/include 
-I/usr/include -I/usr/local/include -I.release_build/ocelot -Iocelot 
ocelot/ocelot/parser/implementation/PTXLexer.cpp
ocelot/ocelot/parser/implementation/PTXLexer.cpp: In static member function 
'static std::string parser::PTXLexer::toString(int)':
ocelot/ocelot/parser/implementation/PTXLexer.cpp:51:4: error: 'OPCODE_BFE' was 
not declared in this scope
ocelot/ocelot/parser/implementation/PTXLexer.cpp:143:4: error: 'TOKEN_SM30' was 
not declared in this scope
ocelot/ocelot/parser/implementation/PTXLexer.cpp:144:4: error: 'TOKEN_SM35' was 
not declared in this scope
ocelot/ocelot/parser/implementation/PTXLexer.cpp:202:4: error: 'TOKEN_METADATA' 
was not declared in this scope
ocelot/ocelot/parser/implementation/PTXLexer.cpp:280:4: error: 
'TOKEN_TEXMODE_UNIFIED' was not declared in this scope
ocelot/ocelot/parser/implementation/PTXLexer.cpp:281:4: error: 
'TOKEN_TEXMODE_INDEPENDENT' was not declared in this scope
ocelot/ocelot/parser/implementation/PTXLexer.cpp:282:4: error: 'TOKEN_PTR' was 
not declared in this scope
scons: *** [.release_build/ocelot/ocelot/parser/implementation/PTXLexer.os] 
Error 1

What version of the product are you using? On what operating system?
ocelot rev 2146

Please provide any additional information below.
All dependencies are installed

Original issue reported on code.google.com by [email protected] on 15 Dec 2012 at 2:40

[GoogleCodeExporter]

I found that having a stale installed ptxgrammar.hpp file (in my case, located 
in /usr/incude) prevented the regeneration of this same file from 
parser/implementation/ptxgrammar.yy, causing the the errors in PTXLexer.cpp as 
you noted.

Renaming the installed ptxgrammar.hpp allowed the build to continue past this 
point.

I am not up to speed with SCons, so I was not able to work out why the build 
system would not regenerate ptxgrammar.hpp as a matter of course.

Regards

Original comment by [email protected] on 23 Jan 2013 at 3:11

[GoogleCodeExporter]

this seems to be related to a workaround here: 
https://groups.google.com/forum/#!msg/gpuocelot/CmbCDkiD098/NH0eOMonFqQJ

Original comment by [email protected] on 2 Apr 2013 at 1:36