Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Error while building qemu without X11 support.
Date: Tue, 02 Sep 2014 07:17:43 +0100	[thread overview]
Message-ID: <1409638663.29296.242.camel@ted> (raw)
In-Reply-To: <CAP9ODKr_p-1z-nRLuM_nMVpei3A4Z2CuDh9wzEEpZW9jSEoL-w@mail.gmail.com>

On Tue, 2014-09-02 at 00:33 -0300, Otavio Salvador wrote:
> On Tue, Sep 2, 2014 at 12:30 AM, Robert Yang <liezhi.yang@windriver.com> wrote:
> >
> >
> > On 09/02/2014 11:17 AM, Otavio Salvador wrote:
> >>
> >> On Mon, Sep 1, 2014 at 11:51 PM, Robert Yang <liezhi.yang@windriver.com>
> >> wrote:
> >>>
> >>>
> >>> On 09/02/2014 10:30 AM, Otavio Salvador wrote:
> >>>>
> >>>>
> >>>> Hello,
> >>>>
> >>>> During our regression tests we found the following error:
> >>>>
> >>>> directfb fsl-image-machine-test@imx6qsabresd (1/4) consider defining a
> >>>> PREFERRED_PROVIDER entry to match jpeg
> >>>> directfb fsl-image-machine-test@imx6qsabresd (1/4) ERROR: Nothing
> >>>> PROVIDES 'libxext-native' (but
> >>>
> >>>
> >>>
> >>> Did you use meta/recipes-graphics/xorg-lib/libxext_git.bb ? This one
> >>> doesn't provide native, but libxext_1.3.2.bb does.
> >>>
> >>> Seems that we need remove the git version since it is older:
> >>>
> >>> PV = "1.0.99.1+gitr${SRCPV}"
> >>>
> >>> And doesn't see a license issue.
> >>
> >>
> >> This has been reproduced in our autobuilder.
> >>
> >> It removes:
> >>
> >> x11 and wayland
> >>
> >> and adds:
> >>
> >> directfb
> >>
> >> Can you try to reproduce it?
> >>
> >
> > Yes, I can reproduce the error, sorry, please revert this as a quick
> > workaround:
> >
> > Author: Robert Yang <liezhi.yang@windriver.com>
> > Date:   Tue Jul 29 01:02:44 2014 -0700
> >
> >     qemu-native: depends on libxext-native when enable sdl
> >
> >
> > The DISTRO_FEATURES affects the native recipe, I'm not sure whether this is
> > intended or not.
> 
> This is an error in our autobuilder for regression test; Richard,
> could you revert this in OE-Core?

I think that illustrates the problem but is perhaps not the correct fix.

We did hit some issues like this with poky-tiny and I ended up fixing
this like:

http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=8b70d4b2863f48e843fb6ac9e4a939ae63338093

and also

http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=fd0398f2c1355597a95242e6c8400eae6ad60fa4

Cheers,

Richard





  reply	other threads:[~2014-09-02  6:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02  2:30 Error while building qemu without X11 support Otavio Salvador
2014-09-02  2:51 ` Robert Yang
2014-09-02  3:17   ` Otavio Salvador
2014-09-02  3:30     ` Robert Yang
2014-09-02  3:33       ` Otavio Salvador
2014-09-02  6:17         ` Richard Purdie [this message]
2014-09-02  6:21           ` Robert Yang
2014-09-02  6:25             ` Richard Purdie
2014-09-02  6:28               ` Robert Yang
2014-09-02  6:51         ` Robert Yang
2014-09-02 12:36           ` Otavio Salvador
2014-09-02 13:19             ` Richard Purdie
2014-09-02 13:55               ` Otavio Salvador

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=1409638663.29296.242.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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