octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Overhaul of Java auto-detection (MinGW results)


From: Philip Nienhuis
Subject: Re: Overhaul of Java auto-detection (MinGW results)
Date: Tue, 11 Dec 2012 15:18:38 -0800 (PST)

Rik-4 wrote
> On 12/10/2012 04:34 PM, 

> octave-maintainers-request@

>  wrote:
>> Message: 5
>> Date: Mon, 10 Dec 2012 15:26:48 -0800 (PST)
>> From: Philip Nienhuis <

> address@hidden

> >
>> To: 

> octave-maintainers@

>> Subject: Re: Overhaul of Java auto-detection
>> Message-ID: <

> address@hidden

>>
>> Content-Type: text/plain; charset=us-ascii
>>
>> Rik-4 wrote
>>> > 12/10/12
>>> > 
>>> > All,
>>> > 
>>> > I just pushed a changeset which significantly changes (improves?) the
>>> way
>>> > Java is detected if JAVA_HOME has not been set
>>> > (http://hg.savannah.gnu.org/hgweb/octave/rev/56239ff815a3).  There are
>>> > likely to be kinks which need working out and I particularly need
>>> feedback
>>> > from Mac OS X systems.  Despite all those caveats, I think this is a
>>> much
>>> > better strategy for detection than having a laundry list of
>>> directories to
>>> > check for each operating system and distribution.
>> Sorry to say, but now Java isn't properly picked up any more on my Linux
>> dev
>> box (Mageia-2).
>> All configure does now is echo the entered value for JAVA_HOME; the
>> include
>> dirs etc are blank.
>>
>> W/o JAVA_HOME it doesn't work better; after an hg update (pulling your
>> very
>> changeset), configure ran again but after a while the build broke with
>> complaints about missing jni.h
> Philip,
> 
> Since configure.ac was changed you need to run bootstrap in order to
> regenerate the configure script before running it.
> 
> 'hg pull; hg update; bootstrap; configure; make'
> 
> If you can, run './configure --your-options | tee confdbg.log' and I can
> take a look at what configure discovered.

On MinGW (gcc 3.5.2):

## W/o JAVA_HOME:
:
configure: WARNING: JAVA_HOME environment variable not initialized.
configure: WARNING: Auto-detection will proceed but is unreliable.
checking for java... /c/WINDOWS/system32/java
checking for javac... no
checking for jar... no
configure: WARNING: No javac compiler or jar executable found.  Octave will
not be able to call Java methods.
configure: creating ./config.status
:
  Java home:                   C:\Programs\Java\jre6
  Java JVM path:
  Java CPPFLAGS:
  Java libraries:
:

## W. JAVA_HOME  /c/Programs/Java/jdk1.6.0_33
:
checking for java... /c/Programs/Java/jdk1.6.0_33/jre/bin/java
checking for javac... /c/Programs/Java/jdk1.6.0_33/bin/javac
checking for jar... /c/Programs/Java/jdk1.6.0_33/bin/jar
checking for Java version... 1.6.0_33
configure: WARNING: Library libjvm not found.  Octave will not be able to
call Java methods.
:
  Java home:                   /c/Programs/Java/jdk1.6.0_33
  Java JVM path:
  Java CPPFLAGS:
  Java libraries:
:

Looks similar to what happens on my Linux-Mageia 2 box; it finds the
executables OK but not the jvm.

Philip



--
View this message in context: 
http://octave.1599824.n4.nabble.com/Overhaul-of-Java-auto-detection-tp4647726p4647790.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]