Bug 146950
Summary: | eclipse won't start | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | yeech <rshewan> |
Component: | eclipse | Assignee: | Andrew Overholt <overholt> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-02-03 18:40:50 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
yeech
2005-02-02 22:38:55 UTC
Assigning to me. You need to have the following packages installed (or greater version-releases): gcc4-java-4.0.0-0.22 libgcj4-devel-4.0.0-0.22 libgcj4-4.0.0-0.22 java-1.4.2-gcj4-compat-1.4.2.0-2jpp java-1.4.2-gcj4-compat-devel-1.4.2.0-2jpp You also need to make sure that your java and javac alternatives are pointing to those from java-1.4.2-gcj4-compat: su - -c "update-alternatives --set java \ /usr/lib/jvm/jre-1.4.2-gcj4/bin/java" su - -c "update-alternatives --set javac \ /usr/lib/jvm/java-1.4.2-gcj4/bin/javac" Please close the bug if these things work for you. Otherwise, please give the output of: rpm -qa | grep eclipse rpm -q gcc4-java rpm -q libgcj4-devel which java java --version which javac javac -version Thanks! The update-alternatives did the trick. I still see $ eclipse Warning: -Xms64M not understood. Ignoring. Warning: -Xmx256M not understood. Ignoring. Warning: Could not get charToByteConverterClass! Is this a problem? Is there a web site associated with this effort? The JVM memory warnings can be removed by removing the corresponding flags in /usr/bin/eclipse. Someone should make it so that those flags are not used when we're using GCJ ... and only use the GCJ-specific options (precompiled.db, etc.) when using gij. I guess we'll need to run a java -version to figure out what JVM we're running. Either way, it's not that important right now. I'm not entirely sure about the charToByteConverterClass error. It doesn't seem to be affecting things right now, but there's a bug about it nonetheless: #146959. There isn't really a web site for this effort. I heard something about a fedora-java-devel-list list being created but in the meantime fedora-devel-list is probably the best place to discuss this stuff. Thanks for the interest. Can you close this bug now? Thanks for the information. It runs. The JVM options are not originating from /usr/bin/eclipse. This file appears to be the Fedora version of the file as opposed to eclipse.org. Oh yeah, they're coming from /etc/eclipse.conf (and we set that so we should change it when using the natively-compiled eclipse). Thanks for closing. |