Created attachment 362166 [details] build.log icedtea and icedtea-web fail to emerge with this message: * Messages for package dev-java/icedtea-7.2.4.3: * java-pkg_build-vm-from-handle: No vm found for handles: * icedtea-7 icedtea-bin-7 icedtea7 * icedtea-6 icedtea-bin-6 icedtea6 icedtea6-bin * gcj-jdk * java-pkg_switch-vm: No VM found for handles: * icedtea-7 icedtea-bin-7 icedtea7 * icedtea-6 icedtea-bin-6 icedtea6 icedtea6-bin * gcj-jdk * ERROR: dev-java/icedtea-7.2.4.3::gentoo failed (setup phase): * java-pkg_switch-vm: Failed to determine VM for building * * Call stack: * ebuild.sh, line 93: Called pkg_setup * icedtea-7.2.4.3.ebuild, line 180: Called java-pkg-2_pkg_setup * java-pkg-2.eclass, line 53: Called java-pkg_init * java-utils-2.eclass, line 2064: Called java-pkg_switch-vm * java-utils-2.eclass, line 2519: Called die * The specific snippet of code: * die "${FUNCNAME}: Failed to determine VM for building" * * If you need support, post the output of `emerge --info '=dev-java/icedtea-7.2.4.3::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-java/icedtea-7.2.4.3::gentoo'`. * The complete build log is located at '/var/tmp/portage/dev-java/icedtea-7.2.4.3/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-java/icedtea-7.2.4.3/temp/die.env'. * Working directory: '/usr/lib64/portage/pym' * S: '/var/tmp/portage/dev-java/icedtea-7.2.4.3/work/icedtea-2.4.3'
Created attachment 362168 [details] emerge --info
I think it's rather a eclass problem. Nevertheless, here's more info: ~ # eselect java-vm show Current system-vm icedtea-7 Current user-vm (unset) ~ # java -version java version "1.7.0_40" OpenJDK Runtime Environment (IcedTea 2.4.1) (Gentoo build 1.7.0_40-b31) OpenJDK 64-Bit Server VM (build 24.0-b50, mixed mode)
Try running java-check-environment
Created attachment 362170 [details] java-check-environment
(In reply to Tolga Dalman from comment #4) > Created attachment 362170 [details] > java-check-environment Hmm, ok. What about "java-config -L" ? If that fails, try running python-updater and then repeat the command. Please tell if that helped. If it still fails. It might be that re-emerging java-config and javatoolkit will help. We had such case recently but not sure what's going on. Did you recently update python?
Indeed, re-emerging java-config fixed the problem. I did the usual upgrade from python-2.7.5-r3 to -r4 last week, so that was most likely the reason. However, that leaves me with a bad feeling, for two reasons: 1. I was not able to deduce the problem from the error messages by emerge. That's probably an area where the problem analysis and reporting could be improved. 2. Randomly breaking packages from a Python upgrade in the -r versions indicates a general problem to me. Though, I don't know how to prevent or even test this properly. Anyway, thank you very much for your quick help on that issue!
Apparently the problem is not due to python upgrade, but due to removal of python-updater:0 which should only happen when you run emerge --depclean. Did you run that depclean lately?
(In reply to Vlastimil Babka (Caster) from comment #7) > Apparently the problem is not due to python upgrade, but due to removal of > python-updater:0 which should only happen when you run emerge --depclean. > Did you run that depclean lately? Sorry, not python-updater:0 but python-exec:0
(In reply to Vlastimil Babka (Caster) from comment #8) > > Did you run that depclean lately? > > Sorry, not python-updater:0 but python-exec:0 Yes.
Thanks, I'll add it to existing bug then. Unfortunately I don't see an easy way to improve error reporting here. This problem wasn't really anticipated. *** This bug has been marked as a duplicate of bug 489440 ***
(In reply to Vlastimil Babka (Caster) from comment #10) > Thanks, I'll add it to existing bug then. Again: thank you very much for your quick help. > Unfortunately I don't see an easy way to improve error reporting here. This > problem wasn't really anticipated. Well, the core problem here is the "broken" java-config. One solution could be a self-check of java-config in java-pkg_switch-vm. I would have been able to fix this problem my self, I think.
