32611 2009-12-16 08:12:51 -0800 build-webkit --chromium can't handle changes to GYP files 2013-04-08 14:12:53 -0700 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) All All RESOLVED WONTFIX P2 Normal --- 1 abarth webkit-unassigned eric evan schenney yaar oldest_to_newest 172297 0 abarth 2009-12-16 08:12:51 -0800 abarth@qbuntu:~/git/webkit-chromium-ews$ touch WebKit/chromium/base/base.gyp abarth@qbuntu:~/git/webkit-chromium-ews$ ./WebKitTools/Scripts/build-webkit --chromium make -j4 BUILDTYPE=Release webkit gyp_webkit -fmake --ignore-environment -Ibuild/common.gypi "--depth=." "-Dinside_chromium_build=0" "-Dv8_use_snapshot=false" "-Dmsvs_use_common_release=0" WebKit.gyp /bin/sh: gyp_webkit: not found make: *** [Makefile] Error 127 This is blocking the EWS. 172318 1 abarth 2009-12-16 09:12:58 -0800 I've found a way to hack around the problem: In WebKit/chromium/Makefile: gyp_webkit -fmake --ignore-environment ...... should be python gyp_webkit -fmake --ignore-environment ...... Now I just need to figure out where this file comes from. 172325 2 abarth 2009-12-16 09:24:15 -0800 Found the bug: abarth@qbuntu:~/git/webkit-qt-ews/WebKit/chromium/tools/gyp$ svn diff Index: pylib/gyp/generator/make.py =================================================================== --- pylib/gyp/generator/make.py (revision 751) +++ pylib/gyp/generator/make.py (working copy) @@ -1129,7 +1129,8 @@ makefile_name, ' '.join(map(Sourceify, build_files)), gyp.common.EncodePOSIXShellList( - [gyp.common.FixIfRelativePath(params['gyp_binary'], options.depth), + ['python', + gyp.common.FixIfRelativePath(params['gyp_binary'], options.depth), '-fmake'] + gyp.RegenerateFlags(options) + build_files_args))) Now I just need to figure out what the process is for upstreaming the fix.