From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gdb: fix gnulib issue with musl and uClibc toolchains
Date: Sun, 24 Jul 2016 16:26:40 +0200 [thread overview]
Message-ID: <20160724162640.20156247@free-electrons.com> (raw)
In-Reply-To: <9f0b5f73-7c32-2a3d-7ed1-d15869b6f855@gmail.com>
Hello,
On Sun, 24 Jul 2016 16:24:37 +0200, Romain Naour wrote:
> The issue appear with gdb 7.11.1 only, that's due to bundled gnulib version has
> been updated.
> We didn't see this issue in the autobuilders since gdb 7.11.1 is not tested (not
> the default Kconfig choice)
Aah, ok! I indeed tested with gdb 7.10 and not 7.11. I think the fact
that it happens only starting with gdb 7.11 was missing in your commit
log :-)
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-07-24 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-23 16:50 [Buildroot] [PATCH] package/gdb: fix gnulib issue with musl and uClibc toolchains Romain Naour
2016-07-24 13:55 ` Thomas Petazzoni
2016-07-24 14:13 ` Romain Naour
2016-07-24 14:17 ` Thomas Petazzoni
2016-07-24 14:24 ` Romain Naour
2016-07-24 14:26 ` 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=20160724162640.20156247@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