public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Nick Clifton <nickc@sourceware.org> To: bfd-cvs@sourceware.org, gdb-cvs@sourceware.org Subject: [binutils-gdb/binutils-2_40-branch] Ensure that libbacktrace/allocfail.sh is not deleted when creating release tarballs. Date: Thu, 12 Jan 2023 13:38:40 +0000 (GMT) [thread overview] Message-ID: <20230112133840.9458E3858C66@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=7145c3f61007f955b1611b55810b5503c92663c3 commit 7145c3f61007f955b1611b55810b5503c92663c3 Author: Nick Clifton <nickc@redhat.com> Date: Thu Jan 12 13:37:59 2023 +0000 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'. 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-01-12 13:38 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=20230112133840.9458E3858C66@sourceware.org \ --to=nickc@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: linkBe 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).