From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] python: Add tk to DEPENDS
Date: Sat, 24 Mar 2012 00:33:10 +0100 [thread overview]
Message-ID: <4F6D0836.7000907@opendreambox.org> (raw)
In-Reply-To: <1332544467-2071-1-git-send-email-andrei@gherzan.ro>
On 24.03.2012 00:14, Andrei Gherzan wrote:
> This is needed for _tkinter python module.
>
> [YOCTO #1937]
>
> Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
> ---
> meta/recipes-devtools/python/python_2.7.2.bb | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/meta/recipes-devtools/python/python_2.7.2.bb b/meta/recipes-devtools/python/python_2.7.2.bb
> index cb0a1d5..6969929 100644
> --- a/meta/recipes-devtools/python/python_2.7.2.bb
> +++ b/meta/recipes-devtools/python/python_2.7.2.bb
> @@ -1,5 +1,5 @@
> require python.inc
> -DEPENDS = "python-native bzip2 db gdbm openssl readline sqlite3 zlib"
> +DEPENDS = "python-native bzip2 db gdbm openssl readline sqlite3 zlib tk"
Andrei,
this breaks builds without x11:
ERROR: Nothing PROVIDES 'virtual/libx11' (but .../meta-oe/recipes-devtools/tcltk/tk_8.5.8.bb DEPENDS on or otherwise requires it)
ERROR: libx11-diet PROVIDES virtual/libx11 but was skipped: 'x11' not in DISTRO_FEATURES
ERROR: libx11-trim PROVIDES virtual/libx11 but was skipped: 'x11' not in DISTRO_FEATURES
ERROR: libx11 PROVIDES virtual/libx11 but was skipped: 'x11' not in DISTRO_FEATURES
ERROR: libx11-nativesdk PROVIDES virtual/libx11 but was skipped: 'x11' not in DISTRO_FEATURES
ERROR: Required build target 'tk' has no buildable providers.
Missing or unbuildable dependency chain was: ['tk', 'virtual/libx11']
Besides that, tk is not part of OE-core.
Regards,
Andreas
next prev parent reply other threads:[~2012-03-23 23:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 23:14 [PATCH] python: Add tk to DEPENDS Andrei Gherzan
2012-03-23 23:33 ` Andreas Oberritter [this message]
2012-03-23 23:39 ` Andreas Oberritter
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=4F6D0836.7000907@opendreambox.org \
--to=obi@opendreambox.org \
--cc=openembedded-core@lists.openembedded.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