Summary: | dev-libs/cyrus-sasl-2.1.22 failed with USE=java | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Joshua Pettett <bugs.gentoo.devel> |
Component: | [OLD] Unspecified | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Joshua Pettett
2006-10-03 14:54:28 UTC
*** This bug has been marked as a duplicate of 133247 *** Bug #133247 is marked as FIXED; how could it be fixed if I'm still having this problem with the latest cyrus-sasl ebuild in portage? Also, bug #133247 seems to describe a situation in which a jdk is installed but not recognised. In my case, there is NOT a jdk installed, but the cyrus-sasl ebuild is trying to use `jar` anyway. Ditto here. In the middle of a emerge -e system, cyrus-sasl borked. Once I used "-java" in /etc/portage/package.use, cyrus-sasl compiled. (In reply to comment #2) > In my case, there is NOT a jdk installed, but the cyrus-sasl ebuild is trying > to use `jar` anyway. Well, if you don't have JDK installed, it obviously won't work. The ebuild depends on it: <snip> RDEPEND="berkdb? ( >=sys-libs/db-3.2 ) gdbm? ( >=sys-libs/gdbm-1.8.0 ) ldap? ( >=net-nds/openldap-2.0.25 ) mysql? ( >=dev-db/mysql-3.23.51 ) postgres? ( >=dev-db/postgresql-7.2 ) pam? ( virtual/pam ) ssl? ( >=dev-libs/openssl-0.9.6d ) kerberos? ( virtual/krb5 ) authdaemond? ( || ( >=net-mail/courier-imap-3.0.7 >=mail-mta/courier-0.46 ) ) java? ( =virtual/jdk-1.4* ) ntlm_unsupported_patch? ( >=net-fs/samba-3.0.9 )" DEPEND="${RDEPEND} >=sys-apps/sed-4 >=sys-devel/autoconf-2.58 sys-devel/automake sys-devel/libtool" </snip> |