Hello All! Subj. Just found that on x86 and ppc OpenJDK-devel installs into "/usr/lib/jvm/java-1.6.0-openjdk", on x86_64 - into "/usr/lib/jvm/java-1.6.0-openjdk.x86_64", and on ppc64 - into "/usr/lib/jvm/java-1.6.0-openjdk.ppc64".
Is it intentional, or this is a bug? In any case how can I pass JDK home to buildscripts w/o ugly %ifarch/else?
On Sunday 07 December 2008 12:05:35 pm Peter Lemenkov wrote:
Hello All! Subj. Just found that on x86 and ppc OpenJDK-devel installs into "/usr/lib/jvm/java-1.6.0-openjdk", on x86_64 - into "/usr/lib/jvm/java-1.6.0-openjdk.x86_64", and on ppc64 - into "/usr/lib/jvm/java-1.6.0-openjdk.ppc64".
Is it intentional, or this is a bug? In any case how can I pass JDK home to buildscripts w/o ugly %ifarch/else?
-- With best regards!
Well, we also use alternatives to handle choosing the java version to use. If JDK_HOME is just supposed to contain 'bin/javac' then you can set it to '/usr'.
Le dimanche 07 décembre 2008 à 12:11 -0800, Conrad Meyer a écrit :
On Sunday 07 December 2008 12:05:35 pm Peter Lemenkov wrote:
Hello All! Subj. Just found that on x86 and ppc OpenJDK-devel installs into "/usr/lib/jvm/java-1.6.0-openjdk", on x86_64 - into "/usr/lib/jvm/java-1.6.0-openjdk.x86_64", and on ppc64 - into "/usr/lib/jvm/java-1.6.0-openjdk.ppc64".
Is it intentional, or this is a bug? In any case how can I pass JDK home to buildscripts w/o ugly %ifarch/else?
Well, we also use alternatives to handle choosing the java version to use. If JDK_HOME is just supposed to contain 'bin/javac' then you can set it to '/usr'.
The "jre" alternative controls access to the default system jre, and the "java" alternative does the same for the full jdk
On Sun, Dec 7, 2008 at 3:05 PM, Peter Lemenkov lemenkov@gmail.com wrote:
In any case how can I pass JDK home to buildscripts w/o ugly %ifarch/else?
First, try to make scripts not reliant on the presence of the JAVA_HOME environment variable. It should be enough to simply invoke "java" to get a JVM.
However, if you need it, simply wrap invocations to the scripts with JAVA_HOME=/etc/alternatives/jre which uses the alternatives system to point to the system-preferred JRE.
2008/12/7, Colin Walters walters@verbum.org:
On Sun, Dec 7, 2008 at 3:05 PM, Peter Lemenkov lemenkov@gmail.com wrote:
In any case how can I pass JDK home to buildscripts w/o ugly %ifarch/else?
First, try to make scripts not reliant on the presence of the JAVA_HOME environment variable. It should be enough to simply invoke "java" to get a JVM.
I'll do.
However, if you need it, simply wrap invocations to the scripts with JAVA_HOME=/etc/alternatives/jre which uses the alternatives system to point to the system-preferred JRE.
Thanks! It's working.
On Sun, Dec 7, 2008 at 12:05 PM, Peter Lemenkov lemenkov@gmail.com wrote:
Hello All! Subj. Just found that on x86 and ppc OpenJDK-devel installs into "/usr/lib/jvm/java-1.6.0-openjdk", on x86_64 - into "/usr/lib/jvm/java-1.6.0-openjdk.x86_64", and on ppc64 - into "/usr/lib/jvm/java-1.6.0-openjdk.ppc64".
Is it intentional, or this is a bug? In any case how can I pass JDK home to buildscripts w/o ugly %ifarch/else?
-- With best regards!
Everything that I have been building, I have been doing without requiring any of the java environment variables, the way it is setup right now it should JustWork tm if you call java javac etc.
--Brennan Ashton