From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-05-08
Date: Mon, 09 May 2016 21:18:01 +0200 [thread overview]
Message-ID: <1462821481.2493.5.camel@embedded.rocks> (raw)
In-Reply-To: <20160509063023.2DB5D103487@stock.ovh.net>
On Mo, 2016-05-09 at 08:30 +0200, Thomas Petazzoni wrote:
> Build statistics for 2016-05-08
> ===============================
>
> Detail of failures
> ===================
>
> ??????x86_64 |???????????????????apitrace-7.0 | NOK |
> http://autobuild.buildroot.net/results/7c49bafc67e4173ba93faba12beb19
> 776ac7cb8d/
Looks like GCC bug?54482 [1] produced by static linking with libstdc++.
Any suggestions how to resolve this? Remove GCC 4.7 support?
Add?BR2_TOOLCHAIN_HAS_GCC_BUG_54482?
[1]?https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54482
Best regards
J?rg Krause
prev parent reply other threads:[~2016-05-09 19:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-05-08 Thomas Petazzoni
2016-05-09 19:18 ` Jörg Krause [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=1462821481.2493.5.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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