All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2019-02-13
Date: Thu, 14 Feb 2019 09:39:47 +0100	[thread overview]
Message-ID: <20190214093947.3949384d@windsurf> (raw)
In-Reply-To: <20190214100244.GB15212@momiji>

Hello,

On Thu, 14 Feb 2019 10:02:44 +0200
Adrian Perez de Castro <aperez@igalia.com> wrote:

> On Thu, 14 Feb 2019 07:00:39 -0000, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> 
> > [...]
> >
> > microblazeel |                   brotli-1.0.7 | NOK | http://autobuild.buildroot.net/results/1b6e6c5fddf3538ed7f150294c3d8fa94b3e4c59 |       
> 
> This seems to be the following upstream GCC bug:
> 
>   https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78380
> 
> and likely related to this other one reported by Thomas:
> 
>   https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69401
> 
> Apparently GCC 8.x does not have the issue, so I wonder if it would make
> sense to add a depends on BR2_TOOLCHAIN_GCC_AT_LEAST_{8 or 7} in the brotli
> package when the target is Microblaze.

Did you verify that the issue is fixed with gcc 7.x or gcc 8.x ?

> Only woff2 need brotli (libcurl has an optional dependency), and woff2
> itself is only used by WebKit for Web fonts, and if WOFF2 support is at
> build time in WebKit the rest of Web fonts formats (WOFF1, TTF, etc.)
> still work fine, so I think the disruption would be minimal.
> 
> Does the above sound reasonable to do?

Yes, if the issue no longer happens with gcc >= 7.x, it seems like a
reasonable option.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-02-14  8:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14  7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2019-02-13 Thomas Petazzoni
2019-02-14  8:02 ` Adrian Perez de Castro
2019-02-14  8:39   ` Thomas Petazzoni [this message]
2019-02-15  0:13     ` Adrian Perez de Castro
2019-02-15 11:06       ` Peter Korsgaard
2019-02-15 12:49         ` Adrian Perez de Castro
2019-02-16 13:49           ` 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=20190214093947.3949384d@windsurf \
    --to=thomas.petazzoni@bootlin.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.