Package Details: emscripten-git 2:2.0.15.r31.g249815cf7-2

Git Clone URL: https://aur.archlinux.org/emscripten-git.git (read-only, click to copy)
Package Base: emscripten-git
Description: LLVM-to-JavaScript compiler
Upstream URL: http://emscripten.org
Licenses: custom
Conflicts: binaryen, emscripten
Provides: emscripten
Submitter: None
Maintainer: None
Last Packager: haawda
Votes: 28
Popularity: 0.000000
First Submitted: 2012-10-01 17:47 (UTC)
Last Updated: 2021-03-13 19:40 (UTC)

Dependencies (13)

Required by (9)

Sources (5)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

EscapedNull commented on 2014-08-07 21:42 (UTC)

haawada, I don't know how I didn't find that page when I was looking for a solution, but sure enough, it worked. I was running emcc in a proot without binding /dev/shm. Cheers and thanks for the update!

haawda commented on 2014-08-07 16:57 (UTC)

Does this help? http://stackoverflow.com/questions/3314031/django-celery-implementation-oserror-errno-38-function-not-implemented#comment7543003_3699231

EscapedNull commented on 2014-08-07 15:12 (UTC)

After the update to package version 1.20.0, the python invoker script (emcc) always crashes. I tried $ cp -i emscripten-git/emscripten.config ~/.emscripten $ source ./emscripten-git/emscripten.sh $ emcc --clear-cache and still have had no luck. I don't know whether this is a fault of the package, emscripten itself, my system, or something else. Here is the full stack trace and additional info: http://pastebin.com/tRwGn8db Looks like I'll be downgrading back to 1.18.3. If anyone else has run into this problem, please share. Any help is appreciated.

haawda commented on 2014-06-25 20:22 (UTC)

EscapedNull: this is the default behaviour of -git-packages. Btw., I updated the package, but I am really not sure if it is packaged correctly. Help is appreciated.

EscapedNull commented on 2014-04-28 12:21 (UTC)

What's up with these version numbers? PKGBUILD says 1.15.0, AUR says 1.15.0-1, and after upgrading em++ --version says 1.16.0? Anyway, thanks for the upgrade! em++ automatically detected the version change and cleared the cache; no logout was required for me. :)

bitwave commented on 2014-04-23 14:59 (UTC)

please add cmake as build dependency

cruelbob commented on 2014-03-21 20:43 (UTC)

I updated PKGBUILD. If you have previous version then you should restart system because of env variables.

svenstaro commented on 2014-03-21 18:58 (UTC)

The .emscripten file should look like this because you set those variables. LLVM_ROOT = os.path.expanduser(os.getenv('EMSCRIPTEN_FASTCOMP') or '/opt/emscripten-fastcomp') # directory Instead, it has this LLVM_ROOT = os.path.expanduser(os.getenv('LLVM') or '/usr/bin') # directory You should change the default config the package generates or provide the user with a good install message.

EscapedNull commented on 2014-03-20 12:41 (UTC)

@cruelbob I tried rm -i ~/.emscripten ./emscripten.sh emcc and I still got the same "no JSBackend" message, even after logging out and logging back in. Note that it says "Running sanity checks" every time the "no JSBackend" message appears. Probably emscripten.sh needs to be sourced by ~/.bash_profile or something, to make the environment variables persistent. Copying the config manually works, and it's easier.

cruelbob commented on 2014-03-20 04:49 (UTC)

@Svenstaro @EscapedNull To everyone. emscripten.sh includes: export EM_CONFIG="/usr/lib/emscripten/emscripten.config" On first run(in stall script) emscripten does sanity checks and creates sanity config files. So you should restart or relogin to your computer. After that emscripten works properly. Dont copy config file to your home directory. I will add this msg to install script.

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »