public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Treat warnings different from errors in buildman?
Date: Fri, 22 Aug 2014 07:52:02 -0400	[thread overview]
Message-ID: <20140822115202.GT19374@bill-the-cat> (raw)
In-Reply-To: <53F7254C.2070207@gmail.com>

On Fri, Aug 22, 2014 at 01:11:08PM +0200, Daniel Schwierzeck wrote:

> On 22.08.2014 12:47, Tom Rini wrote:
> > On Fri, Aug 22, 2014 at 11:01:52AM +0200, Daniel Schwierzeck wrote:
> >> 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.
> > 
> > Ah, what I mean was that I can't seem to find the right 'trick' to have
> > CONFIG_USE_PRIVATE_LIBGCC work today.  I tried make-flags for buildman
> > and export CONFIG_USE_PRIVATE_LIBGCC=yes in my wrapper around MAKEALL.
> > 
> 
> The trick is to use "CONFIG_USE_PRIVATE_LIBGCC=y" instead of
> "CONFIG_USE_PRIVATE_LIBGCC=yes" because it is handled like a boolean
> Kconfig symbol.
> 
> BTW: I'm using env scripts for different toolchains which could be
> sourced. For ELDK-5.5 I have:
> 
> $ cat env-eldk5.5-mips
> export CONFIG_USE_PRIVATE_LIBGCC=y
> export USE_PRIVATE_LIBGCC=yes
> export
> CROSS_COMPILE=/opt/eldk-5.5/mips/sysroots/i686-eldk-linux/usr/bin/mips-linux/mips-linux-

Ah, OK.  I've got something started on buildman now for an env-flags
section and it's building mips/mipsel.  I'll post a patch once it's
less embarassing looking.

-- 
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/20140822/87042d29/attachment.pgp>

  reply	other threads:[~2014-08-22 11:52 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
2014-08-22 10:47   ` Tom Rini
2014-08-22 11:11     ` Daniel Schwierzeck
2014-08-22 11:52       ` Tom Rini [this message]
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=20140822115202.GT19374@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