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

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


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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-14 13:40 Carlos Rafael Giani [this message]
2014-08-14 13:52 ` Beaglebone Black and libgles-omap3 : build problem Carlos Rafael Giani
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=53ECBC66.4070509@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.