From: David Relson <relson@osagesoftware.com>
To: gentoo-user@lists.gentoo.org
Cc: ken69267@gmail.com
Subject: Re: [gentoo-user] Java problem
Date: Sat, 22 May 2010 20:43:54 -0400 [thread overview]
Message-ID: <20100522204354.612ea038@osage.osagesoftware.com> (raw)
In-Reply-To: <20100522173524.15554ac1@khaos>
On Sat, 22 May 2010 17:35:24 -0400
Kenneth Prugh wrote:
> On Sat, 22 May 2010 16:10:39 -0400
> David Relson <relson@osagesoftware.com> wrote:
>
> > [...]
>
> What does `eselect java-vm list` say?
>
> Also, You might need to manually emerge dev-java/ant-junit.
root@osage ~ # eselect java-vm list
Available Java Virtual Machines:
[1] emul-linux-x86-java-1.6
[2] sun-jdk-1.6 system-vm
[3] sun-jre-bin-1.6
For all 3 packages, version 1.6.0.20 is installed.
Manually emerging ant-junit pulls in ant-core as a dependency which
fails in the manner previously reported, i.e.
* CPV: dev-java/ant-core-1.8.1
* REPO: gentoo
* USE: amd64 elibc_glibc kernel_linux multilib userland_GNU
!!! ERROR: Package ant-junit was not found!
* Unable to determine VM for building from dependencies:
NV_DEPEND: >=virtual/jdk-1.4
!dev-java/ant-tasks
!dev-java/ant-optional >=dev-java/java-config-2.1.9-r1
source? ( app-arch/zip )
>=dev-java/javatoolkit-0.3.0-r2
* ERROR: dev-java/ant-core-1.8.1 failed:
* Failed to determine VM for building.
*
* Call stack:
* ebuild.sh, line 48: Called pkg_setup
* ebuild.sh, line 1346: Called java-pkg-2_pkg_setup
* java-pkg-2.eclass, line 63: Called java-pkg_init
* java-utils-2.eclass, line 2126: Called java-pkg_switch-vm
* java-utils-2.eclass, line 2550: 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/ant-core-1.8.1',
* the complete build log and the output of 'emerge -pqv
=dev-java/ant-core-1.8.1'. !!! 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
next prev parent reply other threads:[~2010-05-23 0:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 20:10 [gentoo-user] Java problem David Relson
2010-05-22 21:35 ` Kenneth Prugh
2010-05-23 0:43 ` David Relson [this message]
2010-05-23 0:51 ` Kenneth Prugh
2010-05-23 0:57 ` David Relson
2010-05-23 1:32 ` David Abbott
2010-05-23 4:30 ` Kenneth Prugh
2010-05-23 3:41 ` [gentoo-user] " walt
2010-05-23 13:24 ` David Relson
2010-05-23 14:32 ` Arttu V.
2010-05-23 14:57 ` David Relson
2010-05-23 15:16 ` Arttu V.
2010-05-23 16:53 ` David Relson
2010-05-23 16:24 ` walt
2010-05-23 16:56 ` David Relson
2010-05-23 18:01 ` walt
2010-05-24 1:26 ` David Relson
2010-05-24 1:43 ` Kenneth Prugh
2010-05-24 11:11 ` walt
2010-05-24 11:37 ` David Relson
2010-05-25 11:46 ` [gentoo-user] SOLVED " David Relson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100522204354.612ea038@osage.osagesoftware.com \
--to=relson@osagesoftware.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=ken69267@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox