From: Dagg Stompler <daggs@gmx.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] Revert "odroid-mali: mark package as BROKEN"
Date: Mon, 13 Mar 2017 11:08:34 +0200 [thread overview]
Message-ID: <20170313090834.13715-2-daggs@gmx.com> (raw)
In-Reply-To: <20170313090834.13715-1-daggs@gmx.com>
This reverts commit e2ac546c1951ba8a3e88965d3023eb38a9493f28.
as upstream fixed the reported issue, unmark this pkg as BROKEN.
Signed-off-by: Dagg Stompler <daggs@gmx.com>
---
package/odroid-mali/Config.in | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/package/odroid-mali/Config.in b/package/odroid-mali/Config.in
index 5a6af7504..e5c07f237 100644
--- a/package/odroid-mali/Config.in
+++ b/package/odroid-mali/Config.in
@@ -5,16 +5,6 @@ config BR2_PACKAGE_ODROID_MALI
select BR2_PACKAGE_ODROID_SCRIPTS # runtime
depends on BR2_TOOLCHAIN_USES_GLIBC
depends on BR2_aarch64 || BR2_ARM_EABIHF
- # The version of the khrplatform.h header bundled with
- # odroid-mali has a definition of the khronos_intptr_t and
- # khronos_ssize_t that doesn't match the official Khronos
- # registry headers or the Mesa3D headers. Due to this, it
- # causes conflicts with some packages that redefines those
- # types (with the correct definitions), such as libepoxy.
- #
- # Issue reported upstream at:
- # https://github.com/mdrjr/c2_mali/issues/1
- depends on BROKEN
help
Install the ARM Mali drivers for odroidc2 based systems.
--
2.12.0
next prev parent reply other threads:[~2017-03-13 9:08 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 ` Dagg Stompler [this message]
2017-03-13 12:33 ` 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
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=20170313090834.13715-2-daggs@gmx.com \
--to=daggs@gmx.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