From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gdb: move version selection from gdb.mk to Config.in.host
Date: Mon, 3 Feb 2014 22:32:32 +0100 [thread overview]
Message-ID: <20140203223232.58bce1dc@skate> (raw)
In-Reply-To: <1391031881-19546-1-git-send-email-arnout@mind.be>
Dear Arnout Vandecappelle (Essensium/Mind),
On Wed, 29 Jan 2014 22:44:41 +0100, Arnout Vandecappelle
(Essensium/Mind) wrote:
> This avoids duplication of the version selection between these two files.
>
> Cc: Spenser Gilliland <spenser@gillilanding.com>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
> Warning: I have not really tested this!
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
> package/gdb/Config.in.host | 14 +++++++++-----
> package/gdb/gdb.mk | 14 --------------
> 2 files changed, 9 insertions(+), 19 deletions(-)
Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
I haven't actually built this, but I've done some testing by looking at
the .config file, and it indeed contains a proper BR2_GDB_VERSION value
even when a cross-gdb is not being built. Therefore, I'm fairly
confident that this patch is OK to be applied.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-03 21:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 21:51 [Buildroot] [PATCH v2] gcc: coexist upstream with vendor git releases for mb and arc Spenser Gilliland
2014-01-27 21:51 ` [Buildroot] [PATCH v2] gdb: use git version for cross-gdb Spenser Gilliland
2014-01-29 21:39 ` Arnout Vandecappelle
2014-01-29 21:44 ` [Buildroot] [PATCH] gdb: move version selection from gdb.mk to Config.in.host Arnout Vandecappelle
2014-01-30 1:29 ` Spenser Gilliland
2014-01-30 7:57 ` Arnout Vandecappelle
2014-02-03 21:32 ` Thomas Petazzoni [this message]
2014-02-08 22:11 ` Peter Korsgaard
2014-01-27 21:51 ` [Buildroot] [PATCH v2] binutils: whitespace cleanup Spenser Gilliland
2014-02-03 21:33 ` Thomas Petazzoni
2014-02-04 8:49 ` Peter Korsgaard
2014-01-27 21:51 ` [Buildroot] [PATCH v2] binutils: coexist upstream and vendor binutils for arc and microblaze Spenser Gilliland
2014-01-27 21:51 ` [Buildroot] [PATCH v2] libnspr: add microblaze support Spenser Gilliland
2014-02-03 21:33 ` Thomas Petazzoni
2014-02-04 8:52 ` Peter Korsgaard
2014-01-27 21:51 ` [Buildroot] [PATCH v2] libsigsegv: fix for microblaze Spenser Gilliland
2014-01-27 21:51 ` [Buildroot] [PATCH v2] pixman: do not build demos or tests Spenser Gilliland
2014-01-29 8:30 ` Peter Korsgaard
2014-07-18 20:21 ` Thomas De Schampheleire
2014-01-27 21:51 ` [Buildroot] [PATCH v2] glibc: change to tagged release Spenser Gilliland
2014-01-27 21:51 ` [Buildroot] [PATCH v2] binutils: " Spenser Gilliland
2014-01-27 21:51 ` [Buildroot] [PATCH v2] gcc: " Spenser Gilliland
2014-01-27 21:51 ` [Buildroot] [PATCH v2] gdb: " Spenser Gilliland
2014-01-28 17:36 ` [Buildroot] [PATCH v2] gcc: coexist upstream with vendor git releases for mb and arc Arnout Vandecappelle
2014-01-28 23:34 ` Spenser Gilliland
2014-01-29 20:58 ` Arnout Vandecappelle
2014-01-30 1:25 ` Spenser Gilliland
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=20140203223232.58bce1dc@skate \
--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