From mboxrd@z Thu Jan 1 00:00:00 1970 From: York Sun Date: Tue, 31 Mar 2015 08:37:38 -0700 Subject: [U-Boot] [PATCH] kbuild: move ARCH, CPU, etc. to top Makefile to fix random build error In-Reply-To: <1427803341-28286-1-git-send-email-yamada.masahiro@socionext.com> References: <1427803341-28286-1-git-send-email-yamada.masahiro@socionext.com> Message-ID: <551ABF42.1030005@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 05: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. > > Signed-off-by: Masahiro Yamada > Reported-by: Tom Rini > > Reported-by: York Sun > Reported-by: Stephen Warren > --- > > Sorry for leaving this problem so long. > > I have never been able to reproduce this bug on my computer, > so I am not sure this patch can fix the problem. > I wrote this patch based on my guess. > (I just tested this patch has no bad impact.) > > Tom, York, Stephen, > > Could you test this patch fixes the problem? > Yes I will try. It seems to related to specific OS. I have seen it on old CentOS (fast machine though) when running by script. But I haven't been able to reproduce it reliably. York