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: Wed, 15 Mar 2017 09:12:41 +0100	[thread overview]
Message-ID: <20170315091241.40a1a396@free-electrons.com> (raw)
In-Reply-To: <trinity-fe2675f8-6575-4221-b2c0-58c922f95d24-1489559834487@3capp-mailcom-bs10>

Hello,

On Wed, 15 Mar 2017 07:37:14 +0100, daggs wrote:

> not sure I follow, I was able to compile libepoxy with odroid-mali without any problem, what issue have you encountered?

Exactly the issue you mentioned in your e-mail: "the above will fail
libepoxy on Xlib.h no such file or directory found".

You solved it by enabling X11, but this is wrong. When you're doing
OpenGL ES + EGL, you don't necessarily need X11, so it shouldn't be
necessary to enable X11.

Best regards,

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

  reply	other threads:[~2017-03-15  8:12 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 [this message]
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

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=20170315091241.40a1a396@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