From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Treat warnings different from errors in buildman?
Date: Thu, 21 Aug 2014 12:53:42 -0400 [thread overview]
Message-ID: <20140821165342.GP19374@bill-the-cat> (raw)
Hey,
So as I migrate scripts over to buildman, one issue I have is that
today warning and errors are treated the same:
u-boot (master)$ ./tools/buildman/buildman -b master -c 1 -ve -T 1 -j 9 'arc|blackfin|microblaze|m68k|nds32|sparc|x86|aarch64|sandbox|mips' -s
Summary of 1 commit for 128 boards (1 thread, 9 jobs per thread)
01: git-mailrc: add patman and buildman alias
mips: + pb1000 dbau1550_el qemu_mipsel maltael
sparc: + grsim_leon2 gr_cpci_ax2000 gr_ep2s60 grsim gr_xc3s_1500
arc: + tb100 arcangel4-be axs101 arcangel4
sandbox: + sandbox
mips is the mipsel libgcc thing, I need to see if eldk5.5 behaves
better than 5.2.1 in that regard and passing or setting
CONFIG_USE_PRIVATE_LIBGCC=yes. sparc is however all warnings (old gcc
warning when it should not).
Also, is there any way to note which boards/arches an error comes from?
+/home/trini/work/u-boot/master/.bm-work/00/disk/part.c: In function
`get_device':
+/home/trini/work/u-boot/master/.bm-work/00/disk/part.c:453: warning:
'hwpart' might be used uninitialized in this function
Is confusing if you hadn't done a sparc solo build before and seen that.
Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140821/b6c49953/attachment.pgp>
next reply other threads:[~2014-08-21 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 16:53 Tom Rini [this message]
2014-08-21 18:43 ` [U-Boot] Treat warnings different from errors in buildman? Tom Rini
2014-08-22 9:01 ` Daniel Schwierzeck
2014-08-22 10:47 ` Tom Rini
2014-08-22 11:11 ` Daniel Schwierzeck
2014-08-22 11:52 ` Tom Rini
2014-08-23 5:59 ` 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=20140821165342.GP19374@bill-the-cat \
--to=trini@ti.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