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:23:18 +0100 |
| commit | 3b669bc3f32f7594f38187a284a65ca2c35a0121 (patch) | |
| tree | 2321ecab46a2ca4e94026292c3a662e2f9c0e776 /package/utils/lua | |
| parent | 26595eac0580053e5910b04db0458074c6f3b8ee (diff) | |
| download | upstream-3b669bc3f32f7594f38187a284a65ca2c35a0121.tar.gz upstream-3b669bc3f32f7594f38187a284a65ca2c35a0121.tar.bz2 upstream-3b669bc3f32f7594f38187a284a65ca2c35a0121.zip | |
at91: sam9x,sama5: 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 (shortened for brewity):
+ dd bs=512 if=root.ext4 of=openwrt-22.03...sdcard.img.gz.img
dd: failed to open 'root.ext4': No such file or directory
Thats happening 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` image filename becomes available from
other Make targets 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.
Fixing remaining subtargets ommited in commit 5c3679e39b61 ("at91:
sama7: fix racy SD card image generation").
Fixes: 5c3679e39b61 ("at91: sama7: fix racy SD card image generation")
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Diffstat (limited to 'package/utils/lua')
0 files changed, 0 insertions, 0 deletions