subject:"\[U\-Boot\] buildman errors"

Re: [U-Boot] buildman errors

2016-01-26 Thread Bin Meng

Hi Tom,

On Wed, Jan 27, 2016 at 10:08 AM, Tom Rini  wrote:
> On Wed, Jan 27, 2016 at 09:55:02AM +0800, Bin Meng wrote:
>> Hi Tom,
>>
>> On Tue, Jan 26, 2016 at 10:47 PM, Tom Rini  wrote:
>> > On Tue, Jan 26, 2016 at 12:26:07PM +0800, Bin Meng wrote:
>> >> Hi Tom,
>> >>
>> >> On Mon, Jan 25, 2016 at 10:12 PM, Tom Rini  wrote:
>> >> > On Mon, Jan 25, 2016 at 11:18:26AM +0800, Bin Meng wrote:
>> >> >> Hi Tom,
>> >> >>
>> >> >> On Mon, Jan 25, 2016 at 11:05 AM, Tom Rini  wrote:
>> >> >> > On Mon, Jan 25, 2016 at 10:34:16AM +0800, Bin Meng wrote:
>> >> >> >> Hi Tom,
>> >> >> >>
>> >> >> >> On Mon, Jan 25, 2016 at 12:19 AM, Tom Rini  
>> >> >> >> wrote:
>> >> >> >> > On Sun, Jan 24, 2016 at 12:00:42PM +0800, Bin Meng wrote:
>> >> >> >> >
>> >> >> >> >> Hi,
>> >> >> >> >>
>> >> >> >> >> Summary of 71 commits for 1100 boards (24 threads, 1 job per 
>> >> >> >> >> thread)
>> >> >> >> >> 01: iocon / bamboo: Drop CONFIG_SYS_LONGHELP
>> >> >> >> >>   blackfin:  +   bf561-acvilon cm-bf561 blackstamp bf537-minotaur
>> >> >> >> >> bct-brettl2 cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1 
>> >> >> >> >> bf527-ad7160-eval
>> >> >> >> >> bf609-ezkit bf537-stamp bf527-ezkit-v2 cm-bf537e tcm-bf518 
>> >> >> >> >> cm-bf537u
>> >> >> >> >> bf527-ezkit cm-bf533 bf533-ezkit ibf-dsp561 bf537-pnav bf537-srv1
>> >> >> >> >> cm-bf548 bf538f-ezkit bf548-ezkit bf525-ucr2 blackvme tcm-bf537
>> >> >> >> >> bf533-stamp dnp5370 bf518f-ezbrd bf526-ezbrd bf561-ezkit br4
>> >> >> >> >>aarch64:  +   test
>> >> >> >> >>  avr32:  +   atngw100mkii grasshopper atstk1002 atngw100
>> >> >> >> >> sh:  +   sh7753evb sh7785lcr_32bit sh7785lcr
>> >> >> >> >>arc:  +   arcangel4-be axs101 axs103 tb100 arcangel4
>> >> >> >> >>   openrisc:  +   openrisc-generic
>> >> >> >> >>powerpc:  +   TQM834x katmai
>> >> >> >> >>arm:  +   mx28evk mx28evk_nand xfi3 bg0900 sansa_fuze_plus
>> >> >> >> >> mx23evk m28evk sc_sps_1 mx28evk_spi apx4devkit mx23_olinuxino
>> >> >> >> >> mx28evk_auart_console
>> >> >> >> >>  nds32:  +   adp-ag101p
>> >> >> >> >
>> >> >> >> > I need to finally fetch a few toolchains as I don't do
>> >> >> >> > avr32/sh/openrisc/nds32 iirc.  As a tangent, x86 is very broken 
>> >> >> >> > with gcc
>> >> >> >> > 5.x, can you look into it? :)
>> >> >> >> >
>> >> >> >>
>> >> >> >> Sure, I can look into x86. Which gcc 5.x toolchain are you using?
>> >> >> >
>> >> >> > Pretty much any, I've seen it for a long time but not had time to 
>> >> >> > poke
>> >> >> > at the libgcc "fun" that's involved here.
>> >> >> >
>> >> >>
>> >> >> I mean if there is any prebuilt gcc 5.x for me to grab and test? Or do
>> >> >> I need build one from gcc source?
>> >> >
>> >> > Fedora has shipped with gcc 5.x for a release or two and Debian/unstable
>> >> > is how I get all of my gcc 5.x toolchains for build testing.
>> >> >
>> >>
>> >> I installed a fresh Fedora 23 and got gcc 5.1.1 up and running.
>> >> However I see _zero_ compiler warnings/errors using gcc 5.1.1 when
>> >> building all of the 9 x86 boards.
>> >>
>> >> The only thing I noticed, which is probably best matched to what you
>> >> said "x86 is very broken with gcc 5.x", is:
>> >>
>> >>   HOSTCC  tools/aisimage.o
>> >> In file included from tools/aisimage.c:10:0:
>> >> include/image.h:923:27: fatal error: openssl/evp.h: No such file or 
>> >> directory
>> >> compilation terminated.
>> >> scripts/Makefile.host:111: recipe for target 'tools/aisimage.o' failed
>> >> make[1]: *** [tools/aisimage.o] Error 1
>> >> Makefile:1196: recipe for target 'tools' failed
>> >> make: *** [tools] Error 2
>> >
>> > Are you using the stock configs?
>>
>> Yes.
>>
>> > +(galileo,crownbay,coreboot-x86,bayleybay,qemu-x86,chromebook_link,minnowmax,chromebox_panther)
>> > arch/x86/lib/built-in.o: In function `__wrap___udivdi3':
>> > +(galileo,crownbay,coreboot-x86,bayleybay,qemu-x86,chromebook_link,minnowmax,chromebox_panther)
>> > build/../arch/x86/lib/gcc.c:25: undefined reference to
>> > `__normal___udivdi3'
>> >
>>
>> Is your Fedora a 64-bit installation? And a 64-bit gcc compiler,
>> right? I am using 32-bit Fedora with a 32-bit gcc. This is nothing
>> related to gcc 5.x too. The same thing happens in gcc 4.x. If we want
>> to use 64-bit gcc to build 32-bit U-Boot, gcc must ship with multilib
>> support.
>
> Ug, even with CONFIG_USE_PRIVATE_LIBGCC=y ?
>

Yes. x86 build relies on gcc to provide a normal libgcc and adds some
hacks on top of it (private).

Regards,
Bin
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] buildman errors

2016-01-26 Thread Tom Rini

On Tue, Jan 26, 2016 at 12:26:07PM +0800, Bin Meng wrote:
> Hi Tom,
> 
> On Mon, Jan 25, 2016 at 10:12 PM, Tom Rini  wrote:
> > On Mon, Jan 25, 2016 at 11:18:26AM +0800, Bin Meng wrote:
> >> Hi Tom,
> >>
> >> On Mon, Jan 25, 2016 at 11:05 AM, Tom Rini  wrote:
> >> > On Mon, Jan 25, 2016 at 10:34:16AM +0800, Bin Meng wrote:
> >> >> Hi Tom,
> >> >>
> >> >> On Mon, Jan 25, 2016 at 12:19 AM, Tom Rini  wrote:
> >> >> > On Sun, Jan 24, 2016 at 12:00:42PM +0800, Bin Meng wrote:
> >> >> >
> >> >> >> Hi,
> >> >> >>
> >> >> >> Summary of 71 commits for 1100 boards (24 threads, 1 job per thread)
> >> >> >> 01: iocon / bamboo: Drop CONFIG_SYS_LONGHELP
> >> >> >>   blackfin:  +   bf561-acvilon cm-bf561 blackstamp bf537-minotaur
> >> >> >> bct-brettl2 cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1 
> >> >> >> bf527-ad7160-eval
> >> >> >> bf609-ezkit bf537-stamp bf527-ezkit-v2 cm-bf537e tcm-bf518 cm-bf537u
> >> >> >> bf527-ezkit cm-bf533 bf533-ezkit ibf-dsp561 bf537-pnav bf537-srv1
> >> >> >> cm-bf548 bf538f-ezkit bf548-ezkit bf525-ucr2 blackvme tcm-bf537
> >> >> >> bf533-stamp dnp5370 bf518f-ezbrd bf526-ezbrd bf561-ezkit br4
> >> >> >>aarch64:  +   test
> >> >> >>  avr32:  +   atngw100mkii grasshopper atstk1002 atngw100
> >> >> >> sh:  +   sh7753evb sh7785lcr_32bit sh7785lcr
> >> >> >>arc:  +   arcangel4-be axs101 axs103 tb100 arcangel4
> >> >> >>   openrisc:  +   openrisc-generic
> >> >> >>powerpc:  +   TQM834x katmai
> >> >> >>arm:  +   mx28evk mx28evk_nand xfi3 bg0900 sansa_fuze_plus
> >> >> >> mx23evk m28evk sc_sps_1 mx28evk_spi apx4devkit mx23_olinuxino
> >> >> >> mx28evk_auart_console
> >> >> >>  nds32:  +   adp-ag101p
> >> >> >
> >> >> > I need to finally fetch a few toolchains as I don't do
> >> >> > avr32/sh/openrisc/nds32 iirc.  As a tangent, x86 is very broken with 
> >> >> > gcc
> >> >> > 5.x, can you look into it? :)
> >> >> >
> >> >>
> >> >> Sure, I can look into x86. Which gcc 5.x toolchain are you using?
> >> >
> >> > Pretty much any, I've seen it for a long time but not had time to poke
> >> > at the libgcc "fun" that's involved here.
> >> >
> >>
> >> I mean if there is any prebuilt gcc 5.x for me to grab and test? Or do
> >> I need build one from gcc source?
> >
> > Fedora has shipped with gcc 5.x for a release or two and Debian/unstable
> > is how I get all of my gcc 5.x toolchains for build testing.
> >
> 
> I installed a fresh Fedora 23 and got gcc 5.1.1 up and running.
> However I see _zero_ compiler warnings/errors using gcc 5.1.1 when
> building all of the 9 x86 boards.
> 
> The only thing I noticed, which is probably best matched to what you
> said "x86 is very broken with gcc 5.x", is:
> 
>   HOSTCC  tools/aisimage.o
> In file included from tools/aisimage.c:10:0:
> include/image.h:923:27: fatal error: openssl/evp.h: No such file or directory
> compilation terminated.
> scripts/Makefile.host:111: recipe for target 'tools/aisimage.o' failed
> make[1]: *** [tools/aisimage.o] Error 1
> Makefile:1196: recipe for target 'tools' failed
> make: *** [tools] Error 2

Are you using the stock configs?
+(galileo,crownbay,coreboot-x86,bayleybay,qemu-x86,chromebook_link,minnowmax,chromebox_panther)
arch/x86/lib/built-in.o: In function `__wrap___udivdi3':
+(galileo,crownbay,coreboot-x86,bayleybay,qemu-x86,chromebook_link,minnowmax,chromebox_panther)
build/../arch/x86/lib/gcc.c:25: undefined reference to
`__normal___udivdi3'

-- 
Tom


signature.asc
Description: Digital signature
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] buildman errors

2016-01-26 Thread Bin Meng

Hi Tom,

On Tue, Jan 26, 2016 at 10:47 PM, Tom Rini  wrote:
> On Tue, Jan 26, 2016 at 12:26:07PM +0800, Bin Meng wrote:
>> Hi Tom,
>>
>> On Mon, Jan 25, 2016 at 10:12 PM, Tom Rini  wrote:
>> > On Mon, Jan 25, 2016 at 11:18:26AM +0800, Bin Meng wrote:
>> >> Hi Tom,
>> >>
>> >> On Mon, Jan 25, 2016 at 11:05 AM, Tom Rini  wrote:
>> >> > On Mon, Jan 25, 2016 at 10:34:16AM +0800, Bin Meng wrote:
>> >> >> Hi Tom,
>> >> >>
>> >> >> On Mon, Jan 25, 2016 at 12:19 AM, Tom Rini  wrote:
>> >> >> > On Sun, Jan 24, 2016 at 12:00:42PM +0800, Bin Meng wrote:
>> >> >> >
>> >> >> >> Hi,
>> >> >> >>
>> >> >> >> Summary of 71 commits for 1100 boards (24 threads, 1 job per thread)
>> >> >> >> 01: iocon / bamboo: Drop CONFIG_SYS_LONGHELP
>> >> >> >>   blackfin:  +   bf561-acvilon cm-bf561 blackstamp bf537-minotaur
>> >> >> >> bct-brettl2 cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1 
>> >> >> >> bf527-ad7160-eval
>> >> >> >> bf609-ezkit bf537-stamp bf527-ezkit-v2 cm-bf537e tcm-bf518 cm-bf537u
>> >> >> >> bf527-ezkit cm-bf533 bf533-ezkit ibf-dsp561 bf537-pnav bf537-srv1
>> >> >> >> cm-bf548 bf538f-ezkit bf548-ezkit bf525-ucr2 blackvme tcm-bf537
>> >> >> >> bf533-stamp dnp5370 bf518f-ezbrd bf526-ezbrd bf561-ezkit br4
>> >> >> >>aarch64:  +   test
>> >> >> >>  avr32:  +   atngw100mkii grasshopper atstk1002 atngw100
>> >> >> >> sh:  +   sh7753evb sh7785lcr_32bit sh7785lcr
>> >> >> >>arc:  +   arcangel4-be axs101 axs103 tb100 arcangel4
>> >> >> >>   openrisc:  +   openrisc-generic
>> >> >> >>powerpc:  +   TQM834x katmai
>> >> >> >>arm:  +   mx28evk mx28evk_nand xfi3 bg0900 sansa_fuze_plus
>> >> >> >> mx23evk m28evk sc_sps_1 mx28evk_spi apx4devkit mx23_olinuxino
>> >> >> >> mx28evk_auart_console
>> >> >> >>  nds32:  +   adp-ag101p
>> >> >> >
>> >> >> > I need to finally fetch a few toolchains as I don't do
>> >> >> > avr32/sh/openrisc/nds32 iirc.  As a tangent, x86 is very broken with 
>> >> >> > gcc
>> >> >> > 5.x, can you look into it? :)
>> >> >> >
>> >> >>
>> >> >> Sure, I can look into x86. Which gcc 5.x toolchain are you using?
>> >> >
>> >> > Pretty much any, I've seen it for a long time but not had time to poke
>> >> > at the libgcc "fun" that's involved here.
>> >> >
>> >>
>> >> I mean if there is any prebuilt gcc 5.x for me to grab and test? Or do
>> >> I need build one from gcc source?
>> >
>> > Fedora has shipped with gcc 5.x for a release or two and Debian/unstable
>> > is how I get all of my gcc 5.x toolchains for build testing.
>> >
>>
>> I installed a fresh Fedora 23 and got gcc 5.1.1 up and running.
>> However I see _zero_ compiler warnings/errors using gcc 5.1.1 when
>> building all of the 9 x86 boards.
>>
>> The only thing I noticed, which is probably best matched to what you
>> said "x86 is very broken with gcc 5.x", is:
>>
>>   HOSTCC  tools/aisimage.o
>> In file included from tools/aisimage.c:10:0:
>> include/image.h:923:27: fatal error: openssl/evp.h: No such file or directory
>> compilation terminated.
>> scripts/Makefile.host:111: recipe for target 'tools/aisimage.o' failed
>> make[1]: *** [tools/aisimage.o] Error 1
>> Makefile:1196: recipe for target 'tools' failed
>> make: *** [tools] Error 2
>
> Are you using the stock configs?

Yes.

> +(galileo,crownbay,coreboot-x86,bayleybay,qemu-x86,chromebook_link,minnowmax,chromebox_panther)
> arch/x86/lib/built-in.o: In function `__wrap___udivdi3':
> +(galileo,crownbay,coreboot-x86,bayleybay,qemu-x86,chromebook_link,minnowmax,chromebox_panther)
> build/../arch/x86/lib/gcc.c:25: undefined reference to
> `__normal___udivdi3'
>

Is your Fedora a 64-bit installation? And a 64-bit gcc compiler,
right? I am using 32-bit Fedora with a 32-bit gcc. This is nothing
related to gcc 5.x too. The same thing happens in gcc 4.x. If we want
to use 64-bit gcc to build 32-bit U-Boot, gcc must ship with multilib
support.

Regards,
Bin
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] buildman errors

2016-01-26 Thread Tom Rini

On Wed, Jan 27, 2016 at 09:55:02AM +0800, Bin Meng wrote:
> Hi Tom,
> 
> On Tue, Jan 26, 2016 at 10:47 PM, Tom Rini  wrote:
> > On Tue, Jan 26, 2016 at 12:26:07PM +0800, Bin Meng wrote:
> >> Hi Tom,
> >>
> >> On Mon, Jan 25, 2016 at 10:12 PM, Tom Rini  wrote:
> >> > On Mon, Jan 25, 2016 at 11:18:26AM +0800, Bin Meng wrote:
> >> >> Hi Tom,
> >> >>
> >> >> On Mon, Jan 25, 2016 at 11:05 AM, Tom Rini  wrote:
> >> >> > On Mon, Jan 25, 2016 at 10:34:16AM +0800, Bin Meng wrote:
> >> >> >> Hi Tom,
> >> >> >>
> >> >> >> On Mon, Jan 25, 2016 at 12:19 AM, Tom Rini  
> >> >> >> wrote:
> >> >> >> > On Sun, Jan 24, 2016 at 12:00:42PM +0800, Bin Meng wrote:
> >> >> >> >
> >> >> >> >> Hi,
> >> >> >> >>
> >> >> >> >> Summary of 71 commits for 1100 boards (24 threads, 1 job per 
> >> >> >> >> thread)
> >> >> >> >> 01: iocon / bamboo: Drop CONFIG_SYS_LONGHELP
> >> >> >> >>   blackfin:  +   bf561-acvilon cm-bf561 blackstamp bf537-minotaur
> >> >> >> >> bct-brettl2 cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1 
> >> >> >> >> bf527-ad7160-eval
> >> >> >> >> bf609-ezkit bf537-stamp bf527-ezkit-v2 cm-bf537e tcm-bf518 
> >> >> >> >> cm-bf537u
> >> >> >> >> bf527-ezkit cm-bf533 bf533-ezkit ibf-dsp561 bf537-pnav bf537-srv1
> >> >> >> >> cm-bf548 bf538f-ezkit bf548-ezkit bf525-ucr2 blackvme tcm-bf537
> >> >> >> >> bf533-stamp dnp5370 bf518f-ezbrd bf526-ezbrd bf561-ezkit br4
> >> >> >> >>aarch64:  +   test
> >> >> >> >>  avr32:  +   atngw100mkii grasshopper atstk1002 atngw100
> >> >> >> >> sh:  +   sh7753evb sh7785lcr_32bit sh7785lcr
> >> >> >> >>arc:  +   arcangel4-be axs101 axs103 tb100 arcangel4
> >> >> >> >>   openrisc:  +   openrisc-generic
> >> >> >> >>powerpc:  +   TQM834x katmai
> >> >> >> >>arm:  +   mx28evk mx28evk_nand xfi3 bg0900 sansa_fuze_plus
> >> >> >> >> mx23evk m28evk sc_sps_1 mx28evk_spi apx4devkit mx23_olinuxino
> >> >> >> >> mx28evk_auart_console
> >> >> >> >>  nds32:  +   adp-ag101p
> >> >> >> >
> >> >> >> > I need to finally fetch a few toolchains as I don't do
> >> >> >> > avr32/sh/openrisc/nds32 iirc.  As a tangent, x86 is very broken 
> >> >> >> > with gcc
> >> >> >> > 5.x, can you look into it? :)
> >> >> >> >
> >> >> >>
> >> >> >> Sure, I can look into x86. Which gcc 5.x toolchain are you using?
> >> >> >
> >> >> > Pretty much any, I've seen it for a long time but not had time to poke
> >> >> > at the libgcc "fun" that's involved here.
> >> >> >
> >> >>
> >> >> I mean if there is any prebuilt gcc 5.x for me to grab and test? Or do
> >> >> I need build one from gcc source?
> >> >
> >> > Fedora has shipped with gcc 5.x for a release or two and Debian/unstable
> >> > is how I get all of my gcc 5.x toolchains for build testing.
> >> >
> >>
> >> I installed a fresh Fedora 23 and got gcc 5.1.1 up and running.
> >> However I see _zero_ compiler warnings/errors using gcc 5.1.1 when
> >> building all of the 9 x86 boards.
> >>
> >> The only thing I noticed, which is probably best matched to what you
> >> said "x86 is very broken with gcc 5.x", is:
> >>
> >>   HOSTCC  tools/aisimage.o
> >> In file included from tools/aisimage.c:10:0:
> >> include/image.h:923:27: fatal error: openssl/evp.h: No such file or 
> >> directory
> >> compilation terminated.
> >> scripts/Makefile.host:111: recipe for target 'tools/aisimage.o' failed
> >> make[1]: *** [tools/aisimage.o] Error 1
> >> Makefile:1196: recipe for target 'tools' failed
> >> make: *** [tools] Error 2
> >
> > Are you using the stock configs?
> 
> Yes.
> 
> > +(galileo,crownbay,coreboot-x86,bayleybay,qemu-x86,chromebook_link,minnowmax,chromebox_panther)
> > arch/x86/lib/built-in.o: In function `__wrap___udivdi3':
> > +(galileo,crownbay,coreboot-x86,bayleybay,qemu-x86,chromebook_link,minnowmax,chromebox_panther)
> > build/../arch/x86/lib/gcc.c:25: undefined reference to
> > `__normal___udivdi3'
> >
> 
> Is your Fedora a 64-bit installation? And a 64-bit gcc compiler,
> right? I am using 32-bit Fedora with a 32-bit gcc. This is nothing
> related to gcc 5.x too. The same thing happens in gcc 4.x. If we want
> to use 64-bit gcc to build 32-bit U-Boot, gcc must ship with multilib
> support.

Ug, even with CONFIG_USE_PRIVATE_LIBGCC=y ?

-- 
Tom


signature.asc
Description: Digital signature
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] buildman errors

2016-01-25 Thread Marek Vasut

On Tuesday, January 26, 2016 at 05:26:07 AM, Bin Meng wrote:
> Hi Tom,
> 
> On Mon, Jan 25, 2016 at 10:12 PM, Tom Rini  wrote:
> > On Mon, Jan 25, 2016 at 11:18:26AM +0800, Bin Meng wrote:
> >> Hi Tom,
> >> 
> >> On Mon, Jan 25, 2016 at 11:05 AM, Tom Rini  wrote:
> >> > On Mon, Jan 25, 2016 at 10:34:16AM +0800, Bin Meng wrote:
> >> >> Hi Tom,
> >> >> 
> >> >> On Mon, Jan 25, 2016 at 12:19 AM, Tom Rini  wrote:
> >> >> > On Sun, Jan 24, 2016 at 12:00:42PM +0800, Bin Meng wrote:
> >> >> >> Hi,
> >> >> >> 
> >> >> >> Summary of 71 commits for 1100 boards (24 threads, 1 job per
> >> >> >> thread) 01: iocon / bamboo: Drop CONFIG_SYS_LONGHELP
> >> >> >> 
> >> >> >>   blackfin:  +   bf561-acvilon cm-bf561 blackstamp bf537-minotaur
> >> >> >> 
> >> >> >> bct-brettl2 cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1
> >> >> >> bf527-ad7160-eval bf609-ezkit bf537-stamp bf527-ezkit-v2
> >> >> >> cm-bf537e tcm-bf518 cm-bf537u bf527-ezkit cm-bf533 bf533-ezkit
> >> >> >> ibf-dsp561 bf537-pnav bf537-srv1 cm-bf548 bf538f-ezkit
> >> >> >> bf548-ezkit bf525-ucr2 blackvme tcm-bf537 bf533-stamp dnp5370
> >> >> >> bf518f-ezbrd bf526-ezbrd bf561-ezkit br4
> >> >> >> 
> >> >> >>aarch64:  +   test
> >> >> >>
> >> >> >>  avr32:  +   atngw100mkii grasshopper atstk1002 atngw100
> >> >> >>  
> >> >> >> sh:  +   sh7753evb sh7785lcr_32bit sh7785lcr
> >> >> >>
> >> >> >>arc:  +   arcangel4-be axs101 axs103 tb100 arcangel4
> >> >> >>   
> >> >> >>   openrisc:  +   openrisc-generic
> >> >> >>   
> >> >> >>powerpc:  +   TQM834x katmai
> >> >> >>
> >> >> >>arm:  +   mx28evk mx28evk_nand xfi3 bg0900 sansa_fuze_plus
> >> >> >> 
> >> >> >> mx23evk m28evk sc_sps_1 mx28evk_spi apx4devkit mx23_olinuxino
> >> >> >> mx28evk_auart_console
> >> >> >> 
> >> >> >>  nds32:  +   adp-ag101p
> >> >> > 
> >> >> > I need to finally fetch a few toolchains as I don't do
> >> >> > avr32/sh/openrisc/nds32 iirc.  As a tangent, x86 is very broken
> >> >> > with gcc 5.x, can you look into it? :)
> >> >> 
> >> >> Sure, I can look into x86. Which gcc 5.x toolchain are you using?
> >> > 
> >> > Pretty much any, I've seen it for a long time but not had time to poke
> >> > at the libgcc "fun" that's involved here.
> >> 
> >> I mean if there is any prebuilt gcc 5.x for me to grab and test? Or do
> >> I need build one from gcc source?
> > 
> > Fedora has shipped with gcc 5.x for a release or two and Debian/unstable
> > is how I get all of my gcc 5.x toolchains for build testing.
> 
> I installed a fresh Fedora 23 and got gcc 5.1.1 up and running.
> However I see _zero_ compiler warnings/errors using gcc 5.1.1 when
> building all of the 9 x86 boards.
> 
> The only thing I noticed, which is probably best matched to what you
> said "x86 is very broken with gcc 5.x", is:
> 
>   HOSTCC  tools/aisimage.o
> In file included from tools/aisimage.c:10:0:
> include/image.h:923:27: fatal error: openssl/evp.h: No such file or
> directory compilation terminated.
> scripts/Makefile.host:111: recipe for target 'tools/aisimage.o' failed
> make[1]: *** [tools/aisimage.o] Error 1
> Makefile:1196: recipe for target 'tools' failed
> make: *** [tools] Error 2
> 
> But this is nothing related to gcc 5.x. It should be something related
> to openssl. After I "dnf install openssl-devel", minnowmax can be
> built successfully without any error/warning.

Yeah, that's our standard openssl bug :-)
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] buildman errors

2016-01-25 Thread Bin Meng

Hi Tom,

On Mon, Jan 25, 2016 at 10:12 PM, Tom Rini  wrote:
> On Mon, Jan 25, 2016 at 11:18:26AM +0800, Bin Meng wrote:
>> Hi Tom,
>>
>> On Mon, Jan 25, 2016 at 11:05 AM, Tom Rini  wrote:
>> > On Mon, Jan 25, 2016 at 10:34:16AM +0800, Bin Meng wrote:
>> >> Hi Tom,
>> >>
>> >> On Mon, Jan 25, 2016 at 12:19 AM, Tom Rini  wrote:
>> >> > On Sun, Jan 24, 2016 at 12:00:42PM +0800, Bin Meng wrote:
>> >> >
>> >> >> Hi,
>> >> >>
>> >> >> Summary of 71 commits for 1100 boards (24 threads, 1 job per thread)
>> >> >> 01: iocon / bamboo: Drop CONFIG_SYS_LONGHELP
>> >> >>   blackfin:  +   bf561-acvilon cm-bf561 blackstamp bf537-minotaur
>> >> >> bct-brettl2 cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1 bf527-ad7160-eval
>> >> >> bf609-ezkit bf537-stamp bf527-ezkit-v2 cm-bf537e tcm-bf518 cm-bf537u
>> >> >> bf527-ezkit cm-bf533 bf533-ezkit ibf-dsp561 bf537-pnav bf537-srv1
>> >> >> cm-bf548 bf538f-ezkit bf548-ezkit bf525-ucr2 blackvme tcm-bf537
>> >> >> bf533-stamp dnp5370 bf518f-ezbrd bf526-ezbrd bf561-ezkit br4
>> >> >>aarch64:  +   test
>> >> >>  avr32:  +   atngw100mkii grasshopper atstk1002 atngw100
>> >> >> sh:  +   sh7753evb sh7785lcr_32bit sh7785lcr
>> >> >>arc:  +   arcangel4-be axs101 axs103 tb100 arcangel4
>> >> >>   openrisc:  +   openrisc-generic
>> >> >>powerpc:  +   TQM834x katmai
>> >> >>arm:  +   mx28evk mx28evk_nand xfi3 bg0900 sansa_fuze_plus
>> >> >> mx23evk m28evk sc_sps_1 mx28evk_spi apx4devkit mx23_olinuxino
>> >> >> mx28evk_auart_console
>> >> >>  nds32:  +   adp-ag101p
>> >> >
>> >> > I need to finally fetch a few toolchains as I don't do
>> >> > avr32/sh/openrisc/nds32 iirc.  As a tangent, x86 is very broken with gcc
>> >> > 5.x, can you look into it? :)
>> >> >
>> >>
>> >> Sure, I can look into x86. Which gcc 5.x toolchain are you using?
>> >
>> > Pretty much any, I've seen it for a long time but not had time to poke
>> > at the libgcc "fun" that's involved here.
>> >
>>
>> I mean if there is any prebuilt gcc 5.x for me to grab and test? Or do
>> I need build one from gcc source?
>
> Fedora has shipped with gcc 5.x for a release or two and Debian/unstable
> is how I get all of my gcc 5.x toolchains for build testing.
>

I installed a fresh Fedora 23 and got gcc 5.1.1 up and running.
However I see _zero_ compiler warnings/errors using gcc 5.1.1 when
building all of the 9 x86 boards.

The only thing I noticed, which is probably best matched to what you
said "x86 is very broken with gcc 5.x", is:

  HOSTCC  tools/aisimage.o
In file included from tools/aisimage.c:10:0:
include/image.h:923:27: fatal error: openssl/evp.h: No such file or directory
compilation terminated.
scripts/Makefile.host:111: recipe for target 'tools/aisimage.o' failed
make[1]: *** [tools/aisimage.o] Error 1
Makefile:1196: recipe for target 'tools' failed
make: *** [tools] Error 2

But this is nothing related to gcc 5.x. It should be something related
to openssl. After I "dnf install openssl-devel", minnowmax can be
built successfully without any error/warning.

Regards,
Bin
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] buildman errors

2016-01-25 Thread Tom Rini

On Mon, Jan 25, 2016 at 11:18:26AM +0800, Bin Meng wrote:
> Hi Tom,
> 
> On Mon, Jan 25, 2016 at 11:05 AM, Tom Rini  wrote:
> > On Mon, Jan 25, 2016 at 10:34:16AM +0800, Bin Meng wrote:
> >> Hi Tom,
> >>
> >> On Mon, Jan 25, 2016 at 12:19 AM, Tom Rini  wrote:
> >> > On Sun, Jan 24, 2016 at 12:00:42PM +0800, Bin Meng wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> Summary of 71 commits for 1100 boards (24 threads, 1 job per thread)
> >> >> 01: iocon / bamboo: Drop CONFIG_SYS_LONGHELP
> >> >>   blackfin:  +   bf561-acvilon cm-bf561 blackstamp bf537-minotaur
> >> >> bct-brettl2 cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1 bf527-ad7160-eval
> >> >> bf609-ezkit bf537-stamp bf527-ezkit-v2 cm-bf537e tcm-bf518 cm-bf537u
> >> >> bf527-ezkit cm-bf533 bf533-ezkit ibf-dsp561 bf537-pnav bf537-srv1
> >> >> cm-bf548 bf538f-ezkit bf548-ezkit bf525-ucr2 blackvme tcm-bf537
> >> >> bf533-stamp dnp5370 bf518f-ezbrd bf526-ezbrd bf561-ezkit br4
> >> >>aarch64:  +   test
> >> >>  avr32:  +   atngw100mkii grasshopper atstk1002 atngw100
> >> >> sh:  +   sh7753evb sh7785lcr_32bit sh7785lcr
> >> >>arc:  +   arcangel4-be axs101 axs103 tb100 arcangel4
> >> >>   openrisc:  +   openrisc-generic
> >> >>powerpc:  +   TQM834x katmai
> >> >>arm:  +   mx28evk mx28evk_nand xfi3 bg0900 sansa_fuze_plus
> >> >> mx23evk m28evk sc_sps_1 mx28evk_spi apx4devkit mx23_olinuxino
> >> >> mx28evk_auart_console
> >> >>  nds32:  +   adp-ag101p
> >> >
> >> > I need to finally fetch a few toolchains as I don't do
> >> > avr32/sh/openrisc/nds32 iirc.  As a tangent, x86 is very broken with gcc
> >> > 5.x, can you look into it? :)
> >> >
> >>
> >> Sure, I can look into x86. Which gcc 5.x toolchain are you using?
> >
> > Pretty much any, I've seen it for a long time but not had time to poke
> > at the libgcc "fun" that's involved here.
> >
> 
> I mean if there is any prebuilt gcc 5.x for me to grab and test? Or do
> I need build one from gcc source?

Fedora has shipped with gcc 5.x for a release or two and Debian/unstable
is how I get all of my gcc 5.x toolchains for build testing.

-- 
Tom


signature.asc
Description: Digital signature
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] buildman errors

2016-01-24 Thread Marek Vasut

On Monday, January 25, 2016 at 04:12:37 AM, Bin Meng wrote:
> Hi Marek,

Hi!

> On Mon, Jan 25, 2016 at 11:01 AM, Marek Vasut  wrote:
> > On Monday, January 25, 2016 at 03:58:38 AM, Bin Meng wrote:
> >> Hi Marek,
> >> 
> >> On Mon, Jan 25, 2016 at 10:52 AM, Marek Vasut  wrote:
> >> > On Monday, January 25, 2016 at 03:45:25 AM, Bin Meng wrote:
> >> >> On Mon, Jan 25, 2016 at 10:42 AM, Bin Meng  wrote:
> >> >> > On Mon, Jan 25, 2016 at 1:01 AM, Stefano Babic  wrote:
> >> >> >> On 24/01/2016 17:41, Marek Vasut wrote:
> >> >> >>> On Sunday, January 24, 2016 at 05:19:54 PM, Tom Rini wrote:
> >> >>  On Sun, Jan 24, 2016 at 12:00:42PM +0800, Bin Meng wrote:
> >> >> > Hi,
> >> >> > 
> >> >> > Summary of 71 commits for 1100 boards (24 threads, 1 job per
> >> >> > thread) 01: iocon / bamboo: Drop CONFIG_SYS_LONGHELP
> >> >> > 
> >> >> >   blackfin:  +   bf561-acvilon cm-bf561 blackstamp
> >> >> >   bf537-minotaur
> >> >> > 
> >> >> > bct-brettl2 cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1
> >> >> > bf527-ad7160-eval bf609-ezkit bf537-stamp bf527-ezkit-v2
> >> >> > cm-bf537e tcm-bf518 cm-bf537u bf527-ezkit cm-bf533 bf533-ezkit
> >> >> > ibf-dsp561 bf537-pnav bf537-srv1 cm-bf548 bf538f-ezkit
> >> >> > bf548-ezkit bf525-ucr2 blackvme tcm-bf537 bf533-stamp dnp5370
> >> >> > bf518f-ezbrd bf526-ezbrd bf561-ezkit br4
> >> >> > 
> >> >> >aarch64:  +   test
> >> >> >
> >> >> >  avr32:  +   atngw100mkii grasshopper atstk1002 atngw100
> >> >> >  
> >> >> > sh:  +   sh7753evb sh7785lcr_32bit sh7785lcr
> >> >> >
> >> >> >arc:  +   arcangel4-be axs101 axs103 tb100 arcangel4
> >> >> >   
> >> >> >   openrisc:  +   openrisc-generic
> >> >> >   
> >> >> >powerpc:  +   TQM834x katmai
> >> >> >
> >> >> >arm:  +   mx28evk mx28evk_nand xfi3 bg0900
> >> >> >sansa_fuze_plus
> >> >> > 
> >> >> > mx23evk m28evk sc_sps_1 mx28evk_spi apx4devkit mx23_olinuxino
> >> >> > mx28evk_auart_console
> >> >> >>> 
> >> >> >>> All of MXS is broken, why ? I don't recall any chances to MXS
> >> >> >>> being done recently, so what happened ?
> >> >> >> 
> >> >> >> I confirm this - I have not seen any breakage (but I built today
> >> >> >> with an older gcc). Bing, can you output what you have seen for
> >> >> >> mxs boards ? They looks ok to me.
> >> >> > 
> >> >> > $ make m28evk_defconfig
> >> >> > 
> >> >> >   HOSTCC  scripts/basic/fixdep
> >> >> >   HOSTCC  scripts/kconfig/conf.o
> >> >> >   SHIPPED scripts/kconfig/zconf.tab.c
> >> >> >   SHIPPED scripts/kconfig/zconf.lex.c
> >> >> >   SHIPPED scripts/kconfig/zconf.hash.c
> >> >> >   HOSTCC  scripts/kconfig/zconf.tab.o
> >> >> >   HOSTLD  scripts/kconfig/conf
> >> >> > 
> >> >> > #
> >> >> > # configuration written to .config
> >> >> > #
> >> >> > $ make
> >> >> > scripts/kconfig/conf  --silentoldconfig Kconfig
> >> >> > 
> >> >> >   CHK include/config.h
> >> >> >   UPD include/config.h
> >> >> >   GEN include/autoconf.mk
> >> >> >   GEN include/autoconf.mk.dep
> >> >> >   GEN spl/include/autoconf.mk
> >> >> >   CHK include/config/uboot.release
> >> >> >   UPD include/config/uboot.release
> >> >> >   CHK include/generated/version_autogenerated.h
> >> >> >   UPD include/generated/version_autogenerated.h
> >> >> >   CHK include/generated/timestamp_autogenerated.h
> >> >> >   UPD include/generated/timestamp_autogenerated.h
> >> >> >   CC  lib/asm-offsets.s
> >> >> >   CHK include/generated/generic-asm-offsets.h
> >> >> >   UPD include/generated/generic-asm-offsets.h
> >> >> >   CC  arch/arm/lib/asm-offsets.s
> >> >> >   CHK include/generated/asm-offsets.h
> >> >> >   UPD include/generated/asm-offsets.h
> >> >> >   HOSTCC  tools/bmp_logo
> >> >> >   HOSTCC  tools/envcrc.o
> >> >> >   WRAPtools/lib/crc32.c
> >> >> >   HOSTCC  tools/lib/crc32.o
> >> >> >   WRAPtools/common/env_embedded.c
> >> >> >   HOSTCC  tools/common/env_embedded.o
> >> >> >   WRAPtools/lib/sha1.c
> >> >> >   HOSTCC  tools/lib/sha1.o
> >> >> >   HOSTLD  tools/envcrc
> >> >> >   HOSTCC  tools/gen_eth_addr
> >> >> >   HOSTCC  tools/img2srec
> >> >> >   HOSTCC  tools/mkenvimage.o
> >> >> >   HOSTCC  tools/os_support.o
> >> >> >   HOSTLD  tools/mkenvimage
> >> >> >   HOSTCC  tools/aisimage.o
> >> >> >   HOSTCC  tools/atmelimage.o
> >> >> >   WRAPtools/common/bootm.c
> >> >> >   HOSTCC  tools/common/bootm.o
> >> >> >   HOSTCC  tools/default_image.o
> >> >> >   WRAPtools/lib/fdtdec_common.c
> >> >> >   HOSTCC  tools/lib/fdtdec_common.o
> >> >> >   WRAPtools/lib/fdtdec.c
> >> >> >   HOSTCC  tools/lib/fdtdec.o
> >> >> >   HOSTCC  tools/fit_common.o
> >> >> >   HOSTCC  tools/fit_image.o
> >> >> >   HOSTCC  tools/gpimage.o
> >> >> >   HOSTCC  tools/gpimage-common.o
> >> >> >   WRAP

Re: [U-Boot] buildman errors

2016-01-24 Thread Marek Vasut

On Monday, January 25, 2016 at 03:58:38 AM, Bin Meng wrote:
> Hi Marek,
> 
> On Mon, Jan 25, 2016 at 10:52 AM, Marek Vasut  wrote:
> > On Monday, January 25, 2016 at 03:45:25 AM, Bin Meng wrote:
> >> On Mon, Jan 25, 2016 at 10:42 AM, Bin Meng  wrote:
> >> > On Mon, Jan 25, 2016 at 1:01 AM, Stefano Babic  wrote:
> >> >> On 24/01/2016 17:41, Marek Vasut wrote:
> >> >>> On Sunday, January 24, 2016 at 05:19:54 PM, Tom Rini wrote:
> >>  On Sun, Jan 24, 2016 at 12:00:42PM +0800, Bin Meng wrote:
> >> > Hi,
> >> > 
> >> > Summary of 71 commits for 1100 boards (24 threads, 1 job per
> >> > thread) 01: iocon / bamboo: Drop CONFIG_SYS_LONGHELP
> >> > 
> >> >   blackfin:  +   bf561-acvilon cm-bf561 blackstamp bf537-minotaur
> >> > 
> >> > bct-brettl2 cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1
> >> > bf527-ad7160-eval bf609-ezkit bf537-stamp bf527-ezkit-v2 cm-bf537e
> >> > tcm-bf518 cm-bf537u bf527-ezkit cm-bf533 bf533-ezkit ibf-dsp561
> >> > bf537-pnav bf537-srv1 cm-bf548 bf538f-ezkit bf548-ezkit bf525-ucr2
> >> > blackvme tcm-bf537 bf533-stamp dnp5370 bf518f-ezbrd bf526-ezbrd
> >> > bf561-ezkit br4
> >> > 
> >> >aarch64:  +   test
> >> >
> >> >  avr32:  +   atngw100mkii grasshopper atstk1002 atngw100
> >> >  
> >> > sh:  +   sh7753evb sh7785lcr_32bit sh7785lcr
> >> >
> >> >arc:  +   arcangel4-be axs101 axs103 tb100 arcangel4
> >> >   
> >> >   openrisc:  +   openrisc-generic
> >> >   
> >> >powerpc:  +   TQM834x katmai
> >> >
> >> >arm:  +   mx28evk mx28evk_nand xfi3 bg0900 sansa_fuze_plus
> >> > 
> >> > mx23evk m28evk sc_sps_1 mx28evk_spi apx4devkit mx23_olinuxino
> >> > mx28evk_auart_console
> >> >>> 
> >> >>> All of MXS is broken, why ? I don't recall any chances to MXS being
> >> >>> done recently, so what happened ?
> >> >> 
> >> >> I confirm this - I have not seen any breakage (but I built today with
> >> >> an older gcc). Bing, can you output what you have seen for mxs
> >> >> boards ? They looks ok to me.
> >> > 
> >> > $ make m28evk_defconfig
> >> > 
> >> >   HOSTCC  scripts/basic/fixdep
> >> >   HOSTCC  scripts/kconfig/conf.o
> >> >   SHIPPED scripts/kconfig/zconf.tab.c
> >> >   SHIPPED scripts/kconfig/zconf.lex.c
> >> >   SHIPPED scripts/kconfig/zconf.hash.c
> >> >   HOSTCC  scripts/kconfig/zconf.tab.o
> >> >   HOSTLD  scripts/kconfig/conf
> >> > 
> >> > #
> >> > # configuration written to .config
> >> > #
> >> > $ make
> >> > scripts/kconfig/conf  --silentoldconfig Kconfig
> >> > 
> >> >   CHK include/config.h
> >> >   UPD include/config.h
> >> >   GEN include/autoconf.mk
> >> >   GEN include/autoconf.mk.dep
> >> >   GEN spl/include/autoconf.mk
> >> >   CHK include/config/uboot.release
> >> >   UPD include/config/uboot.release
> >> >   CHK include/generated/version_autogenerated.h
> >> >   UPD include/generated/version_autogenerated.h
> >> >   CHK include/generated/timestamp_autogenerated.h
> >> >   UPD include/generated/timestamp_autogenerated.h
> >> >   CC  lib/asm-offsets.s
> >> >   CHK include/generated/generic-asm-offsets.h
> >> >   UPD include/generated/generic-asm-offsets.h
> >> >   CC  arch/arm/lib/asm-offsets.s
> >> >   CHK include/generated/asm-offsets.h
> >> >   UPD include/generated/asm-offsets.h
> >> >   HOSTCC  tools/bmp_logo
> >> >   HOSTCC  tools/envcrc.o
> >> >   WRAPtools/lib/crc32.c
> >> >   HOSTCC  tools/lib/crc32.o
> >> >   WRAPtools/common/env_embedded.c
> >> >   HOSTCC  tools/common/env_embedded.o
> >> >   WRAPtools/lib/sha1.c
> >> >   HOSTCC  tools/lib/sha1.o
> >> >   HOSTLD  tools/envcrc
> >> >   HOSTCC  tools/gen_eth_addr
> >> >   HOSTCC  tools/img2srec
> >> >   HOSTCC  tools/mkenvimage.o
> >> >   HOSTCC  tools/os_support.o
> >> >   HOSTLD  tools/mkenvimage
> >> >   HOSTCC  tools/aisimage.o
> >> >   HOSTCC  tools/atmelimage.o
> >> >   WRAPtools/common/bootm.c
> >> >   HOSTCC  tools/common/bootm.o
> >> >   HOSTCC  tools/default_image.o
> >> >   WRAPtools/lib/fdtdec_common.c
> >> >   HOSTCC  tools/lib/fdtdec_common.o
> >> >   WRAPtools/lib/fdtdec.c
> >> >   HOSTCC  tools/lib/fdtdec.o
> >> >   HOSTCC  tools/fit_common.o
> >> >   HOSTCC  tools/fit_image.o
> >> >   HOSTCC  tools/gpimage.o
> >> >   HOSTCC  tools/gpimage-common.o
> >> >   WRAPtools/common/image-fit.c
> >> >   HOSTCC  tools/common/image-fit.o
> >> >   HOSTCC  tools/image-host.o
> >> >   WRAPtools/common/image.c
> >> >   HOSTCC  tools/common/image.o
> >> >   HOSTCC  tools/imagetool.o
> >> >   HOSTCC  tools/imximage.o
> >> >   HOSTCC  tools/kwbimage.o
> >> >   WRAPtools/lib/md5.c
> >> >   HOSTCC  tools/lib/md5.o
> >> >   HOSTCC  tools/lpc32xximage.o
> >> >   HOSTCC  tools/mxsimage.o
> >> >   HOSTCC  tools/omapimage.o
> >> >   HOSTCC  tools/pblimage.o
> >> >   HOSTCC  tools/pbl_crc32.o
> >> >

Re: [U-Boot] buildman errors

2016-01-24 Thread Bin Meng

On Mon, Jan 25, 2016 at 10:42 AM, Bin Meng  wrote:
> On Mon, Jan 25, 2016 at 1:01 AM, Stefano Babic  wrote:
>> On 24/01/2016 17:41, Marek Vasut wrote:
>>> On Sunday, January 24, 2016 at 05:19:54 PM, Tom Rini wrote:
 On Sun, Jan 24, 2016 at 12:00:42PM +0800, Bin Meng wrote:
> Hi,
>
> Summary of 71 commits for 1100 boards (24 threads, 1 job per thread)
> 01: iocon / bamboo: Drop CONFIG_SYS_LONGHELP
>
>   blackfin:  +   bf561-acvilon cm-bf561 blackstamp bf537-minotaur
>
> bct-brettl2 cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1 bf527-ad7160-eval
> bf609-ezkit bf537-stamp bf527-ezkit-v2 cm-bf537e tcm-bf518 cm-bf537u
> bf527-ezkit cm-bf533 bf533-ezkit ibf-dsp561 bf537-pnav bf537-srv1
> cm-bf548 bf538f-ezkit bf548-ezkit bf525-ucr2 blackvme tcm-bf537
> bf533-stamp dnp5370 bf518f-ezbrd bf526-ezbrd bf561-ezkit br4
>
>aarch64:  +   test
>
>  avr32:  +   atngw100mkii grasshopper atstk1002 atngw100
>
> sh:  +   sh7753evb sh7785lcr_32bit sh7785lcr
>
>arc:  +   arcangel4-be axs101 axs103 tb100 arcangel4
>
>   openrisc:  +   openrisc-generic
>
>powerpc:  +   TQM834x katmai
>
>arm:  +   mx28evk mx28evk_nand xfi3 bg0900 sansa_fuze_plus
>
> mx23evk m28evk sc_sps_1 mx28evk_spi apx4devkit mx23_olinuxino
> mx28evk_auart_console
>>>
>>> All of MXS is broken, why ? I don't recall any chances to MXS being done
>>> recently, so what happened ?
>>
>> I confirm this - I have not seen any breakage (but I built today with an
>> older gcc). Bing, can you output what you have seen for mxs boards ?
>> They looks ok to me.
>>
>
> $ make m28evk_defconfig
>   HOSTCC  scripts/basic/fixdep
>   HOSTCC  scripts/kconfig/conf.o
>   SHIPPED scripts/kconfig/zconf.tab.c
>   SHIPPED scripts/kconfig/zconf.lex.c
>   SHIPPED scripts/kconfig/zconf.hash.c
>   HOSTCC  scripts/kconfig/zconf.tab.o
>   HOSTLD  scripts/kconfig/conf
> #
> # configuration written to .config
> #
> $ make
> scripts/kconfig/conf  --silentoldconfig Kconfig
>   CHK include/config.h
>   UPD include/config.h
>   GEN include/autoconf.mk
>   GEN include/autoconf.mk.dep
>   GEN spl/include/autoconf.mk
>   CHK include/config/uboot.release
>   UPD include/config/uboot.release
>   CHK include/generated/version_autogenerated.h
>   UPD include/generated/version_autogenerated.h
>   CHK include/generated/timestamp_autogenerated.h
>   UPD include/generated/timestamp_autogenerated.h
>   CC  lib/asm-offsets.s
>   CHK include/generated/generic-asm-offsets.h
>   UPD include/generated/generic-asm-offsets.h
>   CC  arch/arm/lib/asm-offsets.s
>   CHK include/generated/asm-offsets.h
>   UPD include/generated/asm-offsets.h
>   HOSTCC  tools/bmp_logo
>   HOSTCC  tools/envcrc.o
>   WRAPtools/lib/crc32.c
>   HOSTCC  tools/lib/crc32.o
>   WRAPtools/common/env_embedded.c
>   HOSTCC  tools/common/env_embedded.o
>   WRAPtools/lib/sha1.c
>   HOSTCC  tools/lib/sha1.o
>   HOSTLD  tools/envcrc
>   HOSTCC  tools/gen_eth_addr
>   HOSTCC  tools/img2srec
>   HOSTCC  tools/mkenvimage.o
>   HOSTCC  tools/os_support.o
>   HOSTLD  tools/mkenvimage
>   HOSTCC  tools/aisimage.o
>   HOSTCC  tools/atmelimage.o
>   WRAPtools/common/bootm.c
>   HOSTCC  tools/common/bootm.o
>   HOSTCC  tools/default_image.o
>   WRAPtools/lib/fdtdec_common.c
>   HOSTCC  tools/lib/fdtdec_common.o
>   WRAPtools/lib/fdtdec.c
>   HOSTCC  tools/lib/fdtdec.o
>   HOSTCC  tools/fit_common.o
>   HOSTCC  tools/fit_image.o
>   HOSTCC  tools/gpimage.o
>   HOSTCC  tools/gpimage-common.o
>   WRAPtools/common/image-fit.c
>   HOSTCC  tools/common/image-fit.o
>   HOSTCC  tools/image-host.o
>   WRAPtools/common/image.c
>   HOSTCC  tools/common/image.o
>   HOSTCC  tools/imagetool.o
>   HOSTCC  tools/imximage.o
>   HOSTCC  tools/kwbimage.o
>   WRAPtools/lib/md5.c
>   HOSTCC  tools/lib/md5.o
>   HOSTCC  tools/lpc32xximage.o
>   HOSTCC  tools/mxsimage.o
>   HOSTCC  tools/omapimage.o
>   HOSTCC  tools/pblimage.o
>   HOSTCC  tools/pbl_crc32.o
>   WRAPtools/lib/rc4.c
>   HOSTCC  tools/lib/rc4.o
>   HOSTCC  tools/rkcommon.o
>   HOSTCC  tools/rkimage.o
>   HOSTCC  tools/rksd.o
>   HOSTCC  tools/rkspi.o
>   HOSTCC  tools/socfpgaimage.o
>   WRAPtools/lib/sha256.c
>   HOSTCC  tools/lib/sha256.o
>   WRAPtools/common/hash.c
>   HOSTCC  tools/common/hash.o
>   HOSTCC  tools/ublimage.o
>   HOSTCC  tools/zynqimage.o
>   WRAPtools/lib/libfdt/fdt.c
>   HOSTCC  tools/lib/libfdt/fdt.o
>   WRAPtools/lib/libfdt/fdt_ro.c
>   HOSTCC  tools/lib/libfdt/fdt_ro.o
>   WRAPtools/lib/libfdt/fdt_rw.c
>   HOSTCC  tools/lib/libfdt/fdt_rw.o
>   WRAPtools/lib/libfdt/fdt_strerror.c
>   HOSTCC  tools/lib/libfdt/fdt_strerror.o
>   WRAPtools/lib/libfdt/fdt_wip.c
>   HOSTCC  tools/lib/libfdt/fdt_wip.o
>   WRAPtools/lib/libfdt/fdt_region.c
>   HOSTCC  tools/lib/libfdt/fdt_region.o
>

Re: [U-Boot] buildman errors

2016-01-24 Thread Bin Meng

On Mon, Jan 25, 2016 at 1:01 AM, Stefano Babic  wrote:
> On 24/01/2016 17:41, Marek Vasut wrote:
>> On Sunday, January 24, 2016 at 05:19:54 PM, Tom Rini wrote:
>>> On Sun, Jan 24, 2016 at 12:00:42PM +0800, Bin Meng wrote:
 Hi,

 Summary of 71 commits for 1100 boards (24 threads, 1 job per thread)
 01: iocon / bamboo: Drop CONFIG_SYS_LONGHELP

   blackfin:  +   bf561-acvilon cm-bf561 blackstamp bf537-minotaur

 bct-brettl2 cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1 bf527-ad7160-eval
 bf609-ezkit bf537-stamp bf527-ezkit-v2 cm-bf537e tcm-bf518 cm-bf537u
 bf527-ezkit cm-bf533 bf533-ezkit ibf-dsp561 bf537-pnav bf537-srv1
 cm-bf548 bf538f-ezkit bf548-ezkit bf525-ucr2 blackvme tcm-bf537
 bf533-stamp dnp5370 bf518f-ezbrd bf526-ezbrd bf561-ezkit br4

aarch64:  +   test

  avr32:  +   atngw100mkii grasshopper atstk1002 atngw100

 sh:  +   sh7753evb sh7785lcr_32bit sh7785lcr

arc:  +   arcangel4-be axs101 axs103 tb100 arcangel4

   openrisc:  +   openrisc-generic

powerpc:  +   TQM834x katmai

arm:  +   mx28evk mx28evk_nand xfi3 bg0900 sansa_fuze_plus

 mx23evk m28evk sc_sps_1 mx28evk_spi apx4devkit mx23_olinuxino
 mx28evk_auart_console
>>
>> All of MXS is broken, why ? I don't recall any chances to MXS being done
>> recently, so what happened ?
>
> I confirm this - I have not seen any breakage (but I built today with an
> older gcc). Bing, can you output what you have seen for mxs boards ?
> They looks ok to me.
>

$ make m28evk_defconfig
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/kconfig/conf.o
  SHIPPED scripts/kconfig/zconf.tab.c
  SHIPPED scripts/kconfig/zconf.lex.c
  SHIPPED scripts/kconfig/zconf.hash.c
  HOSTCC  scripts/kconfig/zconf.tab.o
  HOSTLD  scripts/kconfig/conf
#
# configuration written to .config
#
$ make
scripts/kconfig/conf  --silentoldconfig Kconfig
  CHK include/config.h
  UPD include/config.h
  GEN include/autoconf.mk
  GEN include/autoconf.mk.dep
  GEN spl/include/autoconf.mk
  CHK include/config/uboot.release
  UPD include/config/uboot.release
  CHK include/generated/version_autogenerated.h
  UPD include/generated/version_autogenerated.h
  CHK include/generated/timestamp_autogenerated.h
  UPD include/generated/timestamp_autogenerated.h
  CC  lib/asm-offsets.s
  CHK include/generated/generic-asm-offsets.h
  UPD include/generated/generic-asm-offsets.h
  CC  arch/arm/lib/asm-offsets.s
  CHK include/generated/asm-offsets.h
  UPD include/generated/asm-offsets.h
  HOSTCC  tools/bmp_logo
  HOSTCC  tools/envcrc.o
  WRAPtools/lib/crc32.c
  HOSTCC  tools/lib/crc32.o
  WRAPtools/common/env_embedded.c
  HOSTCC  tools/common/env_embedded.o
  WRAPtools/lib/sha1.c
  HOSTCC  tools/lib/sha1.o
  HOSTLD  tools/envcrc
  HOSTCC  tools/gen_eth_addr
  HOSTCC  tools/img2srec
  HOSTCC  tools/mkenvimage.o
  HOSTCC  tools/os_support.o
  HOSTLD  tools/mkenvimage
  HOSTCC  tools/aisimage.o
  HOSTCC  tools/atmelimage.o
  WRAPtools/common/bootm.c
  HOSTCC  tools/common/bootm.o
  HOSTCC  tools/default_image.o
  WRAPtools/lib/fdtdec_common.c
  HOSTCC  tools/lib/fdtdec_common.o
  WRAPtools/lib/fdtdec.c
  HOSTCC  tools/lib/fdtdec.o
  HOSTCC  tools/fit_common.o
  HOSTCC  tools/fit_image.o
  HOSTCC  tools/gpimage.o
  HOSTCC  tools/gpimage-common.o
  WRAPtools/common/image-fit.c
  HOSTCC  tools/common/image-fit.o
  HOSTCC  tools/image-host.o
  WRAPtools/common/image.c
  HOSTCC  tools/common/image.o
  HOSTCC  tools/imagetool.o
  HOSTCC  tools/imximage.o
  HOSTCC  tools/kwbimage.o
  WRAPtools/lib/md5.c
  HOSTCC  tools/lib/md5.o
  HOSTCC  tools/lpc32xximage.o
  HOSTCC  tools/mxsimage.o
  HOSTCC  tools/omapimage.o
  HOSTCC  tools/pblimage.o
  HOSTCC  tools/pbl_crc32.o
  WRAPtools/lib/rc4.c
  HOSTCC  tools/lib/rc4.o
  HOSTCC  tools/rkcommon.o
  HOSTCC  tools/rkimage.o
  HOSTCC  tools/rksd.o
  HOSTCC  tools/rkspi.o
  HOSTCC  tools/socfpgaimage.o
  WRAPtools/lib/sha256.c
  HOSTCC  tools/lib/sha256.o
  WRAPtools/common/hash.c
  HOSTCC  tools/common/hash.o
  HOSTCC  tools/ublimage.o
  HOSTCC  tools/zynqimage.o
  WRAPtools/lib/libfdt/fdt.c
  HOSTCC  tools/lib/libfdt/fdt.o
  WRAPtools/lib/libfdt/fdt_ro.c
  HOSTCC  tools/lib/libfdt/fdt_ro.o
  WRAPtools/lib/libfdt/fdt_rw.c
  HOSTCC  tools/lib/libfdt/fdt_rw.o
  WRAPtools/lib/libfdt/fdt_strerror.c
  HOSTCC  tools/lib/libfdt/fdt_strerror.o
  WRAPtools/lib/libfdt/fdt_wip.c
  HOSTCC  tools/lib/libfdt/fdt_wip.o
  WRAPtools/lib/libfdt/fdt_region.c
  HOSTCC  tools/lib/libfdt/fdt_region.o
  HOSTCC  tools/dumpimage.o
  HOSTLD  tools/dumpimage
  HOSTCC  tools/mkimage.o
  HOSTLD  tools/mkimage
  HOSTCC  tools/mxsboot
tools/mxsboot.c: In function ‘mx28_create_sd_image’:
tools/mxsboot.c:560: warning: implicit declaration of function ‘htole32’
/tmp/cchLIV6q.o: In function `main':

Re: [U-Boot] buildman errors

2016-01-24 Thread Marek Vasut

On Monday, January 25, 2016 at 03:45:25 AM, Bin Meng wrote:
> On Mon, Jan 25, 2016 at 10:42 AM, Bin Meng  wrote:
> > On Mon, Jan 25, 2016 at 1:01 AM, Stefano Babic  wrote:
> >> On 24/01/2016 17:41, Marek Vasut wrote:
> >>> On Sunday, January 24, 2016 at 05:19:54 PM, Tom Rini wrote:
>  On Sun, Jan 24, 2016 at 12:00:42PM +0800, Bin Meng wrote:
> > Hi,
> > 
> > Summary of 71 commits for 1100 boards (24 threads, 1 job per thread)
> > 01: iocon / bamboo: Drop CONFIG_SYS_LONGHELP
> > 
> >   blackfin:  +   bf561-acvilon cm-bf561 blackstamp bf537-minotaur
> > 
> > bct-brettl2 cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1
> > bf527-ad7160-eval bf609-ezkit bf537-stamp bf527-ezkit-v2 cm-bf537e
> > tcm-bf518 cm-bf537u bf527-ezkit cm-bf533 bf533-ezkit ibf-dsp561
> > bf537-pnav bf537-srv1 cm-bf548 bf538f-ezkit bf548-ezkit bf525-ucr2
> > blackvme tcm-bf537 bf533-stamp dnp5370 bf518f-ezbrd bf526-ezbrd
> > bf561-ezkit br4
> > 
> >aarch64:  +   test
> >
> >  avr32:  +   atngw100mkii grasshopper atstk1002 atngw100
> >  
> > sh:  +   sh7753evb sh7785lcr_32bit sh7785lcr
> >
> >arc:  +   arcangel4-be axs101 axs103 tb100 arcangel4
> >   
> >   openrisc:  +   openrisc-generic
> >   
> >powerpc:  +   TQM834x katmai
> >
> >arm:  +   mx28evk mx28evk_nand xfi3 bg0900 sansa_fuze_plus
> > 
> > mx23evk m28evk sc_sps_1 mx28evk_spi apx4devkit mx23_olinuxino
> > mx28evk_auart_console
> >>> 
> >>> All of MXS is broken, why ? I don't recall any chances to MXS being
> >>> done recently, so what happened ?
> >> 
> >> I confirm this - I have not seen any breakage (but I built today with an
> >> older gcc). Bing, can you output what you have seen for mxs boards ?
> >> They looks ok to me.
> > 
> > $ make m28evk_defconfig
> > 
> >   HOSTCC  scripts/basic/fixdep
> >   HOSTCC  scripts/kconfig/conf.o
> >   SHIPPED scripts/kconfig/zconf.tab.c
> >   SHIPPED scripts/kconfig/zconf.lex.c
> >   SHIPPED scripts/kconfig/zconf.hash.c
> >   HOSTCC  scripts/kconfig/zconf.tab.o
> >   HOSTLD  scripts/kconfig/conf
> > 
> > #
> > # configuration written to .config
> > #
> > $ make
> > scripts/kconfig/conf  --silentoldconfig Kconfig
> > 
> >   CHK include/config.h
> >   UPD include/config.h
> >   GEN include/autoconf.mk
> >   GEN include/autoconf.mk.dep
> >   GEN spl/include/autoconf.mk
> >   CHK include/config/uboot.release
> >   UPD include/config/uboot.release
> >   CHK include/generated/version_autogenerated.h
> >   UPD include/generated/version_autogenerated.h
> >   CHK include/generated/timestamp_autogenerated.h
> >   UPD include/generated/timestamp_autogenerated.h
> >   CC  lib/asm-offsets.s
> >   CHK include/generated/generic-asm-offsets.h
> >   UPD include/generated/generic-asm-offsets.h
> >   CC  arch/arm/lib/asm-offsets.s
> >   CHK include/generated/asm-offsets.h
> >   UPD include/generated/asm-offsets.h
> >   HOSTCC  tools/bmp_logo
> >   HOSTCC  tools/envcrc.o
> >   WRAPtools/lib/crc32.c
> >   HOSTCC  tools/lib/crc32.o
> >   WRAPtools/common/env_embedded.c
> >   HOSTCC  tools/common/env_embedded.o
> >   WRAPtools/lib/sha1.c
> >   HOSTCC  tools/lib/sha1.o
> >   HOSTLD  tools/envcrc
> >   HOSTCC  tools/gen_eth_addr
> >   HOSTCC  tools/img2srec
> >   HOSTCC  tools/mkenvimage.o
> >   HOSTCC  tools/os_support.o
> >   HOSTLD  tools/mkenvimage
> >   HOSTCC  tools/aisimage.o
> >   HOSTCC  tools/atmelimage.o
> >   WRAPtools/common/bootm.c
> >   HOSTCC  tools/common/bootm.o
> >   HOSTCC  tools/default_image.o
> >   WRAPtools/lib/fdtdec_common.c
> >   HOSTCC  tools/lib/fdtdec_common.o
> >   WRAPtools/lib/fdtdec.c
> >   HOSTCC  tools/lib/fdtdec.o
> >   HOSTCC  tools/fit_common.o
> >   HOSTCC  tools/fit_image.o
> >   HOSTCC  tools/gpimage.o
> >   HOSTCC  tools/gpimage-common.o
> >   WRAPtools/common/image-fit.c
> >   HOSTCC  tools/common/image-fit.o
> >   HOSTCC  tools/image-host.o
> >   WRAPtools/common/image.c
> >   HOSTCC  tools/common/image.o
> >   HOSTCC  tools/imagetool.o
> >   HOSTCC  tools/imximage.o
> >   HOSTCC  tools/kwbimage.o
> >   WRAPtools/lib/md5.c
> >   HOSTCC  tools/lib/md5.o
> >   HOSTCC  tools/lpc32xximage.o
> >   HOSTCC  tools/mxsimage.o
> >   HOSTCC  tools/omapimage.o
> >   HOSTCC  tools/pblimage.o
> >   HOSTCC  tools/pbl_crc32.o
> >   WRAPtools/lib/rc4.c
> >   HOSTCC  tools/lib/rc4.o
> >   HOSTCC  tools/rkcommon.o
> >   HOSTCC  tools/rkimage.o
> >   HOSTCC  tools/rksd.o
> >   HOSTCC  tools/rkspi.o
> >   HOSTCC  tools/socfpgaimage.o
> >   WRAPtools/lib/sha256.c
> >   HOSTCC  tools/lib/sha256.o
> >   WRAPtools/common/hash.c
> >   HOSTCC  tools/common/hash.o
> >   HOSTCC  tools/ublimage.o
> >   HOSTCC  tools/zynqimage.o
> >   WRAPtools/lib/libfdt/fdt.c
> >   HOSTCC  tools/lib/libfdt/fdt.o
> >   WRAP

Re: [U-Boot] buildman errors

2016-01-24 Thread Tom Rini

On Mon, Jan 25, 2016 at 10:34:16AM +0800, Bin Meng wrote:
> Hi Tom,
> 
> On Mon, Jan 25, 2016 at 12:19 AM, Tom Rini  wrote:
> > On Sun, Jan 24, 2016 at 12:00:42PM +0800, Bin Meng wrote:
> >
> >> Hi,
> >>
> >> Summary of 71 commits for 1100 boards (24 threads, 1 job per thread)
> >> 01: iocon / bamboo: Drop CONFIG_SYS_LONGHELP
> >>   blackfin:  +   bf561-acvilon cm-bf561 blackstamp bf537-minotaur
> >> bct-brettl2 cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1 bf527-ad7160-eval
> >> bf609-ezkit bf537-stamp bf527-ezkit-v2 cm-bf537e tcm-bf518 cm-bf537u
> >> bf527-ezkit cm-bf533 bf533-ezkit ibf-dsp561 bf537-pnav bf537-srv1
> >> cm-bf548 bf538f-ezkit bf548-ezkit bf525-ucr2 blackvme tcm-bf537
> >> bf533-stamp dnp5370 bf518f-ezbrd bf526-ezbrd bf561-ezkit br4
> >>aarch64:  +   test
> >>  avr32:  +   atngw100mkii grasshopper atstk1002 atngw100
> >> sh:  +   sh7753evb sh7785lcr_32bit sh7785lcr
> >>arc:  +   arcangel4-be axs101 axs103 tb100 arcangel4
> >>   openrisc:  +   openrisc-generic
> >>powerpc:  +   TQM834x katmai
> >>arm:  +   mx28evk mx28evk_nand xfi3 bg0900 sansa_fuze_plus
> >> mx23evk m28evk sc_sps_1 mx28evk_spi apx4devkit mx23_olinuxino
> >> mx28evk_auart_console
> >>  nds32:  +   adp-ag101p
> >
> > I need to finally fetch a few toolchains as I don't do
> > avr32/sh/openrisc/nds32 iirc.  As a tangent, x86 is very broken with gcc
> > 5.x, can you look into it? :)
> >
> 
> Sure, I can look into x86. Which gcc 5.x toolchain are you using?

Pretty much any, I've seen it for a long time but not had time to poke
at the libgcc "fun" that's involved here.

-- 
Tom


signature.asc
Description: Digital signature
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] buildman errors

2016-01-24 Thread Bin Meng

Hi Tom,

On Mon, Jan 25, 2016 at 12:19 AM, Tom Rini  wrote:
> On Sun, Jan 24, 2016 at 12:00:42PM +0800, Bin Meng wrote:
>
>> Hi,
>>
>> Summary of 71 commits for 1100 boards (24 threads, 1 job per thread)
>> 01: iocon / bamboo: Drop CONFIG_SYS_LONGHELP
>>   blackfin:  +   bf561-acvilon cm-bf561 blackstamp bf537-minotaur
>> bct-brettl2 cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1 bf527-ad7160-eval
>> bf609-ezkit bf537-stamp bf527-ezkit-v2 cm-bf537e tcm-bf518 cm-bf537u
>> bf527-ezkit cm-bf533 bf533-ezkit ibf-dsp561 bf537-pnav bf537-srv1
>> cm-bf548 bf538f-ezkit bf548-ezkit bf525-ucr2 blackvme tcm-bf537
>> bf533-stamp dnp5370 bf518f-ezbrd bf526-ezbrd bf561-ezkit br4
>>aarch64:  +   test
>>  avr32:  +   atngw100mkii grasshopper atstk1002 atngw100
>> sh:  +   sh7753evb sh7785lcr_32bit sh7785lcr
>>arc:  +   arcangel4-be axs101 axs103 tb100 arcangel4
>>   openrisc:  +   openrisc-generic
>>powerpc:  +   TQM834x katmai
>>arm:  +   mx28evk mx28evk_nand xfi3 bg0900 sansa_fuze_plus
>> mx23evk m28evk sc_sps_1 mx28evk_spi apx4devkit mx23_olinuxino
>> mx28evk_auart_console
>>  nds32:  +   adp-ag101p
>
> I need to finally fetch a few toolchains as I don't do
> avr32/sh/openrisc/nds32 iirc.  As a tangent, x86 is very broken with gcc
> 5.x, can you look into it? :)
>

Sure, I can look into x86. Which gcc 5.x toolchain are you using?

Regards,
Bin
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] buildman errors

2016-01-24 Thread Bin Meng

Hi Marek,

On Mon, Jan 25, 2016 at 10:52 AM, Marek Vasut  wrote:
> On Monday, January 25, 2016 at 03:45:25 AM, Bin Meng wrote:
>> On Mon, Jan 25, 2016 at 10:42 AM, Bin Meng  wrote:
>> > On Mon, Jan 25, 2016 at 1:01 AM, Stefano Babic  wrote:
>> >> On 24/01/2016 17:41, Marek Vasut wrote:
>> >>> On Sunday, January 24, 2016 at 05:19:54 PM, Tom Rini wrote:
>>  On Sun, Jan 24, 2016 at 12:00:42PM +0800, Bin Meng wrote:
>> > Hi,
>> >
>> > Summary of 71 commits for 1100 boards (24 threads, 1 job per thread)
>> > 01: iocon / bamboo: Drop CONFIG_SYS_LONGHELP
>> >
>> >   blackfin:  +   bf561-acvilon cm-bf561 blackstamp bf537-minotaur
>> >
>> > bct-brettl2 cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1
>> > bf527-ad7160-eval bf609-ezkit bf537-stamp bf527-ezkit-v2 cm-bf537e
>> > tcm-bf518 cm-bf537u bf527-ezkit cm-bf533 bf533-ezkit ibf-dsp561
>> > bf537-pnav bf537-srv1 cm-bf548 bf538f-ezkit bf548-ezkit bf525-ucr2
>> > blackvme tcm-bf537 bf533-stamp dnp5370 bf518f-ezbrd bf526-ezbrd
>> > bf561-ezkit br4
>> >
>> >aarch64:  +   test
>> >
>> >  avr32:  +   atngw100mkii grasshopper atstk1002 atngw100
>> >
>> > sh:  +   sh7753evb sh7785lcr_32bit sh7785lcr
>> >
>> >arc:  +   arcangel4-be axs101 axs103 tb100 arcangel4
>> >
>> >   openrisc:  +   openrisc-generic
>> >
>> >powerpc:  +   TQM834x katmai
>> >
>> >arm:  +   mx28evk mx28evk_nand xfi3 bg0900 sansa_fuze_plus
>> >
>> > mx23evk m28evk sc_sps_1 mx28evk_spi apx4devkit mx23_olinuxino
>> > mx28evk_auart_console
>> >>>
>> >>> All of MXS is broken, why ? I don't recall any chances to MXS being
>> >>> done recently, so what happened ?
>> >>
>> >> I confirm this - I have not seen any breakage (but I built today with an
>> >> older gcc). Bing, can you output what you have seen for mxs boards ?
>> >> They looks ok to me.
>> >
>> > $ make m28evk_defconfig
>> >
>> >   HOSTCC  scripts/basic/fixdep
>> >   HOSTCC  scripts/kconfig/conf.o
>> >   SHIPPED scripts/kconfig/zconf.tab.c
>> >   SHIPPED scripts/kconfig/zconf.lex.c
>> >   SHIPPED scripts/kconfig/zconf.hash.c
>> >   HOSTCC  scripts/kconfig/zconf.tab.o
>> >   HOSTLD  scripts/kconfig/conf
>> >
>> > #
>> > # configuration written to .config
>> > #
>> > $ make
>> > scripts/kconfig/conf  --silentoldconfig Kconfig
>> >
>> >   CHK include/config.h
>> >   UPD include/config.h
>> >   GEN include/autoconf.mk
>> >   GEN include/autoconf.mk.dep
>> >   GEN spl/include/autoconf.mk
>> >   CHK include/config/uboot.release
>> >   UPD include/config/uboot.release
>> >   CHK include/generated/version_autogenerated.h
>> >   UPD include/generated/version_autogenerated.h
>> >   CHK include/generated/timestamp_autogenerated.h
>> >   UPD include/generated/timestamp_autogenerated.h
>> >   CC  lib/asm-offsets.s
>> >   CHK include/generated/generic-asm-offsets.h
>> >   UPD include/generated/generic-asm-offsets.h
>> >   CC  arch/arm/lib/asm-offsets.s
>> >   CHK include/generated/asm-offsets.h
>> >   UPD include/generated/asm-offsets.h
>> >   HOSTCC  tools/bmp_logo
>> >   HOSTCC  tools/envcrc.o
>> >   WRAPtools/lib/crc32.c
>> >   HOSTCC  tools/lib/crc32.o
>> >   WRAPtools/common/env_embedded.c
>> >   HOSTCC  tools/common/env_embedded.o
>> >   WRAPtools/lib/sha1.c
>> >   HOSTCC  tools/lib/sha1.o
>> >   HOSTLD  tools/envcrc
>> >   HOSTCC  tools/gen_eth_addr
>> >   HOSTCC  tools/img2srec
>> >   HOSTCC  tools/mkenvimage.o
>> >   HOSTCC  tools/os_support.o
>> >   HOSTLD  tools/mkenvimage
>> >   HOSTCC  tools/aisimage.o
>> >   HOSTCC  tools/atmelimage.o
>> >   WRAPtools/common/bootm.c
>> >   HOSTCC  tools/common/bootm.o
>> >   HOSTCC  tools/default_image.o
>> >   WRAPtools/lib/fdtdec_common.c
>> >   HOSTCC  tools/lib/fdtdec_common.o
>> >   WRAPtools/lib/fdtdec.c
>> >   HOSTCC  tools/lib/fdtdec.o
>> >   HOSTCC  tools/fit_common.o
>> >   HOSTCC  tools/fit_image.o
>> >   HOSTCC  tools/gpimage.o
>> >   HOSTCC  tools/gpimage-common.o
>> >   WRAPtools/common/image-fit.c
>> >   HOSTCC  tools/common/image-fit.o
>> >   HOSTCC  tools/image-host.o
>> >   WRAPtools/common/image.c
>> >   HOSTCC  tools/common/image.o
>> >   HOSTCC  tools/imagetool.o
>> >   HOSTCC  tools/imximage.o
>> >   HOSTCC  tools/kwbimage.o
>> >   WRAPtools/lib/md5.c
>> >   HOSTCC  tools/lib/md5.o
>> >   HOSTCC  tools/lpc32xximage.o
>> >   HOSTCC  tools/mxsimage.o
>> >   HOSTCC  tools/omapimage.o
>> >   HOSTCC  tools/pblimage.o
>> >   HOSTCC  tools/pbl_crc32.o
>> >   WRAPtools/lib/rc4.c
>> >   HOSTCC  tools/lib/rc4.o
>> >   HOSTCC  tools/rkcommon.o
>> >   HOSTCC  tools/rkimage.o
>> >   HOSTCC  tools/rksd.o
>> >   HOSTCC  tools/rkspi.o
>> >   HOSTCC  tools/socfpgaimage.o
>> >   WRAPtools/lib/sha256.c
>> >   HOSTCC  tools/lib/sha256.o
>> >   WRAPtools/common/hash.c
>> >   HOSTCC

Re: [U-Boot] buildman errors

2016-01-24 Thread Bin Meng

Hi Marek,

On Mon, Jan 25, 2016 at 11:01 AM, Marek Vasut  wrote:
> On Monday, January 25, 2016 at 03:58:38 AM, Bin Meng wrote:
>> Hi Marek,
>>
>> On Mon, Jan 25, 2016 at 10:52 AM, Marek Vasut  wrote:
>> > On Monday, January 25, 2016 at 03:45:25 AM, Bin Meng wrote:
>> >> On Mon, Jan 25, 2016 at 10:42 AM, Bin Meng  wrote:
>> >> > On Mon, Jan 25, 2016 at 1:01 AM, Stefano Babic  wrote:
>> >> >> On 24/01/2016 17:41, Marek Vasut wrote:
>> >> >>> On Sunday, January 24, 2016 at 05:19:54 PM, Tom Rini wrote:
>> >>  On Sun, Jan 24, 2016 at 12:00:42PM +0800, Bin Meng wrote:
>> >> > Hi,
>> >> >
>> >> > Summary of 71 commits for 1100 boards (24 threads, 1 job per
>> >> > thread) 01: iocon / bamboo: Drop CONFIG_SYS_LONGHELP
>> >> >
>> >> >   blackfin:  +   bf561-acvilon cm-bf561 blackstamp bf537-minotaur
>> >> >
>> >> > bct-brettl2 cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1
>> >> > bf527-ad7160-eval bf609-ezkit bf537-stamp bf527-ezkit-v2 cm-bf537e
>> >> > tcm-bf518 cm-bf537u bf527-ezkit cm-bf533 bf533-ezkit ibf-dsp561
>> >> > bf537-pnav bf537-srv1 cm-bf548 bf538f-ezkit bf548-ezkit bf525-ucr2
>> >> > blackvme tcm-bf537 bf533-stamp dnp5370 bf518f-ezbrd bf526-ezbrd
>> >> > bf561-ezkit br4
>> >> >
>> >> >aarch64:  +   test
>> >> >
>> >> >  avr32:  +   atngw100mkii grasshopper atstk1002 atngw100
>> >> >
>> >> > sh:  +   sh7753evb sh7785lcr_32bit sh7785lcr
>> >> >
>> >> >arc:  +   arcangel4-be axs101 axs103 tb100 arcangel4
>> >> >
>> >> >   openrisc:  +   openrisc-generic
>> >> >
>> >> >powerpc:  +   TQM834x katmai
>> >> >
>> >> >arm:  +   mx28evk mx28evk_nand xfi3 bg0900 sansa_fuze_plus
>> >> >
>> >> > mx23evk m28evk sc_sps_1 mx28evk_spi apx4devkit mx23_olinuxino
>> >> > mx28evk_auart_console
>> >> >>>
>> >> >>> All of MXS is broken, why ? I don't recall any chances to MXS being
>> >> >>> done recently, so what happened ?
>> >> >>
>> >> >> I confirm this - I have not seen any breakage (but I built today with
>> >> >> an older gcc). Bing, can you output what you have seen for mxs
>> >> >> boards ? They looks ok to me.
>> >> >
>> >> > $ make m28evk_defconfig
>> >> >
>> >> >   HOSTCC  scripts/basic/fixdep
>> >> >   HOSTCC  scripts/kconfig/conf.o
>> >> >   SHIPPED scripts/kconfig/zconf.tab.c
>> >> >   SHIPPED scripts/kconfig/zconf.lex.c
>> >> >   SHIPPED scripts/kconfig/zconf.hash.c
>> >> >   HOSTCC  scripts/kconfig/zconf.tab.o
>> >> >   HOSTLD  scripts/kconfig/conf
>> >> >
>> >> > #
>> >> > # configuration written to .config
>> >> > #
>> >> > $ make
>> >> > scripts/kconfig/conf  --silentoldconfig Kconfig
>> >> >
>> >> >   CHK include/config.h
>> >> >   UPD include/config.h
>> >> >   GEN include/autoconf.mk
>> >> >   GEN include/autoconf.mk.dep
>> >> >   GEN spl/include/autoconf.mk
>> >> >   CHK include/config/uboot.release
>> >> >   UPD include/config/uboot.release
>> >> >   CHK include/generated/version_autogenerated.h
>> >> >   UPD include/generated/version_autogenerated.h
>> >> >   CHK include/generated/timestamp_autogenerated.h
>> >> >   UPD include/generated/timestamp_autogenerated.h
>> >> >   CC  lib/asm-offsets.s
>> >> >   CHK include/generated/generic-asm-offsets.h
>> >> >   UPD include/generated/generic-asm-offsets.h
>> >> >   CC  arch/arm/lib/asm-offsets.s
>> >> >   CHK include/generated/asm-offsets.h
>> >> >   UPD include/generated/asm-offsets.h
>> >> >   HOSTCC  tools/bmp_logo
>> >> >   HOSTCC  tools/envcrc.o
>> >> >   WRAPtools/lib/crc32.c
>> >> >   HOSTCC  tools/lib/crc32.o
>> >> >   WRAPtools/common/env_embedded.c
>> >> >   HOSTCC  tools/common/env_embedded.o
>> >> >   WRAPtools/lib/sha1.c
>> >> >   HOSTCC  tools/lib/sha1.o
>> >> >   HOSTLD  tools/envcrc
>> >> >   HOSTCC  tools/gen_eth_addr
>> >> >   HOSTCC  tools/img2srec
>> >> >   HOSTCC  tools/mkenvimage.o
>> >> >   HOSTCC  tools/os_support.o
>> >> >   HOSTLD  tools/mkenvimage
>> >> >   HOSTCC  tools/aisimage.o
>> >> >   HOSTCC  tools/atmelimage.o
>> >> >   WRAPtools/common/bootm.c
>> >> >   HOSTCC  tools/common/bootm.o
>> >> >   HOSTCC  tools/default_image.o
>> >> >   WRAPtools/lib/fdtdec_common.c
>> >> >   HOSTCC  tools/lib/fdtdec_common.o
>> >> >   WRAPtools/lib/fdtdec.c
>> >> >   HOSTCC  tools/lib/fdtdec.o
>> >> >   HOSTCC  tools/fit_common.o
>> >> >   HOSTCC  tools/fit_image.o
>> >> >   HOSTCC  tools/gpimage.o
>> >> >   HOSTCC  tools/gpimage-common.o
>> >> >   WRAPtools/common/image-fit.c
>> >> >   HOSTCC  tools/common/image-fit.o
>> >> >   HOSTCC  tools/image-host.o
>> >> >   WRAPtools/common/image.c
>> >> >   HOSTCC  tools/common/image.o
>> >> >   HOSTCC  tools/imagetool.o
>> >> >   HOSTCC  tools/imximage.o
>> >> >   HOSTCC  tools/kwbimage.o
>> >> >   WRAPtools/lib/md5.c
>> >> >   HOSTCC  tools/lib/md5.o
>> >> >   HOSTCC

Re: [U-Boot] buildman errors

2016-01-24 Thread Bin Meng

Hi Tom,

On Mon, Jan 25, 2016 at 11:05 AM, Tom Rini  wrote:
> On Mon, Jan 25, 2016 at 10:34:16AM +0800, Bin Meng wrote:
>> Hi Tom,
>>
>> On Mon, Jan 25, 2016 at 12:19 AM, Tom Rini  wrote:
>> > On Sun, Jan 24, 2016 at 12:00:42PM +0800, Bin Meng wrote:
>> >
>> >> Hi,
>> >>
>> >> Summary of 71 commits for 1100 boards (24 threads, 1 job per thread)
>> >> 01: iocon / bamboo: Drop CONFIG_SYS_LONGHELP
>> >>   blackfin:  +   bf561-acvilon cm-bf561 blackstamp bf537-minotaur
>> >> bct-brettl2 cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1 bf527-ad7160-eval
>> >> bf609-ezkit bf537-stamp bf527-ezkit-v2 cm-bf537e tcm-bf518 cm-bf537u
>> >> bf527-ezkit cm-bf533 bf533-ezkit ibf-dsp561 bf537-pnav bf537-srv1
>> >> cm-bf548 bf538f-ezkit bf548-ezkit bf525-ucr2 blackvme tcm-bf537
>> >> bf533-stamp dnp5370 bf518f-ezbrd bf526-ezbrd bf561-ezkit br4
>> >>aarch64:  +   test
>> >>  avr32:  +   atngw100mkii grasshopper atstk1002 atngw100
>> >> sh:  +   sh7753evb sh7785lcr_32bit sh7785lcr
>> >>arc:  +   arcangel4-be axs101 axs103 tb100 arcangel4
>> >>   openrisc:  +   openrisc-generic
>> >>powerpc:  +   TQM834x katmai
>> >>arm:  +   mx28evk mx28evk_nand xfi3 bg0900 sansa_fuze_plus
>> >> mx23evk m28evk sc_sps_1 mx28evk_spi apx4devkit mx23_olinuxino
>> >> mx28evk_auart_console
>> >>  nds32:  +   adp-ag101p
>> >
>> > I need to finally fetch a few toolchains as I don't do
>> > avr32/sh/openrisc/nds32 iirc.  As a tangent, x86 is very broken with gcc
>> > 5.x, can you look into it? :)
>> >
>>
>> Sure, I can look into x86. Which gcc 5.x toolchain are you using?
>
> Pretty much any, I've seen it for a long time but not had time to poke
> at the libgcc "fun" that's involved here.
>

I mean if there is any prebuilt gcc 5.x for me to grab and test? Or do
I need build one from gcc source?

Regards,
Bin
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] buildman errors

2016-01-24 Thread Stefano Babic

On 24/01/2016 17:41, Marek Vasut wrote:
> On Sunday, January 24, 2016 at 05:19:54 PM, Tom Rini wrote:
>> On Sun, Jan 24, 2016 at 12:00:42PM +0800, Bin Meng wrote:
>>> Hi,
>>>
>>> Summary of 71 commits for 1100 boards (24 threads, 1 job per thread)
>>> 01: iocon / bamboo: Drop CONFIG_SYS_LONGHELP
>>>
>>>   blackfin:  +   bf561-acvilon cm-bf561 blackstamp bf537-minotaur
>>>
>>> bct-brettl2 cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1 bf527-ad7160-eval
>>> bf609-ezkit bf537-stamp bf527-ezkit-v2 cm-bf537e tcm-bf518 cm-bf537u
>>> bf527-ezkit cm-bf533 bf533-ezkit ibf-dsp561 bf537-pnav bf537-srv1
>>> cm-bf548 bf538f-ezkit bf548-ezkit bf525-ucr2 blackvme tcm-bf537
>>> bf533-stamp dnp5370 bf518f-ezbrd bf526-ezbrd bf561-ezkit br4
>>>
>>>aarch64:  +   test
>>>
>>>  avr32:  +   atngw100mkii grasshopper atstk1002 atngw100
>>>  
>>> sh:  +   sh7753evb sh7785lcr_32bit sh7785lcr
>>>
>>>arc:  +   arcangel4-be axs101 axs103 tb100 arcangel4
>>>   
>>>   openrisc:  +   openrisc-generic
>>>   
>>>powerpc:  +   TQM834x katmai
>>>
>>>arm:  +   mx28evk mx28evk_nand xfi3 bg0900 sansa_fuze_plus
>>>
>>> mx23evk m28evk sc_sps_1 mx28evk_spi apx4devkit mx23_olinuxino
>>> mx28evk_auart_console
> 
> All of MXS is broken, why ? I don't recall any chances to MXS being done
> recently, so what happened ?

I confirm this - I have not seen any breakage (but I built today with an
older gcc). Bing, can you output what you have seen for mxs boards ?
They looks ok to me.

Best regards,
Stefano Babic


-- 
=
DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
=
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] buildman errors

2016-01-24 Thread Tom Rini

On Sun, Jan 24, 2016 at 12:00:42PM +0800, Bin Meng wrote:

> Hi,
> 
> Summary of 71 commits for 1100 boards (24 threads, 1 job per thread)
> 01: iocon / bamboo: Drop CONFIG_SYS_LONGHELP
>   blackfin:  +   bf561-acvilon cm-bf561 blackstamp bf537-minotaur
> bct-brettl2 cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1 bf527-ad7160-eval
> bf609-ezkit bf537-stamp bf527-ezkit-v2 cm-bf537e tcm-bf518 cm-bf537u
> bf527-ezkit cm-bf533 bf533-ezkit ibf-dsp561 bf537-pnav bf537-srv1
> cm-bf548 bf538f-ezkit bf548-ezkit bf525-ucr2 blackvme tcm-bf537
> bf533-stamp dnp5370 bf518f-ezbrd bf526-ezbrd bf561-ezkit br4
>aarch64:  +   test
>  avr32:  +   atngw100mkii grasshopper atstk1002 atngw100
> sh:  +   sh7753evb sh7785lcr_32bit sh7785lcr
>arc:  +   arcangel4-be axs101 axs103 tb100 arcangel4
>   openrisc:  +   openrisc-generic
>powerpc:  +   TQM834x katmai
>arm:  +   mx28evk mx28evk_nand xfi3 bg0900 sansa_fuze_plus
> mx23evk m28evk sc_sps_1 mx28evk_spi apx4devkit mx23_olinuxino
> mx28evk_auart_console
>  nds32:  +   adp-ag101p

I need to finally fetch a few toolchains as I don't do
avr32/sh/openrisc/nds32 iirc.  As a tangent, x86 is very broken with gcc
5.x, can you look into it? :)

-- 
Tom


signature.asc
Description: Digital signature
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] buildman errors

2016-01-24 Thread Marek Vasut

On Sunday, January 24, 2016 at 05:19:54 PM, Tom Rini wrote:
> On Sun, Jan 24, 2016 at 12:00:42PM +0800, Bin Meng wrote:
> > Hi,
> > 
> > Summary of 71 commits for 1100 boards (24 threads, 1 job per thread)
> > 01: iocon / bamboo: Drop CONFIG_SYS_LONGHELP
> > 
> >   blackfin:  +   bf561-acvilon cm-bf561 blackstamp bf537-minotaur
> > 
> > bct-brettl2 cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1 bf527-ad7160-eval
> > bf609-ezkit bf537-stamp bf527-ezkit-v2 cm-bf537e tcm-bf518 cm-bf537u
> > bf527-ezkit cm-bf533 bf533-ezkit ibf-dsp561 bf537-pnav bf537-srv1
> > cm-bf548 bf538f-ezkit bf548-ezkit bf525-ucr2 blackvme tcm-bf537
> > bf533-stamp dnp5370 bf518f-ezbrd bf526-ezbrd bf561-ezkit br4
> > 
> >aarch64:  +   test
> >
> >  avr32:  +   atngw100mkii grasshopper atstk1002 atngw100
> >  
> > sh:  +   sh7753evb sh7785lcr_32bit sh7785lcr
> >
> >arc:  +   arcangel4-be axs101 axs103 tb100 arcangel4
> >   
> >   openrisc:  +   openrisc-generic
> >   
> >powerpc:  +   TQM834x katmai
> >
> >arm:  +   mx28evk mx28evk_nand xfi3 bg0900 sansa_fuze_plus
> > 
> > mx23evk m28evk sc_sps_1 mx28evk_spi apx4devkit mx23_olinuxino
> > mx28evk_auart_console

All of MXS is broken, why ? I don't recall any chances to MXS being done
recently, so what happened ?

> >  nds32:  +   adp-ag101p
> 
> I need to finally fetch a few toolchains as I don't do
> avr32/sh/openrisc/nds32 iirc.  As a tangent, x86 is very broken with gcc
> 5.x, can you look into it? :)

Best regards,
Marek Vasut
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] buildman errors

2016-01-24 Thread Tom Rini

On Sun, Jan 24, 2016 at 06:01:44PM +0100, Stefano Babic wrote:
> On 24/01/2016 17:41, Marek Vasut wrote:
> > On Sunday, January 24, 2016 at 05:19:54 PM, Tom Rini wrote:
> >> On Sun, Jan 24, 2016 at 12:00:42PM +0800, Bin Meng wrote:
> >>> Hi,
> >>>
> >>> Summary of 71 commits for 1100 boards (24 threads, 1 job per thread)
> >>> 01: iocon / bamboo: Drop CONFIG_SYS_LONGHELP
> >>>
> >>>   blackfin:  +   bf561-acvilon cm-bf561 blackstamp bf537-minotaur
> >>>
> >>> bct-brettl2 cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1 bf527-ad7160-eval
> >>> bf609-ezkit bf537-stamp bf527-ezkit-v2 cm-bf537e tcm-bf518 cm-bf537u
> >>> bf527-ezkit cm-bf533 bf533-ezkit ibf-dsp561 bf537-pnav bf537-srv1
> >>> cm-bf548 bf538f-ezkit bf548-ezkit bf525-ucr2 blackvme tcm-bf537
> >>> bf533-stamp dnp5370 bf518f-ezbrd bf526-ezbrd bf561-ezkit br4
> >>>
> >>>aarch64:  +   test
> >>>
> >>>  avr32:  +   atngw100mkii grasshopper atstk1002 atngw100
> >>>  
> >>> sh:  +   sh7753evb sh7785lcr_32bit sh7785lcr
> >>>
> >>>arc:  +   arcangel4-be axs101 axs103 tb100 arcangel4
> >>>   
> >>>   openrisc:  +   openrisc-generic
> >>>   
> >>>powerpc:  +   TQM834x katmai
> >>>
> >>>arm:  +   mx28evk mx28evk_nand xfi3 bg0900 sansa_fuze_plus
> >>>
> >>> mx23evk m28evk sc_sps_1 mx28evk_spi apx4devkit mx23_olinuxino
> >>> mx28evk_auart_console
> > 
> > All of MXS is broken, why ? I don't recall any chances to MXS being done
> > recently, so what happened ?
> 
> I confirm this - I have not seen any breakage (but I built today with an
> older gcc). Bing, can you output what you have seen for mxs boards ?
> They looks ok to me.

They're good for me too, BUT! I suspect it comes down to the openssl-dev
requirement on the host side which I also have thought Marek noted at
some point as a problem anyhow due to license issues maybe?

-- 
Tom


signature.asc
Description: Digital signature
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] buildman errors

2016-01-23 Thread Bin Meng

Hi,

Summary of 71 commits for 1100 boards (24 threads, 1 job per thread)
01: iocon / bamboo: Drop CONFIG_SYS_LONGHELP
  blackfin:  +   bf561-acvilon cm-bf561 blackstamp bf537-minotaur
bct-brettl2 cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1 bf527-ad7160-eval
bf609-ezkit bf537-stamp bf527-ezkit-v2 cm-bf537e tcm-bf518 cm-bf537u
bf527-ezkit cm-bf533 bf533-ezkit ibf-dsp561 bf537-pnav bf537-srv1
cm-bf548 bf538f-ezkit bf548-ezkit bf525-ucr2 blackvme tcm-bf537
bf533-stamp dnp5370 bf518f-ezbrd bf526-ezbrd bf561-ezkit br4
   aarch64:  +   test
 avr32:  +   atngw100mkii grasshopper atstk1002 atngw100
sh:  +   sh7753evb sh7785lcr_32bit sh7785lcr
   arc:  +   arcangel4-be axs101 axs103 tb100 arcangel4
  openrisc:  +   openrisc-generic
   powerpc:  +   TQM834x katmai
   arm:  +   mx28evk mx28evk_nand xfi3 bg0900 sansa_fuze_plus
mx23evk m28evk sc_sps_1 mx28evk_spi apx4devkit mx23_olinuxino
mx28evk_auart_console
 nds32:  +   adp-ag101p
+In file included from ../include/common.h:86,
+ from ../lib/asm-offsets.c:15:
+../include/part.h:13: error: redefinition of typedef ‘block_dev_desc_t’
+../include/ide.h:44: error: previous declaration of ‘block_dev_desc_t’ was here
+make[2]: *** [lib/asm-offsets.s] Error 1
+make[1]: *** [prepare0] Error 2
+make: *** [sub-make] Error 2
+../tools/mxsboot.c: In function ‘mx28_create_sd_image’:
+../tools/mxsboot.c:560: warning: implicit declaration of function ‘htole32’
+/tmp/ccTLvksq.o: In function `main':
+mxsboot.c:(.text+0x6d8): undefined reference to `htole32'
+mxsboot.c:(.text+0x6e7): undefined reference to `htole32'
+mxsboot.c:(.text+0x6f6): undefined reference to `htole32'
+mxsboot.c:(.text+0x705): undefined reference to `htole32'
+mxsboot.c:(.text+0x711): undefined reference to `htole32'
+/tmp/ccTLvksq.o:mxsboot.c:(.text+0x71d): more undefined references to
`htole32' follow
+collect2: ld returned 1 exit status
+make[2]: *** [tools/mxsboot] Error 1
+make[1]: *** [tools] Error 2
+In file included from ../include/common.h:86:0,
+../include/part.h:13:31: error: redefinition of typedef 'block_dev_desc_t'
+../include/ide.h:44:31: note: previous declaration of
'block_dev_desc_t' was here
+board/renesas/sh7753evb/built-in.o: In function `init_gether_mdio':
+build/../board/renesas/sh7753evb/sh7753evb.c:94: undefined reference
to `PMB_ADDR_BASE'
+build/../board/renesas/sh7753evb/sh7753evb.c:94: undefined reference
to `PMB_DATA_BASE'
+build/../board/renesas/sh7753evb/sh7753evb.c:94: undefined reference
to `mk_pmb_addr_val'
+build/../board/renesas/sh7753evb/sh7753evb.c:94: undefined reference
to `mk_pmb_data_val'
+make[1]: *** [u-boot] Error 1
+/tmp/cc4yyPwX.o: In function `main':
+/tmp/cc4yyPwX.o:mxsboot.c:(.text+0x71d): more undefined references to
`htole32' follow
+../include/part.h:13: error: redefinition of typedef 'block_dev_desc_t'
+../include/ide.h:44: note: previous declaration of 'block_dev_desc_t' was here
+/tmp/cc2IW0SD.o: In function `main':
+/tmp/cc2IW0SD.o:mxsboot.c:(.text+0x71d): more undefined references to
`htole32' follow
+../include/ide.h:44: error: previous declaration of 'block_dev_desc_t' was here
+/tmp/ccbcq0iG.o: In function `main':
+/tmp/ccbcq0iG.o:mxsboot.c:(.text+0x71d): more undefined references to
`htole32' follow
+/tmp/ccMo5qYk.o: In function `main':
+/tmp/ccMo5qYk.o:mxsboot.c:(.text+0x71d): more undefined references to
`htole32' follow
+(((base + size - 1) >> CSBNDS_EA_SHIFT) &
+^
+../board/tqc/tqm834x/tqm834x.c:80:2: note: containing loop
+  for(cs = 0; cs < 4; ++cs) {
+  ^
+/tmp/ccgFlFwP.o: In function `main':
+/tmp/ccgFlFwP.o:mxsboot.c:(.text+0x71d): more undefined references to
`htole32' follow
+In file included from ../include/linux/byteorder/big_endian.h:14:0,
+ from ../arch/powerpc/include/asm/byteorder.h:82,
+ from ../arch/powerpc/include/asm/bitops.h:8,
+ from ../include/linux/bitops.h:123,
+ from ../include/common.h:20,
+ from ../drivers/net/eepro100.c:8:
+  return le16_to_cpu (*(volatile u16 *) (addr + dev->iobase));
+   ^
+../include/linux/byteorder/swab.h:81:31: note: in definition of macro
'__swab16'
+ (__builtin_constant_p((__u16)(x)) ? \
+   ^
+../include/linux/byteorder/generic.h:92:21: note: in expansion of
macro '__le16_to_cpu'
+ #define le16_to_cpu __le16_to_cpu
+ ^
+../drivers/net/eepro100.c:243:9: note: in expansion of macro 'le16_to_cpu'
+ ^
+../include/linux/byteorder/swab.h:23:13: note: in definition of macro
'___swab16'
+   (((__u16)(x) & (__u16)0x00ffU) << 8) | \
+ ^
+../include/linux/byteorder/big_endian.h:37:26: note: in expansion of
macro '__swab16'
+ #define __le16_to_cpu(x) __swab16((__force __u16)(__le16)(x))
+  ^
+../include/linux/byteorder/swab.h:24:13: note: in definition of macro
'___swab16'
+   (((__u16)(x) & (__u16)0xff00U) >> 8) ))
+../include/linux/byteorder/swab.h:83:13: note: in

Re: [U-Boot] buildman errors

Re: [U-Boot] buildman errors

Re: [U-Boot] buildman errors

Re: [U-Boot] buildman errors

Re: [U-Boot] buildman errors

Re: [U-Boot] buildman errors

Re: [U-Boot] buildman errors

Re: [U-Boot] buildman errors

Re: [U-Boot] buildman errors

Re: [U-Boot] buildman errors

Re: [U-Boot] buildman errors

Re: [U-Boot] buildman errors

Re: [U-Boot] buildman errors

Re: [U-Boot] buildman errors

Re: [U-Boot] buildman errors

Re: [U-Boot] buildman errors

Re: [U-Boot] buildman errors

Re: [U-Boot] buildman errors

Re: [U-Boot] buildman errors

Re: [U-Boot] buildman errors

Re: [U-Boot] buildman errors

[U-Boot] buildman errors

22 matches

Site Navigation

Mail list logo

Footer information