Bug 372097 – dev-java/jpfcodegen-0.4 needs jdom-jaxen to build

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Gil Desmarais 2011-06-17 20:35:53 UTC]

dev-java/jpfcodegen-0.4 needs dev-java/jdom-jaxen to build (= depends on it).

I tried to install dev-java/jdom-jaxen and emerge jpdfcodegen again - with succes.


`cat /var/tmp/portage/dev-java/jpfcodegen-0.4/temp/build.log`

 * Package:    dev-java/jpfcodegen-0.4
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        consolekit elibc_glibc kernel_linux policykit userland_GNU x86
 * FEATURES:   sandbox
!!! ERROR: Package jdom-jaxen-1.0 was not found!
 * Unable to determine VM for building from dependencies:
NV_DEPEND: app-arch/unzip
        >=virtual/jdk-1.5
        dev-java/velocity:0
        dev-java/jpf:1.5  >=dev-java/java-config-2.1.9-r1 >=sys-apps/portage-2.1.2.7  >=dev-java/ant-core-1.7.0
       
       >=sys-apps/portage-2.1.2.7
       >=dev-java/javatoolkit-0.3.0-r2
       >=dev-lang/python-2.4
 * ERROR: dev-java/jpfcodegen-0.4 failed (setup phase):
 *   Failed to determine VM for building.
 * 
 * Call stack:
 *             ebuild.sh, line   56:  Called pkg_setup
 *             ebuild.sh, line 1446:  Called java-pkg-2_pkg_setup
 *     java-pkg-2.eclass, line   63:  Called java-pkg_init
 *   java-utils-2.eclass, line 2175:  Called java-pkg_switch-vm
 *   java-utils-2.eclass, line 2599:  Called die
 * The specific snippet of code:
 *                              die "Failed to determine VM for building."
 * 
 * If you need support, post the output of 'emerge --info =dev-java/jpfcodegen-0.4',
 * the complete build log and the output of 'emerge -pqv =dev-java/jpfcodegen-0.4'.
!!! When you file a bug report, please include the following information:
GENTOO_VM=  CLASSPATH="" JAVA_HOME=""
JAVACFLAGS="" COMPILER=""
and of course, the output of emerge --info
 * The complete build log is located at '/var/tmp/portage/dev-java/jpfcodegen-0.4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-java/jpfcodegen-0.4/temp/die.env'.
 * S: '/var/tmp/portage/dev-java/jpfcodegen-0.4/work/jpfcodegen-0.4'

[Comment 1 William L. Thomson Jr. 2015-03-20 20:15:18 UTC]

I think this can be closed as invalid

ws ~ # emerge -qC jdom-jaxen 
dev-java/jdom-jaxen: 1.0-r1 1.1.1 none none 

All selected packages: =dev-java/jdom-jaxen-1.0-r1 =dev-java/jdom-jaxen-1.1.1
>>> Waiting 5 seconds before starting...
>>> (Control-C to abort)...
>>> Unmerging in: 5 4 3 2 1
>>> Unmerging (1 of 2) dev-java/jdom-jaxen-1.0-r1...
>>> Unmerging (2 of 2) dev-java/jdom-jaxen-1.1.1...

ws ~ # emerge -qv jpfcodegen
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) dev-java/jpfcodegen-0.4::gentoo
>>> Installing (1 of 1) dev-java/jpfcodegen-0.4::gentoo
>>> Jobs: 1 of 1 complete                           Load avg: 0.91, 1.05, 0.79


Merged fine for me, and I removed jdom-jaxen entirely as you can see, prior to merging the package.

[Comment 2 James Le Cuirot 2015-03-20 21:55:21 UTC]

I've also failed to reproduce this. jdom-jaxen is an indirect dependency via velocity and jdom. java-config will spit out this error if you unmerge jdom-jaxen and request the full classpath with dependencies but this doesn't happen while building. Even if it did, it still suggests that the user must have erroneously removed jdom-jaxen. Perhaps the behaviour of the eclasses or java-config have changed in this regard since the bug was filed.