Emscripten should never be using system Clang, so uninstalling/reinstalling different versions should not be affecting the issue.
With emsdk, you should not delete ~/.emscripten manually, or if you do, you must call "emsdk activate <sdk-of-your-choice>" to recreate ~/.emscripten. Otherwise Emscripten compiler won't locate the packages under the emsdk directory. I believe the root cause is the "node" vs "nodejs" issue. The next version of emsdk will contain two different fixes for that: it will autodetect when system node.js is "nodejs" and not "node", and second, emsdk will come with node.js bundled in it, so that one doesn't necessarily need a system node.js. As a manual workaround before the fixed version, you can try calling "emsdk activate <sdk-of-your-choice>", and then editing the generated ~/.emscripten file to change "node" to "nodejs". 2015-10-26 16:00 GMT+02:00 Flix <[email protected]>: > > > *SOLVED*For some reasons The Ubuntu upgrade system had detected that the > *nodejs* package was useless had to be removed from version 15.10. > > I had to reinstall it, to delete again all the .emscripten config files in > $HOME, to rerun: emcc -v twice and everything started to work again. > > Thanks! > > > -- > 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. > -- 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.
