From: justin <jlec@gentoo.org>
To: gentoo-devhelp@lists.gentoo.org
Subject: Re: [gentoo-devhelp] How does PYTHON_COMPAT work?
Date: Sun, 10 Aug 2014 11:08:31 +0200 [thread overview]
Message-ID: <53E7368F.8070102@gentoo.org> (raw)
In-Reply-To: <lrt6t5$gi1$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]
On 06/08/14 14:26, Nikos Chantziaras wrote:
> I have an ebuild where:
>
> PYTHON_COMPAT=( python3_3 python3_4 )
> inherit distutils-r1
>
> works just fine. Now python 3.3 doesn't work anymore for the software,
> so I removed that. But this:
>
> PYTHON_COMPAT=( python3_4 )
> # or: PYTHON_COMPAT=python3_4
> inherit distutils-r1
>
> doesn't work. During emerge:
>
> Calculating dependencies \
>
> !!! Problem resolving dependencies for net-misc/livestreamer
> ... done!
>
> !!! The ebuild selected to satisfy "livestreamer" has unmet requirements.
> - net-misc/livestreamer-1.9.0::Local USE="" ABI_X86="64"
> PYTHON_TARGETS="-python3_4"
>
> The following REQUIRED_USE flag constraints are unsatisfied:
> python_targets_python3_4
>
> The above constraints are a subset of the following complete expression:
> any-of ( python_targets_python3_4 )
>
>
Hi,
You have not enable python 3.4 as a python provider in your make.conf.
But for the emerge you need to set at least one python ABI. Just add
net-misc/livestreamer python_targets_python3_4
to your package.use.
Justin
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 959 bytes --]
next prev parent reply other threads:[~2014-08-11 20:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 12:26 [gentoo-devhelp] How does PYTHON_COMPAT work? Nikos Chantziaras
2014-08-10 9:08 ` justin [this message]
2014-08-19 6:07 ` [gentoo-devhelp] " Nikos Chantziaras
2014-08-19 6:23 ` Nikos Chantziaras
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=53E7368F.8070102@gentoo.org \
--to=jlec@gentoo.org \
--cc=gentoo-devhelp@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