On 2015年07月30日 19:37, Otavio Salvador wrote:
Hello, On Thu, Jul 30, 2015 at 3:26 AM, Rongqing Li <rongqing...@windriver.com> wrote: ...u-boot-mkimage just be upgraded, and has the similar your suggestive fix: commit cffcd2861310855130db52c93f7bf4d9b511741d Author: Masahiro Yamada <yamada.masah...@socionext.com> Date: Fri Apr 3 12:30:25 2015 +0900 kbuild: include config.mk when auto.conf is not older than .config Since the Kconfig conversion, config.mk has been included only when include/config/auto.conf is newer than the .config file. It causes build error if both files have the same time-stamps. It is actually possible because EXT* file systems have a 1s time-stamp resolution. The config.mk should be included when include/config/auto.conf is *not older* than the .config file. Signed-off-by: Masahiro Yamada <yamada.masah...@socionext.com> Reported-by: Tom Rini <tr...@konsulko.com> Reported-by: York Sun <york...@freescale.com> Reported-by: Stephen Warren <swar...@nvidia.com> Reported-by: Matthew Gerlach <mgerl...@opensource.altera.com> Tested-by: Stephen Warren <swar...@nvidia.com>This is part of 2015.07 release so I am wondering what is the issue here? Is this patch for old release? Fido for instance?
"It causes build error if both files have the same time-stamps. It is actually possible because EXT* file systems have a 1s time-stamp resolution." Ｉ see the build error on SUSE Linux Enterprise Desktop 11 SP2 with ext3 filesystem frequently. -Roy -- Best Reagrds, Roy | RongQing Li -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
