Errors installing java-1.2.6 package in octave-MingW-3.2.x

[Philip Nienhuis]

Hi,

Trying to install the java-1.2.6 package in Octave-MingW turns into a
lengthy affair on my WinXP SP3 box.

I'm running octave-3.2.0 from the
Octave-3.2.0_i686-pc-mingw32_gcc-4.3.0_setup.exe file on octave.sf.net.

I installed the Java development package jdk-6u16-windows-i586.exe into
C:\Programs\Java\jdk1.6.0_16
The .\include directories thus live in
C:\Programs\Java\jdk1.6.0_16\include  and
C:\Programs\Java\jdk1.6.0_16\include\win32

I've added these dirs to the environment variable JAVA_INCS:

========= CMD window =============
C:\Home\Philip>echo %JAVA_INCS%
-I:C:/Programs/java/jdk1.6.0_16/include
-I:C:/Programs/java/jdk1.6.0_16/include/win32
========== /CMD window ===========

& to be sure, also set the variable JAVA_INCS in Octave:

Octave-3.2.0: 5 > JAVA_INCS
JAVA_INCS = -I:C:/Programs/java/jdk1.6.0_16/include
-I:C:/Programs/java/jdk1.6.0_16/include/win32
Octave-3.2.0: 6 >

Trying "pkg install java-1.2.6.tar.gz" then gives:

Octave-3.2.0: 5 > pkg install java-1.2.6.tar.gz
       0 [main] sh 4528 open_stackdumpfile: Dumping stack trace to
sh.exe.stackdump
./config.status: line 72:  5636 Segmentation fault      (core dumped) (
test "X`printf %s $as_echo`"
  = "X$as_echo" ) 2>/dev/null
       0 [main] sh 6104 open_stackdumpfile: Dumping stack trace to
sh.exe.stackdump
./config.status: line 81:  5144 Segmentation fault      (core dumped) (
PATH='/bin;/bin'; FPATH=$PAT
H; sh -c : ) >/dev/null 2>&1
./config.status: line 88:  5472 Segmentation fault      (core dumped) (
( MAIL=60; unset MAIL ) || e
xit ) >/dev/null 2>&1
       0 [main] sh 5344 open_stackdumpfile: Dumping stack trace to
sh.exe.stackdump
       0 [main] sh 5864 open_stackdumpfile: Dumping stack trace to
sh.exe.stackdump
: error: cannot create .lineno; rerun with a POSIX shell
the configure script returned the following error: checking for gcc...
mingw32-gcc-4.3.0-dw2
checking for C compiler default output file name... a.exe
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... .exe
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether mingw32-gcc-4.3.0-dw2 accepts -g... yes
checking for mingw32-gcc-4.3.0-dw2 option to accept ISO C89... none needed
checking for mkoctfile... mkoctfile
retrieving compile and link flags from mkoctfile
checking for F77_FUNC... yes
checking for octave... octave
checking for OCTAVE_VERSION in Octave... 3.2.0
checking for octave_config_info('canonical_host_type') in Octave...
i686-pc-mingw32
checking for octave_config_info('SHLEXT') in Octave... dll
checking whether ln -s works... yes
checking for ranlib... ranlib
checking for strip... strip
checking for java... java
checking for javac... javac
checking for jar... jar
checking for Java version... 1.6.0_16
configure: creating ./config.status
error: called from `pkg>configure_make' in file
C:\Programs\Octave\3.2.0_gcc-4.3.0\share\octave\3.2.
0\m\pkg\pkg.m near line 1242, column 2
error: called from:
error:
C:\Programs\Octave\3.2.0_gcc-4.3.0\share\octave\3.2.0\m\pkg\pkg.m at
line 714, column 5
error:
C:\Programs\Octave\3.2.0_gcc-4.3.0\share\octave\3.2.0\m\pkg\pkg.m at
line 287, column 7
Octave-3.2.0: 5 >

This also happens with the octave-MingW-3.2.2 binary Windows packages
from octave-forge on another box (WinXP SP2).

I think the core dumps reported first on top actually result from the
errors lower in the messages list; I suppose they come from distinct
processes writing to output?

My system:
Windows XP SP3 English; Core Duo 2.5 Ghz 2GB RAM % several gigs of free
disk space.

Is the java-1.2.6 package broken for MingW? Or am I doing something
wrong here?
How can I dig further?

Thanks,

Philip

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev

[Michael Goffioul-2]

There have been some fixes committed recently to support
MinGW better. So the first thing would be to grab sources
from the SVN repository (the changed files are src/Makefile,
src/configure.base and src/__java__.cc). Then you have to
define JAVA_HOME variable as C:\Programs\Java\jdk1.6.0_16
and it should (hopefully) work out of the box.

Michael.


On Tue, Sep 22, 2009 at 6:09 PM, Philip Nienhuis <pr.nienhuis@...> wrote:

> Hi,
>
> Trying to install the java-1.2.6 package in Octave-MingW turns into a
> lengthy affair on my WinXP SP3 box.
>
> I'm running octave-3.2.0 from the
> Octave-3.2.0_i686-pc-mingw32_gcc-4.3.0_setup.exe file on octave.sf.net.
>
> I installed the Java development package jdk-6u16-windows-i586.exe into
> C:\Programs\Java\jdk1.6.0_16
> The .\include directories thus live in
> C:\Programs\Java\jdk1.6.0_16\include  and
> C:\Programs\Java\jdk1.6.0_16\include\win32
>
> I've added these dirs to the environment variable JAVA_INCS:
>
> ========= CMD window =============
> C:\Home\Philip>echo %JAVA_INCS%
> -I:C:/Programs/java/jdk1.6.0_16/include
> -I:C:/Programs/java/jdk1.6.0_16/include/win32
> ========== /CMD window ===========
>
> & to be sure, also set the variable JAVA_INCS in Octave:
>
> Octave-3.2.0: 5 > JAVA_INCS
> JAVA_INCS = -I:C:/Programs/java/jdk1.6.0_16/include
> -I:C:/Programs/java/jdk1.6.0_16/include/win32
> Octave-3.2.0: 6 >
>
> Trying "pkg install java-1.2.6.tar.gz" then gives:
>
> Octave-3.2.0: 5 > pkg install java-1.2.6.tar.gz
>       0 [main] sh 4528 open_stackdumpfile: Dumping stack trace to
> sh.exe.stackdump
> ./config.status: line 72:  5636 Segmentation fault      (core dumped) (
> test "X`printf %s $as_echo`"
>  = "X$as_echo" ) 2>/dev/null
>       0 [main] sh 6104 open_stackdumpfile: Dumping stack trace to
> sh.exe.stackdump
> ./config.status: line 81:  5144 Segmentation fault      (core dumped) (
> PATH='/bin;/bin'; FPATH=$PAT
> H; sh -c : ) >/dev/null 2>&1
> ./config.status: line 88:  5472 Segmentation fault      (core dumped) (
> ( MAIL=60; unset MAIL ) || e
> xit ) >/dev/null 2>&1
>       0 [main] sh 5344 open_stackdumpfile: Dumping stack trace to
> sh.exe.stackdump
>       0 [main] sh 5864 open_stackdumpfile: Dumping stack trace to
> sh.exe.stackdump
> : error: cannot create .lineno; rerun with a POSIX shell
> the configure script returned the following error: checking for gcc...
> mingw32-gcc-4.3.0-dw2
> checking for C compiler default output file name... a.exe
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables... .exe
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether mingw32-gcc-4.3.0-dw2 accepts -g... yes
> checking for mingw32-gcc-4.3.0-dw2 option to accept ISO C89... none needed
> checking for mkoctfile... mkoctfile
> retrieving compile and link flags from mkoctfile
> checking for F77_FUNC... yes
> checking for octave... octave
> checking for OCTAVE_VERSION in Octave... 3.2.0
> checking for octave_config_info('canonical_host_type') in Octave...
> i686-pc-mingw32
> checking for octave_config_info('SHLEXT') in Octave... dll
> checking whether ln -s works... yes
> checking for ranlib... ranlib
> checking for strip... strip
> checking for java... java
> checking for javac... javac
> checking for jar... jar
> checking for Java version... 1.6.0_16
> configure: creating ./config.status
> error: called from `pkg>configure_make' in file
> C:\Programs\Octave\3.2.0_gcc-4.3.0\share\octave\3.2.
> 0\m\pkg\pkg.m near line 1242, column 2
> error: called from:
> error:
> C:\Programs\Octave\3.2.0_gcc-4.3.0\share\octave\3.2.0\m\pkg\pkg.m at
> line 714, column 5
> error:
> C:\Programs\Octave\3.2.0_gcc-4.3.0\share\octave\3.2.0\m\pkg\pkg.m at
> line 287, column 7
> Octave-3.2.0: 5 >
>
> This also happens with the octave-MingW-3.2.2 binary Windows packages
> from octave-forge on another box (WinXP SP2).
>
> I think the core dumps reported first on top actually result from the
> errors lower in the messages list; I suppose they come from distinct
> processes writing to output?
>
> My system:
> Windows XP SP3 English; Core Duo 2.5 Ghz 2GB RAM % several gigs of free
> disk space.
>
> Is the java-1.2.6 package broken for MingW? Or am I doing something
> wrong here?
> How can I dig further?
>
> Thanks,
>
> Philip
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Octave-dev mailing list
> Octave-dev@...
> https://lists.sourceforge.net/lists/listinfo/octave-dev
>

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev

[Philip Nienhuis]

Hi Michael,

Michael Goffioul wrote:
> There have been some fixes committed recently to support
> MinGW better. So the first thing would be to grab sources
> from the SVN repository (the changed files are src/Makefile,
> src/configure.base and src/__java__.cc). Then you have to
> define JAVA_HOME variable as C:\Programs\Java\jdk1.6.0_16
> and it should (hopefully) work out of the box.
>

Thank you very much (also for the updated files sent in another e-mail).

It did work out-of-the-box - that is: sort of; no errors but a lot of
warnings. Echoed below, perhaps it's useful for the developers:

=======================<screen messages>===============================
Octave-3.2.0: 4 > pkg install java-1.2.6.tar.gz
__java__.cc: In function 'void initialize_jvm()':
__java__.cc:385: warning: deprecated conversion from string constant to
'char*'
__java__.cc: In function 'octave_value get_array_elements(JNIEnv*,
_jobject*, const octave_value_lis
t&)':
__java__.cc:612: warning: deprecated conversion from string constant to
'char*'
__java__.cc: In function 'octave_value set_array_elements(JNIEnv*,
_jobject*, const octave_value_lis
t&, const octave_value&)':
__java__.cc:634: warning: deprecated conversion from string constant to
'char*'
__java__.cc: In function 'octave_value box(JNIEnv*, _jobject*, _jclass*)':
__java__.cc:783: warning: deprecated conversion from string constant to
'char*'
__java__.cc:848: warning: deprecated conversion from string constant to
'char*'
__java__.cc: In function 'octave_value box_more(JNIEnv*, _jobject*,
_jclass*)':
__java__.cc:927: warning: unused variable 'cols'
__java__.cc: In function 'int unbox(JNIEnv*, const octave_value&,
jobject_ref&, jclass_ref&)':
__java__.cc:988: warning: deprecated conversion from string constant to
'char*'
__java__.cc:1052: warning: deprecated conversion from string constant to
'char*'
__java__.cc: In function 'int java_event_hook()':
__java__.cc:1117: warning: deprecated conversion from string constant to
'char*'
__java__.cc: In member function 'octave_value
octave_java::do_java_invoke(JNIEnv*, const std::string
&, const octave_value_list&)':
__java__.cc:1696: warning: deprecated conversion from string constant to
'char*'
__java__.cc: In static member function 'static octave_value
octave_java::do_java_invoke(JNIEnv*, con
st std::string&, const std::string&, const octave_value_list&)':
__java__.cc:1721: warning: deprecated conversion from string constant to
'char*'
__java__.cc: In static member function 'static octave_value
octave_java::do_java_create(JNIEnv*, con
st std::string&, const octave_value_list&)':
__java__.cc:1746: warning: deprecated conversion from string constant to
'char*'
__java__.cc: In member function 'octave_value
octave_java::do_java_get(JNIEnv*, const std::string&)'
:
__java__.cc:1767: warning: deprecated conversion from string constant to
'char*'
__java__.cc: In static member function 'static octave_value
octave_java::do_java_get(JNIEnv*, const
std::string&, const std::string&)':
__java__.cc:1787: warning: deprecated conversion from string constant to
'char*'
__java__.cc: In member function 'octave_value
octave_java::do_java_set(JNIEnv*, const std::string&,
const octave_value&)':
__java__.cc:1813: warning: deprecated conversion from string constant to
'char*'
__java__.cc: In static member function 'static octave_value
octave_java::do_java_set(JNIEnv*, const
std::string&, const std::string&, const octave_value&)':
__java__.cc:1835: warning: deprecated conversion from string constant to
'char*'
Octave-3.2.0: 5 >
=======================</screen messages>==============================

At least I've got a Java package now (including __java__.oct).

Next job:
Installing jhandles.

I'll keep you updated.

Best wishes,

Philip

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev