From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] qt: Allow enabling of QtWebKit with GCC 6+
Date: Tue, 19 Sep 2017 18:41:33 +0200 [thread overview]
Message-ID: <20170919184133.77dd6d16@windsurf> (raw)
In-Reply-To: <20170919091444.34950-1-didin@synopsys.com>
Hello,
On Tue, 19 Sep 2017 12:14:44 +0300, Evgeniy Didin wrote:
> Building Qt with QtWebKit on configuration step there is
> a check which disables QtWebKit build with GCC 6+.
> Back in the day nobody thought about building Qt with GCC
> version greater than 5.x. And now with modern GCCs like
> 6.x and 7.x this assumption gets in the way.
>
> Given in Buildroot today we don't have GCC older than 4.9
> it should be safe to remove now meaningless check completely.
>
> Signed-off-by: Evgeniy Didin <didin@synopsys.com>
> Cc: Alexey Brodkin <abrodkin@synopsys.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>
> ---
> configure | 14 --------------
> 1 file changed, 14 deletions(-)
I am not sure what you expect us to do with this patch: indeed it is
not a Buildroot patch as Buildroot does not have a configure script.
Perhaps you wanted instead to do a patch that adds a patch in
package/qt/ instead ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-09-19 16:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 9:14 [Buildroot] [PATCH] qt: Allow enabling of QtWebKit with GCC 6+ Evgeniy Didin
2017-09-19 16:41 ` Thomas Petazzoni [this message]
2017-09-19 19:37 ` Arnout Vandecappelle
-- strict thread matches above, loose matches on Subject: below --
2017-09-22 12:50 Evgeniy Didin
2017-10-03 19:59 ` Thomas Petazzoni
2017-10-14 7:49 ` Peter Korsgaard
2017-10-17 9:02 ` Peter Korsgaard
2017-10-17 15:02 ` Alexey Brodkin
2017-10-24 6:15 ` 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=20170919184133.77dd6d16@windsurf \
--to=thomas.petazzoni@free-electrons.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