From: Stafford Horne <shorne@gmail.com>
To: buildroot@buildroot.org
Cc: Stafford Horne <shorne@gmail.com>
Subject: [Buildroot] [PATCH] package/gdb: Enable OpenRISC GDB support
Date: Sat, 30 Jul 2022 07:07:48 +0900 [thread overview]
Message-ID: <20220729220748.3737915-1-shorne@gmail.com> (raw)
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>
---
package/gdb/Config.in | 1 -
package/gdb/Config.in.host | 1 -
2 files changed, 2 deletions(-)
diff --git a/package/gdb/Config.in b/package/gdb/Config.in
index a39837fe71..2708834ee2 100644
--- a/package/gdb/Config.in
+++ b/package/gdb/Config.in
@@ -3,7 +3,6 @@ config BR2_PACKAGE_GDB_ARCH_SUPPORTS
default y
depends on !((BR2_arm || BR2_armeb) && BR2_BINFMT_FLAT)
depends on !BR2_microblaze
- depends on !BR2_or1k
comment "gdb/gdbserver needs a toolchain w/ threads, threads debug"
depends on BR2_PACKAGE_GDB_ARCH_SUPPORTS
diff --git a/package/gdb/Config.in.host b/package/gdb/Config.in.host
index 43af64a1ed..dfa9f8c384 100644
--- a/package/gdb/Config.in.host
+++ b/package/gdb/Config.in.host
@@ -3,7 +3,6 @@ config BR2_PACKAGE_HOST_GDB_ARCH_SUPPORTS
default y
depends on !((BR2_arm || BR2_armeb) && BR2_BINFMT_FLAT)
depends on !BR2_microblaze
- depends on !BR2_or1k
comment "Host GDB Options"
depends on !BR2_TOOLCHAIN_EXTERNAL_GDB_SERVER_COPY
--
2.37.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-07-29 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 22:07 Stafford Horne [this message]
2022-07-30 14:48 ` [Buildroot] [PATCH] package/gdb: Enable OpenRISC GDB support Yann E. MORIN
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=20220729220748.3737915-1-shorne@gmail.com \
--to=shorne@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox