Beaglebone Black and libgles-omap3 : build problem

Beaglebone Black and libgles-omap3 : build problem

[Carlos Rafael Giani]

Hello,

I have a BeagleBone black here, and want to build a rootfs for it with 
Yocto. It shall include support for the SGX GPU.

But when I try to build this, I get:

ERROR: Nothing PROVIDES 'libgles-omap3'
ERROR: libgles-omap3 was skipped: incompatible with machine beaglebone 
(not in COMPATIBLE_MACHINE)
ERROR: libgles-omap3 was skipped: incompatible with machine beaglebone 
(not in COMPATIBLE_MACHINE)
ERROR: libgles-omap3-x11 PROVIDES libgles-omap3 but was skipped: 
incompatible with machine beaglebone (not in COMPATIBLE_MACHINE)
ERROR: libgles-omap3 was skipped: incompatible with machine beaglebone 
(not in COMPATIBLE_MACHINE)

However, this is incorrect. The BeagleBone Black has an AM3359 SoC, 
which does have the SGX, so it is compatible. Looking into the recipe, 
it lists ti33x as being compatible, yet the build breaks. I fixed this 
locally by adding "beaglebone" to the list of compatible machines, but 
of course this is a hack.

Does anybody have some insight into this? Is "beaglebone" perhaps the 
wrong machine for the BeagleBone black? I didn't find any machine config 
called "bblack" or "beagleboneblack" or similar.

cheers

Re: Beaglebone Black and libgles-omap3 : build problem

[Carlos Rafael Giani]

On 2014-08-14 15:40, Carlos Rafael Giani wrote:
> Hello,
>
> I have a BeagleBone black here, and want to build a rootfs for it with 
> Yocto. It shall include support for the SGX GPU.
>
> But when I try to build this, I get:
>
> ERROR: Nothing PROVIDES 'libgles-omap3'
> ERROR: libgles-omap3 was skipped: incompatible with machine beaglebone 
> (not in COMPATIBLE_MACHINE)
> ERROR: libgles-omap3 was skipped: incompatible with machine beaglebone 
> (not in COMPATIBLE_MACHINE)
> ERROR: libgles-omap3-x11 PROVIDES libgles-omap3 but was skipped: 
> incompatible with machine beaglebone (not in COMPATIBLE_MACHINE)
> ERROR: libgles-omap3 was skipped: incompatible with machine beaglebone 
> (not in COMPATIBLE_MACHINE)
>
> However, this is incorrect. The BeagleBone Black has an AM3359 SoC, 
> which does have the SGX, so it is compatible. Looking into the recipe, 
> it lists ti33x as being compatible, yet the build breaks. I fixed this 
> locally by adding "beaglebone" to the list of compatible machines, but 
> of course this is a hack.
>
> Does anybody have some insight into this? Is "beaglebone" perhaps the 
> wrong machine for the BeagleBone black? I didn't find any machine 
> config called "bblack" or "beagleboneblack" or similar.
>
> cheers



In addition to the libgles-omap3 problems, I also cannot build 
omap3-sgx-modules . Yocto version is daisy, meta-ti daisy branch, HEAD 
of meta-ti is at a817ad5826b1c35084a6abb093b89a3916ecb283 .


This is what I get when building omap3-sgx-modules:


/home/test/yocto-ti/build/.build-yocto/tmp/work/beaglebone-poky-linux-gnueabi/omap3-sgx-modules/5.01.01.01-c/Graphics_SDK_5_01_01_01/GFX_Linux_KM/services4/3rdparty/dc_omapfb3_linux/omaplfb_linux.c: 
In function 'OMAPLFBWaitForVSync':
/home/test/yocto-ti/build/.build-yocto/tmp/work/beaglebone-poky-linux-gnueabi/omap3-sgx-modules/5.01.01.01-c/Graphics_SDK_5_01_01_01/GFX_Linux_KM/services4/3rdparty/dc_omapfb3_linux/omaplfb_linux.c:180:92: 
error: 'struct omap_dss_device' has no member named 'output'
  #define OMAP_DSS_MANAGER(man, dev) struct omap_overlay_manager *man = 
(dev) != NULL ? (dev)->output->manager : NULL
^
/home/test/yocto-ti/build/.build-yocto/tmp/work/beaglebone-poky-linux-gnueabi/omap3-sgx-modules/5.01.01.01-c/Graphics_SDK_5_01_01_01/GFX_Linux_KM/services4/3rdparty/dc_omapfb3_linux/omaplfb_linux.c:821:2: 
note: in expansion of macro 'OMAP_DSS_MANAGER'
   OMAP_DSS_MANAGER(psDSSMan, psDSSDev);
   ^
make[3]: *** 
[/home/test/yocto-ti/build/.build-yocto/tmp/work/beaglebone-poky-linux-gnueabi/omap3-sgx-modules/5.01.01.01-c/Graphics_SDK_5_01_01_01/GFX_Linux_KM/services4/3rdparty/dc_omapfb3_linux/omaplfb_linux.o] 
Error 1



I apply the patch at 
http://git.buildroot.net/buildroot/tree/package/ti-gfx/ti-gfx-0001-fix-build-omaplfb-linux.patch 
. This helps, but there is another error:


In file included from 
/home/test/yocto-ti/build/.build-yocto/tmp/work/beaglebone-poky-linux-gnueabi/omap3-sgx-modules/5.01.01.01-c/Graphics_SDK_5_01_01_01/GFX_Linux_KM/services4/srvkm/include/services_headers.h:55:0,
                  from 
/home/test/yocto-ti/build/.build-yocto/tmp/work/beaglebone-poky-linux-gnueabi/omap3-sgx-modules/5.01.01.01-c/Graphics_SDK_5_01_01_01/GFX_Linux_KM/services4/srvkm/common/queue.c:42:
/home/test/yocto-ti/build/.build-yocto/tmp/work/beaglebone-poky-linux-gnueabi/omap3-sgx-modules/5.01.01.01-c/Graphics_SDK_5_01_01_01/GFX_Linux_KM/services4/include/servicesint.h:51:21: 
fatal error: sysinfo.h: No such file or directory
  #include "sysinfo.h"
                      ^
compilation terminated.
make[2]: *** 
[/home/test/yocto-ti/build/.build-yocto/tmp/work/beaglebone-poky-linux-gnueabi/omap3-sgx-modules/5.01.01.01-c/Graphics_SDK_5_01_01_01/GFX_Linux_KM/services4/srvkm/common/queue.o] 
Fehler 1


Now I do not know where this omnious sysinfo.h is. I cannot find it 
anywhere.

What can I do?

Re: Beaglebone Black and libgles-omap3 : build problem

[Denys Dmytriyenko]

Don't use beaglebone machine from meta-yocto-bsp, but instead use beaglebone 
machine from meta-ti, if you want to use other components from meta-ti...

-- 
Denys


On Thu, Aug 14, 2014 at 03:40:54PM +0200, Carlos Rafael Giani wrote:
> Hello,
> 
> I have a BeagleBone black here, and want to build a rootfs for it
> with Yocto. It shall include support for the SGX GPU.
> 
> But when I try to build this, I get:
> 
> ERROR: Nothing PROVIDES 'libgles-omap3'
> ERROR: libgles-omap3 was skipped: incompatible with machine
> beaglebone (not in COMPATIBLE_MACHINE)
> ERROR: libgles-omap3 was skipped: incompatible with machine
> beaglebone (not in COMPATIBLE_MACHINE)
> ERROR: libgles-omap3-x11 PROVIDES libgles-omap3 but was skipped:
> incompatible with machine beaglebone (not in COMPATIBLE_MACHINE)
> ERROR: libgles-omap3 was skipped: incompatible with machine
> beaglebone (not in COMPATIBLE_MACHINE)
> 
> However, this is incorrect. The BeagleBone Black has an AM3359 SoC,
> which does have the SGX, so it is compatible. Looking into the
> recipe, it lists ti33x as being compatible, yet the build breaks. I
> fixed this locally by adding "beaglebone" to the list of compatible
> machines, but of course this is a hack.
> 
> Does anybody have some insight into this? Is "beaglebone" perhaps
> the wrong machine for the BeagleBone black? I didn't find any
> machine config called "bblack" or "beagleboneblack" or similar.
> 
> cheers
> -- 
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti

Re: Beaglebone Black and libgles-omap3 : build problem

[Diego Sueiro]

[-- Attachment #1: Type: text/plain, Size: 556 bytes --]

Hi,

On Thu, Aug 14, 2014 at 11:03 AM, Denys Dmytriyenko <denys@ti.com> wrote:

> Don't use beaglebone machine from meta-yocto-bsp, but instead use
> beaglebone
> machine from meta-ti, if you want to use other components from meta-ti...
>

Just complementing. Remove meta-yocto-bsp from your bblayers.conf

Regards,

--
*dS
Diego Sueiro

Administrador do Embarcados
www.embarcados.com.br
<http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>

/*long live rock 'n roll*/

[-- Attachment #2: Type: text/html, Size: 1091 bytes --]

Re: Beaglebone Black and libgles-omap3 : build problem

[Carlos Rafael Giani]

[-- Attachment #1: Type: text/plain, Size: 781 bytes --]

On 2014-08-14 16:07, Diego Sueiro wrote:
> Hi,
>
> On Thu, Aug 14, 2014 at 11:03 AM, Denys Dmytriyenko <denys@ti.com 
> <mailto:denys@ti.com>> wrote:
>
>     Don't use beaglebone machine from meta-yocto-bsp, but instead use
>     beaglebone
>     machine from meta-ti, if you want to use other components from
>     meta-ti...
>
>
> Just complementing. Remove meta-yocto-bsp from your bblayers.conf
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> Administrador do Embarcados
> www.embarcados.com.br 
> <http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>
>
> /*long live rock 'n roll*/

Thanks! Such an easy an obvious solution. Apparently I thought too 
complicated again :)
It works now.

[-- Attachment #2: Type: text/html, Size: 2188 bytes --]