Hi Andreas, On 31 December 2014 at 05:44, Andreas Bießmann <andreas.de...@googlemail.com> wrote: > Hi Simon, > > while test-building 2015.01-rc4 I encountered following strange > behaviour of buildman: > > ---8<--- > andreas@andreas-pc % ./tools/buildman/buildman -b buildtest -o /tmp/bar > -v avr32 > boards.cfg is up to date. Nothing to do. > Building 1 commit for 10 boards (6 threads, 1 job per thread) > Cloning repo for thread 0 > Cloning repo for thread 1 > Cloning repo for thread 2 > Cloning repo for thread 3 > Cloning repo for thread 4 > Cloning repo for thread 5 > 01: Prepare v2015.01-rc4 > avr32: + atstk1006 > 01: Prepare v2015.01-rc4 > avr32: + atngw100 > 01: Prepare v2015.01-rc4 > avr32: + favr-32-ezkit > 01: Prepare v2015.01-rc4 > avr32: + atstk1004 > 01: Prepare v2015.01-rc4 > avr32: + hammerhead > 01: Prepare v2015.01-rc4 > avr32: + grasshopper > 01: Prepare v2015.01-rc4 > avr32: + atstk1003 > 01: Prepare v2015.01-rc4 > avr32: + atstk1002 > 01: Prepare v2015.01-rc4 > avr32: + mimc200 > 01: Prepare v2015.01-rc4 > avr32: + atngw100mkii > 0 4 6 /10 0:00:02 : atngw100mkii > ./tools/buildman/buildman -b buildtest -o /tmp/bar -v avr32 82.57s user > 16.90s system 249% cpu 39.899 total > andreas@andreas-pc % ./tools/buildman/buildman -b buildtest -o /tmp/bar > -v -lsed > boards.cfg is up to date. Nothing to do. > Summary of 1 commit for 1204 boards (6 threads, 1 job per thread) > 01: Prepare v2015.01-rc4 > avr32: + atngw100mkii atstk1003 grasshopper favr-32-ezkit > atstk1006 atstk1004 atstk1002 atngw100 hammerhead mimc200 > +(grasshopper,atngw100,favr-32-ezkit,atstk1006,atstk1004,hammerhead) > Could not find linker script. > +(grasshopper,atngw100,favr-32-ezkit,atstk1006,atstk1004,hammerhead) > make[1]: *** [prepare1] Error 1 > +(grasshopper,atngw100,favr-32-ezkit,atstk1006,atstk1004,hammerhead) > make: *** [sub-make] Error 2 > w+(atngw100mkii,atstk1002,atstk1003,mimc200) ../tools/kwbimage.c: In > function ‘kwbimage_set_header’: > w+(atngw100mkii,atstk1002,atstk1003,mimc200) ../tools/kwbimage.c:803:8: > warning: ‘headersz’ may be used uninitialized in this function > [-Wmaybe-uninitialized] > andreas@andreas-pc % ./tools/buildman/buildman -b buildtest -o /tmp/bar > -v -lsed grasshopper > boards.cfg is up to date. Nothing to do. > Summary of 1 commit for 1 boards (1 thread, 6 jobs per thread) > 01: Prepare v2015.01-rc4 > avr32: + grasshopper > +(grasshopper) Could not find linker script. > +(grasshopper) make[1]: *** [prepare1] Error 1 > +(grasshopper) make: *** [sub-make] Error 2 > andreas@andreas-pc % ./tools/buildman/buildman -b buildtest -o > /tmp/grasshopper -v grasshopper > boards.cfg is up to date. Nothing to do. > Building 1 commit for 1 boards (1 thread, 6 jobs per thread) > Cloning repo for thread 0 > 01: Prepare v2015.01-rc4 > avr32: + grasshopper > 0 1 0 /1 grasshopper > ./tools/buildman/buildman -b buildtest -o /tmp/grasshopper -v > grasshopper 14.11s user 2.69s system 183% cpu 9.171 total > andreas@andreas-pc % ./tools/buildman/buildman -b buildtest -o > /tmp/grasshopper -v -lsed grasshopper > boards.cfg is up to date. Nothing to do. > Summary of 1 commit for 1 boards (1 thread, 6 jobs per thread) > 01: Prepare v2015.01-rc4 > avr32: + grasshopper > w+(grasshopper) ../tools/kwbimage.c: In function ‘kwbimage_set_header’: > w+(grasshopper) ../tools/kwbimage.c:803:8: warning: ‘headersz’ may be > used uninitialized in this function [-Wmaybe-uninitialized] > --->8--- > > buildman complains about missing linker script for most boards which is > an error when building all avr32 boards. While it detects the correct > warning for still not fixed kwbimage.c maybe-uninitialized when building > just the single board which had an error before. Both builds are based > on v2015.01-rc4 and built in different locations.
Sorry for not getting back sooner - twice I read your email and tried to understand what is going on. If a build already exists, buildman will not re-run it. Also the output with -v is only provided for a build that actually happens. If it happened in the last run, it won't be reported again. The flow I use is: buildman -b <branch> to do the build, then buildman -b <branch> -s to see the errors and warnings, nicely sorted and collected. The -v option is a convenience which shows output as things are built. Does that have bearing on what you are seeing? Regards, Simon _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
