Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error C2065: 'history_key' : undeclared identifier #206

Closed
GoogleCodeExporter opened this issue Apr 22, 2015 · 6 comments
Closed

error C2065: 'history_key' : undeclared identifier #206

GoogleCodeExporter opened this issue Apr 22, 2015 · 6 comments

Comments

@GoogleCodeExporter
Copy link

@GoogleCodeExporter GoogleCodeExporter commented Apr 22, 2015

What steps will reproduce the problem?

1. > python build_mozc.py gyp --noqt
2. > python build_mozc.py build_tools -c Release
3. > python build_mozc.py build -c Release package


What is the expected output?

Error-free code generation. 


What do you see instead?

Generating code
Finished generating code
[421/448] CXX obj\prediction\prediction.dictionary_predictor.obj
FAILED: ninja -t msvc -e environment.x86 -- "c:\Program Files (x86)\Microsoft Vi
sual Studio 10.0\VC\bin\cl.exe" /nologo /showIncludes /FC @obj\prediction\predic
tion.dictionary_predictor.obj.rsp /c ..\..\prediction\dictionary_predictor.cc /F
oobj\prediction\prediction.dictionary_predictor.obj /Fdobj\prediction\prediction
.pdb
c:\work\mozc\src\prediction\dictionary_predictor.cc(1210) : error C2065: 'histor
y_key' : undeclared identifier
c:\work\mozc\src\prediction\dictionary_predictor.cc(1210) : error C2065: 'histor
y_value' : undeclared identifier
c:\work\mozc\src\prediction\dictionary_predictor.cc(1214) : error C2065: 'histor
y_key' : undeclared identifier
c:\work\mozc\src\prediction\dictionary_predictor.cc(1214) : error C2065: 'histor
y_value' : undeclared identifier
[421/448] LIB obj\win32\tip\tip_core.lib
ninja: build stopped: subcommand failed.
Traceback (most recent call last):
  File "build_mozc.py", line 1437, in <module>
    main()
  File "build_mozc.py", line 1425, in main
    BuildMain(cmd_opts, cmd_args, original_directory_name)
  File "build_mozc.py", line 1040, in BuildMain
    BuildOnWindows(targets)
  File "build_mozc.py", line 1021, in BuildOnWindows
    RunOrDie([ninja, '-C', target_dir] + tokens)
  File "c:\work\mozc\src\build_tools\util.py", line 97, in RunOrDie
    '==========']))
build_tools.util.RunOrDieError:
==========
 ERROR: ninja.exe -C out/Release mozc_win32_build32
==========


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

Source code checked out with gclient sync command on Dec 31, 2013. Compiler is 
VC 2010 Professional Version 10.0.40219.1 with SP1Rel,
Microsoft .NET Framework Version 4.5.50709 SP1Rel, Windows 7 and Windows SDK 
v7.0A.


Please provide any additional information below.

Original issue reported on code.google.com by chenlimi...@gmail.com on 31 Dec 2013 at 5:00

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Apr 22, 2015

Thank you for the report.
Although I'm not able to reproduce this issue yet, it seems to be a text 
encoding issue.

Could you retry the build after deleting line 1209 in 
src/prediction/dictionary_predictor.cc?
https://code.google.com/p/mozc/source/browse/trunk/src/prediction/dictionary_pre
dictor.cc?r=178#1209
>   //  ex) 六本木+ヒルズ->レジデンス

Thanks.

Original comment by yukawa@google.com on 2 Jan 2014 at 10:27

  • Changed state: Started
  • Added labels: OpSys-Windows
@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Apr 22, 2015

Problem solved. Thank you very much! 

Original comment by chenlimi...@gmail.com on 5 Jan 2014 at 4:51

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Apr 22, 2015

[deleted comment]
@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Apr 22, 2015

By the way, your instruction says the mozc_tool.exe file is in 
C:\work\mozc\src\out\ReleaseDynamic\, but in reality it's in 
C:\work\mozc\src\out\Release. Hope it's the same file. Also, your instruction 
says one should look for a number of executables in 
C:\work\mozc\src\out\Release64 but in reality there is no such directory. The 
closest matching destination directory is C:\work\mozc\src\out\Release_x64. 
Hope that's what the instruction is talking about. 

Original comment by chenlimi...@gmail.com on 6 Jan 2014 at 3:04

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Apr 22, 2015

Thank you for letting them me know. Updated the instruction as r189 and r190.
Please let me know if there is still something incorrect.

Original comment by yukawa@google.com on 12 Jan 2014 at 8:59

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Apr 22, 2015

Should be fixed in r192.

Original comment by yukawa@google.com on 16 May 2014 at 1:24

  • Changed state: Fixed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.