From mboxrd@z Thu Jan 1 00:00:00 1970 From: York Sun Date: Tue, 31 Mar 2015 08:57:37 -0700 Subject: [U-Boot] [PATCH] kbuild: move ARCH, CPU, etc. to top Makefile to fix random build error In-Reply-To: <551AC132.3030509@wwwdotorg.org> References: <1427803341-28286-1-git-send-email-yamada.masahiro@socionext.com> <551AC132.3030509@wwwdotorg.org> Message-ID: <551AC3F1.3030007@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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