LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   error in eclipse 3.0 amd64 and mandrake 9.2 (https://www.linuxquestions.org/questions/linux-software-2/error-in-eclipse-3-0-amd64-and-mandrake-9-2-a-169680/)

ahki 04-13-2004 03:02 PM

error in eclipse 3.0 amd64 and mandrake 9.2
 
I installed Eclipse 3.0, eclipse-SDK-3.0M8-linux-gtk-amd64, on Mandrake 64. Java SDK version is 1.4.2. But I have the following error when I run eclipse. Could you tell me why this happens.

java.lang.UnsatisfiedLinkError: /home/ki/Documents/eclipse/plugins/org.eclipse.swt.gtk64_3.0.0/os/linux/amd64/libswt-pi-gtk-3044.so: /home/ki/Documents/e
clipse/plugins/org.eclipse.swt.gtk64_3.0.0/os/linux/amd64/libswt-pi-gtk-3044.so: cannot open shared object file: No such file or directory
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1560)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1469)
at java.lang.Runtime.loadLibrary0(Runtime.java:788)
at java.lang.System.loadLibrary(System.java:834)
at org.eclipse.swt.internal.Library.loadLibrary(Library.java:100)
at org.eclipse.swt.internal.gtk.OS.<clinit>(OS.java:19)
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:112)
at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:271)
at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:151)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:66)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:277)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:239)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:117)
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:324)
at org.eclipse.core.launcher.Main.basicRun(Main.java:267)
at org.eclipse.core.launcher.Main.run(Main.java:692)
at org.eclipse.core.launcher.Main.main(Main.java:676)

Thanks,
Ki

yangel88 06-30-2004 10:54 AM

I have the same error for eclipse M8 as well( I have suse9.1pro, amd64), after I got the source and build locally, the problem seemed to be disappeared. Now I have tried all M9 versions, eg. RC1, RC2, I have the same problem once again. I wonder if it is the kernel problem as it is working fine in Debian! Can anyone help?

Grameentech 07-21-2004 02:29 PM

Mandrake Eclipse3.0 JBOSS newbie
 
I followed good advice from http://www.csfalcon.com:81/applications/app_java.jsp to install Eclipse and was able to run it. Then, I followed instructions to load JBOSS as a pluggin. I could not locate the correct working directory for JBoss so closed down eclipse and now cannot relaunch. After trying to work through fg jobs (with limited results) I restarted the machine. The JBOSS config may or may not be relevant.

The error appears on the use of "eclipse&" and also on "eclipse-clean&".
?Problems during startup. Check the ".log" file in the ".metadata" directory of your workspace.?
The verbose error is
" !ENTRY org.eclipse.core.launcher 4 0 Jul 21, 2004 05:24:40.41
!MESSAGE Exception launching the Eclipse Platform:
An exception occurred while writing to the platform log:
java.io.FileNotFoundException: /etc/workspace/.metadata/.config/workspace/.metadata/.log (No such file or directory)"

The file workspace/.metadata/.log exists and shows this:
"ENTRY org.eclipse.team.cvs.core 4 -14 July 14
!MESSGE Terminated with fatal signal 11"

What should I try? Seems related to this thread.

yangel88 08-10-2004 04:20 PM

I have discovered a strange solution to overcome the unsatisfiedLinkError. I built eclipse3.0 from source using the command "build -os linux -ws gtk -arch x86 target install" rather than "build -os linux -ws gtk -arch amd64 target install", the result generated from this command can be run on the amd64 machine! I am now wondering why? Can anyone help?


All times are GMT -5. The time now is 11:40 AM.