no up-to-date "NV_DEPEND" of jdk-1.6* Reproducible: Always Steps to Reproduce: use a system with prebuilt binary packages and do a "emerge -ev world" with hsqldb in world file. (The built machine has two jdk installed, but the binary-using machine hasn't and runs into this problem.) Actual Results: >>> Emerging (1 of 93) dev-db/hsqldb-1.8.0.9-r1 to / >>> Extracting info /usr/lib/portage/pym/portage_dep.py:39: DeprecationWarning: DEPRECATION NOTICE: The portage_dep module was replaced by portage.dep !!! ERROR: Couldn't find suitable VM. Possible invalid dependency string. * Unable to determine VM for building from dependencies: NV_DEPEND: || ( =virtual/jdk-1.5* =virtual/jdk-1.4* ) test? ( dev-java/junit:0 ) app-arch/unzip java-virtuals/servlet-api:2.3 >=dev-java/java-config-2.0.33-r1 >=sys-apps/portage-2.1.2.7 source? ( app-arch/zip ) >=dev-java/javatoolkit-0.2.0-r1 >=sys-apps/portage-2.1.2.7 >=dev-java/ant-core-1.7.0 VNEED: * * ERROR: dev-db/hsqldb-1.8.0.9-r1 failed. * Call stack: * ebuild.sh, line 49: Called pkg_setup * environment, line 3814: Called java-pkg-2_pkg_setup * environment, line 2118: Called java-pkg_init * environment, line 2802: Called java-pkg_switch-vm * environment, line 3282: Called die * The specific snippet of code: * die "Failed to determine VM for building."; * The die message: * Failed to determine VM for building. * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/dev-db/hsqldb-1.8.0.9-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-db/hsqldb-1.8.0.9-r1/temp/environment'. * !!! When you file a bug report, please include the following information: GENTOO_VM= CLASSPATH="" JAVA_HOME="" JAVACFLAGS="-source 1.4 -target 1.4" COMPILER="javac" and of course, the output of emerge --info !!! Setup failed: 1 HSQLDB runs under Java 1.6, own built ebuild with NV_DEPEND jdk-1.6 runs fine.
This isn't really specific to hsqldb. This just points out the *** This bug has been marked as a duplicate of bug 206024 ***
How about an update? >=virtual/jdk-1.5* or =virtual/jdk-1.6* This will work, and this is the present. JDK 1.6! Thanks PS: "[Bug 206024] java-pkg-2* eclasses binpkg issues" - has nothing to do with outaged setup information 1.4/1.5 vs. 1.6.
(In reply to comment #2) > > PS: "[Bug 206024] java-pkg-2* eclasses binpkg issues" - has nothing to do with > outaged setup information 1.4/1.5 vs. 1.6. > Yes it does. As the eclass expects DEPEND items to be there while in pkg_* it means you must have a virtual/jdk:1.4 or virtual/jdk:1.5 installed even when installing from binary packages. This is a bug in the eclass. The only solution I know of at the moment involves modifying most of the Java ebuilds but guess we just have to bite the bullet sooner than later. *** This bug has been marked as a duplicate of bug 206024 ***
"emerge virtual/jdk:1.5" This works! Thank you all very much! Solution from bug 206024.
