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 14:19:48 +0100	[thread overview]
Message-ID: <1409663988.18528.7.camel@ted> (raw)
In-Reply-To: <CAP9ODKqfNwXn_dEUu-WT6zLoUM_MDDtgPRp2WfUU238UcpuKJw@mail.gmail.com>

On Tue, 2014-09-02 at 09:36 -0300, Otavio Salvador wrote:
> > How about only remove the x11 for target ?
> >
> > DISTRO_FEATURES_remove_class-target = "x11"
> 
> This is a workaround. Few days ago it built fine so a clear regression.

Lets take a step back and think about this for a minute.

If you build qemu-native configured with sdl, its likely you do want X
support. As this stood, the linkage with libxext was problematic.
Robert's patch makes the situation deterministic so in that sense its as
correct as the various other determinism patches.

The issue is that in some builds, you relied on x11-native not being
built and this is now showing up as an issue. What can be done is to
make the libxext dependency conditional on x11 in DISTRO_FEATURES as
we've done in other cases. It doesn't really make this invalid or a
regression, just that like other determinism fixes, we've resolved this
in a way means we need to rethink a few things.

I'd strongly suggest people think about whether they do really want x11
in "native" DISTRO_FEATURES since in reality, I suspect most people do.

So I'll take a patch making the dependency conditional but I don't
believe its what most people actually want.

Cheers,

Richard




  reply	other threads:[~2014-09-02 13:19 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
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 [this message]
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=1409663988.18528.7.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