diff options
| author | Petr Štetiar <ynezz@true.cz> | 2023-01-03 12:44:51 +0100 |
|---|---|---|
| committer | Petr Štetiar <ynezz@true.cz> | 2023-01-11 15:16:52 +0100 |
| commit | 5c3679e39b615ff29c9315f810e8e15775cc2d01 (patch) | |
| tree | 78032df5e546fd0dfc82ac895433268203e73d9f /target/linux/x86 | |
| parent | cb679adf184d30261368707cd2b4f6cc7cf2a686 (diff) | |
| download | upstream-5c3679e39b615ff29c9315f810e8e15775cc2d01.tar.gz upstream-5c3679e39b615ff29c9315f810e8e15775cc2d01.tar.bz2 upstream-5c3679e39b615ff29c9315f810e8e15775cc2d01.zip | |
at91: sama7: fix racy SD card image generation
We've few low spec (make -j3) build workers attached to the 22.03
buildbot instance which from time to time exhibit following build
failure during image generation:
+ dd bs=512 if=root.ext4 of=openwrt-22.03-snapshot-r20028-43d71ad93e-at91-sama7-microchip_sama7g5-ek-ext4-sdcard.img.gz.img seek=135168 conv=notrunc
dd: failed to open 'root.ext4': No such file or directory
Thats likely due to the fact, that on buildbots we've
`TARGET_PER_DEVICE_ROOTFS=y` which produces differently named filesystem
image in the SD card image target dependency chain:
make_ext4fs -L rootfs ... root.ext4+pkg=68b329da
and that hardcoded root.ext4 becomes available from other target in the
later stages. So lets fix this issue by using IMAGE_ROOTFS Make variable
which should contain proper path to the root filesystem image.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Diffstat (limited to 'target/linux/x86')
0 files changed, 0 insertions, 0 deletions