Arch Linux User Repository

Hi, in PKGBUILD you should quote variables that may contain spaces, in particular ${srcdir} and ${pkgdir} on lines 30, 37, 39, 48-49, 53, 61, 74-76, 78-81 and 91-94. Otherwise the build fails when there are directories that contain spaces.

See https://wiki.archlinux.org/index.php/Arch_packaging_standards.

Have a nice day.

Thanks for the hint, done.

You could copy the stable emscripten.sh:
https://git.archlinux.org/svntogit/community.git/tree/trunk/emscripten.sh?h=packages/emscripten

Looks like `/etc/profile.d/emscripten.sh` sets $EMSCRIPTEN_FASTCOMP to `/opt/emscripten-fastcomp` instead of `/usr/lib/emscripten-fastcomp`, leading to "No such file" errors.

Well I definitely had such problems, but right now it works fine, so I removed the option for the time being.

Well I never had any problems building this before parallel builds were inactivated. What are the reasons you did this?

I had reasons to turn off parallel builds with options=('!makeflags').

The option MAKEFLAGS from makepkg.conf is ignored, this package takes forever to build on multicore processors because it only compiles one file at a time.

Doesn't this need clang as makedeps?

Problem was in my makepkg config.
I edited /etc/makepkg.conf and removed -fvar-tracking-assigments from
#DEBUG_CFLAGS="-g -fvar-tracking-assignments"
#DEBUG_CXXFLAGS="-g -fvar-tracking-assignments"

I'm getting
"clang: error: unknown argument: '-fvar-tracking-assignments'"

I think, not upstream but me was the culprit. I borrowd some ideas from the stable PKGBUILD which hopefully fix this.

Getting this:

CRITICAL root: Cannot find /opt/emscripten-fastcomp/clang++, check the paths in ~/.emscripten

Perhaps some things have been changing upstream?

@Svenstaro et al.: done[1]. I did a few things a bit different than this package, though. However, as I just recently started using emscipten, there might be things to improve. Most tests of the included test suite run fine so far.

[1]: https://aur.archlinux.org/packages/emscripten/

fixed

haawda, I've run into the same problem as lugubrious. It turns out that the current PKGBUILD doesn't compile emscripten-fastcomp-clang even though it's required to properly run emscripten. I've made a patch that fixes that (in addition to fixing `emcc --help` etc):

https://gist.github.com/Idorobots/ad4d749074f1d3715019

Somebody make an emscripten (no git) package from the releases so I can eventually stick it into [community]! :P

lugubrious, I cannot reproduce your error.

I've figured out what's wrong - I need to run it with EMCC_FAST_COMPILER=0
Is there any way to run it with the fast compiler or do I need more tools?

Also as an amendment, I had to remove then reinstall clang to get it to correctly copy over the clang files to /opt/emscripten-fasctomp/

I'm getting this error

error: unknown target triple 'asmjs-unknown-emscripten', please use -triple or -arch
ERROR root: compiler frontend failed to generate LLVM bitcode, halting

Any ideas? I'm a bit clueless. thanks

After the current build I was getting this error

WARNING root: Could not verify LLVM version: [Errno 2] No such file or directory
INFO root: (Emscripten: Running sanity checks)
CRITICAL root: Cannot find /opt/emscripten-fastcomp/clang++, check the paths in ~/.emscripten

The fix was symbolically linking them over

$ sudo cp -s /usr/bin/clang* /opt/emscripten-fastcomp/

build failed when using clang to compile, so I explicitely set CC=gcc now.

Well, either it fixed itself or running makepkg twice fixes it.

fatal: Cannot update paths and switch to branch 'makepkg' at the same time.
Did you intend to checkout 'origin/incoming' which can not be resolved as commit?
==> ERROR: Failure while creating working copy of emscripten git repo
Aborting...

I'm not really sure what the problem is, I've tried to massage the git commands manually a bit, but it still seems to be failing.

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!

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

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.

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.

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. :)

please add cmake as build dependency

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

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.

@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.

@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.

@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 to install script.

Also, really really don't do thing with the current user, please. That includes running a script that will generate something for the current user. This only works once. Please don't do that. Write a message there instead, informing the user.

@cruelbob: The issue is illustrated right here by EscapedNull.

@Svenstaro That worked! Thanks! For the next person who runs into this:
cp -i emscripten.config ~/.emscripten

@cruelbob Mad props on upgrading to fastcomp. I guess this means no more compile-time coffee breaks :)

You are seeing my issue probably. Manually copy proper config file in place.

When I run emcc/em++ I get:
CRITICAL root: fastcomp in use, but LLVM has not been built with the JavaScript backend as a target, llc reports [...]

Has anyone else run into this?

Svenstaro, What is wrong in install script for you?

The install script didn't work reliably for me. I had to copy the config by hand to make it work. When I ran emcc, it told me that it was actually running for the first time. Anyway, it works quite well, so thanks for the PKGBUILD.

I switched emscripten backend in this packet to llvm-backend(c++) version. For details see url from my previous comment.

I switched backend to llvm-backend(c++). See url from previous comment.

https://github.com/kripken/emscripten/wiki/LLVM-Backend

benob, thanks for the reply. I didn't realize emscripten itself was written in Javascript. It makes sense now. Looking forward to trying the C++ backend when/if it becomes available.

Emscripten needs a js interpreter because the compiler (from LLVM to js) itself is written in javascript. A new c++ backend is being written but I don't know the current status.

Why is Node.js a dependency? You can use emscripten to compile to browser Javascript just the same.

ok, it is up-to-date now

Disowning package as I don't use it anymore

may be you can add enviroment variable to system?

emscripten.sh to /etc/profile.d

#!/bin/bash

export EMSCRIPTEN=/usr/lib/emscripten

that branch isn’t up-to-date, so it’s hardly “emscripten-git” anymore.

Updated source, thanks.

note to anyone wondering:
source=('git://github.com/kripken/emscripten.git#branch=llvmsvn'

Emscripten from master branch now doesnt work with clang 3.3 from pacman. I think you can see llvmsvn branch of emscripten.

I applied the patch, thanks.

Please update your PKGBUILD to meet the new https://wiki.archlinux.org/index.php/Arch_CVS/SVN_PKGBUILD_guidelines

I have already made a patch: http://pastebin.com/DtdZ8Z9D

P.S: And with the new CVS PKGBUILD way, it is no longer needed to build in a separate emscripten-build directory, because makepkg will automatically clone a backup for you.