From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] dependency problem - how to decipher this one
Date: Wed, 14 May 2014 18:39:58 -0400 [thread overview]
Message-ID: <20140514223958.GA11182@waltdnes.org> (raw)
In-Reply-To: <1400088551.15558.0@numa-i>
On Wed, May 14, 2014 at 07:29:11PM +0200, Helmut Jarausch wrote
> Hi,
>
> trying to emerge x11-libs/gtk+:2 (2.24.23-r1) together with
> dev-libs/atk (2.12.0-r1) I get the following messages
>
> emerge: there are no ebuilds to satisfy
> ">=dev-libs/atk-1.29.2[introspection?,abi_x86_32(-)?,abi_x86_64(-)?,
> abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?]".
> (dependency required by "x11-libs/gtk+-2.24.23-r1" [ebuild])
> (dependency required by "x11-libs/gtk+:2" [argument])
>
> How can this be deciphered? How can I trace / debug the problem.
Plan A) try adding the line...
dev-libs/atk -introspection
...to /etc/portage/package.use
Plan B) if some other package requires atk built with introspection,
then make sure that atk is not built with any of abi_x86_32, or
abi_x86_64, abi_x86_x32, or abi_mips_n32, or abi_mips_n64, or
abi_mips_o32. I.e. if you're running on AMD or Intel, add the line...
dev-libs/atk -abi_x86_32 -abi_x86_64 -abi_x86_x32
...to /etc/portage/package.use
In both cases (Plan A and Plan B), execute the command...
emerge -1 atk
...immediately afterwards.
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
next prev parent reply other threads:[~2014-05-14 22:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 17:29 [gentoo-user] dependency problem - how to decipher this one Helmut Jarausch
2014-05-14 22:39 ` Walter Dnes [this message]
2014-05-30 19:48 ` Yuan MEI
2014-06-01 19:31 ` Volker Armin Hemmann
2014-06-01 20:51 ` Volker Armin Hemmann
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=20140514223958.GA11182@waltdnes.org \
--to=waltdnes@waltdnes.org \
--cc=gentoo-user@lists.gentoo.org \
/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