| Who to "sue": unable to start Eclipse 3.1 on Mac Pro! [message #172127] |
Fri, 22 September 2006 08:13  |
Eclipse User |
|
|
|
Originally posted by: doki.episteme.no
I have just purchased the lastest Mac Pro Dual Core Xeon, only to discover
that Eclipse 3.1 is unable to start on it. I posted the stack dump at the
end of this note.
Eclipse 3.2, however, works perfectly on that platform. The trouble is
that I cannot start using it right away. I use Borland Together for
Eclipse, a product which requires Eclipse 3.1. As a result, I am unable to
use (rather expensive) Borland Together on my (rather expensive) Mac Pro.
Grrrr...
Well, this is probably not Borlands fault, to be exact, but it is Borland
that got the money, isnŽt it? I cannot expect this problem to be solved in
foreseeable future, however. Firstly, Eclipse 3.1 has been obsolete for a
while now, so the bug-fix focus is already on 3.2. Secondly, there is a
possibility that this is not Eclipses fault in the first place. How about
Apple? They ported Java on this platform only recently. What about them
not getting it quite right? For example, I have no trouble with running
Eclipse 3.1 on an elderly iMac G5 machine.
The question is: who to nag? Borland or Apple? Or does the problem belong
to Eclipse anyway?
Here is the error message I get:
java.lang.UnsatisfiedLinkError:
/Users/gorandostanic/Borland/Together/Developer2006/eclipse/ configuration/org.eclipse.osgi/bundles/287/1/.cp/libswt-pi-c arbon-3138.jnilib:
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:12 3)
at org.eclipse.swt.internal.carbon.OS.<clinit>(OS.java:20)
at org.eclipse.swt.widgets.Display.createDisplay(Display.java:8 56)
at org.eclipse.swt.widgets.Display.create(Display.java:836)
at org.eclipse.swt.graphics.Device.<init>(Device.java:118)
at org.eclipse.swt.widgets.Display.<init>(Display.java:676)
at org.eclipse.swt.widgets.Display.<init>(Display.java:667)
at
org.eclipse.ui.internal.Workbench.createDisplay(Workbench.ja va:394)
at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:155)
at
org.eclipse.ui.internal.ide.IDEApplication.createDisplay(IDE Application.java:128)
at
org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:79)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:226)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:376)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:163)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.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)
|
|
|
| Re: Who to "sue": unable to start Eclipse 3.1 on Mac Pro! [message #172152 is a reply to message #172127] |
Fri, 22 September 2006 09:37  |
| Eclipse User |
|
|
|
Originally posted by: dmsubs.NOSPAM.consertum.com
Suggest you:
1. Speak to Borland technical support
2. Try it with Rosetta
--
Derek
Doki wrote:
> I have just purchased the lastest Mac Pro Dual Core Xeon, only to
> discover that Eclipse 3.1 is unable to start on it. I posted the stack
> dump at the end of this note.
> Eclipse 3.2, however, works perfectly on that platform. The trouble is
> that I cannot start using it right away. I use Borland Together for
> Eclipse, a product which requires Eclipse 3.1. As a result, I am unable
> to use (rather expensive) Borland Together on my (rather expensive) Mac
> Pro. Grrrr...
>
> Well, this is probably not Borlands fault, to be exact, but it is
> Borland that got the money, isnŽt it? I cannot expect this problem to be
> solved in foreseeable future, however. Firstly, Eclipse 3.1 has been
> obsolete for a while now, so the bug-fix focus is already on 3.2.
> Secondly, there is a possibility that this is not Eclipses fault in the
> first place. How about Apple? They ported Java on this platform only
> recently. What about them not getting it quite right? For example, I
> have no trouble with running Eclipse 3.1 on an elderly iMac G5 machine.
>
> The question is: who to nag? Borland or Apple? Or does the problem
> belong to Eclipse anyway?
> Here is the error message I get:
>
> java.lang.UnsatisfiedLinkError:
> /Users/gorandostanic/Borland/Together/Developer2006/eclipse/ configuration/org.eclipse.osgi/bundles/287/1/.cp/libswt-pi-c arbon-3138.jnilib:
>
> 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:12 3)
> at org.eclipse.swt.internal.carbon.OS.<clinit>(OS.java:20)
> at org.eclipse.swt.widgets.Display.createDisplay(Display.java:8 56)
> at org.eclipse.swt.widgets.Display.create(Display.java:836)
> at org.eclipse.swt.graphics.Device.<init>(Device.java:118)
> at org.eclipse.swt.widgets.Display.<init>(Display.java:676)
> at org.eclipse.swt.widgets.Display.<init>(Display.java:667)
> at
> org.eclipse.ui.internal.Workbench.createDisplay(Workbench.ja va:394)
> at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:155)
> at
> org.eclipse.ui.internal.ide.IDEApplication.createDisplay(IDE Application.java:128)
>
> at
> org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:79)
> at
> org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:226)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:376)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:163)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.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)
>
>
>
|
|
|
| Re: Who to "sue": unable to start Eclipse 3.1 on Mac Pro! [message #172184 is a reply to message #172127] |
Fri, 22 September 2006 13:57 |
| Eclipse User |
|
|
|
Originally posted by: jefmyers.us.ibm.com
Doki,
Eclipse 3.1 does not run on OS X/x86 out of the box. This was a
limitation of Eclipse, not a problem with Sun/Java. I'd be surprised if
Borland listed that combination as a supported platform for their
product. Happily, like you said this issue has been fixed and Eclipse
3.2 works fine on that platform. If you're comfortable hacking your
Eclipse platform underlying your Borland installation (and possibly
voiding any support Borland provides), you can apply the patch attached
to this bug report: https://bugs.eclipse.org/bugs/show_bug.cgi?id=98889
to get Eclipse 3.1.2 working on OS X/x86.
Hope this helps,
- Jeff
|
|
|
|
Powered by
FUDForum. Page generated in 0.08420 seconds
] 
Search
Help
Register
Login
Home
