All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vadym Kochan <vadim4j@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2019-02-27
Date: Thu, 28 Feb 2019 21:19:21 +0200	[thread overview]
Message-ID: <20190228191921.GA28686@lwo1-lhp-f71841> (raw)
In-Reply-To: <20190228070048.49BF086B2B@whitealder.osuosl.org>

Hi Thomas, All

On Thu, Feb 28, 2019 at 07:00:43AM -0000, Thomas Petazzoni wrote:

> Results for branch 'master'
> ===========================
> 
> Classification of failures by reason
> ------------------------------------
> 

...

>                     efl-1.21.1 | 1 

...

> 
> 
> Detail of failures
> ------------------
> 

...

>         i586 |                     efl-1.21.1 | NOK | http://autobuild.buildroot.net/results/62ca120f1e54e8c3ae445f98b2624b526569f007 |     

I tried build this defconfig and it fails for me too. The failure is
caused because mesa3d installs some GL related typedef's which efl
declares them too because GL_ES_VERSION_2_0 is not defined by mesa3d. I
can fix the build only if manually select ES and EGL support for mes3d,
and manually select BR2_PACKAGE_EFL_OPENGLES=y. I really dont know which
part behaves wrongly (mesa3d or efl), so just put here my observation.


P.S.
Perhaps, maybe, it is needed to add checking (during configure) for these
re-defined GL types in efl instead of checking for GLES version definition.

Regards,
Vadim Kochan

      reply	other threads:[~2019-02-28 19:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-28  7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2019-02-27 Thomas Petazzoni
2019-02-28 19:19 ` Vadym Kochan [this message]

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=20190228191921.GA28686@lwo1-lhp-f71841 \
    --to=vadim4j@gmail.com \
    --cc=buildroot@busybox.net \
    /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.