Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] odroid-mali: fix broken headers.
Date: Sun, 19 Mar 2017 09:42:32 +0100	[thread overview]
Message-ID: <20170319094232.4088533c@free-electrons.com> (raw)
In-Reply-To: <trinity-31a9d6e0-5836-4ca5-b1c7-2ba16255609d-1489911005153@3capp-mailcom-bs11>

Hello,

On Sun, 19 Mar 2017 09:10:05 +0100, daggs wrote:

> a question, does the latest gl related patch to libepoxy is relevant
> for this issue? if so, can you comment on how?

It is indeed relevant: if the egl.pc provided by odroid-mali defines
the appropriate -DMESA_EGL_NO_X11_HEADERS in its Cflags when the
non-X11 version of odroid-mali is installed.

That being said, upstream feedback
(https://github.com/anholt/libepoxy/pull/113) on Gustavo patch wasn't
entirely positive, so a different solution might be needed. But in the
mean time, a patch for odroid-mali egl.pc should resolve the issue.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      reply	other threads:[~2017-03-19  8:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-13  9:08 [Buildroot] [PATCH 1/2] odroid-mali: fix broken headers Dagg Stompler
2017-03-13  9:08 ` [Buildroot] [PATCH 2/2] Revert "odroid-mali: mark package as BROKEN" Dagg Stompler
2017-03-13 12:33 ` [Buildroot] [PATCH 1/2] odroid-mali: fix broken headers Thomas Petazzoni
2017-03-13 14:17   ` daggs
2017-03-14 21:54     ` Thomas Petazzoni
2017-03-15  6:37       ` daggs
2017-03-15  8:12         ` Thomas Petazzoni
2017-03-15  9:52           ` daggs
2017-03-15 10:01             ` Thomas Petazzoni
2017-03-19  8:10               ` daggs
2017-03-19  8:42                 ` Thomas Petazzoni [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=20170319094232.4088533c@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox