SCIENTIFIC-LINUX-USERS Archives

February 2009

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Craig Moore <[log in to unmask]>
Reply To:
Craig Moore <[log in to unmask]>
Date:
Wed, 11 Feb 2009 09:15:24 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (191 lines)
On Tue, 2009-02-10 at 13:39 -0600, Troy Dawson wrote:
> Craig Moore wrote:
> > On Tue, 2009-02-10 at 10:08 -0600, Troy Dawson wrote:
> >> Craig Moore wrote:
> >>> I've just installed eclipse using the package manager, and I cannot 
> >>> start the program. This is what I installed:
> >>>
> >>> $ rpm -q eclipse-jdt
> >>> eclipse-jdt-3.2.1-19.el5.x86_64
> >>>
> >>> Here is my computer's info:
> >>>
> >>> $ cat redhat-release 
> >>> Scientific Linux SL release 5.2 (Boron)
> >>>
> >>> $ cat /proc/cpuinfo
> >>> model name      : Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz
> >>>
> >>> $ cat /proc/meminfo
> >>> MemTotal:      3907664 kB
> >>> MemFree:       2096508 kB
> >>>
> >>> $ cat partitions 
> >>> major minor  #blocks  name
> >>>
> >>>    8     0  244140625 sda
> >>>    8     1     104391 sda1
> >>>    8     2  244035382 sda2
> >>>  253     0  241991680 dm-0
> >>>  253     1    2031616 dm-1
> >>>
> >>> Here is the text from the error log:
> >>>
> >>> $ cat /home/cmoore/workspace/.metadata/.log
> >>> !SESSION 2009-02-10 16:33:01.457
> >>> -----------------------------------------------
> >>> eclipse.buildId=M20060921-0945
> >>> java.version=1.6.0_12
> >>> java.vendor=Sun Microsystems Inc.
> >>> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> >>> Command-line arguments:  -os linux -ws gtk -arch x86_64
> >>>
> >>> !ENTRY org.eclipse.osgi 4 0 2009-02-10 16:33:02.549
> >>> !MESSAGE Application error
> >>> !STACK 1
> >>> java.lang.UnsatisfiedLinkError: /usr/lib64/eclipse/configuration/org.eclipse.osgi/bundles/101/1/.cp/libswt-pi-gtk-3235.so: /usr/lib64/eclipse/configuration/org.eclipse.osgi/bundles/101/1/.cp/libswt-pi-gtk-3235.so: wrong ELF class: ELFCLASS64 (Possible cause: architecture word width mismatch)
> >>>         at java.lang.ClassLoader$NativeLibrary.load(Native Method)
> >>>         at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1778)
> >>>         at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1687)
> >>>         at java.lang.Runtime.loadLibrary0(Runtime.java:823)
> >>>         at java.lang.System.loadLibrary(System.java:1030)
> >>>         at
> >>> org.eclipse.swt.internal.Library.loadLibrary(Library.java:123)
> >>>         at org.eclipse.swt.internal.gtk.OS.<clinit>(OS.java:22)
> >>>         at
> >>> org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:63)
> >>>         at
> >>> org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:54)
> >>>         at org.eclipse.swt.widgets.Display.<clinit>(Display.java:126)
> >>>         at
> >>> org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:433)
> >>>         at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161)
> >>>         at
> >>> org.eclipse.ui.internal.ide.IDEApplication.createDisplay(IDEApplication.java:122)
> >>>         at
> >>> org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:75)
> >>>         at org.eclipse.core.internal.runtime.PlatformActivator
> >>> $1.run(PlatformActivator.java:78)
> >>>         at
> >>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
> >>>         at
> >>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
> >>>         at
> >>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> >>>         at
> >>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
> >>>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>>         at
> >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> >>>         at
> >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> >>>         at java.lang.reflect.Method.invoke(Method.java:597)
> >>>         at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
> >>>         at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
> >>>         at org.eclipse.core.launcher.Main.run(Main.java:977)
> >>>         at org.eclipse.core.launcher.Main.main(Main.java:952)
> >>>
> >>> Any ideas how I can fix this?
> >>>
> >>> Thanks,
> >>> Craig
> >> Hi Craig,
> >> I am not a big eclipse user, so I'm not positive about this.  But since 
> >> you are on x86_64, there might be a i386 version x86_64 conflict.  I 
> >> would see if maybe there is a problem with having both i386 and x86_64 
> >> version of jdk installed.  To check do a
> >>
> >> rpm -qa | grep jdk | sort
> >> rpm -qa | grep java | sort
> >>
> >> Troy
> > 
> > I almost always use emacs, but I find eclipse to be a superior editor
> > for doing java and xml files. Emacs can't handle indentation on HTML
> > files, whereas eclipse can do it without breaking a sweat. Usually if I
> > can't use eclipse, then I use the tidy program for cleaning up my html.
> > 
> > Here is the output from the commands:
> > 
> > $ rpm -qa | grep jdk | sort
> > jdk-1.6.0_12-fcs.i586
> > jdk-1.6.0_12-fcs.x86_64
> > 
> > $ rpm -qa | grep java | sort
> > ant-javamail-1.6.5-2jpp.2.x86_64
> > bsh-javadoc-1.3.0-9jpp.1.x86_64
> > gcc-java-4.1.2-42.el5.x86_64
> > glib-java-0.2.6-3.fc6.x86_64
> > java-1.4.2-gcj-compat-1.4.2.0-40jpp.115.x86_64
> > java-1.4.2-gcj-compat-devel-1.4.2.0-40jpp.115.i386
> > java-1.4.2-gcj-compat-devel-1.4.2.0-40jpp.115.x86_64
> > java-1.4.2-gcj-compat-src-1.4.2.0-40jpp.115.x86_64
> > java-1.5.0-sun-compat-1.5.0.90-2.sl.jpp.noarch
> > java-1.6.0-sun-compat-1.6.0.12-1.sl5.jpp.x86_64
> > xmlrpc-javadoc-2.0.1-3jpp.1.x86_64
> > 
> > The only item that looks different are these two, but I do not know if
> > they are the culprits:
> > 
> > jdk-1.6.0_12-fcs.i586
> > java-1.5.0-sun-compat-1.5.0.90-2.sl.jpp.noarch
> > 
> > I have come across a bug on the Red Hat bug tracker that might be
> > related here:
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=455709
> > 
> > But if I read this correctly, then it will not get fixed until they port
> > Fedora to 64 bit? The last log message was at the end of January.
> > 
> > Craig
> > 
> 
> Hi Craig,
> My guess is that there is a problem with having both jdk i586 and x86_64 
> both on at the same time.
> I believe you can the i586 off without any troubles.
> java-1.5.0-sun-compat-1.5.0.90-2.sl.jpp.noarch can go off also, but it 
> really is just a placeholder that helped transition everything up to jdk 
> 1.6.
> Can you try
> rpm -e java-1.5.0-sun-compat-1.5.0.90-2.sl.jpp.noarch
> rpm -e jdk-1.6.0_12-fcs.i586
> 
> And see if you get the same error.
> Troy

I tried the two commands and now I receive the following error in a
window:

JVM terminated. Exit code=127
/usr/bin/java
-Xms40m
-Xmx256m
-Dosgi.sharedConfiguration.area=/usr/lib64/eclipse/configuration
-jar /usr/share/eclipse/startup.jar
-os linux
-ws gtk
-arch x86_64
-launcher /usr/bin/eclipse
-name Eclipse
-showsplash 600
-exitdata 5540018
-vm /usr/bin/java
-vmargs
-Xms40m
-Xmx256m
-Dosgi.sharedConfiguration.area=/usr/lib64/eclipse/configuration
-jar /usr/share/eclipse/startup.jar 

at the command line I get the following error:

/usr/bin/java: error while loading shared libraries: libjli.so: cannot
open shared object file: No such file or directory

I guess that wasn't it. How can I restore the files back to the way they
were (i.e. undo what I just did) ? Any other ideas?

Thanks,
Craig

ATOM RSS1 RSS2