> The problem is that ecj-bootstrap is the source of the failure. It somehow
> needs some setup from java-gcj-compat to fullfill its job. You can easily
> verify this by installing java-gcj-compat and compiling a simple
> HelloWorld.java with /usr/bin/ecj-bootstrap which will work. Removing
> java-gcj-compat and it will fail. However, where the problem is is still
> to be investigated.
compiling HelloWorld fails:
[parsing HelloWorld.java - #1/1]
----------
1. ERROR in HelloWorld.java
(at line 1)
class HelloWorld {
^
The type java.lang.Object cannot be resolved. It is indirectly referenced from
required .class file\s
----------
1 problem (1 error)
ecj-bootstrap does use gij to run the ecj.jar file, it finds
/usr/lib/jvm/java-1.4.2-gcj-4.0-1.4.2.0/jre/lib/rt.jar (pointing to
libgcj-4.0.jar) only if java-gcj-compat is installed.
explicitely adding -bootclasspath /usr/share/java/libgcj-4.0.jar works
around that failure. Is this the right thing to do, or is the real
problem that ecj derives the bootclasspath implicitely from the
runtime used to run ecj?
Matthias
_______________________________________________
pkg-java-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
