automotive-sig August 2025

automotive-sig@lists.centos.org

3 participants
3 discussions

Custom kernel build fails: rsync: Argument list too long
by Sebastian Hetze 02 Mar '26

02 Mar '26

Hi *, when trying to build the centos-stream-9 main-automotive kernel for the x86_64 architecture as described in the automotive sig documentation <https://sigs.centos.org/automotive/building/building_an_os_image_that%20use…>, it fails. The failing command appears to be /usr/bin/make -s 'HOSTCFLAGS=-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64-v2 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection' 'HOSTLDFLAGS=-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 ' -j12 ARCH=x86_64 V=1 'TARGETS=bpf cgroup mm livepatch net net/forwarding net/mptcp netfilter tc-testing memfd drivers/net/bonding iommu cachestat drivers/net' SKIP_TARGETS= FORCE_TARGETS=1 INSTALL_PATH=/home/she/rpmbuild/BUILDROOT/kernel-automotive-5.14.0-570.518_at.el9iv.x86_64/usr/libexec/kselftests VMLINUX_H= DEFAULT_INSTALL_HDR_PATH=0 install with the error make[3]: Entering directory '/home/she/Workspace/centos-stream-9/redhat/rpm/BUILD/kernel-5.14.0-570.518_at.el9iv/linux-5.14.0-570.518_at.el9iv.x86_64/tools/testing/selftests/bpf' Auto-detecting system features: ... llvm: [ OFF ] make[3]: rsync: Argument list too long make[3]: *** [Makefile:768: test_progs-no_alu32-extras] Error 127 make[3]: Leaving directory '/home/she/Workspace/centos-stream-9/redhat/rpm/BUILD/kernel-5.14.0-570.518_at.el9iv/linux-5.14.0-570.518_at.el9iv.x86_64/tools/testing/selftests/bpf' make[2]: *** [Makefile:233: install] Error 2 This is the unmodified main-automotive branch of the current centos-stream-9 kernel on a current centos-stream-9 system. Setting ulimit -S -s unlimited for ARG_MAX 6291456 does not make any difference. It looks like the actual problem is not with the rsync command line. Any hint what is going wrong and how to proceed? Beste Grüße Sebastian Hetze -- Principal Software Engineer Red Hat GmbH. Niederlassung Berlin Leipziger Platz 16, 10117 Berlin Mobil: +49 173 8914205 E-Mail: she(a)redhat.com Registered seat: Werner von Siemens Ring 14, D-85630 Grasbrunn, Germany Commercial register: Amtsgericht Muenchen/Munich, HRB 153243,Managing Directors: Ryan Barnhart, Charles Cachera, Michael O'Neill, Amy Ross

3 2

Re: Request to create a repository `k3-upstream-boot`
by Enric Balletbo i Serra 28 Aug '25

28 Aug '25

Dear list, Hopefully I'm subscribed now and the email is not lost. I'd like to make a request for a `k3-upstream-boot` repository at ` https://gitlab.com/CentOS/automotive/rpms/` <https://gitlab.com/CentOS/automotive/rpms/>. This repository will host the RPM package for firmware needed to boot TI k3 platforms like the J784S4 EVM and AM69-SK boards. While here, I'd like to take the opportunity to ask you to create another repository, 's32g-vendor-boot'. Similar to the other, this repository will host the RPM package for firmware needed to boot S32G platforms using the public vendor components/repositories Your help is appreciated. Best regards, Enric > On Thu, Jul 31, 2025 at 4:13 PM Enric Balletbo i Serra < > eballetb(a)redhat.com> wrote: > >> Dear list, >> >> Could you please create a `k3-upstream-boot` repository in our GitLab >> instance under https://gitlab.com/CentOS/automotive/rpms/? >> >> The purpose of this repository is to track the rpm package that >> contains the firmware required to boot different TI k3 platforms like >> J784S4 EVM and AM69-SK boards. >> >> Best regards, >> Enric >> >

2 3

Re: Request to create a repository `k3-upstream-boot`
by Pierre-Yves Chibon 28 Aug '25

28 Aug '25

On Wed, Aug 27, 2025 at 01:35:26PM +0200, Enric Balletbo i Serra via automotive-sig wrote: > Dear list, > Hopefully I'm subscribed now and the email is not lost. I'd like to make a > request for a `k3-upstream-boot` repository at > `[1]https://gitlab.com/CentOS/automotive/rpms/`. This repository will host > the RPM package for firmware needed to boot TI k3 platforms like the > J784S4 EVM and AM69-SK boards. > While here, I'd like to take the opportunity to ask you to create another > repository, 's32g-vendor-boot'. Similar to the other, this repository will > host the RPM package for firmware needed to boot S32G platforms using the > public vendor components/repositories Both projects have been created: https://gitlab.com/CentOS/automotive/rpms/k3-upstream-boot https://gitlab.com/CentOS/automotive/rpms/s32g-vendor-boot Happy packing! Pierre PS: now sent from the right email

2 2

2026

2025

2024

2023

2022

2021

automotive-sig August 2025