From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH] kernel-shark: Fix search path for libtracefs
Date: Wed, 5 Feb 2020 09:07:43 +0200 [thread overview]
Message-ID: <20200205070743.13836-1-tz.stoyanov@gmail.com> (raw)
Cmake uses wrong relative path while searching for
development version of libtracefs: lib/trace-cmd,
but the tracefs library is located at lib/tracefs
Signed-off-by: Tzvetomir Stoyanov (VMware) <tz.stoyanov@gmail.com>
---
kernel-shark/build/FindTraceCmd.cmake | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel-shark/build/FindTraceCmd.cmake b/kernel-shark/build/FindTraceCmd.cmake
index f27fafe..c29b779 100644
--- a/kernel-shark/build/FindTraceCmd.cmake
+++ b/kernel-shark/build/FindTraceCmd.cmake
@@ -43,7 +43,7 @@ find_library(TRACECMD_LIBRARY NAMES trace-cmd/libtracecmd.a
${CMAKE_SOURCE_DIR}/../lib/
NO_DEFAULT_PATH)
-find_library(TRACEFS_LIBRARY NAMES trace-cmd/libtracefs.a
+find_library(TRACEFS_LIBRARY NAMES tracefs/libtracefs.a
PATHS $ENV{TRACE_CMD}/lib/
${CMAKE_SOURCE_DIR}/../lib/
NO_DEFAULT_PATH)
--
2.24.1
next reply other threads:[~2020-02-05 7:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 7:07 Tzvetomir Stoyanov (VMware) [this message]
2020-02-17 8:50 ` [PATCH] kernel-shark: Fix search path for libtracefs Yordan Karadzhov (VMware)
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=20200205070743.13836-1-tz.stoyanov@gmail.com \
--to=tz.stoyanov@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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).