public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Joel Brobecker <brobecke@sourceware.org>
To: bfd-cvs@sourceware.org, gdb-cvs@sourceware.org
Subject: [binutils-gdb/gdb-13-branch] Ensure that libbacktrace/allocfail.sh is not deleted when creating release tarballs.
Date: Thu, 2 Feb 2023 04:54:59 +0000 (GMT) [thread overview]
Message-ID: <20230202045459.E77CF3858401@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=16c45b9ab64de96190fd10f26d3fb17f6948822e
commit 16c45b9ab64de96190fd10f26d3fb17f6948822e
Author: Nick Clifton <nickc@redhat.com>
Date: Thu Feb 2 08:53:45 2023 +0400
Ensure that libbacktrace/allocfail.sh is not deleted when creating release tarballs.
* Makefile.am (CLEANFILES): Import patch from upstream to prevent
allocafail.sh from being removed when running 'make clean'.
(cherry picked from commit edf64cd235f5ecb3725e7cf1ff83bbdb6dd53340)
Diff:
---
libbacktrace/ChangeLog | 5 +++++
libbacktrace/Makefile.am | 2 +-
libbacktrace/Makefile.in | 2 +-
3 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/libbacktrace/ChangeLog b/libbacktrace/ChangeLog
index 983f81672fb..14df45e7072 100644
--- a/libbacktrace/ChangeLog
+++ b/libbacktrace/ChangeLog
@@ -1,3 +1,8 @@
+2023-01-12 Nick Clifton <nickc@redhat.com>
+
+ * Makefile.am (CLEANFILES): Import patch from upstream to prevent
+ allocafail.sh from being removed when running 'make clean'.
+
2021-11-12 Martin Liska <mliska@suse.cz>
PR libbacktrace/103167
diff --git a/libbacktrace/Makefile.am b/libbacktrace/Makefile.am
index bf9d30a382c..e4f34b5fbd7 100644
--- a/libbacktrace/Makefile.am
+++ b/libbacktrace/Makefile.am
@@ -539,7 +539,7 @@ check_PROGRAMS += $(BUILDTESTS)
TESTS += $(BUILDTESTS)
CLEANFILES = \
- $(TESTS) *.debug elf_for_test.c edtest2_build.c gen_edtest2_build \
+ $(filter-out allocfail.sh,$(TESTS)) *.debug elf_for_test.c edtest2_build.c gen_edtest2_build \
*.dsyms *.fsyms *.keepsyms *.dbg *.mdbg *.mdbg.xz *.strip
clean-local:
diff --git a/libbacktrace/Makefile.in b/libbacktrace/Makefile.in
index 5167ca80ad1..0a61880ba67 100644
--- a/libbacktrace/Makefile.in
+++ b/libbacktrace/Makefile.in
@@ -1130,7 +1130,7 @@ libbacktrace_TEST_CFLAGS = $(EXTRA_FLAGS) $(WARN_FLAGS) -g
@HAVE_ELF_TRUE@xztest_alloc_LDADD = libbacktrace_alloc.la \
@HAVE_ELF_TRUE@ $(am__append_28) $(CLOCK_GETTIME_LINK)
CLEANFILES = \
- $(TESTS) *.debug elf_for_test.c edtest2_build.c gen_edtest2_build \
+ $(filter-out allocfail.sh,$(TESTS)) *.debug elf_for_test.c edtest2_build.c gen_edtest2_build \
*.dsyms *.fsyms *.keepsyms *.dbg *.mdbg *.mdbg.xz *.strip
reply other threads:[~2023-02-02 4:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230202045459.E77CF3858401@sourceware.org \
--to=brobecke@sourceware.org \
--cc=bfd-cvs@sourceware.org \
--cc=gdb-cvs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).