Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] JAVA50_HOME and JAVA60_HOME env variables are set to IBM ppc jdks

I'm not sure where you're seeing these values, but if you tell me (and suggest which versions I should replace them with) I'll get right on it.

Denis



On 09/24/2010 12:36 PM, Nick Boldt wrote:
Current values are:

JAVA60_HOME=/opt/public/common/ibm-java-jdk-ppc-60
JAVA50_64_HOME=/opt/public/common/ibm-java2-ppc64-50
JAVA50_HOME=/opt/public/common/ibm-java2-ppc-50
JAVA14_HOME=/opt/public/common/ibm-java2-142
JAVA_FOUNDATION_HOME=/opt/public/common/org.eclipse.sdk-feature/libs

What should the new defaults be? IBM or Sun? And why don't aren't the old paths executable anymore?

$ for d in $(find /opt/public/common/ -maxdepth 1 -type d -name "ibm*" -o -name "sun*" -o -name "jdk*"); do echo $d; $d/bin/java -version; echo "------"; echo ""; done

/opt/public/common/sun-jdk1.6.0_21_i586
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot(TM) Server VM (build 17.0-b16, mixed mode)
------

/opt/public/common/jdk-1.6.x86_64
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode)
------

/opt/public/common/ibm-java-jdk-ppc-60
-committer_shell: /opt/public/common/ibm-java-jdk-ppc-60/bin/java: cannot execute binary file
------

/opt/public/common/ibm-java-x86_64-60
java version "1.6.0"
Java(TM) SE Runtime Environment (build pxa6460sr8-20100409_01(SR8))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr8-20100401_55940 (JIT enabled, AOT enabled)
J9VM - 20100401_055940
JIT  - r9_20100401_15339
GC   - 20100308_AA)
JCL  - 20100408_01
------

/opt/public/common/sun-jdk1.6.0_21_x64
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
------

/opt/public/common/jdk-1.5.0_16
java version "1.5.0_16"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b02)
Java HotSpot(TM) Server VM (build 1.5.0_16-b02, mixed mode)
------

/opt/public/common/jdk-1.6.0_10
java version "1.6.0_10"
Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
Java HotSpot(TM) Server VM (build 11.0-b15, mixed mode)
------

/opt/public/common/ibm-java-ppc64-60-SR7
-committer_shell: /opt/public/common/ibm-java-ppc64-60-SR7/bin/java: cannot execute binary file
------

/opt/public/common/ibm-java2-ppc-50
-committer_shell: /opt/public/common/ibm-java2-ppc-50/bin/java: cannot execute binary file
------

/opt/public/common/ibm-java-ppc-60
-committer_shell: /opt/public/common/ibm-java-ppc-60/bin/java: No such file or directory
------

/opt/public/common/jdk-1.5.0-22.x86_64
java version "1.5.0_22"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_22-b03, mixed mode)
------

/opt/public/common/ibm-java2-ppc-50-old
-committer_shell: /opt/public/common/ibm-java2-ppc-50-old/bin/java: cannot execute binary file
------

/opt/public/common/ibm-java2-ppc64-50
-committer_shell: /opt/public/common/ibm-java2-ppc64-50/bin/java: cannot execute binary file
------



On 09/24/2010 11:05 AM, Jeff Johnston wrote:
Our project uses the JAVA50_HOME and JAVA60_HOME environment variables.
These are pointing to the ibm jdks in /opt/public/common.

I have a workaround in place, but can these be updated for the new
x86_64 build machine?

-- Jeff J.

Back to the top