Subversion 1.0.4-rc1 gets errors building the Java bindings. It seems to be a badly named path. Reproducible: Always Steps to Reproduce: 1. emerge subversion Actual Results: make[1]: Entering directory `/var/tmp/portage/subversion-1.0.4-r1/work/subversion-1.0.4/subversion/bindings/java/javahl/src' CLASSPATH=../cls:./../cls:$CLASSPATH none/bin/javac -d ../cls -g org/tigris/subversion/javahl/BlameCallback.java org/tigris/subversion/javahl/ClientException.java org/tigris/subversion/javahl/DirEntry.java org/tigris/subversion/javahl/JNIError.java org/tigris/subversion/javahl/LogMessage.java org/tigris/subversion/javahl/NodeKind.java org/tigris/subversion/javahl/Notify.java org/tigris/subversion/javahl/PromptUserPassword.java org/tigris/subversion/javahl/PromptUserPassword2.java org/tigris/subversion/javahl/PromptUserPassword3.java org/tigris/subversion/javahl/PropertyData.java org/tigris/subversion/javahl/Revision.java org/tigris/subversion/javahl/SVNClient.java org/tigris/subversion/javahl/SVNClientInterface.java org/tigris/subversion/javahl/SVNClientSynchronized.java org/tigris/subversion/javahl/Status.java /bin/sh: line 1: none/bin/javac: No such file or directory make[1]: *** [classnoinst.stamp] Error 127 make[1]: Leaving directory `/var/tmp/portage/subversion-1.0.4-r1/work/subversion-1.0.4/subversion/bindings/java/javahl/src' make: *** [all-recursive] Error 1 !!! ERROR: dev-util/subversion-1.0.4-r1 failed. !!! Function src_compile, Line 156, Exitcode 2 !!! Compilation failed Expected Results: Subversion should be compiled and merged
Make sure that you have a jdk configured correctly with java-config. The none part in the javac command comes from java-config returning none instead of a path on jdk-config --jdk-home
That is a work-around, not a resolution. I don't have a JDK installed and configured and this should not require me to stop my world update, install a java jdk, and resume the world update. Thats why we have dependancies. If you're suggestion were a valid resolution, we wouldn't have portage at all, we'd all just use the raw tarballs and wing it. Secondly, these java bindings are not properly controlled by the java USE flag, which has no affect on if they are built or not. I don't actually care to have the java bindings: i dont need them. Thus, when i did 'USE="-java" emerge subversion" the compile should have ran smoothly, skipping the java bindings, but it doesn't. I don't mean to be a pain in the ass, but this bug was prematurely marked resolved. It needs to be reopened and fixed properly. If I find the time, I'll fix it myself. If anyone else has the same problem and fixes it, just as well.
The jdk is a clear dependency for subversion, so it should be installed (what is the output of "java-config -L"? I'll check about the building of subversion with USE="-java"
Turns out i did have the blackdown-jdk installed, but i had to add it to my paths manually. This is surely not the right way for things to be. Also, i've tried with -java and no go. The ebuild doesn't account for it.
Adding to the path is not necessary, please use "java-config -S" This should happen most times automatically. As another point, USE=-java works perfectly for me. Have you possibly put java in the package use flags (/etc/portage/package.use) for subversion? Alternatively remember that when continuing an ebuild (or using the ebuild command) the environment is not updated, but the retained version is used.
