Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10161] New: unable to build u-boot.imx reliably
Date: Thu, 03 Aug 2017 17:29:55 +0000	[thread overview]
Message-ID: <bug-10161-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 10161
           Summary: unable to build u-boot.imx reliably
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: yurovsky at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

Created attachment 7156
  --> https://bugs.busybox.net/attachment.cgi?id=7156&action=edit
hacky workaround

I'm unable to build the u-boot.imx image (for Freescale i.MX SoCs) reliably
(that is, it generally works but if I "slow down" my system by making the CPUs
busy, or use a slower machine, I can break the build very often).

The issue seems to be in u-boot's build system but I'm not certain so I wanted
to check if there's anything that we might be doing in buildroot that should be
done differently before taking this up with them.

To build the i.MX image the config should have:

BR2_TARGET_UBOOT_FORMAT_IMX=y

(and be one of the i.MX targets anyway since we need a board target in u-boot).
What happens is u-boot will process a template config file and eventually
mkimage is run to generate the .imx image using the .cfg files in the board
directory. The build will fail because the processed .cfg isn't found and it
seems that the .cfg was in fact built, it just raced with the image step.

I have a workaround that, while hacky, shows that we can prevent the problem by
making those steps less parallel (attached).

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

             reply	other threads:[~2017-08-03 17:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03 17:29 bugzilla at busybox.net [this message]
2017-08-04 17:04 ` [Buildroot] [Bug 10161] unable to build u-boot.imx reliably bugzilla at busybox.net
2017-08-04 17:37 ` 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@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