From: Peter Korsgaard <peter@korsgaard.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 18:46:41 +0200 [thread overview]
Message-ID: <87a7b01bf2.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <24a3771b-2bf4-66a7-2b84-13eeb87488c3@orolia.com> ("Julien Béraud"'s message of "Thu, 19 Sep 2019 16:07:33 +0000")
>>>>> "Julien" == Julien B?raud <julien.beraud@orolia.com> writes:
> On 19/09/2019 17:26, Peter Korsgaard wrote:
>>>>>>> "Julien" == Julien B?raud <julien.beraud@orolia.com> writes:
>>
>> > Backport:
>> > https://github.com/qt/qtbase/commit/a52d7861edfb5956de38ba80015c4dd0b596259b#diff-0b4819f9df9c43297ba840d1ac401599
>> > Signed-off-by: Julien Beraud <julien.beraud@orolia.com>
>>
>> Ehh, I got a bit confused first as this looked like a git commit
>> notification.
> Sorry I am just referring to the commit in the upstream project
>>
>> Why would this be applicable for 2019.02.x? We don't offer gcc9 support
>> in 2019.02.x.
> This issue happens when trying to build qt5 on buildroot on a machine
> that has gcc9 (native) installed. It is not a cross-compilation issue.
> Do you mean that you don't want to support that ?
No, that we do want to support - But this wasn't clear from your commit
message.
What about qt 5.6? Do we need a similar patch there?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-09-19 16:46 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 [this message]
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
-- 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=87a7b01bf2.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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