From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9301] New: U-boot fails to build with default zynq_zed_defconfig configuration
Date: Fri, 23 Sep 2016 14:41:00 +0000 [thread overview]
Message-ID: <bug-9301-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=9301
Bug ID: 9301
Summary: U-boot fails to build with default zynq_zed_defconfig
configuration
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: matt.kraai at abbott.com
CC: buildroot at uclibc.org
Target Milestone: ---
When I run `make zynq_zed_defconfig && make all` on master, the build
eventually fails with the following messages:
> cp -dpf .../buildroot/output/build/uboot-xilinx-v2016.2/spl/boot.bin .../buildroot/output/images/
> cp: cannot stat '.../buildroot/output/build/uboot-xilinx-v2016.2/spl/boot.bin': No such file or directory
Commit fad58cefa4a392b52eafe46a773f8cbfb8aadb43 introduced this error. Before
that commit, no make targets were specified when make was invoked to build
uboot. This caused make to build the all target, which caused it to build
spl/boot.bin. After that commit, the u-boot.img target was specified. As a
result of this change, make only built u-boot.img and not spl/boot.bin.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-09-23 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 14:41 bugzilla at busybox.net [this message]
2016-09-26 20:22 ` [Buildroot] [Bug 9301] U-boot fails to build with default zynq_zed_defconfig configuration bugzilla at busybox.net
2016-09-27 17:44 ` bugzilla at busybox.net
2016-09-28 16:13 ` bugzilla at busybox.net
2016-10-11 15:50 ` 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-9301-163@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