From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] kbuild: move ARCH, CPU, etc. to top Makefile to fix random build error
Date: Tue, 31 Mar 2015 08:57:37 -0700 [thread overview]
Message-ID: <551AC3F1.3030007@freescale.com> (raw)
In-Reply-To: <551AC132.3030509@wwwdotorg.org>
On 03/31/2015 08:45 AM, Stephen Warren wrote:
> On 03/31/2015 06:02 AM, Masahiro Yamada wrote:
>> Since the Kconfig conversion, some developers have reported that
>> Kbuild sometimes fails completely at random. According to the error
>> reports, it seems to occur for any target board, but only on very
>> fast computers.
>>
>> The log message for the fail case is like this:
>>
>> make[1]: *** No rule to make target `../arch//cpu/u-boot.lds',
>> needed by `u-boot.lds'. Stop.
>>
>> It looks like the top config.mk has not been included for *some*
>> reason, and $(ARCH) has been left blank.
>>
>> I suspect "autoconf_is_current" is not working in some situation.
>>
>> This commit moves the definition of ARCH, CPU, SOC, etc. to the
>> top Makefile, so they are surely set.
>
> This doesn't solve the issue for me, although it improves the chance of
> success and changes the error I get.
>
> With and without this patch, I ran:
>
> CROSS_COMPILE=arm-linux-gnueabi- ./MAKEALL rpi_2
>
> ... until whichever of success/fail had the fewest "hits" had at least 5
> "hits".
>
> Without this patch, the build failed 6 out of 11 runs with:
>
Stephen is so fast, saved me time to setup and test.
Let me know if I need to run test from my side.
York
next prev parent reply other threads:[~2015-03-31 15:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 12:02 [U-Boot] [PATCH] kbuild: move ARCH, CPU, etc. to top Makefile to fix random build error Masahiro Yamada
2015-03-31 15:37 ` York Sun
2015-03-31 15:45 ` Stephen Warren
2015-03-31 15:57 ` York Sun [this message]
2015-04-01 22:33 ` Stephen Warren
2015-04-03 3:54 ` Masahiro Yamada
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=551AC3F1.3030007@freescale.com \
--to=yorksun@freescale.com \
--cc=u-boot@lists.denx.de \
/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