From: Eduard Zingerman <eddyz87@gmail.com>
To: Mykola Lysenko <nickolay.lysenko@gmail.com>, bpf@vger.kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, memxor@gmail.com
Subject: Re: [PATCH bpf-next v7 9/9] selftests/bpf: build each test runner instance in its own sub-make
Date: Tue, 25 Aug 2026 21:58:09 -0700 [thread overview]
Message-ID: <5eda92178e2176a0a8bf85768fd724a6df26699a.camel@gmail.com> (raw)
In-Reply-To: <20cda214c123d41183bb1e5f95af8c1d9dd6621e.camel@gmail.com>
On Tue, 2026-08-25 at 16:55 -0700, Eduard Zingerman wrote:
...
> I tested this patch-set for:
> - clean build within selftests directory, ok
> - minimal rebuild after progs/*.c is touched, ok
> - minimal rebuild after prog_tests/*.c is touched, ok
> - test_progs, test_verifier, test_progs-cpuv4, test_maps
> all work
> - build with O= specified, something goes sideways:
> the build completes but the tests can't be executed.
>
> For example:
>
> $ make -j O=~/work/tmp/tests-build
>
> In the vm:
>
> # cd /home/eddy/work/tmp/test-build
> # ./test_verifier
> Failed to load bpf_testmod.ko into the kernel: -8
>
> # ./test_progs -a verifier_and
> ./test_progs: error while loading shared libraries: libLLVM.so.18.1: cannot open shared object file: No such file or directory
>
> Note the following oddity:
>
> [root@testhost bpf]# ldd ./test_progs
> linux-vdso.so.1 (0x00007f8bf85d5000)
> libelf.so.1 => /lib64/libelf.so.1 (0x00007f8bf01cd000)
> libz.so.1 => /lib64/libz.so.1 (0x00007f8bf01aa000)
> libm.so.6 => /lib64/libm.so.6 (0x00007f8bf00bc000)
> libzstd.so.1 => /lib64/libzstd.so.1 (0x00007f8befff8000)
> libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f8befc00000)
> libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f8beffca000)
> libc.so.6 => /lib64/libc.so.6 (0x00007f8befa0e000)
> /lib64/ld-linux-x86-64.so.2 (0x00007f8bf85d7000)
> [root@testhost bpf]# cd -
> /home/eddy/work/tmp/test-build
> [root@testhost test-build]# ldd ./test_progs
> linux-vdso.so.1 (0x00007fd8fe342000)
> libelf.so.1 => /lib64/libelf.so.1 (0x00007fd8fe319000)
> libz.so.1 => /lib64/libz.so.1 (0x00007fd8fe2f6000)
> libpcap.so.1 => /lib64/libpcap.so.1 (0x00007fd8fe2a9000)
> libLLVM.so.18.1 => not found
> libc.so.6 => /lib64/libc.so.6 (0x00007fd8fe0b7000)
> libzstd.so.1 => /lib64/libzstd.so.1 (0x00007fd8fdff1000)
> libibverbs.so.1 => /lib64/libibverbs.so.1 (0x00007fd8fdfd1000)
> /lib64/ld-linux-x86-64.so.2 (0x00007fd8fe344000)
> libnl-route-3.so.200 => /lib64/libnl-route-3.so.200 (0x00007fd8fdf3c000)
> libnl-3.so.200 => /lib64/libnl-3.so.200 (0x00007fd8fdf1a000)
> libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fd8fdeee000)
Redid the testing with O= and the above issue is gone.
Probably an error somewhere between the chain and keyboard.
Sorry for the noise, O= works as expected.
prev parent reply other threads:[~2026-08-26 4:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 19:42 [PATCH bpf-next v7 0/9] selftests/bpf: restructure the Makefile as a layered build Mykola Lysenko
2026-08-23 19:42 ` [PATCH bpf-next v7 1/9] selftests/bpf: keep headers off the generic link command line Mykola Lysenko
2026-08-23 19:42 ` [PATCH bpf-next v7 2/9] selftests/bpf: drop stale lines, restore two header dependencies Mykola Lysenko
2026-08-23 20:41 ` bot+bpf-ci
2026-08-24 22:47 ` Eduard Zingerman
2026-08-23 19:42 ` [PATCH bpf-next v7 3/9] selftests/bpf: factor the permissive-mode skip suffix into a helper Mykola Lysenko
2026-08-23 19:51 ` sashiko-bot
2026-08-23 19:42 ` [PATCH bpf-next v7 4/9] selftests/bpf: generate the signing key and certificate once Mykola Lysenko
2026-08-23 19:42 ` [PATCH bpf-next v7 5/9] selftests/bpf: generate verifier/tests.h in a regular recipe Mykola Lysenko
2026-08-23 19:42 ` [PATCH bpf-next v7 6/9] selftests/bpf: derive the bench object list from the sources Mykola Lysenko
2026-08-24 23:42 ` Eduard Zingerman
2026-08-23 19:42 ` [PATCH bpf-next v7 7/9] selftests/bpf: extract BPF skeleton generation into a helper script Mykola Lysenko
2026-08-23 19:42 ` [PATCH bpf-next v7 8/9] selftests/bpf: move shared build definitions into Makefile.buildvars Mykola Lysenko
2026-08-23 20:53 ` bot+bpf-ci
2026-08-25 6:45 ` Eduard Zingerman
2026-08-23 19:42 ` [PATCH bpf-next v7 9/9] selftests/bpf: build each test runner instance in its own sub-make Mykola Lysenko
2026-08-23 21:05 ` bot+bpf-ci
2026-08-25 23:55 ` Eduard Zingerman
2026-08-26 4:58 ` Eduard Zingerman [this message]
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=5eda92178e2176a0a8bf85768fd724a6df26699a.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jolsa@kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=nickolay.lysenko@gmail.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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.