[eclipse-maintainers] Re: Eclipse 3.0 Running on Kaffe
Karl Trygve Kalleberg
karltk@gentoo.org
Sat, 15 Jan 2005 02:56:03 +0100
Grzegorz B. Prokopski wrote:
> On Tue, 2005-11-01 at 00:04 -0600, Jerry Haltom wrote:
>
>>The sources for these packages is located at:
>>
>>http://kyoto.larvalstage.net/ubuntu/warty
>>
>>These are compiled for my desktop installation of Ubuntu warty/hoary.
>>The source packages should be re-compilable on unstable. PLEASE
>>RECOMPILE!
>
>
> I did, but using free-java-sdk. Unfortunatelly jikes we have in Debian
> seems to be not good enough to compile it. After a while I got this:
>
> runtime.jar:
> [mkdir] Created
> dir: /mnt/beta/tmp/eclipse-build/eclipse-3.0.1/source-tree/plugins/org.eclipse.core.runtime/temp.folder/runtime.jar.bin
> [javac] Compiling 158 source files
> to /mnt/beta/tmp/eclipse-build/eclipse-3.0.1/source-tree/plugins/org.eclipse.core.runtime/temp.folder/runtime.jar.bin
> [...]
> [javac] Found 2 semantic errors compiling
> "/mnt/beta/tmp/eclipse-build/eclipse-3.0.1/source-tree/plugins/org.eclipse.core.runtime/src/org/eclipse/core/internal/registry/ExtensionRegistry.java":
>
> [javac] 52. ListenerInfo
> listenerInfo = (ListenerInfo) listenerInfos[i];
> [javac] ^----------^
> [javac] *** Semantic Error: The static type
> "org.eclipse.core.internal.registry.ExtensionRegistry
> $ExtensionEventDispatcherJob" must use a qualified name to access the
> non-static member type
> "org.eclipse.core.internal.registry.ExtensionRegistry$ListenerInfo" of
> the enclosing type
> "org.eclipse.core.internal.registry.ExtensionRegistry".
>
>
> [javac] 52. ListenerInfo
> listenerInfo = (ListenerInfo) listenerInfos[i];
> [javac]
> ^----------^
> [javac] *** Semantic Error: The static type
> "org.eclipse.core.internal.registry.ExtensionRegistry
> $ExtensionEventDispatcherJob" must use a qualified name to access the
> non-static member type
> "org.eclipse.core.internal.registry.ExtensionRegistry$ListenerInfo" of
> the enclosing type
> "org.eclipse.core.internal.registry.ExtensionRegistry".
>
>
>
> Is this a jikes bug? Or is it missing some option to accept such code?
> Any ideas how can we (slightly) alter the source to make it work?
FWIW, ever since the summer of 2003, I've tried building the Eclipse
using Jikes unmodified, but that's never worked.
From talking to the Eclipse developers, I also get the impression that
they are not interested in spending time on maintaining workarounds for
Jikes "features".
There's even been talk about bootstrapping Eclipse with their own Java
compiler, but afaik, nobody's made out an issue about it in their issue
tracker yet.
-- Karl T