Hi Neal,
thank you for sharing your thoughts.
The dependencies listed in the kernel.spec are resolved, so this is not the cause of the problem.
Here is how to reproduce:
1. build a centos-stream-9 host as a VM 1. the VM is running on a Fedora host, I think this should not matter 2. in order to shorten the turnaround time, the VM has some substantial resources: 12 cores 32 GB of RAM. This may be important. 2. prepare for development tasks, as described in Building an AutoSD image that includes a custom kernel https://sigs.centos.org/automotive/building/building_an_os_image_that%20uses_a_custom_kernel/ : $ sudo dnf update $ sudo dnf groupinstall "Development Tools" $ sudo dnf install ncurses-devel bison flex elfutils-libelf-devel openssl-devel dwarves 3. Clone the centos-stream-9 kernel sources: $ git clone https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9.git 4. Install the build deps (again as described for the AutoSD image build): $ cd centos-stream-9 $ make -j$(nproc) dist-srpm $ sudo dnf config-manager --set-enabled crb $ sudo dnf builddep redhat/rpm/SPECS/kernel.spec 5. Build the kernel packages: $ make -j$(nproc) DISTLOCALVERSION=_at BUILDOPTS="-selftests +verbose" dist-all-rpms 2>&1 | tee -a output01
The failing rsync command is rsync -aq /home/she/Workspace/centos-stream-9/redhat/rpm/BUILD/kernel-5.14.0-570_at.el9/linux-5.14.0-570_at.el9.x86_64/tools/testing/selftests/bpf/urandom_read /home/she/Workspace/centos-stream-9/redhat/rpm/BUILD/kernel-5.14.0-570_at.el9/linux-5.14.0-570_at.el9.x86_64/tools/testing/selftests/bpf/bpf_testmod.ko /home/she/Workspace/centos-stream-9/redhat/rpm/BUILD/kernel-5.14.0-570_at.el9/linux-5.14.0-570_at.el9.x86_64/tools/testing/selftests/bpf/bpf_test_no_cfi.ko /home/she/Workspace/centos-stream-9/redhat/rpm/BUILD/kernel-5.14.0-570_at.el9/linux-5.14.0-570_at.el9.x86_64/tools/testing/selftests/bpf/bpf_test_modorder_x.ko /home/she/Workspace/centos-stream-9/redhat/rpm/BUILD/kernel-5.14.0-570_at.el9/linux-5.14.0-570_at.el9.x86_64/tools/testing/selftests/bpf/bpf_test_modorder_y.ko /home/she/Workspace/centos-stream-9/redhat/rpm/BUILD/kernel-5.14.0-570_at.el9/linux-5.14.0-570_at.el9.x86_64/tools/testing/selftests/bpf/liburandom_read.so /home/she/Workspace/centos-stream-9/redhat/rpm/BUILD/kernel-5.14.0-570_at.el9/linux-5.14.0-570_at.el9.x86_64/tools/testing/selftests/bpf/xdp_synproxy /home/she/Workspace/centos-stream-9/redhat/rpm/BUILD/kernel-5.14.0-570_at.el9/linux-5.14.0-570_at.el9.x86_64/tools/testing/selftests/bpf/sign-file /home/she/Workspace/centos-stream-9/redhat/rpm/BUILD/kernel-5.14.0-570_at.el9/linux-5.14.0-570_at.el9.x86_64/tools/testing/selftests/bpf/uprobe_multi ima_setup.sh verify_sig_setup.sh progs/btf_dump_test_case_bitfields.c progs/btf_dump_test_case_multidim.c progs/btf_dump_test_case_namespacing.c progs/btf_dump_test_case_ordering.c progs/btf_dump_test_case_packing.c progs/btf_dump_test_case_padding.c progs/btf_dump_test_case_syntax.c /home/she/Workspace/centos-stream-9/redhat/rpm/BUILD/kernel-5.14.0-570_at.el9/linux-5.14.0-570_at.el9.x86_64/tools/testing/selftests/bpf/no_alu32/
This should explain the file not found error. And obviously the actual length of the argument list is way below our limits. So the error messages are misleading. The problem must be somewhere else.
To make things a bit more confusing: After quite some experimenting, including completely new installations of the build host, I occasionally get a successful build. But this appears to happen at random. Sequences of "make dist-clean; make dist-all-rpms" sometimes succeed and sometimes fail. There are no dmesg warnings or other indications of a problem with the running VM.
Is it possible, that the -j$(nproc) causes the problem? I do see "-j12 forced in submake: resetting jobserver mode." warnings from make.
Beste Grüße Sebastian Hetze