All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: meta-ti@yoctoproject.org
Subject: Re: Beaglebone Black and libgles-omap3 : build problem
Date: Thu, 14 Aug 2014 15:52:49 +0200	[thread overview]
Message-ID: <53ECBF31.1050708@pseudoterminal.org> (raw)
In-Reply-To: <53ECBC66.4070509@pseudoterminal.org>

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?


  reply	other threads:[~2014-08-14 13:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-14 13:40 Beaglebone Black and libgles-omap3 : build problem Carlos Rafael Giani
2014-08-14 13:52 ` Carlos Rafael Giani [this message]
2014-08-14 14:03 ` Denys Dmytriyenko
2014-08-14 14:07   ` Diego Sueiro
2014-08-14 14:30     ` Carlos Rafael Giani

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=53ECBF31.1050708@pseudoterminal.org \
    --to=dv@pseudoterminal.org \
    --cc=meta-ti@yoctoproject.org \
    /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.