From mboxrd@z Thu Jan 1 00:00:00 1970 From: York Sun Date: Fri, 24 Jul 2015 08:55:25 -0700 Subject: [U-Boot] buildman dtc check error In-Reply-To: References: <55B16656.1030904@freescale.com> <55B191A7.9040102@freescale.com> Message-ID: <55B25FED.3080709@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 07/23/2015 08:45 PM, Simon Glass wrote: > Hi York, > > On 23 July 2015 at 19:15, York Sun wrote: >> >> >> On 07/23/2015 03:24 PM, Simon Glass wrote: >>> Hi York, >>> >>> On 23 July 2015 at 16:10, York Sun wrote: >>>> Simon, >>>> >>>> I am facing a weird issue on the latest u-boot. I can successfully build u-boot >>>> manually, but with buildman I see checkdtc error. >>>> >>>> aarch64: + ls2085aqds >>>> +make[1]: *** [checkdtc] Error 1 >>>> +make: *** [sub-make] Error 2 >>>> >>>> I have DTC 1.4.1-ge5e6df7c. Is there any flag for buildman I can see more >>>> information? I always use -vVeu as the flag. >>> >>> That's not very helpful, sorry. You can always look at the raw logs. >>> You could try an in-tree build with -i if that is what you are using >>> normally. >>> >> >> Simon, >> >> The raw log has been a mystery for me since beginning. Where do I find it? >> Using -i flag also has the same error message. > > We really should solve this mystery :-) It's documented in the buildman README. > > By default, ..//// > > or if you are just building current source it is in ../current > Thanks, Simon. I didn't use --force-build. So I guess repeat build didn't actually build anything. I found the file "log" but it is empty for a successful build. York