From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10161] unable to build u-boot.imx reliably
Date: Fri, 04 Aug 2017 17:04:57 +0000 [thread overview]
Message-ID: <bug-10161-163-8d0b88CX1L@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10161-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10161
--- Comment #1 from Arnout Vandecappelle <arnout@mind.be> ---
Without any other evidence, we can only assume it's an issue with the U-Boot
build system. And something that is very hard to fix at the Buildroot level:
since we don't know which U-Boot version is being used, we can't easily patch
it.
I have done a quick review of the Makefile for imx in the U-Boot source, and it
looks good to me. But you haven't really given sufficient information to
pinpoint the problem. You should try to reproduce with V=1 so we get usable
output. And also try to reproduce outside of Buildroot - should be easy, you
basically just have to run 'make CROSS_COMPILE=... ARCH=arm ..._defconfig; make
CROSS_COMPILE=... ARCH=arm V=1 u-boot.imx'.
Or perhaps it only happens when you try to build u-boot.imx and u-boot-dtb.imx
in parallel?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-08-04 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 17:29 [Buildroot] [Bug 10161] New: unable to build u-boot.imx reliably bugzilla at busybox.net
2017-08-04 17:04 ` bugzilla at busybox.net [this message]
2017-08-04 17:37 ` [Buildroot] [Bug 10161] " bugzilla at busybox.net
2017-08-11 16:13 ` bugzilla at busybox.net
2018-01-11 7: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-10161-163-8d0b88CX1L@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