Lennart Sorensen writes: > Well xulrunner seems to have an issue with javac based on this last part > of the build log: > > Compiling Java interface classes > find _javagen -name "*.java" > java.files > /usr/lib/jvm/java-gcj/bin/javac -source 1.4 -classpath . -d . -sourcepath > _javagen @java.files > Exception in thread "main" java.lang.NoClassDefFoundError: > org.eclipse.jdt.core.compiler.IProblem > <<No stacktrace available>> > make[3]: *** [org/mozilla/xpcom/.class_done] Error 1 > make[3]: Leaving directory > `/build/buildd/xulrunner-1.8.0.5/extensions/java/xpcom/interfaces' > make[2]: *** [tier_99] Error 2 > make[2]: Leaving directory `/build/buildd/xulrunner-1.8.0.5' > make[1]: *** [default] Error 2 > make[1]: Leaving directory `/build/buildd/xulrunner-1.8.0.5' > make: *** [build-stamp] Error 2 > > I seem to recall a bunch of java problems on arm in the past with > packages having to use a different java compiler on arm compared to > what was used on other architectures. I don't remember if that was > ever fixed. I think it was jikes that was broken, and gcj that worked > for the particular packages.
please check building with gcj-4.1 from experimental, and with an ecj-bootstrap rebuilt with gcj-4.1. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
