From: David Laight <david.laight.linux@gmail.com>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Willy Tarreau <w@1wt.eu>,
linux-kernel@vger.kernel.org, Cheng Li <lechain@gmail.com>
Subject: Re: [PATCH] selftests/nolibc: Fix build with host headers and libc
Date: Mon, 16 Feb 2026 22:21:18 +0000 [thread overview]
Message-ID: <20260216222118.5bc39904@pumpkin> (raw)
In-Reply-To: <5f38b16b-1abf-4e22-92f1-9dc086c72e55@t-8ch.de>
On Mon, 16 Feb 2026 19:51:24 +0100
Thomas Weißschuh <linux@weissschuh.net> wrote:
> On 2026-02-14 11:57:24+0000, david.laight.linux@gmail.com wrote:
> > From: David Laight <david.laight.linux@gmail.com>
> >
> > Many systems don't have strlcpy() or strlcat().
> > Change is_nolibc to a #define so that the calls are optimised out.
> > Create #define wrappers so the code is syntactially valid.
> >
> > Additionall readdir_r() is likely to be marked deprecated.
>
> "Additionally"
>
> > So disable "-Wdeprecated-declarations".
>
> Could you split this into multiple patches?
>
> > Fixes: 6fe8360b16acb ("selftests/nolibc: also test libc-test through regular selftest framework")
> > Signed-off-by: David Laight <david.laight.linux@gmail.com>
> > ---
> > tools/testing/selftests/nolibc/nolibc-test.c | 13 +++++++++----
> > 1 file changed, 9 insertions(+), 4 deletions(-)
> >
> > diff --git a/tools/testing/selftests/nolibc/nolibc-test.c b/tools/testing/selftests/nolibc/nolibc-test.c
> > index 1b9d3b2e2491..eb2421b42e75 100644
> > --- a/tools/testing/selftests/nolibc/nolibc-test.c
> > +++ b/tools/testing/selftests/nolibc/nolibc-test.c
> > @@ -66,13 +66,18 @@ static const char *argv0;
> > /* will be used by constructor tests */
> > static int constructor_test_value;
> >
> > -static const int is_nolibc =
> > #ifdef NOLIBC
> > - 1
> > +#define is_nolibc 1
> > #else
> > - 0
> > +#define is_nolibc 0
> > +/* strlcat() and strlcpy() may not be in the system headers. */
> > +#undef strlcat
> > +#undef strlcpy
> > +#define strlcat(d, s, l) 0
> > +#define strlcpy(d, s, l) 0
> > +/* readdir_r() is likely to be marked deprecated */
> > +#pragma GCC diagnostic ignored "-Wdeprecated-declarations"
> > #endif
>
> I'd prefer to disable this via $(cc-option) in the Makefile.
> Unknown pragmas tend to introduce more warnings.
There is already a similar pragma in the file and this one isn't a new one warning.
The other option is to disable the test for !is_nolibc and #define readir_r() away.
That may not need is_nolibc changing to be a #define.
David
>
> > -;
> >
> > /* definition of a series of tests */
> > struct test {
> > --
> > 2.39.5
> >
next prev parent reply other threads:[~2026-02-16 22:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 11:57 [PATCH] selftests/nolibc: Fix build with host headers and libc david.laight.linux
2026-02-16 18:51 ` Thomas Weißschuh
2026-02-16 22:21 ` David Laight [this message]
2026-02-18 17:23 ` Thomas Weißschuh
2026-02-18 22:51 ` David Laight
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=20260216222118.5bc39904@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=lechain@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=w@1wt.eu \
/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