New: buildroot-2019.08-rc3 does not build for Pi Zero W

https://bugs.busybox.net/show_bug.cgi?id=12156

Bug ID: 12156
Summary: buildroot-2019.08-rc3 does not build for Pi Zero W
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: critical
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: info at hifiberry.com
CC: buildroot at uclibc.org
Target Milestone: ---

When trying to build a Pi Zero W image with the latest release candidate, build stops when trying to install the DTB file for the Pi Zero:

INFO: cmd: "mkdir -p "/home/matuschd/buildroot-2019.08-rc3/output/build/genimage.tmp"" (stderr):
INFO: cmd: "rm -rf "/home/matuschd/buildroot-2019.08-rc3/output/build/genimage.tmp"/*" (stderr):
INFO: cmd: "mkdir -p "/home/matuschd/buildroot-2019.08-rc3/output/build/genimage.tmp"" (stderr):
INFO: cmd: "cp -a "/home/matuschd/buildroot-2019.08-rc3/output/target" "/home/matuschd/buildroot-2019.08-rc3/output/build/genimage.tmp/root"" (stderr):
INFO: cmd: "find '/home/matuschd/buildroot-2019.08-rc3/output/build/genimage.tmp/root' -depth -type d -printf '%P\0' | xargs -0 -I {} touch -r '/home/matuschd/buildroot-2019.08-rc3/output/target/{}' '/home/matuschd/buildroot-2019.08-rc3/output/build/genimage.tmp/root/{}'" (stderr):
ERROR: file(bcm2708-rpi-zero-w.dtb):
stat(/home/matuschd/buildroot-2019.08-rc3/output/images/bcm2708-rpi-zero-w.dtb)
failed: No such file or directory
ERROR: vfat(boot.vfat): could not setup bcm2708-rpi-zero-w.dtb Makefile:812: recipe for target 'target-post-image' failed make[1]: *** [target-post-image] Error 1
Makefile:84: recipe for target '_all' failed
make: *** [_all] Error 2

Seems to me that the filename should be bcm2708-rpi-0-w.dtb instead of bcm2708-rpi-zero-w.dtb

Commands to reproduce the error:

make raspberrypi0w_defconfig
make

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=12156

Peter Korsgaard <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED

--- Comment #1 from Peter Korsgaard <[email protected]> --- Are you sure this is a clean build? I cannot reproduce it here:

INFO: vfat(boot.vfat): adding file 'bcm2708-rpi-0-w.dtb' as 'bcm2708-rpi-0-w.dtb' ...
INFO: vfat(boot.vfat): cmd: "MTOOLS_SKIP_CHECK=1 mcopy -bsp -i '/home/peko/source/buildroot/output-rpi/images/boot.vfat' '/home/peko/source/buildroot/output-rpi/images/bcm2708-rpi-0-w.dtb' '::'" (stderr):
INFO: vfat(boot.vfat): adding file 'rpi-firmware/bootcode.bin' as 'rpi-firmware/bootcode.bin' ...

And the file is there as it should be:
find -name bcm2708-rpi-0-w.\* ./build/linux-custom/arch/arm/boot/dts/bcm2708-rpi-0-w.dtb ./build/linux-custom/arch/arm/boot/dts/bcm2708-rpi-0-w.dts ./build/linux-headers-custom/arch/arm/boot/dts/bcm2708-rpi-0-w.dts ./images/bcm2708-rpi-0-w.dtb
git describe
2019.08-rc3-3-g268bdf0360

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=12156

--- Comment #2 from Peter Korsgaard <[email protected]> --- (In reply to info from comment #0)
But the defconfig USES bcm2708-rpi-0-w.dtb:

grep DTS_NAME configs/raspberrypi0w_defconfig BR2_LINUX_KERNEL_INTREE_DTS_NAME="bcm2708-rpi-0-w"

Did you perhaps edit raspberrypi0w_defconfig locally?

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=12156

info at hifiberry.com changed:

What |Removed |Added
----------------------------------------------------------------------------

         Resolution|---                         |INVALID
             Status|ASSIGNED                    |RESOLVED

--- Comment #3 from info at hifiberry.com ---
Just did a fresh extract of the buildroot tar file. Works now. Looks like something was messed up on the system.

You are receiving this mail because:
You are on the CC list for the bug.