After manually specifying the path:
BINARYEN_ROOT = os.path.expanduser(os.getenv('BINARYEN',
'/home/raphy/emsdk/upstream/emscripten/emcc')) # directory
I get this other error: No such file or directory: '/usr/bin/clang'
(base) raphy@pc:~$ emcc -v
emcc (Emscripten gcc/clang-like replacement + linker emulating GNU ld)
2.0.1
Traceback (most recent call last):
File "/home/raphy/emsdk/upstream/emscripten/emcc.py", line 3327, in
<module>
sys.exit(run(sys.argv))
File "/home/raphy/emsdk/upstream/emscripten/emcc.py", line 781, in run
code = run_process([clang, '-v'], check=False).returncode
File "/home/raphy/emsdk/upstream/emscripten/tools/shared.py", line
204, in run_process
ret = subprocess.run(cmd, check=check, input=input, *args, **kw)
File "/home/raphy/anaconda3/lib/python3.8/subprocess.py", line 493,
in run
with Popen(*popenargs, **kwargs) as process:
File "/home/raphy/anaconda3/lib/python3.8/subprocess.py", line 858,
in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/home/raphy/anaconda3/lib/python3.8/subprocess.py", line 1706,
in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: '/usr/bin/clang'
(base) raphy@pc:~$
Il giorno mar 27 lug 2021 alle ore 16:24 Raphael Stonehorse <
[email protected]> ha scritto:
> After executing `activate`:
>
> (base) raphy@pc:~/emsdk$ ./emsdk activate sdk-2.0.1-64bit
> Resolving SDK version '2.0.1' to
> 'sdk-releases-upstream-13e29bd55185e3c12802bc090b4507901856b2ba-64bit'
> Setting the following tools as active:
> node-14.15.5-64bit
> releases-upstream-13e29bd55185e3c12802bc090b4507901856b2ba-64bit
>
> Next steps:
> - To conveniently access emsdk tools from the command line,
> consider adding the following directories to your PATH:
> /home/raphy/emsdk
> /home/raphy/emsdk/node/14.15.5_64bit/bin
> /home/raphy/emsdk/upstream/emscripten
> - This can be done for the current shell by running:
> source "/home/raphy/emsdk/emsdk_env.sh"
> - Configure emsdk in your shell startup scripts by running:
> echo 'source "/home/raphy/emsdk/emsdk_env.sh"' >>
> $HOME/.bash_profile
> (base) raphy@pc:~/emsdk$
>
> I've set in .bashrc :
>
> export PATH="/home/raphy/emsdk:$PATH"
> export PATH="/home/raphy/emsdk/node/14.15.5_64bit/bin:$PATH"
> export PATH="/home/raphy/emsdk/upstream/emscripten:$PATH"
>
> Now I get:
>
> (base) raphy@pc:~$ emcc -v
> emcc: error: BINARYEN_ROOT is set to empty value in
> /home/raphy/emsdk/upstream/emscripten/.emscripten
>
>
>
> Il giorno mar 27 lug 2021 alle ore 16:01 Raphael Stonehorse <
> [email protected]> ha scritto:
>
>>
>> Hi all!,
>>
>> I've installed emscripten in Ubuntu 20.04 .
>> The installation seemed ok:
>>
>> (base) raphy@pc:~$ git clone
>> https://github.com/emscripten-core/emsdk.git
>> Cloning into 'emsdk'...
>> remote: Enumerating objects: 2819, done.
>> remote: Counting objects: 100% (81/81), done.
>> remote: Compressing objects: 100% (46/46), done.
>> remote: Total 2819 (delta 48), reused 62 (delta 35), pack-reused 2738
>> Receiving objects: 100% (2819/2819), 1.48 MiB | 20.81 MiB/s, done.
>> Resolving deltas: 100% (1800/1800), done.
>>
>> (base) raphy@pc:~$ cd emsdk/
>> (base) raphy@pc:~/emsdk$ ./emsdk install sdk-2.0.1-64bit
>> (base) raphy@pc:~/emsdk$ ./emsdk install sdk-2.0.1-64bit
>> Resolving SDK version '2.0.1' to 'sdk-releases-upstream-
>> 13e29bd55185e3c12802bc090b4507901856b2ba-64bit'
>> Installing SDK 'sdk-releases-upstream-
>> 13e29bd55185e3c12802bc090b4507901856b2ba-64bit'..
>> Installing tool 'node-14.15.5-64bit'..
>> Downloading: /home/raphy/emsdk/zips/node-v14.15.5-linux-x64.tar.xz
>> from
>>
>> https://storage.googleapis.com/webassembly/emscripten-releases-builds/deps/node-
>> v14.15.5-linux-x64.tar.xz, 21391232 Bytes
>> Unpacking '/home/raphy/emsdk/zips/node-v14.15.5-linux-x64.tar.xz' to
>> '/home/raphy
>> /emsdk/node/14.15.5_64bit'
>> Done installing tool 'node-14.15.5-64bit'.
>> Installing tool
>> 'releases-upstream-13e29bd55185e3c12802bc090b4507901856b2ba-
>> 64bit'..
>> Downloading: /home/raphy/emsdk
>> /zips/13e29bd55185e3c12802bc090b4507901856b2ba-wasm-binaries.tbz2
>> from
>>
>> https://storage.googleapis.com/webassembly/emscripten-releases-builds/linux
>> /13e29bd55185e3c12802bc090b>
>> Unpacking '/home/raphy/emsdk
>> /zips/13e29bd55185e3c12802bc090b4507901856b2ba-wasm-binaries.tbz2' to
>> '
>> /home/raphy/emsdk/upstream'
>> Done installing tool 'releases-upstream-
>> 13e29bd55185e3c12802bc090b4507901856b2ba-64bit'.
>> Running post-install step: npm ci ...
>> Done running: npm ci
>> Done installing SDK 'sdk-releases-upstream-
>> 13e29bd55185e3c12802bc090b4507901856b2ba-64bit'.
>>
>> (base) raphy@pc:~/emsdk$ ./upstream/emscripten/emc
>> emcc emcmake emconfigure
>> emcc.py emcmake.py emconfigure.py
>> (base) raphy@pc:~/emsdk$ ./upstream/emscripten/emcc --check
>>
>>
>> ========================================================================
>> ======
>> Welcome to Emscripten!
>>
>> This is the first time any of the Emscripten tools has been run.
>>
>> A settings file has been copied to
>> /home/raphy/emsdk/upstream/emscripten
>> /.emscripten, at absolute path: /home/raphy/emsdk/upstream/emscripten
>> /.emscripten
>>
>> It contains our best guesses for the important paths, which are:
>>
>> LLVM_ROOT = /usr/bin
>> NODE_JS = /home/raphy/.nvm/versions/node/v14.17.0/bin/node
>> EMSCRIPTEN_ROOT = /home/raphy/emsdk/upstream/emscripten
>>
>> Please edit the file if any of those are incorrect.
>>
>> This command will now exit. When you are done editing those paths,
>> re-run it.
>>
>> ========================================================================
>> ======
>>
>> But when just simply checking the version I get "no config file found" :
>>
>> (base) raphy@pc:~/emsdk$ ./upstream/emscripten/emcc -v
>> emcc: error: emscripten config file not found:
>> /home/raphy/emsdk/.emscripten
>>
>> What am I missing? How to solve the problem?
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "emscripten-discuss" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/emscripten-discuss/a-Ph7m7CXAU/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to
>> [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/emscripten-discuss/f34991ca-9b2b-449c-b779-c100df70caf8n%40googlegroups.com
>> <https://groups.google.com/d/msgid/emscripten-discuss/f34991ca-9b2b-449c-b779-c100df70caf8n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>
--
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/emscripten-discuss/CAKSMiAP7ax9iaGZtOws4btQ%2BS-TN6YJ5LwLyczNrQ_6p4oZHqQ%40mail.gmail.com.
