:-D
On Mon, Apr 18, 2016 at 1:39 PM, Jakob Kummerow <[email protected]> wrote: > Hm. That appears to have bitrotted then. Which kind of indicates how much > usage the MinGW build is getting. It's community maintained, so feel free > to fix it and contribute a patch. As a first hint: instead of >> >> make out/Makefile.ia32 > > there should probably be > >> make out/Makefile.ia32.release >> make out/Makefile.ia32.debug > > in tools/mingw-generate-makefiles.sh around line 79. > > On Mon, Apr 18, 2016 at 7:58 PM, Zac Hansen <[email protected]> wrote: > >> Yeah, it doesn't work for me. Or maybe there's some step I'm missing? >> >> $ tools/mingw-generate-makefiles.sh >> find: 'out': No such file or directory >> make: *** No rule to make target `out/Makefile.ia32'. Stop. >> find: 'out': No such file or directory >> >> >> xaxxon@DESKTOP-QK88IBI MINGW64 ~/v8 ((1ff65e9...)) >> $ mkdir out >> >> xaxxon@DESKTOP-QK88IBI MINGW64 ~/v8 ((1ff65e9...)) >> $ tools/mingw-generate-makefiles.sh >> make: *** No rule to make target `out/Makefile.ia32'. Stop. >> >> >> On Mon, Apr 18, 2016 at 5:23 AM, Jakob Kummerow <[email protected]> >> wrote: >> >>> Have you seen the MinGW section of the instructions >>> <https://github.com/v8/v8/wiki/Building-with-Gyp#mingw>? >>> >>> On Sun, Apr 17, 2016 at 9:17 AM, Zac Hansen <[email protected]> wrote: >>> >>>> Thank you for your help. I managed to get it compiling in visual >>>> studio 2015.2. >>>> >>>> I submitted this bug: >>>> https://bugs.chromium.org/p/v8/issues/detail?id=4927&can=2&start=0&num=100&q=&colspec=ID%20Type%20Status%20Priority%20Owner%20Summary%20HW%20OS%20Component%20Stars&groupby=&sort= >>>> >>>> I hope that is sufficient information. >>>> >>>> --Zac >>>> >>>> On Saturday, April 16, 2016 at 10:20:09 PM UTC-7, Jochen Eisinger wrote: >>>>> >>>>> I use the mingw that comes with depot_tools (specifically, started via >>>>> git_bash.bat in depot_tools/git-1.9.5 (or whatever the exact directory >>>>> name >>>>> is). >>>>> >>>>> I use, however, visual studio 2015 to build (I just open the >>>>> build/all.sln using VS). I don't think the make generator works on >>>>> windows. >>>>> You might have some luck using ninja (GYP_GENERATORS=ninja). >>>>> >>>>> Can you file a bug about landmines not working with the depot_tool >>>>> toolchain? >>>>> >>>>> best >>>>> -jochen >>>>> >>>>> On Sun, Apr 17, 2016 at 1:39 AM Zac Hansen <[email protected]> wrote: >>>>> >>>>>> It seems the instructions here: >>>>>> https://github.com/v8/v8/wiki/Building-with-Gyp have been broken >>>>>> for 4+ years when looking for solutions to the problems I"m having. >>>>>> >>>>>> I done a clean checkout with DEPOT_TOOLS_WIN_TOOLCHAIN=0 set, put >>>>>> python in my path, but when I type make ia32.releaseI get: >>>>>> >>>>>> $ make ia32.release -j4 >>>>>> make[1]: Entering directory `/c/Users/xaxxon/deleteme3/v8/out' >>>>>> make[1]: *** No rule to make target `../build\isolate.gypi', needed >>>>>> by `Makefile.ia32.release'. Stop. >>>>>> make[1]: Leaving directory `/c/Users/xaxxon/deleteme3/v8/out' >>>>>> make: *** [ia32.release] Error 2 >>>>>> >>>>>> >>>>>> >>>>>> or if I do x64.release: >>>>>> >>>>>> >>>>>> $ make x64.release -j4 >>>>>> make[1]: Entering directory `/c/Users/xaxxon/deleteme3/v8/out' >>>>>> third_party\icu\icudata.target.x64.release.mk:8: warning: overriding >>>>>> commands for target `/c/Users/xaxxon/deleteme3/v8/out/x64.release\ >>>>>> icudt.dll' >>>>>> third_party\icu\icudata.host.x64.release.mk:8: warning: ignoring old >>>>>> commands for target >>>>>> `/c/Users/xaxxon/deleteme3/v8/out/x64.release\icudt.dll' >>>>>> make[1]: *** No rule to make target `../build\isolate.gypi', needed >>>>>> by `Makefile.x64.release'. Stop. >>>>>> make[1]: Leaving directory `/c/Users/xaxxon/deleteme3/v8/out' >>>>>> make: *** [x64.release] Error 2 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> and if I don't do the DEPOT_TOOLS_WIN_TOOLCHAIN=0, I get >>>>>> landmines.py errors. >>>>>> >>>>>>> >>>>>>> >>>>>>> C:\Users\xaxxon\deleteme4>fetch v8 >>>>>>> Running: 'c:\Users\xaxxon\depot_tools\python276_bin\python.exe' >>>>>>> 'c:\Users\xaxxon\depot_tools\gclient.py' root >>>>>>> Running: 'c:\Users\xaxxon\depot_tools\python276_bin\python.exe' >>>>>>> 'c:\Users\xaxxon\depot_tools\gclient.py' config --spec 'solutions = >>>>>>> [ >>>>>>> { >>>>>>> "managed": False, >>>>>>> "name": "v8", >>>>>>> "url": "https://chromium.googlesource.com/v8/v8.git", >>>>>>> "custom_deps": {}, >>>>>>> "deps_file": "DEPS", >>>>>>> "safesync_url": "", >>>>>>> }, >>>>>>> ] >>>>>>> ' >>>>>>> Running: 'c:\Users\xaxxon\depot_tools\python276_bin\python.exe' >>>>>>> 'c:\Users\xaxxon\depot_tools\gclient.py' sync --with_branch_heads >>>>>>> Error: Command >>>>>>> 'c:\\Users\\xaxxon\\depot_tools\\python276_bin\\python.exe >>>>>>> v8/build/landmines.py' returned non-zero exit status 1 in C:\Users\ >>>>>>> xaxxon\deleteme4 >>>>>>> Traceback (most recent call last): >>>>>>> File "c:\Users\xaxxon\depot_tools\\fetch.py", line 346, in >>>>>>> <module> >>>>>>> sys.exit(main()) >>>>>>> File "c:\Users\xaxxon\depot_tools\\fetch.py", line 341, in main >>>>>>> return run(options, spec, root) >>>>>>> File "c:\Users\xaxxon\depot_tools\\fetch.py", line 335, in run >>>>>>> return checkout.init() >>>>>>> File "c:\Users\xaxxon\depot_tools\\fetch.py", line 142, in init >>>>>>> self.run_gclient(*sync_cmd) >>>>>>> File "c:\Users\xaxxon\depot_tools\\fetch.py", line 76, in >>>>>>> run_gclient >>>>>>> return self.run(cmd_prefix + cmd, **kwargs) >>>>>>> File "c:\Users\xaxxon\depot_tools\\fetch.py", line 66, in run >>>>>>> return subprocess.check_output(cmd, **kwargs) >>>>>>> File "c:\Users\xaxxon\depot_tools\python276_bin\lib\subprocess.py" >>>>>>> , line 573, in check_output >>>>>>> raise CalledProcessError(retcode, cmd, output=output) >>>>>>> subprocess.CalledProcessError: Command '('c:\\Users\\xaxxon\\ >>>>>>> depot_tools\\python276_bin\\python.exe', 'c:\\Users\\xaxxon\\ >>>>>>> depot_tools\\gclient.py', 'sync', '--with_branch_heads')' returned >>>>>>> non-zero exit status 2 >>>>>>> >>>>>>> >>>>>>> someone previously suggested running gclient sync after running into >>>>>> this error: >>>>>> >>>>>> C:\Users\xaxxon\deleteme4\v8>gclient sync >>>>>> .gclient file in parent directory C:\Users\xaxxon\deleteme4 might not >>>>>> be the file you want to use >>>>>> Syncing projects: 100% (17/17), done. >>>>>> >>>>>> >>>>>> ________ running 'c:\Users\xaxxon\depot_tools\python276_bin\python.exe >>>>>> v8/build/landmines.py' in 'C:\Users\xaxxon\deleteme4' >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Please follow the instructions at https:// >>>>>> www.chromium.org/developers/how-tos/build-instructions-windows >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Traceback (most recent call last): >>>>>> File "v8/build/landmines.py", line 245, in <module> >>>>>> sys.exit(main()) >>>>>> File "v8/build/landmines.py", line 232, in main >>>>>> gyp_environment.set_environment() >>>>>> File "C:\Users\xaxxon\deleteme4\v8\build\gyp_environment.py", line >>>>>> 54, in set_environment >>>>>> vs_toolchain.SetEnvironmentAndGetRuntimeDllDirs() >>>>>> File "C:\Users\xaxxon\deleteme4\v8\build\vs_toolchain.py", line 44, >>>>>> in SetEnvironmentAndGetRuntimeDllDirs >>>>>> Update() >>>>>> File "C:\Users\xaxxon\deleteme4\v8\build\vs_toolchain.py", line 331 >>>>>> , in Update >>>>>> subprocess.check_call(get_toolchain_args) >>>>>> File "c:\Users\xaxxon\depot_tools\python276_bin\lib\subprocess.py", >>>>>> line 540, in check_call >>>>>> raise CalledProcessError(retcode, cmd) >>>>>> subprocess.CalledProcessError: Command '['c:\\Users\\xaxxon\\ >>>>>> depot_tools\\python276_bin\\python.exe', 'c:\\Users\\xaxxon\\ >>>>>> depot_tools\\win_toolchain\\get_toolchain_if_necessary.py', '--output >>>>>> -json', 'C:\\Users\\xaxxon\\deleteme4\\v8\\build\\win_toolchain.json', >>>>>> '03a4e939cd325d6bc5216af41b92d02dda1366a6']' returned non-zero exit >>>>>> status 1 >>>>>> Error: Command 'c:\\Users\\xaxxon\\depot_tools\\python276_bin\\python.exe >>>>>> v8/build/landmines.py' returned non-zero exit status 1 in C:\Users\ >>>>>> xaxxon\deleteme4 >>>>>> >>>>>> >>>>>> >>>>>> if I try the build anyhow: >>>>>> >>>>>> >>>>>> $ make ia32.release >>>>>> PYTHONPATH= >>>>>> "/c/Users/xaxxon/deleteme4/v8/tools/generate_shim_headers:/c/Users/xaxxon/deleteme4/v8/build::/c/Users/xaxxon/deleteme4/v8/build/gyp/pylib:" >>>>>> \ >>>>>> GYP_GENERATORS=make \ >>>>>> build/gyp/gyp --generator-output="out" build/all.gyp \ >>>>>> -Ibuild/standalone.gypi --depth=. \ >>>>>> -Dv8_target_arch=ia32 \ >>>>>> \ >>>>>> \ >>>>>> -S.ia32.release -Dv8_enable_backtrace=1 - >>>>>> Darm_fpu=default -Darm_float_abi=default >>>>>> make[1]: Entering directory `/c/Users/xaxxon/deleteme4/v8/out' >>>>>> make[1]: *** No rule to make target `../build\isolate.gypi', needed >>>>>> by `Makefile.ia32.release'. Stop. >>>>>> make[1]: Leaving directory `/c/Users/xaxxon/deleteme4/v8/out' >>>>>> make: *** [ia32.release] Error 2 >>>>>> >>>>>> >>>>>> >>>>>> Anyone have a working procedure? Or, failing that, does anyone know >>>>>> if v8 will build under the latest Visual Studio? >>>>>> >>>>>> Thank you. >>>>>> >>>>>> --Zac >>>>>> >>>>>> -- >>>>>> -- >>>>>> 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. >>>>>> >>>>> -- >>>> -- >>>> 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. >>>> >>> >>> -- >>> -- >>> v8-users mailing list >>> [email protected] >>> http://groups.google.com/group/v8-users >>> --- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "v8-users" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/v8-users/eC_0XaOOBFM/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> -- >> 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. >> > > -- > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users > --- > You received this message because you are subscribed to a topic in the > Google Groups "v8-users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/v8-users/eC_0XaOOBFM/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- 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.
