[Fwd: Re: java and linux]

[Janmaat, John]

Hello,

Tweaked things around a little - updated java and made sure some other
packages were in place - and I think I have the java-1.2.4 installed.
pkg list shows it present.  However, when I try to install jhandles, it
still doesn't seem to want to do it.

Here is what I get:

octave:5> pkg list
Package Name  | Version | Installation directory
--------------+---------+-----------------------
        java *|   1.2.4 | /usr/share/octave/packages/java-1.2.4
octave:6> pkg install jhandles-0.3.3a.tar.gz
make: *** [all] Error 255
error: 'make' returned the following error: make: Entering directory
`/tmp/oct-FadCAO/jhandles-0.3.3/src'
Java support not compiled
make: Leaving directory `/tmp/oct-FadCAO/jhandles-0.3.3/src'
error: called from `pkg:configure_make' in
file /usr/share/octave/3.0.1/m/pkg/pkg.m near line 1245, column 2

If I run configure in the jhandles directory (after unpacking, of
course), then

address@hidden:/home/jjanmaat/Desktop/jhandles-0.3.3> ./configure
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
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... mkoctfile
retrieving compile and link flags from mkoctfile
checking for F77_FUNC... yes
checking for octave... octave
checking for OCTAVE_VERSION in Octave... 3.0.1
checking for octave_config_info('canonical_host_type') in Octave...
i686-suse-linux-gnu
checking for octave_config_info('SHLEXT') in Octave... so
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.5.0_15
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking GL/gl.h usability... yes
checking GL/gl.h presence... yes
checking for GL/gl.h... yes
checking for glEnable in -lGL... yes
checking for filesep in Octave... /
checking for pathsep in Octave... :
configure: creating ./config.status
config.status: creating Makeconf

  "$prefix" is /usr/local
  "$exec_prefix" is ${prefix}

octave commands will install into the following directories:
   m-files:   /usr/share/octave/3.0.1/site/m/octave-forge

oct-files: /usr/lib/octave/3.0.1/site/oct/i686-suse-linux-gnu/octave-forge
   binaries:  /usr/lib/octave/3.0.1/site/exec/i686-suse-linux-gnu
alternatives:
   m-files:   /usr/share/octave/3.0.1/site/octave-forge-alternatives/m

oct-files: 
/usr/lib/octave/3.0.1/site/octave-forge-alternatives/oct/i686-suse-linux-gnu

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:      octave (version 3.0.1)
   mkoctfile:   mkoctfile for Octave 1
   java:        Java Development Kit not found
   octave.jar:
   jogl.jar:

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

Suggestions?


On Wed, 2008-07-02 at 09:57 +0200, Michael Goffioul wrote:
> On Tue, Jul 1, 2008 at 9:10 PM, Janmaat, John <address@hidden> wrote:
> > Hello Michael,
> >
> > No go.  My JAVA_HOME points to /usr/lib/jvm/jre, from where the file you
> > mention is located.  It is a directory deeper.  Thought maybe that it
> > couldn't find javac, which is in a branch of the /usr/lib/jvm directory,
> > not the ../jre directory.  Changed that, but still doesn't work.
> 
> There are 2 things you should take care of:
> 1) all java binaries should be in your PATH (java, javac, jar...)
> 2) if JVM is not installed in a directory like:
> /usr/lib/jvm/jre/lib/$ARCH/client/libjvm.so
> then JAVA_HOME should be defined such that JVM is located in
> $JAVA_HOME/jre/lib/$ARCH/client/libjvm.so
> 
> If it still does not work, could you report what you get when
> the configure script of the java package is executed?
> 
> Michael.