From: Steven Rostedt <rostedt@goodmis.org>
To: Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Subject: [PATCH] libtracefs: Force creation of lib/tracefs directory
Date: Wed, 9 Dec 2020 18:09:38 -0500 [thread overview]
Message-ID: <20201209180938.1d69f169@gandalf.local.home> (raw)
From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
If the $(obj)/lib/tracefs directory does not exist, create it before
building the libraries. Otherwise the build will fail due to the directory
not existing.
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
---
Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Makefile b/Makefile
index 5d11abc..02b3d25 100644
--- a/Makefile
+++ b/Makefile
@@ -277,9 +277,11 @@ $(bdir):
LIBS = -L$(obj)/lib/traceevent -ltraceevent
$(LIBTRACEFS_STATIC): force
+ $(Q)mkdir -p $(bdir)
$(Q)$(MAKE) -C $(src)/src $@
$(bdir)/libtracefs.so.$(TRACEFS_VERSION): force
+ $(Q)mkdir -p $(bdir)
$(Q)$(MAKE) -C $(src)/src $@
clean:
--
2.25.4
reply other threads:[~2020-12-09 23:10 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=20201209180938.1d69f169@gandalf.local.home \
--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).