From: Gary Thomas <gary@mlbassoc.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: Is BBCLASSEXTEND in .bbappend supposed to work?
Date: Mon, 18 Apr 2011 06:17:09 -0600 [thread overview]
Message-ID: <4DAC2BC5.4020107@mlbassoc.com> (raw)
In-Reply-To: <0E9C83CD-3E86-46B3-B749-6FAFB94E4BAF@dominion.thruhere.net>
On 04/18/2011 05:34 AM, Koen Kooi wrote:
>
> Op 18 apr 2011, om 13:28 heeft Richard Purdie het volgende geschreven:
>
>> On Mon, 2011-04-18 at 12:55 +0200, Koen Kooi wrote:
>>> Martin did some Xorg cleanup in meta-oe today and we're seeing some strange behaviour. The recipe in question:
>>>
>>> koen@dominion:/OE/tentacle/sources/meta-openembedded/meta-oe$ cat recipes-graphics/xorg-lib/libxrender_0.9.6.bbappend
>>> BBCLASSEXTEND = "native nativesdk"
>>> koen@dominion:/OE/tentacle/sources/meta-openembedded/meta-oe$
>>>
>>> Bitbake-layers tells me:
>>>
>>> INFO: libxrender_0.9.6.bb:
>>> INFO: /OE/tentacle/sources/meta-openembedded/meta-oe/recipes-graphics/xorg-lib/libxrender_0.9.6.bbappend
>>>
>>> So the append is getting picked up, but bitbake gives me:
>>>
>>> ERROR: Nothing PROVIDES 'libxrender-native'
>>> NOTE: Runtime target 'libnss-mdns' is unbuildable, removing...
>>> Missing or unbuildable dependency chain was: ['libnss-mdns', 'avahi', 'gtk+', 'gtk+-native', 'libxrender-native']
>>>
>>> This is with HEAD of bitbake master.
>>
>> I did some experimentation here and this looks like bitbake-layers is
>> seeing the file but bitbake is not. If I touch the libxrender .bb file
>> and then run bitbake -DDD, I see the file mentioned in the logs:
>>
>> $ touch recipes-graphics/xorg-lib/libxrender_0.9.6.bb
>> $ bitbake libxrender-native -DDD | grep append
>> DEBUG: Appending .bbappend file /rphome/poky/meta/recipes-graphics/xorg-lib/libxrender_0.9.6.bbappend to /rphome/poky/meta/recipes-graphics/xorg-lib/libxrender_0.9.6.bb
>> DEBUG: BB /rphome/poky/meta/recipes-graphics/xorg-lib/libxrender_0.9.6.bbappend: handle(data, include)
>> DEBUG: LOAD /rphome/poky/meta/recipes-graphics/xorg-lib/libxrender_0.9.6.bbappend
>>
>> Can you confirm you're seeing that? Admittedly I just hacked a local
>> checkout and I'm not using meta-oe.
>
> I get:
>
> koen@dominion:/OE/tentacle/build$ touch ../sources/openembedded-core/meta/recipes-graphics/xorg-lib/libxrender_0.9.6.bb
> koen@dominion:/OE/tentacle/build$ bitbake libxrender-native -DDD | grep append
> DEBUG: Appending .bbappend file /OE/tentacle/sources/meta-openembedded/meta-oe/recipes-graphics/xorg-lib/libxrender_0.9.6.bbappend to /OE/tentacle/sources/openembedded-core/meta/recipes-graphics/xorg-lib/libxrender_0.9.6.bb
> DEBUG: BB /OE/tentacle/sources/meta-openembedded/meta-oe/recipes-graphics/xorg-lib/libxrender_0.9.6.bbappend: handle(data, include)
> DEBUG: LOAD /OE/tentacle/sources/meta-openembedded/meta-oe/recipes-graphics/xorg-lib/libxrender_0.9.6.bbappend
>
> It then chokes on renderproto-native, which gets fixes by touching the .bb. So it looks like bitbake has some caching issues.
I have seen exactly this behaviour. Rebuilding the cache makes it work. Is there an easy way
to force the cache to rebuild? (I just touch a .conf file...)
>>
>> Do you need to add *.bbappend to BBFILES in layer.conf ?
>
> I have that already :)
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2011-04-18 12:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 10:55 Is BBCLASSEXTEND in .bbappend supposed to work? Koen Kooi
2011-04-18 11:28 ` Richard Purdie
2011-04-18 11:34 ` Koen Kooi
2011-04-18 12:17 ` Gary Thomas [this message]
2011-05-18 19:47 ` Simon Busch
2011-05-18 22:11 ` Gary Thomas
2011-05-19 22:53 ` Richard Purdie
2011-05-20 11:33 ` Gary Thomas
2011-05-20 11:46 ` Richard Purdie
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=4DAC2BC5.4020107@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=koen@dominion.thruhere.net \
--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