[U-Boot] Treat warnings different from errors in buildman?

Daniel Schwierzeck
2014-08-22T11:11:08Z

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-

--
- Daniel