All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [git commit] package/gdb: prevent gdbserver being selected for or1k builds
Date: Fri, 2 Sep 2022 15:32:21 +0000	[thread overview]
Message-ID: <YxIiBS/gUC6pLboY@oscomms1> (raw)
In-Reply-To: <20220830210429.99DB7881AE@busybox.osuosl.org>

On Tue, Aug 30, 2022 at 10:58:01PM +0200, Arnout Vandecappelle wrote:
> commit: https://git.buildroot.net/buildroot/commit/?id=d16db6d8a405c8410f4e892a3993686a3269bdc2
> branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
> 
> There is currently no version of gdbserver for or1k. Until this
> is implemented we will prevent both the direct and indirect
> selection of gdbserver for or1k builds. In practice this means
> that 'cross gdb for the host' cannot be selected and that
> 'full debugger' must be automatically selected for the gdb target
> package.
> 
> This partially reverts commit 991b7b990ad8cd4a37564cd91d5bb0ee7e1e9f11
> which claimed that gdbserver for or1k was already supported before
> version 8.3. That is not true - the commit that adds gdbserver support
> for or1k [1] was only merged for version 12.1, which hasn't been
> integrated in Buildroot yet.

Thanks, sorry for that.  The gdbserver support is a bit newer (last year?)
compared to gdb which was added several years ago.

-Stafford
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-09-02 15:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 20:58 [Buildroot] [git commit] package/gdb: prevent gdbserver being selected for or1k builds Arnout Vandecappelle
2022-09-02 15:32 ` Stafford Horne [this message]
2022-09-03 12:34   ` Romain Naour

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=YxIiBS/gUC6pLboY@oscomms1 \
    --to=shorne@gmail.com \
    --cc=arnout@mind.be \
    --cc=buildroot@buildroot.org \
    /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.