[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: Wed, 8 Aug 2018 05:44:44 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0

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

@Mike comment #24:
_ if bin/client is found, it should prefer that to bin/server_
At one time I had a 32-bit and a 64 bit Octave plus 32-bit and 64-bit Java
installed, and *AFAIR* both Octaves accessed the proper (bitwidth) Java
installation w/o any issue or JAVA_HOME environment settings (the latter don't
exist on Windows by default).
Hopefully linking preferrably to ./bin/client doesn't break that (..)
(IIRC some bitwidth/Java discussion has happened a few years back, also
related to ./client vs. ./server, there may be some clues in that discussion)

And that's not just Octave; I have 32-bit and 64-bit Java installed as I have
a mixture of 32-bit and 64-bit SW that uses Java like GIS clients,
LibreOffice, Freemat at one time,etc. AFAICS all that SW automagically links
to the "proper" Java installation.
(BTW not that I'm a Java fan, but mentioned SW Just Works and fulfills our


Reply to this item at:


  Message sent via Savannah

reply via email to

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