octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #53510] [octave forge] (io) wrong java check


From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #53510] [octave forge] (io) wrong java check
Date: Sat, 31 Mar 2018 09:00:38 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0

Follow-up Comment #14, bug #53510 (project octave):

I installed Java 1.5 64bit and tried to use it with a recent Octave 4.5.0+ on
Windows. Even after fixing the registry key value (wrong folder for Java
64bit), Octave is still unable to load it correctly anyway (as expected):

octave:1> version -java
ans = no Java available
octave:2> javaclasspath
error: unable to start Java VM in C:\Program
Files\Java\jre1.5.0_22\bin\server\jvm.dll
error: called from
    javaclasspath at line 64 column 16


So the version check isn't really needed for the upcoming Octave versions.
However, afaics the minimum Java version was still 1.2 for the 4.2s.
I don't know how widespread those "antique" versions of JRE still are. But for
current releases of Octave, this check should probably be kept in (and adapted
for the new version numbering scheme of the JRE).
The attached patch should work with the old and new numbering schemes.

(file #43742)
    _______________________________________________________

Additional Item Attachment:

File name: bug53510_java9+_version.patch  Size:1 KB


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?53510>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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