From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-16
Date: Mon, 20 Feb 2017 16:10:52 +0100 [thread overview]
Message-ID: <20170220161052.48208eac@free-electrons.com> (raw)
In-Reply-To: <20170220145933.GQ12810@waldemar-brodkorb.de>
Hello,
On Mon, 20 Feb 2017 15:59:33 +0100, Waldemar Brodkorb wrote:
> I am not entirely sure, but can the reason for this be this patch we
> apply on top of gcc 5.4.x
> package/gcc/5.4.0/850-libstdcxx-uclibc-c99.patch?
>
> I think all failures relate to some C++ header failures. Can anybody
> try with this patch applied?
Indeed could be the reason. Worth checking before we apply tons of
patches to individual packages.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-20 15:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 7:28 [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-16 Thomas Petazzoni
2017-02-17 21:12 ` Yann E. MORIN
2017-02-17 22:01 ` Yann E. MORIN
2017-02-17 22:02 ` Waldemar Brodkorb
2017-02-18 8:49 ` Peter Korsgaard
2017-02-20 12:41 ` Thomas Petazzoni
2017-02-20 14:59 ` Waldemar Brodkorb
2017-02-20 15:10 ` Thomas Petazzoni [this message]
2017-02-20 18:14 ` Bernd Kuhls
2017-02-20 22:40 ` Peter Korsgaard
2017-02-20 22:46 ` Thomas Petazzoni
2017-02-20 22:59 ` Peter Korsgaard
2017-02-21 8:05 ` Arnout Vandecappelle
2017-02-21 8:27 ` Thomas Petazzoni
2017-02-21 8:46 ` Arnout Vandecappelle
2017-02-21 8:55 ` Thomas Petazzoni
2017-02-24 14:37 ` Julien Boibessot
2017-02-24 14:48 ` Thomas Petazzoni
2017-02-25 1:47 ` Waldemar Brodkorb
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=20170220161052.48208eac@free-electrons.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.