I feel strange filing a bug against an abuild I helped build, but I am having a problem updating ming through portage, instead of using the old ebuild in a portage overlay I created. The problem is this: the java-config patch for ming-0.3.0 is successfully applied, but it does not seem to point to the correct jvm during compilation. The reason for the error is that I did not follow the guidelines for updating my java configuration by correctly setting the java-config-1 VM. I have not written a patch yet for this problem, as it may be considered superfluous to tag a java instruction message onto a non-java ebuild, but I will at least correct the ebuild soon, and then you can at least consider updating it. If this is an unneeded change, please let me know and I will not write the updated ebuild. All that needs to be added is a message directing the user to http://www.gentoo.org/proj/en/java/java-upgrade.xml after a failed compilation (die) of the java extension for ming. Alternatively, one could consider changing the java-config patch to use (if it works) java-config-1 or java-config-2 instead of java-config, both of which I think return an explanatory error and a link to the correct gentoo java update page. - Best Adam Penser
Could you please post the error log that you are getting?
I fixed the problem by following the instructions on the gentoo java update page, but I will unset the java-config-1 VM to get the problem again: After unsetting, in the src_compile section I got a brief warning of `java-config --jdk-home`/bin/javac -sourcepath . SWFColor.java /bin/sh: /opt/sun-jdk-1.5.0.06/bin/javac: No such file or directory make: *** [SWFColor.class] Error 127 /usr/portage/media-libs/ming/ming-0.3.0.ebuild: line 46: java make failed: command not found and the emerge continued without halting. (This is where I am suggesting that the ebuild could possibly die here with an informative eerror message or something similar to alleviate the problem) When the src_install section arrived, the emerge died with: >>> Install ming-0.3.0 into /var/tmp/portage/ming-0.3.0/image/ category media-libs install: cannot stat `jswf.jar': No such file or directory !!! ERROR: media-libs/ming-0.3.0 failed. Call stack: ebuild.sh, line 1543: Called dyn_install ebuild.sh, line 1017: Called src_install ming-0.3.0.ebuild, line 83: Called java-pkg_doclass 'jswf.jar' java-pkg.eclass, line 99: Called java-pkg_dojar 'jswf.jar' java-pkg.eclass, line 267: Called die !!! jswf.jar not found !!! If you need support, post the topmost build error, and the call stack if relevant. It's apparent that the two are related in the sense that the java compile failed due to the absence of the jar file, that was not created because of the compile problem above. All I am suggesting is that the user should be informed about setting the java-config-1 and java-config-2 correctly, by reading the gentoo java-update page, or that the patch should be modified to use one of these java-configs instead of the plain 'java-config'. After resetting the jdk-1.4 VM with java-config-1, the emerge installs without a glitch. Thanks for your concern and help, Adam Pense
I've done a lot of work recently to move the user along a sane upgrade path. The checks should be smarter, and the messages they get should be more useful. Marking fixed.
