Eclipse SDK-3.0M7
Hello, I'm trying to run Eclipse on SuSE 9.0 for AMD64. The x86_64 installation is working realtively fine ( I still don't have hardware acceleration for Asus 9600XT and the SyncMaster959NF is not recognized). Yast2 says everything installed is up-to-date. This is what I did with the (still unfulfilled) hope of starting Eclipse: 1) Installed 64-bit Blackdown-1.4.2 j2sdk in /usr/local/. I used the profile.local file as advised by SuSe to add the sdk to the PATH and also added conf files in /etc/java. $ java -version java version "1.4.2-rc1" Java(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.4.2-rc1) Java HotSpot(TM) 64-Bit Server VM (build Blackdown-1.4.2-rc1, mixed mode) 2) Downloaded eclipse-SDK-3.0M7-linux-motif.zip in /opt $ cd /opt $ chmod 777 eclipse-SDK-3.0M7-linux-motif.zip $ unzip eclipse-SDK-3.0M7-linux-motif.zip $ cd eclipse $ /.eclipse the result was a terminal full of errors, so I Googled. http://lists.suse.com/archive/suse-amd64/2003-Dec/0086.html removed the errros in the terminal. But then after seeing the splashscreen I got the error box "problems at startup". The .log file read: !SESSION ---------------------------------------------------------------------- !ENTRY org.eclipse.core.launcher 4 0 Mar 05, 2004 19:14:28.561 !MESSAGE Exception launching the Eclipse Platform: !STACK java.lang.UnsatisfiedLinkError: /opt/eclipse/plugins/org.eclipse.swt.motif_3.0.0/os/linux/x86/libswt-motif-3038.so: /opt/eclipse/plugins/org.eclipse.swt.motif_3.0.0/os/linux/x86/libswt-motif-3038.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.motif.OS.<clinit>(OS.java:20) at org.eclipse.swt.graphics.Device.<clinit>(Device.java:89) at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:279) at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:149) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:41) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:257) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:104) 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:279) at org.eclipse.core.launcher.Main.run(Main.java:742) at org.eclipse.core.launcher.Main.main(Main.java:581) so I checked if the file was there and it WAS there: r166022:/opt/eclipse/plugins/org.eclipse.swt.motif_3.0.0/os/linux/x86 # l total 480 drwxrwxr-x 2 root root 304 2004-02-13 02:26 ./ drwxrwxr-x 3 root root 72 2004-02-13 02:26 ../ -rwxr-xr-x 1 root root 2297 2004-02-13 02:26 libswt-awt-motif-3038.so* -rwxr-xr-x 1 root root 15008 2004-02-13 02:26 libswt-gnome-motif-3038.so* -rwxr-xr-x 1 root root 5289 2004-02-13 02:26 libswt-gtk-motif-3038.so* -rwxr-xr-x 1 root root 21763 2004-02-13 02:26 libswt-kde-motif-3038.so* -rwxr-xr-x 1 root root 382789 2004-02-13 02:26 libswt-motif-3038.so* -rwxr-xr-x 1 root root 51776 2004-02-13 02:26 libswt-mozilla-motif-3038.so* ... another 6 or so hours of Googling and experimenting with things like: export LD_LIBRARY_PATH=/opt/eclipse/plugins/org.eclipse.swt.motif_3.0.0/os/linux/x86/ from: http://groups.google.de/groups?hl=de&lr=&ie=UTF-8&oe=UTF-8&threadm=bifv3g%2439si%241%40news.boulder.ibm.com&rnum=20&prev=/groups%3Fq%3Declipse%2BUnsatisfiedLinkError%26start%3D10%26hl%3Dde%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26scoring%3Dd%26selm%3Dbifv3g%252439si%25241%2540news.boulder.ibm.com%26rnum%3D20 and nothing wokrked. I also tried to install the GTK version - the result was equally disastrous: !SESSION ---------------------------------------------------------------------- !ENTRY org.eclipse.core.launcher 4 0 Mar 05, 2004 19:32:42.808 !MESSAGE Exception launching the Eclipse Platform: !STACK java.lang.UnsatisfiedLinkError: /opt/eclipse/plugins/org.eclipse.swt.gtk_3.0.0/os/linux/x86/libswt-pi-gtk-3038.so: /opt/eclipse/plugins/org.eclipse.swt.gtk_3.0.0/os/linux/x86/libswt-pi-gtk-3038.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:279) at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:149) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:41) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:257) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:104) 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:279) at org.eclipse.core.launcher.Main.run(Main.java:742) at org.eclipse.core.launcher.Main.main(Main.java:581) libswt-pi-gtk-3038.so is of course there where it should be: r166022:/opt/eclipse/plugins/org.eclipse.swt.gtk_3.0.0/os/linux/x86 # l total 564 drwxrwxr-x 2 root root 296 2004-02-13 02:27 ./ drwxrwxr-x 3 root root 72 2004-02-13 02:27 ../ -rwxr-xr-x 1 root root 43319 2004-02-13 02:27 libswt-atk-gtk-3038.so* -rwxr-xr-x 1 root root 6583 2004-02-13 02:27 libswt-awt-gtk-3038.so* -rwxr-xr-x 1 root root 14103 2004-02-13 02:27 libswt-gnome-gtk-3038.so* -rwxr-xr-x 1 root root 190447 2004-02-13 02:27 libswt-gtk-3038.so* -rwxr-xr-x 1 root root 51776 2004-02-13 02:27 libswt-mozilla-gtk-3038.so* -rwxr-xr-x 1 root root 259184 2004-02-13 02:27 libswt-pi-gtk-3038.so* Does somebody have a clue how I can get Eclipse working ? Thanks in advance, Stanimir
On Fri, 05 Mar 2004 20:10:10 +0100
Stanimir Arnaudov
1) Installed 64-bit Blackdown-1.4.2 j2sdk in /usr/local/. I used the profile.local file as advised by SuSe to add the sdk to the PATH and also added conf files in /etc/java.
$ java -version java version "1.4.2-rc1" Java(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.4.2-rc1) Java HotSpot(TM) 64-Bit Server VM (build Blackdown-1.4.2-rc1, mixed mode)
2) Downloaded eclipse-SDK-3.0M7-linux-motif.zip in /opt
That package includes native 32bit libraries. You cannot link them with a 64bit JVM. Run Eclipse in a 32bit JVM instead, that works fine. Rebuilding it from scratch may also help, but I'm not sure if their code base is really 64bit clean. Using the 32bit JVM like it is shipped with the distribution is certainly the easiest way. -Andi
Run Eclipse in a 32bit JVM instead, that works fine. Rebuilding it from scratch may also help, but I'm not sure if their code base is really 64bit clean.
No, the Eclipse code is not yet 64 bit clean, but it is well on it's way. The current snapshot of the amd64 version of SWT (representing the biggest part to be ported) will allow you to run 3.0M7 without any major problems (I have only seen one problem which I think is JVM-related). To get this running, I believe you will need to do some building yourself, which may require some experience of Java and C. However, the amd64 support is planned to go into the 3.0M8 release which is just a few weeks away (March 26). Progress may be monitored on https://bugs.eclipse.org/bugs/show_bug.cgi?id=37775 . While on the topic: there should be a release of 1.4.2 for amd64 from Blackdown any day now. There is also the 1.5-B1 JDK to get from Sun Early Access - I have not tried running Eclipse on that beast though. btw, from working with this, I learned that Sun has decided to have their JDK returning the archicture identifier "amd64" instead of "x86_64" (even after the Intel announcements) . Anyone knows if there are any plans to rename the x86_64 identifier used for Linux architecture? __________________________________ Do you Yahoo!? Yahoo! Search - Find what you�re looking for faster http://search.yahoo.com
On Fri, 5 Mar 2004 16:01:09 -0800 (PST)
Johan Backlund
btw, from working with this, I learned that Sun has decided to have their JDK returning the archicture identifier "amd64" instead of "x86_64" (even after the Intel announcements) . Anyone knows if there are any plans to rename the x86_64 identifier used for Linux architecture?
No plans at all. It's very unlikely that uname will change. The only thing that may change would be distribution branding (essentially what's printed on the CD and in "login"). But that is not critical because it's normally not parsed by any scripts. -Andi
participants (3)
-
Andi Kleen
-
Johan Backlund
-
Stanimir Arnaudov