public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Treat warnings different from errors in buildman?
Date: Fri, 22 Aug 2014 11:01:52 +0200	[thread overview]
Message-ID: <53F70700.2020408@gmail.com> (raw)
In-Reply-To: <20140821165342.GP19374@bill-the-cat>

Hi Tom,

On 21.08.2014 18:53, Tom Rini wrote:
> 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.  

ELDK-5.5 doesn't behave better. You will always need
CONFIG_USE_PRIVATE_LIBGCC=yes to build all MIPS boards at once and if
you don't have a full multilib toolchain. I'm still wondering why
Wolfgang decided long time ago, that U-Boot should rely on the
toolchain's libgcc and not use its own variant like the kernel does.

-- 
- Daniel

  parent reply	other threads:[~2014-08-22  9:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-21 16:53 [U-Boot] Treat warnings different from errors in buildman? Tom Rini
2014-08-21 18:43 ` Tom Rini
2014-08-22  9:01 ` Daniel Schwierzeck [this message]
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=53F70700.2020408@gmail.com \
    --to=daniel.schwierzeck@gmail.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