[Octave-bug-tracker] [bug #58312] [octave forge] (io) Defer Java detection until a function is called

[Philip Nienhuis]

Follow-up Comment #5, bug #58312 (project octave):

Mike's "lightweigt" argument made me think a bit more.

The io pkg initialization merely does this:
1. Check if Octave was built with Java support at all
2. Call Java as a shell command (= effectively outside Octave) to check
minimum Java version
3. Try to add Java class libs to the javaclasspath.
If any step gives negative results the rest is skipped.

Formerly, step 1 comprised directly querying the value of one of Octave's
internal build flags; IMO as lightweight as can be.
Since bug #47480 this check is done by calling javachk.m. That function
somehow fiddles with the Java JVM; whatever it does, it's apparently not so
lightweight as just querying some Octave value.

@Christian:
If you start Octave and as first command enter the command:
javachk ("jvm")

do you get that offending warning?
And the same for:
javaclasspath

If you get the warning only with javachk.m, I think we indeed may need to
revisit bug #47480.


As to my previous comment #4, I wrote:
* __it only occurs with a specific dependency on a specific OS, and__

but as I never hit this warning on my Mageia 7 Linux distro (I've only heard
it from other users on other distros) it had better read:

* __it only occurs with a specific dependency on specific distros of a
specific OS, and__

BTW, what OpenJDK version do you run?
Mine is:

[philip@deskprn ~]$ java -version
openjdk version "1.8.0_252"
OpenJDK Runtime Environment (build 1.8.0_252-b09)
OpenJDK 64-Bit Server VM (build 25.252-b09, mixed mode)



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?58312>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/