Tested on ppc64. Ebuild attached.
Created attachment 123026 [details] Cacao 0.98 ebuild
*** Bug 162277 has been marked as a duplicate of this bug. ***
Well, it almost works on x86. You need one unset JAVAC at the beginnig. Cacao configure does not add -bootclasspath to the javac if it is not autodetected. And dosym /opt/${PN}/bin/cacao /usr/bin/cacao shoud be dosym /opt/${P}/bin/cacao /usr/bin/cacao And it sort of colides with jamvm. You could actually have both on the same machine, if you remove /usr/lib/libjvm.la /usr/lib/libjvm.so
> Well, it almost works on x86. You need one unset JAVAC > at the beginning. Cacao configure does not add -bootclasspath to the javac if > it is not autodetected. Okay, I mostly adapted the previous build so this could be a problem there too. I didn't run across this problem with JAVAC, it should be able to pick the bootclasspath. > And > dosym /opt/${PN}/bin/cacao /usr/bin/cacao > should be > dosym /opt/${P}/bin/cacao /usr/bin/cacao Likewise, this image must be present in the previous build. > And it sort of colides with jamvm. You could actually have both on the same > machine, if you remove > /usr/lib/libjvm.la > /usr/lib/libjvm.so This is a problem with them both installing in the same location I guess, I've run across it doing manual builds.
(In reply to comment #4) Behaviour with JAVAC is actually correct - if you opt to specify compiler, than this compiler maybe has it's own parameters for configuring bootclasspath... If you use JAVAC="my_javac_compliler -bootclasspath=/opt/gnu-classpath/.." it works.
Bumped to 0.99.4. from java overlay.
