[U-Boot] build fail due to dependence error

[Masahiro Yamada]

Hi.


2018-07-09 11:39 GMT+09:00 Simon Glass <sjg at chromium.org>:
> +Masahiro who might know
>
> On 2 July 2018 at 01:23, Dr. Philipp Tomsich
> <philipp.tomsich at theobroma-systems.com> wrote:
>> Kever,
>>
>> Could you check the build artifacts in Jenkins to see whether after
>> the ‘make [configname]_defconfig’, the link for asm/arch is correctly
>> set up?
>>
>> Thanks,
>> Philipp.
>>
>> On 2 Jul 2018, at 09:54, Kever Yang <kever.yang at rock-chips.com> wrote:
>>
>> Hi Simon,
>>
>>
>> On 06/30/2018 12:19 PM, Simon Glass wrote:
>>
>> Hi,
>>
>> On 28 June 2018 at 01:41, Dr. Philipp Tomsich
>> <philipp.tomsich at theobroma-systems.com> wrote:
>>
>> Kever,
>>
>> is the link for ‘asm’ set up correctly?
>>
>> Thanks,
>> Philipp.
>>
>> On 28 Jun 2018, at 10:38, Kever Yang <kever.yang at rock-chips.com> wrote:
>>
>> Hi Simon,
>>
>>        Do you have any idea about this error?
>>
>>
>> CC      lib/asm-offsets.s
>>  CC      arch/arm/lib/asm-offsets.s
>> fixdep: error opening config file: arch/arm/include/asm/arch/hardware.h: No
>> such file or directory
>> Kbuild:64: recipe for target 'arch/arm/lib/asm-offsets.s' failed
>> make[1]: *** [arch/arm/lib/asm-offsets.s] Error 2
>> make[1]: *** 正在等待未完成的任务....
>>  CHK     include/config.h
>> Makefile:1340: recipe for target 'prepare0' failed
>>
>> Thanks,
>> - Kever
>>
>> On 06/01/2018 05:59 PM, Kever Yang wrote:
>>
>> Hi Guys,
>>
>>     I met below error from time to time when build U-Boot project.
>>
>> fixdep: error opening config file: arch/arm/include/asm/arch/hardware.h: No
>> such file or directory
>>
>>    The folder 'arch/arm/include/asm/arch' is a link for
>> 'arch/arm/include/asm/arch-rockchip',
>>
>> which is dynamic generate by build system, I thinks there should be some
>> dependency issue?
>>
>>    How to fix this kind of issue?
>>
>> I am not sure what is going on there. I don't see this.
>>
>> Are you using 'make distclean' or 'make mrproper' on your object tree
>> every now and then?
>>
>>
>> This is happen sometimes in our Jenkins verify, It will gone when I
>> rebase the patch(re-build without any change),
>> we do 'make distclean' every time before a new build.


Hmm, I cannot reproduce this error.


I have no clue about this.





-- 
Best Regards
Masahiro Yamada