[U-Boot] help on using buildman

Simon Glass
2014-11-20T19:51:13Z

Hi York,

On 20 November 2014 19:46, York Sun <yorksun@freescale.com> wrote:
> On 11/20/2014 11:22 AM, York Sun wrote:
>> On 11/20/2014 11:13 AM, Simon Glass wrote:
>>> You can only see the make output if you comment out this line in
>>> builderthread.py:
>>>
>>> #args.append('-s')
>>>
>>> Then it will be in a file called 'log'. It would be nice to have an
>>> option for that...
>>>
>>
>> Let me try that.
>>
>
> I made the change to file tools/buildman/builderthread.py
>
> - args.append('-s')
> +# args.append('-s')
>
> I run it again for one commit and with one board
>
> $ ./tools/buildman/buildman -b working_upstream_qoriq --count=1 --keep-outputs
> --force-build --force-reconfig MPC832XEMDS_HOST_66 -ve
> No section: 'make-flags'
> boards.cfg is up to date. Nothing to do.
> Building 1 commit for 1 boards (1 thread, 24 jobs per thread)
> Cloning repo for thread 0
> 01: arm: ls102xa: Select ge2_clk125 for eTSEC clock muxing
> powerpc: + MPC832XEMDS_HOST_66
> +make[1]: *** No rule to make target `../arch//cpu/u-boot.lds', needed by
> `u-boot.lds'. Stop.
> +make: *** [sub-make] Error 2
> 0 0 1 /1 MPC832XEMDS_HOST_66
>
> $ ll
> ../working_upstream_qoriq/01_of_01_g3b33b926_arm--ls102xa--Select/MPC832XEMDS_HOST_66/
> total 28
> -rw-rw-r-- 1 jenkins jenkins 11588 Nov 20 13:28 autoconf.mk
> -rw-rw-r-- 1 jenkins jenkins 1 Nov 20 13:28 done
> -rw-rw-r-- 1 jenkins jenkins 168 Nov 20 13:28 err
> -rw-rw-r-- 1 jenkins jenkins 939 Nov 20 13:28 log
> -rw-rw-r-- 1 jenkins jenkins 276 Nov 20 13:28 toolchain
>
> I don't see much useful information in file log
>
> $ cat
> ../working_upstream_qoriq/01_of_01_g3b33b926_arm--ls102xa--Select/MPC832XEMDS_HOST_66/log
>
> make[1]: Entering directory
> `/local/jenkins/jobs/york-scm-test-upstream-before-requesting-pull/working_upstream_qoriq/.bm-work/00/build'
> GEN ./Makefile
> scripts/kconfig/conf --silentoldconfig Kconfig
> CHK include/config.h
> UPD include/config.h
> GEN include/autoconf.mk
> GEN include/autoconf.mk.dep
> make[1]: Leaving directory
> `/local/jenkins/jobs/york-scm-test-upstream-before-requesting-pull/working_upstream_qoriq/.bm-work/00/build'
> make[1]: Entering directory
> `/local/jenkins/jobs/york-scm-test-upstream-before-requesting-pull/working_upstream_qoriq/.bm-work/00/build'
> CHK include/config/uboot.release
> CHK include/generated/timestamp_autogenerated.h
> GEN ./Makefile
> UPD include/generated/timestamp_autogenerated.h
> UPD include/config/uboot.release
> make[1]: Leaving directory
> `/local/jenkins/jobs/york-scm-test-upstream-before-requesting-pull/working_upstream_qoriq/.bm-work/00/build'
>
> 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.

>
> 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:

[make-flags]
T4240QDS=V=1

Regards,
Simon