Re: Octave 3.8.2 IO corrupting and locking files after creation

[adt992]

Moreover I've tried uninstalling and reinstalling Java (i'm pulling out all
of the stops now):

>> setenv("JAVA_HOME", "C:/Program Files/Java/jdk1.8.0_31")
>> pkg install -auto -forge -verbose java
mkdir (C:\Users\PROJEC~1\AppData\Local\Temp\oct-53)
untar (C:\Octave\Octave-3.8.2\java-1.2.9.tar.gz,
C:\Users\PROJEC~1\AppData\Local\Temp\oct
-53)
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.exe
checking for suffix of executables... .exe
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for mkoctfile... C:/Octave/Octave-3.8.2/bin/mkoctfile-3.8.2.exe
retrieving compile and link flags from
C:/Octave/Octave-3.8.2/bin/mkoctfile-3.8.2.exe
checking for F77_FUNC... yes
checking for octave... C:/Octave/Octave-3.8.2/bin/octave-3.8.2.exe
checking for OCTAVE_VERSION in Octave... 3.8.2
checking for octave_config_info('canonical_host_type') in Octave...
i686-w64-mingw32
checking for octave_config_info('SHLEXT') in Octave... dll
checking whether ln -s works... no, using cp -p
checking for ranlib... ranlib
checking for strip... strip
checking for java... /c/Program Files/Java/jdk1.8.0_31/bin/java
checking for javac... /c/Program Files/Java/jdk1.8.0_31/bin/javac
checking for jar... /c/Program Files/Java/jdk1.8.0_31/bin/jar
checking for Java version...
./configure: line 3257: test: too many arguments
configure: WARNING: this package requires at least Java-1.5
configure: creating ./config.status
config.status: creating Makeconf

  "$prefix" is C:/Octave/Octave-3.8.2/share/octave/packages/java-1.2.9
  "$exec_prefix" is ${prefix}

octave commands will install into the following directories:
   m-files:  
/home/benutzer/mxe-octave/usr/i686-w64-mingw32/share/octave/3.8.2/site/m/oc
tave-forge
   oct-files:
/home/benutzer/mxe-octave/usr/i686-w64-mingw32/lib/octave/3.8.2/site/oct/i6
86-w64-mingw32/octave-forge
   binaries: 
/home/benutzer/mxe-octave/usr/i686-w64-mingw32/libexec/octave/3.8.2/site/ex
ec/i686-w64-mingw32
alternatives:
   m-files:  
/home/benutzer/mxe-octave/usr/i686-w64-mingw32/share/octave/3.8.2/site/octa
ve-forge-alternatives/m
   oct-files:
/home/benutzer/mxe-octave/usr/i686-w64-mingw32/lib/octave/3.8.2/site/octave
-forge-alternatives/oct/i686-w64-mingw32

shell commands will install into the following directories:
   binaries:  ${exec_prefix}/bin
   man pages: ${datarootdir}/man
   libraries: ${exec_prefix}/lib
   headers:   ${prefix}/include

octave-forge is configured with
   octave:      C:/Octave/Octave-3.8.2/bin/octave-3.8.2.exe (version 3.8.2)
   mkoctfile:   C:/Octave/Octave-3.8.2/bin/mkoctfile-3.8.2.exe for Octave 2
  * java:        Java Development Kit not found*

find . -name NOINSTALL -print    # shows which toolboxes won't be installed

make: Entering directory `/tmp/oct-53/java/src'
*Java support not compiled*
make: Leaving directory `/tmp/oct-53/java/src'

I'm guessing the JDK isn't being properly pointed to? 



--
View this message in context: 
http://octave.1599824.n4.nabble.com/Octave-3-8-2-IO-corrupting-and-locking-files-after-creation-tp4669498p4669500.html
Sent from the Octave - General mailing list archive at Nabble.com.