From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] qt-4.8.7 ICE on powerpc [was: [autobuild.buildroot.net] Build results for 2018-05-31]
Date: Fri, 1 Jun 2018 14:24:01 +0200 [thread overview]
Message-ID: <20180601142401.63697c3b@windsurf> (raw)
In-Reply-To: <bd26e178-b204-056d-3646-7ececd9964d5@mind.be>
Hello,
On Fri, 1 Jun 2018 13:12:56 +0200, Arnout Vandecappelle wrote:
> > On Fri, 1 Jun 2018 09:58:01 +0200, Arnout Vandecappelle wrote:
> >> On 01-06-18 08:00, Thomas Petazzoni wrote:
> >>> powerpc | qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/cebd1d3d013d40bf71bf20696c28818f58d9533a | ORPH
> >>
> >> This one has also been failing for a *long* time. It is caused by
> >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60818
> >
> > Doesn't this bug report claims that the issue has been fixed in gcc
> > 6.x... but still the autobuild failure happens with a gcc 6.x based
> > toolchain ?
>
> Well, a single bug report sometimes contains multiple bugs :-). Apparently part
> of the problem was only fixed in GCC7.2, and it's possible that some part is not
> fixed yet.
If a single bug report contains multiple bugs, then our
BR2_TOOLCHAIN_GCC_HAS_BUG_xyz naming has a serious problem :-)
Is this specific Qt4 issue resolved with gcc 7.x ? Some testing on this
would be nice.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-06-01 12:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-05-31 Thomas Petazzoni
2018-06-01 7:58 ` [Buildroot] qt-4.8.7 ICE on powerpc [was: [autobuild.buildroot.net] Build results for 2018-05-31] Arnout Vandecappelle
2018-06-01 9:06 ` Thomas Petazzoni
2018-06-01 11:12 ` Arnout Vandecappelle
2018-06-01 12:24 ` Thomas Petazzoni [this message]
2018-06-07 21:48 ` Arnout Vandecappelle
2018-06-08 16:22 ` Peter Korsgaard
2018-06-01 12:48 ` [Buildroot] [autobuild.buildroot.net] Build results for 2018-05-31 Matthew Weber
2018-06-01 12:57 ` Thomas Petazzoni
2018-06-01 13:12 ` Matthew Weber
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=20180601142401.63697c3b@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