 |
 |
Sorry, I was not being clear. I know there is the jpackage in SL(C) and how it can do things with different java versions. SLC304 default install does not include jpackage but j2re-1.4.2_06-4.cern and pre/post install script. In contrast SL204 does have jpackage and no sun java. LCG 2.4.0 release_notes/install/upgrade docu says: (from the "LCG2-Manual-Install.pdf") ------------------------------------------------------------------------- 3. JAVA INSTALLATION You should install java sdk 1.4.2 on your system before installing the middleware. Download it from SUN java web site (1.4.2 is required - http://java.sun.com/j2se/1.4.2/download.html). You should absolutely install the J2SDK 1.4.2 rpm package (if you do not install it in RPM format you ll not be able to install the middleware), on the sun java web page follow the link RPM in a self extracting file. Then follow instructions provided by SUN. Set in your site-info.def (YAIM configuration file) the variable JAVA LOCATION to your java installation directory. ------------------------------------------------------------------------- So, is not a "strange reason" to install SUN java for LCG 2.4.0 on SL(C)30X but the clear reason to do so. On Wed, 13 Apr 2005, Kostas Georgiou wrote: > On Wed, Apr 13, 2005 at 01:36:17AM +0400, Valery Mitsyn wrote: > > > did anybody see this when invoke: > > > > ----------------- > > vrvs:~ # /usr/bin/java > > libgcj-java-placeholder.sh > > > > This script is a placeholder for the /usr/bin/java > > - PATH can be dropped for sanity. > > - PATH can be replaced (does hepix do so?). > > - /usr/bin/jav* can be hardcoded in the script or binary (ahh, ohh! been > > there) > > - an application may have own search strategy for java. > > Well the "standard" way in RHEL is to use the jpackage rpms. The /usr/bin/java > link is set to the latest version by default but applications can use the /usr/lib/jvm/java-* > links if they are after specific versions (some lcg tools fail with 1.5.0 for example). > > > So, looks like another rpm should be provided by LCG to carry > > about /etc/alternatives/... links for Sun's j2sdk like it was > > in CERN j2re. > > Instead of using the sun rpm you should be installing a jpackage one (you need to > build it of course but it only takes 30 secs ;). If for some strange reason you > want to use the sun rpm have a look at the java-1.4.2-sun-compat rpm from jpackage > which provides compatibility symlinks. > > Cheers, > Kostas > > For the record here is what you get in my RHEL machines. > > $ ls -ald /usr/bin/java > lrwxrwxrwx 1 root root 22 Jul 6 2004 /usr/bin/java -> /etc/alternatives/java > > $ ls -ald /etc/alternatives/java > lrwxrwxrwx 1 root root 35 Apr 11 15:50 /etc/alternatives/java -> /usr/lib/jvm/jre-1.5.0-sun/bin/java > > $ ls -al /usr/lib/jvm > lrwxrwxrwx 1 root root 26 Jul 6 2004 java -> /etc/alternatives/java_sdk > lrwxrwxrwx 1 root root 32 Jul 6 2004 java-1.4.2 -> /etc/alternatives/java_sdk_1.4.2 > lrwxrwxrwx 1 root root 22 Dec 22 04:03 java-1.4.2-ibm -> java-1.4.2-ibm-1.4.2.0 > drwxr-xr-x 6 root root 4096 Nov 10 20:36 java-1.4.2-ibm-1.4.2.0 > lrwxrwxrwx 1 root root 32 Apr 11 15:50 java-1.5.0 -> /etc/alternatives/java_sdk_1.5.0 > lrwxrwxrwx 1 root root 20 Apr 11 15:50 java-1.5.0-sun -> java-1.5.0-sun-1.5.0 > drwxr-xr-x 6 root root 4096 Apr 11 15:50 java-1.5.0-sun-1.5.0 > lrwxrwxrwx 1 root root 30 Aug 4 2004 java-ibm -> /etc/alternatives/java_sdk_ibm > lrwxrwxrwx 1 root root 30 Apr 11 15:50 java-sun -> /etc/alternatives/java_sdk_sun > lrwxrwxrwx 1 root root 21 Jul 6 2004 jre -> /etc/alternatives/jre > lrwxrwxrwx 1 root root 27 Jul 6 2004 jre-1.4.2 -> /etc/alternatives/jre_1.4.2 > lrwxrwxrwx 1 root root 26 Dec 22 04:02 jre-1.4.2-ibm -> java-1.4.2-ibm-1.4.2.0/jre > lrwxrwxrwx 1 root root 27 Apr 11 15:50 jre-1.5.0 -> /etc/alternatives/jre_1.5.0 > lrwxrwxrwx 1 root root 24 Apr 11 15:50 jre-1.5.0-sun -> java-1.5.0-sun-1.5.0/jre > lrwxrwxrwx 1 root root 25 Aug 4 2004 jre-ibm -> /etc/alternatives/jre_ibm > lrwxrwxrwx 1 root root 25 Apr 11 15:50 jre-sun -> /etc/alternatives/jre_sun > Best regards, Valery Mitsyn