[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Java jni.h
From: |
Philip Nienhuis |
Subject: |
Re: Java jni.h |
Date: |
Sat, 8 Dec 2012 13:01:12 -0800 (PST) |
Michael Godfrey wrote
> On 12/07/2012 02:05 PM, Rik wrote:
>> Try setting JAVA_HOME to /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.9.x86_64.
> I will try that, but of course it will break the next time java is
> updated,
> Is there a more persistent way?
In my /usr/lib/jvm directory I have several subdirs, some empty, some
suggesting an older java version.
Yet there's a persistent "java" symlink that points (in a few steps) to the
current java version (in my case /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.6)
and gets updated by rpm each time java is updated.
So try to find if there's a similar symlink in your box.
BTW:
/usr/lib/jvm/java ->
/etc/alternatives/java_sdk ->
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.6
If I do:
export JAVA_HOME=/usr/lib/jvm/java
before configure, Octave builds fine and all Java stuff works.
Philip
--
View this message in context:
http://octave.1599824.n4.nabble.com/Java-compilation-warnings-tp4647602p4647667.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.
- Java compilation warnings, Rik, 2012/12/06
- Re: Java compilation warnings, Richard Crozier, 2012/12/07
- Re: Java compilation warnings, Michael D. Godfrey, 2012/12/07
- Re: Java jni.h, Rik, 2012/12/07
- Re: Java jni.h, Michael D. Godfrey, 2012/12/07
- Re: Java jni.h, Rik, 2012/12/07
- Re: Java jni.h, Michael D. Godfrey, 2012/12/07
- Re: Java jni.h, Rik, 2012/12/07
- Re: Java jni.h,
Philip Nienhuis <=
- Re: Java jni.h, Michael D. Godfrey, 2012/12/07
Re: Java compilation warnings, Philip Nienhuis, 2012/12/07
Re: Java compilation warnings, Alexander Hansen, 2012/12/07
Java compilation warnings, John W. Eaton, 2012/12/07