dev-java/gnu-classpath: Build with regular javac instead of ECJ
authorJames Le Cuirot <chewi@gentoo.org>
Sun, 10 Jan 2016 20:34:46 +0000 (20:34 +0000)
committerJames Le Cuirot <chewi@gentoo.org>
Sun, 10 Jan 2016 20:50:04 +0000 (20:50 +0000)
commit040c1d83edf3fa7992664595216f20e53ee54761
tree4eefd8fc04055ffe2c5aec6459271dfeaaa1e84e
parent3c04ef02813e90548ffa0c2b8c2dca8a77d9bbd7
dev-java/gnu-classpath: Build with regular javac instead of ECJ

I believe GNU Classpath favoured ECJ because it was the only FOSS
compiler capable of building it at the time. OpenJDK is now preferable
and the statement in configure.ac that not using ECJ results in
com.sun.tools.javac not being included doesn't hold true.

The simplification is nice but this also avoids a race condition
occuring with ECJ on ppc. This is almost certainly a CACAO issue. See
http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=2782.

Package-Manager: portage-2.2.26
dev-java/gnu-classpath/gnu-classpath-0.98-r5.ebuild [moved from dev-java/gnu-classpath/gnu-classpath-0.98-r4.ebuild with 81% similarity]