[09:53] <awafaa> doko: what were the langs that you mentioned needed work for arm64?
[09:54] <doko> awafaa, what do you mean?
[09:55] <awafaa> doko: at Connect you mentioned some langs that needed work like mono & golang
[09:55] <awafaa> doko: what were the others?
[09:59] <suihkulokki> awafaa: ghci/mono are the biggest blockers. then we have a handful of esoteric languages (gcl, clisp, gauche, pascal, ...) and another handful of potentially rising language (rust, julia, ...)
[10:01] <suihkulokki> awafaa: and node.js needs a backport of libv8 (current aarch64 libv8 is head, but there is no abi and node.js needs 3.14 of libv8)
[10:01]  * ogra_ wonders why the world needs so many langs ... insane
[10:04] <ogra_> "... want to solve a problem ? just invent a new programming language !!"
[10:04] <doko> suihkulokki, maybe mention ghci in linaro-aarch64?
[10:08] <suihkulokki> doko: it's there: https://bugs.launchpad.net/linaro-aarch64/+bug/1287505
[10:10] <doko> suihkulokki, ghc is there. I thought you were talking about ghci?
[10:13] <awafaa> suihkulokki: for nodejs it's probably going to be a matter of wait for a sync between the two projects
[10:17] <suihkulokki> awafaa: it's not clear if that's going to happen anytime soon.. I don't think node.js upstream is working on it
[10:19] <awafaa> suihkulokki: ok, I'll ferret around here and see what we can do
[15:01] <awafaa> hmm
[15:12] <awafaa> doko / suihkulokki looks like nodejs v0.10.x is stuck with libv8 3.14
[15:13] <awafaa> the unstable 0.11.x is using 3.24 so hopefully v0.12.x will use 3.26+ of v8 which should resolve your issues