AFAIK, if you use the --embedded installation option you also need to call emcc etc. with the --em-config option to tell the tools where the .emscripten file is.
If you're just getting started with emscripten I would recommend not installing with --embedded, this is only really useful if you need to manage several emscripten installations in parallel on the same machine. Cheers, -Floh Am Samstag, 17. Oktober 2015 17:28:29 UTC+2 schrieb Flix: > > > *Solved!* > > I had to delete all the files in my HOME directory starting with > .emscripten and rerun (twice): ./emcc -v. > Now my output is: > > INFO root: (Emscripten: Running sanity checks) > emcc (Emscripten gcc/clang-like replacement + linker emulating GNU ld) > 1.34.1 > clang version 3.7.0 > Target: x86_64-unknown-linux-gnu > Thread model: posix > Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/4.9 > Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/4.9.2 > Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/5.0.1 > Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9 > Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9.2 > Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.0.1 > Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9 > Candidate multilib: .;@m64 > Selected multilib: .;@m64 > INFO root: (Emscripten: Running sanity checks) > > > However I think it's not possible to have an embedded and movable > emscripten installation, since now I got new ".emscripten files" in my HOME > folder (and thus: emsdk activate --embedded XXX, that should create a > "local" configuration, becomes useless). > > -- 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.
