Eclipse problems under x86_64 / 10.0
Hi. I just updated to 10.0, and everything seems to work except Eclipse. I get an unsatisfied link error. The error message doesn't make much sense since the file it is complaining is present. Anyone know what's going on? I suspect 32 vs 64 bit issues, but SuSE's approach to java configuration is so bizarre I haven't been able to figure it out. Thanks! !SESSION 2005-10-24 14:29:27.405 ----------------------------------------------- eclipse.buildId=I20050627-1435 java.version=1.5.0_03 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Command-line arguments: -os linux -ws gtk -arch x86 -data /home/mike/.eclipse !ENTRY org.eclipse.osgi 2005-10-24 14:29:31.189 !MESSAGE Application error !STACK 1 java.lang.UnsatisfiedLinkError: /home/mike/.eclipse/org.eclipse.platform_3.1.1/configuration/org.eclipse.osgi/bundles/69/1/.cp/libswt-pi-gtk-3138.so: /home/mike/.eclipse/org.eclipse.platform_3.1.1/configuration/org.eclipse.osgi/bundles/69/1/.cp/libswt-pi-gtk-3138.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:1751) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1660) at java.lang.Runtime.loadLibrary0(Runtime.java:822) at java.lang.System.loadLibrary(System.java:992) at org.eclipse.swt.internal.Library.loadLibrary(Library.java:123) 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:122) at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:381) at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:155) at org.eclipse.ui.internal.ide.IDEApplication.createDisplay(IDEApplication.java:128) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:79) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163) 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:585) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334) at org.eclipse.core.launcher.Main.basicRun(Main.java:278) at org.eclipse.core.launcher.Main.run(Main.java:973) at org.eclipse.core.launcher.Main.main(Main.java:948) !ENTRY org.eclipse.osgi 2005-10-24 14:29:31.193 !MESSAGE Bundle update@plugins/org.eclipse.platform.source.linux.gtk.x86_3.1.0/ [45] was not resolved. !SUBENTRY 1 org.eclipse.osgi 2005-10-24 14:29:31.194 !MESSAGE Missing host org.eclipse.platform.source_3.1.0. !SESSION 2005-10-24 14:38:32.144 ----------------------------------------------- eclipse.buildId=I20050627-1435
hi, * Mike <mikedl@comcast.net> [051024 20:57]:
Hi. I just updated to 10.0, and everything seems to work except Eclipse. I get an unsatisfied link error. The error message doesn't make much sense since the file it is complaining is present.
Anyone know what's going on? I suspect 32 vs 64 bit issues, but SuSE's approach to java configuration is so bizarre I haven't been able to figure it out.
I don't really know much about eclipse, but as this is 32bit only, it probably is sth. different. A quick look gave me: ~/.eclipse/ > find . -name libswt-pi-gtk-3138.so ./org.eclipse.platform_3.1.1/configuration/org.eclipse.osgi/bundles/68/1/.cp/libswt-pi-gtk-3138.so ~/.eclipse/ > So, only the path below is wrong, it states */69/1/* But, don't ask me why.
Thanks! java.lang.UnsatisfiedLinkError: /home/mike/.eclipse/org.eclipse.platform_3.1.1/configuration/org.eclipse.osgi/bundles/69/1/.cp/libswt-pi-gtk-3138.so: /home/mike/.eclipse/org.eclipse.platform_3.1.1/configuration/org.eclipse.osgi/bundles/69/1/.cp/libswt-pi-gtk-3138.so: -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com
Regards, Stefan -- SUSE LINUX Products GmbH, Maxfeldstr. 5 Mail: sf@suse.de D-90409 Nuernberg Phone: +49-911-740 53 - 0 GPG 1024D/91614BBC B226 E3DA 37B0 2170 7403 D19C 18AF E579 9161 4BBC
Mike wrote:
Hi. I just updated to 10.0, and everything seems to work except Eclipse. I get an unsatisfied link error. The error message doesn't make much sense since the file it is complaining is present.
Anyone know what's going on? I suspect 32 vs 64 bit issues, but SuSE's approach to java configuration is so bizarre I haven't been able to figure it out.
Thanks!
<snip>
java.lang.UnsatisfiedLinkError: /home/mike/.eclipse/org.eclipse.platform_3.1.1/configuration/org.eclipse.osgi/bundles/69/1/.cp/libswt-pi-gtk-3138.so: /home/mike/.eclipse/org.eclipse.platform_3.1.1/configuration/org.eclipse.osgi/bundles/69/1/.cp/libswt-pi-gtk-3138.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:1751) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1660) at java.lang.Runtime.loadLibrary0(Runtime.java:822) at java.lang.System.loadLibrary(System.java:992)
</snip> Looks like Eclipse's JNI code was compiled for 32-bit Java while you're trying to load 64-bit code or vice-versa. Have you tried to do an ldd on /home/mike/.eclipse/org.eclipse.platform_3.1.1/configuration/org.eclipse.osgi/bundles/69/1/.cp/libswt-pi-gtk-3138.so ?
You also might try upgrading to Netbeans. It is more advanced in many ways than Eclipse. Also runs 100% Java so no bittedness to worry about. Grab the latest 64 bit JVM @ Sun and load the latest daily build of NB5. Can't hurt anything. Need more info let me know. Chuck Davis P.S. Last sighting of my packages was in PA heading for Seattle. So I have not tested ANYTHING on 10.0 yet. Yes, I ALWAYS buy at least one package for the Company and one for myself to reward those who do the work I like. On Tuesday 25 October 2005 1:20 pm, Pierre Patino wrote:
Mike wrote:
Hi. I just updated to 10.0, and everything seems to work except Eclipse. I get an unsatisfied link error. The error message doesn't make much sense since the file it is complaining is present.
Anyone know what's going on? I suspect 32 vs 64 bit issues, but SuSE's approach to java configuration is so bizarre I haven't been able to figure it out.
Thanks!
<snip>
java.lang.UnsatisfiedLinkError: /home/mike/.eclipse/org.eclipse.platform_3.1.1/configuration/org.eclipse. osgi/bundles/69/1/.cp/libswt-pi-gtk-3138.so: /home/mike/.eclipse/org.eclipse.platform_3.1.1/configuration/org.eclipse. osgi/bundles/69/1/.cp/libswt-pi-gtk-3138.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:1751) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1660) at java.lang.Runtime.loadLibrary0(Runtime.java:822) at java.lang.System.loadLibrary(System.java:992)
</snip>
Looks like Eclipse's JNI code was compiled for 32-bit Java while you're trying to load 64-bit code or vice-versa. Have you tried to do an ldd on /home/mike/.eclipse/org.eclipse.platform_3.1.1/configuration/org.eclipse.os gi/bundles/69/1/.cp/libswt-pi-gtk-3138.so ?
On Tuesday 25 October 2005 15:20, Pierre Patino wrote:
Looks like Eclipse's JNI code was compiled for 32-bit Java while you're trying to load 64-bit code or vice-versa. Have you tried to do an ldd on /home/mike/.eclipse/org.eclipse.platform_3.1.1/configuration/org.eclipse.os gi/bundles/69/1/.cp/libswt-pi-gtk-3138.so ?
Yes, it looks like the eclipse startup script is trying to run 32-bit eclipse code under the 64 bit JVM. I don't know why SUSE would include mismatched components, but I'm pretty sure there's nothing odd about my setup that would cause this. I've installed the 64 bit eclipse from eclipse.org and it seems to work well so far. I wish the SUSE packagers had sorted this out - now I'll have to tweak all the 10.0 installs by hand... mike.
Mike wrote:
I've installed the 64 bit eclipse from eclipse.org and it seems to work well so far. I wish the SUSE packagers had sorted this out - now I'll have to tweak all the 10.0 installs by hand...
You can also start Eclipse with the "-vm" argument to tell it to use a specific JVM. I have both 32 and 64-bit JVMs installed on my system, and I use them both. So this argument helps me use the right JVM every time. It also makes it easy to switch JVMs if you need to. If you dont use the "-vm" argument then eclipse simply looks in the path and uses the first JVM it finds. Mark
participants (5)
-
Chuck Davis -
Mark Horton -
Mike -
Pierre Patino -
Stefan Fent