Erm. Two minutes after posting my eyes fall onto this message in the build 
log:

"Please follow the instructions at 
https://www.chromium.org/developers/how-tos/build-instructions-windows";

Setting the new environment variable seems to get me past the failure.

I will report if I fall into some other hole later. Sorry for wasting your 
time.

/T

On Thursday, December 17, 2015 at 4:35:21 PM UTC+3, t2771 wrote:
>
> I have been building and using v8 for several years now, things were 
> working great. I recently decided to upgrade from 4.6 to 4.7, following 
> Chrome, and ran into a problem.
>
> I am running Windows 10, no Cygwin. So:
>
> I downloaded depot_tools, unpacked the archive, added the path to the 
> unpacked files to PATH - OK.
> Ran gclient, it updated itself - OK.
> Ran gclient several more times to be sure it updated fully - OK (updated 
> completely the first time, in prior times it was sometimes continuing to 
> update on the second run).
> Created a new folder - OK.
> 'fetch v8' in the new folder - it downloads data for several minutes, then 
> fails with the message - 'Error: Command 
> 'c:...\\depot_tools\\python276_bin\\python.exe v8/build/landmines.py' 
> returned non-zero exit status 1 in ...'.
> Running 'gclient sync' fails in the same way.
>
> Is there something wrong with my configuration (I can't think of anything, 
> it's a pretty standard system with next to no software apart from Visual 
> Studio 2015, no Cygwin, plus as I said I have been building v8 for years, 
> it never failed like that, and I didn't change anything in the config - 
> apart from installing OS updates from Microsoft)? Any help?
>
> Thanks in advance.
>
> /T Crawford
>
>

-- 
-- 
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to