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

' gyp' fails when gyp r1667 or higher is used #198

GoogleCodeExporter opened this issue Apr 22, 2015 · 1 comment


Copy link

GoogleCodeExporter commented Apr 22, 2015

If you are using gclient to check out Mozc and its dependent libraries, this 
issue never affects you.

As of Mozc r171, has internally called gyp as 'python 
This was OK because /usr/bin/gyp was a python script for a long time.
However, gyp r1667 replaced /usr/bin/gyp with a bash script.
As a result, 'python /usr/bin/gyp' no longer works well and ' gyp' 
results in a syntax like this if you build Mozc r171 or prior with gyp r1667 or 
higher. (Note that Mozc r171 is designed and tested to be combined only with 
gyp r1656. See our DEPS file as described below)

Here is the sample error log.
  File "/home/user_name/work/oss_mozc/src/third_party/gyp/gyp", line 6
    BASE=`dirname $0`
SyntaxError: invalid syntax
Traceback (most recent call last):
  File "", line 1480, in <module>
  File "", line 1462, in main
    GypMain(cmd_opts, cmd_args)
  File "", line 926, in GypMain
  File "/home/user_name/work/oss_mozc/src/build_tools/", line 97, in RunOrDie

If you want to build Mozc r171 with gyp r1667 or higher, you can use the 
attached patch (except for Windows).

A bit detailed background:
Our DEPS file describes what versions of external libraries are used to build 
the corresponding release of Google Japanese Input.

Of course it is OK for a user and/or distributor to use OSS Mozc with different 
versions of external libraries as long as the source code license is satisfied, 
but we will put very low priority on fixing issues that occurs only in such a 
trial. Basically our primary goal is to release a maximum subset of Google 
Japanese Input under OSS license in a sustainable manner.

We appreciate your understanding of our situation.

Original issue reported on by on 16 Sep 2013 at 5:50


Copy link

GoogleCodeExporter commented Apr 22, 2015

Fixed in r178.

Original comment by on 31 Oct 2013 at 7:04

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

1 participant