Bug 141477 - dev-java/kaffe-1.1.7 fails because of dev-java/java-config
|
Bug#:
141477
|
Product: Gentoo Linux
|
Version: 2006.0
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: java@gentoo.org
|
Reported By: schrangl@gmx.net
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: dev-java/kaffe-1.1.7 fails because of dev-java/java-config
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2006-07-23 03:36 0000
|
If kaffe finds the executable "jar" somewhere in the PATH it will be used
during compilation, otherwise it will use its own. The java-config packages
provides a script (/usr/bin/jar) as a wrapper for the selected VM's jar
executable. If no jre/jdk is installed, java-config's script fails, and so does
the kaffe build, which tries to use it. One way to resolve this would
(possibly) be to install java-config-* after kaffe, since it doesn't seem to be
needed before anyways.
It's not "Core system"...
Installing java-config after kaffe isn't really possible, since kaffe (and all
vms) depend on java-config during their postinstall.
The better way would be to find a way to force kaffe to use it's own jar.
Adding export FASTJAR="$S/external/gcc/fastjar/fastjar" to src_compile force
kaffe to use it's own jar. I don't know if it's a good solution.
Using fastjar is probably a pretty good solution> It can actually be packaged
separately, and we have ebuilds kicking around our overlays somewhee I'm quite
sure.
Fixed with 1.1.7-r1. Thanks for reporting!