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 commons-dbcp 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 96) dev-java/commons-dbcp-1.2.2 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 www-servers/tomcat:6 dev-java/xerces:2 ) >=dev-java/commons-pool-1.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-java/commons-dbcp-1.2.2 failed. * Call stack: * ebuild.sh, line 49: Called pkg_setup * environment, line 3730: Called java-pkg-2_pkg_setup * environment, line 2095: Called java-pkg_init * environment, line 2779: Called java-pkg_switch-vm * environment, line 3259: 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-java/commons-dbcp-1.2.2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-java/commons-dbcp-1.2.2/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 ggpweb1 ~ # Expected Results: no failure, just the use of newest jdk 1.6 (which is available).
*** 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
(In reply to comment #2) > 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 > >=virtual/jdk-1.4 would only work with binary packages. 1.6 has a new JDBC API that commons-dbcp does not build against. In the future read the bug that your bug has been marked a duplicate of. The Java eclasses are buggy and should not rely on DEPEND items being installed while in pkg_* functions. When the eclass works with only jres installed all the Java packages automatically get the fix. *** 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.
