All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit branch/2019.02.x] qt5base: Add patch to fix compile issue with gcc9
Date: Thu, 19 Sep 2019 21:49:33 +0200	[thread overview]
Message-ID: <20190919214933.58202b9f@windsurf> (raw)
In-Reply-To: <20190919073529.30254-1-julien.beraud@orolia.com>

On Thu, 19 Sep 2019 07:36:05 +0000
Julien B?raud <julien.beraud@orolia.com> wrote:

> Backport:
> https://github.com/qt/qtbase/commit/a52d7861edfb5956de38ba80015c4dd0b596259b#diff-0b4819f9df9c43297ba840d1ac401599
> Signed-off-by: Julien Beraud <julien.beraud@orolia.com>

With an extended commit log explaining that it fixes an issue when
building Qt5 on a machine with gcc9 as its system compiler, and a blank
line before the SoB:

Acked-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

(I actually had the exact same patch sitting around in one of my
branch, as I encountered the same issue working on 2019.02 Qt5 project)

Thanks,

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

  parent reply	other threads:[~2019-09-19 19:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19  7:36 [Buildroot] [git commit branch/2019.02.x] qt5base: Add patch to fix compile issue with gcc9 Julien Béraud
2019-09-19 15:26 ` Peter Korsgaard
2019-09-19 16:07   ` Julien Béraud
2019-09-19 16:46     ` Peter Korsgaard
2019-09-20  8:26       ` Julien Béraud
2019-09-19 19:48     ` Thomas Petazzoni
2019-09-20  7:50       ` Julien Béraud
2019-09-20  7:53         ` Thomas Petazzoni
2019-09-20  8:02           ` Julien Béraud
2019-09-19 19:49 ` Thomas Petazzoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-10-01 21:49 Peter Korsgaard

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=20190919214933.58202b9f@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.