On 09/14/2016 02:55 PM, Jon Masters wrote:
Hi Jeremy, all,
Perhaps Jeremy can update us on the status, and then he and others
help drive this forward (someone should nominate themselves as the ring
leader too). I spoke with Cavium earlier today, and I know they'll be
keen to help. I know Qualcomm had expressed interest during our IRC
meetings in helping out. To that end, I'm copying at least those I know
so far who are interested here.
(this is the short version, even so, it got really long) <chuckle>
Right now, there are posted patches for 1.8.5, 17, 24 and 38 in the
fedora mozjs defects 1242326, 1375305, 1375547. The 17, 24 and 38
versions are fairly straightforward backports of the upstream mmap patch
which maintains the mozjs ABI. The dependent packages should not need to
be rebuilt. The 1.8.5 is based on an earlier patch and moves the tagging
bits higher in the word and will require a further work to go beyond
48-bit. That means that all js185 packages will need to be rebuilt
against it. Doing it this way helps to solve some problems with couchdb.
There are public patches to move polkit (fedora bug #1375368, polkit bug
#74592) to mozjs24
That removes the mozjs17 dependency in fedora.
There are also public patches for libproxy
, and pacrunner
get them off js185.
Further, there is another effort to move 0ad off mozjs31 to mozj38.
This leaves couchdb, elinks, erlang, freewrl/libEIA, mediatomb and
plowshare on js185.
At the moment, as far as mozjs is concerned I think its mostly working.
The remaining js185 projects should work, but should have further
attention. Erlang and freewrl are not trivial, and while it appears that
freewrl was moving towards duktape, it doesn't actually appear to be
working at the moment.
There is also a similar mess for lua, for which upstream version 2.1 has
patches, but those need investigation and backporting for nginx/etc on
fedora. Frankly, I'm trying to clear off my small piece of mozjs before
jumping into the lua bucket. If someone wants to grab that portion they
are welcome to it.
I can provide more detail about specifics in mozjs if anyone is
interested. My general goal right now is to consolidate on mozjs24 and
mozjs38. If once that happens I will consider it done. If anyone decides
to grab one of the projects let me know, I have partial (not yet 100%
functional) reworks for a couple of them. Further, it should be noted
that at least mozjs24 has regression failures on fedora/aarch64 at the
moment. Those failures are not dependent on 48-bit.
0ad-0:0.0.20-4.fc25.x86_64 (in progress to 38
(nothing at the moment, just in rawhide)