[Octave-bug-tracker] [bug #47606] mxe-octave installer for 64 bit seems not check 64 bit JRE but 32 bit JRE

[Philip Nienhuis]

Follow-up Comment #7, bug #47606 (project octave):

Answer 1:
32-bit Octave (based on comparing octave-4.0.1-cli.exe's time stamps in the
installer and in OCTAVE_HOME/bin I think the existing one from ftp.gnu.org):

>> strsplit (getenv ("PATH"), pathsep)
ans =
{
  [1,1] = C:\Programs\Octave\Octave32-4.0.1\bin
  [1,2] = C:\ProgramData\Oracle\Java\javapath
  [1,3] = C:\Program Files (x86)\Intel\iCLS Client\
  [1,4] = C:\Program Files\Intel\iCLS Client\
  [1,5] = C:\Windows\system32
  [1,6] = C:\Windows
  [1,7] = C:\Windows\System32\Wbem
  [1,8] = C:\Windows\System32\WindowsPowerShell\v1.0\
  [1,9] = C:\Program Files\Intel\Intel(R) Management Engine Components\DAL
  [1,10] = C:\Program Files\Intel\Intel(R) Management Engine Components\IPT
  [1,11] = C:\Program Files (x86)\Intel\Intel(R) Management Engine
Components\DAL
  [1,12] = C:\Program Files (x86)\Intel\Intel(R) Management Engine
Components\IPT
  [1,13] = C:\Program Files\TortoiseHg\
  [1,14] = C:\Program Files (x86)\Skype\Phone\
  [1,15] = C:\Programs\Octave\Octave32-4.0.1\bin
  [1,16] = C:\Programs\Octave\Octave32-4.0.1\notepad++
  [1,17] =
C:\Programs\Octave\Octave32-4.0.1\libexec\octave\4.0.1\site\exec\i686-w64-mingw32
  [1,18] =
C:\Programs\Octave\Octave32-4.0.1\libexec\octave\api-v50+\site\exec\i686-w64-mingw32
  [1,19] =
C:\Programs\Octave\Octave32-4.0.1\libexec\octave\site\exec\i686-w64-mingw32
  [1,20] =
C:\Programs\Octave\Octave32-4.0.1\libexec\octave\4.0.1\exec\i686-w64-mingw32
  [1,21] = C:\Programs\Octave\Octave32-4.0.1\bin
}


Octave-4.1.0+ (64bit) shows the same PATH with "Octave32-4.0.1" replaced by
"Octave-4.1.0+_w64VEtst"

============================================
Answer 2:
Using the io package's scripts:

octave-4.0.1 32-bit does this:

>> chk_spreadsheet_support ('', 3)
:
:
1. Checking Octave's Java support... OK.
2. Checking Java dependencies...
  Checking Java JRE presence.... OK, found one.
  Java seems to work OK.
  Java (version 1.8.0_77) seems OK.
  Maximum JVM memory:   248 MiB; should better be at least 400 MB!
    Hint: adapt setting -Xmx in file 'java.opts' (supposed to be here:)
   
C:\Programs\Octave\Octave32-4.0.1\share\octave\packages\java-<version>\java.opts


and

>> io_xls_testscript ("uno")
:
:
Oops, Octave hit an error.
Maybe you have 64-bit Libre/OpenOffice installed?
32-bit Octave requires 32-bit L.O. / OOo.


The LibreOffice UNO-Java bridge (belonging to LO, not stuff in the io
package!) contains several compiled procedures so LO just doesn't work if
Octave has a different "bit width", even if the io package finds the LO java
parts and added them to the javaclasspath.
Octave can only find out if it "matches" by trying.

Now, with 64-bit Octave-4.1.0+

>> io_xls_testscript ("uno")

Testing .xls interface UNO using file io-test.xls...
:
:
10. Cleaning up..... OK
ans =
{
  [1,1] = UNO
  [1,2] = +
:


(so runs fine) and

>> chk_spreadsheet_support ('', 3)
:
:
1. Checking Octave's Java support... OK.
2. Checking Java dependencies...
  Checking Java JRE presence.... OK, found one.
  Java seems to work OK.
  Java (version 1.8.0_77) seems OK.
  Maximum JVM memory:  1812 MiB; sufficient.
:


so each version (32bit and 64bit) of Octave picks up the matching Java
version.


One question now is: did JWE build the 32-bit installer with a 32-bit or a
64-bit JDK on his Linux box?

AFAICS 32-bit or 64-bit Octave doesn't make a difference as regards 32-bit or
64-bit Java JRE when just invoking methods from ready-baked Java class libs .
jar files) in the javaclasspath. 
Admittedly a 32-bit Java JRE implies a smaller JVM heap than that of a 64-bit
Java JRE, as shown above in the verbatim blocks.


    _______________________________________________________

Reply to this item at:

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

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