search

skufog / libyuv

Automatically exported from code.google.com/p/libyuv
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

when doing a gclient sync I receive the 93% (15/16) done.tools/gyp and it fails as shown below? Any suggestions? #310

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
mkdir libyuv && cd libyuv
svn co http://src.chromium.org/svn/trunk/tools/depot_tools . 
./gclient config http://libyuv.googlecode.com/svn/trunk
./gclient sync 
What is the expected output? What do you see instead?
an error condition, not sure if there is something I have missing, here are the 
files I have added to the default installation
sudo yum update
sudo yum install make libtool autoconf subversion git cvs wget libogg-devel gcc 
gcc-c++

What version of the product are you using? On what operating system?
trying to install from the current trunk release 1773, CentOS 6.5 
uname -a = 2.6.32-431.el6.x86_64 #1 SMP Fri Nov 22 03:15:09 UTC 2013 x86_64 
x86_64 x86_64 GNU/Linux

Please provide any additional information below.

Checked out revision 1773.
Syncing projects:  93% (15/16), done.tools/gyp

________ running '/usr/bin/python trunk/tools/clang/scripts/update.py 
--mac-only ' in '/var/dev/libyuv.1'

________ running '/usr/bin/python trunk/build/gyp_chromium --depth=trunk 
trunk/a ll.gyp -Dextra_gyp_flag=0' in '/var/dev/libyuv.1'
Updating projects from gyp files...
Exception: invalid syntax (all.gyp, line 8)
Traceback (most recent call last):
  File "/var/dev/libyuv.1/trunk/tools/gyp/pylib/gyp/input.py", line 472, in Call LoadTargetBuildFile
    includes, depth, check, False)
  File "/var/dev/libyuv.1/trunk/tools/gyp/pylib/gyp/input.py", line 362, in Load TargetBuildFile
    includes, True, check)
  File "/var/dev/libyuv.1/trunk/tools/gyp/pylib/gyp/input.py", line 219, in Load OneBuildFile
    None)
  File "<string>", line 8

   ^
SyntaxError: invalid syntax

Error: Command /usr/bin/python trunk/build/gyp_chromium --depth=trunk 
trunk/all. gyp -Dextra_gyp_flag=0 returned non-zero exit status 1 in 
/var/dev/libyuv.1

Thanks in advance,

Peter Michael Gits

Original issue reported on code.google.com by pgits.ge...@gmail.com on 3 Feb 2014 at 9:54

GoogleCodeExporter commented 9 years ago 
depot tools comes from chromium and webrtc.
the DEPS files in trunk specifies versions, which are likely a little old.
I usually check the chromium build instructions when things break.

To just get the source, without the dependencies
svn checkout https://libyuv.googlecode.com/svn/trunk/ libyuv

you could try webrtc, which includes libyuv, to see if the issue is specific to 
libyuv, or a more general depottools issue.

trying your tests, albiet on windows, the first one syncs up the depot tools to 
current folder

svn co http://src.chromium.org/svn/trunk/tools/depot_tools .
normally I would add them to my path.  Those will be tip of tree, so its 
possible theres a breakage.

.\gclient config http://libyuv.googlecode.com/svn/trunk
creates a .gclient file
its installing git, svn, python
my .gclient file looks like this
solutions = [
  { "name"        : "trunk",
    "url"         : "http://libyuv.googlecode.com/svn/trunk",
    "deps_file"   : "DEPS",
    "managed"     : True,
    "custom_deps" : {
    },
    "safesync_url": "",
  },
]
cache_dir = None

.\gclient sync pulls in the source and all DEPS.
most of the dependencies are for tests or mobile sdks.  The only real code 
dependency is jpeg.
this takes a few minutes, but works for me.

On linux, once you have a sync, its good to call
tools/clang/scripts/update.sh
before a build, if you might want to use clang.

and then an example build
GYP_DEFINES="clang=0 target_arch=x64" ./build/gyp_chromium -f ninja --depth=. 
libyuv_test.gyp
ninja -j8 -C out/Debug
ninja -j8 -C out/Release

Original comment by fbarch...@google.com on 5 Feb 2014 at 1:50

GoogleCodeExporter commented 9 years ago 
As it works for me, and its a python error, perhaps you should see what version 
of python you're running?

Original comment by fbarch...@google.com on 6 Feb 2014 at 11:44

GoogleCodeExporter commented 9 years ago 
I think the only actionable item I can do for this now would be to update to 
the latest chromium dependencies.

Original comment by fbarch...@chromium.org on 28 Feb 2014 at 11:32

GoogleCodeExporter commented 9 years ago 
bumped chromium deps 255773

Original comment by fbarch...@chromium.org on 26 Mar 2014 at 9:30

GoogleCodeExporter commented 9 years ago 
r991 updated the gclient sync to newer chromium tools.  mainly affects runhooks 
which gclient sync runs.
Works for me on mac, ios and windows.

Original comment by fbarch...@chromium.org on 28 Mar 2014 at 6:21