On Thu, 13 Oct 2022, 17:00 Alexandre Belloni, <alexandre.bell...@bootlin.com>
wrote:

> On 13/10/2022 09:52:44+0200, Marta Rybczynska wrote:
> > Hello all,
> > I'm trying to build the core-image-weston in kirkstone to look into
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=14926
> >
> > It turns out that the image does not build (oe-core
> > e728d0965d6fda8ac54e065ca7bf7eb9da9a8170 with bitbake
> > 6603c3e39f1cf746669ec6c9f0be8c6e6ece426e). I'm getting:
> >
> > $ bitbake core-image-weston
> > Loading cache: 100%
> >
> |###################################################################################################################################|
> > Time: 0:00:00
> > Loaded 1640 entries from dependency cache.
> > NOTE: Resolving any missing task queue dependencies
> > ERROR: Nothing RPROVIDES 'weston-xwayland' (but
> > /oe-standalone/oe-core/meta/recipes-graphics/images/core-image-weston.bb
> > RDEPENDS on
> > or otherwise requires it)
> > NOTE: Runtime target 'weston-xwayland' is unbuildable, removing...
> > Missing or unbuildable dependency chain was: ['weston-xwayland']
> > ERROR: Required build target 'core-image-weston' has no buildable
> providers.
> > Missing or unbuildable dependency chain was: ['core-image-weston',
> > 'weston-xwayland']
> >
> > Summary: There were 2 ERROR messages, returning a non-zero exit code.
> >
> > I can't find this one in bugzilla. Is it a known issue?
> >
>
> Did you remove x11 from your DISTRO_FEATURES?
>

No. This is a fresh clone. The only changes I have are in local.conf:
DL_DIR and parallel build options. That's why I'm surprised.

Regards
Marta

>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#171687): 
https://lists.openembedded.org/g/openembedded-core/message/171687
Mute This Topic: https://lists.openembedded.org/mt/94299411/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to