On 3/8/25 6:34 AM, Costa Shulyupin wrote: > On Wed, 5 Mar 2025 at 00:11, Donald Zickus <dzickus@xxxxxxxxxx> wrote: >> >> Hi, >> >> If anyone wants to chew on a kernel build problem on the centos mailing list. There are multiple replies to the thread with no success. >> >> Cheers, >> Don >> >> ---------- Forwarded message --------- >> From: Sebastian Hetze <shetze@xxxxxxxxxx> >> Date: Sat, Mar 1, 2025 at 6:50 AM >> Subject: [CentOS-devel] make dist-all-rpms fails with test_progs-no_alu32-extras Error >> To: <devel@xxxxxxxxxxxxxxxx> >> >> >> Hi * >> >> I recently tried to compile a custom centos-stream-9 automotive SIG kernel and failed. >> >> Now I see the very same problem is present in the mainline centos-stream-9 kernel. >> >> When I clone the sources from https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9 on a freshly installed centos-stream-9 host, the make dist-all-rpms target fails with >> >> make[3]: rsync: Argument list too long >> make[3]: *** [Makefile:768: test_progs-no_alu32-extras] Error 127 >> >> >> This is certainly not a problem with rsync and the ulimits are definitely sufficient to deal with this ~2000 char argument list. >> >> So what is going on here? >> This rsync call appears to come from the tools/testing/selftests/bpf/Makefile. >> The problem persists if I BUILDOPTS="-selftests" and I understand bpf to be a SKIP_TARGET by default, anyway. >> >> >> Does anyone have a hint? What is missing or what am I missing? > > I’ve bisected the issue and identified that it was introduced by commit > selftests/bpf: Use auto-dependencies for test objects > > https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/commit/a7ff7bd4cdad76f4f1c37ee7c918e201dbb7ce6e > Hi everyone. I tried to reproduce the error using a centos9-stream docker image [1] (I know it might be not exactly right), following steps from the original thread [2]. This command: make -j$(nproc) DISTLOCALVERSION=_at BUILDOPTS="-selftests" dist-all-rpms completed successfully on tag kernel-5.14.0-571.el9 [3]. Shortly after auto-dependencies change was merged, a few problems with out-of-tree builds were discovered and fixed. The symptom was also an rsync command failure. See relevant thread on bpf mailing list [4]. I noticed that the fixes are not merged into centos9-stream tree. I think it's worth trying to test the build with the fixes applied [5]. It's just a guess though, as I wasn't able to reproduce the failure. [1] https://hub.docker.com/r/dokken/centos-stream-9 [2] https://lists.centos.org/hyperkitty/list/devel@xxxxxxxxxxxxxxxx/thread/N4JBZWVP2OTQXWQ52E73SBRHE6GA6XPB/ [3] https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/commit/15b5887ebd883f74aaa63ab124bc0f75770eb6b1 [4] https://lore.kernel.org/bpf/877cbfwqre.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx [5] https://lore.kernel.org/bpf/20240916195919.1872371-1-ihor.solodrai@xxxxx/
