All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Stafford Horne <shorne@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [for-master 2/2] package/gdb: prevent gdbserver being selected for or1k builds
Date: Mon, 29 Aug 2022 19:45:04 +0200	[thread overview]
Message-ID: <970c1ae5-66dc-6154-669e-7872441fda9b@gmail.com> (raw)
In-Reply-To: <20220829154642.60430d08@windsurf>

Hello Thomas,

Le 29/08/2022 à 15:46, Thomas Petazzoni a écrit :
> Hello Romain,
> 
> On Sat, 27 Aug 2022 18:14:31 +0200
> Romain Naour <romain.naour@gmail.com> wrote:
> 
>> 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
>>
>> Signed-off-by: Romain Naour <romain.naour@gmail.com>
>> Cc: Stafford Horne <shorne@gmail.com>
>> ---
>> gdbserver for or1k requires gdb 12.1 [1] but this version is
>> not available in Buildroot 2022.08 and only in the next branch
>> (upcoming 2022.011).
> 
> But in:
> 
> commit 991b7b990ad8cd4a37564cd91d5bb0ee7e1e9f11
> Author: Stafford Horne <shorne@gmail.com>
> Date:   Sat Jul 30 07:07:48 2022 +0900
> 
>     package/gdb: Enable OpenRISC GDB support
>     
>     The OpenRiSC gdb port has supported native debugging since version 8.3
>     and remote debugging since before that.  So it is now safe to enabled
>     this.
>     
>     This patch removes the conditions blocking gdb from being built on or1k
>     architecture builds.
>     
>     Signed-off-by: Stafford Horne <shorne@gmail.com>
>     Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
> 
> Stafford said that "remote debugging" works.

I'm not sure about "remote debugging" but the commit I'm referring is titled
"gdb: or1k: implement gdb server"

I noticed that or1k entry is missing in gdbserver/configure.srv until gdb 12.

> 
> So, what is correct? :-)

I guess git has the answer:

$ git tag --contains 4933265c3f71b9134363d0c05f09542d5cc677f4
binutils-2_38
binutils-2_39
gdb-12-branchpoint
gdb-12.1-release

Best regards,
Romain

> 
> Thomas

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

  reply	other threads:[~2022-08-29 17:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-27 16:14 [Buildroot] [for-master 1/2] package/glibc: glibc on or1k needs a toolchain w/ headers >= 5.4 Romain Naour
2022-08-27 16:14 ` [Buildroot] [for-master 2/2] package/gdb: prevent gdbserver being selected for or1k builds Romain Naour
2022-08-29 13:46   ` Thomas Petazzoni via buildroot
2022-08-29 17:45     ` Romain Naour [this message]
2022-08-30 21:19   ` Arnout Vandecappelle
2022-08-30 20:33 ` [Buildroot] [for-master 1/2] package/glibc: glibc on or1k needs a toolchain w/ headers >= 5.4 Arnout Vandecappelle
2022-09-18  7:02 ` Peter Korsgaard

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=970c1ae5-66dc-6154-669e-7872441fda9b@gmail.com \
    --to=romain.naour@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=shorne@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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.