linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-trace-devel@vger.kernel.org
Subject: [PATCH 5/5] libtracefs: Keep build_install file around
Date: Tue, 15 Dec 2020 23:38:57 -0500	[thread overview]
Message-ID: <20201216043922.025513420@goodmis.org> (raw)
In-Reply-To: 20201216043852.168982058@goodmis.org

From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>

Instead of rebuilding the build_install files every time the uninstall is
created, make it depend on the prefix, as if the prefix is the same, then
the uninstall should be the same.

Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
---
 Makefile | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/Makefile b/Makefile
index 204a4e5e6e1f..a7d58081bf4b 100644
--- a/Makefile
+++ b/Makefile
@@ -276,7 +276,7 @@ define build_uninstall_script
 	$(Q)$(RM) -rf $(BUILD_OUTPUT)/tmp_build
 endef
 
-build_uninstall:
+build_uninstall: $(BUILD_PREFIX)
 	$(call build_uninstall_script,install,uninstall)
 
 $(BUILD_OUTPUT)/build_uninstall: build_uninstall
@@ -289,7 +289,6 @@ endef
 
 uninstall: $(BUILD_OUTPUT)/build_uninstall
 	@$(foreach file,$(shell cat $(BUILD_OUTPUT)/build_uninstall),$(call uninstall_file,$(file)))
-	$(Q)$(RM) $<
 
 PHONY += force
 force:
-- 
2.29.2



      parent reply	other threads:[~2020-12-16  4:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16  4:38 [PATCH 0/5] libtracefs: Makefile fixes, add uninstall and fix dependency of libtracefs.pc Steven Rostedt
2020-12-16  4:38 ` [PATCH 1/5] libtracefs: Have etcdir always be at the root directory Steven Rostedt
2020-12-16  4:38 ` [PATCH 2/5] libtracefs: Remove obsolete do_install_ld call Steven Rostedt
2020-12-16  4:38 ` [PATCH 3/5] libtracefs: Add make uninstall Steven Rostedt
2020-12-16  4:38 ` [PATCH 4/5] libtracefs: Update libtracefs.pc if prefix is different Steven Rostedt
2020-12-16  4:38 ` Steven Rostedt [this message]

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=20201216043922.025513420@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=linux-trace-devel@vger.kernel.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 NNTP newsgroup(s).