[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to build MXE Octave-4.0.0 64 bits with Java support?

From: Philip Nienhuis
Subject: Re: How to build MXE Octave-4.0.0 64 bits with Java support?
Date: Sun, 7 Jun 2015 14:08:27 -0700 (PDT)

Rafael wrote
> Hi,
> I tried to build Octave-4.0.0 using this instructions:
> http://wiki.octave.org/Windows_Installer
> The build was created on a *Debian 8* system using *--enable-64* flag and

While it doesn't matter for your actual question: do you really need 64-bit
indexing?  If you just build with --enable-windows-64, you'll get a 64-bit
Octave with 32-bit indexing that only runs on Win64 and can access double
arrays of 16 GB / complex 32 GB / single & int32 8 GB.  Enough for most

> it works fine on *Windows*, but it looks like the Java interface was not
> built for some reason. If I try to run any Java command, I get something
> like this:
>>> javaclasspath
> error: javaMethod: Octave was not compiled with Java interface
> error: called from
>     javaclasspath at line 64 column 16

Apparently on your Debian system, Java wasn't picked up by the mxe-octave
build system.
Do you have a 64-bit JDK on your Debian system?

mxe-octave should be able to detect it; or rather, the Octave configure
system should, when it is invoked by the mxe build process.

First step:
In mxe-octave (on Debian), look in the log/ directory for "octave", it's a
symlink to the configure and build log for Octave. Look in there to find out
if Octave's configure found the JDK. You can search/grep for "Java home: "
and "Java JVM path:"

Second step:
After having verified that you indeed have a 64-bit JDK installed on Debian,
manually add the required info in the relevant configure stanza in
mxe-octave/src/octave.mk (or .../stable-octave.mk, whatever is mentioned in
the top of mxe-octave/Makefile).  To find out what you need, run
./configure --help in an Octave build directory on Linux, it is something
like --with-java-includedir= and --with-java-libdir=. I'm on Windows now so
I can't check.  
Oh, and IIRC it may be that you'd need to omit the include dir itself in the
path, so:
--with-java-includedir=/full/path/to/java/jdk and omit the final /include
(!)  -  just experiment a bit.


View this message in context: 
Sent from the Octave - Maintainers mailing list archive at Nabble.com.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]