From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: libpython2
Date: Wed, 11 Apr 2012 12:43:52 +0100 [thread overview]
Message-ID: <1334144632.10826.167.camel@ted> (raw)
In-Reply-To: <4F843878.2060705@opendreambox.org>
On Tue, 2012-04-10 at 15:41 +0200, Andreas Oberritter wrote:
> Hi,
>
> bitbake complains:
>
> "NOTE: multiple providers are available for runtime libpython2 (python,
> python-nativesdk)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match libpython2"
>
> That's because I'm building a recipe for a binary that RDEPENDS_${PN} on
> libpython2. So I added PREFERRED_PROVIDER_libpython2 = "python" to my
> disto.conf, but the warning cited above persists.
>
> python_2.7.2.bb contains:
>
> PACKAGES =+ "lib${BPN}2"
> ...
> BBCLASSEXTEND = "nativesdk"
>
> Shouldn't it rather create libpython2 and libpython2-nativesdk or
> something similar?
>
> What could be the reason for the warning to persist?
python-nativesdk should not be providing libpython2. There is a bug in
the packaging somewhere. This usually results in needing to add the
PKGSUFFIX mess. I want to get rid of that entirely and switch to the
multilib way of handling this with a prefix but it didn't happen in time
for 1.2 :(.
Cheers,
Richard
prev parent reply other threads:[~2012-04-11 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 13:41 libpython2 Andreas Oberritter
2012-04-10 13:56 ` libpython2 Chris Larson
2012-04-11 11:45 ` libpython2 Richard Purdie
2012-04-11 11:43 ` Richard Purdie [this message]
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=1334144632.10826.167.camel@ted \
--to=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.