Hi York,
On 20 November 2014 19:55, York Sun <york...@freescale.com> wrote:
> 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?
Add a 'print' line to make() in builder.py:
cmd = [self.gnu_make] + list(args)
print cmd
result = command.RunPipe([cmd], capture=True, capture_stderr=True,
cwd=cwd, raise_on_error=False, **kwargs)
return result
Regards,
Simon
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
