Re: Java package install seems to be ok, but is NOT working.

[PhilipNienhuis]

Werner wrote
> Hell List,
> 
> Sergei is right at all. I have had the same problems and my assumption was
> exactly like Sergei's
> So I decided to make a new java installation (the current installations
> was in any event old - jdk1.6.0_31)
> My system is windows 7 and so the installation was in c:\Program
> Files\Java ... Keep in mind the
> whitespace in path. With this settings you get an error, when you install
> java with
> pkg install -verbose  java-1.2.9.tar.gz. You have carefully check the
> output, there is the message that
> the make file can't found c:\Program Files\Java ... So I install the new
> jdk (jdk1.7.0_25), but in the
> installation process I "correct" the path from c:\Program Files to
> c:\ProgramFiles (it's a little bit strange
> for a windows 7 system). Therefor my output from  strsplit
> (getenv("PATH"), pathsep)  contains now
> [1,7] = c:\ProgramFiles\Java\jdk1.7.0_25\bin\ and that was what I wanted
> -> no whitespace in the path.
> When you now install java with pkg, then all is correct.
> 
> So long Werner

Another issue I hit is that on my 64-bit Win7 box at work, Octave (32-bit)
doesn't like the 64-bit JavaJDK;  not even with the trick of copying the
./server/ directory to the ./client/ directory (the Java package expects
jvm.dll to be in ....../client)

I explicitly had to wipe the 64-bit JDK and install a 32-bit JDK. It doesn't
matter that the latter is somewhere in C:\Program Files (X86)\  (enough
spaces, isn't it?).

My experience on Windows is that it is vital for Octave itself to be
installed in a path w/o spaces. But support SW (Java, Ghostscript, etc) in
e.g., C:\Program Files\ is often recognized properly by Octave. Mind you:
YMMV.

Philip




--
View this message in context: 
http://octave.1599824.n4.nabble.com/Java-package-install-seems-to-be-ok-but-is-NOT-working-tp4648763p4657179.html
Sent from the Octave - General mailing list archive at Nabble.com.