Generating builtins-generated => The system cannot execute the specified program.

[petebannister]

I have a hunch that this is due to the command line getting too long? Possibly only a Windows issue building from a long sub-path. And by long I don't mean all that long at all really - perhaps 20 chars.
One build I did actually succeeded and then had unresolved externals linking mksnapsot. I guess it would be luck of the draw as to where MAX_PATH and any whitespace in the commandline intersect..

In any case it looks like it is a problem that will only get worse. And this stage of the build could presumably run multiple instances of torque in parallel to avoid the bottleneck here.

[gengjiawen]

Same issue, the windows CI works good, not sure why.

[bnoordhuis]

CI builds in D:/a/v8-cmake/build which is probably just short enough to avoid the issue.

[petebannister]

This was quite a while ago now, but if IIRC, multiple files are passed to torque in one go. Perhaps this could be divided up and maybe even parallelized in the process - I think it was maxing out only one core on my system. But as I said this was a long time ago so I could be mistaken!!

[Jamlee]

Same issue

[technyon]

Any update on this? The windows build is completely broken like this, and there's already a pull request.

[ScSofts]

I think I found some solutions.

1. Clone your project in a shorter path
2. Enable Long Paths in Windows 10, Version 1607, and Later
3. Use an older version of v8-cmake

[kingdevnl]

Is there any other fix for this instead of having to use an older version?
I don't think for OSS it would be great to ask people to run a reg patch file to build a project.