From: Denys Dmytriyenko <denis@denix.org>
To: Jeremy Puhlman <jpuhlman@mvista.com>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: Conflict between BBCLASSEXTEND and named recipes.
Date: Fri, 16 Mar 2012 15:08:31 -0400 [thread overview]
Message-ID: <20120316190831.GA21763@denix.org> (raw)
In-Reply-To: <4F6373BE.3040209@mvista.com>
On Fri, Mar 16, 2012 at 10:09:18AM -0700, Jeremy Puhlman wrote:
> There seems to be a bug with available providers when a recipe file
> provides the same name as an extended recipe. The extended version of
> the recipe does not seem to be available at all.
>
> Example:
>
> If zlib_1.2.6.bb exists in a layer, with BBCLASSEXTEND="native
> zlib-nativesdk" defined, and zlib-native_1.2.5.bb exists, the version
> 1.2.6 of zlib-native is not selectable at all.
>
>
> bitbake -s | grep zlib
> zlib :1.2.6-r0
> zlib-native :1.2.5-r0
> zlib-nativesdk :1.2.6-r0
>
> Even with PREFERRED_PROVIDER_zlib-naitve = 1.2.6 the results are the
> same. I have been poking around the parser, but really haven't made any
> progress, figured I would poke the list.
I don't have a solution, but I can confirm that this was a known issue all the
way back when BBCLASSEXTEND got introduced in Classic OE. The workaround was
to remove or mask the actual *-native.bb recipes.
--
Denys
next prev parent reply other threads:[~2012-03-16 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 17:09 Conflict between BBCLASSEXTEND and named recipes Jeremy Puhlman
2012-03-16 19:08 ` Denys Dmytriyenko [this message]
2012-03-16 21:35 ` Jeremy Puhlman
2012-03-17 9:14 ` Martin Jansa
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=20120316190831.GA21763@denix.org \
--to=denis@denix.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=jpuhlman@mvista.com \
/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.