linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miko Larsson via B4 Relay <devnull+mikoxyzzz.gmail.com@kernel.org>
To: linux-trace-devel@vger.kernel.org
Cc: Miko Larsson <mikoxyzzz@gmail.com>
Subject: [PATCH v2 1/3] utest/tracefs-utest: include linux/limits.h
Date: Thu, 22 Feb 2024 11:12:44 +0100	[thread overview]
Message-ID: <20240222-utest-fixes-v2-1-ba9cd06b41d3@gmail.com> (raw)
In-Reply-To: <20240222-utest-fixes-v2-0-ba9cd06b41d3@gmail.com>

From: Miko Larsson <mikoxyzzz@gmail.com>

This fixes the build with musl + clang >=15; musl doesn't define
PATH_MAX anywhere else, and clang >=15 doesn't allow implicit
declarations with >=c99. Without this, the build fails due to PATH_MAX
not being defined.

We could include limits.h from the libc, but AFAIK the libc doesn't
necessarily have to define PATH_MAX, so it's safer to just include
linux/limits.h

Fixes: 845f16976929 ("libtracefs: Add unit tests")
Signed-off-by: Miko Larsson <mikoxyzzz@gmail.com>
---
 utest/tracefs-utest.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/utest/tracefs-utest.c b/utest/tracefs-utest.c
index 963fac7..70bcf3e 100644
--- a/utest/tracefs-utest.c
+++ b/utest/tracefs-utest.c
@@ -16,6 +16,8 @@
 #include <kbuffer.h>
 #include <pthread.h>
 
+#include <linux/limits.h>
+
 #include <sys/mount.h>
 #include <sys/syscall.h>
 

-- 
2.43.0


  reply	other threads:[~2024-02-22 10:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22 10:12 [PATCH v2 0/3] utest: fix build with musl + clang >=15 Miko Larsson via B4 Relay
2024-02-22 10:12 ` Miko Larsson via B4 Relay [this message]
2024-02-22 14:53   ` [PATCH v2 1/3] utest/tracefs-utest: include linux/limits.h Steven Rostedt
2024-02-22 16:04     ` Steven Rostedt
2024-02-22 17:24       ` Miko Larsson
2024-02-22 10:12 ` [PATCH v2 2/3] utest/tracefs-utest: define _LARGEFILE64_SOURCE Miko Larsson via B4 Relay
2024-02-22 10:12 ` [PATCH v2 3/3] utest/trace-utest: include libgen.h Miko Larsson via B4 Relay

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=20240222-utest-fixes-v2-1-ba9cd06b41d3@gmail.com \
    --to=devnull+mikoxyzzz.gmail.com@kernel.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=mikoxyzzz@gmail.com \
    /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).