From: Gary Thomas <gary@mlbassoc.com>
To: "pighi@selea.com" <pighi@selea.com>, meta-freescale@yoctoproject.org
Subject: Re: HOB unable to parse initial sabresd
Date: Tue, 18 Mar 2014 04:05:52 -0600 [thread overview]
Message-ID: <53281A80.8090804@mlbassoc.com> (raw)
In-Reply-To: <201403180942.s2I9gos3018368@vivaldi15.register.it>
On 2014-03-18 03:42, pighi@selea.com wrote:
> well the errors are actually 2 (the ame conflct) one is on libgl and the seond one is on libgl-dev
Yes, I see this as well.
Trying to resolve runtime dependency libgl-dev resulted in conflicting PREFERRED_PROVIDER entries being found.
The providers found were: ['/local/poky-multi/meta/recipes-graphics/mesa/mesa_9.2.5.bb',
'/local/poky-multi/meta-fsl-arm/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q_3.10.9-1.0.0-hfp.bb']
The PREFERRED_PROVIDER entries resulting in this conflict were: ['PREFERRED_PROVIDER_virtual/mesa = mesa', 'PREFERRED_PROVIDER_virtual/libgl = gpu-viv-bin-mx6q']
Worse than just this error/conflict is
the fact that hob just stopped and I only saw the error when I tried
to kill/close it.
I think you should file a bug against this.
n.b. I don't see this error if I run bitbake from the command line.
>> ----- Original Message -----
>> From: gary@mlbassoc.com
>> To: pighi@selea.com,meta-freescale@yoctoproject.org
>> Data: Tue, 18 Mar 2014 03:31:25 -0600
>> Subject: Re: [meta-freescale] HOB unable to parse initial sabresd
>
>> On 2014-03-18 03:24, pighi@selea.com wrote:
>>> I'm using the Master branch
>>
>> Master branch of both Poky/Yocto and meta-fsl-arm*
>> What revision (since these are quickly moving targets)?
>>
>>>> ----- Original Message -----
>>>> From: gary@mlbassoc.com
>>>> To: meta-freescale@yoctoproject.org
>>>> Data: Tue, 18 Mar 2014 03:11:53 -0600
>>>> Subject: Re: [meta-freescale] HOB unable to parse initial sabresd
>>>
>>>> On 2014-03-18 03:07, pighi@selea.com wrote:
>>>>> I want to bump this problem with Hob, the error i still present and not resolved yet:
>>>>>
>>>>> https://lists.yoctoproject.org/pipermail/meta-freescale/2013-October/005444.html
>>>>>
>>>>> https://lists.yoctoproject.org/pipermail/meta-freescale/2013-December/006067.html
>>>>
>>>> What revision/branch of the metadata are you using?
>>
>>
>> --
>> ------------------------------------------------------------
>> Gary Thomas | Consulting for the
>> MLB Associates | Embedded world
>> ------------------------------------------------------------
>>
>>
>
>
> Dott.Ing. Omar Pighi
> R&D Selea
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2014-03-18 10:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 9:42 HOB unable to parse initial sabresd pighi
2014-03-18 10:05 ` Gary Thomas [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-03-18 13:03 pighi
2014-03-18 11:17 pighi
2014-03-18 10:10 pighi
2014-03-18 9:37 pighi
2014-03-18 9:24 pighi
2014-03-18 9:31 ` Gary Thomas
2014-03-18 9:07 pighi
2014-03-18 9:11 ` Gary Thomas
2013-10-30 13:50 Doug Schwanke
2013-11-01 13:20 ` George Reimer
2013-11-05 15:14 ` Florian
2013-12-16 23:41 ` George Reimer
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=53281A80.8090804@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=meta-freescale@yoctoproject.org \
--cc=pighi@selea.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.