I build rootfs for RPI Zero W
Yocto build started fail after commit “meta-mender-raspberrypi: Adjust to U-Boot 2025.04”
The problem is in the openembedded-core there is no U-Boot 2025.04 on the branch scarthgap
So patch fails trying to patch U-Boot-2024.01 by patch for 2025.04
ERROR: u-boot-1_2024.01-r0 do_patch: Applying patch '0001-configs-rpi-enable-mender-requirements.patch' on target directory '/workspace/tmp/work/sun_rpi0w-poky-linux-gnueabi/u-boot/2024.01/git'
CmdError('quilt --quiltrc /workspace/tmp/work/sun_rpi0w-poky-linux-gnueabi/u-boot/2024.01/recipe-sysroot-native/etc/quiltrc push', 0, 'stdout: Applying patch 0001-configs-rpi-enable-mender-requirements.patch
patching file configs/rpi_0_w_defconfig
Hunk #1 FAILED at 25.
Hunk #2 FAILED at 49.
2 out of 2 hunks FAILED -- rejects in file configs/rpi_0_w_defconfig
patching file configs/rpi_2_defconfig
Hunk #1 FAILED at 25.
Hunk #2 succeeded at 50 (offset 1 line).
1 out of 2 hunks FAILED -- rejects in file configs/rpi_2_defconfig
patching file configs/rpi_3_32b_defconfig
Hunk #1 FAILED at 24.
Hunk #2 succeeded at 51 (offset 1 line).
1 out of 2 hunks FAILED -- rejects in file configs/rpi_3_32b_defconfig
patching file configs/rpi_3_b_plus_defconfig
Hunk #1 FAILED at 27.
Hunk #2 FAILED at 57.
2 out of 2 hunks FAILED -- rejects in file configs/rpi_3_b_plus_defconfig
patching file configs/rpi_3_defconfig
Hunk #1 FAILED at 27.
Hunk #2 FAILED at 57.
2 out of 2 hunks FAILED -- rejects in file configs/rpi_3_defconfig
patching file configs/rpi_4_32b_defconfig
patching file configs/rpi_4_defconfig
Hunk #1 succeeded at 26 with fuzz 2 (offset -4 lines).
Hunk #2 FAILED at 69.
1 out of 2 hunks FAILED -- rejects in file configs/rpi_4_defconfig
patching file configs/rpi_arm64_defconfig
Hunk #1 succeeded at 25 with fuzz 2 (offset -2 lines).
Hunk #2 FAILED at 63.
1 out of 2 hunks FAILED -- rejects in file configs/rpi_arm64_defconfig
patching file configs/rpi_defconfig
Hunk #1 FAILED at 25.
Hunk #2 FAILED at 49.
2 out of 2 hunks FAILED -- rejects in file configs/rpi_defconfig
patching file env/Kconfig
Hunk #1 succeeded at 96 (offset -13 lines).
patching file include/configs/rpi.h
Patch 0001-configs-rpi-enable-mender-requirements.patch does not apply (enforce with -f)
stderr: ')
ERROR: Logfile of failure stored in: /workspace/tmp/work/sun_rpi0w-poky-linux-gnueabi/u-boot/2024.01/temp/log.do_patch.1821
Hi @mark-berner,
Thanks for reaching out! The Raspberry Pi builds in meta-mender-community depend on meta-lts-mixins to provide a more up-to-date version of u-boot. See meta-mender-community/kas/include/raspberrypi.yml at 6898594833c6c2836d74a3d96d16ffa7ab05a368 · mendersoftware/meta-mender-community · GitHub.
After adding that layer/branch on the given revision, the patches should apply.
Greetz,
Josef
Adding meta-lts-mixing didn’t help, sure I do simething wrong
Is it right set of repos should I download ?
RUN git clone -b scarthgap git://git.yoctoproject.org/poky /yocto/poky
RUN git clone -b scarthgap git://git.openembedded.org/openembedded-core /yocto/poky/meta-openembedded-core
RUN git clone -b scarthgap git://git.openembedded.org/meta-openembedded /yocto/poky/meta-openembedded
RUN git clone -b scarthgap git://git.yoctoproject.org/meta-raspberrypi /yocto/poky/meta-raspberrypi
RUN git clone -b scarthgap/u-boot git://git.yoctoproject.org/meta-lts-mixins /yocto/poky/meta-lts-mixins
RUN git clone -b scarthgap https://github.com/mendersoftware/meta-mender /yocto/poky/meta-mender
RUN git clone -b scarthgap https://github.com/mendersoftware/meta-mender-community /yocto/poky/meta-mender-community
Hi @mark-berner,
That looks a bit strange, but at least at first glance should probably work. In any case, can you try to build using the provided kas configuration (meta-mender-community/kas/raspberrypi0-wifi.yml at scarthgap · mendersoftware/meta-mender-community · GitHub)? It’s there for exactly that reason, being able to have a reproducible build setup. The last weekly build a couple of days was successful, see build_boards · mendersoftware/meta-mender-community@6898594 · GitHub.
Greetz,
Josef
Actualy I don’t use kas. Is it must for now using kas?
@mark-berner well, its not a must. But it would definitely help in understanding where the problem is. As I said, its purpose is providing a reproducible build with known good versions.
Greetz,
Josef
I have complex dockerized build, and migrate to kas will take a time, but just taking from kas dependencies valid commit SHA, did solve the problem
Thanks a lot for help.
Mark
RUN git clone -b scarthgap git://git.yoctoproject.org/poky /yocto/poky
RUN git --git-dir=/yocto/poky/.git --work-tree=/yocto/poky checkout c162696dae5798e2ab1198403d0bc1d65d64068d
RUN git clone -b scarthgap git://git.openembedded.org/meta-openembedded /yocto/poky/meta-openembedded
RUN git --git-dir=/yocto/poky/meta-openembedded/.git --work-tree=/yocto/poky/meta-openembedded checkout e92d0173a80ea7592c866618ef5293203c50544c
RUN git clone -b scarthgap https://github.com/agherzan/meta-raspberrypi.git /yocto/poky/meta-raspberrypi
RUN git --git-dir=/yocto/poky/meta-raspberrypi/.git --work-tree=/yocto/poky/meta-raspberrypi checkout 1091bde25e9ebaea33114edb85e4aee931d105f3
RUN git clone -b scarthgap/u-boot git://git.yoctoproject.org/meta-lts-mixins /yocto/poky/meta-lts-mixins
RUN git --git-dir=/yocto/poky/meta-lts-mixins/.git --work-tree=/yocto/poky/meta-lts-mixins checkout a44882db02a0ed0f149371831bfbe067665eb42b
RUN git clone -b scarthgap https://github.com/mendersoftware/meta-mender /yocto/poky/meta-mender
RUN git --git-dir=/yocto/poky/meta-mender/.git --work-tree=/yocto/poky/meta-mender checkout 0d393c2267a92091f975eb932338c07109f5f5fd
RUN git clone -b scarthgap https://github.com/mendersoftware/meta-mender-community /yocto/poky/meta-mender-community
RUN git --git-dir=/yocto/poky/meta-mender-community/.git --work-tree=/yocto/poky/meta-mender-community checkout 6898594833c6c2836d74a3d96d16ffa7ab05a368
1 Like
Hi @mark-berner,
Thanks, I consider the topic solved then. Just for future reference, kas also supports containerized builds: Building in a Container — kas 4.8.1 documentation
Greetz,
Josef