From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] help on using buildman
Date: Thu, 20 Nov 2014 11:55:48 -0800 [thread overview]
Message-ID: <546E4744.3090108@freescale.com> (raw)
In-Reply-To: <CAPnjgZ36r-eZcbwEh97Nf49VDNqMrKAcLUHEjkvM__tYOcaGdw@mail.gmail.com>
On 11/20/2014 11:51 AM, Simon Glass wrote:
>>
>> Nothing more than that. Where shall I look for ARCH?
>
> That doesn't look like a full build to me. The 'err' file may have
> more clues. You could try without '--force-build --force-reconfig'
> perhaps.
>
No, it failed. The err file has this
$ cat err
make[1]: *** No rule to make target `../arch//cpu/u-boot.lds', needed by
`u-boot.lds'. Stop.
make[1]: *** Waiting for unfinished jobs....
make: *** [sub-make] Error 2
>>
>> If I build for board T4240QDS, it has error on most but not all. T4240QDS
>> T4240QDS_SRIO_PCIE_BOOT T4240QDS_SECURE_BOOT failed, but T4240QDS_NAND didn't.
>
> It's a bit of a mystery. How about adding V=1 in your make flags in ~/.buildman:
>
I think the key is to configure it, not build it. With the failure case, it
doesn't build. I am thinking to find the equivalent to "make ARCH=power ...".
How to dump that?
York
next prev parent reply other threads:[~2014-11-20 19:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 18:47 [U-Boot] help on using buildman York Sun
2014-11-20 19:13 ` Simon Glass
2014-11-20 19:22 ` York Sun
2014-11-20 19:46 ` York Sun
2014-11-20 19:51 ` Simon Glass
2014-11-20 19:55 ` York Sun [this message]
2014-11-20 20:10 ` Simon Glass
2014-11-20 20:18 ` York Sun
2014-11-20 21:04 ` York Sun
2014-11-20 21:33 ` York Sun
2014-11-20 21:34 ` York Sun
2014-11-20 21:46 ` Simon Glass
2014-11-20 22:25 ` York Sun
2014-11-20 23:35 ` York Sun
2014-11-21 4:14 ` Simon Glass
2014-11-21 4:42 ` Masahiro Yamada
2014-11-21 4:53 ` Masahiro Yamada
2014-11-21 4:55 ` York Sun
2014-11-21 6:00 ` Masahiro Yamada
[not found] ` <E5C75E70-6F62-4E5C-9861-1D903D9BBFC9@freescale.com>
2014-11-21 6:47 ` York Sun
2014-11-21 17:14 ` York Sun
2014-11-21 17:22 ` York Sun
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=546E4744.3090108@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