[Top][All Lists]

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

[Octave-bug-tracker] [bug #40111] support runtime selection of Java with

From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #40111] support runtime selection of Java with JAVA_HOME on Linux and Unix systems
Date: Tue, 7 Aug 2018 15:35:00 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48

Follow-up Comment #23, bug #40111 (project octave):

I don't know if it's related to comment #22,bt on my Win7 PC octave doesn't
find Java anymore.

>> javaclasspath
error: javaMethod: could not find library or dependencies: linked in or loaded
error: called from
    javaclasspath at line 64 column 16

>> system ("java -version")
java version "10.0.1" 2018-04-17
Java(TM) SE Runtime Environment 18.3 (build 10.0.1+10)
Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.1+10, mixed mode)
ans = 0

Then, looking at the cset
http://hg.savannah.gnu.org/hgweb/octave/rev/3ddd74bd7b11 I see in L1.13:
+  std::string subdirs[] = {"bin/client", "bin/server"};

As at least on Windows it is perfectly possible to have both 32bit and 64bit
Java installed, where the 32bit jvm.dll lives in
C:/Program files (X86)/java/jre<version>/bin/client
and the 64bit one in 
C:/Program Files/java/jre<version>/bin/server
I wonder if the various versions won't be mixed up and Java detection would
fail. Shouldn't there be a sort of preselection based on whether Octave is 32
or 64 bit?


Reply to this item at:


  Message sent via Savannah

reply via email to

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