From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] buildman dtc check error
Date: Fri, 24 Jul 2015 08:55:25 -0700 [thread overview]
Message-ID: <55B25FED.3080709@freescale.com> (raw)
In-Reply-To: <CAPnjgZ0HXQF1hndLUCntSXf-2rU4fJC5ewtHg+aYNb+s25=w3A@mail.gmail.com>
On 07/23/2015 08:45 PM, Simon Glass wrote:
> Hi York,
>
> On 23 July 2015 at 19:15, York Sun <yorksun@freescale.com> wrote:
>>
>>
>> On 07/23/2015 03:24 PM, Simon Glass wrote:
>>> Hi York,
>>>
>>> On 23 July 2015 at 16:10, York Sun <yorksun@freescale.com> 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, ../<branch>/<commit>/<board>/
>
> 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
prev parent reply other threads:[~2015-07-24 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 22:10 [U-Boot] buildman dtc check error York Sun
2015-07-23 22:24 ` Simon Glass
2015-07-24 1:15 ` York Sun
2015-07-24 3:45 ` Simon Glass
2015-07-24 15:55 ` York Sun [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55B25FED.3080709@freescale.com \
--to=yorksun@freescale.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox