From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] package/uclibc: add upstream patch to fix build issue with gcc7
Date: Wed, 24 May 2017 16:21:24 +0200 [thread overview]
Message-ID: <20170524162124.7d8cd4c4@free-electrons.com> (raw)
In-Reply-To: <20170523202440.6949-1-romain.naour@gmail.com>
Hello,
On Tue, 23 May 2017 22:24:38 +0200, Romain Naour wrote:
> As reported on the mailing list [1], there is a build issue with gcc 7
> and uClibc-ng.
>
> Thanks to Waldemar for the fix :)
>
> [1] http://lists.busybox.net/pipermail/buildroot/2017-May/191140.html
>
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> Cc: Waldemar Brodkorb <wbx@openadk.org>
> ---
> ...es.h-with-GNU-C-library-fixes-gcc-7.1-too.patch | 64 ++++++++++++++++++++++
> 1 file changed, 64 insertions(+)
> create mode 100644 package/uclibc/0001-sync-features.h-with-GNU-C-library-fixes-gcc-7.1-too.patch
Applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-05-24 14:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 20:24 [Buildroot] [PATCH v2 1/3] package/uclibc: add upstream patch to fix build issue with gcc7 Romain Naour
2017-05-23 20:24 ` [Buildroot] [PATCH v2 2/3] package/gcc: add support for gcc 7 Romain Naour
2017-05-24 14:26 ` Thomas Petazzoni
2017-05-24 14:37 ` Waldemar Brodkorb
2017-05-24 14:47 ` Alexey Brodkin
2017-05-25 17:52 ` Romain Naour
2017-05-23 20:24 ` [Buildroot] [PATCH v2 3/3] package/gcc: remove gcc 4.8 Romain Naour
2017-05-24 14:21 ` 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=20170524162124.7d8cd4c4@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.