Summary: | javaws not handled more elegantly with AMD64 Sun 1.5 JDK/JRE. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sean Parsons <gentoo> |
Component: | New packages | Assignee: | Java team <java> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | chris, denilsonsa |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sean Parsons
2006-02-11 18:26:07 UTC
This actually wouldn't occur without the migration-overlay. The new system adds symlinks in /usr/bin to a script call run-java-tool. In short, this script figures out which tool you're calling (java, javac, javaws, etc), and then based on your settings, will call the appropriate tool from the appropriate VM. A some more details can be found at: https://projects.gentooexperimental.org/expj/wiki/Old_system_new_system_and_why As for javaws for sun-jre and sun-jdk 1.5, they don't seem to install javaws, which is a bug in it's own right. As for the run-java-tool, the error message could be improved to something like... 'Tried to execute javaws from the VM located in /etc/java-config-2/current-system-vm, but the executable did not exist'. (In reply to comment #1) > The new system adds symlinks in /usr/bin to a script call run-java-tool. In > short, this script figures out which tool you're calling (java, javac, javaws, > etc), and then based on your settings, will call the appropriate tool from the > appropriate VM. It appears that the java-run-tool can be fixed to execute /opt/java32/javaws/javaws instead of /opt/sun-jdk-1.5.<*>/bin/javaws then javaws will work. Chris (In reply to comment #2) > It appears that the java-run-tool can be fixed to execute > /opt/java32/javaws/javaws instead of /opt/sun-jdk-1.5.<*>/bin/javaws then > javaws will work. While that may get it working, I really doubt that is the correct fix. In this case, the 64 bit sun-jdk-1.5's javaws ends up pointing at a 32bit blackdown-jre-1.4 javaws. (In reply to comment #3) > While that may get it working, I really doubt that is the correct fix. In this > case, the 64 bit sun-jdk-1.5's javaws ends up pointing at a 32bit > blackdown-jre-1.4 javaws. Yes, I see that now. But it does appear to work. One can even go into the java web start preferences, add the sun-1.5 engine and disable the blackdown-1.4 engine. It appears similar to an issue I'm having with a 32 bit system - a missing javawsbin issue. Chris (In reply to comment #4) > Yes, I see that now. But it does appear to work. One can even go into the java > web start preferences, add the sun-1.5 engine and disable the blackdown-1.4 > engine. Just to followup, by doing the above and starting an app it does run Sun's java: 10272 pts/3 Sl 0:01 /opt/sun-jdk-1.5.0.08/bin/java -Xbootclasspath/a:/opt/java32/javaws/javaws 10316 pts/3 Sl 0:01 /opt/sun-jdk-1.5.0.08/bin/java -Xbootclasspath/a:/opt/java32/javaws/javaws Chris Found these notes from Sun's java download site: ==================================================== Solaris x64 self-extracting file (use 32-bit version for applet and Java Web Start support) Linux x64 RPM in self-extracting file (use 32-bit version for applet and Java Web Start support) Linux x64 self-extracting file (use 32-bit version for applet and Java Web Start support) ==================================================== the other bug seems to have proposed solution so duping this one although it was first *** This bug has been marked as a duplicate of bug 147198 *** |