From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12156] buildroot-2019.08-rc3 does not build for Pi Zero W
Date: Fri, 30 Aug 2019 10:12:39 +0000 [thread overview]
Message-ID: <bug-12156-163-oOTAl1LnjQ@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12156-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12156
Peter Korsgaard <jacmet@uclibc.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #1 from Peter Korsgaard <jacmet@uclibc.org> ---
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.
next prev parent reply other threads:[~2019-08-30 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 7:37 [Buildroot] [Bug 12156] New: buildroot-2019.08-rc3 does not build for Pi Zero W bugzilla at busybox.net
2019-08-30 10:12 ` bugzilla at busybox.net [this message]
2019-08-30 10:16 ` [Buildroot] [Bug 12156] " bugzilla at busybox.net
2019-08-30 10:55 ` bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-12156-163-oOTAl1LnjQ@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox