Description
If I remove the O2, I can built without errors. The emsdk is installed from sdk-incoming-64bit on 2016-08-21.
emsdk install --vs2015 sdk-incoming-64bit
I have plenty of free RAM(Total:16GB with no other programs running) and SSD space when the error happened.
F:\Emscripten\emscripten\incoming>emcc F:\App\SDL_App\TestEmscripten\TestEmscripten.cpp --bind -s FULL_ES2=1 -s USE_SDL=2 -s USE_SDL_IMAGE=2 -s ASSERTIONS=1 -D EMSCRIPTEN -std=c++11 -I F:\App\SDL_App\ext\glm-0.9.5.3\glm -O2 --llvm-opts 2 -o project.html
Traceback (most recent call last):
File "F:\Emscripten\emscripten\incoming\emcc", line 13, in
emcc.run()
File "F:\Emscripten\emscripten\incoming\emcc.py", line 1811, in run
JSOptimizer.flush()
File "F:\Emscripten\emscripten\incoming\emcc.py", line 1708, in flush
run_passes(chunks[0], title, just_split=False, just_concat=False)
File "F:\Emscripten\emscripten\incoming\emcc.py", line 1681, in run_passes
final = shared.Building.js_optimizer(final, passes, debug_level >= 4, JSOptimizer.extra_info, just_split=just_split, just_concat=just_concat)
File "F:\Emscripten\emscripten\incoming\tools\shared.py", line 1756, in js_optimizer
ret = js_optimizer.run(filename, passes, NODE_JS, debug, extra_info, just_split, just_concat)
File "F:\Emscripten\emscripten\incoming\tools\js_optimizer.py", line 555, in run
return temp_files.run_and_clean(lambda: run_on_js(filename, passes, js_engine, source_map, extra_info, just_split, just_concat))
File "F:\Emscripten\emscripten\incoming\tools\tempfiles.py", line 78, in run_and_clean
return func()
File "F:\Emscripten\emscripten\incoming\tools\js_optimizer.py", line 555, in
return temp_files.run_and_clean(lambda: run_on_js(filename, passes, js_engine, source_map, extra_info, just_split, just_concat))
File "F:\Emscripten\emscripten\incoming\tools\js_optimizer.py", line 450, in run_on_js
filenames = pool.map(run_on_chunk, commands, chunksize=1)
File "F:\Emscripten\python\2.7.5.3_64bit\lib\multiprocessing\pool.py", line 250, in map
return self.map_async(func, iterable, chunksize).get()
File "F:\Emscripten\python\2.7.5.3_64bit\lib\multiprocessing\pool.py", line 554, in get
raise self._value
WindowsError: [Error 2] The system cannot find the file specified
Activity
kripken commentedon Aug 23, 2016
EMCC_DEBUG=1
might show more info that can help.Also worth trying
emcc --clear-cache
to see if this was a disk error during system lib building.shaovoon commentedon Aug 24, 2016
I have clear cache and set EMCC_DEBUG=1. I got this in debug log.
DEBUG:root:testing for asm.js target, because if not present (i.e. this is plain vanilla llvm, not emscripten fastcomp), we will use the wasm target instead (set EMCC_WASM_BACKEND to skip this check)
DEBUG:root:check tells us to use asm.js backend
How to build fastcomp?
kripken commentedon Aug 24, 2016
You can use the sdk or build manually from source.
shaovoon commentedon Aug 25, 2016
One thing I do not understand, isn't sdk-incoming-64bit already Fastcomp enabled? Can you tell me which branch or tag is Fastcomp enabled by default?
saschanaz commentedon Aug 27, 2016
I'm having the same issue on SDK version 1.36.9 which is downloaded and built by
emsdk
tool. Maybe something went wrong on SDK part?JMLX42 commentedon Aug 27, 2016
@kripken same issue when building from sources with VS2015 yesterday with
incoming
andmaster
.js_optimizer.py
creates a bunch of temporary js files, creates a bunch of commands to call the optimizer on each file and dispatches that to Python'sPool
component (frompool.py
).But it looks like those temp files don't exist anymore when the pool runs or terminates.
kripken commentedon Aug 27, 2016
This is likely windows-specific, so I don't think I can help much, maybe @juj has an idea. But I would check if you see that problem on small "hello world" programs too, might help narrow things down.
saschanaz commentedon Aug 28, 2016
Yes I do. This simple code causes the problem.
Full debug log:
saschanaz commentedon Aug 30, 2016
I think this is not an unexistent fastcomp problem as my debug log says
DEBUG:root:check tells us to use asm.js backend
after the check.emsdk install sdk-tag-1.36.8-64bit
on Windows won't succeed emscripten-core/emscripten-fastcomp-clang#9kripken commentedon Aug 30, 2016
Those
DEBUG:root:failed to use vanilla file, will re-check: too many values to unpack
look bad, doesemcc --clear-cache
help?shaovoon commentedon Aug 31, 2016
emcc --clear-cache
does not help in my case.kripken commentedon Aug 31, 2016
What does
~/.emscripten_cache/is_vanilla.txt
contain? (that's the file it reads before showing that error)shaovoon commentedon Aug 31, 2016
There is only 1 line in my
is_vanilla.txt
0:F:/Emscripten/clang/fastcomp/build_incoming_vs2015_64/RelWithDebInfo/bin
This folder exists on my PC and is filled with clang tools.
15 remaining items