From: Steven Rostedt <rostedt@goodmis.org>
To: Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Subject: [PATCH] libtracefs: Define gettid() when not defined
Date: Wed, 25 Aug 2021 19:45:43 -0400 [thread overview]
Message-ID: <20210825194543.34de6c3f@rorschach.local.home> (raw)
From: Steven Rostedt <rostedt@rorschach.local.home>
tracefs-hist.c uses the gettid() system call, but older glibcs do not
define it. Define the system call when it is not already defined.
Signed-off-by: Steven Rostedt <rostedt@rorschach.local.home>
---
src/tracefs-hist.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/src/tracefs-hist.c b/src/tracefs-hist.c
index 003715f..c0d3049 100644
--- a/src/tracefs-hist.c
+++ b/src/tracefs-hist.c
@@ -24,6 +24,11 @@
#define ASCENDING ".ascending"
#define DESCENDING ".descending"
+#ifndef gettid
+# include <sys/syscall.h>
+# define gettid() syscall(__NR_gettid)
+#endif
+
struct tracefs_hist {
struct tep_handle *tep;
struct tep_event *event;
--
2.30.2
reply other threads:[~2021-08-25 23:45 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=20210825194543.34de6c3f@rorschach.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).