Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Chung-Ju Wu <jasonwucj@gmail.com>
To: Pedro Alves <palves@redhat.com>,
	binutils@sourceware.org, gdb-patches@sourceware.org
Cc: Wei-Cheng Wang <cole945@gmail.com>,
	Kuan-Lin Chen <kuanlinchentw@gmail.com>
Subject: [PATCH, nds32] Exclude building gdb for nds32*-*-* target.
Date: Fri, 05 Sep 2014 07:13:00 -0000	[thread overview]
Message-ID: <CADj25HPBucRuGhD6GrHfJct5cibNrcZ5FuGn67CB5o6zYXrdyw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 810 bytes --]

Hi, gdb & binutils maintainers,

Currently the nds32 port for gdb is still under contribution process.
So the gdb has not been supported yet for --target=nds32*-*-*.
It would be good if we can disable gdb before nds32 port for gdb is ready.

The attachment is the patch of configure.ac and I use autoconf 2.64
to regenerate configure.  But I notice some inconsistent changes between
configure.ac and configure.  Looks like there was something wrong on
previous commit 1f995db6ad2c9325a8db45b73fea29c8ab9200e1 ... and I just
accidentally fix it in this patch when regenerating configure. :p

The plain text ChangeLog is as below, is this patch OK for commit?


2014-09-05  Chung-Ju Wu  <jasonwucj@gmail.com>

    * configure.ac (nds32*-*-*): Disable gdb.
    * configure: Regenerated.


Best regards,
jasonwucj

[-- Attachment #2: 0001-Disable-gdb-for-nds32-until-supported.patch --]
[-- Type: application/octet-stream, Size: 1656 bytes --]

From a96bc4c1638187e18a6e2f71e2c158dddcf5d68f Mon Sep 17 00:00:00 2001
From: Chung-Ju Wu <jasonwucj@andestech.com>
Date: Fri, 5 Sep 2014 14:56:57 +0800
Subject: [PATCH] Disable gdb for nds32*-*-* until supported.

---
 configure    | 11 +++++++----
 configure.ac |  3 +++
 2 files changed, 10 insertions(+), 4 deletions(-)

diff --git a/configure b/configure
index 26c9886..dfea3bd 100755
--- a/configure
+++ b/configure
@@ -3369,10 +3369,6 @@ case "${target}" in
     ;;
   *-*-rtems*)
     noconfigdirs="$noconfigdirs ${libgcj}"
-    # this is not caught below because this stanza matches earlier
-    case $target in
-      or1k*-*-*) noconfigdirs="$noconfigdirs gdb" ;;
-    esac
     ;;
   *-*-tpf*)
     noconfigdirs="$noconfigdirs ${libgcj}"
@@ -3607,6 +3603,10 @@ case "${target}" in
     ;;
   *-*-rtems*)
     noconfigdirs="$noconfigdirs target-libgloss"
+    # this is not caught below because this stanza matches earlier
+    case $target in
+      or1k*-*-*) noconfigdirs="$noconfigdirs gdb" ;;
+    esac
     ;;
     # The tpf target doesn't support gdb yet.
   *-*-tpf*)
@@ -3805,6 +3805,9 @@ case "${target}" in
   mips*-*-*)
     noconfigdirs="$noconfigdirs gprof"
     ;;
+  nds32*-*-*)
+    noconfigdirs="$noconfigdirs gdb"
+    ;;
   or1k*-*-*)
     noconfigdirs="$noconfigdirs gdb"
     ;;
diff --git a/configure.ac b/configure.ac
index 028cbda..dada090 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1133,6 +1133,9 @@ case "${target}" in
   mips*-*-*)
     noconfigdirs="$noconfigdirs gprof"
     ;;
+  nds32*-*-*)
+    noconfigdirs="$noconfigdirs gdb"
+    ;;
   or1k*-*-*)
     noconfigdirs="$noconfigdirs gdb"
     ;;
-- 
1.9.0


             reply	other threads:[~2014-09-05  7:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-05  7:13 Chung-Ju Wu [this message]
2014-09-05 13:51 ` Joel Sherrill
2014-09-05 17:00   ` Joel Brobecker
2014-09-05 19:10     ` Joel Sherrill
2014-09-05 19:27       ` top-level configure regenerated (was: "Re: [PATCH, nds32] Exclude building gdb for nds32*-*-* target.") Joel Brobecker
2014-09-05 20:10       ` [PATCH, nds32] Exclude building gdb for nds32*-*-* target Chung-Ju Wu
2014-09-05 20:29         ` Joel Brobecker

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=CADj25HPBucRuGhD6GrHfJct5cibNrcZ5FuGn67CB5o6zYXrdyw@mail.gmail.com \
    --to=jasonwucj@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=cole945@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kuanlinchentw@gmail.com \
    --cc=palves@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox