Try clearing the install, and redoing it again, this time capturing the log
output to check for errors. I believe it had run out of memory again, given
that the executables don't exist.
Note that emsdk has a number of cores configure option ("-j1") that you can
pass to the build to make it only use a single core, which will reduce
memory pressure.
2015-12-09 21:53 GMT+02:00 <[email protected]>:
> In the past I've installed emscripten in a vagrant box via `apt-get
> install -y emscripten`.
>
> Yesterday I started to setup a new box, and wanted to use the latest
> version of emscripten. I followed the instructions on the website for
> installing the SDK.
>
> When running `./emsdk install latest`, my vagrant box ran out of memory,
> so I bumped up the vm settings, and re-ran `./emsdk install latest`.
>
> Eventually everything worked, I ran `./emsdk activate latest`, then
> `source ./emsdk_env.sh`.
>
> Now when I run `emcc -v` I get an error about `clang++` not being found:
>
> vagrant@vagrant-ubuntu-trusty-32:~/emsdk_portable$ emcc -v
>> WARNING:root:Could not verify LLVM version: [Errno 2] No such file or
>> directory
>> WARNING:root:could not check fastcomp: [Errno 2] No such file or directory
>> INFO:root:(Emscripten: Running sanity checks)
>> CRITICAL:root:Cannot find
>> /home/vagrant/emsdk_portable/clang/tag-e1.35.12/build_tag-e1.35.12_32/bin/clang++,
>> check the paths in /home/vagrant/.emscripten
>
>
> My ~/.emscripten config:
>
> import os
>>
>> LLVM_ROOT='/home/vagrant/emsdk_portable/clang/tag-e1.35.12/build_tag-e1.35.12_32/bin'
>> NODE_JS='/home/vagrant/emsdk_portable/node/4.1.1_32bit/bin/node'
>> EMSCRIPTEN_ROOT='/home/vagrant/emsdk_portable/emscripten/tag-1.35.12'
>>
>> EMSCRIPTEN_NATIVE_OPTIMIZER='/home/vagrant/emsdk_portable/emscripten/tag-1.35.12_32bit_optimizer/optimizer'
>> SPIDERMONKEY_ENGINE = ''
>> V8_ENGINE = ''
>> TEMP_DIR = '/tmp'
>> COMPILER_ENGINE = NODE_JS
>> JS_ENGINES = [NODE_JS]
>
>
> An the LLVM_ROOT folder:
>
>>
>> vagrant@vagrant-ubuntu-trusty-32:~/emsdk_portable$ ls -lah
>> /home/vagrant/emsdk_portable/clang/tag-e1.35.12/build_tag-e1.35.12_32/bin/
>> total 4.5G
>> drwxr-xr-x 2 vagrant vagrant 4.0K Dec 9 18:55 .
>> drwxr-xr-x 13 vagrant vagrant 4.0K Dec 9 18:55 ..
>> -rwxr-xr-x 1 vagrant vagrant 330M Dec 9 11:00 arcmt-test
>> -rwxr-xr-x 1 vagrant vagrant 227M Dec 9 11:07 bugpoint
>> -rwxr-xr-x 1 vagrant vagrant 19K Dec 9 11:00 c-arcmt-test
>> -rwxr-xr-x 1 vagrant vagrant 269K Dec 9 10:59 c-index-test
>> -rw-r--r-- 1 vagrant vagrant 0 Dec 9 10:33 clang-3.8
>> -rwxr-xr-x 1 vagrant vagrant 717M Dec 9 11:04 clang-check
>> -rwxr-xr-x 1 vagrant vagrant 30M Dec 9 10:46 clang-format
>> -rwxr-xr-x 1 vagrant vagrant 12M Dec 9 09:23 clang-tblgen
>> -rwxr-xr-x 1 vagrant vagrant 12K Dec 9 09:21 count
>> -rwxr-xr-x 1 vagrant vagrant 284M Dec 9 10:33 diagtool
>> -rwxr-xr-x 1 vagrant vagrant 4.2M Dec 9 09:21 FileCheck
>> -rwxr-xr-x 1 vagrant vagrant 290M Dec 9 11:15 llc
>> -rwxr-xr-x 1 vagrant vagrant 276M Dec 9 11:13 lli
>> -rwxr-xr-x 1 vagrant vagrant 1.9M Dec 9 11:13 lli-child-target
>> -rwxr-xr-x 1 vagrant vagrant 106M Dec 9 09:22 llvm-ar
>> -rwxr-xr-x 1 vagrant vagrant 35M Dec 9 11:11 llvm-as
>> -rwxr-xr-x 1 vagrant vagrant 4.2M Dec 9 11:07 llvm-bcanalyzer
>> -rwxr-xr-x 1 vagrant vagrant 2.5M Dec 9 09:22 llvm-config
>> -rwxr-xr-x 1 vagrant vagrant 43M Dec 9 11:09 llvm-cov
>> -rwxr-xr-x 1 vagrant vagrant 256M Dec 9 11:06 llvm-c-test
>> -rwxr-xr-x 1 vagrant vagrant 39M Dec 9 11:15 llvm-cxxdump
>> -rwxr-xr-x 1 vagrant vagrant 34M Dec 9 11:08 llvm-diff
>> -rwxr-xr-x 1 vagrant vagrant 28M Dec 9 11:07 llvm-dis
>> -rwxr-xr-x 1 vagrant vagrant 278M Dec 9 11:14 llvm-dsymutil
>> -rwxr-xr-x 1 vagrant vagrant 42M Dec 9 11:12 llvm-dwarfdump
>> -rwxr-xr-x 1 vagrant vagrant 57M Dec 9 11:13 llvm-extract
>> lrwxrwxrwx 1 vagrant vagrant 7 Dec 9 09:22 llvm-lib -> llvm-ar
>> -rwxr-xr-x 1 vagrant vagrant 50M Dec 9 11:13 llvm-link
>> -rwxrwxr-x 1 vagrant vagrant 1.7K Dec 9 08:22 llvm-lit
>> -rwxr-xr-x 1 vagrant vagrant 339M Dec 9 11:16 llvm-lto
>> -rwxr-xr-x 1 vagrant vagrant 107M Dec 9 11:06 llvm-mc
>> -rwxr-xr-x 1 vagrant vagrant 3.6M Dec 9 11:08 llvm-mcmarkup
>> -rwxr-xr-x 1 vagrant vagrant 105M Dec 9 11:07 llvm-nm
>> -rwxr-xr-x 1 vagrant vagrant 58M Dec 9 11:05 llvm-objdump
>> -rwxr-xr-x 1 vagrant vagrant 6.8M Dec 9 11:12 llvm-pdbdump
>> -rwxr-xr-x 1 vagrant vagrant 83K Dec 9 09:21 llvm-PerfectShuffle
>> -rwxr-xr-x 1 vagrant vagrant 26M Dec 9 11:17 llvm-profdata
>> lrwxrwxrwx 1 vagrant vagrant 7 Dec 9 09:22 llvm-ranlib -> llvm-ar
>> -rwxr-xr-x 1 vagrant vagrant 42M Dec 9 11:11 llvm-readobj
>> -rwxr-xr-x 1 vagrant vagrant 56M Dec 9 11:08 llvm-rtdyld
>> -rwxr-xr-x 1 vagrant vagrant 38M Dec 9 11:07 llvm-size
>> -rwxr-xr-x 1 vagrant vagrant 63M Dec 9 11:12 llvm-split
>> -rwxr-xr-x 1 vagrant vagrant 30M Dec 9 11:08 llvm-stress
>> -rwxr-xr-x 1 vagrant vagrant 45M Dec 9 11:08 llvm-symbolizer
>> -rwxr-xr-x 1 vagrant vagrant 33M Dec 9 08:26 llvm-tblgen
>> -rwxr-xr-x 1 vagrant vagrant 1.8M Dec 9 09:21 not
>> -rwxr-xr-x 1 vagrant vagrant 41M Dec 9 11:08 obj2yaml
>> -rwxr-xr-x 1 vagrant vagrant 381M Dec 9 11:10 opt
>> -rwxr-xr-x 1 vagrant vagrant 45M Dec 9 11:15 sancov
>> -rwxrwxr-x 1 vagrant vagrant 52K Dec 9 10:46 scan-build
>> -rwxrwxr-x 1 vagrant vagrant 4.4K Dec 9 10:46 scan-view
>> -rwxr-xr-x 1 vagrant vagrant 38M Dec 9 11:17 verify-uselistorder
>> -rwxr-xr-x 1 vagrant vagrant 7.0M Dec 9 11:11 yaml2obj
>> -rwxr-xr-x 1 vagrant vagrant 4.4M Dec 9 09:21 yaml-bench
>
>
> Any ideas what's going on here? Is running `./emsdk install latest`
> idempotent (and can re-run it if it errors out, and it'll pick up where it
> left off)?
>
> Any idea why there isn't a `clang++` file in the LLVM_ROOT or why
> clang-3.8 has a size of 0? Is this normal, or did something go wrong with
> my build?
>
> Thanks for any help or suggestions! I might just go back to installing
> via apt-get, but then I'll be on an older version. Is there a good way to
> `apt-get install` a more recent version? Any links someone can share?
> Thanks again!
>
>
> --
> 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.
