Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Mesa mess
Date: Wed, 23 Oct 2013 18:57:41 -0600	[thread overview]
Message-ID: <52687085.9060605@mlbassoc.com> (raw)
In-Reply-To: <526804E7.3020406@mlbassoc.com>

On 2013-10-23 11:18, Gary Thomas wrote:
> On 2013-10-23 11:13, Gary Thomas wrote:
>> On 2013-10-23 08:07, Burton, Ross wrote:
>>> On 23 October 2013 14:43, Gary Thomas <gary@mlbassoc.com> wrote:
>>>> With the current master (Poky ffb440c37c), I can't build anything
>>>> with a virtual/mesa requirement.  This seems to bring in both mesa
>>>> and mesa-gl, which fight to the death, killing the build :-(
>>>
>>> Presumably you want just mesa-gl?
>>>
>>> I guess your distro is setting a preferred provider for
>>> virtual/something to mesa-gl, and something else is pulling in mesa,
>>> probably through a default.  Can you check that all of the
>>> mesa-related virtual/* lines are set in your distro, my hunch is that
>>> you don't have virtual/mesa set to mesa-gl.
>
> I also compared all of the PREFERRED_PROVIDERs between my build and a stock
> poky build and they are identical.
>
>>>
>>> If the distro looks right then try using depexp to see what is pulling
>>> in mesa when it shouldn't be?
>>
>> I looked through this and nothing was obvious.  According to depmod, neither
>> mesa nor mesa-gl have any direct "reverse depends", i.e. packages that depend
>> on them.  As far as I can see, it's just coming from the xserver-xorg dependency
>> on virtual/mesa.
>>
>> Which led me to another experiment which I truly do not understand.  I removed
>> the mesa-gl recipe and now when I try to build 'virtual/mesa' I get a message
>> that there is no provider :-(  However, I *can* build mesa with no problems.
>> I also checked it against the other PROVIDES from mesa.inc and all of them
>> except for virtual/mesa work.  How can this possibly be?
>
> To be clear, 'bitbake virtual/libgl' (or any of its friends except virtual/mesa)
> will cause 'mesa' to be built, but 'bitbake virtual/mesa' fails.
>

I found the cause :-)  In addition to OE-core, I am using meta-ti on an OMAP3 target.
In meta-ti, there is this line:
   meta-ti/recipes-graphics/mesa/mesa-omap3-common.inc:PROVIDES_omap3 = "virtual/libgl"
I added virtual/mesa to this list and it now builds again.  I'm not sure that this is
100% correct though.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2013-10-24  0:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-23 13:43 Mesa mess Gary Thomas
2013-10-23 14:07 ` Burton, Ross
2013-10-23 17:13   ` Gary Thomas
2013-10-23 17:18     ` Gary Thomas
2013-10-24  0:57       ` Gary Thomas [this message]
2013-10-24  7:43         ` Andreas Müller
2013-10-24  8:58           ` Andreas Müller
2013-10-28 14:54         ` Burton, Ross
2013-10-28 14:57           ` Gary Thomas

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=52687085.9060605@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox