**** BEGIN LOGGING AT Thu May 08 02:59:58 2014
May 08 09:53:07 <awafaa> doko: what were the langs that you mentioned needed work for arm64?
May 08 09:54:53 <doko> awafaa, what do you mean?
May 08 09:55:39 <awafaa> doko: at Connect you mentioned some langs that needed work like mono & golang
May 08 09:55:45 <awafaa> doko: what were the others?
May 08 09:59:44 <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, ...)
May 08 10:01: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)
May 08 10:01:46 * ogra_ wonders why the world needs so many langs ... insane
May 08 10:04:19 <ogra_> "... want to solve a problem ? just invent a new programming language !!"
May 08 10:04:36 <doko> suihkulokki, maybe mention ghci in linaro-aarch64?
May 08 10:08:37 <suihkulokki> doko: it's there: https://bugs.launchpad.net/linaro-aarch64/+bug/1287505
May 08 10:10:10 <doko> suihkulokki, ghc is there. I thought you were talking about ghci?
May 08 10:13:57 <awafaa> suihkulokki: for nodejs it's probably going to be a matter of wait for a sync between the two projects
May 08 10:17:35 <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
May 08 10:19:40 <awafaa> suihkulokki: ok, I'll ferret around here and see what we can do
May 08 15:01:41 <awafaa> hmm
May 08 15:12:26 <awafaa> doko / suihkulokki looks like nodejs v0.10.x is stuck with libv8 3.14
May 08 15:13:18 <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
**** ENDING LOGGING AT Fri May 09 03:00:01 2014