|
On 11/27/2013 02:14 PM, Michael
Goffioul wrote:
11/27/13
This problem is still very much present for me. I have done
nothing
special either on the Linux side or the Windows side. On the
Linux side, I
have Java installed and when I run the MXE cross-build it
succeeds. On the
Windows side I have Windows XP and I just downloaded the
standard package
from Oracle which gives me Java 7 Update 45 (probably just a
JRE). I get a
segfault every time when using any Java command.
It seems to me that we may need to be more careful in configure.ac about
distinguishing between $build_os and $host_os. We require a
Java
environment on the $build_os in order to produce .class and .jar
files that
are a part of Octave. We require a jvm on the $host_os in order
to run
things, but we can't test that in a cross-compiling situation
and should
just assume "yes".
For any Java experts, is it possible that the problem is
architecture
related (32-bit vs. 64-bit). My build platform is x86_64
Linux, but
Windows XP Home Edition is 32 bit.
See this link [1]. For plain Java, it shouldn't be a problem.
Java is "compile-once-run-everywhere". However, there might be
problems if the java integration part of octave was compiled
with 64 bits header files.
Michael.
I've filed a bug report on this
(https://savannah.gnu.org/bugs/index.php?40727). I used gdb and the
backtrace is actually pointing to Octave code. It still could be a
problem with the JNI interface, but I'm growing less certain of
that. In any case I installed a 32-bit JDK on the Linux side and am
attempting a full re-compile to see if that helps any.
--Rik
|