From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] gdb: add upstream patch to fix inconsistency with glibc header
Date: Tue, 28 Mar 2017 22:07:55 +0200 [thread overview]
Message-ID: <20170328220755.668a4cbb@free-electrons.com> (raw)
In-Reply-To: <20170326224032.10708-1-arnout@mind.be>
Hello,
On Mon, 27 Mar 2017 00:40:31 +0200, Arnout Vandecappelle
(Essensium/Mind) wrote:
> In glibc 2.25, the proc_service.h header was copied from gdb to glibc.
> However, in the process the 'const' was removed, which leads to build
> failures with glibc >= 2.25.
>
> gdb 7.12.1 already contains this patch. The patch for 7.11.1 comes
> straight from upstream, the patch for 7.10.1 is backported by me.
>
> Fixes http://autobuild.buildroot.net/results/6b1b44e72147113b3f0e3f049cb9026d6c7dffb7
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
> ...7-Sync-proc_service-definition-with-GLIBC.patch | 287 +++++++++++++++
> ...2-Sync-proc_service-definition-with-GLIBC.patch | 389 +++++++++++++++++++++
> 2 files changed, 676 insertions(+)
> create mode 100644 package/gdb/7.10.1/0007-Sync-proc_service-definition-with-GLIBC.patch
> create mode 100644 package/gdb/7.11.1/0002-Sync-proc_service-definition-with-GLIBC.patch
Both applied to master. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-03-28 20:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-26 22:40 [Buildroot] [PATCH 1/2] gdb: add upstream patch to fix inconsistency with glibc header Arnout Vandecappelle
2017-03-26 22:40 ` [Buildroot] [PATCH 2/2] gdb: pass gdb_cv_prfpregset_t_broken=no Arnout Vandecappelle
2017-03-28 20:07 ` 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=20170328220755.668a4cbb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox