Re: Problem w/ setting Sun's JVM via (g)alternatives?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 08/27/2009 01:54 PM, Marcelo M. Garcia wrote:
On 08/27/2009 06:20 PM, Daniel B. Thurman wrote:

Since I am trying to get Eclipse's Ganemede working
again, I am told that I would need to use Sun's JRE,
however, I opted to use the JDK instead of the JRE.

I have downloaded and installed Sun's JDK 1.6 & 1.5
into /opt and it looks good. I can via environment
setting run the java -version tests.

However

I have added the /opt/jdk[...]/bin/java to the alternatives
list in the 'java' category for both versions as follows:

/opt/jdk.1.6[...]/bin/java priority: 1000
/opt/jdk.1.5[...]/bin/java priority: 500

then selected JDK v1.6, and tried to launch Eclipse.

What resulted was a popup failure with the
relevant entry:

[...]
-vm /opt/jdk1.6.0_16/bin/../jre/lib/i386/client/libjvm.so
[...]
Note: the entire "barf" is at the end of the line.

Why is 'java' replaced with '../jre/lib/i386/client/libjvm.so'?
Yes, the -vm path exist.

Is this normal?

Side question: is the JRE instead of JDK required? I wanted
the JDK so that I can do Java development but I do not think
there is a difference except only where the jre path is different.

Thanks-
Dan

The "barf":
===========================================
JVM terminated. Exit code=-1
-Xms40m
-Xmx512m
-XX:MaxPermSize=128m
-XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith

-XX:CompileCommand=exclude,org/eclipse/jdt/internal/compiler/lookup/ParameterizedMethodBinding,<init>

-XX:CompileCommand=exclude,org/eclipse/cdt/internal/core/dom/parser/cpp/semantics/CPPTemplates,instantiateTemplate

-XX:CompileCommand=exclude,org/eclipse/cdt/internal/core/pdom/dom/cpp/PDOMCPPLinkage,addBinding

-XX:CompileCommand=exclude,org/python/pydev/editor/codecompletion/revisited/PythonPathHelper,isValidSourceFile

-XX:CompileCommand=exclude,org/python/pydev/ui/filetypes/FileTypesPreferencesPage,getDottedValidSourceFiles

-Dorg.eclipse.equinox.p2.reconciler.dropins.directory=/usr/share/eclipse/dropins

-Djava.class.path=/usr/lib/eclipse/plugins/org.eclipse.equinox.launcher_1.0.101.R34x_v20081125.jar

-os linux
-ws gtk
-arch x86
-showsplash
/usr/lib/eclipse//plugins/org.fedoraproject.ide.platform_3.4.2/splash.bmp
-launcher /usr/lib/eclipse/eclipse
-name Eclipse
--launcher.library
/usr/lib/eclipse/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.101.R34x_v20080805/eclipse_1116.so

-startup
/usr/lib/eclipse/plugins/org.eclipse.equinox.launcher_1.0.101.R34x_v20081125.jar

-vm /opt/jdk1.6.0_16/bin/../jre/lib/i386/client/libjvm.so
-vmargs
-Xms40m
-Xmx512m
-XX:MaxPermSize=128m
-XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith

-XX:CompileCommand=exclude,org/eclipse/jdt/internal/compiler/lookup/ParameterizedMethodBinding,<init>

-XX:CompileCommand=exclude,org/eclipse/cdt/internal/core/dom/parser/cpp/semantics/CPPTemplates,instantiateTemplate

-XX:CompileCommand=exclude,org/eclipse/cdt/internal/core/pdom/dom/cpp/PDOMCPPLinkage,addBinding

-XX:CompileCommand=exclude,org/python/pydev/editor/codecompletion/revisited/PythonPathHelper,isValidSourceFile

-XX:CompileCommand=exclude,org/python/pydev/ui/filetypes/FileTypesPreferencesPage,getDottedValidSourceFiles

-Dorg.eclipse.equinox.p2.reconciler.dropins.directory=/usr/share/eclipse/dropins

-Djava.class.path=/usr/lib/eclipse/plugins/org.eclipse.equinox.launcher_1.0.101.R34x_v20081125.jar

===========================================

Hi

I installed the JDK-1.6u16 in my F-11, and I used the following commands:
alternatives --install /usr/bin/java java /usr/java/jdk1.6.0_16/bin/java 2 alternatives --install /usr/bin/javac javac /usr/java/jdk1.6.0_16/bin/javac 2
alternatives --config java
alternatives --config javac

It seems that you are forgetting the 'config' part of 'alternatives'.

I use this CentOS wiki as reference:
http://wiki.centos.org/TipsAndTricks/PluginsFor64BitFirefox

Regards

mg.


I have gotten the alternatives mess straightened out.  I have
Sun's JDK 1.5.0_20 & 1.6.0_16 installed and working correctly.
I have tested each of the `java/c -version',  switching using
galternatives and `java/c -version' correctly reports the
correct version each time.

Now, I have verified that regardless of which Java version one is
using, it does not fix  the problem with Ganymede. I have tried
all 4 versions of java (two to Fedora's gcj/open, and the other
two:  Sun's 1.5.0_20 & 1.6.0_16) and both Fedora-11-Eclipse &
Galileo works fine.  Just not Ganymede, and the problem may
be that of what Andrew Overholt has said:

"... he was bitten by the fact that the XULRunner APIs changed
post-Eclipse 3.4 (Ganymede)"

I don't know what Andrew means by: "post-Eclipse 3.4 (Ganymede)",
but I assume he means Eclipse's Ganymede SR-2 release, if so,
that is not working, at least for me.

But here is the thing, Ganymede SR-2 works on F9, can't say for sure
about F10, but does not on F11.  So I am not sure when between
these Fedora versions: "XULRunner APIs [has] changed". ;)

Dan

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux