From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Bug in buildman?
Date: Wed, 31 Dec 2014 13:44:23 +0100 [thread overview]
Message-ID: <54A3EFA7.20603@googlemail.com> (raw)
Hi Simon,
while test-building 2015.01-rc4 I encountered following strange
behaviour of buildman:
---8<---
andreas at 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 at 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 at 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 at 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.
Best regards
Andreas Bie?mann
next reply other threads:[~2014-12-31 12:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-31 12:44 Andreas Bießmann [this message]
2015-01-29 17:41 ` [U-Boot] Bug in buildman? Simon Glass
2015-01-29 18:05 ` Andreas Bießmann
2015-01-29 18:27 ` Simon Glass
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=54A3EFA7.20603@googlemail.com \
--to=andreas.devel@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.