Are you using the Eclipse rpm or did you download Eclipse directly from
www.eclipse.org.
I just tried Eclipse 3.2 downloaded from www.eclipse.org and it started
just fine. I have not added all of the modules that I normally run
(just rebuilding the machine after a disk drive failure), but I don't
anticipate any problems.
Redhat sometimes makes changes to the packages in order to get them to
run will in their environment. I've noticed this in Firefox, some IP
telephony applications, and in the past the KDE development environment.
You might try installing the tar ball from www.eclipse.org, and then
using an explicit path to launch that version. If you have a workspace
set up already, back it up first and start the downloaded Eclipse
without a workspace.
I don't know if the downloaded Eclipse will run against the GNU Java.
Hope this helps . . . .
/mde/
just my two cents
On Wed, 2006-06-09 at 12:07 +0200, Mostafa Afgani wrote:
$ export PATH=/opt/jdk1.5.0_08/bin:$PATH; eclipse
LoadPlugin: failed to initialize shared library libXt.so [libXt.so:
cannot open shared object file: No such file or directory]
LoadPlugin: failed to initialize shared library libXext.so
[libXext.so: cannot open shared object file: No such file or
directory]
I've never experienced this. If I am testing something with a
proprietary JVM, I use the -vm option as Mark mentioned before.
Something like this:
eclipse -vm <path to java binary>
