All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Hogan <james.hogan@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gdb: convert to the package infrastructure
Date: Thu, 28 Feb 2013 12:11:35 +0000	[thread overview]
Message-ID: <512F4977.6000402@imgtec.com> (raw)
In-Reply-To: <20130228094741.50f605fc@skate>

Hi Thomas,

On 28/02/13 08:47, Thomas Petazzoni wrote:
> On Thu, 28 Feb 2013 08:39:18 +0000, James Hogan wrote:
> 
>>> * It really doesn't make sense to build host-gdb without a
>>> gdbserver for the target. So I would auto-select gdbserver from
>>> host-gdb.
>>
>> Kgdb (kernel debugging) is one use case where you'd want host-gdb
>> without necessarily gdbserver.
> 
> Hum, correct.
> 
>>> * Does it really make sense to keep options for four different gdb
>>> versions? Can't we just remove the user-selectable version
>>> completely?
>>
>> The option is useful for arches which don't have their gdb port
>> upstream yet, giving them a chance to update their patches.
> 
> Not sure to follow here: Arnout mentions the choice list of gdb
> versions, which only have a limited number of choices already. If you
> need Buildroot to use some custom gdb version, then you already have to
> modify Buildroot anyway. Or maybe I'm missing the point you're making?

Yes, but the modification is as simple as adding a patch file in the
right place.

Cheers
James

  reply	other threads:[~2013-02-28 12:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26 22:13 [Buildroot] [PATCH] gdb: convert to the package infrastructure Thomas Petazzoni
2013-02-28  8:00 ` Arnout Vandecappelle
2013-02-28  8:39   ` James Hogan
2013-02-28  8:47     ` Thomas Petazzoni
2013-02-28 12:11       ` James Hogan [this message]
2013-02-28 12:20         ` Thomas Petazzoni
2013-02-28 12:24           ` James Hogan
2013-02-28  8:56   ` Thomas Petazzoni
2013-03-01 21:42     ` Arnout Vandecappelle

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=512F4977.6000402@imgtec.com \
    --to=james.hogan@imgtec.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.