Bug 145647
Summary: | The priority of gcj in alternatives is too high. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ryo Dairiki <nue-nubata> |
Component: | java-1.4.2-gcj-compat | Assignee: | Thomas Fitzsimmons <fitzsim> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-03-03 23:48:11 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ryo Dairiki
2005-01-20 13:49:35 UTC
If you want to use Sun's JVM, your best bet is to build a JPackage starting from their .nosrc.rpm. Installing the resulting RPM will cause Sun's VM to own the java tools in /usr/bin. Otherwise, if you just want to use Sun's RPM, you'll need to put $JAVA_HOME/bin at the start of your PATH. In general, you should put any custom binary directory at the start of your PATH to ensure that custom binaries take precedence over system-default ones. Note that in Fedore Core 4 test 1, you may not need Sun's JVM anymore; java-1.4.2-gcj-compat and java-1.4.2-gcj-compat-devel wrap the GCJ toolset to provide JPackage-compatible Free Software runtime and development environments. Give them a try! Closing. |