From mboxrd@z Thu Jan 1 00:00:00 1970 From: Simon Glass Date: Sun, 8 Jul 2018 20:39:24 -0600 Subject: [U-Boot] build fail due to dependence error In-Reply-To: <16B6121B-9855-47A6-961A-613834160116@theobroma-systems.com> References: <83756b95-d066-2667-f036-24fd1097541e@rock-chips.com> <19ab9dda-5133-829a-4c4f-6988926a4a9f@rock-chips.com> <0C0CB5DB-9494-4784-AFA0-FD15BD8D2390@theobroma-systems.com> <16B6121B-9855-47A6-961A-613834160116@theobroma-systems.com> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit To: u-boot@lists.denx.de +Masahiro who might know On 2 July 2018 at 01:23, Dr. Philipp Tomsich 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 wrote: > > Hi Simon, > > > On 06/30/2018 12:19 PM, Simon Glass wrote: > > Hi, > > On 28 June 2018 at 01:41, Dr. Philipp Tomsich > wrote: > > Kever, > > is the link for ‘asm’ set up correctly? > > Thanks, > Philipp. > > On 28 Jun 2018, at 10:38, Kever Yang 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. > > Thanks, > - Kever > > Regards, > Simon > > On 2 July 2018 at 02:23, Dr. Philipp Tomsich 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 wrote: > > Hi Simon, > > > On 06/30/2018 12:19 PM, Simon Glass wrote: > > Hi, > > On 28 June 2018 at 01:41, Dr. Philipp Tomsich > wrote: > > Kever, > > is the link for ‘asm’ set up correctly? > > Thanks, > Philipp. > > On 28 Jun 2018, at 10:38, Kever Yang 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. > > Thanks, > - Kever > > Regards, > Simon > >