Yes the problems appears with -02 optimization and when adding --pre-js foo.js file . I don't see anything adding EMCC_DEBUG=2. Where is the so called "temp dir" supposed to be ? (OSX here)
Thanks. Stephane Le samedi 19 juillet 2014 00:54:49 UTC+2, Alon Zakai a écrit : > > That likely means a failure during a JS optimization pass. Please file a > testcase if you can. If you prefer to debug yourself, running with > EMCC_DEBUG=2 should emit all the outputs to the temp dir, and sometimes it > is obvious from them what is wrong. > > - Alon > > > > On Fri, Jul 18, 2014 at 4:52 AM, Stéphane Letz <[email protected] > <javascript:>> wrote: > >> After updating to latest SDK 1.21.0, we now get this error when compiling >> our C++ code: >> >> >> /Documents/emsdk-portable/emscripten/1.21.0/tools/eliminator/node_modules/uglify-js/lib/parse-js.js:272 >> throw new JS_Parse_Error(message, line, col, pos); >> ^ >> TypeError: object is not a function >> at new JS_Parse_Error >> (/Documents/emsdk-portable/emscripten/1.21.0/tools/eliminator/node_modules/uglify-js/lib/parse-js.js:261:21) >> at js_error >> (/Documents/emsdk-portable/emscripten/1.21.0/tools/eliminator/node_modules/uglify-js/lib/parse-js.js:272:15) >> at croak >> (/Documents/emsdk-portable/emscripten/1.21.0/tools/eliminator/node_modules/uglify-js/lib/parse-js.js:742:17) >> at token_error >> (/Documents/emsdk-portable/emscripten/1.21.0/tools/eliminator/node_modules/uglify-js/lib/parse-js.js:749:17) >> at unexpected >> (/Documents/emsdk-portable/emscripten/1.21.0/tools/eliminator/node_modules/uglify-js/lib/parse-js.js:755:17) >> at block_ >> (/Documents/emsdk-portable/emscripten/1.21.0/tools/eliminator/node_modules/uglify-js/lib/parse-js.js:998:40) >> at >> /Documents/emsdk-portable/emscripten/1.21.0/tools/eliminator/node_modules/uglify-js/lib/parse-js.js:978:43 >> at >> /Documents/emsdk-portable/emscripten/1.21.0/tools/eliminator/node_modules/uglify-js/lib/parse-js.js:982:29 >> at >> /Documents/emsdk-portable/emscripten/1.21.0/tools/eliminator/node_modules/uglify-js/lib/parse-js.js:1112:43 >> at maybe_unary >> (/Documents/emsdk-portable/emscripten/1.21.0/tools/eliminator/node_modules/uglify-js/lib/parse-js.js:1209:27) >> >> >> Any idea? >> >> Thanks. >> >> Stéphane Letz >> >> >> >> >> Le lundi 7 juillet 2014 15:12:16 UTC+2, jj a écrit : >> >>> Hi everyone, >>> >>> it's due time for a new emsdk update, and this one finally brings in >>> support for Linux as well! >>> >>> Download Emscripten SDK 1.21.0 from https://github.com/ >>> kripken/emscripten/wiki/Emscripten-SDK >>> >>> Here's what's new in the SDK: >>> - Matches the Emscripten compiler 1.21.0. See compiler ChangeLog at >>> https://github.com/kripken/emscripten/blob/incoming/ChangeLog . >>> - Updated SpiderMonkey to version 30. >>> - The Master and Incoming SDK versions now automate the process of >>> getting the Emscripten "fastcomp" Clang backend and building it. This >>> allows the SDK to support Linux as well, where to be compatible with the >>> widest variety of distros, Emscripten Clang is always built from sources. >>> - vs-tool version 0.94 fixes known reported issues with Visual Studio >>> integration. >>> - Fixes Windows Python issues with the portable SDK. >>> - A lot of people have reported that they would like to see the unit >>> test suite being shipped by the SDK, so it has been restored to be part of >>> the Emscripten package. The unit test suite is optional for Emscripten >>> operation however, so if you want to conserve disk space, you can freely >>> delete that directory. >>> - The process of setting up PATH and environment variables has been >>> updated to add support for Linux and OSX. Use the 'emsdk_env' script to >>> help set up a cmd prompt with the currently active tools. >>> >>> The new build automation in the SDK allows all three OSes to fetch and >>> build the latest fastcomp without user intervention. This requires a >>> working native compiler toolchain on the system. As a design principle to >>> make emsdk be as non-intrusive as possible, we want to avoid making emsdk >>> access apt-get and/or other distro-specific package managers, so instead >>> emsdk is set up to print out error conditions on missing tools, that should >>> guide the user to perform the installation of the required dependencies if >>> those don't exist (gcc, cmake, python, node). >>> >>> As usual, the following bug trackers take in items for the SDK: >>> - Emscripten compiler: https://github.com/kripken/emscripten/issues >>> - Emsdk: https://github.com/juj/emsdk/issues >>> - Visual Studio integration: https://github.com/juj/vs-tool/issues >>> >>> Happy Emscriptening! >>> Jukka >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "emscripten-discuss" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" 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.
