From: Li Zhijian <lizhijian@fujitsu.com>
To: nvdimm@lists.linux.dev
Cc: Li Zhijian <lizhijian@fujitsu.com>
Subject: [ndctl PATCH] meson.build: add libtracefs version >=1.2.0 dependency
Date: Fri, 12 May 2023 16:10:26 +0800 [thread overview]
Message-ID: <20230512081026.735459-1-lizhijian@fujitsu.com> (raw)
Compile with libtracefs < 1.2.0(1.0.2 in Fedora33) will get errors:
/usr/bin/ld: cxl/cxl.p/event_trace.c.o: in function `cxl_event_tracing_enable':
/path/to/ndctl/build/../cxl/event_trace.c:238: undefined reference to `tracefs_event_enable'
/usr/bin/ld: /path/to/ndctl/build/../cxl/event_trace.c:242: undefined reference to `tracefs_trace_is_on'
/usr/bin/ld: /path/to/ndctl/build/../cxl/event_trace.c:245: undefined reference to `tracefs_trace_on'
/usr/bin/ld: cxl/cxl.p/event_trace.c.o: in function `cxl_event_tracing_disable':
/path/to/ndctl/build/../cxl/event_trace.c:251: undefined reference to `tracefs_trace_off'
/usr/bin/ld: cxl/cxl.p/monitor.c.o: in function `monitor_event':
/path/to/ndctl/build/../cxl/monitor.c:74: undefined reference to `tracefs_instance_file_open'
Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
---
meson.build | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meson.build b/meson.build
index 50e83cf770a2..50cb4800ab9b 100644
--- a/meson.build
+++ b/meson.build
@@ -145,7 +145,7 @@ uuid = dependency('uuid')
json = dependency('json-c')
if get_option('libtracefs').enabled()
traceevent = dependency('libtraceevent')
- tracefs = dependency('libtracefs')
+ tracefs = dependency('libtracefs', version : '>=1.2.0')
endif
if get_option('docs').enabled()
--
2.29.2
reply other threads:[~2023-05-12 8:12 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=20230512081026.735459-1-lizhijian@fujitsu.com \
--to=lizhijian@fujitsu.com \
--cc=nvdimm@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.