From: Sergio Durigan Junior <sergiodj@redhat.com>
To: GDB Patches <gdb-patches@sourceware.org>
Cc: Rainer Orth <ro@cebitec.uni-bielefeld.de>,
Joel Brobecker <brobecker@adacore.com>,
Jan Kratochvil <jan.kratochvil@redhat.com>,
binutils@sourceware.org,
Sergio Durigan Junior <sergiodj@redhat.com>
Subject: [PATCH] Add "contrib" to the list of GDB support dirs (on src-release.sh)
Date: Wed, 12 Sep 2018 05:21:00 -0000 [thread overview]
Message-ID: <20180912052059.12729-1-sergiodj@redhat.com> (raw)
In-Reply-To: <20180911120016.GC3379@adacore.com>
On commit:
commit 5a6996172e6294ea37054b1a9caa3a923a8fe399
Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Date: Mon Aug 6 16:05:16 2018 +0200
Update dg-extract-results.* from gcc
dg-extract-results.sh was moved from the "gdb/contrib/" directory to
the toplevel "contrib/" directory. However, src-release.sh was not
updated in order to include "contrib/" in the tarball release of GDB.
This makes it very inconvenient to run and analyze the GDB testsuite
results. This commit adds "contrib/" to the list of support
directories that are included in each GDB release.
ChangeLog:
2018-09-12 Sergio Durigan Junior <sergiodj@redhat.com>
* src-release.sh (GDB_SUPPORT_DIRS): Add "contrib".
---
ChangeLog | 4 ++++
src-release.sh | 2 +-
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/ChangeLog b/ChangeLog
index ad0ed1d0e8..9fe7427b83 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2018-09-12 Sergio Durigan Junior <sergiodj@redhat.com>
+
+ * src-release.sh (GDB_SUPPORT_DIRS): Add "contrib".
+
2018-07-16 Nick Clifton <nickc@redhat.com>
* src-release.sh (DEVO_SUPPORT): Add test-driver and ar-lib.
diff --git a/src-release.sh b/src-release.sh
index d0425d6aab..fe5dab5fb3 100755
--- a/src-release.sh
+++ b/src-release.sh
@@ -313,7 +313,7 @@ gas_release()
tar_compress $package $tool "$GAS_SUPPORT_DIRS" "$compressors"
}
-GDB_SUPPORT_DIRS="bfd include libiberty opcodes readline sim intl libdecnumber cpu zlib"
+GDB_SUPPORT_DIRS="bfd include libiberty opcodes readline sim intl libdecnumber cpu zlib contrib"
gdb_release()
{
compressors=$1
--
2.17.1
next prev parent reply other threads:[~2018-09-12 5:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 11:02 Update dg-extract-results.* from gcc Rainer Orth
2018-07-25 19:08 ` Tom Tromey
2018-07-26 20:54 ` Sergio Durigan Junior
2018-07-31 12:46 ` Rainer Orth
2018-07-31 12:44 ` Rainer Orth
2018-08-06 13:50 ` Rainer Orth
2018-08-07 11:52 ` Rainer Orth
2018-08-07 14:35 ` Pedro Alves
2018-08-08 14:36 ` Rainer Orth
2018-08-08 15:24 ` Pedro Alves
2018-10-01 9:36 ` dg-extract-results's bad sorting behavior (Re: Update dg-extract-results.* from gcc) Pedro Alves
2018-09-11 11:02 ` [obv] Fix dg-extract-results.sh path [Re: Update dg-extract-results.* from gcc] Jan Kratochvil
2018-09-11 11:03 ` Missing toplevel contrib/ in gdb-*.tar.xz " Jan Kratochvil
2018-09-11 11:20 ` Rainer Orth
2018-09-11 12:01 ` Joel Brobecker
2018-09-12 5:21 ` Sergio Durigan Junior [this message]
2018-09-13 14:26 ` [PATCH] Add "contrib" to the list of GDB support dirs (on src-release.sh) Tom Tromey
2018-09-13 16:35 ` Sergio Durigan Junior
2018-09-12 5:23 ` Missing toplevel contrib/ in gdb-*.tar.xz [Re: Update dg-extract-results.* from gcc] Sergio Durigan Junior
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=20180912052059.12729-1-sergiodj@redhat.com \
--to=sergiodj@redhat.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=ro@cebitec.uni-bielefeld.de \
/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