From: Shuah <shuah@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>
Cc: Shuah Khan <shuah@kernel.org>
Subject: Re: Problems when trying to build tools/testing/selftests
Date: Wed, 3 Dec 2025 10:25:29 -0700 [thread overview]
Message-ID: <bb2426dd-3c29-4c94-ac77-aaa0b422b2e7@kernel.org> (raw)
In-Reply-To: <44e08e2f-7f22-4106-b581-56150cafb048@roeck-us.net>
On 12/2/25 22:20, Guenter Roeck wrote:
> Hi,
>
> when trying to build tools/testing/selftests, I get a lot of warnings such as
>
> mount-notify_test.c: In function ‘fanotify_fsmount’:
> mount-notify_test.c:360:14: warning: implicit declaration of function ‘fsopen’; did you mean ‘fdopen’?
>
> and subsequent build errors.
>
> testing/selftests/filesystems/mount-notify/mount-notify_test.c:360: undefined reference to `fsopen'
> /usr/bin/ld: tools/testing/selftests/filesystems/mount-notify/mount-notify_test.c:363: undefined reference to `fsconfig'
> /usr/bin/ld:tools/testing/selftests/filesystems/mount-notify/mount-notify_test.c:366: undefined reference to `fsmount'
> /usr/bin/ld: tools/testing/selftests/filesystems/mount-notify/mount-notify_test.c:371: undefined reference to `move_mount'
>
> This does not just affect a single file, but several of them.
>
> What am I missing ? Is there some magic needed to build the selftests ?
Not sure. It built fine for me on Linux 6.18 latest. Are you missing
a library possibly?
thanks,
-- Shuah
next prev parent reply other threads:[~2025-12-03 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 5:20 Problems when trying to build tools/testing/selftests Guenter Roeck
2025-12-03 17:25 ` Shuah [this message]
2025-12-03 17:55 ` Randy Dunlap
2025-12-03 21:01 ` Guenter Roeck
2025-12-03 21:51 ` Shuah Khan
2025-12-03 22:01 ` Guenter Roeck
2025-12-03 22:25 ` Shuah Khan
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=bb2426dd-3c29-4c94-ac77-aaa0b422b2e7@kernel.org \
--to=shuah@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@roeck-us.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.