From: Adrian Perez de Castro <aperez@igalia.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] package/brotli: disable for microblaze
Date: Sat, 16 Feb 2019 15:45:28 +0200 [thread overview]
Message-ID: <20190216134530.14717-2-aperez@igalia.com> (raw)
In-Reply-To: <20190216134530.14717-1-aperez@igalia.com>
The brotli package cannot be currently built due to a compiler bug. Not
many packages use it so the impact of disabling it for Microblaze will
be small: only libcurl and woff2 use it; and woff2 is used by webkitgtk
which itself can be built without the woff2 support.
This fixes the following autobuilder failure:
http://autobuild.buildroot.net/results/1b6e6c5fddf3538ed7f150294c3d8fa94b3e4c59/
Signed-off-by: Adrian Perez de Castro <aperez@igalia.com>
---
package/brotli/Config.in | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/package/brotli/Config.in b/package/brotli/Config.in
index e40f5b6b9f..f2a4bdd8e9 100644
--- a/package/brotli/Config.in
+++ b/package/brotli/Config.in
@@ -1,5 +1,10 @@
config BR2_PACKAGE_BROTLI
bool "brotli"
+ # Building on Microblaze is currently broken due to the following
+ # GCC bugs, which affect all versions currently available:
+ # - https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78380
+ # - https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69401
+ depends on !BR2_microblaze
help
Generic-purpose lossless compression library. The algorithm
compresses data using a combination of a modern variant of
--
2.20.1
next prev parent reply other threads:[~2019-02-16 13:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-16 13:45 [Buildroot] [PATCH 0/3] Disable brotli for Microblaze and propagate dependecies Adrian Perez de Castro
2019-02-16 13:45 ` Adrian Perez de Castro [this message]
2019-02-16 13:45 ` [Buildroot] [PATCH 2/3] package/woff2: propagate microblaze dependecy Adrian Perez de Castro
2019-02-16 13:45 ` [Buildroot] [PATCH 3/3] package/webkitgtk: propagate microblaze dependency Adrian Perez de Castro
2019-02-19 22:25 ` Arnout Vandecappelle
2019-02-22 9:50 ` Adrian Perez de Castro
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=20190216134530.14717-2-aperez@igalia.com \
--to=aperez@igalia.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