All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>,
	Randy Dunlap <rdunlap@infradead.org>, Shuah <shuah@kernel.org>,
	"open list:KERNEL SELFTEST FRAMEWORK"
	<linux-kselftest@vger.kernel.org>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: Problems when trying to build tools/testing/selftests
Date: Wed, 3 Dec 2025 14:51:01 -0700	[thread overview]
Message-ID: <12c91daf-0d8f-4b97-a8ee-952dc305d6cb@linuxfoundation.org> (raw)
In-Reply-To: <4f96cd7f-57d1-436a-8772-28cf1efe8154@roeck-us.net>

On 12/3/25 14:01, Guenter Roeck wrote:
> On 12/3/25 09:55, Randy Dunlap wrote:
>>
>>
>> On 12/3/25 9:25 AM, Shuah wrote:
>>> 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 usually indicates missing libraries or header path
issues.

>>>>
>>>> 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?
>>
>> Guenter, did you follow Documentation/dev-tools/kselftest.rst?
>>
> 
> The document says
> 
> To build the tests::
> 
>    $ make headers
>    $ make -C tools/testing/selftests
> 
> which is what I did.
> 
> I did run
> 
> kselftest_deps.sh gcc
> 
> which tells me
> 
> FAIL: net/tcp_ao/Makefile dependency check: $(LIB)
> FAIL: bpf/Makefile dependency check: $(LIBELF_LIBS)
> FAIL: bpf/Makefile dependency check: $(PCAP_LIBS)
> FAIL: net/netfilter/Makefile dependency check: $(MNL_LDLIBS)
> FAIL: net/netfilter/Makefile dependency check: $(MNL_LDLIBS)
> --------------------------------------------------------
> Targets failed build dependency check on system:
> bpf net
> --------------------------------------------------------
> Missing libraries system
> $(LIB) $(LIBELF_LIBS) $(MNL_LDLIBS) $(PCAP_LIBS)
> 
> which doeesn't really help. For example, PCAP_LIBS seems to refer to libpcap,
> and I have libpcap-dev installed on my system.
> 
> Unless I am missing something that doesn't explain the build failures.
> 

I ran "make kselftest-all" - mount-notify/mount-notify_test.c built
fine on Linux 6.18 - which repo are you trying on?

Can you try "make kselftest-all" and tell me what happens?

I also tried

make -C tools/testing/selftests

and

make -C tools/testing/selftests TARGETS="filesystems/mount-notify"

Which repo are you trying on?

thanks,
-- Shuah




  reply	other threads:[~2025-12-03 21:51 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
2025-12-03 17:55   ` Randy Dunlap
2025-12-03 21:01     ` Guenter Roeck
2025-12-03 21:51       ` Shuah Khan [this message]
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=12c91daf-0d8f-4b97-a8ee-952dc305d6cb@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=rdunlap@infradead.org \
    --cc=shuah@kernel.org \
    /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.