From: Joel Brobecker <brobecker@adacore.com>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: Chung-Ju Wu <jasonwucj@gmail.com>,
Pedro Alves <palves@redhat.com>,
"binutils@sourceware.org" <binutils@sourceware.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Wei-Cheng Wang <cole945@gmail.com>,
Kuan-Lin Chen <kuanlinchentw@gmail.com>
Subject: top-level configure regenerated (was: "Re: [PATCH, nds32] Exclude building gdb for nds32*-*-* target.")
Date: Fri, 05 Sep 2014 19:27:00 -0000 [thread overview]
Message-ID: <20140905192755.GA8976@adacore.com> (raw)
In-Reply-To: <540A0A9E.5080709@oarcorp.com>
[-- Attachment #1: Type: text/plain, Size: 564 bytes --]
> Please regenerate it and commit it. I posted asking for that a few
> weeks ago. It is a top level configure and someone who touches it more
> routinely should do it.
That's really quick and easy to do, so I've done it (patch attached).
But I also think that it's the same as any other configure script
regeneration, so anyone hacking configure scripts should feel free
to do it as well. Usually, reviewing the differences introduced during
the regeneration is sufficient to be confident about the update.
ChangeLog:
* configure: Regenerate.
--
Joel
[-- Attachment #2: 0001-Regenerate-top-level-configure.patch --]
[-- Type: text/x-diff, Size: 1498 bytes --]
From f8797b5ad9aa357d80578ce020e95f1c43de7c9a Mon Sep 17 00:00:00 2001
From: Joel Brobecker <brobecker@adacore.com>
Date: Fri, 5 Sep 2014 12:19:56 -0700
Subject: [PATCH] Regenerate top-level configure.
Our top-level configure somehow got out of sync the current
configure.ac, so this patch regenerates it.
ChangeLog:
* configure: Regenerate.
---
ChangeLog | 4 ++++
configure | 8 ++++----
2 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index e9be42b..e668542 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2014-09-05 Joel Brobecker <brobecker@adacore.com>
+
+ * configure: Regenerate.
+
2014-08-27 Will Newton <will.newton@linaro.org>
* src-release.sh: New file.
diff --git a/configure b/configure
index 26c9886..9fc1c88 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*)
--
1.9.1
next prev parent reply other threads:[~2014-09-05 19:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 7:13 [PATCH, nds32] Exclude building gdb for nds32*-*-* target Chung-Ju Wu
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 ` Joel Brobecker [this message]
2014-09-05 20:10 ` 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=20140905192755.GA8976@adacore.com \
--to=brobecker@adacore.com \
--cc=binutils@sourceware.org \
--cc=cole945@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=jasonwucj@gmail.com \
--cc=joel.sherrill@oarcorp.com \
--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