Issue2718
Created on 2018-12-08.04:03:42 by tpearson-raptor, last changed 2019-01-08.22:54:30 by jeff.allen.
Messages | |||
---|---|---|---|
msg12200 (view) | Author: Timothy Pearson (tpearson-raptor) | Date: 2018-12-08.04:03:41 | |
Since the Jython standalone JAR includes platform-specific libraries, it should be built to include support for the ppc64el platform. We have been having to rebuild the sources into a standalone JAR on our POWER boxes, which breaks downstream consumers that assume the standalone official Jython JAR includes the needed platform support. |
|||
msg12201 (view) | Author: Timothy Pearson (tpearson-raptor) | Date: 2018-12-08.04:05:14 | |
Notably this breaks Zimbra unless the standalone JAR built on our POWER systems is substituted for the official JAR that Zimbra installs. On 12/07/2018 10:03 PM, Timothy Pearson wrote: > > New submission from Timothy Pearson <tpearson@raptorengineering.com>: > > Since the Jython standalone JAR includes platform-specific libraries, it should be built to include support for the ppc64el platform. We have been having to rebuild the sources into a standalone JAR on our POWER boxes, which breaks downstream consumers that assume the standalone official Jython JAR includes the needed platform support. > > ---------- > components: Library > messages: 12200 > nosy: tpearson-raptor > severity: major > status: open > title: Jython not built for IBM Linux on POWER (ppc64el) systems > versions: Jython 2.7 > > _______________________________________ > Jython tracker <report@bugs.jython.org> > <http://bugs.jython.org/issue2718> > _______________________________________ |
|||
msg12202 (view) | Author: Jeff Allen (jeff.allen) | Date: 2018-12-11.23:21:18 | |
Is this simply a case of adding a JFFI stub JAR and including it around here to the build? https://hg.python.org/jython/file/tip/build.xml#l591 As the build file indicates, we get these from https://github.com/jnr/jffi/tree/master/archive . We cite ppc64le, but there doesn't seem to be a JAR for ppc64el in the jffi distribution. From what I have read, these two names designate the same architecture but there has been confusion over the preferred name (e.g. what uname should return, or os.arch equal). I think this may be for jnr/jffi to deal with. Selection of the right stub happens here: https://github.com/jnr/jffi/blob/master/src/main/java/com/kenai/jffi/internal/StubLoader.java#L179 I may be barking up the wrong tree, of course. If jnr/jffi can't help and there's a work-around in Jython's scope, we would consider doing so. What is it you do to create a standalone JAR that works for you? |
|||
msg12204 (view) | Author: Jeff Allen (jeff.allen) | Date: 2018-12-12.06:47:31 | |
Further research. Support in Jython first appears here: https://hg.python.org/jython/rev/f6b3ddbc1df8 on the eve of the release of 2.7.1, so if you're using 2.7.1 it ought to work but with 2.7.0 it won't. The 2.7.1 JAR is hard to find (never understood why) and I'm also conscious of a bug that may discourage use in high-performance multiprocessor applications. In relation to this being a jnr/jffi problem, this is relevant: https://github.com/jnr/jffi/pull/11, and the tangle of PRs and issues you can reach from it. Collectively, it looks like jnr/jffi support works. If we assume jnr/jffi actually works, it may simply be that clients are using the 2.7.0 JAR. |
|||
msg12310 (view) | Author: Jeff Allen (jeff.allen) | Date: 2019-01-08.22:54:30 | |
Nothing further from OP to respond to our questions, so I assume we answered it adequately. |
History | |||
---|---|---|---|
Date | User | Action | Args |
2019-01-08 22:54:30 | jeff.allen | set | status: open -> closed resolution: fixed messages: + msg12310 |
2018-12-12 06:47:33 | jeff.allen | set | messages: + msg12204 |
2018-12-11 23:21:20 | jeff.allen | set | priority: normal nosy: + jeff.allen messages: + msg12202 |
2018-12-08 04:05:15 | tpearson-raptor | set | messages: + msg12201 |
2018-12-08 04:03:42 | tpearson-raptor | create |
Supported by Python Software Foundation,
Powered by Roundup