Re: Issues installing libgles-omap3

[Carlos Rafael Giani <dv@pseudoterminal.org>]

Very late reply, but I still write this so it may help others:

I've had the same problem. Turns out that by adding at the end of 
conf/local.conf the line:

   PACKAGE_CLASSES = "package_ipk"

the problem is fixed.
I don't know why RPM isn't handling this properly, but everything works 
fine with this change.


Am 2014-10-09 um 00:01 schrieb Alexandre Belloni:
> On 08/10/2014 at 21:53:58 +0200, Alexandre Belloni wrote :
>> On 08/10/2014 at 14:13:38 -0400, Denys Dmytriyenko wrote :
>>> On Wed, Oct 08, 2014 at 06:15:07PM +0200, Alexandre Belloni wrote:
>>>> Hi,
>>>>
>>>> I'm trying to build an image with poky (daisy) for the am335x-evm. While
>>>> libgles-omap3 builds fine. At the final installation step (do_rootfs for
>>>> my image), it fails with:
>>>>
>>>> Computing transaction...error: Can't install libgles-omap3-es5-5.01.01.01-r38.1@cortexa8t2hf_vfp_neon: no package provides libews.so
>>>>
>>>> On another build machine, it fails with:
>>>>
>>>> Computing transaction...error: Can't install libgles-omap3-es3-5.01.01.01-r38.1@cortexa8t2hf_vfp_neon: no package provides libews.so
>>>>
>>>>
>>>> What I don't understand is why it is not selecting libgles-omap3-es8
>>>> which as I understand would be the correct package for ti33x.
>>>>
>>>> Any insight on how to debug that ?
>>> Can you please show how do you pull it into your image. Thanks.
>>>
>> Sure, I tried multiple things, but basically, I have:
>>
>> PREFERRED_PROVIDER_virtual/egl ?= "libgles-omap3"
>> PREFERRED_PROVIDER_virtual/libgles1 ?= "libgles-omap3"
>> PREFERRED_PROVIDER_virtual/libgles2 ?= "libgles-omap3"
>> PREFERRED_PROVIDER_virtual/libgl ?= "mesa-gl"
>> PREFERRED_PROVIDER_virtual/mesa ?= "mesa-gl"
>>
>> and libgles-omap3 is coming as a dependency of qtbase (from meta-qt5).
>> But I also tried removing qtbase from my image recipe and putting
>> directly either libgles-omap3 or libgles-omap3-es8 in IMAGE_INSTALL,
>> with the same result.
>>
> Just to let you know, the same image recipe builds fine when using
> meta-arago.
>