- This topic has 31 replies, 5 voices, and was last updated 13 years, 5 months ago by support-tony.
-
AuthorPosts
-
Clayton E. CramerMember@support-tony wrote:
Clayton,
The other jdk file that I referred to is the one without the “-rpm” in the name. So something like “jdk-6u26-linux-i586.bin”. The steps I was referring to are those mentioned here: https://www.genuitec.com/forums/topic/trying-to-install-myeclpse-9-0-under-suse-9-0/#post-317550
You seemed to install eclipse classic OK (yes, it is just an extract) but had trouble starting eclipse. Did you install Mozilla, through Yast, as I’d done in the post linked to above? Again, for me, eclipse classic installed and ran just fine, with the MyEclipse update site install appearing to work OK.
I don’t know why you are getting the “cannot execute binary file” error, since I can execute it fine. The only thing I can think of is that your system is a 64 bit system but the downloaded JDK is a 32 bit version. However, I can’t check this myself as I can’t find a 64 bit SuSE 9 distribution (the one I installed is 32 bit). This could possibly be a reason for many of the problems you’ve unfortunately had trying to install MyEclipse.
Mozilla 1.6 is already installed. When I execute pulse-installer, I get the following log file:
!SESSION 2011-06-29 08:52:48.526 ———————————————–
eclipse.buildId=unknown
java.version=1.5.0_04
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!ENTRY org.eclipse.osgi 4 0 2011-06-29 08:52:53.570
!MESSAGE Application error
!STACK 1
java.lang.IllegalStateException: initialize() must be called first; not yet initialized
at com.genuitec.pulse2.client.common.PulseClientPaths.getInstance(Unknown Source)
at com.genuitec.pulse2.client.installer.ui.application.InstallerApplication.start(Unknown Source)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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.equinox.launcher.Main.invokeFramework(Main.java:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
support-tonyKeymasterClayton,
I’m not sure what to suggest except maybe the first JDK you installed (which you mentioned on the first page of this topic) was a 64 bit version of the JDK and now that is being picked up in preference to any other JDK you’ve installed, or tried to install. Many of your problems might be cause by a 64 bit/32 bit conflict somewhere.
I go back to the first steps I tried on a fresh SuSE 9.0 installation: https://www.genuitec.com/forums/topic/trying-to-install-myeclpse-9-0-under-suse-9-0/#post-317550
Have you tried these steps (except Mozilla install), with the non-rpm JDK bin file? Perhaps telling the MyEclipse installer precisely where the 32 bit VM is (assuming you’re installing a 32 bit version of MyEclipse, which you seem to be) will do the trick.Other than that, could you just try uninstalling all JDKs, JREs, eclipse, MyEclipse installations or partial installations that you have, deleting the hidden files, like .myeclipse… or .pulse.. files/directories in your home directory, and starting again with a clean 32 bit JDK, a clean download of MyEclipse installer and follow the steps I mentioned above.
Personally, I’ve tried all of the methods for installing MyEclipse (off-line installer, archived eclipse update site and pulse) on my installation of 32 bit SuSE 9.0 and have had no problems at all, so it’s difficult to debug this problem from here, since I can’t replicate what you are seeing.
-
AuthorPosts