mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Mark Brown <broonie@kernel.org>
Cc: Willy Tarreau <w@1wt.eu>, Shuah Khan <shuah@kernel.org>,
	 linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 1/9] tools/nolibc: move ioctl() to sys/ioctl.h
Date: Wed, 21 May 2025 15:08:05 +0200	[thread overview]
Message-ID: <89bb5a3e-dd6c-475d-9c5d-0bd1595be735@t-8ch.de> (raw)
In-Reply-To: <eda3af4a-8dfe-4f82-a934-2d0256b754e2@sirena.org.uk>

On 2025-05-21 14:03:37+0100, Mark Brown wrote:
> On Thu, May 15, 2025 at 09:57:47PM +0200, Thomas Weißschuh wrote:
> > This is the location regular userspace expects this definition.
> > 
> > Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> 
> This is in -next as b8c436bbef0f2a and breaks the build of all the arm64
> selftests using nolibc: 
> 
> clang --target=aarch64-linux-gnu -fintegrated-as -fno-asynchronous-unwind-tables -fno-ident -s -Os -nostdlib \
> 	-static -include ../../../../include/nolibc/nolibc.h \
> 	-ffreestanding -Wall tpidr2.c -o /home/broonie/git/bisect/tools/testing/selftests/arm64/abi/tpidr2 -lgcc
> In file included from <built-in>:1:
> In file included from ./../../../../include/nolibc/nolibc.h:100:
> ./../../../../include/nolibc/sys/ioctl.h:8:10: fatal error: 'nolibc.h' file not found
>     8 | #include "nolibc.h"
>       |          ^~~~~~~~~~
> 1 error generated.
> 
> This happens because:
> 
> > +++ b/tools/include/nolibc/sys/ioctl.h
> > @@ -0,0 +1,29 @@
> > +/* SPDX-License-Identifier: LGPL-2.1 OR MIT */
> > +/*
> > + * Ioctl definitions for NOLIBC
> > + * Copyright (C) 2017-2021 Willy Tarreau <w@1wt.eu>
> > + */
> > +
> > +/* make sure to include all global symbols */
> > +#include "nolibc.h"
> 
> assumes that the nolibc include directory is in the include path, or
> otherwise set up with a -I path, previously you just had to include
> nolibc.h with the includes that are there working due to being relative
> to nolibc.h.  I'll send a patch for the arm64 tests.

Thanks for the report.
Inside sys/ this should actually be #include "../nolibc.h".
I'll doublecheck all of sys/ and see why our new header checks didn't
catch this.

> It looks like the RISC-V selftests are also impacted, I didn't spot any
> other users that didn't already have an -I.

No changes to the selftests should be necessary.

  reply	other threads:[~2025-05-21 13:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-15 19:57 [PATCH 0/9] tools/nolibc: split out more headers Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 1/9] tools/nolibc: move ioctl() to sys/ioctl.h Thomas Weißschuh
2025-05-21 13:03   ` Mark Brown
2025-05-21 13:08     ` Thomas Weißschuh [this message]
2025-05-21 13:22       ` Mark Brown
2025-05-21 13:45         ` Thomas Weißschuh
2025-05-21 13:58           ` Mark Brown
2025-05-21 18:49           ` Mark Brown
2025-05-23  8:33             ` Thomas Weißschuh
2025-05-23 10:14               ` Mark Brown
2025-05-15 19:57 ` [PATCH 2/9] tools/nolibc: move mount() to sys/mount.h Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 3/9] tools/nolibc: move prctl() to sys/prctl.h Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 4/9] tools/nolibc: move reboot() to sys/reboot.h Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 5/9] tools/nolibc: move getrlimit() and friends to sys/resource.h Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 6/9] tools/nolibc: move makedev() and friends to sys/sysmacros.h Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 7/9] tools/nolibc: move uname() and friends to sys/utsname.h Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 8/9] tools/nolibc: move NULL and offsetof() to sys/stddef.h Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 9/9] selftests/nolibc: drop include guards around standard headers Thomas Weißschuh
2025-05-16  3:50 ` [PATCH 0/9] tools/nolibc: split out more headers Willy Tarreau

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=89bb5a3e-dd6c-475d-9c5d-0bd1595be735@t-8ch.de \
    --to=linux@weissschuh.net \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --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

all inboxes | Powered by JetHome®