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 0/3] utest: fix build with musl + clang >=15
Date: Thu, 22 Feb 2024 11:12:43 +0100 [thread overview]
Message-ID: <20240222-utest-fixes-v2-0-ba9cd06b41d3@gmail.com> (raw)
Clang 15 onwards defaults to -Werror=implicit-function-declaration
which, combined with musl not declaring all the stuff we need without
the missing includes and defines, breaks the utest build. This series
fixes thus by simply adding the missing stuff.
Signed-off-by: Miko Larsson <mikoxyzzz@gmail.com>
---
Changes in v2:
- Better commit descriptions, messages
- Link to v1: https://lore.kernel.org/r/20240215-utest-fixes-v1-0-24678d859de2@gmail.com
---
Miko Larsson (3):
utest/tracefs-utest: include linux/limits.h
utest/tracefs-utest: define _LARGEFILE64_SOURCE
utest/trace-utest: include libgen.h
utest/trace-utest.c | 1 +
utest/tracefs-utest.c | 4 ++++
2 files changed, 5 insertions(+)
---
base-commit: 5f27b7f3fb7d88b29522baf3883cc0e2e28b1af0
change-id: 20240215-utest-fixes-893315be225b
Best regards,
--
Miko Larsson <mikoxyzzz@gmail.com>
next 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 Miko Larsson via B4 Relay [this message]
2024-02-22 10:12 ` [PATCH v2 1/3] utest/tracefs-utest: include linux/limits.h Miko Larsson via B4 Relay
2024-02-22 14:53 ` 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-0-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 read-only IMAP folder(s) and NNTP newsgroup(s).