All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/qt5/qt5webengine: fix build error
Date: Wed, 1 Apr 2020 17:03:48 +0200	[thread overview]
Message-ID: <20200401170348.72cf210f@windsurf.home> (raw)
In-Reply-To: <238c867c-5852-8295-d62e-ee6bf6812391@benettiengineering.com>

Hello Giulio,

Reviving this old thread.

On Fri, 20 Dec 2019 12:43:30 +0100
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:

> > Some googling leads to
> > https://github.com/OSSystems/meta-browser/issues/135, which itself
> > links to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83623.
> > 
> > It seems like the bug has been fixed in both the gcc 6.x (fix was in gcc 6.5.0) and gcc 7.x
> > branches (fix was in gcc 7.3.0).  
> 
> And indeed I've built it successfully with gcc 7.5.

For the record, I'm hitting this compiler bug when building
qt5webengine on Buildroot 2019.02.x with gcc 7.4.0. I double checked,
and the fix pointed at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83623 has been merged in
gcc 7.3.0, so it definitely is in gcc 7.4.0.

I am now trying to rebuild with gcc 7.5.0, since you said it was
successful for you. If it is, then the issue was not gcc bug 83623.

Best regards,

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

  parent reply	other threads:[~2020-04-01 15:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-30 11:58 [Buildroot] [PATCH] package/qt5/qt5webengine: fix build error Bartosz Bilas
2019-07-30 14:03 ` Thomas Petazzoni
2019-07-30 16:06   ` Bartosz Biłas
2019-07-30 21:30 ` Peter Seiderer
2019-07-31  7:15   ` Bartosz Biłas
2019-08-11 20:30     ` Thomas Petazzoni
2019-09-04 11:54       ` Andreas Naumann
2019-12-20 11:43       ` Giulio Benetti
2019-12-20 17:16         ` Bartosz Bilas
2020-04-01 15:03         ` Thomas Petazzoni [this message]
2020-04-02  5:35           ` 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=20200401170348.72cf210f@windsurf.home \
    --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.