From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain: GCC bug 85862
Date: Thu, 7 Jun 2018 15:11:28 +0200 [thread overview]
Message-ID: <20180607151128.2ca5e5ea@windsurf> (raw)
In-Reply-To: <647b5badffcc071f204e324a62cfc8dc@230ruedubac.fr>
Hello,
On Thu, 07 Jun 2018 14:43:46 +0200, davidb wrote:
> Regarding the commit id bd03966d4ebeb284ac3afb5f3b8cba13da2b9983 that
> disables qt5webengine when the bug 85862 can be triggered on microblaze
> arch, I can't enable qt5webengine when selecting QT5 Latest version
> (5.10) and x86_64 arch.
>
> I think the test about the bug should be inverted:
>
> diff --git a/package/qt5/qt5webengine/Config.in
> b/package/qt5/qt5webengine/Config.in
> index 38486c6dcf..744d659567 100644
> --- a/package/qt5/qt5webengine/Config.in
> +++ b/package/qt5/qt5webengine/Config.in
> @@ -31,7 +31,7 @@ config BR2_PACKAGE_QT5WEBENGINE
> depends on BR2_TOOLCHAIN_USES_GLIBC # execinfo.h, mallinfo
> depends on BR2_HOST_GCC_AT_LEAST_4_8 # qt5base-icu
> depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_8 # qt5base-icu
> - depends on BR2_TOOLCHAIN_HAS_GCC_BUG_85862 ||
> BR2_PACKAGE_QT5_VERSION_5_6 # libnss
> + depends on !BR2_TOOLCHAIN_HAS_GCC_BUG_85862 ||
> BR2_PACKAGE_QT5_VERSION_5_6 # libnss
Gah, indeed! Could you send a patch to fix this ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-06-07 13:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 20:29 [Buildroot] [PATCH] toolchain: GCC bug 85862 Matt Weber
2018-05-21 21:49 ` Peter Korsgaard
2018-05-22 21:00 ` Thomas Petazzoni
2018-05-23 20:38 ` Romain Naour
2018-05-23 20:57 ` Matthew Weber
2018-05-23 21:08 ` Romain Naour
2018-05-23 21:55 ` Matthew Weber
2018-06-07 12:43 ` davidb
2018-06-07 13:11 ` Thomas Petazzoni [this message]
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=20180607151128.2ca5e5ea@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox